Bug#345647: madwifi driver causes kernel oops

2006-01-04 Thread Graham
Hi Kel, Thank you for the links. > Well, in my experience these gui apps for configuring wireless on linux > really cause more trouble than they are worth. Maybe, but: 1. You and I are fine with console based configuration tools, but many people, including the owner of this laptop, will not tou

Bug#345647: madwifi driver causes kernel oops

2006-01-04 Thread Kel Modderman
Graham wrote: Hi Kel, Thank you for the links. Well, in my experience these gui apps for configuring wireless on linux really cause more trouble than they are worth. Maybe, but: 1. You and I are fine with console based configuration tools, but many people, including the owner of th

Bug#345647: madwifi driver causes kernel oops

2006-01-03 Thread Loïc Minier
On Tue, Jan 03, 2006, Graham wrote: > ioctl(10, SIOCGIWSCAN According to include/linux/wireless.h, this is the syscall used to request scan results from the last scan to the madwifi driver, check whether "iwlist ath0 scan" crashes too. -- Loïc Minier <[EMAIL PROTECTED]> Current Earth status:

Bug#345647: madwifi driver causes kernel oops

2006-01-03 Thread Kel Modderman
Graham wrote: It may be related to the inability of this module to do background scanning, or it could just be a plain old bug in the code. Try using the basic wireless-tools and refrain from using the graphical apps, and see if you can reproduce this instability. Hi Kel, I'm just gettin

Bug#345647: madwifi driver causes kernel oops

2006-01-03 Thread Graham
> Maybe you can get the syscall causing this with strace? That's a good idea. Here's the last bit of the strace output. gettimeofday({1136337522, 921263}, NULL) = 0 gettimeofday({1136337522, 921656}, NULL) = 0 gettimeofday({1136337522, 922370}, NULL) = 0 ioctl(5, FIONREAD, [1]) =

Bug#345647: madwifi driver causes kernel oops

2006-01-03 Thread Graham
> It may be related to the inability of this module to do background > scanning, or it could just be a plain old bug in the code. Try using the > basic wireless-tools and refrain from using the graphical apps, and see > if you can reproduce this instability. Hi Kel, I'm just getting started with

Bug#345647: madwifi driver causes kernel oops

2006-01-03 Thread Loïc Minier
Hi, On Mon, Jan 02, 2006, Graham wrote: > When I click "scan for networks" in kwifimanager, kwifimanager > crashes, and dmesg shows this: Maybe you can get the syscall causing this with strace? Cheers, -- Loïc Minier <[EMAIL PROTECTED]>

Bug#345647: madwifi driver causes kernel oops

2006-01-02 Thread Kel Modderman
Graham wrote: Package: madwifi-source Version: 2005 I've built the module against the Debian "official" kernel 2.6.14-2-686 (version 2.6.14-7). I have a ThinkPad A22p and an Enterasys Networks PCMCIA a/b/g card. I will attach the output of "lspci -vvv". When I click "scan for networks" in

Bug#345647: madwifi driver causes kernel oops

2006-01-02 Thread Graham
Package: madwifi-source Version: 2005 I've built the module against the Debian "official" kernel 2.6.14-2-686 (version 2.6.14-7). I have a ThinkPad A22p and an Enterasys Networks PCMCIA a/b/g card. I will attach the output of "lspci -vvv". When I click "scan for networks" in kwifimanager, kw