[613] in linux-net channel archive
Re: Kernel panics with 1.2.10
daemon@ATHENA.MIT.EDU (Daniel Hollis)
Wed Jul 5 10:41:31 1995
From: dhollis@hq.jcic.org (Daniel Hollis)
To: gpg109@rsphy1.anu.edu.au (Paul Gortmaker)
Date: Tue, 4 Jul 1995 23:46:40 -0700 (PDT)
Cc: linux-net@vger.rutgers.edu
In-Reply-To: <9507050624.AA13711@rsphy9.anu.edu.au> from "Paul Gortmaker" at Jul 5, 95 04:24:02 pm
> >I've been having tons of system crashes all of a sudden. The system
> >always seems to die at 17f238 which is _ei_interrupt. This is with Kernel
> >1.2.10.
> Note that the masking of the ENISR_RDC bit (0x40) is no longer necessary,
> and I removed it from 1.3.x kernels. I suggest you grab an 8390.c from
> a 1.3.5 kernel if you want to run a 1.2.11 kernel. (Not 1.3.6 as it is
> incompatible due to skb changes.) Looking at the above assembly and the
> printk messages seems to indicate that you are getting bogus interrupts on
> irq 15 (the garbage heap of PIC #2)
If this is the case, I guess we should see these fixes in 1.2.12, right? :)
> >eth0: WD80x3 at 0x280, 00 80 48 85 E1 CC assigning address 0xd0000 WD8003-old, IRQ 15, shared memory at 0xd0000-0xd1fff.
> >wd.c:v1.10 9/23/94 Donald Becker (becker@cesdis.gsfc.nasa.gov)
> Didn't this come up before? The probe report is showing that you have one
> of the old 8 bit EEPROMless full length 8k RAM cards. But if that was the
> case, you couldn't be using irq 15 on an 8 bit card! Not to mention the
> fact that all wd/SMC cards have 00 00 C0 as the vendor prefix. Is this
> some sort of wd-clone card? My list of vendor prefixes doesn't list any
> valid 00 80 48 NIC hardware address prefixes.
It's some no-name WD clone. It is a 16 bit card (at least, according to
the manual, the board itself, etc.) and it has jumpers for IRQ 15, IRQ
12, etc.. I'll try to get the exact model number and brand name when I go
into the office tomorrow. I have also tried to look up the MAC address in
the vendor list and haven't been able to find anything, either.
Note BTW, that when I stopped using the Rocketport altogether (e.g.
stopped loading the kernel module), the crashes completely stopped. So
there is apparently some really strange interaction going on here between
the network drivers and the Rocketport.
-Dan
----
------------------------------------------------------------------------------
Dan Hollis | Seiyuu Daisuki! |"Ranko-chan, ii oyome-san
MAGICK.NET System Administrator | Orikasa Ai | ni nareru wa yo" -
http://www.magick.net/ | Yokoyama Chisa | Saotome Nodoka
dhollis@magick.net | ("(^_^)") |
------------------------------------------------------------------------------
