* Revert commit in ath9k
@ 2009-08-14 3:42 Sujith
2009-08-14 6:09 ` Pavel Roskin
2009-08-14 12:19 ` John W. Linville
0 siblings, 2 replies; 4+ messages in thread
From: Sujith @ 2009-08-14 3:42 UTC (permalink / raw)
To: linville; +Cc: linux-wireless
John,
Can you revert the commit - "ath9k: Change DEBUG level for certain interrupts" ?
This interrupt seems to trigger fairly often and floods the log.
The driver does seem to work with this message suppressed.
(which was the original behaviour).
The actual cause for this bug is still unknown, but until it is
found and fixed, the earlier behaviour can be retained.
Sorry for the trouble. :)
Sujith
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Revert commit in ath9k
2009-08-14 3:42 Revert commit in ath9k Sujith
@ 2009-08-14 6:09 ` Pavel Roskin
2009-08-14 6:17 ` Sujith
2009-08-14 12:19 ` John W. Linville
1 sibling, 1 reply; 4+ messages in thread
From: Pavel Roskin @ 2009-08-14 6:09 UTC (permalink / raw)
To: Sujith; +Cc: linville, linux-wireless
Quoting Sujith <Sujith.Manoharan@atheros.com>:
> John,
>
> Can you revert the commit - "ath9k: Change DEBUG level for certain
> interrupts" ?
> This interrupt seems to trigger fairly often and floods the log.
I think it would be better to revert only the part for the actually
triggered AR_INTR_SYNC_LOCAL_TIMEOUT. This way we'll learn of other
unexpected interrupts if they happen for some users.
--
Regards,
Pavel Roskin
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Revert commit in ath9k
2009-08-14 6:09 ` Pavel Roskin
@ 2009-08-14 6:17 ` Sujith
0 siblings, 0 replies; 4+ messages in thread
From: Sujith @ 2009-08-14 6:17 UTC (permalink / raw)
To: Pavel Roskin; +Cc: linville, linux-wireless
Pavel Roskin wrote:
> Quoting Sujith <Sujith.Manoharan@atheros.com>:
>
> > John,
> >
> > Can you revert the commit - "ath9k: Change DEBUG level for certain
> > interrupts" ?
> > This interrupt seems to trigger fairly often and floods the log.
>
> I think it would be better to revert only the part for the actually
> triggered AR_INTR_SYNC_LOCAL_TIMEOUT. This way we'll learn of other
> unexpected interrupts if they happen for some users.
Well, the other interrupts are handled appropriately (marked as FATAL).
And the ISR does a chip reset for all interrupts marked as FATAL.
SYNC_LOCAL_TIMEOUT was the one I was really interested in, since I saw it
occurring in my machine - and was curious about its occurrence elsewhere.
Apparently, it is widespread. :)
Sujith
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Revert commit in ath9k
2009-08-14 3:42 Revert commit in ath9k Sujith
2009-08-14 6:09 ` Pavel Roskin
@ 2009-08-14 12:19 ` John W. Linville
1 sibling, 0 replies; 4+ messages in thread
From: John W. Linville @ 2009-08-14 12:19 UTC (permalink / raw)
To: Sujith; +Cc: linux-wireless
On Fri, Aug 14, 2009 at 09:12:08AM +0530, Sujith wrote:
> Can you revert the commit - "ath9k: Change DEBUG level for certain interrupts" ?
> This interrupt seems to trigger fairly often and floods the log.
> The driver does seem to work with this message suppressed.
> (which was the original behaviour).
>
> The actual cause for this bug is still unknown, but until it is
> found and fixed, the earlier behaviour can be retained.
>
> Sorry for the trouble. :)
OK
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2009-08-14 12:30 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-08-14 3:42 Revert commit in ath9k Sujith
2009-08-14 6:09 ` Pavel Roskin
2009-08-14 6:17 ` Sujith
2009-08-14 12:19 ` John W. Linville
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).