[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#538212: please provide a linux-image-r5k-ip22

On Thu, Jul 23, 2009 at 22:44 -0600, dann frazier wrote:
> reassign 538212 linux-2.6
> thanks
> On Fri, Jul 24, 2009 at 05:55:01AM +0200, Siggy Brentrup wrote:
> > Package: linux-latest-2.6
> > Severity: wishlist
> > 
> > I'm owning an Indy R5000 with IP22 ROM.
> > 
> > last dist-upgrade left me with an unconfigured openssh-server because
> > ssh-keygen & friends segfault during initialization.
> > 
> > I  seem  to remember from before 2004 that I experienced similar
> > problems which were remedied by installing a r5k-ip22 kernel.
> > 
> > Since I can't find  any documentation on that fact, it's just from the
> > top of my head.

> What evidence do you have that this is a kernel issue?

It's from my previous experience from 2001 I guess; I know for sure
replacing r4k-ip22 with r5k-ip22 cured the problem previously, just
can't find any reference, I guess it was a tip received on irc.

> Was there an oops (see dmesg output)?

Nothing in /var/log/dmesg*

> Can you get a backtrace w/ gdb? Does it go away if you back to the
> previous kernel?

No, first I experienced the problem during a dist-upgrade w/
2.6.26-2-r4k-ip22, still logged in via ssh sitting downstairs on my
teras; when I came back to the Indy's console for booting the new
kernel I noticed a full screen titled 'you have found a kernel bug
#7'.  Hoping this will disappear with the new kernel and
openssh-server being configured I rebooted to the current kernel,
sadly only with partial success:

  - no more kernel errors on screen

  - openssh-server still fails to configure (one of ssh-keygen's
    friends segfaulting.)

I'm attaching the recording from "2>&1 gdb ssh | tee gdb_ssh"

You almost convinced me the problem is not kernel related and
searching the archives of debian mips yielded a message from
Martin Michlmayr <tbm@cyrius.com>
stating that r4k-ip22 are running on r5k-ip22 machines too.

You may close the bug for now, I'll investigate further and reopen and
reassign it: living w/o a working sshd on that machine isn't really an

Thanks for caring
               or:                bsb-at-psycho-dot-i21k-dot-de
O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "mips-linux-gnu"...
(no debugging symbols found)
(gdb) run nfs.winnegan.fake
Starting program: /usr/bin/ssh nfs.winnegan.fake
(no debugging symbols found)

Program received signal SIGSEGV, Segmentation fault.
0x2aab566c in ?? () from /lib/ld.so.1
(gdb) where
#0  0x2aab566c in ?? () from /lib/ld.so.1
warning: GDB can't find the start of the function at 0x2aab566c.

    GDB is unable to find the start of the function at 0x2aab566c
and thus can't determine the size of that function's stack frame.
This means that GDB may be unable to access that stack frame, or
the frames below it.
    This problem is most likely caused by an invalid program counter or
stack pointer.
    However, if you think GDB should simply search farther back
from 0x2aab566c for code which looks like the beginning of a
function, you can increase the range of the search using the `set
heuristic-fence-post' command.
#1  0x2aab566c in ?? () from /lib/ld.so.1
warning: GDB can't find the start of the function at 0x2aab566b.
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) c

Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.
(gdb) q

Attachment: signature.asc
Description: Digital signature

Reply to: