Kernel panic with >=3.1.30 & >=2.4.18

[Martin Weinberg]

On Tue, 21 May 2002 10:14:37 +1000
David Gibson <david at gibson.dropbear.id.au> wrote:

> On Mon, May 20, 2002 at 07:54:42PM -0400, Martin Weinberg wrote:
> > Folks,
> > 
> > Jean Tourrilhes suggested I post this query/problem for David Gibson on
> > this list.
> > 
> > 
> > I have:
> > 
> > an PII 450Mhz on a AsusP2B board runningsystem library 2.2.5 (Debian
> > 3.0/Woody), kernel 2.4.16 and pcmcia-cs 3.1.30, with a Orinoco Silver PC
> > card in the Orinoco branded ISA adapter card.
> > 
> > Everything works fine with this configuration.
> > 
> > After upgrade to kernel 2.4.18, I experienced a kernel panic when the
> > pcmcia drivers were loaded (no problem without loading the drivers). I
> > upgraded to pcmcia-cs 3.1.33 with no difference. I also tried 2.4.19-pre8
> > with the same behavior.  I could not get the native kernel drivers to
> > detect the ISA-PCMCIA bridge, so all of this is with the standalone drivers.
> 
> Do you mean when you load the pcmcia base modules, or when you insert
> the card (loading the orinoco modules)?

The card is always plugged into the ISA bridge card.  I run cardmgr
to initialize the network.

Based on the ksym log file in /var/log/ksysoops, it seems to crash on
loading the orinoco driver; I see symbols for pcmcia_core, i82365, ds 
and then that's it.  I haven't tried insmodding one by one.

> > When it does work (old configuration), I see:
> > ds: no socket drivers loaded!
> > Intel ISA/PCI/CardBus PCIC probe:
> > Vadem VG-469 rev 00 ISA-to-PCMCIA at port 0x3e2 ofs 0x00
> > host opts [0]: none
> > host opts [1]: none
> > ISA irqs (scanned) = 4,14,15 polling interval = 1000 ms
> > cs: memory probe 0x0d0000-0x0dffff: excluding 0xd0000-0xd3fff
> > cs: memory probe 0x0c0000-0x0cffff: excluding 0xc0000-0xcffff
> > hermes.c: 3 Oct 2001 David Gibson <hermes at gibson.dropbear.id.au>
> > orinoco.c 0.08 (David Gibson <hermes at gibson.dropbear.id.au> and others)
> > orinoco_cs.c 0.08 (David Gibson <hermes at gibson.dropbear.id.au> and others)
> > cs: IO port probe 0x0100-0x04ff: excluding 0x1f0-0x1f7 0x290-0x297 0x388-0x38f 0x3c0-0x3e7 0x3f0-0x3ff 0x4d0-0x4d7
> > cs: IO port probe 0x01f8-0x028f: clean.
> > cs: IO port probe 0x0298-0x0387: clean.
> > cs: IO port probe 0x0390-0x03bf: clean.
> > cs: IO port probe 0x03e8-0x03ef: clean.
> > cs: IO port probe 0x0400-0x04cf: clean.
> > cs: IO port probe 0x04d8-0x04ff: clean.
> > cs: IO port probe 0x0800-0x08ff: clean.
> > cs: IO port probe 0x0a00-0x0aff: clean.
> > cs: IO port probe 0x0c00-0x0cff: clean.
> > eth1: Station identity 001f:0001:0004:0020
> > eth1: Looks like a Lucent/Agere firmware version 4.32
> > eth1: Ad-hoc demo mode supported.
> > eth1: WEP supported, "128"-bit key.
> > eth1: MAC address 00:60:1D:F0:37:05
> > eth1: Station name "HERMES I"
> > eth1: ready
> > eth1: index 0x01: Vcc 5.0, irq 14, io 0x0100-0x013f
> > 
> > Any thoughts?  What has changed between 2.4.18 and 2.4.16 that would
> > affect the standalone drivers?
> 
> -- 
> David Gibson			| For every complex problem there is a
> david at gibson.dropbear.id.au	| solution which is simple, neat and
> 				| wrong.  -- H.L. Mencken
> http://www.ozlabs.org/people/dgibson


-- 

===========================================================================

Martin Weinberg                      Phone: (413) 545-3821
Dept. of Physics and Astronomy       FAX:   (413) 545-2117/0648
530 Graduate Research Tower
University of Massachusetts
Amherst, MA  01003-4525