Bug#345647: madwifi driver causes kernel oops

[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 touch them. The
majority of users really do want a GUI.

2. Software should never crash. Error messages are fine when something
goes wrong, but a crash is never acceptable, especially in kernel
mode.

So "don't use a GUI config tool" is only valid as a temporary
workaround, not as a permanent solution.

That said, I'm here to help, not to belittle your efforts.

Let me know if there's anything I can do.

I'm thinking about having a look at the code (ath_ioctl_giwscan). I'm
pretty good with C, though not at all familiar with Linux kernel code.
But it might be worth a shot.

-- graham