[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: IRQ 19 Problem in Squeeze & Wheezy but Sid OK



On Sun, Mar 20, 2011 at 12:32 PM, Wayne Topa <linuxtwo@gmail.com> wrote:
>  Linux Version 2.6.32-5-amd64
>  Compiled #1 SMP Wed Jan 12 03:40:32 UTC 2011
>  Two 1GHz AMD Athlon 64 X2 Processors, 4GB RAM
>  3999.52 Bogomips Total
>
>
> I installed, back in February, Squeeze on 3 partitions. For 2 days
> Squeeze worked fine with wicd but then quit with this error:
>
> ____
>>
>> eb 22 12:13:10 dj kernel: [  604.383622] wlan0: authenticate with
>> 00:21:e8:b5:c4:b5 (try 1)
>> Feb 22 12:13:10 dj kernel: [  604.580045] wlan0: authenticate with
>> 00:21:e8:b5:c4:b5 (try 2)
>> Feb 22 12:13:10 dj kernel: [  604.780042] wlan0: authenticate with
>> 00:21:e8:b5:c4:b5 (try 3)
>> Feb 22 12:13:10 dj kernel: [  604.953908] Pid: 0, comm: kworker/0:0 Not
>> tainted 2.6.37-1-amd64 #1
>> Feb 22 12:13:10 dj kernel: [  604.953910] Call Trace:
>> Feb 22 12:13:10 dj kernel: [  604.953912]  <IRQ>  [<ffffffff81092ff1>] ?
>> __report_bad_irq+0x30/0x80
>> Feb 22 12:13:10 dj kernel: [  604.953923]  [<ffffffff81093168>] ?
>> note_interrupt+0x127/0x19f
>> Feb 22 12:13:10 dj kernel: [  604.953927]  [<ffffffff8100f6d5>] ?
>> sched_clock+0x5/0x8
>> Feb 22 12:13:10 dj kernel: [  604.953931]  [<ffffffff81093b47>] ?
>> handle_fasteoi_irq+0xcc/0xf7
>> Feb 22 12:13:10 dj kernel: [  604.953935]  [<ffffffff8100bf48>] ?
>> handle_irq+0x17/0x1f
>> Feb 22 12:13:10 dj kernel: [  604.953938]  [<ffffffff8100b603>] ?
>> do_IRQ+0x50/0xb5
>> Feb 22 12:13:10 dj kernel: [  604.953942]  [<ffffffff8131ef13>] ?
>> ret_from_intr+0x0/0x11
>> Feb 22 12:13:10 dj kernel: [  604.953944]  <EOI>  [<ffffffff81028108>] ?
>> native_safe_halt+0x2/0x3
>> Feb 22 12:13:10 dj kernel: [  604.953951]  [<ffffffff81010a95>] ?
>> default_idle+0x39/0x57
>> Feb 22 12:13:10 dj kernel: [  604.953954]  [<ffffffff81010bac>] ?
>> c1e_idle+0xf9/0xfd
>> Feb 22 12:13:10 dj kernel: [  604.953957]  [<ffffffff81008be9>] ?
>> cpu_idle+0xb2/0x124
>> Feb 22 12:13:10 dj kernel: [  604.953960]  [<ffffffff81317db4>] ?
>> start_secondary+0x1e5/0x1eb
>> Feb 22 12:13:10 dj kernel: [  604.980023] wlan0: authentication with
>> 00:21:e8:b5:c4:b5 timed out
>>
>>
>> Message from syslogd@dj at Tue Feb 22 12:13:10 2011 ...
>> dj kernel: [  604.953998] Disabling IRQ #19
>
> I then upgraded the 2nd Squeeze partition to Testing/Wheezy and the same
> error occurred as above.
>
> After many upgrade the log messages have changed, somewhat, but the problem
> remains.  This line was the change
> ___
>  irq 19: nobody cared (try booting with the "irqpoll" option)
> which I have done on both with no change noticeable.
>
>  In addition any login on tty1 gets
> After many upgrade the log messages have changed, somewhat, but the problem
> remains.  This line was the change
>
> which I have done on both with no change noticeable other the
> line about trying irqpoll being gone.
> ______
>  Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
> permitted by applicable law.
> -bash: no job control in this shell   <<<<<<<<<<< Only on tty1
>
> I then upgraded the 3rd partition to testing then to Sid.  It works
> fine without ANY of above problems.  After an upgrade a few days ago
> the wlan0 interface times out in less then the  lease time though.
>
> It seems like a kernel error but all 3 partitions are running the same
> kernel.  I did try the 2.6.37 kernel in Wheezy but the problem remains.
>
> Here is the current log message for both Squeeze & Wheezy
> ___
> Mar 20 12:29:34 dj kernel: [   68.088593] ath9k 0000:03:00.0: PCI INT A
> disabled
> Mar 20 12:29:34 dj kernel: [   68.088623] ath9k: Driver unloaded
> Mar 20 12:29:34 dj kernel: [   68.228646] cfg80211: Using static regulatory
> domain info
> Mar 20 12:29:34 dj kernel: [   68.228649] cfg80211: Regulatory domain: US
> Mar 20 12:29:34 dj kernel: [   68.228651] ^I(start_freq - end_freq @
> bandwidth), (max_antenna_gain, max_eirp)
> Mar 20 12:29:34 dj kernel: [   68.228654] ^I(2402000 KHz - 2472000 KHz @
> 40000 KHz), (600 mBi, 2700 mBm)
> Mar 20 12:29:34 dj kernel: [   68.228657] ^I(5170000 KHz - 5190000 KHz @
> 40000 KHz), (600 mBi, 2300 mBm)
> Mar 20 12:29:34 dj kernel: [   68.228659] ^I(5190000 KHz - 5210000 KHz @
> 40000 KHz), (600 mBi, 2300 mBm)
> Mar 20 12:29:34 dj kernel: [   68.228662] ^I(5210000 KHz - 5230000 KHz @
> 40000 KHz), (600 mBi, 2300 mBm)
> Mar 20 12:29:34 dj kernel: [   68.228664] ^I(5230000 KHz - 5330000 KHz @
> 40000 KHz), (600 mBi, 2300 mBm)
> Mar 20 12:29:34 dj kernel: [   68.228666] ^I(5735000 KHz - 5835000 KHz @
> 40000 KHz), (600 mBi, 3000 mBm)
> Mar 20 12:29:34 dj kernel: [   68.229107] cfg80211: Calling CRDA for
> country: US
> Mar 20 12:29:34 dj kernel: [   68.245630] ath9k 0000:03:00.0: PCI INT A ->
> GSI 19 (level, low) -> IRQ 19
> Mar 20 12:29:34 dj kernel: [   68.245642] ath9k 0000:03:00.0: setting
> latency timer to 64
> Mar 20 12:29:34 dj kernel: [   68.370925] ath: EEPROM regdomain: 0x10
> Mar 20 12:29:34 dj kernel: [   68.370926] ath: EEPROM indicates we should
> expect a direct regpair map
> Mar 20 12:29:34 dj kernel: [   68.370929] ath: Country alpha2 being used: CO
> Mar 20 12:29:34 dj kernel: [   68.370931] ath: Regpair used: 0x10
> Mar 20 12:29:34 dj kernel: [   68.371882] phy0: Selected rate control
> algorithm 'ath9k_rate_control'
> Mar 20 12:29:34 dj kernel: [   68.373019] cfg80211: Calling CRDA for
> country: CO
> Mar 20 12:29:34 dj kernel: [   68.373170] Registered led device:
> ath9k-phy0::radio
> Mar 20 12:29:34 dj kernel: [   68.373188] Registered led device:
> ath9k-phy0::assoc
> Mar 20 12:29:34 dj kernel: [   68.373205] Registered led device:
> ath9k-phy0::tx
> Mar 20 12:29:34 dj kernel: [   68.373223] Registered led device:
> ath9k-phy0::rx
> Mar 20 12:29:34 dj kernel: [   68.373232] phy0: Atheros AR5418 MAC/BB Rev:2
> AR2133 RF Rev:81: mem=0xffffc900165a0000, irq=19
> Mar 20 12:29:40 dj kernel: [   74.268771] ADDRCONF(NETDEV_UP): wlan0: link
> is not ready
>
> I have been troubleshooting this for a month now and have not found anything
> I can pin it to.
>
> There was a similar post a week or two ago about IRQ 19 causing the disks
> (IIRC) to restart but I have not heard of any solutions yet.
>
> Google has a bunch of IRQ 19 problems on debian but they are over a year old
> and no real solutions were found that I could find.
>
> Any comments/suggestions would be sincerely appreciated.
>
> Wayne
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject
> of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> Archive: 4D863A3F.9050700@gmail.com">http://lists.debian.org/4D863A3F.9050700@gmail.com
>
>

Hi Wayne,

You reported is problem on Feb 27, right?

The IRQ 19 problem I reported then seems to disappear when I boot my
machine with the "irqpoll" parameter.

At least it has been up for 15 days with its /proc/irq/19/spurious
looking like this:
count 58513
unhandled 2
last_unhandled 1208748848 ms

the last unhandled IRQ being nearly 14 days ago.

Mark


Reply to: