Bug#670593: linux-image-3.2.0-2-amd64: max_batch_time not honoured or incorrect in /proc/mounts
Package: linux-image-3.2.0-2-amd64 Version: 3.2.15-1 Severity: normal This happens on both 3.2 from backports and 3.2 in wheezy, tested on both. Might happen in earlier kernels too. umount /test; mount -o max_batch_time=14000 /test; grep test /proc/mounts produces: /dev/mapper/test /test ext4 rw,noatime,user_xattr,acl,commit=600,max_batch_time=0,barrier=0,journal_async_commit,stripe=768,data=writeback Note max_batch_time=0 means batching off according to ext4.txt from the linux kernel documentation. umount /test; mount -o max_batch_time=15000 /test; grep test /proc/mounts produces: /dev/mapper/test /test ext4 rw,noatime,user_xattr,acl,commit=600,barrier=0,journal_async_commit,stripe=768,data=writeback This is correct since 15000 is the default. umount /test; mount -o max_batch_time=15000,min_batch_time=42 /test; grep test /proc/mounts produces: /dev/mapper/test /test ext4 rw,noatime,user_xattr,acl,commit=600,min_batch_time=42,max_batch_time=42,barrier=0,journal_async_commit,stripe=768,data=writeback Now they are both 42! So either the reporting of /proc/mounts or parsing when mount options are set is broken. -- System Information: Debian Release: 6.0.4 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-0.bpo.1-amd64 (SMP w/6 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/20120427060454.21576.71826.report...@cherry.wza.us
Bug#627372: [2.6.32 - 2.6.38 regression] GM45: Console turns black during boot
Hi I compiled both versions as per your instructions, and the behaviour is the same each time. I need to use setpci ... to get the screen backlight on. Do you need any additional information? Alan On Apr 26, 2012 7:23 PM, Jonathan Nieder jrnie...@gmail.com wrote: tags 627372 + upstream patch moreinfo quit Hi Alan, Alan Zimmerman wrote: Console turns black during boot, roughly at the point where normally the console font changes. Thanks again. At last there is a patch to test (attached). Could you try it? Possible 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. 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, and test git checkout stable/linux-3.2.y cp /boot/config-$(uname -r) .config; # current configuration make localmodconfig; # optional: minimize configuration make deb-pkg; # optionally with -jnum for parallel build dpkg -i ../name of package; # as root reboot Hopefully it reproduces the black screen at boot. 4. 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 An alternative set of instructions is at [1]. If it works, we can try applying the patch and pass this information upstream to help them decide when to roll it out. Hope that helps, Jonathan [1] http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official or the corresponding page in the debian-kernel-handbook package
Bug#670398: linux-image-2.6.32-5-amd64: SSH logins hang while hpet interrupts multiply on Intel Nehalem CPUs
On Fri, Apr 27, 2012 at 04:19:21AM +0100, Ben Hutchings wrote: Hi, So it looks like in this case at least you're seeing a bug in USB error recovery and not anything to do with timing using the TSC vs HPET. Ok, a few minutes ago I got aware of another system with the given symptoms with a SandyBridge CPU (E3-1220) and the same CallTrace. I'm now wondering what I could do to help to debug such issue further? All those Dell systems (R210 and R210 II) are equipped with DRAC KVM cards. They expose the input of the KVM Java applet as USB devices to the system. For at least one of the effected systems I'm pretty sure that nobody tried to use the KVM applet while that issue appearead but that doesn't mean anything. External USB devices were not connected to the systems. Kernel is linux-image-2.6.32-5-amd64 2.6.32-38 Sven -- 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/20120427133047.ga12...@sho.bk.hosteurope.de
Bug#670634: linux-image-2.6.32-5-686: SV266A with VIA KT266A: suspend to RAM not available
Am Freitag, den 27.04.2012, 15:31 +0200 schrieb Paul Menzel: Package: linux-2.6 Version: 2.6.32-41squeeze2 Unfortunately it is hard to test newer versions, since the BIOS does not allow to boot from an USB media. […] the option suspend to RAM is not available on the motherboard SV266A with a VIA KT266A(?) chipset [1]. $ echo mem | sudo tee /sys/power/state mem tee: /sys/power/state: No such device $ ls /sys/power/ diskimage_size pm_test resume state $ ls /sys/power/state /sys/power/state $ sudo su # echo mem /sys/power/state bash: echo: Schreibfehler: Kein passendes Gerät gefunden. I looked around in the BIOS and the option *ACPI functions* is set to *Enabled*. There is also an option *Suspend Mode* which I can set to *Disable* or to a number of minutes. But I guess I do not want the BIOS to suspend my system but using the operating system for that task. Is Linux looking at the ACPI tables and they are wrong in this case? Can I force suspend to RAM somehow to test it? I attach the output of `dmidecode` and `biosdecode` (Squeeze versions). Although I am not sure if it will be useful or not. Thanks, Paul [1] http://lists.freedesktop.org/archives/pm-utils/2010-June/002176.html -- Package-specific info: ** Version: Linux version 2.6.32-5-686 (Debian 2.6.32-41squeeze2) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Mon Mar 26 05:20:33 UTC 2012 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 root=UUID=582643ad-cb1e-4a01-bca4-5c8ad8562447 ro parport=0 quiet ** Not tainted ** Kernel log: [1.880840] Uniform CD-ROM driver Revision: 3.20 [1.881684] sr 0:0:1:0: Attached scsi CD-ROM sr0 [1.886508] sr1: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray [1.886770] sr 1:0:0:0: Attached scsi CD-ROM sr1 [1.909648] sd 0:0:0:0: Attached scsi generic sg0 type 0 [1.910146] sr 0:0:1:0: Attached scsi generic sg1 type 5 [1.911441] sr 1:0:0:0: Attached scsi generic sg2 type 5 [1.940052] usb 2-1: new low speed USB device using uhci_hcd and address 2 [2.106022] usb 2-1: New USB device found, idVendor=1241, idProduct=1122 [2.106030] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [2.106235] usb 2-1: configuration #1 chosen from 1 choice [2.132546] usbcore: registered new interface driver hiddev [2.151697] input: HID 1241:1122 as /devices/pci:00/:00:10.0/usb2/2-1/2-1:1.0/input/input0 [2.151983] generic-usb 0003:1241:1122.0001: input,hidraw0: USB HID v1.00 Mouse [HID 1241:1122] on usb-:00:10.0-1/input0 [2.152093] usbcore: registered new interface driver usbhid [2.152458] usbhid: v2.6:USB HID core driver [2.348047] usb 2-2: new low speed USB device using uhci_hcd and address 3 [2.527930] usb 2-2: New USB device found, idVendor=046d, idProduct=c30f [2.527939] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [2.527944] usb 2-2: Product: Logitech USB Keyboard [2.527948] usb 2-2: Manufacturer: Logitech [2.528216] usb 2-2: configuration #1 chosen from 1 choice [2.545744] input: Logitech Logitech USB Keyboard as /devices/pci:00/:00:10.0/usb2/2-2/2-2:1.0/input/input1 [2.545953] generic-usb 0003:046D:C30F.0002: input,hidraw1: USB HID v1.10 Keyboard [Logitech Logitech USB Keyboard] on usb-:00:10.0-2/input0 [2.580104] input: Logitech Logitech USB Keyboard as /devices/pci:00/:00:10.0/usb2/2-2/2-2:1.1/input/input2 [2.580237] generic-usb 0003:046D:C30F.0003: input,hidraw2: USB HID v1.10 Device [Logitech Logitech USB Keyboard] on usb-:00:10.0-2/input1 [2.627161] PM: Starting manual resume from disk [2.627172] PM: Resume from partition 8:5 [2.627175] PM: Checking hibernation image. [2.648921] PM: Error -22 checking image file [2.648924] PM: Resume from disk failed. [2.735754] EXT4-fs (sda1): mounted filesystem with ordered data mode [ 18.393028] udev[329]: starting version 164 [ 18.701813] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3 [ 18.701831] ACPI: Power Button [PWRB] [ 18.701952] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input4 [ 18.701965] ACPI: Sleep Button [SLPB] [ 18.702103] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input5 [ 18.702109] ACPI: Power Button [PWRF] [ 18.801413] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [ 18.813370] input: PC Speaker as /devices/platform/pcspkr/input/input6 [ 19.031666] NET: Registered protocol family 23 [ 19.042768] Marking TSC unstable due to TSC halts in idle [ 19.044725] processor LNXCPU:00: registered as cooling_device1 [ 19.045676] Switching to clocksource acpi_pm [ 19.078663] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [
Bug#627372: [2.6.32 - 2.6.38 regression] GM45: Console turns black during boot
tags 627372 - patch moreinfo fixed-upstream quit Hi, Alan Zimmerman wrote: I compiled both versions as per your instructions, and the behaviour is the same each time. I need to use setpci ... to get the screen backlight on. Thanks. Let's take this upstream. -- 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/20120427170808.GC687@burratino
Processed: Re: [2.6.32 - 2.6.38 regression] GM45: Console turns black during boot
Processing commands for cont...@bugs.debian.org: tags 627372 - patch moreinfo fixed-upstream Bug #627372 [linux-2.6] linux-image-2.6.38-2-686: Console turns black during boot Bug #625727 [linux-2.6] linux-image-2.6.38-2-amd64: Console turns black during boot, backlight turns off Removed tag(s) fixed-upstream, moreinfo, and patch. Removed tag(s) fixed-upstream, moreinfo, and patch. quit Stopping processing here. Please contact me if you need assistance. -- 625727: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625727 627372: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627372 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.133554650215402.transcr...@bugs.debian.org
Bug#670634: linux-image-2.6.32-5-686: SV266A with VIA KT266A: suspend to RAM not available
On Fri, Apr 27, 2012 at 03:31:30PM +0200, Paul Menzel wrote: Package: linux-2.6 Version: 2.6.32-41squeeze2 Severity: normal Dear Debian folks, the option suspend to RAM is not available on the motherboard SV266A with a VIA KT266A(?) chipset [1]. What makes you think this is a kernel bug? Does this work in other operating systems or kernel versions on this same hardware? [...] I looked around in the BIOS and the option *ACPI functions* is set to *Enabled*. ACPI is a broad interface with hundreds of features which the system firmware (BIOS) can *optionally* support. You should always enable ACPI but it doesn't mean suspend to RAM will be possible. There is also an option *Suspend Mode* which I can set to *Disable* or to a number of minutes. But I guess I do not want the BIOS to suspend my system but using the operating system for that task. Is Linux looking at the ACPI tables and they are wrong in this case? Can I force suspend to RAM somehow to test it? No, there is no way to suspend to RAM on x86 without using ACPI or (on old systems) APM. If the system firmware doesn't tell the kernel suspend to RAM is possible, then it isn't. Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- 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/20120427174522.gn3...@decadent.org.uk
Processed: tagging 670634
Processing commands for cont...@bugs.debian.org: tags 670634 + moreinfo Bug #670634 [linux-2.6] linux-image-2.6.32-5-686: SV266A with VIA KT266A: suspend to RAM not available Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 670634: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670634 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.133554873326437.transcr...@bugs.debian.org
Processed: Re: max_batch_time not honoured or incorrect in /proc/mounts
Processing commands for cont...@bugs.debian.org: reassign 670593 src:linux-2.6 3.2.15-1 Bug #670593 [linux-image-3.2.0-2-amd64] linux-image-3.2.0-2-amd64: max_batch_time not honoured or incorrect in /proc/mounts Bug reassigned from package 'linux-image-3.2.0-2-amd64' to 'src:linux-2.6'. No longer marked as found in versions linux-2.6/3.2.15-1. Ignoring request to alter fixed versions of bug #670593 to the same values previously set Bug #670593 [src:linux-2.6] linux-image-3.2.0-2-amd64: max_batch_time not honoured or incorrect in /proc/mounts Marked as found in versions linux-2.6/3.2.15-1. reassign 654206 src:linux-2.6 2.6.32-39 Bug #654206 [linux-2.6] linux-image-3.0.0-2-amd64: max_batch_time doesn't seem to work Bug reassigned from package 'linux-2.6' to 'src:linux-2.6'. No longer marked as found in versions 2.6.32-39, 3.1.6-1, and 3.0.0-6. Ignoring request to alter fixed versions of bug #654206 to the same values previously set Bug #654206 [src:linux-2.6] linux-image-3.0.0-2-amd64: max_batch_time doesn't seem to work Marked as found in versions linux-2.6/2.6.32-39. found 654206 linux-2.6/3.1.6-1 , linux-2.6/3.0.0-6 Bug #654206 [src:linux-2.6] linux-image-3.0.0-2-amd64: max_batch_time doesn't seem to work Marked as found in versions linux-2.6/3.1.6-1 and linux-2.6/3.0.0-6. merge 654206 670593 Bug #654206 [src:linux-2.6] linux-image-3.0.0-2-amd64: max_batch_time doesn't seem to work Bug #654206 [src:linux-2.6] linux-image-3.0.0-2-amd64: max_batch_time doesn't seem to work Marked as found in versions linux-2.6/3.2.15-1. Bug #670593 [src:linux-2.6] linux-image-3.2.0-2-amd64: max_batch_time not honoured or incorrect in /proc/mounts Marked as found in versions linux-2.6/3.1.6-1, linux-2.6/2.6.32-39, and linux-2.6/3.0.0-6. Merged 654206 670593 tags 654206 + patch upstream Bug #654206 [src:linux-2.6] linux-image-3.0.0-2-amd64: max_batch_time doesn't seem to work Bug #670593 [src:linux-2.6] linux-image-3.2.0-2-amd64: max_batch_time not honoured or incorrect in /proc/mounts Added tag(s) upstream and patch. Added tag(s) upstream and patch. fixed 654206 linux-2.6/3.3~rc6-1~experimental.1 Bug #654206 [src:linux-2.6] linux-image-3.0.0-2-amd64: max_batch_time doesn't seem to work Bug #670593 [src:linux-2.6] linux-image-3.2.0-2-amd64: max_batch_time not honoured or incorrect in /proc/mounts Marked as fixed in versions linux-2.6/3.3~rc6-1~experimental.1. Marked as fixed in versions linux-2.6/3.3~rc6-1~experimental.1. quit Stopping processing here. Please contact me if you need assistance. -- 654206: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654206 670593: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670593 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.133555938512908.transcr...@bugs.debian.org
Bug#669052: [regression 3.2.12 - 3.2.14] r8169 driver not automatically loaded
Jean-Louis Mounier wrote: Package: initramfs-tools Version: 0.101 [...] MODULES=most Hmm, that looks ok. Thanks. Please attach output from: * lsinitramfs /boot/initrd.img-3.2.0-1-amd64 * lsinitramfs /boot/initrd.img-3.2.0-2-amd64 * grep . /etc/modprobe.d/* I'd also be interested in the result of the following procedure: 1. Back up /boot/initrd.img-3.2.0-1-amd64 for later analysis. 2. update-initramfs -k 3.2.0-1-amd64 -u 3. Try to boot 3.2.6-1. Does it still load the r8169 module automatically? 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/20120427210357.GC2821@burratino
