[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: kernel troubles
Re: kernel troubles
Mon, 31 Dec 2001 08:52:52 -0700
Marcus Brinkmann (Marcus.Brinkmann@ruhr-uni-bochum.de) said:
> On Sat, Dec 29, 2001 at 04:11:23PM -0700, mike burrell wrote:
> > Marcus Brinkmann (Marcus.Brinkmann@ruhr-uni-bochum.de) 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
> > > > 127.0.0.1"
> > > > 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
> > 127.0.0.1" 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 127.0.0.1" 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.
indeed the problem was sharing interrupts. both cards were using IRQ 11.
i've taken the Via Rhine card out and am just running the 3Com card, without
any problems (obviously -- i'm writing and sending this e-mail under the
i'm guessing by your response that IRQ sharing is a known issue?
anyway, still no closer on figuring out why the Via Rhine card doesn't work
on its own (and it doesn't even give a nice, pretty crash message; it just
freezes). i remember it didn't work very well under older versions of
Linux (i think i'd tried it in 2.2 and fought with it a lot), so it could
just be a driver issue. i'd really like to get that one working, though,
as that's the one i use under Linux (since it's 100Mbit, and the 3Com is
just 10Mbit), and i'm sure i'll grow quickly tired of swapping net cards
in and out every time i reboot :)
for now i'm going to play around in the Hurd for a while longer. my goal
for today is to get development tools installed so that i can play around
with the gnumach source (and maybe do some printk debugging).
btw i'm pretty impressed with the terminal emulation of the Hurd. colour
and everything, wow :)
/"\ m i k e b u r r e l l
\ / ASCII RIBBON CAMPAIGN email@example.com
X AGAINST HTML MAIL,
/ \ AND NEWS TOO, dammit