Comment 31 for bug 341952
Revision history for this message
| Romain1101 (romainmadala) wrote Re: [Bug 341952] Re: ath5k locks up system in jaunty - "ath5k phy0: noise floor calibration timeout" | #31 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Well,
The failure keeps occuring ! My screen freezes, only the mouse can move but keep its current icon when occurs the failure and neither keyboard nor mouse respond to events!
The only thing I am able to do is a hard reboot of the machine.
Well the failure may be witnessed on the .xsession-error log.
Please help, or at least can someone tell me what package I have to link to this bug?
----- Mail Original -----
De: "Romain1101" <email address hidden>
À: <email address hidden>
Envoyé: Mardi 24 Mars 2009 16h10:40 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: Re: [Bug 341952] Re: ath5k locks up system in jaunty - "ath5k phy0: noise floor calibration timeout"
Thanks gene !
Indeed that line in kern.log is strange and therefore interesting but It does not occurs
everytime with my failure whereas that paragraph about the IRQ11 - which already provided troobles
to me in previous versions of ubuntu because of my ethernet card - really is.
Furthermore...I updated my system this morning with the new linux-image pkg
and I may have understood something, which i'm gonna explain to you :
I've been experiencing for weeks a reboot of my X server...sometimes, dont know whether it's kde, plasma
or xorg but something crashes and then I'm sent back to the KDE login screen.
And I think this is the same bug, and that the problem yesterday was simply that my xserver couldn't restart on its own!
Because as you says, I think I just lose the interface with the system - that the system keeps working.
I'll try to ssh my system from outside, I guess we will be right.
Do you know if there is a mean ( a shell command ) to inspect the tty output used
you by default kde uses the #7 and then you can go back to a pure console using ctrl+alt+F#
because I have the impression that my all problem comes from either kde or plasma ( who knows maybe deeply from qtcore)
and comes to log on a diferent tty ? As well just to check, could you remind me a shell command which permits to
check the memory status of my system in real time ?
I'll try as well launch a session by my own so as to get back some trace...
Do you have any idea how I could better get back some traces ?
Because I didn't succeed to get some when my xserver reboots...never succeed to know why !!
about ath5, I don't understand your query because my wireless driver is
ipw2200 with an intel card ?
----- Mail Original -----
De: "gene" <email address hidden>
À: <email address hidden>
Envoyé: Mardi 24 Mars 2009 14h51:07 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne
Objet: [Bug 341952] Re: ath5k locks up system in jaunty - "ath5k phy0: noise floor calibration timeout"
I would google this ominous entry in your ker.log:
"Mar 23 16:10:35 MadPrt-010909 kernel: [ 921.661361] kwalletmanager[
It might be related to gtk (if it is, or qt, if its kde ) +skype, since things crash when you manipulate a window
It tells you that it segfaults, this hurts. However, this might easier
to troubleshoot than in my case. Ne segfault entries.
If you can't find it on the launchpad, I suggest you open a new bug.
Alternatively, deinstall skype and use linphone or gnome-meeting :)
Good luck!
--
ath5k locks up system in jaunty - "ath5k phy0: noise floor calibration timeout"
https:/
You received this bug notification because you are a direct subscriber
of the bug.
Status in The Bugzilla Bug Tracking System: Invalid
Status in The Linux Kernel: Confirmed
Status in “linux” source package in Ubuntu: Triaged
Status in Fedora: Confirmed
Bug description:
After upgrading to jaunty I started experiencing frequent system/x server freezes.
Happens all of a sudden with X session completely frozen with no keys working, including SysRq. Hard reboot is necessary.
It is hard to tell what is the reason. Tried to examine the logs - doesn't give me a clue.
There are a number of suspicious entries in the /var/log/dmesg* though
All of them except for the current and the oldest ones are all ENDING with this:
vmap allocation failed: use vmalloc=<size> to increase size.
Like:
~$ zgrep 'vmap' /var/log/dmesg* -A5
/var/log/dmesg.0:[ 35.911114] vmap allocation failed: use vmalloc=<size> to increase size.
/var/log/
/var/log/
/var/log/
Also I can recall that my memory icon in the gnome-system-
filled (light and dark green ) at the time of crashes.
uname -a
Linux jenshen 2.6.28-8-generic #28-Ubuntu SMP Thu Mar 5 21:49:36 UTC 2009 i686 GNU/Linux
I will also attach some files like dmesg, and logs if needed
Thanks in advance
--
ath5k locks up system in jaunty - "ath5k phy0: noise floor calibration timeout"
https:/
You received this bug notification because you are a direct subscriber
of the bug.
Status in The Bugzilla Bug Tracking System: Invalid
Status in The Linux Kernel: Confirmed
Status in “linux” source package in Ubuntu: Triaged
Status in Fedora: Confirmed
Bug description:
After upgrading to jaunty I started experiencing frequent system/x server freezes.
Happens all of a sudden with X session completely frozen with no keys working, including SysRq. Hard reboot is necessary.
It is hard to tell what is the reason. Tried to examine the logs - doesn't give me a clue.
There are a number of suspicious entries in the /var/log/dmesg* though
All of them except for the current and the oldest ones are all ENDING with this:
vmap allocation failed: use vmalloc=<size> to increase size.
Like:
~$ zgrep 'vmap' /var/log/dmesg* -A5
/var/log/dmesg.0:[ 35.911114] vmap allocation failed: use vmalloc=<size> to increase size.
/var/log/
/var/log/
/var/log/
Also I can recall that my memory icon in the gnome-system-
uname -a
Linux jenshen 2.6.28-8-generic #28-Ubuntu SMP Thu Mar 5 21:49:36 UTC 2009 i686 GNU/Linux
I will also attach some files like dmesg, and logs if needed
Thanks in advance