[Bug 341952] Re: system freeze/crash in jaunty (maybe related to "vmap allocation failed" error message)

[gene]

Hello all,
I have a question. Does anybody care at all? If not, what's the purpose of installing alpha in the first place? 
I report a very important problem that might be jeopardizing the release of jaunty itself.... and still talking to myself

It is not a problem of impossibility to use eye-candy compiz features or
some other laughable issues. It is the system crash all of a sudden!
Kernel is dead. This what makes M$ Windows Windows....

When I converted to Linux/Unix, I hardly can recall of any crashes
(Fedora Core 4). Nowadays it is pretty occasional. I understand that it
mostly concerns   video and other hardware drivers, mostly proprietary
or back-engineered ones.


So could I get some sort of feedback at least? How do I debug the kernel? How do I debug some of its suspicious modules at least? Hope to hear from anyone...

Thanks in advance

** Summary changed:

- system freeze/crash in jaunty (maybe related to "vmap allocation failed" error message)
+ system freeze/crash in jaunty (maybe related to "vmap allocation failed" or "ath5k phy0: unsupported jumbo/ath5k phy0: noise floor calibration timeout"

-- 
system freeze/crash in jaunty (maybe related to "vmap allocation failed" or "ath5k phy0: unsupported jumbo/ath5k phy0: noise floor calibration timeout"  
https://bugs.launchpad.net/bugs/341952
You received this bug notification because you are a member of Kernel
Bugs, which is a direct subscriber.