[parisc-linux] Kernel crash when loggin in via ssh

[parisc-linux] Kernel crash when loggin in via ssh

[M. Grabert]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1268 bytes --]

Hi parisc-linux,

I tried to upgrade my C240 (from old 2.4.19-pa2) to linux-2.4.20-pa10 and
linux-2.4.20-pa13 (compiled with gcc-3.2.2-pre). Both new kernels boot
up fine, all daemons/programms seem to work, even network is up, but the
C240 (beast) instantly hangs after I try to ssh into the beast from my
Intel laptop (bucephalas).
Both systems (PA-RISC and Intel) are debian/sid, apt-get upgraded on Dec 8.
I tried the following on the laptop:

==
bucephalas:/home/xam/parisc# ssh xam@beast
xam@beast's password:
Warning: No xauth data; using fake authentication data for X11 forwarding.
==

The ssh authenification is obviously successful, but I won't get a shell prompt
since the C240 crashes immediately after the login.

It works when booting the old linux-2.4.19-pa2, so there must be a bug
introduced between 2.4.19-pa2 and 2.4.20-pa10.

Attached are the kernel stack/register dump and parts of the System.map
when running linux-2.4.20-pa13.
I didn't include the kernel config since it is quite large, but the only
thing that has changed is that I use SYM2 instead of SYM1 on 2.4.20-pa13.
The config of 2.4.20-pa10 (not working) and 2.4.19-pa7 (working) is the
same, and it hasn't changed for quite a while since before that and always
worked.

greetings max

[-- Attachment #2: Type: TEXT/PLAIN, Size: 1916 bytes --]

excerpt from System.map-2.4.20-pa13:
(kernel crashes after trying to do a ssh login from laptop to C240,
 after successful authentification)

10126da8 t set_user
10126e44 T sys_setreuid
10126fec T sys_setuid
101270f8 T sys_setresuid
101272a0 T sys_getresuid
10127340 T sys_setresgid
10127450 T sys_getresgid
101274f0 T sys_setfsuid
101275d8 T sys_setfsgid
1012765c T sys_times
10127698 T sys_setpgid
1012779c T sys_getpgid

1019793c t initialize_tty_struct
10197a74 T tty_default_put_char
10197aa4 T tty_register_devfs
10197aa8 T tty_unregister_devfs
10197aac T tty_register_driver
10197b94 T tty_unregister_driver
10197cfc T tty_paranoia_check
10197d7c t do_tty_write
10197f34 t check_unthrottle
10197f8c t reset_buffer_flags
10197fe4 T n_tty_flush_buffer
10198034 T n_tty_chars_in_buffer
10198078 t opost
10198234 t opost_block
10198424 t echo_char
101984bc t eraser
101988dc t n_tty_receive_room
10198908 t n_tty_write_wakeup
10198954 t n_tty_receive_buf
10198d38 T is_ignored
10198d84 t n_tty_set_termios
10199178 t n_tty_close
101991b4 t n_tty_open
10199254 t read_chan
101998d8 t write_chan
10199b44 t normal_poll
10199cdc t put_tty_queue
10199d24 t n_tty_receive_char
1019a3d8 t copy_from_read_buf
1019a4a0 T tty_wait_until_sent
1019a5b4 t unset_locked_termios
1019a6ac t change_termios
1019a8a4 t set_termios
1019aa48 t get_termio
1019ab60 t inq_canon
1019abcc T send_prio_char
1019ac5c T n_tty_ioctl
1019b0d0 T raw_open
1019b2bc T raw_release
1019b378 T raw_ioctl
1019b3dc T raw_ctl_ioctl
1019b664 T raw_read
1019b698 T raw_write
1019b6cc t rw_raw_dev
1019b9f0 t pty_close
1019bb30 t pty_unthrottle
1019bba8 t pty_write
1019bd54 t pty_write_room
1019bd94 t pty_chars_in_buffer
1019bdf8 t pty_get_device_number
1019be40 t pty_set_lock
1019beb4 t pty_bsd_ioctl
1019befc t pty_unix98_ioctl
1019bf48 t pty_flush_buffer
1019bfb8 t pty_open

[-- Attachment #3: Type: TEXT/PLAIN, Size: 1995 bytes --]

PING bucephalas.ucc.ie (143.239.201.200): 56 data bytes
64 bytes from 143.239.201.200: icmp_seq=0 ttl=64 time=0.6 ms
64 bytes from 143.239.201.200: icmp_seq=1 ttl=64 time=0.1 ms

--- bucephalas.ucc.ie ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 0.1/0.3/0.6 ms
beast:/etc/rcS.d# 
Stack Dump:
 2d072fc0:  0004070f 4c4c4c4c 4c4c4c4c 4c4c4c4c 
 2d072fb0:  4c4c4c4c 4c4c4c4c 4c4c4c4c 4c4c4c4c 
 2d072fa0:  4c4c4c4c 4c4c4c4c 4c4c4c4c 4c4c4c4c 
 2d072f90:  4c4c4c4c 4c4c4c4c 4c4c4c4c 4c4c4c4c 
 2d072f80:  4c4c4c4c 4c4c4c4c 4c4c4c4c 4c4c4c4c 
 2d072f70:  4c4c4c4c 4c4c4c4c 4c4c4c4c 4c4c4c4c 

Kernel addresses on the stack:
 [<1019bd4c>]  [<10197a98>]  [<1019813c>]  [<10198470>] 
 [<10199e40>]  [<101989ec>]  [<1019bd4c>]  [<10197a98>] 
 [<1019813c>]  [<10198470>]  [<10199e40>]  [<101989ec>] 
 [<1019bd4c>]  [<10197a98>]  [<1019813c>]  [<10198470>] 
 [<10199e40>]  [<101989ec>]  [<1019bd4c>]  [<10197a98>] 
 [<1019813c>]  [<10198470>]  [<10199e40>]  [<101989ec>] 
 [<1019bd4c>]  [<10197a98>]  [<1019813c>]  [<10198470>] 
 [<10199e40>]  [<101989ec>]  [<1019bd4c>]  [<10197a98>] 
 [<1019813c>]  [<10198470>]  [<10199e40>]  [<101989ec>] 
 [<1019bd4c>] 

Kernel Fault: Code=6 regs=2d072fc0 (Addr=4c4c4c4c)

     YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
PSW: 00000000000001000000011100001111 Not tainted
r00-03  00000000 00000000 4c4c4c4c 2fd99000
r04-07  2f1ee000 00000001 2d072f08 2fd99000
r08-11  00000001 00000000 00000000 0008b660
r12-15  2fd9996c 2d04c6d0 00069d9c 00069d9c
r16-19  00000004 00069d9c 00000004 0000007f
r20-23  ffffffff 00000001 00000000 00000001
r24-27  2f46b740 00000000 2f1ee000 1027e010
r28-31  00001000 00000031 2d072fc0 10197a98
sr0-3   00000000 00000075 00000000 00000075
sr4-7   00000000 00000000 00000000 00000000

IASQ: 00000000 00000000 IAOQ: 4c4c4c4c 4c4c4c50
 IIR: 43ffff80    ISR: 08030258  IOR: 34030100
 CPU:        0   CR30: 2d04c000 CR31: 10320000
 ORIG_R28: 6bd33fc1

Re: [parisc-linux] Kernel crash when loggin in via ssh

[Carlos O'Donell]

> It works when booting the old linux-2.4.19-pa2, so there must be a bug
> introduced between 2.4.19-pa2 and 2.4.20-pa10.

What compiler/toolchain did you use to compile 2.4.19-pa2?

c.

Re: [parisc-linux] Kernel crash when loggin in via ssh

[M. Grabert]

On Tue, 10 Dec 2002, Carlos O'Donell wrote:

> > It works when booting the old linux-2.4.19-pa2, so there must be a bug
> > introduced between 2.4.19-pa2 and 2.4.20-pa10.
>
> What compiler/toolchain did you use to compile 2.4.19-pa2?

Honestly, I don't know 100%. It wasn't gcc-3.2.2-pre for sure, but i
*THINK* it was gcc-3.0.4 (I have to do a dmesg next time)!

Re: [parisc-linux] Kernel crash when loggin in via ssh

[M. Grabert]

On Tue, 10 Dec 2002, Carlos O'Donell wrote:

> > It works when booting the old linux-2.4.19-pa2, so there must be a bug
> > introduced between 2.4.19-pa2 and 2.4.20-pa10.
>
> What compiler/toolchain did you use to compile 2.4.19-pa2?

Reading my previous post about the change in the Voodoo3 issue (Nov 26),
I realized that linux-2.4.20-rc1-pa7 obviously also worked.
This kernel was definitely compiled with gcc-3.0.4 (the one that
was in sid as of Nov 26).

Yes, it might be a gcc issue ... haven't thought of that ...
I'll try to recompile the latest kernel with a gcc-3.0.4 - tomorrow!

greetings max

Re: [parisc-linux] Kernel crash when loggin in via ssh

[Carlos O'Donell]

> Reading my previous post about the change in the Voodoo3 issue (Nov 26),
> I realized that linux-2.4.20-rc1-pa7 obviously also worked.
> This kernel was definitely compiled with gcc-3.0.4 (the one that
> was in sid as of Nov 26).
> 
> Yes, it might be a gcc issue ... haven't thought of that ...
> I'll try to recompile the latest kernel with a gcc-3.0.4 - tomorrow!

So the urban legend goes that gcc-3.2 compiled kernels may infact
produce mildly incorrect results in the networking code.

I have yet to verify this, and JDA seems to indicate that he has working
kernels with gcc-3.2. While I've only recently tested gcc-3.0.x and
gcc-3.1.x based compiles.

I don't like urban legends >:} *Added item to Chrismas todo list*

c.

[parisc-linux] another kernel compilation error

[Tim Kemna]

Hi,

I'm trying to compile a kernel, version 2.4.20-pa13. But I get the following
error:

ld -T /usr/src/linux-2.4.20-pa13/arch/parisc/vmlinux.lds
arch/parisc/kernel/hea
d.o  init/main.o init/version.o init/do_mounts.o \
--start-group \
arch/parisc/kernel/pdc_cons.o arch/parisc/kernel/process.o
arch/parisc/lib/lib.a
 arch/parisc/mm/mm.o arch/parisc/kernel/kernel.o arch/parisc/hpux/hpux.o
kernel/
kernel.o mm/mm.o fs/fs.o ipc/ipc.o arch/parisc/kernel/init_task.o \
 drivers/char/char.o drivers/block/block.o drivers/misc/misc.o
drivers/net/net.o
 drivers/media/media.o drivers/scsi/scsidrv.o drivers/cdrom/driver.o
drivers/vid
eo/video.o drivers/gsc/gscbus.o arch/parisc/math-emu/math.o \
net/network.o \
`gcc -print-libgcc-file-name`
/usr/src/linux-2.4.20-pa13/arch/parisc/lib/lib.a /
usr/src/linux-2.4.20-pa13/lib/lib.a  \
        --end-group \
        -o vmlinux
ld: arch/parisc/kernel/kernel.o(.text.show_trace+0x58): fixing
R_PARISC_DPREL21L
ld: arch/parisc/kernel/kernel.o(.text.timer_interrupt+0x88): fixing
R_PARISC_DPR
EL21L
ld: arch/parisc/kernel/kernel.o(.text.timer_interrupt+0x94): fixing
R_PARISC_DPR
EL21L
drivers/char/char.o: In function `hp_diva_check':
drivers/char/char.o(.text.hp_diva_check+0x60): undefined reference to
`rs_interr
upt'
make: *** [vmlinux] Error 1

What am I doing wrong?

Greetings,
Tim

Re: [parisc-linux] another kernel compilation error

[Paul Bame]

> drivers/char/char.o: In function `hp_diva_check':
> drivers/char/char.o(.text.hp_diva_check+0x60): undefined reference to
> `rs_interrupt'
> make: *** [vmlinux] Error 1
> 
> What am I doing wrong?

Probably nothing but I did :-)  My Diva changes currently require
CONFIG_SERIAL_SHARE_IRQ to be set -- need to fix that.

        -P

Re: [parisc-linux] another kernel compilation error

[Tim Kemna]

> > drivers/char/char.o: In function `hp_diva_check':
> > drivers/char/char.o(.text.hp_diva_check+0x60): undefined reference to
> > `rs_interrupt'
> > make: *** [vmlinux] Error 1
> > 
> > What am I doing wrong?
> 
> Probably nothing but I did :-)  My Diva changes currently require
> CONFIG_SERIAL_SHARE_IRQ to be set -- need to fix that.

I can't find that option in my .config

Re: [parisc-linux] another kernel compilation error

[Thibaut VARENE]

Le mercredi, 11 d=E9c 2002, =E0 14:51 Europe/Paris, Tim Kemna a =E9crit =
:
>
> drivers/char/char.o: In function `hp_diva_check':
> drivers/char/char.o(.text.hp_diva_check+0x60): undefined reference to
> `rs_interr
> upt'
> make: *** [vmlinux] Error 1
>
Weird I'm also having an error on char.o:

         -o vmlinux
drivers/char/char.o: In function `.L1757':
drivers/char/char.o(.text.vt_ioctl+0x51c): undefined reference to=20
`key_maps'
drivers/char/char.o: In function `handle_scancode':
drivers/char/char.o(.text.handle_scancode+0x25c): undefined reference=20
to `key_maps'
drivers/char/char.o: In function `handle_diacr':
drivers/char/char.o(.text.handle_diacr+0x1c): undefined reference to=20
`accent_table_size'
drivers/char/char.o: In function `do_fn':
drivers/char/char.o(.text.do_fn+0x8): undefined reference to=20
`func_table'
drivers/char/char.o: In function `compute_shiftstate':
drivers/char/char.o(.text.compute_shiftstate+0x90): undefined reference=20=

to `key_maps'
drivers/char/char.o: In function `do_slock':
drivers/char/char.o(.text.do_slock+0x74): undefined reference to=20
`key_maps'
make: *** [vmlinux] Error 1

same kernel; 64bit UP for a B2600 in graphic mode (SuckyIO/STIcon...)

I'm gonna investigate soon...
Mail me for .config...=

Re: [parisc-linux] another kernel compilation error

[Grant Grundler]

On Wed, Dec 11, 2002 at 02:51:44PM +0100, Tim Kemna wrote:
> I'm trying to compile a kernel, version 2.4.20-pa13. But I get the following
> error:
...
> drivers/char/char.o: In function `hp_diva_check':
> drivers/char/char.o(.text.hp_diva_check+0x60): undefined reference to
> `rs_interrupt'

Maybe you don't have CONFIG_PCI=y/CONFIG_SERIAL_SHARE_IRQ=y?

grant

[parisc-linux] Re: Solved: Kernel crash when loggin in via ssh

[M. Grabert]

On Wed, 11 Dec 2002, Carlos O'Donell wrote:

> Subject: Re: [parisc-linux] Kernel crash when loggin in via ssh
>
> > Reading my previous post about the change in the Voodoo3 issue (Nov 26),
> > I realized that linux-2.4.20-rc1-pa7 obviously also worked.
> > This kernel was definitely compiled with gcc-3.0.4 (the one that
> > was in sid as of Nov 26).
> >
> > Yes, it might be a gcc issue ... haven't thought of that ...
> > I'll try to recompile the latest kernel with a gcc-3.0.4 - tomorrow!

It IS a gcc issue.

gcc-3.0_3.0.4-13 produces a working kernel, gcc-3.2-3.2.2-0pre0 produces
a miscompiled kernel (faulty networking, causes kernel crash).
I made NO updates whatsoever; same kernel configuration, just using gcc-3.0
insted of gcc-3.2. I just make a make clean; make dep; make vmlinux ...

Since now all my kernels compiled with gcc-3.0 were working, just when I
upgraded to gcc-3.2 the problems occured.

> So the urban legend goes that gcc-3.2 compiled kernels may infact
> produce mildly incorrect results in the networking code.

I think it is no urban legend anymore ... :-/
I've also see quite alot reports on p-l about miscompiled kernels with
anything other than gcc-3.0.4, actually several months ago; so I thought
these issues have been solved by now ...

> I have yet to verify this, and JDA seems to indicate that he has working
> kernels with gcc-3.2. While I've only recently tested gcc-3.0.x and
> gcc-3.1.x based compiles.
>
> I don't like urban legends >:} *Added item to Chrismas todo list*

Merry christmas then :-}

greetings max

Re: [parisc-linux] Re: Solved: Kernel crash when loggin in via ssh

[John David Anglin]

> > > Yes, it might be a gcc issue ... haven't thought of that ...
> > > I'll try to recompile the latest kernel with a gcc-3.0.4 - tomorrow!
> 
> It IS a gcc issue.

That is not sufficient proof.  Just because code "works" with one compiler
version, doesn't mean that there isn't a problem with the code.  Someone
actually has to produce a sample of miscompiled code.  The debian 3.0.4
is not a supported version of gcc.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6605)

Re: [parisc-linux] Re: Solved: Kernel crash when loggin in via ssh

[M. Grabert]

On Wed, 11 Dec 2002, John David Anglin wrote:

> > It IS a gcc issue.
>
> That is not sufficient proof.  Just because code "works" with one compiler
> version, doesn't mean that there isn't a problem with the code.  Someone
> actually has to produce a sample of miscompiled code.  The debian 3.0.4
> is not a supported version of gcc.

okay, fair enough. But for now I stick to gcc-3.0.4 ...

BTW, did anybody try to compile kernels with CVS gcc-3.3 ?
Otherwise I'll waste my time this weekend building a native compiler and
try to recompile the same kernel again with the CVS gcc main branch (3.3?)

greetings max

Re: [parisc-linux] Re: Solved: Kernel crash when loggin in via ssh

[Randolph Chung]

> gcc-3.0_3.0.4-13 produces a working kernel, gcc-3.2-3.2.2-0pre0 produces
> a miscompiled kernel (faulty networking, causes kernel crash).

Just to reiterate Dave's point, this is not necessarily a compiler
problem. 

> I think it is no urban legend anymore ... :-/
> I've also see quite alot reports on p-l about miscompiled kernels with
> anything other than gcc-3.0.4, actually several months ago; so I thought
> these issues have been solved by now ...

you will also see several attempts from me to get more info about these
problems, since i have yet to reproduce this. No one has stepped forward
to provide the info to track this down...

please, follow the info at
http://www.parisc-linux.org/faq/kernelbug-howto.html to report where is
the crash, what is your config, etc.... just saying "it doesn't work"
will not help us fix it.

randolph
-- 
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/

Re: [parisc-linux] Re: Solved: Kernel crash when loggin in via ssh

[Thibaut VARENE]

Le jeudi, 12 d=E9c 2002, =E0 01:05 Europe/Paris, Randolph Chung a =E9crit =
:

>> gcc-3.0_3.0.4-13 produces a working kernel, gcc-3.2-3.2.2-0pre0=20
>> produces
>> a miscompiled kernel (faulty networking, causes kernel crash).
>
> Just to reiterate Dave's point, this is not necessarily a compiler
> problem.
I'm pretty interested to help finding out whether it is or not a=20
compiler problem.

I had the exact same problem that what was mentioned here, a couple of=20=

months ago, with both native and cross compiler (gcc-3.2).
Any attempt to login on the box via network led to a kernel crash.

I'll try to reproduce it to track down where the kernel crashed, since=20=

I don't remember it off hand.

Anyway, I'd be interested in learning what you guys may suspect as=20
other possible cause for this _weird_ behaviour...

HTH,


Thibaut VARENE
The PA/Linux ESIEE Team
http://pateam.esiee.fr/=

Re: [parisc-linux] Re: Solved: Kernel crash when loggin in via ssh

[Randolph Chung]

> It IS a gcc issue.
> 
> gcc-3.0_3.0.4-13 produces a working kernel, gcc-3.2-3.2.2-0pre0 produces
> a miscompiled kernel (faulty networking, causes kernel crash).
> I made NO updates whatsoever; same kernel configuration, just using gcc-3.0
> insted of gcc-3.2. I just make a make clean; make dep; make vmlinux ...

btw, i just built this: 

$ ssh -p 1022 -2 tausq@gsyprf10.external.hp.com
tausq@a500:~$ dmesg|grep gcc
Linux version 2.4.20-pa13 (tausq@a500) (gcc version 3.2.2 20021202 (Debian prerelease)) #12 SMP Wed Dec 11 23:02:01 PST 2002

still need to try 32-bit...
randolph

Re: [parisc-linux] Re: Solved: Kernel crash when loggin in via ssh

[John David Anglin]

> $ ssh -p 1022 -2 tausq@gsyprf10.external.hp.com
> tausq@a500:~$ dmesg|grep gcc
> Linux version 2.4.20-pa13 (tausq@a500) (gcc version 3.2.2 20021202 (Debian prerelease)) #12 SMP Wed Dec 11 23:02:01 PST 2002

I plan to change BIGGEST_ALIGNMENT back to 64 bits on the 32 branch today
assuming that testing is successful.  The main branch was changed yesterday.
This affects the alignment of long doubles under hpux and possibly the
alignment of __atomic_lock_t types parisc-linux linux.

I have been testing revised glibc locking code.  It only requires integer
alignment for __atomic_lock_t types.  I am convinced this is the
correct solution.  The __attribute__ ((aligned(16))) doesn't always
do what you want.  Specifically, it doesn't work for stack locals, or
malloc'd data.  

There is still one gcc pthread test failure (pthread6) under investigation.