Bug#668547: Same problem here.
Hi. I'm experencing same problem here. I can not use reportbug when connected, reportbug email is below. Victor. Subject: linux-image-3.2.0-2-amd64: Same problem as #668547 Package: linux-2.6 Version: 3.2.16-1 Severity: normal *** Please type your report below this line *** Hi. After upgrading to 3.2.0.2 wireless connection disconnects too much often, sometimes it does not connect and some others its speed does not even allow to email reading. When it does not connect it is usual to see in the logs May 4 09:14:30 chiquitin kernel: [ 1765.778754] wlan0: authenticated May 4 09:14:30 chiquitin kernel: [ 1765.814156] wlan0: associate with 88:25:2c:92:3d:aa (try 1) May 4 09:14:30 chiquitin kernel: [ 1765.840670] wlan0: RX AssocResp from 88:25:2c:92:3d:aa (capab=0x421 status=0 aid=1) May 4 09:14:30 chiquitin kernel: [ 1765.840673] wlan0: associated but it seems to be that dhcp does not receive any package. using static ip does not fix this, nor using a different dhcp client (I've tried pump and dhclient, now I'm using dhcpcd) I think the problem is related to the Invalid misc field. Now it's 384, but it is usually over 10.000 (although I have not seen 40.000, it disconnects before always). $ iwconfig lono wireless extensions. wwan0 no wireless extensions. wlan0 IEEE 802.11abg ESSID:WiFi_Et_Mi_Casa Mode:Managed Frequency:2.472 GHz Access Point: 88:25:2C:92:3D:AA Bit Rate=36 Mb/s Tx-Power=15 dBm Retry long limit:7 RTS thr:off Fragment thr:off Power Management:off Link Quality=53/70 Signal level=-57 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:384 Missed beacon:0 eth0 no wireless extensions. I've tried disabling wifi-N and some other options with no luck. This is the one giving me the best performance (at least it connects). $ cat /etc/modprobe.d/iwlagn-iwlwifi-options.conf # From https://bugs.launchpad.net/ubuntu/+source/linux/+bug/548992 # From https://bugzilla.redhat.com/show_bug.cgi?format=multipleid=716602 # options iwlagn ack_check=1 fw_restart=1 11n_disable=1 options iwlwifi ack_check=1 fw_restart=1 11n_disable=1 # plcp_check=0 bt_coex_active=0 And even disabling IPv6: cat /etc/default/grub # If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. GRUB_DEFAULT=0 GRUB_TIMEOUT=10 GRUB_DISTRIBUTOR=`lsb_release -i -s 2 /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT=nosplash noquiet acpi_backlight=vendor ipv6.disable=1 resume=UUID=d499e746-95bc-478d-9f10-f6416becc142 GRUB_CMDLINE_LINUX=nosplash noquiet acpi_backlight=vendor ipv6.disable=1 resume=UUID=d499e746-95bc-478d-9f10-f6416becc142 ... I've tried too to switch between WPA2, WPA1, WEP and no encryption. The last disconnects less times (I'm using it now), but there is no huge difference between them. -- Package-specific info: ** Version: Linux version 3.2.0-2-amd64 (Debian 3.2.16-1) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Mon Apr 30 05:20:23 UTC 2012 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-2-amd64 root=UUID=bf4cba67-e87c-4ca6-a2bc-ba1b2c55114c ro nosplash noquiet acpi_backlight=vendor ipv6.disable=1 resume=UUID=d499e746-95bc-478d-9f10-f6416becc142 nosplash noquiet acpi_backlight=vendor ipv6.disable=1 resume=UUID=d499e746-95bc-478d-9f10-f6416becc142 ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [8.883544] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [8.883582] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [8.883621] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) [8.883659] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [8.965498] snd_hda_intel :00:1b.0: PCI INT B - GSI 17 (level, low) - IRQ 17 [8.967493] snd_hda_intel :00:1b.0: irq 48 for MSI/MSI-X [8.967523] snd_hda_intel :00:1b.0: setting latency timer to 64 [8.983710] input: Logitech Optical USB Mouse as /devices/pci:00/:00:1d.0/usb6/6-2/6-2:1.0/input/input9 [8.986182] generic-usb 0003:046D:C016.0001: input,hidraw0: USB HID v1.10 Mouse [Logitech Optical USB Mouse] on usb-:00:1d.0-2/input0 [8.988251] usbcore: registered new interface driver usbhid [8.990265] usbhid: USB HID core driver [9.088990] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input10 [9.094502] input: HDA Intel Mic as /devices/pci:00/:00:1b.0/sound/card0/input11 [9.096632] input: HDA Intel Mic as /devices/pci:00/:00:1b.0/sound/card0/input12 [9.098890] input: HDA Intel Headphone as /devices/pci:00/:00:1b.0/sound/card0/input13 [ 11.813863] Adding 8189948k swap on /dev/sda6. Priority:-1 extents:1 across:8189948k [ 12.268729] EXT3-fs (sda3): using internal journal [ 12.797911] loop: module loaded [
Bug#671292: [bug?] [powerpc] hid_logitech_dj: Wireless mouse does not work in xorg or gpm
Hugo Osvaldo Barrera wrote: Here goes, I'm pretty sure a few of the first lines aren't relevant, but I prefer to send a couple too many instead of a couple to few :) Thanks! That was fast. I'd also be interested in the corresponding output from an Intel architecture machine with the same kernel version for comparison. I'm hoping some obvious difference will jump out --- otherwise I or some other reader will have to look at the actual code. ;-) Hope that helps, 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/20120504074137.GB6451@burratino
Bug#596741: regression: CPU fan fast after resume: won't climb back down (patch from upstream)
On Thu, Apr 26, 2012 at 02:59:29PM -0500, Jonathan Nieder wrote: Even easier is testing using the upstream source. It works like this: Thanks again for the detailed instructions. They really are a help. I was not aware this was possible for the debian flavours. Good stuff. 2. Fetch point release (KMS variant): cd linux git remote add squeeze-drm \ git://git.kernel.org/pub/scm/linux/kernel/git/smb/linux-2.6.32.y-drm33.z.git git fetch squeeze-drm 3. Configure, build, and test: git checkout squeeze-drm/master cp /boot/config-2.6.32-5-* .config; # stock configuration scripts/config --disable DEBUG_INFO make localmodconfig; # optional: minimize configuration make deb-pkg; # optionally with -jnum for parallel build dpkg -i ../name of package; # as root Hopefully it reproduces the problem. So: Alas no â the patch which fixes the issue has already been applied to this branch. So this worked ⺠I haven't tried reverting it to reproduce the issue again, yet, but I can if you want. -- 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/20120504075522.ga18...@ubik.ncl.ac.uk
Bug#596741: regression: CPU fan fast after resume: won't climb back down (patch from upstream)
Jon Dowland wrote: 3. Configure, build, and test: git checkout squeeze-drm/master [...] Alas no — the patch which fixes the issue has already been applied to this branch. So this worked ☺ Thanks. Interesting. What does git log -1 --oneline squeeze-drm/master show? (For me it says ba52a5bbe327 Linux 2.6.32.59.) Does git show squeeze-drm/master:drivers/gpu/drm/radeon/atom.c | grep ATOM_CMD_SPDFANCNTL yield any results? (For me it doesn't.) Does kernel modesetting seem to be working? dmesg output from booting and suspending would also be interesting. Puzzled, 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/20120504081029.GD6451@burratino
Bug#671292: [bug?] [powerpc] hid_logitech_dj: Wireless mouse does not work in xorg or gpm
On 2012.05.04 02:41, Jonathan Nieder wrote: Hugo Osvaldo Barrera wrote: Here goes, I'm pretty sure a few of the first lines aren't relevant, but I prefer to send a couple too many instead of a couple to few :) Thanks! That was fast. I'd also be interested in the corresponding output from an Intel architecture machine with the same kernel version for comparison. I'm hoping some obvious difference will jump out --- otherwise I or some other reader will have to look at the actual code. ;-) Hope that helps, Jonathan Here you go - *I* certainly can't make anything out of it, but hope it helps :) $ uname -a Linux hyperion 3.3.2-1-ARCH #1 SMP PREEMPT Sat Apr 14 09:48:37 CEST 2012 x86_64 AMD Phenom(tm) II X4 945 Processor AuthenticAMD GNU/Linux dmesg: The following ONE line repeated itself 272 times. I've snipped it for readability [335294.173474] drivers/hid/hid-logitech-dj.c: logi_dj_raw_event, size:15 [335294.173485] drivers/hid/hid-logitech-dj.c: logi_dj_ll_input_event: usb-:00:12.1-3:1, type:4 | code:4 | value:589825 [335294.277432] drivers/hid/hid-logitech-dj.c: logi_dj_raw_event, size:15 [335294.277442] drivers/hid/hid-logitech-dj.c: logi_dj_ll_input_event: usb-:00:12.1-3:1, type:4 | code:4 | value:589825 The following ONE line repeated itself 94 times. I've snipped it for readability [335295.841399] drivers/hid/hid-logitech-dj.c: logi_dj_raw_event, size:15 [335295.841407] drivers/hid/hid-logitech-dj.c: logi_dj_ll_input_event: usb-:00:12.1-3:1, type:4 | code:4 | value:589825 [335295.945386] drivers/hid/hid-logitech-dj.c: logi_dj_raw_event, size:15 [335295.945395] drivers/hid/hid-logitech-dj.c: logi_dj_ll_input_event: usb-:00:12.1-3:1, type:4 | code:4 | value:589825 The following ONE line repeated itself 110 times. I've snipped it for readability [335307.282816] drivers/hid/hid-logitech-dj.c: logi_dj_raw_event, size:15 snipped some nvidia related stuff The following ONE line repeated itself 71 times. I've snipped it for readability [335313.294547] drivers/hid/hid-logitech-dj.c: logi_dj_raw_event, size:15 [335313.294559] drivers/hid/hid-logitech-dj.c: logi_dj_ll_input_event: usb-:00:12.1-3:1, type:4 | code:4 | value:589827 [335313.446544] drivers/hid/hid-logitech-dj.c: logi_dj_raw_event, size:15 [335313.446558] drivers/hid/hid-logitech-dj.c: logi_dj_ll_input_event: usb-:00:12.1-3:1, type:4 | code:4 | value:589827 The following ONE line repeated itself 65 times. I've snipped it for readability [335317.788350] drivers/hid/hid-logitech-dj.c: logi_dj_raw_event, size:15 [335317.788360] drivers/hid/hid-logitech-dj.c: logi_dj_ll_input_event: usb-:00:12.1-3:1, type:4 | code:4 | value:589825 The following ONE line repeated itself 22 times. I've snipped it for readability [335318.044338] drivers/hid/hid-logitech-dj.c: logi_dj_raw_event, size:15 [335318.044350] drivers/hid/hid-logitech-dj.c: logi_dj_ll_input_event: usb-:00:12.1-3:1, type:4 | code:4 | value:589825 The following ONE line repeated itself 52 times. I've snipped it for readability [335324.738080] drivers/hid/hid-logitech-dj.c: logi_dj_raw_event, size:15 [335324.738089] drivers/hid/hid-logitech-dj.c: logi_dj_ll_input_event: usb-:00:12.1-3:1, type:4 | code:4 | value:589827 The following ONE line repeated itself 32 times. I've snipped it for readability [335325.068018] drivers/hid/hid-logitech-dj.c: logi_dj_raw_event, size:15 [335325.068030] drivers/hid/hid-logitech-dj.c: logi_dj_ll_input_event: usb-:00:12.1-3:1, type:4 | code:4 | value:589827 The following ONE line repeated itself 30 times. I've snipped it for readability [335325.544000] drivers/hid/hid-logitech-dj.c: logi_dj_raw_event, size:15 [335325.544012] drivers/hid/hid-logitech-dj.c: logi_dj_ll_input_event: usb-:00:12.1-3:1, type:4 | code:4 | value:589825 The following ONE line repeated itself 60 times. I've snipped it for readability [335326.485953] drivers/hid/hid-logitech-dj.c: logi_dj_raw_event, size:15 [335326.485964] drivers/hid/hid-logitech-dj.c: logi_dj_ll_input_event: usb-:00:12.1-3:1, type:4 | code:4 | value:589825 The following ONE line repeated itself 418 times. I've snipped it for readability [335344.725114] drivers/hid/hid-logitech-dj.c: logi_dj_raw_event, size:15 [335344.725123] drivers/hid/hid-logitech-dj.c: logi_dj_ll_input_event: usb-:00:12.1-3:1, type:4 | code:4 | value:589825 [335344.821117] drivers/hid/hid-logitech-dj.c: logi_dj_raw_event, size:15 [335344.821127] drivers/hid/hid-logitech-dj.c: logi_dj_ll_input_event: usb-:00:12.1-3:1, type:4 | code:4 | value:589825 The following ONE line repeated itself 60 times. I've snipped it for readability [335346.279100] drivers/hid/hid-logitech-dj.c: logi_dj_raw_event, size:15 [335346.279110] drivers/hid/hid-logitech-dj.c: logi_dj_ll_input_event: usb-:00:12.1-3:1, type:4 | code:4 | value:589825 [335346.351039] drivers/hid/hid-logitech-dj.c: logi_dj_raw_event, size:15 [335346.351050] drivers/hid/hid-logitech-dj.c:
Bug#669006: closed by Jonathan Nieder jrnie...@gmail.com (Re: ata_piix poor performance on ich5)
: After replacing this disc, the speed issues are history. : : Thanks for the update. Closing. : : The cpu burning is related to NFSv4, after reconfigured to use NFSv3 : my file server is working smoothly. Maybe a bit more detail... The faulty hd made the system behave like without dma, so I was able to make cpu consumption up to 80-100 % even without NFS. But with NFSv4 the system totally slowed down. : I'd be interested to learn more about what happened there so it can : get fixed. Did I understand correctly that with a squeeze kernel : NFSv4 writes do not increase nfsd CPU consumption very much, while : with a wheezy kernel it provokes near 100% CPU consumption? I don't really know, didn't benchmark the new wheezy system over NFS with the squeeze kernel. But occasionally on wheezy, multiple instances of nfsd seem to use all of the cpu time, when configured as NFSv4. I can trigger it anytime on my setup by transfering big files, any vdr recording will do. They are usually 500MB..2TB in size. : If you have time, I suppose I'd suggest filing a new bug with a : summary of the problem. I'm not surprised if there is already one, because someone in #debian.fi@ircnet already told he had to use NFSv3 to get rid of his problems - before I even upgraded to wheezy. If I have the time, I might dig deeper. -- Teemu -- 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/20120504081403.ga15...@tambu.hopto.org
Bug#671292: [bug?] [powerpc] hid_logitech_dj: Wireless mouse does not work in xorg or gpm
On 2012-05-04 05:10, Hugo Osvaldo Barrera wrote: On 2012.05.04 02:41, Jonathan Nieder wrote: Hugo Osvaldo Barrera wrote: Here goes, I'm pretty sure a few of the first lines aren't relevant, but I prefer to send a couple too many instead of a couple to few :) Thanks! That was fast. I'd also be interested in the corresponding output from an Intel architecture machine with the same kernel version for comparison. I'm hoping some obvious difference will jump out --- otherwise I or some other reader will have to look at the actual code. ;-) Hope that helps, Jonathan Here you go - *I* certainly can't make anything out of it, but hope it helps :) $ uname -a Linux hyperion 3.3.2-1-ARCH #1 SMP PREEMPT Sat Apr 14 09:48:37 CEST 2012 x86_64 AMD Phenom(tm) II X4 945 Processor AuthenticAMD GNU/Linux dmesg: snip Oh, it slipped my mind and I used the other (identical) mouse for this, does that matter? They're the exact same model. -- Hugo Osvaldo Barrera -- 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/4fa38ffd.6080...@osvaldobarrera.com.ar
Bug#671292: [bug?] [powerpc] hid_logitech_dj: Wireless mouse does not work in xorg or gpm
Hugo Osvaldo Barrera wrote: Oh, it slipped my mind and I used the other (identical) mouse for this, does that matter? They're the exact same model. Probably doesn't matter, but thanks for mentioning it. Sincerely, 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/20120504083605.GI6451@burratino
Bug#669006: NFSv4: high cpu usage in nfsd compared to NFSv3 (Re: ata_piix poor performance on ich5)
Teemu wrote: : If you have time, I suppose I'd suggest filing a new bug with a : summary of the problem. I'm not surprised if there is already one, because someone in #debian.fi@ircnet already told he had to use NFSv3 to get rid of his problems - before I even upgraded to wheezy. If I have the time, I might dig deeper. Excellent. No need to worry about looking for duplicates, at least at first --- a self-contained report with enough information to start talking to upstream would be quite enough. 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/20120504083935.GJ6451@burratino
Processed (with 1 errors): Re: [squeeze - 2.6.36 regression] holes in characters rendered on screen in X
Processing commands for cont...@bugs.debian.org: Version: 2:2.17.0+git20120101-1 Unknown command or malformed arguments to command. tags 606939 - moreinfo + unreproducible Bug #606939 [linux-2.6] linux-image-2.6.36-trunk-686: holes in characters rendered on screen in X Removed tag(s) moreinfo. Bug #606939 [linux-2.6] linux-image-2.6.36-trunk-686: holes in characters rendered on screen in X Added tag(s) unreproducible. # approximating: sid as of 13 December 2010 reassign 606939 xserver-xorg-video-intel 2:2.13.0-2 Bug #606939 [linux-2.6] linux-image-2.6.36-trunk-686: holes in characters rendered on screen in X Bug reassigned from package 'linux-2.6' to 'xserver-xorg-video-intel'. No longer marked as found in versions 2.6.36-1~experimental.1 and linux-2.6/3.2.1-2. Ignoring request to alter fixed versions of bug #606939 to the same values previously set Bug #606939 [xserver-xorg-video-intel] linux-image-2.6.36-trunk-686: holes in characters rendered on screen in X Marked as found in versions xserver-xorg-video-intel/2:2.13.0-2. # guessing: because SNA was disabled in this version found 606939 xserver-xorg-video-intel/2:2.18.0-1 Bug #606939 [xserver-xorg-video-intel] linux-image-2.6.36-trunk-686: holes in characters rendered on screen in X Marked as found in versions xserver-xorg-video-intel/2:2.18.0-1. forwarded 606939 https://bugzilla.kernel.org/26002#c13 Bug #606939 [xserver-xorg-video-intel] linux-image-2.6.36-trunk-686: holes in characters rendered on screen in X Set Bug forwarded-to-address to 'https://bugzilla.kernel.org/26002#c13'. affects 606939 + src:linux-2.6 Bug #606939 [xserver-xorg-video-intel] linux-image-2.6.36-trunk-686: holes in characters rendered on screen in X Added indication that 606939 affects src:linux-2.6 # squeeze kernel worked fine tags 606939 + wheezy sid experimental Bug #606939 [xserver-xorg-video-intel] linux-image-2.6.36-trunk-686: holes in characters rendered on screen in X Added tag(s) sid, wheezy, and experimental. quit Stopping processing here. Please contact me if you need assistance. -- 606939: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606939 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.13361224276202.transcr...@bugs.debian.org
Bug#670958: [regression] HP laptops: udev/power_supply battery oscilates between remove and add
tags 670958 + patch moreinfo
quit
Hi all,
Andy Whitcroft wrote[1]:
Based on Matthew's feedback here is a version which optimises
based on the power_unit field as returned from the battery info.
Could someone who suffers from this issue please test this out
and report back. Thanks.
Instructions:
0. prerequisites:
apt-get install git build-essential
1. get a copy of the kernel history, if you don't already have it:
git clone \
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
2. add point releases:
cd linux
git remote add stable \
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
git fetch stable
3. configure, build, test:
git checkout stable/linux-3.2.y
cp /boot/config-$(uname -r) .config; # current configuration
scripts/config --disable DEBUG_INFO
make localmodconfig; # optional: minimize configuration
make deb-pkg; # optionally with -jnum for parallel build
dpkg -i ../name of package; # as root
reboot
... test test test ...
Hopefully it reproduces the bug. So:
4. try the patch (attached):
cd linux
git am -3sc /path/to/patch
make deb-pkg; # maybe with -j4
dpkg -i ../name of package; # as root
reboot
... test test test ...
An alternative set of instructions is at [2].
If you get a chance to try this, please describe the result to Andy by
replying-to-all to his message (i.e., not this one). Whoever is first
should probably also mention that pertinent is misspelled. ;-) If you
have any questions, please don't hesitate to ask.
Thanks,
Jonathan
[1] http://thread.gmane.org/gmane.linux.kernel/1084565/focus=52981
[2] http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s4.2.2
or the corresponding page in the debian-kernel-handbook package
From: Andy Whitcroft a...@canonical.com
Date: Thu, 3 May 2012 14:48:26 +0100
Subject: battery: only refresh the sysfs files when pertinant information
changes
We only need to regenerate the sysfs files when the capacity units
change, avoid the update otherwise.
Signed-off-by: Andy Whitcroft a...@canonical.com
Signed-off-by: Jonathan Nieder jrnie...@gmail.com
---
drivers/acpi/battery.c | 10 +-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/drivers/acpi/battery.c b/drivers/acpi/battery.c
index 7711d94a0409..55354777e696 100644
--- a/drivers/acpi/battery.c
+++ b/drivers/acpi/battery.c
@@ -643,11 +643,19 @@ static int acpi_battery_update(struct acpi_battery
*battery)
static void acpi_battery_refresh(struct acpi_battery *battery)
{
+ int power_unit;
+
if (!battery-bat.dev)
return;
+ power_unit = battery-power_unit;
+
acpi_battery_get_info(battery);
- /* The battery may have changed its reporting units. */
+
+ if (power_unit == battery-power_unit)
+ return;
+
+ /* The battery has changed its reporting units. */
sysfs_remove_battery(battery);
sysfs_add_battery(battery);
}
--
1.7.10.1
Processed: Re: [regression] HP laptops: udev/power_supply battery oscilates between remove and add
Processing commands for cont...@bugs.debian.org: tags 670958 + patch moreinfo Bug #670958 [src:linux-2.6] [regression] HP ProBook 451x: udev/power_supply battery oscilates between remove and add Bug #638970 [src:linux-2.6] [regression] HP ProBook 451x: udev/power_supply battery oscilates between remove and add Added tag(s) moreinfo and patch. Added tag(s) moreinfo and patch. quit Stopping processing here. Please contact me if you need assistance. -- 638970: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638970 670958: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670958 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.133612583624721.transcr...@bugs.debian.org
Bug#671292: [bug?] [powerpc] hid_logitech_dj: Wireless mouse does not work in xorg or gpm
Hi guys, Thanks for those logs, very helpful. Would you be able to test the following patch on both systems and let us know about the result? Cheers, Nestor diff --git a/drivers/hid/hid-logitech-dj.c b/drivers/hid/hid-logitech-dj.c index 38b12e4..763e4d9 100644 --- a/drivers/hid/hid-logitech-dj.c +++ b/drivers/hid/hid-logitech-dj.c @@ -215,6 +215,7 @@ static void logi_dj_recv_add_djhid_device(struct dj_receiver_dev *djrcv_dev, struct usb_device *usbdev = interface_to_usbdev(intf); struct hid_device *dj_hiddev; struct dj_device *dj_dev; + u32 reports_supported; /* Device index goes from 1 to 6, we need 3 bytes to store the * semicolon, the index, and a null terminator @@ -264,9 +265,11 @@ static void logi_dj_recv_add_djhid_device(struct dj_receiver_dev *djrcv_dev, __func__); goto dj_device_allocate_fail; } + memcpy(reports_supported, + dj_report-report_params[DEVICE_PAIRED_RF_REPORT_TYPE], + sizeof(reports_supported)); - dj_dev-reports_supported = le32_to_cpu( - dj_report-report_params[DEVICE_PAIRED_RF_REPORT_TYPE]); + dj_dev-reports_supported = le32_to_cpu(reports_supported); dj_dev-hdev = dj_hiddev; dj_dev-dj_receiver_dev = djrcv_dev; dj_dev-device_index = dj_report-device_index; On Fri, May 4, 2012 at 10:36 AM, Jonathan Nieder jrnie...@gmail.com wrote: Hugo Osvaldo Barrera wrote: Oh, it slipped my mind and I used the other (identical) mouse for this, does that matter? They're the exact same model. Probably doesn't matter, but thanks for mentioning it. Sincerely, 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/CAE7qMrpWMJ=u3h3bbkxxgsknnng7zurs44euh0_lzhq6ucb...@mail.gmail.com
Bug#671292: [bug?] [powerpc] hid_logitech_dj: Wireless mouse does not work in xorg or gpm
Nestor Lopez Casado wrote: Would you be able to test the following patch on both systems and let us know about the result? Instructions for Hugo: # prerequisites apt-get install git build-essential # get the kernel history, if you don't already have it git clone \ git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git # latest mainline kernel cd linux git fetch origin git checkout origin/master # configure cp /boot/config-$(uname -r) .config; # current configuration scripts/config --disable DEBUG_INFO; # smaller build make localmodconfig; # minimize configuration # apply patch git apply --index /path/to/patch # build make deb-pkg; # optionally with -jnum for parallel build # test dpkg -i ../name of package; # as root reboot # to unapply patch: cd linux git reset --hard origin/master # when you want to build again: make deb-pkg; # maybe with -j4 dpkg -i ../name of package; # as root reboot I would also be interested in a capture of the pairing event, if possible: (remove mouse battery or bring mouse out of range) mount -t debugfs debugfs /sys/kernel/debug ls /sys/kernel/debug/hid/ modprobe -r hid_logitech_dj modprobe hid_logitech_dj cat /sys/kernel/debug/hid/device name/events events.captured (insert mouse battery or bring mouse within range) ^C 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/20120504104902.GA7766@burratino
Bug#670958: [regression] HP laptops: udev/power_supply battery oscilates between remove and add
Hi, An alternative set of instructions is at [2]. If you get a chance to try this, please describe the result to Andy by replying-to-all to his message (i.e., not this one). Whoever is first should probably also mention that pertinent is misspelled. ;-) If you have any questions, please don't hesitate to ask. Done, and it is working great, thanks a lot :) (I forgot to put the bug in CC in my replay...) I could not find the word pertinent anywhere in the patch though... maybe I'm blind^^ Kind regards, Ralf -- 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/201205041530.30115.p...@ralfj.de
Processed: tagging 669120
Processing commands for cont...@bugs.debian.org: tags 669120 + pending Bug #669120 [src:linux-2.6] [s390] unreliable timekeeping yielding observable time warps Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 669120: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669120 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.13361478181946.transcr...@bugs.debian.org
Re: Squeeze point release (6.0.5)
On Thu, May 03, 2012 at 11:14:38PM +0100, Adam D. Barratt wrote: On Mon, 2012-04-30 at 10:09 -0600, dann frazier wrote: On Mon, Apr 30, 2012 at 04:15:31AM +0100, Ben Hutchings wrote: On Sun, 2012-04-29 at 16:36 +0100, Adam D. Barratt wrote: Is the new version ready for upload? It's looking like the point release will be the 12/13th, so it would be good to have everything ready in p-u by next weekend. I think it's ready, though there may be some security fixes we should throw in as well. Dann? Yeah - there's some security stuff to get in as well; I'll be working on that this week. Thanks for the confirmation. How are things looking? We've got all the changes committed that I think should go in and I'm doing some testing w/ a build this morning. I expect the upload to happen this afternoon. As far as I can see there aren't any changes on d-i's squeeze branch, so I guess we could just binNMU d-i once lkdi-* are sorted? (and then do dini.) Agreed. -- 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/20120504152624.ga26...@dannf.org
Bug with nfs-common 1:1.2.5-4 Debian Testing
Hi. I couldn't find a debian mailing list for this so hopefully I've got this email going to the right place/people. If not, my apologies. I installed nfs-common on a debian testing box yesterday and got the following error: Setting up libgssglue1 (0.3-4) ... Setting up libtirpc1:i386 (0.2.2-5) ... Setting up libnfsidmap2 (0.25-2) ... Setting up rpcbind (0.2.0-7) ... Starting rpcbind daemon Setting up nfs-common (1:1.2.5-4) ... Creating config file /etc/idmapd.conf with new version Creating config file /etc/default/nfs-common with new version Adding system user `statd' (UID 103) ... Adding new user `statd' (UID 103) with group `nogroup' ... Not creating home directory `/var/lib/nfs'. Starting NFS common utilities: statd idmapd failed! invoke-rc.d: initscript nfs-common, action start failed. dpkg: error processing nfs-common (--configure): subprocess installed post-installation script returned error exit status 1 configured to not write apport reports Errors were encountered while processing: nfs-common E: Sub-process /usr/bin/dpkg returned an error code (1) Although I can mount an nfs share and seemingly access the files just fine, I don't know what idmapd is, if it's important, or why it's failing to start. Whatever the case, it probably needs to be fixed, hence the reason for this report. I'm not sure what further info is useful but here's some background on the box: 32bit debian testing stable kernel 3.3.4 nfs client nfs4 (with experimental 4.1 support) compiled into kernel (not as modules) libgssglue1 i386 0.3-4 libtirpc1 i386 0.2.2-5 libnfsidmap2 i386 0.25-2 rpcbind i386 0.2.0-7 nfs-common i386 1:1.2.5-4 Thanks for your help! -- 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/CAA7C2qjP9FpP0ioNq3hEVQG2SpW3=i6petau4ymdcazbiqk...@mail.gmail.com
Bug#671518: linux-image-3.2: snd_hda_codec_hdmi OOPS on load when transparent_hugepage=always is set on kernel commandline
Package: linux-2.6 Version: 3.2.4-1~bpo60+1 Severity: normal File: linux-image-3.2 1. Computer has HDMI port (not in use for display), uses snd_hda_codec_hdmi driver. 2. udev startup loads snd_hda_codec_hdmi at boot. 3. Reboot and add transparent_hugepages=always to kernel commandline. 4. OOPS during boot (after initramfs, during main fs udev startup) inside snd_hda_codec_hdmi. 4a. FS is read-only, don't save oops log. 5. blacklist snd_hda_codec_hdmi. 6. Boots fine. Will test on Intel GMA wheezy system later. -- Package-specific info: ** Version: Linux version 3.2.0-0.bpo.1-amd64 (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 08:41:32 UTC 2012 ** Command line: BOOT_IMAGE=/vmlinuz-3.2.0-0.bpo.1-amd64 root=/dev/mapper/squeeze ro ro transparent_hugepage=always quiet ** Tainted: PO (4097) * Proprietary module has been loaded. * Out-of-tree module has been loaded. ** Kernel log: [ 21.650089] mdadm: sending ioctl 1261 to a partition! [ 21.650092] mdadm: sending ioctl 1261 to a partition! [ 21.655618] [fglrx] Maximum main memory to use for locked dma buffers: 7770 MBytes. [ 21.655798] [fglrx] vendor: 1002 device: 683d count: 1 [ 21.656166] [fglrx] ioport: bar 4, base 0xce00, size: 0x100 [ 21.656176] pci :01:00.0: PCI INT A - GSI 18 (level, low) - IRQ 18 [ 21.656180] pci :01:00.0: setting latency timer to 64 [ 21.656377] [fglrx] Kernel PAT support is enabled [ 21.656388] [fglrx] module loaded - fglrx 8.96.4 [Apr 5 2012] with 1 minors [ 21.670804] MCE: In-kernel MCE decoding enabled. [ 21.683265] EDAC MC: Ver: 2.1.0 [ 21.684349] AMD64 EDAC driver v3.4.0 [ 21.684384] EDAC amd64: DRAM ECC disabled. [ 21.684389] EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load. [ 21.684390] Either enable ECC checking or force module loading by setting 'ecc_enable_override'. [ 21.684391] (Note that use of the override may cause unknown side effects.) [ 21.877030] ACPI: resource piix4_smbus [io 0x0b00-0x0b07] conflicts with ACPI region SOR1 [io 0xb00-0xb0f] [ 21.877033] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 21.899301] SP5100 TCO timer: SP5100 TCO WatchDog Timer Driver v0.01 [ 21.899356] SP5100 TCO timer: mmio address 0xfec000f0 already in use [ 21.982556] snd_emu10k1 :05:06.0: PCI INT A - GSI 20 (level, low) - IRQ 20 [ 21.988642] Installing spdif_bug patch: SB Audigy 2 ZS [SB0350] [ 21.995784] snd_hda_intel :01:00.1: PCI INT B - GSI 19 (level, low) - IRQ 19 [ 21.995827] snd_hda_intel :01:00.1: irq 46 for MSI/MSI-X [ 21.995840] snd_hda_intel :01:00.1: setting latency timer to 64 [ 22.130790] mdadm: sending ioctl 1261 to a partition! [ 22.130793] mdadm: sending ioctl 1261 to a partition! [ 22.132448] mdadm: sending ioctl 1261 to a partition! [ 22.132450] mdadm: sending ioctl 1261 to a partition! [ 22.132976] mdadm: sending ioctl 1261 to a partition! [ 22.132977] mdadm: sending ioctl 1261 to a partition! [ 22.197880] logitech-djreceiver 0003:046D:C52B.0003: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-:00:12.0-3/input2 [ 22.204917] input: Logitech Unifying Device. Wireless PID:1028 as /devices/pci:00/:00:12.0/usb5/5-3/5-3:1.2/0003:046D:C52B.0003/input/input4 [ 22.204997] logitech-djdevice 0003:046D:C52B.0004: input,hidraw1: USB HID v1.11 Mouse [Logitech Unifying Device. Wireless PID:1028] on usb-:00:12.0-3:1 [ 22.717223] EXT4-fs (dm-4): re-mounted. Opts: (null) [ 22.861048] EXT4-fs (dm-4): re-mounted. Opts: user_xattr,errors=remount-ro,commit=60,journal_checksum,stripe=768 [ 22.943906] loop: module loaded [ 22.968951] it87: Found IT8718F chip at 0x228, revision 5 [ 22.968972] it87: Beeping is supported [ 23.047489] sr 11:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 23.047492] sr 11:0:0:0: [sr0] Sense Key : Illegal Request [current] [ 23.047495] sr 11:0:0:0: [sr0] Add. Sense: Illegal mode for this track [ 23.047498] sr 11:0:0:0: [sr0] CDB: Read(10): 28 00 00 03 c3 00 00 00 02 00 [ 23.047502] end_request: I/O error, dev sr0, sector 986112 [ 23.049235] sr 11:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 23.049238] sr 11:0:0:0: [sr0] Sense Key : Illegal Request [current] [ 23.049240] sr 11:0:0:0: [sr0] Add. Sense: Illegal mode for this track [ 23.049243] sr 11:0:0:0: [sr0] CDB: Read(10): 28 00 00 03 c3 1e 00 00 01 00 [ 23.049247] end_request: I/O error, dev sr0, sector 986232 [ 23.267076] sr 11:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 23.267079] sr 11:0:0:0: [sr0] Sense Key : Illegal Request [current] [ 23.267082] sr 11:0:0:0: [sr0] Add. Sense: Illegal mode for this track [ 23.267085] sr 11:0:0:0: [sr0] CDB: Read(10): 28 00 00 03 c3 00 00 00 02 00 [ 23.267089] end_request: I/O error, dev sr0, sector 986112 [
Bug#655385: Solution available for testing and integration
There is a patch solving this problem: http://forum.openvz.org/index.php?t=msgth=10493goto=45496#msg_45496 Using this patch I was able to solve the problem for us. This issue was redirected to the upstream project, so I posted the patches there: http://bugzilla.openvz.org/show_bug.cgi?id=2142#c3 Our test packages are avaiable for interested users: deb http://deb.clazzes.org/debian squeeze-contrib-1 main I'd of course love to see our solution beeing integrated in Debian. Regards, Christoph Lechleitner -- 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/4fa42ed2.6030...@iteg.at
Bug#671200: linux-2.6: Generate leds-modules for Kirkwood Debian installer
On Thu, May 03, 2012 at 11:19:43AM +0100, Martin Michlmayr wrote: * Simon Guinot si...@sequanux.org [2012-04-27 01:15]: On LaCie boards, the leds-ns2 and leds-netxbig drivers are used to configure the LEDs. This drivers are currently not embedded into the network-console installer. As a consequence, it is not possible to change the LEDs behaviour on LaCie boards when the SSH server is ready. Please, consider applying the attached patch. This patch is not correct: --- debian/installer/armel/package-list (revision 18961) +++ debian/installer/armel/package-list (working copy) @@ -5,7 +5,7 @@ # Package: kernel-image Provides_iop32x: rtc-modules -Provides_kirkwood: rtc-modules, jffs2-modules, zlib-modules +Provides_kirkwood: rtc-modules, jffs2-modules, zlib-modules, leds-modules This says that the LEDs moduleas are built-in, which is not the case. You have to create debian/installer/armel/modules/armel-kirkwood/leds-modules with a list of modules. You will find in attachment an updated patch. I'm also not sure about the name leds-modules... maybe they should just be added to input-modules or something but I'll leave that to the kernel/installer team to decide. Index: debian/installer/armel/modules/armel-kirkwood/leds-modules === --- debian/installer/armel/modules/armel-kirkwood/leds-modules (revision 0) +++ debian/installer/armel/modules/armel-kirkwood/leds-modules (revision 0) @@ -0,0 +1,2 @@ +leds-ns2 +leds-netxbig Index: debian/installer/package-list === --- debian/installer/package-list (revision 18961) +++ debian/installer/package-list (working copy) @@ -472,3 +472,9 @@ Priority: extra Description: lzo modules This package contains lzo modules. + +Package: leds-modules +Depends: kernel-image +Priority: extra +Description: LED modules + This package contains LED modules. signature.asc Description: Digital signature
Bug#671518: Update
Was unable to reproduce this on my laptop so it may be related to fglrx or AMD hardware in general. -- 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/201205041651.29571...@wza.us
Processed: Re: random hangups -- BUG: unable to handle kernel paging request at 00007fafb1245388
Processing commands for cont...@bugs.debian.org: reassign 633634 linux-image-2.6.32-5-amd64 Bug #633634 [none] random hangups -- BUG: unable to handle kernel paging request at 7fafb1245388 Warning: Unknown package 'none' Bug reassigned from package 'none' to 'linux-image-2.6.32-5-amd64'. Ignoring request to alter found versions of bug #633634 to the same values previously set Ignoring request to alter fixed versions of bug #633634 to the same values previously set found 633634 2.6.32-34squeeze1 Bug #633634 [linux-image-2.6.32-5-amd64] random hangups -- BUG: unable to handle kernel paging request at 7fafb1245388 Marked as found in versions linux-2.6/2.6.32-34squeeze1. stop Stopping processing here. Please contact me if you need assistance. -- 633634: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633634 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.133617194814435.transcr...@bugs.debian.org
Bug#648751: linux-image-3.0.0-1-rt-amd64: rcu_preempt_state whileshutdown
Hi Uwe, Sorry for the real late response. I installed the kernel you suggested in the same day but I forgot to give my feedback. It solved all my issues, so I think this bugreport should be closed as fixed. I'm currently running 3.2.0 and it's also well so far. Thanks for your help!
Bug#648751: marked as done (linux-image-3.0.0-1-rt-amd64: rcu_preempt_state while shutdown)
Your message dated Sat, 05 May 2012 04:05:02 +0100 with message-id 1336187102.8274.150.camel@deadeye and subject line Re: Bug#648751: linux-image-3.0.0-1-rt-amd64: rcu_preempt_state whileshutdown has caused the Debian Bug report #648751, regarding linux-image-3.0.0-1-rt-amd64: rcu_preempt_state while shutdown 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.) -- 648751: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648751 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 3.0.0-3 Severity: normal Tags: upstream Dear Maintainer, When I shutdown my laptop I get errors like rcu_preempt_state stalled on CPU 1 after Will now halt. message and I can only shutdown if I hold power button. This doesn't happen with kernel 2.6.32-5 from Squeeze. I'll attach a photo later on. Useful info: Dell Vostro 3450, i5 2,3GHz, 4GB of ram (single stick), 500GB of hdd. Debian wheezy -- Package-specific info: ** Version: Linux version 3.0.0-1-rt-amd64 (Debian 3.0.0-3) (b...@decadent.org.uk) (gcc version 4.5.3 (Debian 4.5.3-8) ) #1 SMP PREEMPT RT Sat Aug 27 17:34:31 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.0.0-1-rt-amd64 root=UUID=a7685bc5-e1c1-4864-be73-1a0778773ac6 ro quiet ** Not tainted ** Kernel log: [7.949667] [drm] GART: num cpu pages 131072, num gpu pages 131072 [7.950424] input: Sleep Button as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input3 [7.951448] ACPI: Sleep Button [SLPB] [7.952189] [drm] Loading TURKS Microcode [7.953058] input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input4 [7.953943] ACPI: Lid Switch [LID0] [7.954096] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input5 [7.954197] ACPI: Power Button [PWRF] [7.957385] i915 :00:02.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [7.957389] i915 :00:02.0: setting latency timer to 64 [8.083465] Bluetooth: Generic Bluetooth USB driver ver 0.6 [8.083613] usbcore: registered new interface driver btusb [8.123582] ath9k :02:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [8.123598] ath9k :02:00.0: setting latency timer to 64 [8.140583] input: Dell WMI hotkeys as /devices/virtual/input/input6 [8.150587] Linux media interface: v0.10 [8.175817] ath: EEPROM regdomain: 0x60 [8.175818] ath: EEPROM indicates we should expect a direct regpair map [8.175821] ath: Country alpha2 being used: 00 [8.175822] ath: Regpair used: 0x60 [8.226258] Linux video capture interface: v2.00 [8.240355] uvcvideo: Found UVC 1.00 device Laptop_Integrated_Webcam_FHD (1bcf:2b81) [8.262815] input: Laptop_Integrated_Webcam_FHD as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/input/input7 [8.262935] usbcore: registered new interface driver uvcvideo [8.262937] USB Video Class driver (v1.1.0) [8.269516] Bluetooth: Atheros AR30xx firmware driver ver 1.0 [8.325168] ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control' [8.326680] Registered led device: ath9k-phy0 [8.326687] ieee80211 phy0: Atheros AR9285 Rev:2 mem=0xc900053a, irq=16 [8.385367] ath3k_probe: Error loading firmware [8.385388] ath3k: probe of 4-1.5:1.0 failed with error -5 [8.385842] usbcore: registered new interface driver ath3k [8.423237] radeon :01:00.0: WB enabled [8.439784] [drm] ring test succeeded in 3 usecs [8.440114] [drm] radeon: ib pool ready. [8.440313] [drm] ib test succeeded in 0 usecs [8.442835] [drm] Radeon Display Connectors [8.442853] [drm] Internal thermal controller without fan control [8.443821] [drm] radeon: power management initialized [8.444060] No connectors reported connected with modes [8.444062] [drm] Cannot find any crtc or sizes - going 1024x768 [8.446451] [drm] fb mappable at 0xC0141000 [8.446452] [drm] vram apper at 0xC000 [8.446453] [drm] size 3145728 [8.446454] [drm] fb depth is 24 [8.446455] [drm]pitch is 4096 [8.449527] Console: switching to colour frame buffer device 128x48 [8.452036] fb0: radeondrmfb frame buffer device [8.452038] drm: registered panic notifier [8.452045] [drm] Initialized radeon 2.10.0 20080528 for :01:00.0 on minor 0 [8.540572] i915 :00:02.0: irq 49 for MSI/MSI-X [8.540580] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [8.540582] [drm] Driver supports precise vblank timestamp query. [8.547341] vga_switcheroo: enabled [8.547454] radeon atpx: version is 1 [8.547503] vgaarb:
Bug#648753: marked as done (linux-image-3.0.0-1-rt-amd64: rcu_preempt_state while shutdown)
Your message dated Sat, 05 May 2012 04:05:02 +0100 with message-id 1336187102.8274.150.camel@deadeye and subject line Re: Bug#648751: linux-image-3.0.0-1-rt-amd64: rcu_preempt_state whileshutdown has caused the Debian Bug report #648751, regarding linux-image-3.0.0-1-rt-amd64: rcu_preempt_state while shutdown 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.) -- 648751: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648751 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 3.0.0-3 Severity: normal Dear Maintainer, When I shutdown my laptop I get errors like rcu_preempt_state stalled on CPU 1 after Will now halt. message. I can only shutdown if I hold power button. This doesn't happen with Squeeze kernel 2.6.32-5 I'll attach a photo later on. Thanks in advance. -- Package-specific info: ** Version: Linux version 3.0.0-1-rt-amd64 (Debian 3.0.0-3) (b...@decadent.org.uk) (gcc version 4.5.3 (Debian 4.5.3-8) ) #1 SMP PREEMPT RT Sat Aug 27 17:34:31 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.0.0-1-rt-amd64 root=UUID=a7685bc5-e1c1-4864-be73-1a0778773ac6 ro quiet ** Not tainted ** Kernel log: [7.950424] input: Sleep Button as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input3 [7.951448] ACPI: Sleep Button [SLPB] [7.952189] [drm] Loading TURKS Microcode [7.953058] input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input4 [7.953943] ACPI: Lid Switch [LID0] [7.954096] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input5 [7.954197] ACPI: Power Button [PWRF] [7.957385] i915 :00:02.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [7.957389] i915 :00:02.0: setting latency timer to 64 [8.083465] Bluetooth: Generic Bluetooth USB driver ver 0.6 [8.083613] usbcore: registered new interface driver btusb [8.123582] ath9k :02:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [8.123598] ath9k :02:00.0: setting latency timer to 64 [8.140583] input: Dell WMI hotkeys as /devices/virtual/input/input6 [8.150587] Linux media interface: v0.10 [8.175817] ath: EEPROM regdomain: 0x60 [8.175818] ath: EEPROM indicates we should expect a direct regpair map [8.175821] ath: Country alpha2 being used: 00 [8.175822] ath: Regpair used: 0x60 [8.226258] Linux video capture interface: v2.00 [8.240355] uvcvideo: Found UVC 1.00 device Laptop_Integrated_Webcam_FHD (1bcf:2b81) [8.262815] input: Laptop_Integrated_Webcam_FHD as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/input/input7 [8.262935] usbcore: registered new interface driver uvcvideo [8.262937] USB Video Class driver (v1.1.0) [8.269516] Bluetooth: Atheros AR30xx firmware driver ver 1.0 [8.325168] ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control' [8.326680] Registered led device: ath9k-phy0 [8.326687] ieee80211 phy0: Atheros AR9285 Rev:2 mem=0xc900053a, irq=16 [8.385367] ath3k_probe: Error loading firmware [8.385388] ath3k: probe of 4-1.5:1.0 failed with error -5 [8.385842] usbcore: registered new interface driver ath3k [8.423237] radeon :01:00.0: WB enabled [8.439784] [drm] ring test succeeded in 3 usecs [8.440114] [drm] radeon: ib pool ready. [8.440313] [drm] ib test succeeded in 0 usecs [8.442835] [drm] Radeon Display Connectors [8.442853] [drm] Internal thermal controller without fan control [8.443821] [drm] radeon: power management initialized [8.444060] No connectors reported connected with modes [8.444062] [drm] Cannot find any crtc or sizes - going 1024x768 [8.446451] [drm] fb mappable at 0xC0141000 [8.446452] [drm] vram apper at 0xC000 [8.446453] [drm] size 3145728 [8.446454] [drm] fb depth is 24 [8.446455] [drm]pitch is 4096 [8.449527] Console: switching to colour frame buffer device 128x48 [8.452036] fb0: radeondrmfb frame buffer device [8.452038] drm: registered panic notifier [8.452045] [drm] Initialized radeon 2.10.0 20080528 for :01:00.0 on minor 0 [8.540572] i915 :00:02.0: irq 49 for MSI/MSI-X [8.540580] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [8.540582] [drm] Driver supports precise vblank timestamp query. [8.547341] vga_switcheroo: enabled [8.547454] radeon atpx: version is 1 [8.547503] vgaarb: device changed decodes: PCI::01:00.0,olddecodes=io+mem,decodes=none:owns=none [8.547507] vgaarb: device changed decodes:
Processed: Re: linux-image-3.0.0-1-rt-amd64: rcu_preempt_state whileshutdown
Processing commands for cont...@bugs.debian.org:
tags 648751 - moreinfo
Bug #648751 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6]
linux-image-3.0.0-1-rt-amd64: rcu_preempt_state while shutdown
Bug #648753 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6]
linux-image-3.0.0-1-rt-amd64: rcu_preempt_state while shutdown
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.
fixed 648751 linux-2.6/3.2.16-1
Bug #648751 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6]
linux-image-3.0.0-1-rt-amd64: rcu_preempt_state while shutdown
Bug #648753 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6]
linux-image-3.0.0-1-rt-amd64: rcu_preempt_state while shutdown
Marked as fixed in versions linux-2.6/3.2.16-1.
Marked as fixed in versions linux-2.6/3.2.16-1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
648751: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648751
648753: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648753
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.133619056424637.transcr...@bugs.debian.org
Bug#671518: snd_hda_codec_hdmi OOPS on load when transparent_hugepage=always
Joshua Charles Campbell wrote: Was unable to reproduce this on my laptop so it may be related to fglrx or AMD hardware in general. Thanks for checking. It would be useful to know which of the two: can you reproduce this without the fglrx driver on the machine with a radeon? If so, we can report this upstream and debug it with their help. If not, we can reassign the bug to fglrx-driver and presumably its maintainers would know the proper channels to pass it to AMD. 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/20120505040808.GB2566@burratino
