| 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
| ||
|
Message-ID: <20080211031935.GA12563@zenon.in.qult.net> Date: Mon, 11 Feb 2008 04:19:35 +0100 From: Ignacy Gawedzki <lkml@...t.net> To: Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Oops with hostap_pci (?) Hi, A few days back I started having strange lockups on a gateway machine so I started looking at things. Then I compiled the 2.6.24.1 kernel and started having oopses not long after upping the wlan0 (hostap_pci) interface. So I enabled netconsole and got a few logs. Now the sad point is that I'm getting an oops even with my older kernel which used to be fine (2.6.23.9). I also checked with 2.6.24 and the effects are the same: I boot, I up the wlan0 interface and a few seconds or minutes later, boom! Sometimes only rmmod'ing hostap_pci triggers the oops. I'm suspecting some hardware problem and have already checked the ram with memtest86+ and tested with only one memory module out of two plugged: same thing. If anybody could take a look at these and shed some light on that issue... Thanks a lot, Ignacy -- Save the whales. Feed the hungry. Free the mallocs. View attachment "oops1.txt" of type "text/plain" (2130 bytes) View attachment "oops2.txt" of type "text/plain" (2047 bytes) View attachment "oops3.txt" of type "text/plain" (2123 bytes) View attachment "oops4.txt" of type "text/plain" (2082 bytes) View attachment "oops5.txt" of type "text/plain" (1917 bytes) View attachment "oops6.txt" of type "text/plain" (2124 bytes) View attachment "oops7.txt" of type "text/plain" (2130 bytes)
Powered by blists - more mailing lists