[Bug 472150] Re: Unknown; returned to PC to find crash dialog.
** Attachment added: "AlsaDevices.txt" http://launchpadlibrarian.net/35002757/AlsaDevices.txt ** Attachment added: "AplayDevices.txt" http://launchpadlibrarian.net/35002758/AplayDevices.txt ** Attachment added: "ArecordDevices.txt" http://launchpadlibrarian.net/35002759/ArecordDevices.txt ** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/35002760/BootDmesg.txt ** Attachment added: "Card0.Amixer.values.txt" http://launchpadlibrarian.net/35002761/Card0.Amixer.values.txt ** Attachment added: "Card0.Codecs.codec.0.txt" http://launchpadlibrarian.net/35002762/Card0.Codecs.codec.0.txt ** Attachment added: "Card0.Codecs.codec.3.txt" http://launchpadlibrarian.net/35002763/Card0.Codecs.codec.3.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/35002764/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/35002765/Dependencies.txt ** Attachment added: "IwConfig.txt" http://launchpadlibrarian.net/35002766/IwConfig.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/35002767/Lspci.txt ** Attachment added: "Lsusb.txt" http://launchpadlibrarian.net/35002768/Lsusb.txt ** Attachment added: "OopsText.txt" http://launchpadlibrarian.net/35002769/OopsText.txt ** Attachment added: "PciMultimedia.txt" http://launchpadlibrarian.net/35002770/PciMultimedia.txt ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/35002771/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/35002772/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/35002773/ProcModules.txt ** Attachment added: "RfKill.txt" http://launchpadlibrarian.net/35002775/RfKill.txt ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/35002776/UdevDb.txt ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/35002777/UdevLog.txt -- Unknown; returned to PC to find crash dialog. https://bugs.launchpad.net/bugs/472150 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 472150] [NEW] Unknown; returned to PC to find crash dialog.
Public bug reported: May have been result of resume from suspend. ProblemType: KernelOops Annotation: Your system might become unstable now and might need to be restarted. Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mikegerwitz 2349 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'NVidia'/'HDA NVidia at 0xf9e78000 irq 21' Mixer name : 'Nvidia MCP78 HDMI' Components : 'HDA:10ec0888,14627374,0011 HDA:10de0002,10de0101,0010' Controls : 39 Simple ctrls : 21 Date: Mon Nov 2 06:51:19 2009 DistroRelease: Ubuntu 9.10 Failure: oops HibernationDevice: RESUME=UUID=68faba21-32e6-475d-97c2-b07d840c0bdd MachineType: MSI MS-7374 NonfreeKernelModules: nvidia Package: linux-image-2.6.31-14-generic 2.6.31-14.48 ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.31-14-generic root=UUID=70fd3f0d-126c-4472-bb56-69748fc4aeac ro quiet splash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic RelatedPackageVersions: linux-backports-modules-2.6.31-14-generic N/A linux-firmware 1.24 SourcePackage: linux Tags: kernel-oops Title: [173987.126379] [ cut here ] Uname: Linux 2.6.31-14-generic x86_64 WifiSyslog: dmi.bios.date: 01/18/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.4 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7374 dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.4:bd01/18/2009:svnMSI:pnMS-7374:pvr1.0:rvnMSI:rnMS-7374:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: MS-7374 dmi.product.version: 1.0 dmi.sys.vendor: MSI ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops kernel-oops -- Unknown; returned to PC to find crash dialog. https://bugs.launchpad.net/bugs/472150 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 350065] Re: usb ports randomly shut off Jaunty beta
My motherboard came with additional USB ports that may be connected optionally. I removed it on the 19th after reading the above posts, and I have not had any problems since. While I'd like to give it a bit more time, it does seem to hint at a hardware issue. When I have the time I will attempt to see if it is simply the USB header on the motherboard that is causing the problem, or if the problem occurs regardless of which header it is connected to. I do still have my case's USB ports connected to the motherboard without problems. For those who do have USB ports on their case (or any other external USB ports), try disconnecting them and see if it resolves the issue. If so, try connecting it to a different header. Seeing as how this problem occurred daily for myself, this is a huge improvement. I haven't had to reboot since. -- usb ports randomly shut off Jaunty beta https://bugs.launchpad.net/bugs/350065 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 350065] Re: usb ports randomly shut off Jaunty beta
I would also like to add that it seems the issue is recurring more often. I cannot go an hour without the problem. This is a very severe issue - I'm unable to use my Ubuntu box productively and find myself spending much of my time on my work-issued Windows PC, which lacks a vast majority of the tools I need more my development. When using a KVM switch to switch between my work and home PCs, the mouse first goes, then the keyboard. When switching to the Windows PC, they're re-activated (re-powered). Switching back, no power. The USB mouse that was not connected to the KVM switch continues to operate properly. Previous to the KVM switch being installed, the USB mouse attached directly to the computer would have the same issue. -- usb ports randomly shut off Jaunty beta https://bugs.launchpad.net/bugs/350065 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 350065] Re: usb ports randomly shut off Jaunty beta
Most recent nVidia drivers (185.18.14) does not solve the issue. -- usb ports randomly shut off Jaunty beta https://bugs.launchpad.net/bugs/350065 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 350065] Re: usb ports randomly shut off Jaunty beta
I have also been experiencing this problem since upgrading to Jaunty. My keyboard and mouse are attached through the same USB receiver. The mouse will stop responding, but the keyboard will continue to work. I did notice, however, that the multimedia keys on the keyboard no longer respond after the occurrence. lsusb just hangs - it cannot be killed with Ctrl+C. dmesg shows usb disconnect. Unplugging the device and plugging it back in will result in the keyboard being unresponsive as well. Connecting a new mouse is useless - the device does not receive power. However, connecting my mini USB bluetooth dongle does receive power and is recognized by the OS. This issue occurs seemingly randomly and forces me to use a PS/2 mouse - incredibly frustrating. Anyway, prepare for a buttload of information. -- $ lsusb Bus 004 Device 002: ID 046d:c505 Logitech, Inc. Cordless Mouse+Keyboard Receiver Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub -- $ lsusb -v r...@mikegerwitz-pc:/home/mikegerwitz# lsusb -v Bus 004 Device 002: ID 046d:c505 Logitech, Inc. Cordless Mouse+Keyboard Receiver Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x046d Logitech, Inc. idProduct 0xc505 Cordless Mouse+Keyboard Receiver bcdDevice 17.11 iManufacturer 1 Logitech iProduct2 USB Receiver iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 59 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 98mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 1 Keyboard iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.10 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 63 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 10 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 2 Mouse iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.10 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 190 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 10 Device Status: 0x (Bus Powered) [...] -- $ lshw -short H/W path Device Class Description === system MS-7374 /0 bus MS-7374 /0/0memory 64KiB BIOS /0/3processor AMD Phenom(tm) 9950 Quad-Core Processor /0
[Bug 352046] Re: Notebook remix unusable on EEE PC 900 because the menu is too slow
Confirmed also on the Eee PC 900. Cursor is jumpy and slow when hovering over icons in netbook launcher. Compiz does work but there are display issues (gnome panel does not display, tray icons display only on update, windows disappear). Have not yet taken the time to explore other applications outside the launcher. -- Notebook remix unusable on EEE PC 900 because the menu is too slow https://bugs.launchpad.net/bugs/352046 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 200500] Re: mac80211: WLAN losing connection: No ProbeResp
When I first commented on this bug report, I thought that this was some type of kernel/driver bug. Apparently it's not. This message is consistent with when my router seems to go down, as I found out when a friend using Windows experienced a disconnect at the same time while using my wireless connection. My simple solution: use NetworkManager. I had disabled it as it was buggy during the Intrepid RC releases, but now it works like a charm and immediately reconnects me once the router becomes available again after this error, as you can see below: [337749.729069] wlan0: No ProbeResp from current AP 00:15:e9:76:1a:ee - assume out of range [337750.585205] wlan0: authenticate with AP 00:15:e9:76:1a:ee -- mac80211: WLAN losing connection: No ProbeResp https://bugs.launchpad.net/bugs/200500 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 200500] Re: mac80211: WLAN losing connection: No ProbeResp
I do not think that this fix will be applied in future kernels---I'm not even entirely comfortable applying it to my kernel. Having to allow for response times 50x slower than normal is hardly a "fix". As far as I've seen in this report, the problem hasn't been found. I've tested one of the most recent kernels to date and the problem still exists. So there's no way in saying how long it'll take. So I'd say try compiling the kernel. It's not too difficult to do, just confusing at first. -- mac80211: WLAN losing connection: No ProbeResp https://bugs.launchpad.net/bugs/200500 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 200500] Re: mac80211: WLAN losing connection: No ProbeResp
After attempting what was stated in my previous message (modifying the monitoring interval to "100 * HZ" and recompiling the kernel), I have not received the error. My PC has been on since my last post and my net has not gone down. Speeds are excellent - above what I thought my max was. I see no other problems. I also noticed that the same error is happening on another computer of mine, where it previously didn't. It may be attributed to a new kernel version (2.6.25, while it was previously using 2.6.24). Therefore, I do not think this problem lies within the rt61* drivers. It's a good fix until others figure out a more effective solution. Hope it helps everyone else. -- mac80211: WLAN losing connection: No ProbeResp https://bugs.launchpad.net/bugs/200500 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 200500] Re: mac80211: WLAN losing connection: No ProbeResp
I am not using Ubuntu (Gentoo, vanilla sources, kernel 2.6.27), however I'm having the same problem, so hopefully this information will help. I do not use NetworkManager (it didn't handle my wireless properly), so that is not the problem. I searched the driver source for the phrase, but could not find it anywhere - does anyone know where this error message originates? grep -rl "ProbeResp" ./ I used the above command to locate any strings within all files in the source directory and found nothing of use. However, using the above command to search for "No ProbeResp" in the kernel source directory (2.6.27) produced the following file, in which I found the error message: /usr/src/linux/net/mac80211/mlme.c (line 1059) Above, the following link was referenced: http://rt2x00.serialmonkey.com/phpBB/viewtopic.php?f=5&t=2081&p=30312&hilit=No+ProbeResp+from+current+AP#p30312 However, the file it references does not appear to exist within kernel 2.6.27. The file you are looking for to modify IEEE80211_MONITORING_INTERVAL is the above file (mlme.c). This is the constant that is referenced when a timeout is determined. I'll set it to a higher value (default seems to be "2 * HZ"), recompile, and post back with any success. Either way, it'll only be a temporary fix - we'll need to take it up with serialmonkey to figure out the real problem. Hope this helps. I use the driver rt61pci === dmesg | tail [41884.647257] wlan0: authenticate with AP 00:15:e9:76:1a:ee [41884.658208] wlan0: authenticated [41884.658208] wlan0: associate with AP 00:15:e9:76:1a:ee [41884.668257] wlan0: RX ReassocResp from 00:15:e9:76:1a:ee (capab=0x431 status=0 aid=5) [41884.668257] wlan0: associated [41892.844239] wlan0: no IPv6 routers present [68822.729255] wlan0: No ProbeResp from current AP 00:15:e9:76:1a:ee - assume out of range === === lspci | grep RT 01:07.0 Network controller: RaLink RT2561/RT61 802.11g PCI === === uname -a Linux mikegerwitz-pc 2.6.27-rc4-mikegerwitz #1 SMP Sat Aug 30 20:39:45 EDT 2008 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 5400+ AuthenticAMD GNU/Linux === Wireless works fine until this error occurs, seemingly randomly. This occurs both when the connection is in use and idle. To restart the connection, I sometimes have to remove the kernel module and re-modprobe it, then restart the interface: === $ rmmode rt61pci $ modprobe rt61pci $ /etc/init.d/net.wlan0 restart === The connection then works properly again until the next error, as pasted above from dmesg. -- mac80211: WLAN losing connection: No ProbeResp https://bugs.launchpad.net/bugs/200500 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 131973] Re: desktop random freezes in feisty
Update: I left my laptop idle at the login screen (GDM) and, sure enough, it froze. Therefore no window manager is a problem. I did not experience this problem with previous versions of Ubuntu. -- desktop random freezes in feisty https://bugs.launchpad.net/bugs/131973 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 131973] Re: desktop random freezes in feisty
Excuse me, I posted specs for the wrong computer ;) This occurs on my Toshiba Satellite A10-S169, which uses an onboard Intel graphics card. The computer using Gutsy with the nvidia drivers runs very smoothly with no freezing. -- desktop random freezes in feisty https://bugs.launchpad.net/bugs/131973 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 131973] Re: desktop random freezes in feisty
I do not believe this problem is caused by compiz. I experienced random lockups both with compiz enabled and disabled. I have an nVidia graphics card and use the restricted drivers. No specific action causes the freeze - it's happened while I was in the middle of typing, while the computer was left idle (I originally thought that was the problem), while no programs at all were running, etc. This occurred in Gnome, using Gutsy. I have not tried any other window managers. -- desktop random freezes in feisty https://bugs.launchpad.net/bugs/131973 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
