linux-kernel - Re: ath9k crash 3.2-rc7

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Fri, 06 Jan 2012 12:10:16 +0400
From:	MR <g7af0ec1e3ea1e7b1@...tmail.ru>
To:	Mohammed Shafi <shafi.wireless@...il.com>
CC:	linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org
Subject: Re: ath9k crash 3.2-rc7

 >I have some unpleasant news: it looks like it takes slightly longer with
 >the 
 >fix, but the crash still managed to occur with 3.2 and I lack ESP to check 
 > for warnings immediately before that. I thought that 8 hours is enough 
 > testing, heh. It simply took 9 and a half under nigh-ideal conditions 
 > (stable signal from fixed AP with notebook also steadily in one place).

By the way, what could trigger these crashes in "network event sense"? If this 
can be reproduced with Ad-Hoc (something like ""Ad-Hoc peer changes ESSID then 
changes it back"), I could easily do some stress-testing with a second Linux-
running notebook.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/