[Top][All Lists]

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

Re: kernel troubles

From: Marcus Brinkmann
Subject: Re: kernel troubles
Date: Sun, 30 Dec 2001 15:32:14 +0100
User-agent: Mutt/1.3.24i

On Sat, Dec 29, 2001 at 04:11:23PM -0700, mike burrell wrote:
> Marcus Brinkmann ( said:
> > On Fri, Dec 28, 2001 at 04:08:38PM -0700, mike burrell wrote:
> > > then i tried testing out the networking.  not so good.  a "ping"
> > > yielded a:
> > > 
> > > Kernel General protection trap, eip 0x16ccce
> > > kernel trap, type 13, code = 0
> > > Dump of i386_saved_state 09888ad04:
> > >  .
> > >  . <register dump>
> > >  .
> > > trapno 13: General protection, error 00000000
> > > panic: trap
> > 
> > Holla! seems like a bug in the kernel.  Maybe it is related to having two
> > ethernet cards.  If you can do the test, pull one out and see what happens.
> > 
> > Then you can use both cards again, and boto gnumach-dbg in the gnumahc-dbg
> > package.  Then report he fault eip address again, so we see where it
> > crashes.
> okay i'm afraid my results aren't very useful (at least to my eyes).
> with both cards in (and /servers/socket/2 set up to use the 3Com), "ping
>" gave me:
>       Kernel General protection trap, eip 0x17a3be
>       kernel: General protection (13), code = 0
>       Stopped at 0x17a3be:    testb   $0x40,0x283b68(,%eax,8)
> and after taking out the 3Com and setting it up to use the Via Rhine, it 
> didn't
> give me any message at all -- "ping" just locked up the machine :(

I assume you are using gnumach-dbg 20011013-1 (if not, repeat using that

zcat /gnu/boot/gnumach-dbg.gz > /tmp/gnumach-dbg
objdump --syms /tmp/gnumach-dbg |sort

gives me:

0017a18c l     F .text  000006f8 vortex_open
0017a884 l     F .text  000003e1 vortex_timer
0017ac68 l     F .text  0000025e vortex_tx_timeout
0017aec8 l     F .text  0000026a vortex_error

So your kernel crashes in vortex_open, which belongs to the 3c59x driver.
So it seems that the version of the 3com driver we use in gnumach has
problems with your configuration.  

     Enables the 3Com 590/900 series (592/595/597/900/905)
     "Vortex/Boomerang" netword card devices eth%d.

You can now do several things to find out more.  Like, give us details about
your 3com card.  Check that you aren ot sharing interrupts.  Maybe see if
some bugs for your card where fixed in a newer linux driver, and backport
the newer linux driver to gnumach.

Or you can try to debug the vortex_open function yourself, and see where in
this function it is crashing and why.  Just put some printk's strategically
into gnumach/linux/src/drivers/net/3c59x.c (vortex_open).  This will require
several attempts.

I should be able to find out the exact line number it crashed from the
address 0x17a3be, but:

ulysses:~# addr2line --function -e /tmp/g 0x17a3be

So something is broken in binutils or our gnumach-dbg build.


`Rhubarb is no Egyptian god.' Debian
Marcus Brinkmann              GNU

reply via email to

[Prev in Thread] Current Thread [Next in Thread]