[plug] Weird kernel/boot up messages

[Cameron Patrick]

On Wed, Dec 10, 2003 at 08:32:46PM +0800, James Devenish wrote:

| > sym.0.6.0: setting PCI_COMMAND_INVALIDATE.
| > sym0: <810a> rev 0x11 on pci bus 0 device 6 function 0 irq 11
| > sym0: No NVRAM, ID 7, Fast-10, SE, parity checking
| > sym0: SCSI BUS has been reset.
| 
| Does the sym driver (I presume that's what this comment means) have
| documentation?

There's a 45k Documentation.txt in .../drivers/scsi/sym53c8xx_2/
directory, which doesn't mention what PCI_COMMAND_INVALIDATE might mean
anywhere.  Probably it's harmless?

| > /etc/init.d/rcS: System clock was not updated at this time.
| 
| % fgrep -l 'this time' /etc/init.d
| /etc/init.d/hwclockfirst.sh

Looking at that file... it looks like it's due to the system clock being
in local time rather than GMT?  The machine's ends up with the right
time and time zone so perhaps I shouldn't be too concerned.

| > Debian GNU/Linux 3.0 berty ttyS0
| > berty login: INIT: Id "1" respawning too fast: disabled for 5 minutes
| 
| Presumably you have a line similar to this, in your inittab:
| 
| 1:2345:respawn:/sbin/getty 38400 tty1
| 
| Could the error be somewhat related to:
| > Couldnt get a file descriptor referring to the console
| 
| Is there some kind of device assignment that is not occuring?

Yeah, that's what it looks like to me too - something screwy with
/dev/tty*.  I'm using a serial console, which is something I've never
attempted before, and it's possible I've not set it up properly.  But
I'd have thought that even though the console is on a different physical
device, it would still look no different to the rest of the system to a
console on a VGA card?

Cameron.