Re: PCMCIA network card with woody install
On Sun, 14 Jul 2002 16:09:36 -0400
Seneca <seneca-cunningham@rogers.com> wrote:
> > > > > >
> > > > > >
> > > > <snip>
> > > > > > > > > pcmcia-cs/FAQ.Debian.gz). 2.2.20 (defualt woody
> > > > > > > > > kernel)
> > > > > >
> > > > > > > > Ok, so here goes, managed to get it to boot w/o pcmcia
> > > > > > > > enabled, if I'modprobe i82365' I get a kernel panic,
> > > > > > > > and have to reboot, if I'insmod i82365' I get the
> > > > > > > > following:
> > > > > > > >
> > > > > > > > max:/lib/modules/2.2.20/pcmcia# insmod i82365
> > > > > > > > Using /lib/modules/2.2.20/pcmcia/i82365.o
> > > > > > > > /lib/modules/2.2.20/pcmcia/i82365.o: unresolved symbol
> > > > > > > > pci_set_power_state...so on and so forth for about ten
> > > > > > > > lines of unresolved symbols
> > > > > > > >
> > > > <snip>
> > > > > > >
> > > > > > > > vendor. Ok, so I assume that there's a module not yet
> > > > > > > > loaded, and do an 'insmod pcmcia_core' and another
> > > > > > > > kernel panic.......
> > > > > > >
> > > > > > > Your assumption about the unresolved symbols is correct,
> > > > > > > i82365 requires pcmcia_core.
> > > > > > >
> > > > <snip>
> > > > > > > I have put the 2.2.20 kernel that is in woody on this
> > > > > > > system(a laptop that uses i82365 for the bridge). However,
> > > > > > > I have have not seen it panic (even after multiple boots).
> > > > > > > So, what does it say when the kernel panics (it probably
> > > > > > > says something more than just"kernel panic")?
> > > > > > >
> > > > > > Ok, a couple screens worth of what I would assume to be
> > > > > > debuggin symbols, and these are the last 4 lines of the
> > > > > > kernel panic(after setting /etc/default/pcmcia to
> > > > > > pcmcia="yes" and rebooting).
> > > > > >
> > > > > > Code: 8b 41 04 85 c9 74 22 8b 5a 18 8b 02 89 01 8b 0a 85 c9
> > > > > > 74 08 Aiee, killing interrupt handler
> > > > > > Kernel Panic: Attempted to kill the idel task!
> > > > > > In interrupt handler - not syncing
> > > > > >
> > > > > >
> > > > > > and that's it, right after INIT starts the pcmcia services
> > > > > > (I think, it flashes into the debug for the kernel awful
> > > > > > quick)
> > > > >
> > > > > Those messages show a definite problem. The last time I saw a
> > > > > line starting with "Code: ", my kernel Oopsed.
> > > > >
> > > > > What does it say before the registers && the stack? (you might
> > > > > need to set up a serial console, but scroll lock should work
> > > > > after init starts if you don't mind using pen && paper) What
> > > > > do your logs say (I'm wondering about what they said for the
> > > > > successful boot with pcmcia)?
> > > > >
ok, here's what I managed to grab.....
(actually a fresh install using the bf2.4 images, same result as the 2.2
kernel actually....) max:root@~# modprobe i82365
EFLAGS: 00010293
eax: 00000001 ebx: 00000003 ecx: 00000003 edx: 00000000
esi: 00000001 edi: 00000003 ebp: c086dd00 esp: c086dce8
ds: 0018 es: 0018 ss: 0018
Process modprobe (pid: 133, stackpage=c086d000)
Stack: c0c3a3a0 c01154e6 c032eca0 c0399ab0 ffffffff 000015f0 c086dd4c
c0107f6c 00000003 c183aa24 c086dd4c 00000060 c0390960 00000003
c086dd44 c01080d2 00000003 c086dd4c c0c3a3a0 c0390960 00000246
c0c3a3a0 c0c3a3a0 00000003 Call Trace: [<c01554e6>] [<c183dbac>]
[<c0108199>] [<c183ac85>] [<c010a0a8>] [<c0108457>] [<c183aa24>]
[<c183dbac>] [<c0108199>] [<c183ac85>] [<c183aa24>]
[<c183dbac>] [<c183aa24>] [<c0115850>] [<c0115795>] [<c183e1e0>]
[<c183adab>]
[<c0115850>] [<c183e1e0>] [<c183e288>] [<c183b438>] [<c183e1e0>]
[<c183e288>]
[<c18390c8>] [<c183e1e0>] [<c193b995>] [<c183dc44>] [<c183e1e0>]
[<c183bad2>]
[<c183e218>] [<c0115850>] [<c0115795>] [<c183d3cf>] [<c183d3be>]
[<c1834ee0>]
[<c011635d>] [<c1839060>] [<c0106d7b>]
Code: 0f b7 42 02 f6 c4 40 74 0c 8b 42 44 c7 00 ff ff ff ff eb 0c
<0>:Kernel Panic: Aiee, killing interrupt handler!
In interrupt handler - not syncing
this whole backtrace, was after 'modprobe pcmcia_core' was loaded (which
returned no errors). I have yet to make a serial console work, so
that's copied by hand, please ignore, correct, or flame mercilessly
about any spelling or grammatical errors, as it's early and I haven't
had coffee yet.
...preparing to chuck toughbook out the proverbial window....
--Shawn
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: