console on ttyS0 broken with 2.6.9-bk6-pa1 ?
I just compiled/booted the latest CVS kernel (2.6.9-bk6-pa1) which seems to boot fine. Sadly using a serial console is broken. Any ideas ?
This is the bootlog in minicom:
palo ipl 0.99 root@P100 Sat Apr 13 22:21:21 CEST 2002
Boot image contains:
0/vmlinux32 4714377 bytes @ 0x8000
Information: No console specified on kernel command line. This is normal.
PALO will choose the console currently used by firmware (serial).
Command line for kernel: 'HOME=/ root=/dev/sda3 ip=bootp console=ttyS0 TERM=vt102 palo_kernel=0/vmlinux' Selected kernel: /vmlinux from partition 0
Warning: kernel name doesn't end with 32 or 64 -- Guessing... Choosing 32-bit kernelELF32 executable Entry 00100368 first 00100000 n 1
Segment 0 load 00100000 size 3780741 mediaptr 0x1000
Branching to kernel entry point 0x00100368. If this is the last
message you see, you may need to switch your console. This is
a common symptom -- search the FAQ and mailing list at parisc-linux.org
Linux version 2.6.9-bk6-pa1 (root@p100) (gcc version 3.3.4 (Debian 1:3.3.4-11)) #96 Sun Oct 24 15:44:48 CEST 2004 FP[0] enabled: Rev 1 Model 13
The 32-bit Kernel has started...
Determining PDC firmware type: Snake.
model 000060a0 00000481 00000000 00000000 773c7d2c 00000000 00000004 00000072 00000072
vers 0000000c
model 9000/715
Total Memory: 160 Mb
Built 1 zonelists
Kernel command line: HOME=/ root=/dev/sda3 ip=bootp console=ttyS0 TERM=vt102 palo_kernel=0/vmlinux
....<lot's of other messages skipped...>
Serial: 8250/16550 driver $Revision: 1.90 $ 13 ports, IRQ sharing enabled
ttyS0 at MMIO 0xf0105800 (irq = 90) is a 16550A
Linux version 2.6.9-bk6-pa1 (root@p100) (gcc version 3.3.4 (Debian 1:3.3.4-11)) #96 Sun Oct 24 15:44:48 CEST 2004 Linux version 2.6.9-bk6-pa1 (root@p100) (gcc version 3.3.4 (Debian 1:3.3.4-11)) #96 Sun Oct 24 15:44:48 CEST 2004 Linux version 2.6.9-bk6-pa1 (root@p100) (gcc version 3.3.4 (Debian 1:3.3.4-11)) #96 Sun Oct 24 15:44:48 CEST 2004 Linux version 2.6.9-bk6-pa1 (root@p100) (gcc version 3.3.4 (Debian 1:3.3.4-11)) #96 Sun Oct 24 15:44:48 CEST 2004 <...this last line continues forever...>
_______________________________________________
parisc-linux mailing list
[email protected]
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
Hello Helge,
Quoted 2 lines
I just compiled/booted the latest CVS kernel (2.6.9-bk6-pa1) which seem=
s
Quoted 3 lines
to boot fine.
Sadly using a serial console is broken. Any ideas ?
Sorry I could very help but I experiment a similar pb on my c110:
Quoted 8 lines
This is the bootlog in minicom:
palo ipl 0.99 root@P100 Sat Apr 13 22:21:21 CEST 2002
Boot image contains:
0/vmlinux32 4714377 bytes @ 0x8000Information: No console specified on kernel command line. This is norma=
l.
Quoted 2 lines
PALO will choose the console currently used by firmware (serial). Command line for kernel: 'HOME=3D/ root=3D/dev/sda3 ip=3Dbootp console=3D=
ttyS0
TERM=3Dvt102
Quoted 3 lines
palo_kernel=3D0/vmlinux'
Selected kernel: /vmlinux from partition 0
Warning: kernel name doesn't end with 32 or 64 -- Guessing... Choosing
32-bit
Quoted 8 lines
kernelELF32 executable
Entry 00100368 first 00100000 n 1
Segment 0 load 00100000 size 3780741 mediaptr0x1000Branching to kernel entry point0x00100368. If this is the last message you see, you may need to switch your console. This is a common symptom -- search the FAQ and mailing list at parisc-linux.org=
After this , on this c110 (and b180) model, there are not any more messag= es
display (since release 2.6.9-rc2-pa1?) on serial console (no way to test sti one :( ) before :0x00000009}
lp: driver loaded but no devices found
Generic RTC Driver v1.07
(ie just after sti switch should occur ?)
Quoted 2 lines
Serial: 8250/16550 driver $Revision: 1.90 $ 13 ports, IRQ sharing enabl=
ed
Quoted 1 line
ttyS0 at MMIO
0xf0105800(irq =3D 90) is a 16550A
The same but the message is weird for me:0x00000009}0x00000009}0x00000009}
etc
(Note that one of this line was already displayed before "lp: driver..." ?)
Anyway (may be was I not enough patient) the system never came up (I couldn't even launch a TOC to grab some piminfo: the time stamp of wh= at
I read was date May 23 ... when the hw system clock was well Oct 23 ...?)=
Also a simiar pb on the n4k, the message was:
'io scheduler noop registered'
'io scheduler noop registered'
etc
And the system didn't bring up too (I almost waited 10 mininutes before reset it)
OTC my b2k with 32bit kernel boot fine without any pb of any kind (all me= ssages
are well displayed :)
Cheers,
Joel
-------------------------------------------------------------------------=
--
Tiscali ADSL GO & Light, 2 mois gratuits, profitez-en...
http://reg.tiscali.be/adsl/welcome.asp?lg=3DFR