lkml.org 
[lkml]   [2008]   [Feb]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Oops with hostap_pci (?)
On Mon, Feb 11, 2008 at 04:19:35AM +0100, thus spake Ignacy Gawedzki:
> 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...

Okay, false alarm... it's all my fault. :/

The cause of the problem was my previous tampering with udev rules. The udev
rules as such (on Ubuntu Gutsy) were bad for hostapd, since persistent rules
were written for the wlan0ap interface name created by hostapd. So I changed
a few things that had the unexpected effect of renaming the initial
hostap_pci's wifi0 into wlan0ap. This in turn made hostap_pci oops in many
cases.

Anyway, I've modified my udev rules again and hopefully this will be it. =)

--
"The whole problem with the world is that fools and fanatics are
always so certain of themselves, and wiser people so full of doubts."
- Bertrand Russell


\
 
 \ /
  Last update: 2008-02-11 13:25    [W:0.385 / U:0.032 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site