Comment 5 for bug 32152

Hello, I am also having a problem with my Atheros card, which is a D-Link DWL-AG660 32-bit Cardbus PCMCIA card. I am using version 5.10 Breezy Badger. I am currently reinstalling it for about the 12 time or so due to this problem. My error messages are very different from those already posted however. I am "installing the base system" at the moment on my Ubuntu Laptop, but I'll try to do this brom memory. dmesg mentions something like:
[blah-blah] IRQ 11.
Nobody cared.
Disabling IRQ 11 Try booting with the "IRQPoll" kernel parameter.
[This message set repeats several times].

I never seem to get this message on a fresh install. This happens after I go installing extra packages using aptitude. The messages at first don't happen until an uptime of about 20-30 minutes or so the first time it occurs, then progressively sooner. Eventually, it occurs during bootup immediately after hotplug starts in initlevel 'S'.

In every case, I have run 'dpkg-reconfigure hotplug' and set hotplug to controll all "Auto" ifaces. In every case, I have edited '/etc/network/interfaces' and changed it to:

---cut---
auto lo eth0 ath0

iface lo inet loopback

iface eth0 inet dhcp

iface ath0 inet dhcp
---cut---

My laptop doesn't have any built-in network interfaces, not even IrDA.

I beleive it may be related to a package install. If anyone knows where aptitude's activity log is located, please let me know so I can back it up with each reinstall. I do not find it in /var/log. I often use package sources "backports" and "universe", so there might be a renegade package there.

After this problem occurs, the "link" LED on my PC-Card does flash, as it does after it has been inserted, but has not yet been brought "up".. After this problem occurs 'dhclient' seems to time out. 'cardctl ident' reports no card is inserted in either slot. 'cardctl eject 0' causes LED to stay off. Attempts to bring up ath0 after this problem is triggered reports 'SIG<something>IO: device not present [or 'no such device' or something similar].

Good luck hunting this one down, and let me know what else I can do to help. (ie post syslogs/dmesg contents, etc.)