[NBLUG/talk] ADMTEK Driver, Part II: I'm an OS guinea pig

Dave Sisley dsisley at arczip.com
Thu May 27 06:37:50 PDT 2004


Hey:

Well, I went and installed the ADMTEK driver and I'm afraid that it's
botched my computer up pretty badly.  Of course, I may have helped it
out...

Now when I boot, I get a kernel panic! (I don't do so well either.)
What's weird is that since installing the module, the machine has
booted 'correctly' only 2x out of twenty attempts.  I don't know why
it would boot some times and not others.  I'm writing this on the
compromised machine right now.  I think maybe I will just leave it on
forever.

Below, you will see the output to screen during a bad boot.  Keep in
mind that I had to write this down on paper and then type it into
another machine in order to email it to the list.  That is why you
will see some 7 and 9 digit hex numbers.

Basically my questions for the group are:

- How do I fix this?  I'm thinking that this is pretty fundamental - I
  need to get the module out of there.  I will google this a bit when
  I get a chance later this morning, but if someone wants to toss me a
  fish (as opposed to *teaching* me how to fish...), I won't complain.

- Doesn't this look like it's the module that is making this happen?
  After installing it, I was unable to create a link to my laptop, so
  I was tweaking the network settings.  I just want to make sure that
  this isn't something I caused (other than loading the adm8211
  module).

If it *is* the module, I just want confirmation before I report to the
maintainer of the driver.  

Thanks for any help you can offer! 

-dave.

OUTPUT FROM BOOT:
----------------

<snip...>
Setting Network parameters	[  OK  ]
Bringing up loopback interface	[  OK  ]
Bringing up interface DSL	[  OK  ]
Bringing up interface eth0	[  OK  ]
Bringing up interface eth2: adm8211 device eth2 does not seem to be present, delaying initialization
				[FAILED]
Bringing up interface wireless: Unable to handle kernel NULL pointer dereference at virtual address 0000006c
*pde = 00000000
Oops: 00002 [#1]
CPU: 0
EIP: 0060: [<12ac3769>] Not tainted
EFLAGS: 00010216 (2.6.5-1.358)
EIP is at ieee80211_send_auth+0x105/0x33d [adm8211]
eax: 0c4c50c8  ebx: 0dec3210  ecx: 00000000  edx: 00000006
esi: 0c4c5196  edi: 00000000  ebp: 0c3d6080  esp: 02344f9c
ds: 007b  es: 007b  ss: 0068
Process swapper: (pid=0, threadinfo=0234400 task=022c5aa0
Stack: 00000000 00000000 0c4c50c8 0c450c8 12ac1abe 0c4c5190 02344fd0 12ac3add
       bd300000 12ac50ce 0c4c50f0 02344fd0 0211de03 10c23e00 0237fae4 00000000
       00000001 02369428 0000000a 02316000 0211af6d 02317f94 00000046 00000000
Call Trace:
  [<12ac1abe>] adm8211_set_ssid+0x0/0x78 [adm8211]
  [<12ac1add>] iee80211_authinticate+0x13c/0x154 [adm8211]
  [<12ac50cd>] iee80211_timer+0x0/0xca [adm8211]
  [<0211de03>] run_time_softirq+0x10b/0x12a
  [<0211afr6d>] __do_softirq+0x35/0x73
  [<021078f5>] do_softirq+0x46/0x4d
======================
  [<0210737b7>] do_IRQ+0x15d/0x169
  [<0210403b>] default_idle+0x23/0x26
  [<0210408c>] cpu_idle+0x1f/0x34
  [<02318612>] start_kernel+0x174/0x176

Code:ff 47 6c 0f b7 47 74 83 7c 24 04 0d 75 17 66 89 43 18 0f b7
<0> Kernel panic: Fatal exception in interrupt
In interrupt handler - not syncing

[...and that's it.  The computer just hangs here and I have to shut it
off.]


-- 
Dave Sisley
dsisley at arczip.com
roth-sisley.net




More information about the talk mailing list