Bug#687515: Coredumped after wakeup from suspend, mentioning ifconfig
Hello Ben, thanks for taking the time to look into this. This special bug has happened alltogether two times. The one time I have reported this and a day later (friday). Then I upgraded net-tools to unstable since this was mentioned in the bugreport. After that I had this coredump no more. But it is only two days since then this is not finally, I guess. For configuring the network I use wicd-client. I only have xfce installed on this machine, so wicd-client is about the only usable gui for configuring wlan. I had a similar problem with this machine, again related to suspend. Don't know if it is related or not, but I'll describe it anyway. When putting the machine to sleep via closing the lid then every two days or so the machine used to freeze instead of going to sleep. I then had to reopen the lid and was presented with an unresponsive X-windows. Mouse was working, keyboard was almost dead except the commands like switching to console. Had to press ctrl-alt-f1 to reboot. I've described this in http://forums.debian.net/viewtopic.php?f=5t=83462;. At this time I had KDE running on the machine, which I then removed and switched to xfce. Which did not help. Then I configured the energy settings so that pressing the power-button performed the suspend to ram. Since then I no longer have the problem of freezing before suspend. But now the coredump after wakeup appeared. Sort of trading cholera for measles... Since this seems to be related to networking: I often use different wlan networks. So it can happen that I put the maching to sleep when connected with wlan a, resume when wlan a is no longer present. Or I put it to sleep and at the same time turn of my own mobile hotspot, so wlan is disappearing at this moment. Anyway, if there is anything I can do then contact me. Yours, Gunnar -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5056f0bf.1080...@gunnarstahl.org
Bug#622753: ath9k: Connection over wlan slows down and dies
Hi Ben, since sunday I am running kernel 2.6.38-2-amd64 (uname -a) (dselect version 2.6.38-5). The wlan module works now almost perfect. The almost is due to the fact that connection the machine to the android hotspot somehow fails. But all other hotspots I used until now work as expected. Huge thank-you from me! Yt, Gunnar Am 17.05.2011 05:45, schrieb Ben Hutchings: On Fri, 2011-04-15 at 15:52 +0800, Adrian Chadd wrote: On 15 April 2011 12:00, Ben Hutchingsb...@decadent.org.uk wrote: [...] https://bugzilla.kernel.org/show_bug.cgi?id=31452 Thanks, I've set our bug tracker to follow that bug. Has it been established that it's the same bug though? I had a brief read of that and I'm not so sure. There's so many things that could impact TX throughput. I don't have this problem on FreeBSD on my AR9285 NICs and I've ported almost all of the (non-power saving) related code from ath9k. They happily sit at the expected TX/RX speeds in 11g and 11n modes. Is someone who is experiencing the problem able to do some kernel version bisecting between the known good and known bad kernel? The bug fix from the report on Bugzilla has been included in stable release 2.6.38.5 and Debian's version 2.6.38-5. Does this version fix the problem for you? Ben. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dd2c8ae.3090...@gunnarstahl.org
Bug#622753: linux-image-2.6.38-2-amd64: Connection over wlan slows down and dies
Package: linux-2.6 Version: 2.6.38-3 Severity: important Since linux-image-2.6.38-2-amd64 the wlan connections on this machine is 1) slow to connection and 2) slows down to a crawl and 3) dies after some seconds / mintes and becomes completely unusable. Connecting over standard eth0 makes no problems at all. Only the wlan is affected. Booting the same machine again with linux-image-2.6.32-5-amd64 turns the wlan back to normal again. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: ASUSTeK Computer Inc. product_name: UL30A product_version: 1.0 chassis_vendor: ASUSTeK Computer Inc. chassis_version: 1.0 bios_vendor: American Megatrends Inc. bios_version: 211 board_vendor: ASUSTeK Computer Inc. board_name: UL30A board_version: 1.0 ** Network interface configuration: auto lo iface lo inet loopback ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub [8086:2a40] (rev 07) Subsystem: ASUSTeK Computer Inc. Device [1043:1c47] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0 Capabilities: access denied Kernel driver in use: agpgart-intel 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1862] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 28 Region 0: Memory at fe40 (64-bit, non-prefetchable) [size=4M] Region 2: Memory at d000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at dc00 [size=8] Expansion ROM at unassigned [disabled] Capabilities: access denied Kernel driver in use: i915 00:02.1 Display controller [0380]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a43] (rev 07) Subsystem: ASUSTeK Computer Inc. Device [1043:1862] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Region 0: Memory at fe80 (64-bit, non-prefetchable) [size=1M] Capabilities: access denied 00:1a.0 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 03) (prog-if 00 [UHCI]) Subsystem: ASUSTeK Computer Inc. Device [1043:1c47] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 16 Region 4: I/O ports at d880 [size=32] Capabilities: access denied Kernel driver in use: uhci_hcd 00:1a.1 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] (rev 03) (prog-if 00 [UHCI]) Subsystem: ASUSTeK Computer Inc. Device [1043:1c47] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin B routed to IRQ 21 Region 4: I/O ports at d800 [size=32] Capabilities: access denied Kernel driver in use: uhci_hcd 00:1a.2 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 [8086:2939] (rev 03) (prog-if 00 [UHCI]) Subsystem: ASUSTeK Computer Inc. Device [1043:1c47] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin D routed to IRQ 19 Region 4: I/O ports at d480 [size=32] Capabilities: access denied Kernel driver in use: uhci_hcd 00:1a.7 USB Controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 [8086:293c] (rev 03) (prog-if 20 [EHCI]) Subsystem: ASUSTeK Computer Inc. Device [1043:1c47] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR-
