Chagas, Jason writes:
> Just a bit more of information... The kernel hangs right after "init: memory
> vi". Then it spews an endless string of "*** CONSOLE_ERROR" messages:
Aha! I recognise that as one of my checks in my old console code!
> Starting kswapd v 1.4.2.2
> Keyboard driver v1.01
> **** Turning off console printing ****
> LSB: Done with kbd_init
> SA1100 Serial driver version 4.13 with no serial options enabled
> tty00 at 0xf8050000 (irq = 17) is a SA1100 UART
> Ramdisk driver initialized : 16 ramdisks of 16384K size
> RAMDISK: Compressed image found at block 0
> VFS: Mounted root (ext2 filesystem).
> init: memory vi
> *** CONSOLE_ERROR: console_print entry: vcd->screen.origin: c05227ec, (c008d200)
> *** CONSOLE_ERROR: console_print entry: vcd->screen.origin: c05227ec, (c008d200)
> *** CONSOLE_ERROR: console_print entry: vcd->screen.origin: c05227ec, (c008d200)
> *** CONSOLE_ERROR: console_print entry: vcd->screen.origin: c05227ec, (c008d200)
This can be caused by one of two things - something with big boots trampling
over kernel memory, or something causing a violation of the console code.
Either way, screen.origin contains an invalid address.
Interestingly, this message is not identical to my 2.0.35 message, so I don't
know what the values refer to, and whether they're wrong, and what they're
supposed to be.
_____
|_____| ------------------------------------------------- ---+---+-
| | Russell King [EMAIL PROTECTED] --- ---
| | | | http://www.arm.linux.org.uk/~rmk/armlinux.html / / |
| +-+-+ --- -+-
/ | THE developer of ARM Linux |+| /|\
/ | | | --- |
+-+-+ ------------------------------------------------- /\\\ |
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
