[lkml]   [2012]   [Jan]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: ath9k crash 3.2-rc7
2012/1/9 MR <>:
>  >> So, I am building 3.2 with two patches: over/under-flow catcher (pity
>  >that
>  >> it seems to be on a multiple-times-per-second codepath and just leaving
>  >the
>  > > checks there for everyone is suboptimal) and allegedely proper fix. Both
>  > > applied OK with a small offset.
>  >
>  > as per our assumption, we should not see those over/underflow errors,
>  > with the patch
>  > above mentioned. please let us know if you hit upon this warnings,
>  > even after the proper fix.
> In my experience (and as I understand the situation) if garbage is writen to
> the "chan", it is caught by the check and device is dead-until-reboot anyway.
> On 3.0, even without checks device was dead-until-reboot, but no crash
> happened. All these checks do is converting "panic" to "WiFi broken" for 3.2.

true those checks are to confirm that 'chan' is corrupted and the
patch is to fix it.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2012-01-09 08:59    [W:0.036 / U:0.864 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site