Bug#684352: HP Pavilion dv4000: Wifi kill switch always on unless ACPI=off is used
Also note that my PC is a Compaq Presario V4000T, it shares a lot of the same hardware as the HP Pavillion DV4000, but there are some hardware differences\. They *might* be using the same BIOS,, I really don't know. They do share the same service/repair manual but they have different replacement part#s. Not sure if that's important for you or not. On Sun, Sep 30, 2012 at 8:31 AM, Jonathan Nieder jrnie...@gmail.com wrote: Hi David, David Smith wrote: Hardware: 6-year old laptop with Pentium-M CPU and Intel 2200 wireless. This is a problem that just started happening after I updated to Wheezy. When I boot my PC with the default Debian kernel for Wheezy and the ipw2x00 firmware package, I get a message saying my wireless killswitch is on. Pressing the Wifi button on my laptop and rebooting gives the same results. I pressed the Wifi button and it doesn't light up like it did in Squeeze or Lenny. The button stays dark. [...] When I turn off the Wifi using the network-manager-kde tool, rfkill then shows this: Miho:/home/david# rfkill list all 0: hp-wifi: Wireless LAN Soft blocked: yes Hard blocked: no 1: phy0: Wireless LAN Soft blocked: yes Hard blocked: yes Miho:/home/david# [...] However, using rfkill unblock all results in this: [...] I can then turn the wifi on again in network-manager-kde and connect to a network in the network-manager-kde tool because it thinks the wifi is no longer hardware blocked. [...] [3.546082] ipw2200: Radio Frequency Kill Switch is On: [3.546084] Kill switch must be turned off for wireless networking to work. Thanks for reporting it, and sorry for the slow response. Some ideas: - please attach acpidump output. - am I correct in imagining 3.5.y from experimental behaves the same way? - does the squeeze (2.6.32.y) kernel avoid trouble? It should work fine on a wheezy/sid system. Next step will be to take this upstream, but let's try to figure out what caused the regression (e.g., which subsystem) first. Hope that helps, Jonathan -- To unsubscribe, send mail to 684352-unsubscr...@bugs.debian.org.
Processed: Re: [Pkg-samba-maint] Bug#689196: cifs-utils: mount.cifs causes kernel crash
Processing commands for cont...@bugs.debian.org: reassign 689196 linux Bug #689196 [cifs-utils] cifs-utils: mount.cifs causes kernel crash Bug reassigned from package 'cifs-utils' to 'linux'. No longer marked as found in versions cifs-utils/2:5.5-1. Ignoring request to alter fixed versions of bug #689196 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 689196: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689196 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.134898555230474.transcr...@bugs.debian.org
Bug#686464: USB3 HDD spontaneously disconnects sporadically
Hi Jonathan, I don't have another USB3 cable, but this one looks okay, and it is brand new - it was included with the USB enclosure. I have been using the disk internally since my report, and I have not found the time to remove it from the server to test a another kernel. As I wrote, this had happened on two entirely different PCs. Regards, Sladjan On Sep 30, 2012 2:42 AM, Jonathan Nieder jrnie...@gmail.com wrote: Hi Sladjan, Ben Hutchings wrote: On Sat, 2012-09-01 at 23:17 +0200, Sladjan Ristic wrote: The kernel.log I will upload too occured during copying files from one partition to another (ext4, both on that same external HDD). The drive seemed to disconnect, and this happened sporadically many times I worked with it. Sometimes after a short while, sometimes it didn't occur for hours. [...] Can you try using a different USB cable? If this enclosure has internal cables, can you check that they are firmly connected? If the cables are OK, can you test whether Linux 3.5 (packaged in the experimental suite as linux-image-3.5-trunk-amd64) works better? Now I'm in suspense. Do you still have access to this machine? Any new clues since the initial report? Curious, Jonathan
Bug#684352: Compaq Presario V4000T: Wifi kill switch always on unless ACPI=off is used
tags 684352 - moreinfo # regression severity 684352 important quit David Smith wrote: Some people think it might be a problem in networkmanager, but trying to find the problem there hasn't really gone anywhere. Yeah, it's more likely to be a kernel, firmware, or hardware bug. [...] Kernel from Squeeze(linux-image-2.6.32-5-686): The problem completely disappears. Very useful, thanks. [...] Kernel from Expiermental(linux-image-3.5-trunk-686-pae): System crashes on Waiting for /dev to be populated. Unable to test, although I'm not sure if I'm installing the kernel properly. That might be another instance of the same problem as http://bugs.debian.org/688711. ACPI Dump attached. Thanks! If you prevent the hp-wmi driver from loading (just running echo 'blacklist hp-wmi' /etc/modprobe.d/ds-blacklist-hpwmi.conf and rebooting should do the trick, but check lsmod output to be sure), does that avoid rfkill trouble? If so, please send a summary of symptoms to platform-driver-...@vger.kernel.org, cc-ing linux-wirel...@vger.kernel.org, Anssi Hannula anssi.hann...@iki.fi, and either me or this bug log so we can track it. Be sure to mention - steps to reproduce the problem, expected result, actual result, and how the difference indicates a bug (should be simple enough) - which kernel versions you have tested and what happened with each - full dmesg output from booting and reproducing the bug on an affected kernel, as an attachment - PCI registers for your wireless card (from running lspci -vv -s06:05.0 as root) - any other weird symptoms or observations - a link to http://bugs.debian.org/684352 for the backstory Hopefully someone upstream can suggest steps to perform or a patch to try to further track down the cause. Another hint: another tack would be to try various kernels to narrow down when this regression was introduced. There are various pre-compiled kernel versions at http://snapshot.debian.org/package/linux-2.6/. It would be interesting to see whether 2.6.38 and 2.6.39 exhibit this. Good luck, 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/20120930082510.GA21569@elie.Belkin
Processed: Re: Compaq Presario V4000T: Wifi kill switch always on unless ACPI=off is used
Processing commands for cont...@bugs.debian.org: tags 684352 - moreinfo Bug #684352 [src:linux] Wifi kill switch always on unless ACPI=off is used Removed tag(s) moreinfo. # regression severity 684352 important Bug #684352 [src:linux] Wifi kill switch always on unless ACPI=off is used Severity set to 'important' from 'normal' quit Stopping processing here. Please contact me if you need assistance. -- 684352: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684352 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.134899352428055.transcr...@bugs.debian.org
Bug#680749: Additional info
After some digging I had to realize, that the thinkpad_acpi module is functioning well, the error is in XFCE-s display brightness setter. This is a duplicate of: https://bugzilla.xfce.org/show_bug.cgi?id=7541 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627336 Workaround solution: http://www.n0nb.us/blog/2012/02/restoring-screen-brightness-step-size-on-xfce4/ -- 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/freemail.20120930102132.7216...@xmldata09.freemail.hu
Bug#682971: not have bluetooth usb 0489:e046 Foxconn / Hon Hai
Hi, aborigines wrote: Bus 003 Device 005: ID 0489:e046 Foxconn / Hon Hai Please test the attached patch, for example using the following instructions: 0. prerequisites apt-get install git build-essential 1. 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 2. configure, build, test cd linux git fetch origin git checkout origin/master cp /boot/config-$(uname -r) .config; # current configuration scripts/config --disable DEBUG_INFO make localmodconfig; # optional: minimize configuration scripts/config --module BT_HCIBTUSB 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 3. try the patch cd linux git am -3sc /path/to/the/patch make deb-pkg; # maybe with -j4 dpkg -i ../name of package; # as root reboot ... test test test ... Hope that helps, Jonathan From b79fc3e6e69b27c23e0c159a9ee3ea6367d84e5a Mon Sep 17 00:00:00 2001 From: Gustavo Padovan gust...@padovan.org Date: Wed, 15 Aug 2012 01:38:11 -0300 Subject: [PATCH] Bluetooth: Add USB_VENDOR_AND_INTERFACE_INFO() for Broadcom/Foxconn Foxconn devices has a vendor specific class of device, we will match them differently now. Signed-off-by: Gustavo Padovan gust...@padovan.org Signed-off-by: Jonathan Nieder jrnie...@gmail.com --- drivers/bluetooth/btusb.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c index 654e248763ef..248c1319759a 100644 --- a/drivers/bluetooth/btusb.c +++ b/drivers/bluetooth/btusb.c @@ -100,7 +100,7 @@ static struct usb_device_id btusb_table[] = { { USB_DEVICE(0x413c, 0x8197) }, /* Foxconn - Hon Hai */ - { USB_DEVICE(0x0489, 0xe033) }, + { USB_VENDOR_AND_INTERFACE_INFO(0x0489, 0xff, 0x01, 0x01) }, /*Broadcom devices with vendor specific id */ { USB_VENDOR_AND_INTERFACE_INFO(0x0a5c, 0xff, 0x01, 0x01) }, -- 1.7.10.4
Bug#680749: thinkpad: xfce and platform compete over brightness controls
reassign 680749 xfce4-power-manager forcemerge 627336 680749 affects 680749 + src:linux quit Hi, Gyuro Lehel wrote: [Subject: Re: Bug#680749: Additional info] Please keep in mind that these appear as emails in a crowded inbox, so the subject line can be a good place to put valuable context. After some digging I had to realize, that the thinkpad_acpi module is functioning well, the error is in XFCE-s display brightness setter. This is a duplicate of: https://bugzilla.xfce.org/show_bug.cgi?id=7541 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627336 Workaround solution: http://www.n0nb.us/blog/2012/02/restoring-screen-brightness-step-size-on-xfce4/ Thanks! Merging. Ciao, 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/20120930085103.GA25864@elie.Belkin
Processed: Re: thinkpad: xfce and platform compete over brightness controls
Processing commands for cont...@bugs.debian.org: reassign 680749 xfce4-power-manager Bug #680749 [src:linux] thinkpad: thinkpad_acpi display brightness problems Bug reassigned from package 'src:linux' to 'xfce4-power-manager'. No longer marked as found in versions linux/3.2.20-1. Ignoring request to alter fixed versions of bug #680749 to the same values previously set forcemerge 627336 680749 Bug #627336 [xfce4-power-manager] xfce4-power-manager: Not enough brightness levels Bug #680749 [xfce4-power-manager] thinkpad: thinkpad_acpi display brightness problems Set Bug forwarded-to-address to 'https://bugzilla.xfce.org/show_bug.cgi?id=7541'. Severity set to 'minor' from 'important' 680749 was not blocked by any bugs. 680749 was not blocking any bugs. Added blocking bug(s) of 680749: 626542 Marked as found in versions xfce4-power-manager/1.0.10-3. Added tag(s) upstream and confirmed. Merged 627336 680749 affects 680749 + src:linux Bug #680749 [xfce4-power-manager] thinkpad: thinkpad_acpi display brightness problems Bug #627336 [xfce4-power-manager] xfce4-power-manager: Not enough brightness levels Added indication that 680749 affects src:linux Added indication that 627336 affects src:linux quit Stopping processing here. Please contact me if you need assistance. -- 627336: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627336 680749: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680749 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.134899507515863.transcr...@bugs.debian.org
Bug#689096: ipw2200 crashes on wakeup
Hi Stefan, Stefan Ott wrote: Is there anything I can do to help debug this, other than building trying dozens of kernel versions to try and find the bad commit? I haven't looked closely into this report, but here are two quick ideas: A. Have you tried the 3.5.y kernel from experimental? If it works, we can try to find the patch that fixes the bug and apply the same to wheezy. If it doesn't work, that information will make it much easier for us to get help from upstream. B. You can find various kernels between 2.6.32.y and 3.2.y pre-compiled here: http://snapshot.debian.org/package/linux-2.6/ That would make a few rounds of bisection to find roughly when the bug was introduced easier. (A) seems more promising than (B), since it would be best to get the report in upstream hands soonish. Thanks and 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/20120930085747.GB25864@elie.Belkin
Bug#683695: libdrm-nouveau1a: when using Nvidia Gtx 550 Ti card boot stops at populating /dev
found 683695 linux/3.2.21-3 tags 683695 + moreinfo quit Hi Dick, Dick Thomas wrote: bought a new gfx card Nvidia Gtx 550 Ti and installed wheezy to test it failed to boot stopping at populating /dev but i could still hear the hard drive moving (and yes my hard drive is fine) Thanks for reporting it, and sorry for the slow reply. Your card is an nvcf. If we're lucky, the following change in 3.2.23-1 will have helped: * nouveau: Update to support Fermi (NVC0+) acceleration (Closes: #679566) - Refactor sub-channel use - Bump version to 1.0.0 What kernel do you use? Please attach output from reportbug --template linux-image-$(uname -r) 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/20120930091232.GA26038@elie.Belkin
Processed: Re: libdrm-nouveau1a: when using Nvidia Gtx 550 Ti card boot stops at populating /dev
Processing commands for cont...@bugs.debian.org: found 683695 linux/3.2.21-3 Bug #683695 [src:linux] nouveau needs patches backported from 3.4 to support GTX 550 Ti cards Marked as found in versions linux/3.2.21-3. tags 683695 + moreinfo Bug #683695 [src:linux] nouveau needs patches backported from 3.4 to support GTX 550 Ti cards Added tag(s) moreinfo. quit Stopping processing here. Please contact me if you need assistance. -- 683695: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683695 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.134899636525569.transcr...@bugs.debian.org
Bug#686464: USB3 HDD spontaneously disconnects sporadically
tags 686464 = unreproducible quit Sladjan Ri wrote: I have been using the disk internally since my report, and I have not found the time to remove it from the server to test a another kernel. Thanks for the update, and no problem. Do you think you'll have time to try this some time in the next couple of months? If you won't, it's not clear to me how to move forward on this in the short term, so I'd suggest closing the bug and revisiting it once you or someone else finds a moment to reproduce it. If you're just busy now and will probably have a chance to experiment some time this year, that's fine and we can wait. 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/20120930100045.GA26759@elie.Belkin
Processed: Re: [wheezy] USB3 HDD spontaneously disconnects sporadically
Processing commands for cont...@bugs.debian.org: tags 686464 = unreproducible Bug #686464 [src:linux] linux-image-3.2.0-3-amd64: USB3 controller disconnects external HDD while file system is in use Added tag(s) unreproducible; removed tag(s) moreinfo. quit Stopping processing here. Please contact me if you need assistance. -- 686464: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686464 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.134899925817893.transcr...@bugs.debian.org
Bug#684767: kernel: missing support for Ivy Bridge GT2 Server
On Sun, Sep 30, 2012 at 1:52 AM, Jonathan Nieder jrnie...@gmail.com wrote: Hi Maik, Maik Zumstrull wrote: This is on an Ivy Bridge Xeon E3 with GPU. [...] 3.2 crashes as well, but not as hard as 3.4. With 3.2, X doesn't come up, but you can switch to a console and reboot. Sorry for the slow reply. Please test the attached patch, for example using the following instructions. With those instructions and with the patch, 3.2.30 can bring up i915 KMS. Without the patch, it cannot. Seems to hit the spot. -- 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/CAO=zwd+abgnn3bl8frvi1pgdhkzkfwuo3b8xt8j3gmha+fm...@mail.gmail.com
Bug#686464: USB3 HDD spontaneously disconnects sporadically
Yes, certainly I will try this again, right now my USB enclosure is sitting here without any use. Regards, Sladjan On Sep 30, 2012 12:00 PM, Jonathan Nieder jrnie...@gmail.com wrote: tags 686464 = unreproducible quit Sladjan Ri wrote: I have been using the disk internally since my report, and I have not found the time to remove it from the server to test a another kernel. Thanks for the update, and no problem. Do you think you'll have time to try this some time in the next couple of months? If you won't, it's not clear to me how to move forward on this in the short term, so I'd suggest closing the bug and revisiting it once you or someone else finds a moment to reproduce it. If you're just busy now and will probably have a chance to experiment some time this year, that's fine and we can wait. Jonathan
Bug#687442: linux-image-3.2.0-3-686-pae: Add Intel Ivy Bridge support
Hi, Am Freitag, 28. September 2012 schrieb Jonathan Nieder: If you have a 64-bit CPU, one possibility is sha1sum linux-image-3.2.0-4-amd64_3.2.30-1_amd64.deb dpkg --force-architecture --install linux-image-3.2.0-4-amd64_3.2.20-1_amd64.deb The magic of multi-arch (well, sort of). :) Thanks Jonathan, it helped. I installed and bootet the kernel today. During the boot process the singnal to my DVI connected monitor disappears. I've created a video of the boot process. The last lines are: input: PC Speaker as /devices/platform/pcspkr/input/input4 iTCO_vendor_support: vendor-support=0 iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07 iTCO_wdt: Found a Panther Point TCO device (Version=2, TCOBASE=0x0460) iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni) Unfortunately I could not provide anymore output. With the disabled KMS (i915.modeset=0) the boot was successful. Once I disabled KMS at boottime (i915.modeset=0). This boot process has been completed. Audio and network is working. The dmesg output is attached. Regards, Carsten dmesg_20120930-nokms.log.bz2 Description: application/bzip
Bug#684352: Compaq Presario V4000T: Wifi kill switch always on unless ACPI=off is used
Yes, echo 'blacklist hp-wmi' /etc/modprobe.d/ds-blacklist-hpwmi.conf Fixes the problem in Wheezy, using linux-image-3.2.0-3-686-pae in Wheezy. I'll send an e-mail out tomorrow with all the needed information that you listed. Thanks again for your help. -David
Bug#607242: psmouse: mitigate failing-mouse symptoms
Hi Jim, In January, 2011, Jim Hill wrote: Keep a failing PS/2 mouse usable until it's convenient to replace it. Filter incoming packets: drop invalid ones and attempt to correct for dropped bytes. New parameter 'filter' makes filtering and logging selectable, set to 0 to shut off all effects. [...] My mouse failed while in XP, but I didn't know it - it seemed it'd need cleaning soon. On booting into Linux, it was dangerous, wild slews and random clicks. The difference was consistent, making it seem the problem wasn't the mouse. I think this would be less controversial if the run-time default were to disable the feature. Then if lots of people are setting the parameter and the idea proves itself, the default could change, and in the meantime, people with broken setups would know about the breakage and get a chance to look for other problems. What do you think? Thanks for your work, 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/20120930174353.GA29129@elie.Belkin
Processed: Re: [PATCH v2] psmouse: mitigate failing-mouse symptoms
Processing commands for cont...@bugs.debian.org: tags 607242 - moreinfo Bug #607242 [linux-2.6] psmouse: work around dying mouse by dropping invalid packets (mouse jumping all over the place, many events without EV_SYN) Removed tag(s) moreinfo. End of message, stopping processing here. Please contact me if you need assistance. -- 607242: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607242 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.134902709225771.transcr...@bugs.debian.org
Processed: Re: atl1c fails to force 100 full duplex
Processing commands for cont...@bugs.debian.org: tags 616081 - moreinfo Bug #616081 [linux-2.6] linux-image-2.6.37-2-amd64: atl1c fail to force 100 full duplex Removed tag(s) moreinfo. forwarded 616081 http://thread.gmane.org/gmane.linux.network/190872 Bug #616081 [linux-2.6] linux-image-2.6.37-2-amd64: atl1c fail to force 100 full duplex Changed Bug forwarded-to-address to 'http://thread.gmane.org/gmane.linux.network/190872' from 'net...@vger.kernel.org' End of message, stopping processing here. Please contact me if you need assistance. -- 616081: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616081 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.134902796432376.transcr...@bugs.debian.org
Bug#607242: psmouse: mitigate failing-mouse symptoms
I think this would be less controversial if the run-time default were to disable the feature. Yes, that's the common sensible path to new little-tested features. As you say, it may become enabled by default over time. Then, I think it would be good to have a specific sub-structure for this stuff. It would allow this: + psmouse-err_log_base = 0; + psmouse-interval_base = 0; + psmouse-hotio_log_base = 0; + psmouse-err_log_counter = 0; + psmouse-interval_pkts = 0; + psmouse-hotio_log_counter = 0; to be replaced with a memset. I also think it would make it clearer what these are: + unsigned long interval_base; + unsigned long interval_pkts; + unsigned long hotio_log_base; + unsigned long hotio_log_counter; + unsigned long err_log_base; + unsigned long err_log_counter; to the casual reader. This is only a suggestion, though. thanks /alessandro -- 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/20120930180240.ga31...@mail.gnudd.com
Processed: Re: Elantech touchpad detected as Logitech PS2 Wheel Mouse
Processing commands for cont...@bugs.debian.org: tags 673588 - moreinfo Bug #673588 [linux-2.6] linux-image-3.2.0-2-686-pae: Elantech touchpad detected as PS2 mouse Removed tag(s) moreinfo. quit Stopping processing here. Please contact me if you need assistance. -- 673588: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673588 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.134903124025255.transcr...@bugs.debian.org
Bug#673588: marked as done (linux-image-3.2.0-2-686-pae: Elantech touchpad detected as PS2 mouse)
Your message dated Sun, 30 Sep 2012 11:53:47 -0700 with message-id 20120930185347.GA29660@elie.Belkin and subject line Re: Elantech touchpad detected as Logitech PS2 Wheel Mouse has caused the Debian Bug report #673588, regarding linux-image-3.2.0-2-686-pae: Elantech touchpad detected as PS2 mouse 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.) -- 673588: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673588 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- 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
Bug#689178: No support for modern nVidia cards (GT 610) - System unusable!
On za, 2012-09-29 at 14:44 -0700, Jonathan Nieder wrote: Could you try a 3.5.y kernel from experimental and let us know how it goes? Hi Jonathan, I'll let you know within 72 hours. Kind regards, Kees signature.asc Description: This is a digitally signed message part
Bug#575660: With last kernels, terminal/console processing getting worth.
Hi Regid, In 2010, Regid Ichira wrote: 1) With 32-9, when tty1 shows the login prompt after boot, I can't see the characters that I type. I believe they are not processed as expected. This doesn't happen with 32-5. [...] An old AT (DIN5 connector) white colored keyboard. 01:00.0 VGA compatible controller: 3Dfx Interactive, Inc. Voodoo 3 (rev 01) [...] By connecting over the network one can see that the i8042 interrupt counter does not go up. Do you still have access to this machine? If so, what kernel version are you using these days, and how does it behave? 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/20120930191607.GA29937@elie.Belkin
Bug#570268: marked as done (sky2 fails when memory exceeds 2GB on amd64 kernel)
Your message dated Sun, 30 Sep 2012 12:27:31 -0700 with message-id 20120930192731.GA30179@elie.Belkin and subject line Re: sky2 fails when memory exceeds 2GB on amd64 kernel has caused the Debian Bug report #570268, regarding sky2 fails when memory exceeds 2GB on amd64 kernel 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.) -- 570268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570268 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.32-trunk-amd64 Version: 2.6.32-5 Package: linux-image-2.6.30-2-amd64 Version: 2.6.30-8squeeze1 No matter what brand, size, or speed of ddr2 RAM I try, I cannot successfully boot when the installed memory is greater than 2GB. The system is an Acer Aspire M1100 with the most recent BIOS. I have tried with kernels 2.6.32-5 and 2.6.30-8squeeze1. During the boot sequence, sky2 fails with a 0x2010 pci error; then several programs slowly load until dmsg appears, at which time the screen fills with hexadecimal errors similar to those in this debian bug thread: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=457967 Disabling the network interface in the BIOS allows bootup to finish, although some programs fail to load due to the missing network connection. Decreasing the RAM to 2GB returns booting to normal. I've seen numerous references to bugs with this network hardware and the amd64 kernel, but none related to adding extra memory. I am unaware as to how I can capture the errors, since I cannot finish the boot process when the errors happen. -- Dale Schroeder ---End Message--- ---BeginMessage--- Ben Hutchings wrote: Is this bug still present in Debian 6.0 'squeeze'? I applied many bug fixes to the sky2 driver in package version 2.6.32-22, and those may have fixed it (but I can't tell from the descriptions). Closing due to lack of response, but if you have any more information, please don't hesitate to write and we'll be glad to pick it up again.---End Message---
Bug#557802: No sound with snd-ens1371.ko
tags 557802 - fixed-upstream quit Hi Tino, Tino Schmidt wrote: Two days ago I installed Debian on a 10-year-old laptop. It's a IPC Topnote G. Soundcard is a Creative Labs Ectiva EV1938. The laptop was running a few days ago with Debian Etch and OSS-modules and the output of oss-modul es1371 was quite good. I formated the harddisk to set up Lenny. If I play a music file now, it looks like the file is played without any errors. There are no messages that the hardware or alsa is corrupt. But the speakers are silent. The tool alsamixer shows that nothing is muted and all values are at maximum level. Sorry for the slow response. Do you still have access to this hardware? If so, what kernel are you using and how does it behave? 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/20120930193113.GA30235@elie.Belkin
Processed: Re: [etch-lenny regression] No sound with snd-ens1371.ko
Processing commands for cont...@bugs.debian.org: tags 557802 - fixed-upstream Bug #557802 [linux-2.6] linux-image-2.6.26-2-686: No sound with snd-ens1371.ko Removed tag(s) fixed-upstream. quit Stopping processing here. Please contact me if you need assistance. -- 557802: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557802 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.134903348510367.transcr...@bugs.debian.org
Bug#557802: marked as done (linux-image-2.6.26-2-686: No sound with snd-ens1371.ko)
Your message dated Sun, 30 Sep 2012 12:35:25 -0700 with message-id 20120930193525.GB30235@elie.Belkin and subject line Re: [etch-lenny regression] No sound with snd-ens1371.ko has caused the Debian Bug report #557802, regarding linux-image-2.6.26-2-686: No sound with snd-ens1371.ko 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.) -- 557802: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557802 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-2-686 Version: 2.6.26-19lenny2 Severity: normal Two days ago I installed Debian on a 10-year-old laptop. It's a IPC Topnote G. Soundcard is a Creative Labs Ectiva EV1938. The laptop was running a few days ago with Debian Etch and OSS-modules and the output of oss-modul es1371 was quite good. I formated the harddisk to set up Lenny. If I play a music file now, it looks like the file is played without any errors. There are no messages that the hardware or alsa is corrupt. But the speakers are silent. The tool alsamixer shows that nothing is muted and all values are at maximum level. The tools `speaker-test` shows normal behaviour/output, but also with silent speakers. I checked alsa-mailinglist and found a mistake which is very similar: http://www.mail-archive.com/alsa-user@lists.sourceforge.net/msg22930.html -- Package-specific info: ** Version: Linux version 2.6.26-2-686 (Debian 2.6.26-19lenny2) (da...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Wed Nov 4 20:45:37 UTC 2009 ** Command line: root=/dev/hda1 ro quiet ** Not tainted ** Kernel log: [5.112545] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [5.112556] usb usb1: Product: UHCI Host Controller [5.112564] usb usb1: Manufacturer: Linux 2.6.26-2-686 uhci_hcd [5.112572] usb usb1: SerialNumber: :00:07.2 [5.321132] Uniform Multi-Platform E-IDE driver [5.321152] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx [5.395802] PIIX4: IDE controller (0x8086:0x7111 rev 0x01) at PCI slot :00:07.1 [5.395845] PIIX4: not 100% native mode: will probe irqs later [5.395870] ide0: BM-DMA at 0xfcf0-0xfcf7 [5.395895] ide1: BM-DMA at 0xfcf8-0xfcff [5.395912] Probing IDE interface ide0... [5.539824] Floppy drive(s): fd0 is 1.44M [5.645358] FDC 0 is a National Semiconductor PC87306 [5.720271] hda: SAMSUNG MP0402H, ATA DISK drive [5.808986] Marking TSC unstable due to: TSC halts in idle. [6.39] hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4 [6.392308] hda: UDMA/33 mode selected [6.392387] Probing IDE interface ide1... [7.128196] hdc: MATSHITA CR-176, ATAPI CD/DVD-ROM drive [7.464171] hdc: host max PIO4 wanted PIO255(auto-tune) selected PIO4 [7.464338] hdc: UDMA/33 mode selected [7.464502] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 [7.474517] ide1 at 0x170-0x177,0x376 on irq 15 [7.578801] hda: max request size: 512KiB [7.586442] hda: 78242976 sectors (40060 MB) w/8192KiB Cache, CHS=16383/255/63 [7.586932] hda: cache flushes supported [7.587103] hda: hda1 hda2 hda3 [7.613638] hdc: ATAPI 24X CD-ROM drive, 128kB Cache [7.613658] Uniform CD-ROM driver Revision: 3.20 [7.974106] PM: Starting manual resume from disk [8.055963] kjournald starting. Commit interval 5 seconds [8.055963] EXT3-fs: mounted filesystem with ordered data mode. [9.980834] udevd version 125 started [ 13.977283] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [ 14.006849] Linux agpgart interface v0.103 [ 14.131699] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [ 14.149325] agpgart: Detected an Intel 440BX Chipset. [ 14.155596] agpgart: AGP aperture is 64M @ 0x1800 [ 14.801360] Yenta: CardBus bridge found at :00:0a.0 [:] [ 14.801397] Yenta O2: res at 0x94/0xD4: 88/00 [ 14.801405] Yenta O2: old bridge, disabling read prefetch/write burst [ 14.847404] input: PC Speaker as /class/input/input1 [ 14.928848] Yenta: ISA IRQ mask 0x04b8, PCI irq 11 [ 14.928861] Socket status: 3821 [ 14.929575] Yenta: CardBus bridge found at :00:0a.1 [:] [ 15.056864] Yenta: ISA IRQ mask 0x04b8, PCI irq 11 [ 15.056877] Socket status: 3007 [ 15.057697] piix4_smbus :00:07.3: Found :00:07.3 device [ 15.312476] Error: Driver 'pcspkr' is already registered, aborting... [ 15.475957] ENS1371 :00:04.0: enabling device ( - 0001) [ 15.476679] ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 5 [ 15.476692] PCI: setting IRQ 5
Bug#490816: marked as done (linux-image-2.6-686: tulip has no detection under VirtualPC and Hyper-V)
Your message dated Sun, 30 Sep 2012 12:39:58 -0700 with message-id 20120930193958.GA30342@elie.Belkin and subject line Re: tulip has no link detection, under VirtualPC and Hyper-V has caused the Debian Bug report #490816, regarding linux-image-2.6-686: tulip has no detection under VirtualPC and Hyper-V 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.) -- 490816: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=490816 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: network-manager Version: 0.6.6-1 Severity: normal Please describe the problem: When I boot Debian under Microsoft VirtualPC 2007 or WindowsServer Hyper-V, the network is disconnected. The network interface is has PCI id =1011:0009 Digital Equipment Corporation DECchip 21140 [FasterNet] The Linux kernel module to handle it is tulip. Steps to reproduce: 1. Boot Debian (stable or Testing) under VirtualPC 2007 or Hyper-V 2a. Open a session in a console, type ifconfig : The interface isn't configured 3a. Type ifup eth0 : the interface get configured. or 2b. Open a session under gnome : the NM applet says the link is down. (click on the icon, the Wired Networking isn't ticked in !). 3b. Click on the NM applet, tick-in Wired Networking : the interface get configured. Actual results: We notice that the interface is down. Expected results: The interface should be up and configured. Does this happen every time? Yes. Under Debian stable (kernel 2.6.18 + NM 0.6.4) and Debian Testing (kernel 2.6.25 + NM 0.6.6) I've opened a bug upstream : http://bugzilla.gnome.org/show_bug.cgi?id=542916 Franklin -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.25-2-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages network-manager depends on: ii adduser 3.108add and remove users and groups ii dbus1.2.1-2 simple interprocess messaging syst ii dhcdbd 3.0-4D-Bus interface to the ISC DHCP cl ii hal 0.5.11-2 Hardware Abstraction Layer ii ifupdown0.6.8+nmu1 high level tools to configure netw ii iproute 20080417-1 networking and traffic control too ii iputils-arping 3:20071127-1 Tool to send ICMP echo requests to ii libc6 2.7-10 GNU C Library: Shared libraries ii libdbus-1-3 1.2.1-2 simple interprocess messaging syst ii libdbus-glib-1-20.76-1 simple interprocess messaging syst ii libgcrypt11 1.4.1-1 LGPL Crypto library - runtime libr ii libglib2.0-02.16.3-2 The GLib library of C routines ii libgpg-error0 1.4-2library for common error values an ii libhal1 0.5.11-2 Hardware Abstraction Layer - share ii libiw29 29-1 Wireless tools - library ii libnl1 1.1-2library for dealing with netlink s ii libnm-util0 0.6.6-1 network management framework (shar ii lsb-base3.2-12 Linux Standard Base 3.2 init scrip ii wpasupplicant 0.6.3-2 Client support for WPA and WPA2 (I Versions of packages network-manager recommends: ii network-manager-gnome 0.6.6-2network management framework (GNOM -- no debconf information ---End Message--- ---BeginMessage--- In May, Jonathan Nieder wrote: In 2008, Franklin PIAT wrote: When I boot Debian under Microsoft VirtualPC 2007 or WindowsServer Hyper-V, the network is disconnected. [...] Did you make any progress with the help of Grant? Do you still have access to this [setup], and if so, can you still reproduce the bug? Closing due to lack of response. If you have more information, please don't hesitate to write, though, and we can pick up where we left off.---End Message---
Re: Bug#599161: xen-linux-system-2.6.32-5-xen-amd64: Clock moved forward 50 minutes, caused Xen HVM domU restart
Hello, have you find a solution for this annoying problem? I have exactly the same on two HP Proliant DL 580 G5 servers with debian squeeze and xen hypervisor 4.0. uname -a Linux xen-p01 2.6.32-5-xen-amd64 #1 SMP Sun May 6 08:57:29 UTC 2012 x86_64 GNU/Linux Time jumps forward 50 minutes. Is it a debian kernel bug? A xen bug? A hardware bug? -- 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/cae17a0xxaro-3fpuhxzemz5fxfdwj1xax5demavc_w3bpyl...@mail.gmail.com
Processed: Re: Compaq Presario V4000T: Wifi kill switch always on unless ACPI=off is used
Processing commands for cont...@bugs.debian.org: retitle 684352 [Presario V4000T] hp-wmi: wifi blocked at boot, network-manager and wifi button don't unblock Bug #684352 [src:linux] Wifi kill switch always on unless ACPI=off is used Changed Bug title to '[Presario V4000T] hp-wmi: wifi blocked at boot, network-manager and wifi button don't unblock' from 'Wifi kill switch always on unless ACPI=off is used' End of message, stopping processing here. Please contact me if you need assistance. -- 684352: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684352 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.134903978821276.transcr...@bugs.debian.org
Bug#669314: NFS: kernel forces trailing slash for export in /proc/self/mounts
Hi Chris, Chris Hiestand wrote: On Sep 16, 2012, at 7:00 AM, Ben Hutchings wrote: This was my first thought - but what if userland provides a device name with a slash on the end? I think we have to report it back with the slash in that case. [...] As a point of comparison, matching the given input is the behavior of 2.6.32-5 in Debian Squeeze. So I think your approach is better. Thanks for looking it over. Did you get a chance to test Ben's patch? 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/20120930212341.GA32505@elie.Belkin
Bug#689268: linux-image-3.2.0-3-amd64: Intel HD 4000 (Ivy Bridge) graphics freeze
Package: src:linux Version: 3.2.23-1 Severity: important I'm using the built-in graphics (HD4000) on a i7 3770 Ivy Bridge processor with Z77 chipset. The computer has been runing just fine under heavy load (Folding at Home) for some weeks, but a few days ago I started using it as a workstation, and since then it totally freezes a few times a day. This always happens on interactive input. So far these four events: - close a window - click a link in firefox - ctrl-r to reload a page in firefox - ctrl-k to delete a line in thunderbird's composer The computer is completely frozen. The cpu probably stops working since the fan spins down to it's lowest rpm, I can't ping the interface, caps lock doesn't light up, has to be power cycled. And no clues in the logs. After reboot, redoing the same actions doesn't trigger the bug. But about 3-4 hours later the computer hangs again. Maybe some data structure that is filled upp with time? Googling for solutions, I fond these pages: http://partiallysanedeveloper.blogspot.se/2012/05/ivy-bridge-hd4000-linux-freeze.html http://askubuntu.com/questions/155458/ubuntu-12-04-randomly-freezes-on-ivy-bridge-intel-hd-graphics-4000 http://askubuntu.com/questions/163890/weird-system-freeze-nothing-works-keyboard-mouse-reset-button-ubuntu-12-04-64 I haven't tried with another kernel yet. -- Package-specific info: ** Version: Linux version 3.2.0-3-amd64 (Debian 3.2.23-1) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-8) ) #1 SMP Mon Jul 23 02:45:17 UTC 2012 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-3-amd64 root=/dev/md0 ro ** Not tainted ** Kernel log: [5.621585] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 5636493 [5.621624] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 5636605 [5.621636] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 5636595 [5.621651] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 5636593 [5.621659] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 5636592 [5.621667] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 5636584 [5.621673] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 5636520 [5.621680] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 5636514 [5.621687] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 5636501 [5.621694] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 5636496 [5.621700] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 5636491 [5.621706] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 5636191 [5.621718] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 5636508 [5.621743] EXT4-fs (md0): ext4_orphan_cleanup: deleting unreferenced inode 4064137 [5.621757] EXT4-fs (md0): 15 orphan inodes deleted [5.621808] EXT4-fs (md0): recovery complete [5.925942] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [7.181722] udevd[467]: starting version 175 [7.619643] ACPI: Requesting acpi_cpufreq [7.619661] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input4 [7.619667] ACPI: Power Button [PWRB] [7.620061] Monitor-Mwait will be used to enter C-1 state [7.620080] Monitor-Mwait will be used to enter C-2 state [7.620099] Monitor-Mwait will be used to enter C-3 state [7.620111] ACPI: acpi_idle registered with cpuidle [7.622036] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input5 [7.622104] ACPI: Power Button [PWRF] [7.687301] i801_smbus :00:1f.3: PCI INT C - GSI 18 (level, low) - IRQ 18 [7.687369] ACPI: resource :00:1f.3 [io 0xf040-0xf05f] conflicts with ACPI region SMBI [io 0xf040-0xf04f] [7.687436] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [7.700685] input: PC Speaker as /devices/platform/pcspkr/input/input6 [7.720941] wmi: Mapper loaded [7.722731] iTCO_vendor_support: vendor-support=0 [7.740352] alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni) [7.759663] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07 [7.759776] iTCO_wdt: Found a Panther Point TCO device (Version=2, TCOBASE=0x0460) [7.759880] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [7.869045] [drm] Initialized drm 1.1.0 20060810 [7.890031] i915 :00:02.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [7.890087] i915 :00:02.0: setting latency timer to 64 [7.921302] mtrr: type mismatch for e000,1000 old: write-back new: write-combining [7.921372] [drm] MTRR allocation failed. Graphics performance may suffer. [7.921596] i915 :00:02.0: irq 55 for MSI/MSI-X [7.921599] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [7.921652] [drm] Driver supports precise vblank timestamp
Bug#689274: linux-image-3.5-trunk-amd64: (almost 100% reproducible) kernel bug when trying to mount nfs filesystem
Package: src:linux Version: 3.5.2-1~experimental.1 Severity: important Hi there. I have been semi-consistently (the almost 100% reproducible) getting a kernel Oops whenever I try to mount a NFS filesystem from another computer (an ARM, 32-bit NAS, running pure Debian armel unstable) from my network. This has only happened with kernel 3.5, but not with previous kernels. I also have not yet tried newer kernels on this amd64 system. At first, I thought that this might have been due to some experiments with ZFS that I had been done, but I am not using ZFS now (way too slow---back to ext4). If any further information is needed, please let me know. -- Package-specific info: ** Version: Linux version 3.5-trunk-amd64 (Debian 3.5.2-1~experimental.1) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Mon Aug 20 04:17:46 UTC 2012 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.5-trunk-amd64 root=UUID=c1b72bf3-c292-411d-832a-0b92510b158f ro irqpoll ** Tainted: D (128) * Kernel has oopsed before. ** Kernel log: [ 12.240075] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory [ 12.278102] NFSD: starting 90-second grace period [ 15.914006] Bluetooth: Core ver 2.16 [ 15.921231] NET: Registered protocol family 31 [ 15.928359] Bluetooth: HCI device and connection manager initialized [ 15.935592] Bluetooth: HCI socket layer initialized [ 15.940709] Bluetooth: L2CAP socket layer initialized [ 15.945782] Bluetooth: SCO socket layer initialized [ 16.008176] Bluetooth: RFCOMM TTY layer initialized [ 16.015130] Bluetooth: RFCOMM socket layer initialized [ 16.015133] Bluetooth: RFCOMM ver 1.11 [ 16.610238] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 16.617233] Bluetooth: BNEP filters: protocol multicast [ 16.886831] lp0: using parport0 (interrupt-driven). [ 16.983311] ppdev: user-space parallel port driver [ 20.147376] r8169 :02:00.0: eth0: link down [ 20.147397] r8169 :02:00.0: eth0: link down [ 20.160114] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 21.778714] r8169 :02:00.0: eth0: link up [ 21.788303] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 66.338137] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) [ 78.684574] EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: (null) [ 9608.475442] [ cut here ] [ 9608.475559] kernel BUG at /build/buildd-linux_3.5.2-1~experimental.1-amd64-bLqIZ_/linux-3.5.2/fs/nfs/idmap.c:684! [ 9608.475772] invalid opcode: [#1] SMP [ 9608.475874] CPU 0 [ 9608.475919] Modules linked in: ppdev lp bnep rfcomm bluetooth rfkill cpufreq_powersave cpufreq_stats cpufreq_conservative cpufreq_userspace binfmt_misc nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc it87 hwmon_vid loop fuse snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq radeon powernow_k8 mperf kvm_amd kvm ttm drm_kms_helper drm i2c_algo_bit snd_seq_device snd_timer snd shpchp sp5100_tco edac_mce_amd edac_core processor k10temp parport_pc parport i2c_piix4 i2c_core soundcore button evdev pcspkr thermal_sys ext4 crc16 jbd2 mbcache btrfs crc32c libcrc32c zlib_deflate hid_generic usbhid hid md_mod sg sd_mod crc_t10dif microcode ohci_hcd r8169 mii ahci libahci ehci_hcd libata usbcore usb_common scsi_mod [last unloaded: scsi_wait_scan] [ 9608.478016] [ 9608.478027] Pid: 10022, comm: mount.nfs Not tainted 3.5-trunk-amd64 #1 To Be Filled By O.E.M. To Be Filled By O.E.M./To be filled by O.E.M. [ 9608.478306] RIP: 0010:[a054d36d] [a054d36d] nfs_idmap_legacy_upcall+0xeb/0x147 [nfs] [ 9608.478552] RSP: 0018:8800c52335b8 EFLAGS: 00010282 [ 9608.478666] RAX: 0010 RBX: 880114b3ab00 RCX: [ 9608.478815] RDX: 0010 RSI: 880180182854 RDI: 880114b3ab12 [ 9608.478967] RBP: 880109c28ec0 R08: 880114b3ab02 R09: 880180182844 [ 9608.479116] R10: 489c9f22 R11: 880180182ce0 R12: 880180182ce0 [ 9608.479263] R13: 880135308400 R14: 0010 R15: 81635f58 [ 9608.479413] FS: 7f6f74a727e0() GS:88019fc0() knlGS: [ 9608.479584] CS: 0010 DS: ES: CR0: 8005003b [ 9608.479704] CR2: 00d7e000 CR3: d7aa7000 CR4: 07f0 [ 9608.479852] DR0: DR1: DR2: [ 9608.47] DR3: DR6: 0ff0 DR7: 0400 [ 9608.480147] Process mount.nfs (pid: 10022, threadinfo 8800c5232000, task 8800d79ceea0) [ 9608.480325] Stack: [ 9608.480370] 880180182844 880180182854 880180182ce0 8800c50b8bc0 [ 9608.480549] 880195e13c80 8800c50b8b00 880197132a80 8116572d [ 9608.480727] 1c484040 88017f1b6d20 81635f40 [
Processed (with 1 errors): Re: linux-kbuild-2.6: includes python script w/o declaring a relationship with python
Processing commands for cont...@bugs.debian.org: # bugs closed in linux-kbuild - linux-tools renaming unarchive 405499 Bug #405499 {Done: Debian FTP Masters ftpmas...@ftp-master.debian.org} [linux-kbuild-2.6] linux-kbuild-2.6: includes python script w/o declaring a relationship with python Unarchived Bug 405499 unarchive 475108 Bug #475108 {Done: Debian FTP Masters ftpmas...@ftp-master.debian.org} [linux-kbuild-2.6] Missing file: debian/lib/python/debian_linux/__init__.py Unarchived Bug 475108 unarchive 545017 Bug #545017 {Done: Debian FTP Masters ftpmas...@ftp-master.debian.org} [linux-kbuild-2.6] linux-kbuild-2.6: out-of-date-standards-version Unarchived Bug 545017 unarchive 568165 Bug #568165 {Done: Debian FTP Masters ftpmas...@ftp-master.debian.org} [linux-kbuild-2.6.32] linux-kbuild-2.6.32: please ship recordmcount.pl Bug #568998 {Done: Debian FTP Masters ftpmas...@ftp-master.debian.org} [linux-kbuild-2.6.32] tp-smapi-source: fails to build with kernel 2.6.32-1-686 Unarchived Bug 568165 Unarchived Bug 568998 unarchive 568998 unarchive 598504 Bug #598504 {Done: Debian FTP Masters ftpmas...@ftp-master.debian.org} [linux-kbuild-2.6] ..yoho, linux-headers-4|686|amd64 whines about [UNAVAILABLE] linux-kbuild-2.6.36 Unarchived Bug 598504 End of message, stopping processing here. Please contact me if you need assistance. -- 405499: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=405499 475108: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=475108 545017: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=545017 568165: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568165 568998: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568998 598504: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598504 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.134906328324103.transcr...@bugs.debian.org
Bug#682007: NULL pointer dereference in __fscache_read_or_alloc_pages
Jonathan Nieder jrnie...@gmail.com 2012-09-29 15:22: Hi again, In July, 2012, Brian Kroth wrote: Jonathan Nieder jrnie...@gmail.com 2012-07-21 12:04: Please test the attached patches, for example following the instructions below: [...] Anyways, I'll wait on the results of my previous test first to see if we have a reliable test case from it before moving forward. At this point the grep -r abc ... test is just hitting the cache over and over again, so it's not showing a whole lot. One other thing I'd tried before was something like this run a couple of times in a row (hmm, I suppose I could try them in parallel too): find /fsc_mounted_nfs -type f -exec cat {} /dev/null \; A couple of them paniced, but with inconsistent messages, so I had left them out for now. Perhaps that's worth another shot ... So, how did it go? Did some test case prove reliable? Any other new observations? Sorry, the labs went into their dormant period and all of my test cases ran away for the rest of the summer (the find cmd didn't seem to trigger the __fscache problem), so I hadn't moved any further on this. Now that they're back, I'm definitely seeing it again (about 20 different machines in two days last week), so I've started the process of hunting down a trigger cause again. I'll let you know if I find something. Thanks, Brian signature.asc Description: Digital signature
Bug#405499: linux-kbuild-2.6: includes python script w/o declaring a relationship with python
fixed 405499 linux-kbuild-2.6/2.6.23-1 notfixed 405499 3.0.0-2+rm quit In 2007, dann frazier wrote: root@firetheft:/# /usr/src/linux-kbuild-2.6.18/scripts/show_delta /usr/bin/env: python: No such file or directory root@firetheft:/# linux-kbuild-2.6.18 should either declare a relationship with python (imo, Depends or Recommends) or no longer ship python scripts. Thanks for a pleasant report, and sorry for the slow response. show_delta was removed from linux-kbuild in 2.6.23~rc4-1 (r9423 src/Makefile: Drop unused scripts, 2007-08-30), so let's keep this one closed. 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/20121001045513.GA3775@elie.Belkin
Processed: Re: linux-kbuild-2.6: includes python script w/o declaring a relationship with python
Processing commands for cont...@bugs.debian.org: fixed 405499 linux-kbuild-2.6/2.6.23-1 Bug #405499 {Done: Debian FTP Masters ftpmas...@ftp-master.debian.org} [linux-kbuild-2.6] linux-kbuild-2.6: includes python script w/o declaring a relationship with python Marked as fixed in versions linux-kbuild-2.6/2.6.23-1. notfixed 405499 3.0.0-2+rm Bug #405499 {Done: Debian FTP Masters ftpmas...@ftp-master.debian.org} [linux-kbuild-2.6] linux-kbuild-2.6: includes python script w/o declaring a relationship with python There is no source info for the package 'linux-kbuild-2.6' at version '3.0.0-2+rm' with architecture '' Unable to make a source version for version '3.0.0-2+rm' No longer marked as fixed in versions 3.0.0-2+rm. quit Stopping processing here. Please contact me if you need assistance. -- 405499: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=405499 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.134906732617834.transcr...@bugs.debian.org