Bug#673496: It's dead, Jim.

[Paul Zimmerman <aiwanar@yahoo.com>]

Well, I was very reluctant to go to the trouble of putting it back, but
when I did the machine recognizes it again. This is getting very,
very weird. There was no sign of it the last time it was installed. Maybe
this is related to the other weird hardware effects of the backported
kernel? I also found that after running 3.2 even in "recovery" mode
I could not load the standard stable kernel without a cold restart. It
hung when trying to load X, just like  when the backported kernel itself
tried to load X. The machine had to be physically turned off and 

restarted. It really looks like something is getting scrambled at a very
deep hardware level. I'm afraid to reinstall it now.


Here's the relevant output of lspci -vvnn

00:06.0 Ethernet controller [0200]: Atheros Communications Inc. AR2413 802.11bg NIC [168c:001a] (rev 01)
    Subsystem: Atheros Communications Inc. Compex Wireless 802.11 b/g  MiniPCI Adapter, Rev A1 [WLM54G] [168c:2052]
    Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Latency: 168 (2500ns min, 7000ns max), Cache Line Size: 32 bytes
    Interrupt: pin A routed to IRQ 18
    Region 0: Memory at d0000000 (32-bit, non-prefetchable) [size=64K]
    Capabilities: [44] Power Management version 2
        Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
        Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=2 PME-
    Kernel driver in use: ath5k