On Thu, 2010-02-18 at 13:58 -0800, Mark Sutton wrote: > On Thu, Feb 18, 2010 at 12:31:26PM -0800, Mark Sutton wrote: > > Hi, > > I have this problem as well. > > Hardware is: > > > > Atheros Communications Inc. AR5008 > > Atheros AR5416 MAC/BB Rev:2 AR5133 RF Rev:81 > > > > Kernel:Linux 2.6.32.7 #2 PREEMPT Thu Feb 4 14:19:02 PST 2010 i686 GNU/Linux > > > Here is a call trace from last night when it hung during reboot. > > > pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff: clean. > pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcf7: clean. > pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff: clean. > intel8x0_measure_ac97_clock: measured 55061 usecs (2653 samples) > intel8x0: clocking to 48000 > Registered led device: ath9k-phy0::radio > Registered led device: ath9k-phy0::assoc > Registered led device: ath9k-phy0::tx > Registered led device: ath9k-phy0::rx > phy0: Atheros AR5416 MAC/BB Rev:2 AR5133 RF Rev:81: mem=0xf0ce0000, irq=11 > Adding 1044216k swap on /dev/hda2. Priority:-1 extents:1 across:1044216k > EXT4-fs (hda4): mounted filesystem with ordered data mode ... > Pid: 621, comm: phy0 Not tainted (2.6.32.7 #2) Portable PC > EIP: 0060:[<f087fa1f>] EFLAGS: 00000292 CPU: 0 > EIP is at yenta_interrupt+0x1f/0xf0 [yenta_socket]
That's the PCMCIA subsystem, not ath9k. We could suspect ath9k to cause it if it was immediately after ath9k was loaded, but there were other things going on after the ath9k initialization. -- Regards, Pavel Roskin _______________________________________________ ath9k-devel mailing list [email protected] https://lists.ath9k.org/mailman/listinfo/ath9k-devel
