Re: [SLUG] seg fault on df

[Ramon Buckland <ramon@xxxxxxxxxxxxxxx>]

Thanks Greg, 

It turns out to be the firewire port..
dmesg | grep eth1
...
ip1394: eth1: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0)
...

New for kernel 2.6 :-)

thanks.

On Mon, 2004-05-10 at 08:18, Greg Cockburn wrote:
> You should start at eth0.
> 
> So I guess the kernel thinks there is 3 network cards in your machine.
> 
> lspci
> 
> ifconfig -a
> 
> and see if you can see all three.
> 
> Glad to here it went well.
> 
> Greg
> 
> 
> On Sun, 9 May 2004 11:09 pm, Ramon Buckland wrote:
> > Just letting people know, (and a question below)
> >
> > The upgrade to 2.6 went well and solved my problem.
> > At first I was completely unable to upgrade (seg faulting somewhere
> > in the install of the kernel package whilst on 2.5)
> >
> > So thankfully I had not removed my last good 2.4 kernel so reverted
> > to it (lilo worked thankfully) and then proceeded to upgrade.
> >
> > All seems good so far.
> > I had to add psmouse to my /etc/modules list on boot to support
> > my trackpad (at /dev/psaux), and
> > my wireless pcmcia NIC moved from eth1 to eth2 so I had to update
> > /etc/network/interfaces with a line for eth2.
> >
> > What's the reason for the netowork card move ?
> >
> > Thanks for the help
> >
> > ramon
> >
> > On Fri, 2004-05-07 at 11:36, oscarp@xxxxxxxxxxx wrote:
> > > Quoting Ramon Buckland <ramon@xxxxxxxxxxxxxxx>:
> > >
> > > Learn more why this is so by using commands 'ldd' and 'strace' like this:
> > >
> > > #ldd /bin/df
> > >
> > > #strace /bin/df
> > >
> > > > Hi,
> > > >
> > > > sometime in the past month, I performed an upgrade
> > > > to my unstable debian. (apt-get update/upgrade) and possibly (i can't
> > > > remember, a dist-upgrade.
> > > >
> > > > I'm now getting a seg fault on a few commands., but repeatable is
> > > > when attempting to run df.
> > > >
> > > > Can anyone suggest a way I can resolve the issue? My ultimate aim is to
> > > > fix without a reinstall the box. (but if needed, I guess I will).
> > > >
> > > > Probably the one thing that might be the issue is I am running
> > > > 2.5.72 kernel.
> > > >
> > > > Here's my seg fault (not that it will help much, but show my pain I
> > > > guess :-)
> > > >
> > > > sebago:~# df
> > > > Filesystem           1K-blocks      Used Available Use% Mounted on
> > > > <1>Unable to handle kernel NULL pointer dereference at virtual address
> > > > 00000018
> > > >  printing eip:
> > > >  00000018
> > > >  *pde = 00000000
> > > >  Oops: 0000 [#14]
> > > >  CPU:    0
> > > >  EIP:    0060:[<00000018>]    Not tainted
> > > >  EFLAGS: 00010246
> > > >  eax: 0000010c   ebx: 08051228   ecx: 00000054   edx: 0000007b
> > > >  esi: bffff420   edi: 40156510   ebp: c438a000   esp: c438bfc0
> > > >  ds: 007b   es: 007b   ss: 0068
> > > >  Process df (pid: 9407, threadinfo=c438a000 task=c326ace0)
> > > >  Stack: c010904f 08051228 00000054 bffff420 bffff420 40156510 bffff408
> > > > 0000010c
> > > >         0000007b 0000007b 0000010c 400f0334 00000073 00000246 bffff3b0
> > > > 0000007b
> > > >         Call Trace: [<c010904f>]
> > > >         Code:  Bad EIP value.
> > > >          Segmentation fault
> > > >
> > > >
> > > > --
> > > > SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
> > > > Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
> > >
> > > ----------------------------------------------------------------
> > > This message was sent using IMP, the Internet Messaging Program.