On Wednesday 19 November 2003 02:15 pm, Bruce Evans wrote:
>
> Anyway, the stuff to the left of the slash in the above is the list
> of active consoles and the stuff to the right of the slash is the
> list of possible consoles. You have to move stuff from one list to
> the other. I vaguely rememb
On Tuesday 18 November 2003 08:29 pm, Bruce Evans wrote:
>
> This could be from a speed mismatch or from kern.consmute somehwo getting
> set.
I had wondered about a speed mismatch, but everything I've found says
9600. I did not know to look at kern.consmute. I'll check that.
> - -current has th
On Monday 17 November 2003 04:41 pm, Mike Durian wrote:
>
> I was finally able to get some partial success by setting flag 0x30
> for sio1. When I'd boot, I'd get console messages on my remote
> tip session. However, I'd only receive those messages printed
> fr
On Monday 17 November 2003 02:09 pm, Doug White wrote:
>
> Set flag 0x80 on sio1 and take it off of sio0. Thats what the kernel uses
> to decide which port to use. The BOOT_COMCONSOLE_PORT is used by loader
> only.
I was finally able to get some partial success by setting flag 0x30
for sio1. Whe
On Monday 17 November 2003 10:50 am, Doug White wrote:
>
> To debug this, you will need to set up a serial console with some special
> kernel options. Instructions for booting with serial console are in the
> Handbook, but you will have to compile with the following kernel options:
Is there a tri
I'm using -current cvsup'd as of Nov 15, 2003. When I try to do a
dump or run the btape (fill command) program from bacula, my machine
will lock up hard. Doesn't respond to ping. No access to kernel
debugger. Num lock doesn't come on.
I can perform a dump or run the btape fill program when in
I've filed a bug report on this
http://www.freebsd.org/cgi/query-pr.cgi?pr=45684
but was wondering if anyone else had seen this message on an SMP machine.
Is it a known problem with a know work around? I'm running code from
11/24/02. Load averages and related things also read 0.
You can find
