[Bug 341952] Re: system freeze/crash in jaunty - "ath5k phy0: unsupported jumbo/ath5k phy0: noise floor calibration timeout"

2009-03-22 Thread gene
I am not making it up, or am I? ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Summary changed: - system freeze/crash in jaunty - "ath5k phy0: unsupported jumbo/ath5k phy0: noise floor calibration timeout" + ath5k locks up system in jaunty - "ath5k phy0: noise floor

[Bug 341952] Re: system freeze/crash in jaunty - "ath5k phy0: unsupported jumbo/ath5k phy0: noise floor calibration timeout"

2009-03-22 Thread gene
Dear Leann, I got yet another crash today after just a few hours of fresh session. I was using wireless with no encryption. I do not have ethernet here. The agonizing kernel entries of the kernel log are these (followed by the boot messages): Mar 22 19:12:06 jenshen kernel: [28185.688033] wlan0

[Bug 341952] Re: system freeze/crash in jaunty - "ath5k phy0: unsupported jumbo/ath5k phy0: noise floor calibration timeout"

2009-03-22 Thread gene
Hi Leann, So what do we do next? Thanks -- system freeze/crash in jaunty - "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 Ubuntu Bugs, which is subscribed to Ubunt

[Bug 341952] Re: system freeze/crash in jaunty - "ath5k phy0: unsupported jumbo/ath5k phy0: noise floor calibration timeout"

2009-03-20 Thread gene
I got an update here. Not only that ath5k does not so any job (with WEP) it still crashes my system. I had it once again! So the updated kernel and ath5k driver do not get together still. As I have mentioned many times before, the kernel log complains about ath5k. Especially, before its own "dea

[Bug 341952] Re: system freeze/crash in jaunty - "ath5k phy0: unsupported jumbo/ath5k phy0: noise floor calibration timeout"

2009-03-19 Thread gene
I do not have to blacklist it. But I do need wireless. With the latest kernel *28-11 and backports it does not seem to hurt my system anymore. There is another problem introduced here though. I noticed that when using WEP encryption I have problems with connection. At the moment I think I have a

[Bug 341952] Re: system freeze/crash in jaunty - "ath5k phy0: unsupported jumbo/ath5k phy0: noise floor calibration timeout"

2009-03-18 Thread xtknight
Yes, ath5k hard-freezes my entire system. Even Magic SysRq won't work. Very frustrating. It didn't used to do this. If you don't need wireless, simply blacklist ath5k in any of the /etc/modprobe.d/blacklist* files to stop it from loading on bootup. -- system freeze/crash in jaunty - "ath5k phy

[Bug 341952] Re: system freeze/crash in jaunty - "ath5k phy0: unsupported jumbo/ath5k phy0: noise floor calibration timeout"

2009-03-17 Thread gene
I noticed I can't ssh from my machine with wireless. Apparently, when using wireless, I have a zero upload and a descent download rate equal to that on wired connection. On ethernet, there is no problem with upload. I can test the same router with another laptop running Ubuntu 8.10 - no problem

[Bug 341952] Re: system freeze/crash in jaunty - "ath5k phy0: unsupported jumbo/ath5k phy0: noise floor calibration timeout"

2009-03-17 Thread gene
Let me know if I should file another bug here Thanks -- system freeze/crash in jaunty - "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 Ubuntu Bugs, which is subscr

[Bug 341952] Re: system freeze/crash in jaunty - "ath5k phy0: unsupported jumbo/ath5k phy0: noise floor calibration timeout"

2009-03-17 Thread gene
I noticed I can't ssh from my machine with wireless. Apparently, when using wireless, I have a zero upload and a descent download rate equal to that on wired connection. On ethernet, there is no problem with upload. I can test the same router with another laptop running Ubuntu 8.10 - no problem

[Bug 341952] Re: system freeze/crash in jaunty - "ath5k phy0: unsupported jumbo/ath5k phy0: noise floor calibration timeout"

2009-03-16 Thread gene
Hi Leann, I installed backport modules a couple days ago. Since then no system lock-ups so far. However, I noticed somewhat worse performance of wireless. Sometimes, when I try to connect via ssh/sft/http I fail. But when switching to the ethernet- everything goes smooth again. I also started se

[Bug 341952] Re: system freeze/crash in jaunty - "ath5k phy0: unsupported jumbo/ath5k phy0: noise floor calibration timeout"

2009-03-15 Thread gene
Thanks Leann, You just anticipated my exact question! I've been using ethernet for about 2 days. No crashes so far. As well as entries like the logs: "ath5k phy0: noise floor calibration timeout" I have read some of the related bug threads where you advised to use backports. I will try installi

[Bug 341952] Re: system freeze/crash in jaunty - "ath5k phy0: unsupported jumbo/ath5k phy0: noise floor calibration timeout"

2009-03-15 Thread Leann Ogasawara
Hi gene, If you want switch to testing with just the wired ethernet for a while just to try to confirm this is related to wifi that would be great. Additionally, you may want to try installing linux-backports-modules- jaunty as it contains an updated compat-wireless stack. Thanks. -- system fre

[Bug 341952] Re: system freeze/crash in jaunty - "ath5k phy0: unsupported jumbo/ath5k phy0: noise floor calibration timeout"

2009-03-15 Thread Bug Watch Updater
** Changed in: linux Status: Unknown => Confirmed -- system freeze/crash in jaunty - "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 Ubuntu Bugs, which is su

[Bug 341952] Re: system freeze/crash in jaunty - "ath5k phy0: unsupported jumbo/ath5k phy0: noise floor calibration timeout"

2009-03-15 Thread Tormod Volden
** Changed in: linux Bugwatch: Red Hat Bugzilla #489078 => Linux Kernel Bug Tracker #12647 Status: Confirmed => Unknown ** Changed in: bugzilla Importance: Unknown => Undecided Bugwatch: Linux Kernel Bug Tracker #12647 => None Status: Confirmed => New ** Changed in: bug

[Bug 341952] Re: system freeze/crash in jaunty - "ath5k phy0: unsupported jumbo/ath5k phy0: noise floor calibration timeout"

2009-03-13 Thread gene
Hi Leann, Thanks a lot for your response! This is what I hoped for.

[Bug 341952] Re: system freeze/crash in jaunty - "ath5k phy0: unsupported jumbo/ath5k phy0: noise floor calibration timeout"

2009-03-13 Thread gene
** Attachment added: "dmesg.0" http://launchpadlibrarian.net/23843815/dmesg.0 -- system freeze/crash in jaunty - "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

[Bug 341952] Re: system freeze/crash in jaunty - "ath5k phy0: unsupported jumbo/ath5k phy0: noise floor calibration timeout"

2009-03-13 Thread gene
I do not know how o reproduce the bug. It happens out of blue... seemingly. Like I said I will study what other people did at bugzilla.kernel and let you know. Should I switch to ethernet interface though... Thanks -- system freeze/crash in jaunty - "ath5k phy0: unsupported jumbo/ath5k phy0: n

[Bug 341952] Re: system freeze/crash in jaunty - "ath5k phy0: unsupported jumbo/ath5k phy0: noise floor calibration timeout"

2009-03-13 Thread Leann Ogasawara
Hi Gene, Thanks for taking the time to report this bug and helping to make Ubuntu better. The reason this bug was likely getting overlooked was because it was assigned to the entire Ubuntu project as a whole rather than against the specific kernel package (linux). It is important to make sure bu

[Bug 341952] Re: system freeze/crash in jaunty : "ath5k phy0: unsupported jumbo/ath5k phy0: noise floor calibration timeout"

2009-03-13 Thread gene
** Summary changed: - 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 : "ath5k phy0: unsupported jumbo/ath5k phy0: noise floor calibration timeout" ** Summar

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

2009-03-13 Thread 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-ca

[Bug 341952] Re: system freeze/crash in jaunty (maybe related to "vmap allocation failed" or "ath5k phy0: unsupported jumbo/ath5k phy0: noise floor calibration timeout"

2009-03-13 Thread gene
** Bug watch added: Linux Kernel Bug Tracker #12647 http://bugzilla.kernel.org/show_bug.cgi?id=12647 ** Also affects: bugzilla via http://bugzilla.kernel.org/show_bug.cgi?id=12647 Importance: Unknown Status: Unknown -- system freeze/crash in jaunty (maybe related to "vmap allocat

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

2009-03-13 Thread gene
Yesterday I made an attempt to bring my system to crash by putting it under stress. I simultaneously opened about 500 tabs with both firefox and konqueror (1000 together). The memory was all occupied, making the system to start swapping . System slowed down and even I thought it was it: it sto

[Bug 341952] Re: system freeze/crash in jaunty (maybe related to "vmap allocation failed" or "ath5k phy0: unsupported jumbo/ath5k phy0: noise floor calibration timeout"

2009-03-13 Thread Bug Watch Updater
** Changed in: bugzilla Status: Unknown => Confirmed -- 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 becau

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

2009-03-12 Thread Bug Watch Updater
** Changed in: linux Status: Unknown => Confirmed ** Changed in: fedora Status: Unknown => Confirmed -- system freeze/crash in jaunty (maybe related to "vmap allocation failed" error message) https://bugs.launchpad.net/bugs/341952 You received this bug notification because you are

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

2009-03-12 Thread gene
Forgot to mention that: In the time of crash when attempting to ssh to the machine from another computer I get "no host to route" message Another thing is that the whole desktop seems completely frozen (gnome widgets etc), however the screen does not get blank ** Bug watch added: Red Hat Bugzill

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

2009-03-12 Thread gene
** Summary changed: - system freeze/crash in jaunty + system freeze/crash in jaunty (maybe related to "vmap allocation failed" error message) -- system freeze/crash in jaunty (maybe related to "vmap allocation failed" error message) https://bugs.launchpad.net/bugs/341952 You received this bug

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

2009-03-12 Thread gene
Since I have been experiencing a bunch of other problems with my video card from ATI ( RC410 [Radeon Xpress 200M] [1002:5a62]) , the problem could be related to it. I will attach my xorg.conf ** Attachment added: "xorg.conf" http://launchpadlibrarian.net/23789447/xorg.conf -- system freeze/cr

[Bug 341952] Re: system freeze/crash in jaunty

2009-03-12 Thread gene
I also tried to examine all entries prior to the system boots by grep '0\.00' /var/log/* -B10 | grep -v '0\.00' -A4 I attach its output Thanks ** Attachment added: "preboot_logs" http://launchpadlibrarian.net/23788951/preboot_logs -- system freeze/crash in jaunty https://bugs.launc

[Bug 341952] Re: system freeze/crash in jaunty

2009-03-12 Thread gene
Here's some attachments and also more lines (with -B4 option) of the dmesg logs zgrep 'vmap' /var/log/dmesg* -A5 -B3; grep /var/log/dmesg* /var/log/dmesg.0:[ 26.044801] type=1505 audit(1236820482.928:8): operation="profile_load" name="/usr/sbin/cupsd" name2="default" pid=2542 /var/log/dmesg.0:[