Bug#673511: brcmsmacs: mode IBSS not implemented for Broadcom Wirless LAN controllers
Package: linux-2.6 Version: 3.2.17-1 Severity: normal Tags: upstream Dear Debian folks, the `brcmsmac` [1] module does not support IBSS [2] needed to create ad-hoc networks [3][4][5]. This prevents for example using shared WLAN connections from smart phones. `/var/log/syslog` contains the following messages. ieee80211 phy0: brcms_ops_bss_info_changed: qos enabled: false (implement) ieee80211 phy0: brcmsmac: brcms_ops_bss_info_changed: disassociated ieee80211 phy0: brcms_ops_bss_info_changed: arp filtering: enabled false, count 1 wpa_supplicant[2209]: nl80211: Failed to set interface into IBSS mode wpa_supplicant[2209]: Association request to the driver failed 1. Would it be better to use the module `b43` by default which is supposed to support all modes [3]? 2. If support for IBSS in `brcmsmac` is implemented, could that be backported to Linux 3.2? For interested people, Broadcom’s proprietary `wl` driver supports IBSS too. The WLAN controller in this system is identified by `lspci` as 08:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller (rev 01) and Broadcom’s proprietary driver `wl` identifies the following. wlan0: Broadcom BCM4727 802.11 Hybrid Wireless Controller 5.100.82.112 Thanks, Paul [1] http://wiki.debian.org/brcm80211 [2] https://en.wikipedia.org/wiki/Independent_Basic_Service_Set#Independent_basic_service_set_.28IBSS.29 [3] http://linuxwireless.org/en/users/Drivers/b43#Comparison_of_recent_drivers [4] http://linuxwireless.org/en/users/Drivers/ [5] http://wireless.kernel.org/en/users/Drivers/brcm80211 signature.asc Description: This is a digitally signed message part
Bug#673511: brcmsmacs: mode IBSS not implemented for Broadcom Wirless LAN controllers
On Sat, May 19, 2012 at 10:26:37AM +0200, Paul Menzel wrote: Package: linux-2.6 Version: 3.2.17-1 Severity: normal Tags: upstream Dear Debian folks, the `brcmsmac` [1] module does not support IBSS [2] needed to create ad-hoc networks [3][4][5]. This prevents for example using shared WLAN connections from smart phones. `/var/log/syslog` contains the following messages. ieee80211 phy0: brcms_ops_bss_info_changed: qos enabled: false (implement) ieee80211 phy0: brcmsmac: brcms_ops_bss_info_changed: disassociated ieee80211 phy0: brcms_ops_bss_info_changed: arp filtering: enabled false, count 1 wpa_supplicant[2209]: nl80211: Failed to set interface into IBSS mode wpa_supplicant[2209]: Association request to the driver failed 1. Would it be better to use the module `b43` by default which is supposed to support all modes [3]? 2. If support for IBSS in `brcmsmac` is implemented, could that be backported to Linux 3.2? What is exact model of your adapter (lspci -nn)? I have adapter 14e4:4727 model in my laptop, that is only supported by brcmsmac. -- 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/20120519110922.GA9231@tiikeri.vuoristo.local
Bug#673522: unshare NEWNET + using sockets from before: unregister_netdevice: waiting for lo to become free. Usage count = 2
Package: linux-image-3.2.0-2-amd64
Version: 3.2.16-1
Hi,
CLONE_NEWNET is still buggy (i found random reports with the same error message
from 2010).
uname: Linux * 3.2.0-2-amd64 #1 SMP Mon Apr 30 05:20:23 UTC 2012 x86_64
GNU/Linux
See the attached example.
I don't think it matters much how the socket is used: just create the socket
before the unshare and use it somehow - listen() after unshare() triggered it
too.
The kernel starts spamming the message after the program is terminated.
Also the port is not reachable from the outside - although i admit i couldn't
find docs mentioning this is supported, but it really should be.
(Given that struct net is part of struct sock(common) this shouldn't be hard)
I could reproduce it in virtualbox with rescue mode from
http://cdimage.debian.org/cdimage/wheezy_di_alpha1/amd64/iso-cd/debian-wheezy-DI-a1-amd64-netinst.iso
- when i started it a second time the process would even hang for some time
(not killable).
logs look like this:
[ 796.444219] unregister_netdevice: waiting for lo to become free. Usage count
= 2
[ 806.684213] unregister_netdevice: waiting for lo to become free. Usage count
= 2
[ 816.924212] unregister_netdevice: waiting for lo to become free. Usage count
= 2
[ 827.164217] unregister_netdevice: waiting for lo to become free. Usage count
= 2
[ 837.408237] unregister_netdevice: waiting for lo to become free. Usage count
= 2
[ 847.648216] unregister_netdevice: waiting for lo to become free. Usage count
= 2
[ 857.888219] unregister_netdevice: waiting for lo to become free. Usage count
= 2
[ 868.128224] unregister_netdevice: waiting for lo to become free. Usage count
= 2
[ 878.368221] unregister_netdevice: waiting for lo to become free. Usage count
= 2
[ 888.608215] unregister_netdevice: waiting for lo to become free. Usage count
= 2
#define _GNU_SOURCE
#include sched.h
#include stdio.h
#include stdlib.h
#include strings.h
#include sys/socket.h
#include sys/types.h
#include netinet/in.h
#include netinet/ip.h
int main() {
int listenfd, acceptfd, connectfd;
struct sockaddr_in addr;
socklen_t addrlen = sizeof(addr);
puts(newnet + listen/connect test);
if (-1 == (listenfd = socket(AF_INET, SOCK_STREAM, 0))) { perror(socket failed); abort(); }
if (0 != listen(listenfd, 1)) { perror(listen failed); abort(); }
if (0 != unshare(CLONE_NEWNET)) { perror(unshare failed); abort(); }
if (0 != getsockname(listenfd, (struct sockaddr*) addr, addrlen)) { perror(getsockname failed); }
if (-1 == (connectfd = socket(AF_INET, SOCK_STREAM, 0))) { perror(socket failed); abort(); }
if (0 == connect(connectfd, (struct sockaddr*) addr, addrlen)) {
puts(successful connect - something is wrong here);
} else {
perror(connect failed as expected);
}
close(connectfd);
printf(listening on 0.0.0.0:%i\n, (int) addr.sin_port);
if (-1 == (acceptfd = accept(listenfd, NULL, NULL))) { perror(accept failed); abort(); }
{
char buf[1024];
int len = read(acceptfd, buf, sizeof(buf)-1);
if (len 0) { perror(read failed); abort(); }
buf[len] = 0;
printf(received: '%s'\n, buf);
write(acceptfd, buf, len);
close(acceptfd);
}
puts(done.);
}
Bug#673511: brcmsmacs: mode IBSS not implemented for Broadcom Wirless LAN controllers
Am Samstag, den 19.05.2012, 14:09 +0300 schrieb Touko Korpela: On Sat, May 19, 2012 at 10:26:37AM +0200, Paul Menzel wrote: Package: linux-2.6 Version: 3.2.17-1 Severity: normal Tags: upstream the `brcmsmac` [1] module does not support IBSS [2] needed to create ad-hoc networks [3][4][5]. This prevents for example using shared WLAN connections from smart phones. `/var/log/syslog` contains the following messages. ieee80211 phy0: brcms_ops_bss_info_changed: qos enabled: false (implement) ieee80211 phy0: brcmsmac: brcms_ops_bss_info_changed: disassociated ieee80211 phy0: brcms_ops_bss_info_changed: arp filtering: enabled false, count 1 wpa_supplicant[2209]: nl80211: Failed to set interface into IBSS mode wpa_supplicant[2209]: Association request to the driver failed 1. Would it be better to use the module `b43` by default which is supposed to support all modes [3]? 2. If support for IBSS in `brcmsmac` is implemented, could that be backported to Linux 3.2? What is exact model of your adapter (lspci -nn)? $ lspci -nn […] 08:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller [14e4:4727] (rev 01) […] I have adapter 14e4:4727 model in my laptop, that is only supported by brcmsmac. This system seems to have the same model. Thanks, Paul signature.asc Description: This is a digitally signed message part
Re: Bug#673391: Updates to be2net driver for Debian 7.0
On Fri, 2012-05-18 at 10:39 -0700, sarveshwar.ba...@emulex.com wrote: I am attaching the patches (61) to update the be2net driver. All patches have already been accepted and applied to net-next. I have applied and tested these patches on debian linux-source-3.2_3.2.17-1_all.deb source package. Please apply them to you source tree. 1/61 'sweep the floors and convert some .get_drvinfo routines to strlcpy' (commit 68aad78c5023b8aa82da99b47f9d8cf40e8ca453 upstream) applied to many drivers; please note in the patch header that you've filtered it to just be2net. Same for 27/61 'netdev: make net_device_ops const'. 17/61 'net: make vlan ndo_vlan_rx_[add/kill]_vid return error value' (commit 8e586137e6b63af1e881b328466ab5ffbe562510 upstream) is wrong: CC [M] drivers/net/ethernet/emulex/benet/be_main.o drivers/net/ethernet/emulex/benet/be_main.c:3186:2: warning: initialization from incompatible pointer type [enabled by default] drivers/net/ethernet/emulex/benet/be_main.c:3186:2: warning: (near initialization for ‘be_netdev_ops.ndo_vlan_rx_add_vid’) [enabled by default] drivers/net/ethernet/emulex/benet/be_main.c:3187:2: warning: initialization from incompatible pointer type [enabled by default] drivers/net/ethernet/emulex/benet/be_main.c:3187:2: warning: (near initialization for ‘be_netdev_ops.ndo_vlan_rx_kill_vid’) [enabled by default] You can't go changing the types of netdev operations in a backport. You'll also need to adjust 24/61 'be2net: fix be_vlan_add/rem_vid' (commit 80817cbf5ac13da76f3ee2b9259f26c09b385e84 upstream) to apply without the type change. 31/61 'ethtool: Null-terminate filename passed to ethtool_ops::flash_device' (commit 786f528119722f564a22ad953411374e06116333 upstream) is wrong; by filtering to only drivers/net/emulex/benet/ you've lost the essential part of it! Actually that fix should maybe go to stable, not just Debian. 61/61 'Updating driver version number' isn't upstream as you claimed, but I don't have any objection as long as you explain it in the patch header. Please can you use the script 'git-format-patch-for-backport' http://anonscm.debian.org/viewvc/kernel/people/benh/git-format-patch-for-backport?revision=HEADview=co to generate patches with the upstream commit IDs included. This is a wrapper for 'git format-patch' and takes all the same arguments. Ben. -- Ben Hutchings Experience is directly proportional to the value of equipment destroyed. - Carolyn Scheppner signature.asc Description: This is a digitally signed message part
Bug#619381: linux-image-2.6.38-1-amd64: usb mass storage error causes kernel panic
unarchive 631187 633890 634681 636103 636263 637965 642043 forcemerge 631187 619381 quit Michal Suchanek wrote: Excerpts from Ben Hutchings's message of Thu Mar 24 06:38:05 +0100 2011: On Wed, 2011-03-23 at 13:35 +0100, Michal Suchanek wrote: 1) Attach a SATA drive to a SATA/USB bridge. 2) dd if=/dev/urandom of=/dev/sdf bs=4k 3) detach the drive drom the bridge Not a very good idea... The SATA connectors aren't secured in any way so that's what happens in practice. Thanks again for a pleasant report. Closing optimistically. As usual, confirmation either way about the fix would be useful. Regards, Jonathan -- 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/20120519163307.GA26509@burratino
Uploading linux-2.6 (3.2.18-1)
I intend to release Linux 3.2.18 on Sunday, and then upload linux-2.6 version 3.2.18-1 to unstable. The upstream changes include quite a few stability and security fixes, but this update will be much smaller than 3.2.17. Debian changes include some new hardware support. No ABI change should be necessary. Can 3.2.17-1 be expedited into testing? I don't believe we've had any regressions reported. Ben. -- Ben Hutchings Experience is directly proportional to the value of equipment destroyed. - Carolyn Scheppner signature.asc Description: This is a digitally signed message part
Re: Uploading linux-2.6 (3.2.18-1)
Ben Hutchings b...@decadent.org.uk (19/05/2012): I intend to release Linux 3.2.18 on Sunday, and then upload linux-2.6 version 3.2.18-1 to unstable. The upstream changes include quite a few stability and security fixes, but this update will be much smaller than 3.2.17. Debian changes include some new hardware support. No ABI change should be necessary. Good (no ABI changes). Can 3.2.17-1 be expedited into testing? I don't believe we've had any regressions reported. I'll look into making that happen in the next hour. While I'm at it, thanks for letting us know about all those uploads. That's really appreciated. Mraw, KiBi. signature.asc Description: Digital signature
Processed: severity of 673511 is wishlist
Processing commands for cont...@bugs.debian.org: severity 673511 wishlist Bug #673511 [linux-2.6] brcmsmacs: mode IBSS not implemented for Broadcom Wirless LAN controllers Severity set to 'wishlist' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 673511: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673511 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.13374519896084.transcr...@bugs.debian.org
Bug#673511: brcmsmacs: mode IBSS not implemented for Broadcom Wirless LAN controllers
On Sat, 2012-05-19 at 10:26 +0200, Paul Menzel wrote: Package: linux-2.6 Version: 3.2.17-1 Severity: normal Tags: upstream Dear Debian folks, the `brcmsmac` [1] module does not support IBSS [2] needed to create ad-hoc networks [3][4][5]. This prevents for example using shared WLAN connections from smart phones. [...] That depends on the phone - my phone running CyanogenMod 7.1 (Android 2.3) shares in infrastructure (AP) mode, not IBSS. Anyway, I agree this should be fixed but it's already on the to-do list at http://linuxwireless.org/en/users/Drivers/brcm80211 and there's nothing we can reasonably do about it in Debian. Ben. -- Ben Hutchings Experience is directly proportional to the value of equipment destroyed. - Carolyn Scheppner signature.asc Description: This is a digitally signed message part
Re: firmware loading failure for AR3011 (0cf3:3000 or 0cf3:3005 ?)
James Leddy writes[1]: This turned out to be a problem with the firmware. It should be fixed by this modification to the firmware: http://comments.gmane.org/gmane.linux.kernel/1262485 Reassigning to firmware-atheros, but keeping the libmtp bug too in case an appropriate Breaks ends up being needed to handle upgrades. Thanks for your help, Jonathan [1] https://bugzilla.kernel.org/show_bug.cgi?id=27402 It's been months since I've been waiting for this patch to be merged upstream so that it can move to debian, but that hasn't happened. Since March 6th (date that the patch was posted), there hasn't been any related merged into the linux-firmware git repository: http://git.kernel.org/?p=linux/kernel/git/firmware/linux-firmware.git;a=shortlog I'm unsure how apply and test this git binary patch... Andres -- 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/CAH=dyrhpnf5pekxzquuyqoizto2sosfvlabqawdikswm-s8...@mail.gmail.com
Bug#673522: unshare NEWNET + using sockets from before: unregister_netdevice: waiting for lo to become free. Usage count = 2
On Sat, 2012-05-19 at 13:03 +0200, Stefan Bühler wrote: Package: linux-image-3.2.0-2-amd64 Version: 3.2.16-1 Hi, CLONE_NEWNET is still buggy (i found random reports with the same error message from 2010). uname: Linux * 3.2.0-2-amd64 #1 SMP Mon Apr 30 05:20:23 UTC 2012 x86_64 GNU/Linux See the attached example. I don't think it matters much how the socket is used: just create the socket before the unshare and use it somehow - listen() after unshare() triggered it too. The kernel starts spamming the message after the program is terminated. [...] I don't think this has been fixed upstream, but please test the latest stable version (Linux 3.3.6, available in experimental) and then report this upstream (net...@vger.kernel.org). Ben. -- Ben Hutchings Experience is directly proportional to the value of equipment destroyed. - Carolyn Scheppner signature.asc Description: This is a digitally signed message part
Processed: reassign 673522 to src:linux-2.6, tagging 673522
Processing commands for cont...@bugs.debian.org: reassign 673522 src:linux-2.6 3.2.16-1 Bug #673522 [linux-image-3.2.0-2-amd64] unshare NEWNET + using sockets from before: unregister_netdevice: waiting for lo to become free. Usage count = 2 Bug reassigned from package 'linux-image-3.2.0-2-amd64' to 'src:linux-2.6'. No longer marked as found in versions linux-2.6/3.2.16-1. Ignoring request to alter fixed versions of bug #673522 to the same values previously set Bug #673522 [src:linux-2.6] unshare NEWNET + using sockets from before: unregister_netdevice: waiting for lo to become free. Usage count = 2 Marked as found in versions linux-2.6/3.2.16-1. tags 673522 + upstream moreinfo Bug #673522 [src:linux-2.6] unshare NEWNET + using sockets from before: unregister_netdevice: waiting for lo to become free. Usage count = 2 Added tag(s) upstream and moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 673522: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673522 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.133745329112341.transcr...@bugs.debian.org
Bug#652678: Same problem with Fujitsu Siemens amilo pi2515
Hi, I'm running wheezy with the latest kernel (linux-image-3.2.0-2-686-pae 3.2.16-1) on a fujitsu siemens amilo pi2515. My /proc/bus/input/devices says: [...] I: Bus=0011 Vendor=0002 Product=0001 Version=0063 N: Name=PS/2 Logitech Wheel Mouse P: Phys=isa0060/serio4/input0 S: Sysfs=/devices/platform/i8042/serio4/input/input7 U: Uniq= H: Handlers=mouse0 event7 B: PROP=0 B: EV=7 B: KEY=7 0 0 0 0 0 0 0 0 B: REL=103 [...] Any hint? -- 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/4fb7ebab.9040...@anche.no
Bug#641749: firmware loading failure for AR3011 (0cf3:3000 or 0cf3:3005 ?)
On Sat, 2012-05-19 at 14:48 -0400, Andres Cimmarusti wrote: James Leddy writes[1]: This turned out to be a problem with the firmware. It should be fixed by this modification to the firmware: http://comments.gmane.org/gmane.linux.kernel/1262485 Reassigning to firmware-atheros, but keeping the libmtp bug too in case an appropriate Breaks ends up being needed to handle upgrades. Thanks for your help, Jonathan [1] https://bugzilla.kernel.org/show_bug.cgi?id=27402 It's been months since I've been waiting for this patch to be merged upstream so that it can move to debian, but that hasn't happened. Since March 6th (date that the patch was posted), there hasn't been any related merged into the linux-firmware git repository: http://git.kernel.org/?p=linux/kernel/git/firmware/linux-firmware.git;a=shortlog I'm unsure how apply and test this git binary patch... Costa, please re-send the patch as I never received it. Ben. -- Ben Hutchings Experience is directly proportional to the value of equipment destroyed. - Carolyn Scheppner signature.asc Description: This is a digitally signed message part
Bug#652678: Same problem with Fujitsu Siemens amilo pi2515
On Sat, 2012-05-19 at 20:51 +0200, stimiato wrote: Hi, I'm running wheezy with the latest kernel (linux-image-3.2.0-2-686-pae 3.2.16-1) on a fujitsu siemens amilo pi2515. [...] The original bug was fixed in Linux 3.2, so please open a new bug report. Ben. -- Ben Hutchings Experience is directly proportional to the value of equipment destroyed. - Carolyn Scheppner signature.asc Description: This is a digitally signed message part
Bug#604613: Status of this bug?
[Please always cc the bug address, i.e. reply to all.] On Sun, 2012-05-13 at 14:48 -0700, Paul Zimmerman wrote: On Monday, May 7, 2012 7:11 PM, Ben Hutchings b...@decadent.org.uk wrote: On Mon, 2012-05-07 at 14:51 -0700, Paul Zimmerman wrote: So what is happening with this bug? It seems to be the same thing that has broken what was perfectly working wifi on my laptop when I had Lenny installed. But upgrading to Squeeze so I could continue to get security updates has left me with no wireless connection unless I plug in an external device. It doesn't seem to have been marked as fixed, as it should not be if it is still present in the standard Squeeze kernel, but at the end of one of the responses it says a fix has been entered into the 2.6.36~rc5-1~experimental.1 kernel. [...] The bug log is at http://bugs.debian.org/604613 and there is no claim that it has been fixed. Can you test Linux 3.2 from testing/unstable/squeeze-backports? Then we can see whether it was fixed after Linux 2.6.32. and either report the bug upstream or try to find that fix. Well, I don't claim to understand the system, but in a page linked on this one (http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=11;bug=604613) it gives a series of reassigned reports, ending with: reassign 586995 linux-2.6 2.6.32-24 found 586995 linux-2.6/2.6.32-24 fixed 586995 2.6.36~rc5-1~experimental.1 thanks So it looks like the work on the bug was bounced around to various places, perhaps because the same problem was causing more than one bug report. The fixed line at the end would seem to mean that it was resolved, but put into the experimental kernel rather than the stable one issued to users. I reassigned a large number of bugs with a single control message, one of which happened to be this one. I also marked another bug fixed. As for the backported kernel, I did try that when I first upgraded and found the wifi was broken. It would not finish loading, but froze with a black screen when it tried to start the desktop. It seems to be a little _too_ unstable for me at this time. :) So I simply uninstalled it. But if it has been updated since early March, I can try it again and let you know if it works now. It's updated almost every week in unstable. I can't promise the graphics bug has been fixed though. Ben. -- Ben Hutchings Experience is directly proportional to the value of equipment destroyed. - Carolyn Scheppner signature.asc Description: This is a digitally signed message part
Bug#673496: Booting 3.2 kernel
OK, I went and looked through the logs from my attempt to use the backported 3.2 kernel. Even editing down to just the one boot by that kernel there is more than 50k of text for each. So, here are my best guesses at relevant excerpts. [from kern.log] May 18 09:19:22 Nomad kernel: imklog 4.6.4, log source = /proc/kmsg started. May 18 09:19:22 Nomad kernel: [ 0.00] Initializing cgroup subsys cpuset May 18 09:19:22 Nomad kernel: [ 0.00] Initializing cgroup subsys cpu May 18 09:19:22 Nomad kernel: [ 0.00] Linux version 3.2.0-0.bpo.1-686-pae (Debian 3.2.4-1~bpo60+1) (b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.5-8) ) #1 SMP Sat Feb 11 14:57:20 UTC 2012 ... May 18 09:19:22 Nomad kernel: [ 0.00] DMI: Everex Systems, Inc. Everex StepNote N Series/NM3500W, BIOS 1.0A-2A16-8A20 05/31/2006 ... May 18 09:19:22 Nomad kernel: [ 0.00] Kernel command line: BOOT_IMAGE=/vmlinuz-3.2.0-0.bpo.1-686-pae root=UUID=be9449b5-3502-4bbf-818d-075b4146147b ro quiet ... May 18 09:19:22 Nomad kernel: [ 0.285896] ACPI: bus type pnp registered May 18 09:19:22 Nomad kernel: [ 0.286048] pnp 00:00: [bus 00-ff] May 18 09:19:22 Nomad kernel: [ 0.286052] pnp 00:00: [io 0x0cf8-0x0cff] May 18 09:19:22 Nomad kernel: [ 0.286055] pnp 00:00: [io 0x-0x0cf7 window] May 18 09:19:22 Nomad kernel: [ 0.286058] pnp 00:00: [io 0x0d00-0x window] May 18 09:19:22 Nomad kernel: [ 0.286062] pnp 00:00: [mem 0x8000-0xfff7 window] May 18 09:19:22 Nomad kernel: [ 0.286148] pnp 00:00: Plug and Play ACPI device, IDs PNP0a03 (active) May 18 09:19:22 Nomad kernel: [ 0.286423] pnp 00:01: [dma 4] May 18 09:19:22 Nomad kernel: [ 0.286426] pnp 00:01: [io 0x-0x000f] May 18 09:19:22 Nomad kernel: [ 0.286429] pnp 00:01: [io 0x0081-0x008f] May 18 09:19:22 Nomad kernel: [ 0.286432] pnp 00:01: [io 0x00c0-0x00df] May 18 09:19:22 Nomad kernel: [ 0.286471] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active) May 18 09:19:22 Nomad kernel: [ 0.286483] pnp 00:02: [io 0x0070-0x0075] May 18 09:19:22 Nomad kernel: [ 0.286505] pnp 00:02: [irq 8] May 18 09:19:22 Nomad kernel: [ 0.286543] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active) May 18 09:19:22 Nomad kernel: [ 0.286573] pnp 00:03: [io 0x00f0-0x00ff] May 18 09:19:22 Nomad kernel: [ 0.286581] pnp 00:03: [irq 13] May 18 09:19:22 Nomad kernel: [ 0.286620] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active) May 18 09:19:22 Nomad kernel: [ 0.286648] pnp 00:04: [io 0x0061] May 18 09:19:22 Nomad kernel: [ 0.286686] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active) May 18 09:19:22 Nomad kernel: [ 0.286707] pnp 00:05: [mem 0x-0x0009] May 18 09:19:22 Nomad kernel: [ 0.286711] pnp 00:05: [mem 0x000e-0x000f] May 18 09:19:22 Nomad kernel: [ 0.286714] pnp 00:05: [mem 0xfee0-0xfee00fff] May 18 09:19:22 Nomad kernel: [ 0.286717] pnp 00:05: [mem 0xff38-0xff7f] May 18 09:19:22 Nomad kernel: [ 0.286720] pnp 00:05: [mem 0xfff8-0x] May 18 09:19:22 Nomad kernel: [ 0.286723] pnp 00:05: [mem 0xffb8-0xffbf] May 18 09:19:22 Nomad kernel: [ 0.286805] system 00:05: [mem 0x-0x0009] could not be reserved May 18 09:19:22 Nomad kernel: [ 0.286810] system 00:05: [mem 0x000e-0x000f] could not be reserved May 18 09:19:22 Nomad kernel: [ 0.286814] system 00:05: [mem 0xfee0-0xfee00fff] has been reserved May 18 09:19:22 Nomad kernel: [ 0.286818] system 00:05: [mem 0xff38-0xff7f] has been reserved May 18 09:19:22 Nomad kernel: [ 0.286824] system 00:05: [mem 0xfff8-0x] could not be reserved May 18 09:19:22 Nomad kernel: [ 0.286829] system 00:05: [mem 0xffb8-0xffbf] has been reserved May 18 09:19:22 Nomad kernel: [ 0.286833] system 00:05: Plug and Play ACPI device, IDs PNP0c01 (active) May 18 09:19:22 Nomad kernel: [ 0.286934] pnp 00:06: [io 0x0061-0x0063] May 18 09:19:22 Nomad kernel: [ 0.286937] pnp 00:06: [io 0x0065-0x006f] May 18 09:19:22 Nomad kernel: [ 0.286940] pnp 00:06: [io 0x0080] May 18 09:19:22 Nomad kernel: [ 0.286943] pnp 00:06: [io 0x0092] May 18 09:19:22 Nomad kernel: [ 0.286946] pnp 00:06: [io 0x00a8-0x00a9] May 18 09:19:22 Nomad kernel: [ 0.286949] pnp 00:06: [io 0x04d0-0x04d1] May 18 09:19:22 Nomad kernel: [ 0.286952] pnp 00:06: [io 0xfe10-0xfe11] May 18 09:19:22 Nomad kernel: [ 0.286954] pnp 00:06: [io 0xfe00] May 18 09:19:22 Nomad kernel: [ 0.286957] pnp 00:06: [io 0x4000-0x407f] May 18 09:19:22 Nomad kernel: [ 0.286960] pnp 00:06: [io 0x4100-0x411f] May 18 09:19:22 Nomad kernel: [ 0.287024] system 00:06: [io 0x04d0-0x04d1] has been reserved May 18 09:19:22 Nomad kernel: [ 0.287028] system 00:06: [io 0xfe10-0xfe11] has been reserved May 18 09:19:22 Nomad kernel: [ 0.287032] system 00:06: [io 0xfe00] has been reserved May 18 09:19:22 Nomad kernel: [ 0.287036]
Bug#671689: [regression 3.2-3.3.4] sata_sil (on sil 3512) hotplug broken again
Am 18.05.2012 22:32, schrieb Jonathan Nieder:
Please test the attached patch, for example following the instructions
from [1]. (Found at [2].) Thanks, Jonathan [1]
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official
or the corresponding page in the debian-kernel-handbook package [2]
http://thread.gmane.org/gmane.linux.ide/51860/focus=51881
[ 320.644432] ata5: exception Emask 0x10 SAct 0x0 SErr 0x1 action
0xe frozen
[ 320.644437] ata5: SError: { PHYRdyChg }
[ 320.69] ata5: hard resetting link
[ 321.368035] ata5: SATA link down (SStatus 0 SControl 310)
[ 326.368021] ata5: hard resetting link
[ 326.688028] ata5: SATA link down (SStatus 0 SControl 310)
[ 331.688034] ata5: hard resetting link
[ 332.008027] ata5: SATA link down (SStatus 0 SControl 310)
[ 332.008040] ata5.00: disabled
[ 332.008051] ata5: EH complete
[ 332.008060] ata5.00: detaching (SCSI 4:0:0:0)
[ 332.020060] sd 4:0:0:0: [sdc] Synchronizing SCSI cache
[ 332.020201] sd 4:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 332.020205] sd 4:0:0:0: [sdc] Stopping disk
[ 332.020213] sd 4:0:0:0: [sdc] START_STOP FAILED
[ 332.020215] sd 4:0:0:0: [sdc] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 424.275712] ata5: exception Emask 0x10 SAct 0x0 SErr 0x5 action
0xe frozen
[ 424.275718] ata5: SError: { PHYRdyChg CommWake }
[ 424.275731] ata5: hard resetting link
[ 429.980048] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 430.004251] ata5.00: ATA-8: VB0250EAVER, HPG0, max UDMA/100
[ 430.004254] ata5.00: 488397168 sectors, multi 0: LBA48 NCQ (depth 0/32)
[ 430.044200] ata5.00: configured for UDMA/100
[ 430.044209] ata5: EH complete
[ 430.044319] scsi 4:0:0:0: Direct-Access ATA VB0250EAVER
HPG0 PQ: 0 ANSI: 5
[ 430.044544] sd 4:0:0:0: [sdh] 488397168 512-byte logical blocks: (250
GB/232 GiB)
[ 430.044590] sd 4:0:0:0: [sdh] Write Protect is off
[ 430.044593] sd 4:0:0:0: [sdh] Mode Sense: 00 3a 00 00
[ 430.044613] sd 4:0:0:0: [sdh] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 430.065793] sdh: sdh1
[ 430.066060] sd 4:0:0:0: [sdh] Attached SCSI disk
[ 457.213039] ata5: exception Emask 0x10 SAct 0x0 SErr 0x1 action
0xe frozen
[ 457.213043] ata5: SError: { PHYRdyChg }
[ 457.213053] ata5: hard resetting link
[ 457.936036] ata5: SATA link down (SStatus 0 SControl 310)
[ 462.936071] ata5: hard resetting link
[ 463.256025] ata5: SATA link down (SStatus 0 SControl 310)
[ 468.256023] ata5: hard resetting link
[ 468.576029] ata5: SATA link down (SStatus 0 SControl 310)
[ 468.576042] ata5.00: disabled
[ 468.576054] ata5: EH complete
[ 468.576068] ata5.00: detaching (SCSI 4:0:0:0)
[ 468.577923] sd 4:0:0:0: [sdh] Synchronizing SCSI cache
[ 468.577975] sd 4:0:0:0: [sdh] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 468.577981] sd 4:0:0:0: [sdh] Stopping disk
[ 468.577993] sd 4:0:0:0: [sdh] START_STOP FAILED
[ 468.577995] sd 4:0:0:0: [sdh] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 488.174245] ata5: exception Emask 0x10 SAct 0x0 SErr 0x5 action
0xe frozen
[ 488.174251] ata5: SError: { PHYRdyChg CommWake }
[ 488.174264] ata5: hard resetting link
[ 493.880034] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 493.904203] ata5.00: ATA-8: VB0250EAVER, HPG0, max UDMA/100
[ 493.904206] ata5.00: 488397168 sectors, multi 0: LBA48 NCQ (depth 0/32)
[ 493.936239] ata5.00: configured for UDMA/100
[ 493.936249] ata5: EH complete
[ 493.936389] scsi 4:0:0:0: Direct-Access ATA VB0250EAVER
HPG0 PQ: 0 ANSI: 5
[ 493.936625] sd 4:0:0:0: [sdh] 488397168 512-byte logical blocks: (250
GB/232 GiB)
[ 493.936692] sd 4:0:0:0: [sdh] Write Protect is off
[ 493.936696] sd 4:0:0:0: [sdh] Mode Sense: 00 3a 00 00
[ 493.936726] sd 4:0:0:0: [sdh] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 493.964105] sdh: sdh1
[ 493.965270] sd 4:0:0:0: [sdh] Attached SCSI disk
That was three-time-hotplugging-in-a-row and it works! \o/
So that is a general bug in libata and not driver specific? Is that fix
considered to be safe and will it most likely be included in upstream
kernel?
But first, thanks for the help, finding the patch and everything else,
greatly appreciated. :)
regards
Michael
--
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/4fb81b12.8070...@gmail.com
Bug#673496: X problems
Sorry I didn't save the Xorg.0.log in time from that boot of the 3.2 kernel. It might have been very informative. This machine has many problems with the X system. First it apparently does not report accurate screen size because the initial boot of both Lenny and Squeeze had a huge over-sized screen and I had to figure out how to get into a terminal window and edit xorg.conf to force a correct desktop size. This was done with a virtual screen. Section Screen Identifier Default Screen Monitor Configured Monitor DefaultDepth 16 SubSection Display Depth 16 Virtual 1280 800 EndSubSection EndSection That part at least works in both Lenny and Squeeze. I had thought that the same xorg.conf which worked in Lenny would work in Squeeze, but it didn't. And this is where things gets really weird. When I initially installed Squeeze on this laptop and copied the xorg.conf from the Lenny install there was a problem with the touchpad. X would refuse to load, dumping back to the shell prompt. Looking at the log, it was having an error from not being able to find the right driver for the Glidepoint touchpad. This makes zero sense, but that's what it was saying. Lenny also complained of the touchpad but loaded anyway, using some sort of guess method to use it even though it couldn't find the right driver. (The touchpad does work, btw.) In Squeeze it would halt on this error. After long, tedious trial and error I figured out the changes to make it load. It turned out to be the option to use BIOS to save and restore the VESA modes. Again, this makes no sense, but I don't know the inner workings of the Open Chrome driver. This worked in Lenny: Section Device Identifier Configured Video Device Option SWcursor Option EnableAGPDMA Option VBEModes Option VBESaveRestore EndSection The SWCursor was necessary in Lenny but not in Squeeze. Apparently they figured out how to activate the hardware cursor in later revisions of OpenChrome. So I could drop that for Squeeze. But this is the weird, weird thing. VBESaveRestore is what causes X to barf on the Glidepoint touchpad. Remove that and X will load, though still complaining like it did in Lenny. Fortunately that doesn't seem to be a problem. If I used the OpenChrome driver without the other option, VBEModes, there would be a serious problem. Running the OpenChrome driver on this machine without that option causes hard lockups when you try to exit the desktop. So something to do with resetting from graphical mode to text mode directly instead of using the BIOS causes a hard lock. (Constant hard locks in the video drivers is what makes Windows completely unusable on this machine...) These weird behaviors make it look like internal tests are being updated and made stricter in progressing versions of OpenChrome and making the driver fussier. And it seems likely that some sort of conflict occurs between OpenChrome and the 3.2 kernel that causes the hang when I try to load it. So I cannot yet say if the ath5k driver in that kernel works on this machine. -- 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/1337467181.77226.yahoomail...@web162603.mail.bf1.yahoo.com
Bug#673588: linux-image-3.2.0-2-686-pae: Elantech touchpad detected as PS2 mouse
Package: linux-2.6 Version: 3.2.16-1 Severity: normal Tags: upstream Hi, I'm running linux-image-3.2.0-2-686-pae version 3.2.16-1 on debian wheezy. I unsuccessfully tried version 3.2.17-1 from sid. The laptop is a Fujitsu Siemens Amilo pi2515. My /proc/bus/input/devices says: [...] I: Bus=0011 Vendor=0002 Product=0001 Version=0063 N: Name=PS/2 Logitech Wheel Mouse P: Phys=isa0060/serio4/input0 S: Sysfs=/devices/platform/i8042/serio4/input/input7 U: Uniq= H: Handlers=mouse0 event7 B: PROP=0 B: EV=7 B: KEY=7 0 0 0 0 0 0 0 0 B: REL=103 [...] Any hint? -- Package-specific info: ** Version: Linux version 3.2.0-2-686-pae (Debian 3.2.16-1) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-4) ) #1 SMP Mon Apr 30 05:59:35 UTC 2012 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-2-686-pae root=UUID=ce754bd4-1e36-4c3a-9343-dfa48ae2e393 ro quiet splash ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [ 3245.820683] pcieport :00:1c.3: restoring config space at offset 0xf (was 0x40400, writing 0x4040a) [ 3245.820698] pcieport :00:1c.3: restoring config space at offset 0x9 (was 0x10001, writing 0xf5f1f401) [ 3245.820704] pcieport :00:1c.3: restoring config space at offset 0x8 (was 0x0, writing 0xfbf0fa00) [ 3245.820711] pcieport :00:1c.3: restoring config space at offset 0x7 (was 0x2000, writing 0x4040) [ 3245.820722] pcieport :00:1c.3: restoring config space at offset 0x3 (was 0x81, writing 0x810010) [ 3245.820730] pcieport :00:1c.3: restoring config space at offset 0x1 (was 0x10, writing 0x100507) [ 3245.820796] uhci_hcd :00:1d.0: restoring config space at offset 0x1 (was 0x285, writing 0x281) [ 3245.820822] uhci_hcd :00:1d.0: wake-up capability disabled by ACPI [ 3245.820852] uhci_hcd :00:1d.1: restoring config space at offset 0x1 (was 0x285, writing 0x281) [ 3245.820878] uhci_hcd :00:1d.1: wake-up capability disabled by ACPI [ 3245.820908] uhci_hcd :00:1d.2: restoring config space at offset 0x1 (was 0x285, writing 0x281) [ 3245.820933] uhci_hcd :00:1d.2: wake-up capability disabled by ACPI [ 3245.820973] ehci_hcd :00:1d.7: restoring config space at offset 0x1 (was 0x2900106, writing 0x2900102) [ 3245.820993] ehci_hcd :00:1d.7: wake-up capability disabled by ACPI [ 3245.821000] ehci_hcd :00:1d.7: PME# disabled [ 3245.821022] pci :00:1e.0: restoring config space at offset 0x9 (was 0x10001, writing 0x1fff1) [ 3245.821028] pci :00:1e.0: restoring config space at offset 0x8 (was 0x0, writing 0xfff0) [ 3245.821034] pci :00:1e.0: restoring config space at offset 0x7 (was 0x2280, writing 0x228000f0) [ 3245.821048] pci :00:1e.0: restoring config space at offset 0x1 (was 0x14, writing 0x100107) [ 3245.821101] pci :00:1f.0: restoring config space at offset 0x1 (was 0x217, writing 0x2100107) [ 3245.821122] ata_piix :00:1f.1: restoring config space at offset 0xf (was 0x100, writing 0x1ff) [ 3245.821149] ata_piix :00:1f.1: restoring config space at offset 0x1 (was 0x285, writing 0x2880005) [ 3245.821173] ahci :00:1f.2: restoring config space at offset 0xf (was 0x200, writing 0x20a) [ 3245.821200] ahci :00:1f.2: restoring config space at offset 0x1 (was 0x2b7, writing 0x2b00407) [ 3245.821255] pci :00:1f.3: restoring config space at offset 0x4 (was 0x0, writing 0x8000) [ 3245.821335] iwl3945 :04:00.0: restoring config space at offset 0xf (was 0x100, writing 0x107) [ 3245.821404] iwl3945 :04:00.0: restoring config space at offset 0x4 (was 0x0, writing 0xf800) [ 3245.821418] iwl3945 :04:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x10) [ 3245.821438] iwl3945 :04:00.0: restoring config space at offset 0x1 (was 0x10, writing 0x100506) [ 3245.821586] r8169 :06:00.0: restoring config space at offset 0xf (was 0x100, writing 0x10a) [ 3245.821613] r8169 :06:00.0: restoring config space at offset 0x6 (was 0x4, writing 0xfa04) [ 3245.821623] r8169 :06:00.0: restoring config space at offset 0x4 (was 0x1, writing 0x4001) [ 3245.821631] r8169 :06:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x10) [ 3245.821642] r8169 :06:00.0: restoring config space at offset 0x1 (was 0x10, writing 0x40100507) [ 3245.821814] PM: early resume of devices complete after 1.710 msecs [ 3245.821886] i915 :00:02.0: setting latency timer to 64 [ 3245.821931] uhci_hcd :00:1a.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [ 3245.821943] uhci_hcd :00:1a.0: setting latency timer to 64 [ 3245.822073] usb usb3: root hub lost power or was reset [ 3245.822113] uhci_hcd :00:1a.1: PCI INT B - GSI 21 (level, low) - IRQ 21 [ 3245.87] uhci_hcd :00:1a.1: setting latency timer to 64 [ 3245.822534] usb usb4: root hub lost power or was reset [ 3245.822613] ehci_hcd :00:1a.7: PCI INT C - GSI 18 (level, low) - IRQ 18 [ 3245.822765]
Bug#619381: linux-image-2.6.38-1-amd64: usb mass storage error causes kernel panic
reopen 619381 forwarded 619381 https://bugzilla.kernel.org/show_bug.cgi?id=31802 tags 619381 + moreinfo quit Jonathan Nieder wrote: On Wed, 2011-03-23 at 13:35 +0100, Michal Suchanek wrote: 1) Attach a SATA drive to a SATA/USB bridge. 2) dd if=/dev/urandom of=/dev/sdf bs=4k 3) detach the drive drom the bridge Results in kernel panic. [...] Pid: 15054, comm: dd Not tainted 2.6.38-1-amd64 #1 Dell Inc. OptiPlex 960 /0Y958C RIP: 0010:[8103b9ce] [8103b9ce] task_rq_lock+0x37/0x7a [...] Code: [...] 89 dd 8b 40 18 4c 03 2c c5 d0 08 [...] [...] forcemerge 631187 619381 [...] Thanks again for a pleasant report. Closing optimistically. As usual, confirmation either way about the fix would be useful. Actually, these can't be the same bug, because 619381 was found using 2.6.38-1 and 631187 was tested not to affect 2.6.38-5. What kernel are you using these days? Can you still reproduce this? Curious, Jonathan -- 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/20120519233810.GA32284@burratino
Processed: Re: linux-image-2.6.38-1-amd64: usb mass storage error causes kernel panic
Processing commands for cont...@bugs.debian.org:
reopen 619381
Bug #619381 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6]
linux-image-2.6.38-1-amd64: usb mass storage error causes kernel panic
Bug reopened
Ignoring request to alter fixed versions of bug #619381 to the same values
previously set
forwarded 619381 https://bugzilla.kernel.org/show_bug.cgi?id=31802
Bug #619381 [linux-2.6] linux-image-2.6.38-1-amd64: usb mass storage error
causes kernel panic
Changed Bug forwarded-to-address to
'https://bugzilla.kernel.org/show_bug.cgi?id=31802' from
'https://bugzilla.kernel.org/show_bug.cgi?id=38842'
tags 619381 + moreinfo
Bug #619381 [linux-2.6] linux-image-2.6.38-1-amd64: usb mass storage error
causes kernel panic
Added tag(s) moreinfo.
quit
Stopping processing here.
Please contact me if you need assistance.
--
619381: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619381
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
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/handler.s.c.13374707071860.transcr...@bugs.debian.org
Bug#619381: linux-image-2.6.38-1-amd64: usb mass storage error causes kernel panic
On Sat, 2012-05-19 at 18:38 -0500, Jonathan Nieder wrote: reopen 619381 forwarded 619381 https://bugzilla.kernel.org/show_bug.cgi?id=31802 tags 619381 + moreinfo quit Jonathan Nieder wrote: On Wed, 2011-03-23 at 13:35 +0100, Michal Suchanek wrote: 1) Attach a SATA drive to a SATA/USB bridge. 2) dd if=/dev/urandom of=/dev/sdf bs=4k 3) detach the drive drom the bridge Results in kernel panic. [...] Pid: 15054, comm: dd Not tainted 2.6.38-1-amd64 #1 Dell Inc. OptiPlex 960 /0Y958C RIP: 0010:[8103b9ce] [8103b9ce] task_rq_lock+0x37/0x7a [...] Code: [...] 89 dd 8b 40 18 4c 03 2c c5 d0 08 [...] [...] forcemerge 631187 619381 [...] Thanks again for a pleasant report. Closing optimistically. As usual, confirmation either way about the fix would be useful. Actually, these can't be the same bug, because 619381 was found using 2.6.38-1 and 631187 was tested not to affect 2.6.38-5. What kernel are you using these days? Can you still reproduce this? These bug reports involve different failure cases (soft-removal in #631187 and hard-removal in #619381). However, it's conceivable that the underlying bug was the same, exacerbated by some change in 2.6.39 so that soft-removal was also affected. Ben. -- Ben Hutchings All extremists should be taken out and shot. signature.asc Description: This is a digitally signed message part
Bug#671689: [regression 3.2-3.3.4] sata_sil (on sil 3512) hotplug broken again
tags 671689 - moreinfo quit Michael Schmitt wrote: That was three-time-hotplugging-in-a-row and it works! \o/ Thanks! Passed upstream, so hopefully the fix should be part of 3.3.y soon. -- 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/2012052045.GF4567@burratino
Processed: Re: [regression 3.2-3.3.4] sata_sil (on sil 3512) hotplug broken again
Processing commands for cont...@bugs.debian.org: tags 671689 - moreinfo Bug #671689 [linux-2.6] linux-image-3.3.0-trunk-686-pae: sata_sil (on sil 3512) hotplug broken again Removed tag(s) moreinfo. quit Stopping processing here. Please contact me if you need assistance. -- 671689: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671689 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.133747206410852.transcr...@bugs.debian.org
Bug#673496: X problems
On Sat, 2012-05-19 at 15:39 -0700, Paul Zimmerman wrote:
Sorry I didn't save the Xorg.0.log in time from that boot of the 3.2 kernel.
It might have
been very informative.
This machine has many problems with the X system. First it apparently does
not
report accurate screen size because the initial boot of both Lenny and
Squeeze
had a huge over-sized screen and I had to figure out how to get into a
terminal
window and edit xorg.conf to force a correct desktop size. This was done with
a
virtual screen.
xorg.conf is no longer required on most systems, and you may find that
the X server works better if you remove most of it.
[...]
If I used the OpenChrome driver without the other option, VBEModes,
there would be a serious problem. Running the OpenChrome driver on this
machine
without that option causes hard lockups when you try to exit the desktop. So
something to do with resetting from graphical mode to text mode directly
instead of
using the BIOS causes a hard lock. (Constant hard locks in the video drivers
is what
makes Windows completely unusable on this machine...)
These weird behaviors make it look like internal tests are being updated and
made
stricter in progressing versions of OpenChrome and making the driver fussier.
And it
seems likely that some sort of conflict occurs between OpenChrome and the 3.2
kernel
that causes the hang when I try to load it. So I cannot yet say if the ath5k
driver in that
kernel works on this machine.
Well, you should report that bug separately against
xserver-xorg-video-openchrome. But for now, please boot to single-user
mode ('rescue mode' in the GRUB menu) and test the ath5k driver from the
text console.
Ben.
--
Ben Hutchings
All extremists should be taken out and shot.
signature.asc
Description: This is a digitally signed message part
Processed: severity of 671860 is important
Processing commands for cont...@bugs.debian.org: severity 671860 important Bug #671860 [src:linux-2.6] Disk freeze on 2.6.32 and 3.x kernels: blkback blocked for more than 120 seconds Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 671860: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671860 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.133747633731370.transcr...@bugs.debian.org
Bug#671860: Disk freeze on 2.6.32 and 3.x kernels: blkback blocked for more than 120 seconds
On Mon, 2012-05-07 at 17:33 +0200, Andreas Pflug wrote: Package: linux-image-3.2.0-0.bpo.1-amd64 Version: 3.2.1-2~bpo60+1 Severity: grave Actually, all kernels from 2.6.32 to (at least) 3.2.1 seem to be affected. I run two identical machines: Debian6 AMD64, raid1 software mirror for data disks, on /dev/mdx is lvm2 configured. The /dev/mapper devices are synced to the other machine using drbd. These drb-devices are used for virtual machines. Sometimes, one machine degrades. Apparently the mdX_resync process and blkback collide. Until now, I only observed this on Windows HVM used disk devices. [...] May 6 01:06:24 lady kernel: [4979042.044157] INFO: task blkback.12.hdb:16636 blocked for more than 120 seconds. May 6 01:06:24 lady kernel: [4979042.044255] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. May 6 01:06:24 lady kernel: [4979042.044345] blkback.12.hdb D 880002c817e0 0 16636 2 0x May 6 01:06:24 lady kernel: [4979042.044355] 880002c817e0 0246 8800 8160d020 May 6 01:06:24 lady kernel: [4979042.044366] 00013540 880007dbffd8 880007dbffd8 00013540 May 6 01:06:24 lady kernel: [4979042.044375] 880002c817e0 880007dbe010 81013949 000107cacc78 May 6 01:06:24 lady kernel: [4979042.044385] Call Trace: May 6 01:06:24 lady kernel: [4979042.044398] [81013949] ? sched_clock+0x5/0x8 May 6 01:06:24 lady kernel: [4979042.044423] [a0103673] ? wait_barrier+0x94/0xcd [raid1] May 6 01:06:24 lady kernel: [4979042.044432] [81045e84] ? try_to_wake_up+0x190/0x190 May 6 01:06:24 lady kernel: [4979042.01] [a0104a94] ? make_request+0x11d/0x1689 [raid1] May 6 01:06:24 lady kernel: [4979042.044454] [a010cc7b] ? __split_and_process_bio+0x520/0x532 [dm_mod] [...] This looks like the same bug as #584881 and probably fixed in 3.2.14-1. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584881;msg=113. The current kernel version in squeeze-backports includes that bug fix; please test whether that works for you. If you would like to test my backported bug fix for 2.6.32 (attached to the message linked above), then please do so following the instructions at http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official. Ben. -- Ben Hutchings All extremists should be taken out and shot. signature.asc Description: This is a digitally signed message part
Bug#673588: Elantech touchpad detected as PS2 mouse
Hi Nicola, Quick questions: Nicola Alessi wrote: Tags: upstream Which upstream version did you test? [...] I'm running linux-image-3.2.0-2-686-pae version 3.2.16-1 on debian wheezy. I unsuccessfully tried version 3.2.17-1 from sid. The laptop is a Fujitsu Siemens Amilo pi2515. My /proc/bus/input/devices says: Is this a regression? (In other words, did a previous version work better?) Does 3.3.y from experimental behave any differently? Please attach full dmesg output from booting and a copy of Xorg.0.log. Thanks and sorry for the trouble, Jonathan -- 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/20120520013530.GA32635@burratino
amd64 as default architecture
Most new PCs have an Intel or AMD 64-bit processor, and
popcon.debian.org shows amd64 numbers almost matching i386.
For some time we have also provided the amd64 kernel for i386, identical
in all but the package metadata. This has not always been perfectly
compatible with i386 userland, but split 32/64-bit installations are
increasingly used and I think most bugs have been flushed out by now.
Thanks to multi-arch you can now add amd64 as a secondary architecture
and install the kernel package from amd64, and if your system is running
such a kernel then it can also support userland packages from amd64.
So in wheezy I would like to see:
1. Default architecture (top of the list for installation media/manual)
being amd64 ('64-bit PC').
2. Users of the amd64 kernel flavour on i386 encouraged to add amd64 as
a secondary architecture (debconf note?).
Then in wheezy+1:
3. amd64 kernel flavour for i386 dropped.
4. Kernel and common libraries for amd64 included in i386 installation
media; kernel included on low-number disc.
5. Installer for i386 prefers amd64 kernel on any capable machine
(that's a one-line change!) and adds amd64 as secondary architecture if
this is selected.
Eventually (wheezy+2? +3?) we would stop building a kernel package for
i386.
Does anyone see a problem with the above, in particular points 1 and 2?
(Also, much of the above applies to s390x vs s390. And please let's
have ppc64 and sparc64 soon!)
Ben.
--
Ben Hutchings
All extremists should be taken out and shot.
signature.asc
Description: This is a digitally signed message part
Processed: tagging 671860
Processing commands for cont...@bugs.debian.org: tags 671860 + patch moreinfo Bug #671860 [src:linux-2.6] Disk freeze on 2.6.32 and 3.x kernels: blkback blocked for more than 120 seconds Added tag(s) moreinfo and patch. thanks Stopping processing here. Please contact me if you need assistance. -- 671860: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671860 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.133748052018430.transcr...@bugs.debian.org
Re: amd64 as default architecture
Hi Ben,
On Sun, May 20, 2012 at 03:16:15AM +0100, Ben Hutchings wrote:
Most new PCs have an Intel or AMD 64-bit processor, and
popcon.debian.org shows amd64 numbers almost matching i386.
So in wheezy I would like to see:
1. Default architecture (top of the list for installation media/manual)
being amd64 ('64-bit PC').
2. Users of the amd64 kernel flavour on i386 encouraged to add amd64 as
a secondary architecture (debconf note?).
My biggest concern with this is the same that prevented Ubuntu from
switching to amd64 as a default for 12.04 - namely, that even though almost
all new hardware coming out would benefit from a 64-bit OS, there's a
sizeable fraction of users for whom a 64-bit CD would be nothing more than a
coaster.
https://lists.ubuntu.com/archives/ubuntu-devel/2012-April/035088.html
Now perhaps it's easier for Debian to switch this default than it is for
Ubuntu, since Debian's choice of default arch doesn't have quite the same
all or nothing impact on pressed CDs and the like. But IMHO it's better
for our users to choose a default that's safe, at the cost of some users not
getting the most out of their hardware if they use the default.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: Digital signature
Re: amd64 as default architecture
On Sat, 2012-05-19 at 19:44 -0700, Steve Langasek wrote:
Hi Ben,
On Sun, May 20, 2012 at 03:16:15AM +0100, Ben Hutchings wrote:
Most new PCs have an Intel or AMD 64-bit processor, and
popcon.debian.org shows amd64 numbers almost matching i386.
So in wheezy I would like to see:
1. Default architecture (top of the list for installation media/manual)
being amd64 ('64-bit PC').
2. Users of the amd64 kernel flavour on i386 encouraged to add amd64 as
a secondary architecture (debconf note?).
My biggest concern with this is the same that prevented Ubuntu from
switching to amd64 as a default for 12.04 - namely, that even though almost
all new hardware coming out would benefit from a 64-bit OS, there's a
sizeable fraction of users for whom a 64-bit CD would be nothing more than a
coaster.
I certainly don't propose to have any pages where amd64 is the only
option. But where we have lists of multiple architectures, I would like
to see '64-bit PC' first.
Quite a few such lists sorted alphabetically by Debian architecture
name, which means that 'amd64' comes first. However, 'amd64' confuses
many people, and sorting by descriptive name puts '32-bit PC' first.
https://lists.ubuntu.com/archives/ubuntu-devel/2012-April/035088.html
Now perhaps it's easier for Debian to switch this default than it is for
Ubuntu, since Debian's choice of default arch doesn't have quite the same
all or nothing impact on pressed CDs and the like. But IMHO it's better
for our users to choose a default that's safe, at the cost of some users not
getting the most out of their hardware if they use the default.
Actually, the default Debian installation medium - in so far as it's
linked from the front of www.debian.org - is an amd64/i386 netinst
image, which encourages use of amd64 while still being 'safe'.
Ben.
--
Ben Hutchings
All extremists should be taken out and shot.
signature.asc
Description: This is a digitally signed message part
Bug#504116: [etchnhalf] RAID1 broken after upgrading kernel to 2.6.24-etchnhalf
Hi Olaf, In October, 2008, Olaf Zaplinski wrote: upgraded from 2.6.18 to 2.6.24-etchnhalf on i686 machine, afterwards all my RAID1 volumes were broken: [...] Reason: /dev/hda is running fine (PIIX4), but /dev/sda on 53c875 is missing in the RAID setup. It is accessible: binky:~# fdisk -l /dev/sda Disk /dev/sda: 4335 MB, 4335206400 bytes 255 heads, 63 sectors/track, 527 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes [--snip--] but the RAID setup is broken. Sorry we lost track of this before. Before investigating further, a few questions: - do you still have access to this machine? - if so, how are you coping? What kernel do you use? - any workarounds or other weird observations? Thanks and sorry for the trouble, Jonathan -- 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/20120520032039.GA2287@burratino
Bug#504939: marked as done (kernel crashs permanent if I connect my Nokia Cell-Phone)
Your message dated Sat, 19 May 2012 22:34:39 -0500 with message-id 20120520033439.GA2504@burratino and subject line Re: kernel crashs permanent if I connect my Nokia Cell-Phone has caused the Debian Bug report #504939, regarding kernel crashs permanent if I connect my Nokia Cell-Phone to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 504939: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504939 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.18-6-686 Version: 2.6.18.dfsg.1-18etch1 Severity: important Hello Maintainer, I have upgraded my older Sarge Router to Etch with the above kernel and now my router/kernel crashs all the time... while loading the cdc_acm and sometimes after running for hours. I can not even upgrade to a 2.6.26 from backports.org since it crash during the apt-get procedure... ---[ '/var/log/kern.log' ]-- Nov 7 13:20:43 router kernel: kernel BUG at mm/slab.c:595! Nov 7 13:20:43 router kernel: invalid opcode: [#1] Nov 7 13:20:43 router kernel: SMP Nov 7 13:20:43 router kernel: Modules linked in: rndis_host cdc_ether usbnet soundcore psmouse i2c_piix4 serio_raw ac97_codec shpchp pci_hotplug pcspkr i2c_core intel_agp agpgart yenta_socket rsrc_nonstatic pcmcia_core evdev ext3 jbd mbcache ide_generic ide_cd cdrom ide_disk generic piix ide_core e100 mii uhci_hcd usbcore thermal processor fan Nov 7 13:20:43 router kernel: CPU:0 Nov 7 13:20:43 router kernel: EIP:0060:[c0156d53]Not tainted VLI Nov 7 13:20:43 router kernel: EFLAGS: 00010006 (2.6.18-6-686 #1) Nov 7 13:20:43 router kernel: EIP is at kfree+0x2e/0x65 Nov 7 13:20:43 router kernel: eax: 8060 ebx: c1308ac0 ecx: c7fef7a0 edx: c1026040 Nov 7 13:20:43 router kernel: esi: 0282 edi: c1302392 ebp: c1308800 esp: c77b1e18 Nov 7 13:20:43 router kernel: ds: 007b es: 007b ss: 0068 Nov 7 13:20:43 router kernel: Process modprobe (pid: 1335, ti=c77b task=c7599550 task.ti=c77b) Nov 7 13:20:43 router kernel: Stack: c1308ac0 c893760e c1308806 c893701a c76e7800 c89306a0 c770cae8 c77e3800 Nov 7 13:20:43 router kernel:ffe0 c747fe00 0001 0001 0001 0001 Nov 7 13:20:43 router kernel:c8930660 c76e7800 c8931520 c8931550 c0210e08 c885bba5 c76e7814 c76e7814 Nov 7 13:20:43 router kernel: Call Trace: Nov 7 13:20:43 router kernel: [c893701a] usbnet_probe+0x4ee/0x503 [usbnet] Nov 7 13:20:43 router kernel: [c0210e08] __driver_attach+0x0/0x5d Nov 7 13:20:43 router kernel: [c885bba5] usb_probe_interface+0x58/0x87 [usbcore] Nov 7 13:20:43 router kernel: [c0210d69] driver_probe_device+0x42/0x8b Nov 7 13:20:43 router kernel: [c0210e40] __driver_attach+0x38/0x5d Nov 7 13:20:43 router kernel: [c021088a] bus_for_each_dev+0x33/0x55 Nov 7 13:20:43 router kernel: [c0210cd3] driver_attach+0x11/0x13 Nov 7 13:20:43 router kernel: [c0210e08] __driver_attach+0x0/0x5d Nov 7 13:20:43 router kernel: [c02105a3] bus_add_driver+0x64/0xfd Nov 7 13:20:43 router kernel: [c885b9da] usb_register_driver+0x60/0xbb [usbcore] Nov 7 13:20:43 router kernel: [c01358d9] sys_init_module+0x16c3/0x1846 Nov 7 13:20:43 router kernel: [c0161b28] cp_new_stat64+0xfd/0x10f Nov 7 13:20:43 router kernel: [c0102c11] sysenter_past_esp+0x56/0x79 Nov 7 13:20:43 router kernel: Code: 56 89 c7 53 74 58 9c 5e fa 8d 90 00 00 00 40 c1 ea 0c c1 e2 05 03 15 70 f3 36 c0 8b 02 f6 c4 40 74 03 8b 52 0c 8b 02 84 c0 78 08 0f 0b 53 02 81 b0 29 c0 89 e0 8b 4a 18 25 00 e0 ff ff 8b 40 10 Nov 7 13:20:43 router kernel: EIP: [c0156d53] kfree+0x2e/0x65 SS:ESP 0068:c77b1e18 Nov 7 13:20:43 router kernel: 6es1371: version v0.32 time 22:12:03 Feb 10 2008 Nov 7 13:28:44 router kernel: kernel BUG at mm/slab.c:595! Nov 7 13:28:44 router kernel: invalid opcode: [#1] Nov 7 13:28:44 router kernel: SMP Nov 7 13:28:44 router kernel: Modules linked in: rndis_host cdc_ether usbnet cdc_acm ipv6 button ac battery dm_snapshot dm_mirror dm_mod tsdev pcmcia firmware_class snd_ens1371 snd_rawmidi snd_seq_device snd_ac97_codec snd_ac97_bus psmouse snd_pcm snd_timer snd snd_page_alloc rtc floppy parport_pc parport es1371 gameport soundcore ac97_codec pcspkr serio_raw i2c_piix4 shpchp i2c_core yenta_socket rsrc_nonstatic pcmcia_core intel_agp agpgart pci_hotplug evdev ext3 jbd mbcache ide_generic ide_cd cdrom ide_disk generic uhci_hcd usbcore e100 mii piix ide_core thermal processor fan Nov 7 13:28:44 router kernel: CPU:0 Nov 7 13:28:44 router kernel: EIP:
Bug#511747: [lenny] unresponsible for some time when removing qdisc
Hi Jindřich, In January, 2009, Jindřich Vrba wrote: Version: 2.6.24-6~etchnhalf.7 Severity: important When I delete whole qdisc with iproute command # tc qdisc del dev eth0 root the system don't respond for some time. [...] On testing 2.6.26-1-686 there is the same bug. I also tried 2.6.18-6-amd64 Linux from stable, where it is all right Sorry we lost track of this for so long. Can you still reproduce this bug? What kernel are you using these days? Curious, Jonathan -- 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/20120520034202.GA2702@burratino
Re: amd64 as default architecture
On May 20, Ben Hutchings b...@decadent.org.uk wrote: Then in wheezy+1: 3. amd64 kernel flavour for i386 dropped. Why can't we use the multiarch package in wheezy? -- ciao, Marco signature.asc Description: Digital signature
RE: Debian and Hyper-V VM drivers
On Wed, 2012-05-16 at 15:11 +, Mike Sterling wrote: On Tuesday, May 15, 2012 6:52 PM, Ben Hutchings [mailto:b...@decadent.org.uk] wrote: On Wed, 2012-05-16 at 01:37 +, Mike Sterling wrote: Great, thanks. We've done some investigation into the current status of Wheezy on Hyper-V, and as of 3.2.0-2, there's about a five patch differential between linux-next and the 3.2.0-2 kernel. How can I update to the 3.2.15-1 kernel? I installed Wheezy using the latest testing ISO, but apt-get doesn't want to show a new kernel. [...] In wheezy the current version is 3.2.16-1. The kernel version string doesn't match this because it's used as an ABI version and we try to avoid frequent ABI changes. [...] Thanks for the clarification. There have been a couple of patches that have gone in upstream that we'd like to make sure get applied to the Wheezy kernel. Is there a date or upstream commit ID that you're using to generate the kernel sources that we can use as a base to automatically generate all the accepted upstream patches? You can get our current source from git://anonscm.debian.org/kernel/linux-2.6.git, wheezy branch (note, this branch is subject to rebasing). Each backported commit has an upstream commit reference. Essentially we have everything up to v3.4-rc1. Ben. -- Ben Hutchings All extremists should be taken out and shot. signature.asc Description: This is a digitally signed message part
Bug#409349: usbhid: control queue full; hung apcupsd task
# letting version tracking do its work
tags 409349 - squeeze
tags 409349 + patch moreinfo
quit
Hi again,
Steven Chamberlain wrote:
On 05/04/12 13:48, hugo vanwoerkom wrote:
apcupsd 3.14.10-1 with MODEL: Back-UPS RS 700G and Sid kernel
3.2.0-2-amd64. Can't reproduce problem.
Thanks a lot. So far I've not experienced this in 3.2.0-2-amd64
3.2.12-1 either but I've only been testing for a few hours.
Great, thanks. If this is still reproducible on 2.6.37, based on
$ git log --no-merges --oneline v2.6.37..v3.2.12 --
drivers/hid/usbhid/hid-core.c
fad9fbe8651e HID: usbhid: cancel timer for retry synchronously
5b1b0b812a7b PM / Runtime: Add macro to test for runtime PM events
6dc1418e1314 HID: yurex: recognize GeneralKeys wireless presenter as generic
HID
b4dbde9da8ec HID: Add Support for Setting and Getting Feature Reports from
hidraw
68229689b6dc HID: usbhid: base runtime PM on modern API
4291ee305e9b HID: Add and use hid_level: dev_level equivalents
a path-limited bisect[1] to find the fix should not take many
iterations. Let me know and I can send some commands to try.
The topmost and second-to-bottom commits look especially interesting.
(Unfortunately none of these looks too promising.) I'm attaching a
copy of the topmost backported to 2.6.32.y. Results from trying it
against the squeeze kernel, following instructions from [2], would be
interesting, though I am not too optimistic.
Hope that helps.
Grasping at straws,
Jonathan
[1] http://git-htmldocs.googlecode.com/git/git-bisect-lk2009.html
[2]
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official
or the corresponding page from the debian-kernel-handbook package
From: Oliver Neukum oli...@neukum.org
Date: Thu, 13 Oct 2011 18:21:58 +0200
Subject: HID: usbhid: cancel timer for retry synchronously
commit fad9fbe8651e8abd9794d4b4c4133241aa3093b5 upstream.
This makes sure IO is never restarted while a reset is going on
In particular there seems to be no protection from hid_retry_timeout() calling
hid_start_in() which would start IO after hid_pre_reset() has already called
hid_cease_io() because that uses del_timer(), not del_timer_sync()
Signed-off-by: Oliver Neukum oneu...@suse.de
Signed-off-by: Jiri Kosina jkos...@suse.cz
Signed-off-by: Jonathan Nieder jrnie...@gmail.com
---
drivers/hid/usbhid/hid-core.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/hid/usbhid/hid-core.c b/drivers/hid/usbhid/hid-core.c
index e9add5b3481d..a8bdd6bc7ef2 100644
--- a/drivers/hid/usbhid/hid-core.c
+++ b/drivers/hid/usbhid/hid-core.c
@@ -1216,7 +1216,7 @@ static void hid_cancel_delayed_stuff(struct usbhid_device
*usbhid)
static void hid_cease_io(struct usbhid_device *usbhid)
{
- del_timer(usbhid-io_retry);
+ del_timer_sync(usbhid-io_retry);
usb_kill_urb(usbhid-urbin);
usb_kill_urb(usbhid-urbctrl);
usb_kill_urb(usbhid-urbout);
--
1.7.10.2
Processed: Re: usbhid: control queue full; hung apcupsd task
Processing commands for cont...@bugs.debian.org: # letting version tracking do its work tags 409349 - squeeze Bug #409349 [src:linux-2.6] usbhid: control queue full; hung apcupsd task Bug #611646 [src:linux-2.6] usbhid: control queue full; hung apcupsd task Removed tag(s) squeeze. Removed tag(s) squeeze. tags 409349 + patch moreinfo Bug #409349 [src:linux-2.6] usbhid: control queue full; hung apcupsd task Bug #611646 [src:linux-2.6] usbhid: control queue full; hung apcupsd task Added tag(s) patch. Added tag(s) patch. quit Stopping processing here. Please contact me if you need assistance. -- 409349: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=409349 611646: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611646 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.133748836019957.transcr...@bugs.debian.org
Bug#493813: marked as done (linux-image-2.6.24-etchnhalf.1-amd64: Crashed after a time with clocksource problem)
Your message dated Sat, 19 May 2012 23:37:52 -0500
with message-id 20120520043752.GA10808@burratino
and subject line Re: linux-image-2.6.24-etchnhalf.1-amd64: Crashed after a time
with clocksource problem
has caused the Debian Bug report #493813,
regarding linux-image-2.6.24-etchnhalf.1-amd64: Crashed after a time with
clocksource problem
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
493813: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=493813
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-image-2.6.24-etchnhalf.1-amd64
Version: 2.6.24-6~etchnhalf.4
Severity: grave
Justification: renders package unusable
Please see
http://bugzilla.kernel.org/show_bug.cgi?id=9834
https://issues.rpath.com/browse/RPL-2573
It works again using
clocksource=acpi_pm
as boot parameter
-- Package-specific info:
** Version:
Linux version 2.6.24-etchnhalf.1-amd64 (Debian 2.6.24-6~etchnhalf.4)
(da...@debian.org) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21))
#1 SMP Mon Jul 21 10:36:02 UTC 2008
** Command line:
root=/dev/sda2 clocksource=acpi_pm ro
** Not tainted
** Kernel log:
SCSI subsystem initialized
e1000: :00:11.0: e1000_probe: (PCI:66MHz:32-bit) 00:50:56:aa:0e:5f
Fusion MPT base driver 3.04.06
Copyright (c) 1999-2007 LSI Corporation
Fusion MPT SPI Host driver 3.04.06
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
PIIX4: IDE controller (0x8086:0x7111 rev 0x01) at PCI slot :00:07.1
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x1050-0x1057, BIOS settings: hda:DMA, hdb:pio
PIIX4: IDE port disabled
Probing IDE interface ide0...
hda: VMware Virtual IDE CDROM Drive, ATAPI CD/DVD-ROM drive
hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4
hda: UDMA/33 mode selected
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ACPI: PCI Interrupt :00:10.0[A] - GSI 17 (level, low) - IRQ 17
mptbase: ioc0: Initiating bringup
libata version 3.00 loaded.
ioc0: LSI53C1030 B0: Capabilities={Initiator}
scsi0 : ioc0: LSI53C1030 B0, FwRev=h, Ports=1, MaxQ=128, IRQ=17
scsi 0:0:0:0: Direct-Access VMware Virtual disk 1.0 PQ: 0 ANSI: 2
target0:0:0: Beginning Domain Validation
target0:0:0: Domain Validation skipping write tests
target0:0:0: Ending Domain Validation
target0:0:0: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 127)
scsi 0:0:1:0: Direct-Access VMware Virtual disk 1.0 PQ: 0 ANSI: 2
target0:0:1: Beginning Domain Validation
target0:0:1: Domain Validation skipping write tests
target0:0:1: Ending Domain Validation
target0:0:1: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 127)
hda: ATAPI 1X CD-ROM drive, 32kB Cache
Uniform CD-ROM driver Revision: 3.20
Driver 'sd' needs updating - please use bus_type methods
sd 0:0:0:0: [sda] 75497472 512-byte hardware sectors (38655 MB)
sd 0:0:0:0: [sda] Test WP failed, assume Write Enabled
sd 0:0:0:0: [sda] Cache data unavailable
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] 75497472 512-byte hardware sectors (38655 MB)
sd 0:0:0:0: [sda] Test WP failed, assume Write Enabled
sd 0:0:0:0: [sda] Cache data unavailable
sd 0:0:0:0: [sda] Assuming drive cache: write through
sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7
sd 0:0:0:0: [sda] Attached SCSI disk
sd 0:0:1:0: [sdb] 461373440 512-byte hardware sectors (236223 MB)
sd 0:0:1:0: [sdb] Test WP failed, assume Write Enabled
sd 0:0:1:0: [sdb] Cache data unavailable
sd 0:0:1:0: [sdb] Assuming drive cache: write through
sd 0:0:1:0: [sdb] 461373440 512-byte hardware sectors (236223 MB)
sd 0:0:1:0: [sdb] Test WP failed, assume Write Enabled
sd 0:0:1:0: [sdb] Cache data unavailable
sd 0:0:1:0: [sdb] Assuming drive cache: write through
sdb: sdb1
sd 0:0:1:0: [sdb] Attached SCSI disk
Attempting manual resume
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
agpgart: Detected an Intel 440BX Chipset.
agpgart: AGP aperture is 256M @ 0x0
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
piix4_smbus :00:07.3: Found :00:07.3 device
piix4_smbus :00:07.3: Host SMBus controller not enabled!
ACPI: AC Adapter [ACAD] (on-line)
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
input: Power Button (FF) as /class/input/input2
pnp: the driver 'parport_pc' has been registered
parport_pc 00:08: reported by Plug and Play ACPI
parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
input: PC Speaker as /class/input/input3
ACPI: Power Button (FF) [PWRF]
parport_pc 00:08: driver attached
input: ImPS/2 Generic Wheel
Bug#509011: marked as done (New kernel does not boot up on PegasosPPC)
Your message dated Sat, 19 May 2012 23:44:02 -0500 with message-id 20120520044402.GA10892@burratino and subject line Re: New kernel does not boot up on PegasosPPC has caused the Debian Bug report #509011, regarding New kernel does not boot up on PegasosPPC to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 509011: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=509011 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6-powerpc-etchnhalf Version: 2.6.24+13~etchnhalf.1 Severity: critical I've upgraded my old Sarge installation to recent Etch and was unable to boot up the new kernel package. It failed to mount my root partition. I had to boot up using my old 2.6.19 selfbuilt kernel and rebuild 2.6.24 one. I worked around the problem by linking some of key components (VIA ATA support, PS/2 keyboard, GFX card) into the kernel instead of modules. -- Best regards, Pavel mailto:sonic.am...@gmail.com ---End Message--- ---BeginMessage--- Bastian Blank wrote: On Wed, Dec 17, 2008 at 03:18:42PM +0300, Pavel Fedin wrote: I've upgraded my old Sarge installation to recent Etch and was unable to boot up the new kernel package. It failed to mount my root partition. Please provide a complete log and informations about the hardware. You may also try to specify rootdelay=10 on the kernel commandline. Closing due to lack of response. ---End Message---
Bug#556433: [squeeze] 3c59x: NETDEV WATCHDOG: transmit timed out
Jonathan Nieder wrote: Steve Karg wrote: Do you get the timeouts with a 3.x kernel from sid or experimental? If so, please report this to the net...@vger.kernel.org list, attaching dmesg output from bootup and cc-ing Steffen Klassert klass...@mathematik.tu-chemnitz.de in case he has driver-specific insights plus this bug log so we can track it. I will try that when I get some free time. I starred this in my gmail inbox. :-) I'm just curious: did you get a chance to try 3.x.y from sid? Friendly ping. :) The 3.x.y kernel from sid or squeeze-backports should work fine on a squeeze system. The only packages needed from outside squeeze to try it are the kernel image itself, linux-base, and initramfs-tools. Thanks, Jonathan -- 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/20120520044738.GA10930@burratino
Bug#584314: base: System freezes at random time after Resume from Suspend (Regression)
Hi Andreas, Jonathan Nieder wrote: Andreas Berger wrote: ok, i narrowed it down, but it is: found: linux-image-2.6.36-trunk-686, version 2.6.36-1~experimental.1 not found: linux-image-2.6.37-rc4-686, version 2.6.37~rc4-1~experimental.1 Unfortunately there are a lot of interesting patches in that range, so we will probably need a little more data to track this down. So I suggested: [...] - suspending from single-user mode (kernel params single debug) or from an initramfs shell (kernel param break=top) to see if the same problem occurs even if the i915 driver is not loaded yet when the suspend/hibernate happens Thanks again for all your help narrowing the bug down this far. Did you get a chance to try this? Curious, Jonathan -- 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/20120520053210.GA6@burratino
Bug#585910: marked as done (linux-2.6: Blank screen at startup with 'Intel Corporation Core Processor Integrated Graphics Controller')
Your message dated Sun, 20 May 2012 00:34:38 -0500 with message-id 20120520053438.GA11249@burratino and subject line Re: Switch to i915/KMS leaves console unusable has caused the Debian Bug report #585625, regarding linux-2.6: Blank screen at startup with 'Intel Corporation Core Processor Integrated Graphics Controller' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 585625: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=585625 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-10 Severity: important Hello, kernel maintainers, Kernel version since 2.6.32-10 gets blank screen at startup on a thinkpad X201i laptop which comes with an Intel Corporation Core Processor Integrated Graphics Controller. Kernel parameter 'i915.modeset=0' solved the blank screen at startup, but machine got hangs up after initrd loaded while starting up services. The output of 'lspci -n' indicate this Intel Corporation Core Processor Integrated Graphics Controller is: 00:02.0 0300: 8086:0046 (rev 02) And the output of 'lspci -x': 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) 00: 86 80 46 00 07 04 90 00 02 00 00 03 00 00 00 00 10: 04 00 00 f2 00 00 00 00 0c 00 00 d0 00 00 00 00 20: 01 18 00 00 00 00 00 00 00 00 00 00 aa 17 5a 21 30: 00 00 00 00 90 00 00 00 00 00 00 00 0b 01 00 00 This problem can be easily reproduced with later version even with 2.6.34-1~experimental.2, but cannot be reproduced with 2.6.32-9. I am luckly got such a machine here, I'd glad to help on further tests. Best regards, -Andrew -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-3-amd64 (SMP w/4 CPU cores) Locale: LANG=zh_TW.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Jonathan Nieder wrote: Do you still have access to this hardware? Closing due to lack of response. ---End Message---
Bug#586133: marked as done (linux-image-2.6.32-5-amd64: Boot process pauses indefinitely waiting for keyboard activity)
Your message dated Sun, 20 May 2012 00:43:25 -0500 with message-id 20120520054325.GA11353@burratino and subject line Re: Boot process pauses indefinitely waiting for keyboard activity has caused the Debian Bug report #586133, regarding linux-image-2.6.32-5-amd64: Boot process pauses indefinitely waiting for keyboard activity to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 586133: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586133 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-15 Severity: critical Tags: d-i squeeze Justification: breaks the whole system The kernel pauses waiting for any keyboard input early* in the boot process. Pressing any key during this pause causes the kernel to continue booting normally. There is no error message present when this pause happens, and it occurs also later in the boot process (after loading NFS for example). * The pause first happens after the following lines in the kernel log: [1.352116] usb 1-2: new high speed USB device using ehci_hcd and address 3 [1.372150] usb usb7: New USB device found, idVendor=1d6b, idProduct=0001 [1.372206] usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [1.372270] usb usb7: Product: OHCI Host Controller [1.372323] usb usb7: Manufacturer: Linux 2.6.32-5-amd64 ohci_hcd [1.372378] usb usb7: SerialNumber: :00:14.5 [1.372490] usb usb7: configuration #1 chosen from 1 choice [1.372567] hub 7-0:1.0: USB hub found [PAUSE HAPPENS HERE - I PRESSED SHIFT AFTER ABOUT 12 SECONDS] [ 14.302853] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 14.302901] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 14.324384] usb 1-2: New USB device found, idVendor=058f, idProduct=6362 [ 14.324442] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 14.324499] usb 1-2: Product: Mass Storage Device [ 14.324556] usb 1-2: Manufacturer: Generic [ 14.324608] usb 1-2: SerialNumber: 058F312D81A [ 14.324732] usb 1-2: configuration #1 chosen from 1 choice -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-15) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-1) ) #1 SMP Tue Jun 1 04:34:03 UTC 2010 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 root=/dev/mapper/vg0-root ro rootdelay=60 ** Not tainted ** Kernel log: [ 79.290926] EDAC amd64_edac: Ver: 3.2.0 Jun 1 2010 [ 79.310435] [drm] nouveau :01:00.0: ... appears to be valid [ 79.310491] [drm] nouveau :01:00.0: BIT BIOS found [ 79.310545] [drm] nouveau :01:00.0: Bios version 60.84.35.00 [ 79.310608] [drm] nouveau :01:00.0: TMDS table revision 2.0 not currently supported [ 79.310672] [drm] nouveau :01:00.0: BIT table 'd' not found [ 79.310727] [drm] nouveau :01:00.0: Found Display Configuration Block version 4.0 [ 79.310792] [drm] nouveau :01:00.0: DCB connector table: VHER 0x40 5 14 2 [ 79.310848] [drm] nouveau :01:00.0: 0: 0x2030: type 0x30 idx 0 tag 0x08 [ 79.310916] [drm] nouveau :01:00.0: 1: 0x1130: type 0x30 idx 1 tag 0x07 [ 79.310989] [drm] nouveau :01:00.0: 2: 0x0210: type 0x10 idx 2 tag 0xff [ 79.311061] [drm] nouveau :01:00.0: 3: 0x0211: type 0x11 idx 2 tag 0xff [ 79.311130] [drm] nouveau :01:00.0: 4: 0x0213: type 0x13 idx 2 tag 0xff [ 79.311194] [drm] nouveau :01:00.0: Raw DCB entry 0: 02000300 0028 [ 79.311251] [drm] nouveau :01:00.0: Raw DCB entry 1: 01000302 00020030 [ 79.311306] [drm] nouveau :01:00.0: Raw DCB entry 2: 04011310 0028 [ 79.311362] [drm] nouveau :01:00.0: Raw DCB entry 3: 02011312 00020030 [ 79.311417] [drm] nouveau :01:00.0: Raw DCB entry 4: 010223f1 00c0c080 [ 79.311478] [drm] nouveau :01:00.0: Parsing VBIOS init table 0 at offset 0xBDC4 [ 79.331512] EDAC amd64: This node reports that Memory ECC is currently disabled, set F3x44[22] (:00:18.3). [ 79.331656] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. [ 79.331657] Either enable ECC checking or force module loading by setting 'ecc_enable_override'. [ 79.331658] (Note that use of the override may cause unknown side effects.) [ 79.331872] amd64_edac: probe of :00:18.2 failed with error -22 [ 79.354705] HDA Intel :00:14.2: PCI INT A - GSI 16 (level, low) - IRQ 16 [ 79.360137] [drm] nouveau :01:00.0: Parsing VBIOS init table 1 at offset 0xC0E7 [ 79.360526] 8:3:1: cannot get freq at ep 0x84 [ 79.368241]
Bug#589558: Miscalculation of used/available pages on kernel suspend to disk (not suspending)
Hi again, Jonathan Nieder wrote: Javier Vasquez wrote: MemTotal: 514432 kB SwapTotal: 2096408 kB [...] [ 92.796017] PM: Need to copy 66237 pages [ 92.796017] PM: Normal pages needed: 66237 + 1024, available pages: 64647 [ 92.796017] PM: Not enough free memory [ 92.796017] PM: Error -12 creating hibernation image Yeah, that looks broken. Ping. Do you still have access to a system reproducing this bug? Are you still interested in pursuing it? If not, that's fine, but please do let us know so we can plan accordingly. Thanks, Jonathan -- 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/20120520055041.GA11547@burratino
