Bug#464664: 2.6.24: X86_64 laptop hangs after logging powernow_k8 error while on battery
Jonathan Nieder jrnie...@gmail.com wrote: Thanks for reporting, and sorry for the long silence. That's understandable. Do you still have access to this hardware? If so, would you still be interested in pursuing this bug? (No is an ok answer, but please do let us know so we can plan accordingly.) The corresponding kernel bug was closed with a suggestion to reopen it if it can be reproduced with a recent kernel. I think that's entirely reasonable. I still have the hardware on a shelf somewhere here. At some point I'll take it out, clear the drive and install a recent Debian (probably easier than trying to upgrade a system that hasn't been booted for four years and there's nothing worth preserving on the disk anyway). That's a long way of saying, perhaps just close the bug and when I get to play with the hardware I'll reopen the bug if I can still reproduce the issue with an up to date kernel. -- 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/20120906082103.ga18...@jdc.jasonjgw.net
Bug#660804: [openadsl-users] [Bug 42809] New: kernel panic when receiving an ipsec packet
Eric Dumazet eric.duma...@gmail.com wrote: Which driver handles this Traverse Solos card ? solos_pci, which also requires the atm module. (I'm just trying to help here; I'm not affected by the 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/20120223014614.ga10...@jdc.jasonjgw.net
Bug#623308: linux-image-2.6.38-2-amd64: Lenovo X200 laptop fails to power down under 2.6.38
maximilian attems m...@stro.at wrote: any update on newer 3.0 linux images from testing? The problem hasn't occurred yet with the 3.0.0-1 kernel. Even with laptop-mode not loaded, it still sometimes occurred under 2.6.39. If my poweroff operations continue to succeed under 3.x for a while, we can declare it fixed upstream, I think, whether intentionally or otherwise. -- 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/20110913091143.ga24...@jdc.jasonjgw.net
Bug#623308: linux-image-2.6.38-2-amd64: Lenovo X200 laptop fails to power down under 2.6.38
Moritz Mühlenhoff j...@inutil.org wrote: On Mon, Apr 25, 2011 at 11:29:13AM +1000, Jason White wrote: Laptop-mode appears to be the cause; can you reproduce the bug by enabling it on your X200? How did you activate the laptop mode on your system? If I install laptop-mode-tools, the system still powers down just fine. laptop-mode is deactivated as part of the shutdown sequence, though. Laptop-mode was enabled on my system in the same way, namely by installing laptop-mode-tools. It should be disabled during the shutdown by the init script. I will post a follow-up if I can narrow down the cause further. -- 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/20110429070137.ga18...@jdc.jasonjgw.net
Bug#623308: linux-image-2.6.38-2-amd64: Lenovo X200 laptop fails to power down under 2.6.38
Moritz Mühlenhoff j...@inutil.org wrote: Hmm. I'm having a X200 myself and it powers down just fine with the current sid kernel. Are you using laptop-mode? I'll try it without this. BIOS differences are another possibility, I suppose. Possibly relevant is the fact that acpitool reports, under 2.6.38, that the battery status and thermal readings aren't available, whereas it works under 2.6.32. However, the thermal values are present under /proc/acpi/ibm. -- 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/20110425000352.ga6...@jdc.jasonjgw.net
Bug#623308: linux-image-2.6.38-2-amd64: Lenovo X200 laptop fails to power down under 2.6.38
Laptop-mode appears to be the cause; can you reproduce the bug by enabling it on your X200? -- 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/20110425012913.ga16...@jdc.jasonjgw.net
Bug#623308: linux-image-2.6.38-2-amd64: Lenovo X200 laptop fails to power down under 2.6.38
I've just tested this again, and the bug is still present as of the latest package incorporating 2.6.38.4: Linux jpc2 2.6.38-2-amd64 #1 SMP Sat Apr 23 18:47:49 UTC 2011 x86_64 GNU/Linux After completing the normal shutdown (unmounting file systems, etc.), the machine appears to stop very briefly and then it reboots. -- 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/20110424004910.ga17...@jdc.jasonjgw.net
Bug#623308: linux-image-2.6.38-2-amd64: Lenovo X200 laptop fails to power down under 2.6.38
Package: linux-2.6 Version: 2.6.38-3 Severity: normal After upgrading to 2.6.38-2-amd64, my Lenovo X200 laptop reboots instead of powering down when I run the poweroff command (or equivalently shutdown -h now). That is, the ordinary reboot/shutdown sequence takes place until the moment at which the machine should power off, but it returns to the BIOS screen and reboots instead. Reverting to 2.6.32-5 avoids the regression. -- Package-specific info: ** Version: Linux version 2.6.38-2-amd64 (Debian 2.6.38-3) (b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.5-15) ) #1 SMP Thu Apr 7 04:28:07 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.38-2-amd64 root=UUID=dd38c010-c08f-4ff6-bce0-d81452a3aceb ro quiet ** Tainted: C (1024) * Module from drivers/staging has been loaded. ** Kernel log: [8.552237] usbcore: registered new interface driver uvcvideo [8.552239] USB Video Class driver (v1.0.0) [ 11.762974] loop: module loaded [ 11.921533] speakup: module is from the staging directory, the quality is unknown, you have been warned. [ 11.924765] input: Speakup as /devices/virtual/input/input14 [ 11.924850] speakup 3.1.6: initialized [ 11.924864] synth name on entry is: (null) [ 11.925253] initialized device: /dev/synth, node (MAJOR 10, MINOR 25) [ 11.933515] speakup_soft: module is from the staging directory, the quality is unknown, you have been warned. [ 11.934278] synth probe [ 11.934328] initialized device: /dev/softsynth, node (MAJOR 10, MINOR 26) [ 15.488233] e1000e :00:19.0: irq 44 for MSI/MSI-X [ 15.544149] e1000e :00:19.0: irq 44 for MSI/MSI-X [ 15.544509] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 16.154060] RPC: Registered udp transport module. [ 16.154063] RPC: Registered tcp transport module. [ 16.154065] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 16.274675] FS-Cache: Loaded [ 16.341248] FS-Cache: Netfs 'nfs' registered for caching [ 16.369054] Installing knfsd (copyright (C) 1996 o...@monad.swb.de). [ 17.236963] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None [ 17.236967] e1000e :00:19.0: eth0: 10/100 speed: disabling TSO [ 17.237273] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 17.506338] fuse init (API version 7.16) [ 19.765474] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory [ 19.815238] NFSD: starting 90-second grace period [ 24.952270] Bluetooth: L2CAP ver 2.15 [ 24.952272] Bluetooth: L2CAP socket layer initialized [ 25.075718] Bluetooth: RFCOMM TTY layer initialized [ 25.075722] Bluetooth: RFCOMM socket layer initialized [ 25.075724] Bluetooth: RFCOMM ver 1.11 [ 25.387149] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 25.387151] Bluetooth: BNEP filters: protocol multicast [ 25.682655] Bluetooth: SCO (Voice Link) ver 0.6 [ 25.682658] Bluetooth: SCO socket layer initialized [ 26.068633] lp: driver loaded but no devices found [ 26.208953] ppdev: user-space parallel port driver [ 31.827819] CPUFREQ: Per core ondemand sysfs interface is deprecated - ignore_nice_load [ 32.419067] uhci_hcd :00:1a.0: PCI INT A disabled [ 32.419224] uhci_hcd :00:1a.0: power state changed by ACPI to D3 [ 32.419583] uhci_hcd :00:1a.2: PCI INT C disabled [ 32.419693] uhci_hcd :00:1a.2: power state changed by ACPI to D3 [ 32.419887] ehci_hcd :00:1a.7: PCI INT D disabled [ 32.419952] ehci_hcd :00:1a.7: PME# enabled [ 32.432180] ehci_hcd :00:1a.7: power state changed by ACPI to D3 [ 32.433207] uhci_hcd :00:1d.0: PCI INT A disabled [ 32.433321] uhci_hcd :00:1d.0: power state changed by ACPI to D3 [ 32.433845] ehci_hcd :00:1d.7: PCI INT D disabled [ 32.433910] ehci_hcd :00:1d.7: PME# enabled [ 32.452110] ehci_hcd :00:1d.7: power state changed by ACPI to D3 [ 32.586152] ehci_hcd :00:1a.7: power state changed by ACPI to D0 [ 32.600167] ehci_hcd :00:1a.7: BAR 0: set to [mem 0xf2926c00-0xf2926fff] (PCI address [0xf2926c00-0xf2926fff]) [ 32.600181] ehci_hcd :00:1a.7: power state changed by ACPI to D0 [ 32.600210] ehci_hcd :00:1a.7: restoring config space at offset 0xf (was 0x400, writing 0x40b) [ 32.600248] ehci_hcd :00:1a.7: restoring config space at offset 0x1 (was 0x290, writing 0x2900102) [ 32.600299] ehci_hcd :00:1a.7: PME# disabled [ 32.600311] ehci_hcd :00:1a.7: power state changed by ACPI to D0 [ 32.600321] ehci_hcd :00:1a.7: power state changed by ACPI to D0 [ 32.600339] ehci_hcd :00:1a.7: PCI INT D - GSI 23 (level, low) - IRQ 23 [ 32.600352] ehci_hcd :00:1a.7: setting latency timer to 64 [ 32.743244] ehci_hcd :00:1d.7: power state changed by ACPI to D0 [ 32.760089] ehci_hcd :00:1d.7: BAR 0: set to [mem 0xf2927000-0xf29273ff] (PCI address [0xf2927000-0xf29273ff]) [ 32.760103] ehci_hcd :00:1d.7: power state changed by ACPI to D0 [ 32.760131] ehci_hcd :00:1d.7: restoring config
Bug#619996: nfs-common: idmapd.conf(5) manual page missing
Package: nfs-common Version: 1:1.2.3-1 Severity: wishlist We're missing the idmapd.conf(5) manual page. I checked another distribution and found it there, however, so it does exist. -- 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/20110329025103.18852.51168.reportbug@localhost.localdomain
Bug#619996: nfs-common: idmapd.conf(5) manual page missing
Ben Hutchings b...@decadent.org.uk wrote: It is not included in the upstream source - even though idmapd(8) refers to it! That's weird. Fedora have it, howver. Perhaps this is a forward upstream 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/20110329040152.ga20...@jdc.jasonjgw.net
Bug#575353: linux-image-2.6.33-2-amd64: 2.6.33 fails to boot - unable to mount root fs
Package: linux-2.6 Version: 2.6.33-1~experimental.4 Severity: normal linux-image-2.6.32-3-amd64 is fine, but linux-image-2.6.33-2-amd64 from experimental won't boot. As I can't see the screen, I'm relying on others to report the error message, which is approximately as follows. Kernel panic - unable to mount root fs on unknown-block 0,0 The root file system is XFS, specified as a UUID in /boot/grub/grub.cfg. I also tried booting with the root=/dev/sda1 kernel parameter, but this still resulted in a kernel panic with a stack trace that I wasn't able to capture. I'm planning to set up network console to obtain traces regarding a CPU clock frequency issue on an old laptop that I should be in a position to test in the next week or so, and which is the subject of another outstanding bug report of mine. If necessary, I can apply the same technique here, although it's my primary workstation in this instance and unfortunately the only recovery technique seems to be to power cycle the machine. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: Hewlett-Packard product_name: HP xw6400 Workstation product_version: chassis_vendor: Hewlett-Packard chassis_version: bios_vendor: Hewlett-Packard bios_version: 786D4 v01.23 board_vendor: Hewlett-Packard board_name: 0A04h board_version: NA ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 5000X Chipset Memory Controller Hub [8086:25c0] (rev 12) Subsystem: Hewlett-Packard Company Device [103c:3014] Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Capabilities: access denied 00:02.0 PCI bridge [0604]: Intel Corporation 5000 Series Chipset PCI Express x4 Port 2 [8086:25e2] (rev 12) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Bus: primary=00, secondary=10, subordinate=20, sec-latency=0 I/O behind bridge: 2000-2fff Memory behind bridge: d520-d76f Prefetchable memory behind bridge: d020-d03f Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- BridgeCtl: Parity- SERR+ NoISA+ VGA- MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: access denied Kernel driver in use: pcieport 00:03.0 PCI bridge [0604]: Intel Corporation 5000 Series Chipset PCI Express x4 Port 3 [8086:25e3] (rev 12) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Bus: primary=00, secondary=60, subordinate=60, sec-latency=0 Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- BridgeCtl: Parity- SERR+ NoISA+ VGA- MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: access denied Kernel driver in use: pcieport 00:04.0 PCI bridge [0604]: Intel Corporation 5000X Chipset PCI Express x16 Port 4-7 [8086:25fa] (rev 12) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Bus: primary=00, secondary=40, subordinate=40, sec-latency=0 I/O behind bridge: 1000-1fff Memory behind bridge: d100-d31f Prefetchable memory behind bridge: c000-d01f Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- BridgeCtl: Parity- SERR+ NoISA- VGA+ MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: access denied Kernel driver in use: pcieport 00:05.0 PCI bridge [0604]: Intel Corporation 5000 Series Chipset PCI Express x4 Port 5 [8086:25e5] (rev 12) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Bus: primary=00, secondary=fe, subordinate=fe, sec-latency=0
Bug#575353: linux-image-2.6.33-2-amd64: 2.6.33 fails to boot - unable to mount root fs
maximilian attems m...@stro.at wrote: aboves error message shows that there is no initramfs passed by the bootloader. which grub or lilo do you use? Grub 2. Regenerating the initramfs is what I tried first, but it didn't help. I'll try to investigate further. -- 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/20100325230831.ga8...@jdc.jasonjgw.net
Bug#575353: linux-image-2.6.33-2-amd64: 2.6.33 fails to boot - unable to mount root fs
maximilian attems m...@stro.at wrote: upps sorry, wrong message previously got confused. invoke *if and only if* sda is your harddisc where boot loader is on install-grub /dev/sda update-grub also check that you completed upgrade from grub to grub2. I can confirm the latter; Grub 2 has been working (not chain-loaded anymore) since late last year on this system. It will load 2.6.32-3 fine but not 2.6.33-2. I can re-install it if that would 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/20100326001203.ga14...@jdc.jasonjgw.net
Bug#575353: linux-image-2.6.33-2-amd64: 2.6.33 fails to boot - unable to mount root fs
I ran grub-install /dev/sda and (just to be sure) rebuilt the initramfs. After rebooting, kernel 2.6.33-2 loaded successfully. Thank you for the help. I don't know why everything wasn't updated automatically; perhaps grub-pc 1.98 didn't re-install itself during the upgrade. -- 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/20100326003801.ga3...@jdc.jasonjgw.net
Bug#562025: linux-image-2.6.32-trunk-amd64: After boot, the current virtual console is not TTY1
Package: linux-2.6 Version: 2.6.32-2 Severity: normal I am experiencing the problem described here: http://article.gmane.org/gmane.linux.kernel/927536/ after upgrading to the 2.6.32 kernel. The symptom is that after boot, the current virtual console is not tty1, but instead, for example, tty6 or tty3 (apparently randomly). -- Package-specific info: ** Version: Linux version 2.6.32-trunk-amd64 (Debian 2.6.32-2) (b...@decadent.org.uk) (gcc version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Thu Dec 17 06:29:18 UTC 2009 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-trunk-amd64 root=UUID=7e6b3589-6e9d-49d9-845e-80bc54b055cb ro quiet ** Not tainted ** Kernel log: [9.083243] mptsas: ioc0: attaching raid volume, channel 1, id 0 [9.083736] scsi 6:1:0:0: Direct-Access LSILOGIC Logical Volume 3000 PQ: 0 ANSI: 2 [9.092062] sd 6:1:0:0: [sda] 285155328 512-byte logical blocks: (145 GB/135 GiB) [9.092296] sd 6:1:0:0: [sda] Write Protect is off [9.092300] sd 6:1:0:0: [sda] Mode Sense: 03 00 00 08 [9.092695] sd 6:1:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [9.093693] sda: sda1 [9.103095] sd 6:1:0:0: [sda] Attached SCSI disk [9.242615] device-mapper: uevent: version 1.0.3 [9.242735] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-de...@redhat.com [9.267685] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [9.268689] SGI XFS Quota Management subsystem [9.277879] XFS mounting filesystem sda1 [9.339085] Ending clean XFS mount for filesystem: sda1 [ 10.853606] udev: starting version 149 [ 11.385131] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [ 11.392178] ACPI Error (dsfield-0143): [CAPD] Namespace lookup failure, AE_ALREADY_EXISTS [ 11.392185] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0._OSC] (Node 88013fa3f9a0), AE_ALREADY_EXISTS [ 11.392214] ACPI Warning for \_SB_.PCI0._OSC: Parameter count mismatch - ASL declared 5, ACPI requires 4 (20090903/nspredef-336) [ 11.392338] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [ 11.401913] ACPI: WMI: Mapper loaded [ 11.522203] parport_pc 00:07: reported by Plug and Play ACPI [ 11.522259] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE] [ 11.745899] RME Digi9652 (Hammerfall) :01:04.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [ 11.775416] ACPI: SSDT bffe95de 008C4 (v01 COMPAQ CPU_TM2 0001 MSFT 010E) [ 11.775765] processor LNXCPU:00: registered as cooling_device0 [ 11.776026] processor LNXCPU:01: registered as cooling_device1 [ 11.776417] processor LNXCPU:02: registered as cooling_device2 [ 11.776691] processor LNXCPU:03: registered as cooling_device3 [ 11.846275] intel_rng: Firmware space is locked read-only. If you can't or [ 11.846276] intel_rng: don't want to disable this in firmware setup, and if [ 11.846277] intel_rng: you are certain that your system has a functional [ 11.846279] intel_rng: RNG, try using the 'no_fwh_detect' option. [ 11.972654] usbcore: registered new interface driver snd-usb-audio [ 12.082608] alloc irq_desc for 21 on node -1 [ 12.082611] alloc kstat_irqs on node -1 [ 12.082619] HDA Intel :00:1b.0: PCI INT A - GSI 21 (level, low) - IRQ 21 [ 12.082674] HDA Intel :00:1b.0: setting latency timer to 64 [ 12.183050] EDAC MC: Ver: 2.1.0 Dec 17 2009 [ 12.232045] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input6 [ 12.234922] EDAC MC0: Giving out device to 'i5000_edac.c' 'I5000': DEV :00:10.0 [ 12.234943] EDAC PCI0: Giving out device to module 'i5000_edac' controller 'EDAC PCI controller': DEV ':00:10.0' (POLLED) [ 13.376934] loop: module loaded [ 13.400237] scsi 6:0:0:0: Attached scsi generic sg0 type 0 [ 13.400351] scsi 6:0:1:0: Attached scsi generic sg1 type 0 [ 13.400416] sd 6:1:0:0: Attached scsi generic sg2 type 0 [ 13.412838] smsc47b397: found SMSC SCH5307-NS (base address 0x0480, revision 0) [ 13.412866] ACPI: I/O resource smsc47b397 [0x480-0x481] conflicts with ACPI region SIOH [0x480-0x48f] [ 13.412921] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 13.456511] coretemp coretemp.0: Using relative temperature scale! [ 13.456621] coretemp coretemp.1: Using relative temperature scale! [ 13.456725] coretemp coretemp.2: Using relative temperature scale! [ 13.456842] coretemp coretemp.3: Using relative temperature scale! [ 13.523131] tun: Universal TUN/TAP device driver, 1.6 [ 13.523134] tun: (C) 1999-2004 Max Krasnyansky m...@qualcomm.com [ 13.544796] input: PC Speaker as /devices/platform/pcspkr/input/input7 [ 14.065621] Error: Driver 'pcspkr' is already registered, aborting... [ 14.530673] fuse init (API version 7.13) [ 16.170234] alloc irq_desc for 33 on node -1 [ 16.170238] alloc kstat_irqs on node -1 [ 16.170455]
Bug#560272: initramfs-tools: fails to mount BTRFS root file system under KVM
maximilian attems m...@stro.at wrote: you could simply use rootfstype bootarg, as described in man initramfs-tools. My mistake was to enter it in uppercase (corresponding to the name of the environment variable in the script) rather than in lowercase as I should have done. It works now. Thanks. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#560272: initramfs-tools: fails to mount BTRFS root file system under KVM
Package: initramfs-tools Version: 0.93.4 Severity: wishlist To experiment with BTRFS as the root file system under KVM, I added btrfs and associated modules to /etc/initramfs-tools/modules and built an initrd image, which I then installed to an EXT3 partition in the QCOW2 image to be loaded by KVM. Grub 2 is used as the boot loader, Debian kernel 2.6.32-trunk-amd64. Btrfs is the root file system. (/boot on /dev/hda1, / on /dev/hda2). The initrd fails with a no such device error mounting the root file system and exits to the initrd shell environment. If I then mount the root file system manually: mount /dev/hda2 /root it succeeds, which shows that the btrfs modules are working. Since Btrfs remains experimental, this is probably a low-priority issue, so I've set it to wishlist for now (you're welcome to change this if appropriate, of course.) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#560272: initramfs-tools: fails to mount BTRFS root file system under KVM
Editing scripts.local to hard-code the file system type worked around this bug. I suppose this is now a wishlist bug for Btrfs file system type detection. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#550190: linux-image-2.6.31-trunk-amd64: SCSI warnings/errors with LSI SAS1064E controller
Package: linux-2.6 Version: 2.6.31-1~experimental.1 Severity: normal After upgrading to 2.6.31 from 2.6.30, I get the following, quite frequently, in my log. Oct 8 19:15:03 jdc kernel: [34919.532016] sd 6:1:0:0: strange observation, the queue depth is (64) meanwhile fw queue depth (65) Oct 8 19:15:37 jdc kernel: [34953.528772] sd 6:1:0:0: strange observation, the queue depth is (64) meanwhile fw queue depth (65) Oct 8 19:15:37 jdc kernel: [34953.540511] sd 6:1:0:0: Queue depth not changed yet I haven't found any data corruption, at least not so far. This is my personal workstation, not a test machine, so I wish to avoid file system/data corruption where possible. There are two SAS disks which the previous owner of the machine configured for striping, 73Gb each. -- Package-specific info: ** Version: Linux version 2.6.31-trunk-amd64 (Debian 2.6.31-1~experimental.1) (m...@debian.org) (gcc version 4.3.3 (Debian 4.3.3-5) ) #1 SMP Sun Oct 4 20:37:35 UTC 2009 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.31-trunk-amd64 root=UUID=7e6b3589-6e9d-49d9-845e-80bc54b055cb ro quiet ** Not tainted ** Kernel log: [ 45.521664] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 45.521667] usb 1-7: Product: hp LaserJet 2430 [ 45.521670] usb 1-7: Manufacturer: Hewlett-Packard [ 45.521672] usb 1-7: SerialNumber: CNBG48D047 [ 45.521787] usb 1-7: configuration #1 chosen from 1 choice [ 45.657162] usblp0: USB Bidirectional printer dev 8 if 0 alt 1 proto 2 vid 0x03F0 pid 0x2A17 [ 45.657186] usbcore: registered new interface driver usblp [ 621.417640] mtrr: no MTRR for c000,1000 found [ 628.658310] usb 1-7: USB disconnect, address 8 [ 628.658468] usblp0: removed [ 1327.880446] sd 6:1:0:0: Queue depth not changed yet [ 1352.588020] sd 6:1:0:0: Queue depth not changed yet [ 1363.672517] sd 6:1:0:0: Queue depth not changed yet [ 1370.528250] sd 6:1:0:0: Queue depth not changed yet [ 1370.540010] sd 6:1:0:0: Queue depth not changed yet [ 1495.328613] sd 6:1:0:0: Queue depth not changed yet [ 1495.364828] sd 6:1:0:0: Queue depth not changed yet [ 2958.072271] sd 6:1:0:0: Queue depth not changed yet [ 2959.224018] sd 6:1:0:0: Queue depth not changed yet [ 2965.340273] sd 6:1:0:0: strange observation, the queue depth is (64) meanwhile fw queue depth (65) [ 2968.960515] sd 6:1:0:0: Queue depth not changed yet [ 2969.284769] sd 6:1:0:0: Queue depth not changed yet [ 2969.292508] sd 6:1:0:0: Queue depth not changed yet [ 2975.960018] sd 6:1:0:0: Queue depth not changed yet [ 2976.312624] sd 6:1:0:0: Queue depth not changed yet [ 2981.164517] sd 6:1:0:0: Queue depth not changed yet [ 2981.628516] sd 6:1:0:0: Queue depth not changed yet [ 2990.772520] sd 6:1:0:0: Queue depth not changed yet [ 2991.048514] sd 6:1:0:0: Queue depth not changed yet [ 2991.060271] sd 6:1:0:0: Queue depth not changed yet [ 3003.706760] udev: starting version 146 [ 3005.516770] sd 6:1:0:0: Queue depth not changed yet [ 3007.452139] sd 6:1:0:0: strange observation, the queue depth is (64) meanwhile fw queue depth (65) [ 3007.456022] sd 6:1:0:0: strange observation, the queue depth is (64) meanwhile fw queue depth (65) [ 3025.212023] sd 6:1:0:0: Queue depth not changed yet [ 3033.072024] sd 6:1:0:0: strange observation, the queue depth is (64) meanwhile fw queue depth (65) [ 3033.072030] sd 6:1:0:0: strange observation, the queue depth is (64) meanwhile fw queue depth (65) [ 3060.240018] sd 6:1:0:0: Queue depth not changed yet [ 3060.244508] sd 6:1:0:0: Queue depth not changed yet [ 3195.368271] sd 6:1:0:0: Queue depth not changed yet [ 3195.396011] sd 6:1:0:0: Queue depth not changed yet [ 6014.440268] sd 6:1:0:0: Queue depth not changed yet [ 6014.456515] sd 6:1:0:0: Queue depth not changed yet [10059.184025] usb 1-7: new high speed USB device using ehci_hcd and address 9 [10059.317685] usb 1-7: New USB device found, idVendor=03f0, idProduct=2a17 [10059.317689] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [10059.317692] usb 1-7: Product: hp LaserJet 2430 [10059.317694] usb 1-7: Manufacturer: Hewlett-Packard [10059.317696] usb 1-7: SerialNumber: CNBG48D047 [10059.317810] usb 1-7: configuration #1 chosen from 1 choice [10059.446896] usblp0: USB Bidirectional printer dev 9 if 0 alt 1 proto 2 vid 0x03F0 pid 0x2A17 [10168.489751] mtrr: no MTRR for c000,1000 found [10181.958051] usb 1-7: USB disconnect, address 9 [10181.958211] usblp0: removed [13240.480017] sd 6:1:0:0: Queue depth not changed yet [18305.017304] mtrr: no MTRR for c000,1000 found [20461.744765] usb 1-7: new high speed USB device using ehci_hcd and address 10 [20461.877117] usb 1-7: New USB device found, idVendor=03f0, idProduct=2a17 [20461.877121] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [20461.877124] usb 1-7: Product: hp LaserJet 2430 [20461.877126] usb 1-7: Manufacturer: Hewlett-Packard [20461.877129] usb 1-7: SerialNumber: CNBG48D047 [20461.877244] usb 1-7: configuration #1
Bug#464664: linux-image-2.6.24-1-amd64: X86_64 laptop hangs after logging powernow_k8 error while on battery
By way of follow-up, I think I should be able to use netconsole to obtain (non-visual) access to the kernel oops which this bug causes. I should have time before the end of the year to work on it by upgrading to kernel 2.6.31 and conducting some tests. this machine is not my current laptop anymore, therefore it hasn't been receiving any attention. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#550190: linux-image-2.6.31-trunk-amd64: SCSI warnings/errors with LSI SAS1064E controller
dann frazier da...@debian.org wrote: hmm.. wonder if this would help: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=9d2e9d66a3f032667934144cd61c396ba49f090d Would you be able to test that? I'll test it against 2.6.31.3 in the next few days. Maybe it will also appear in a 2.6.31.x stable release if it's considered to be a bug fix. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#550190: Info received (Bug#550190: linux-image-2.6.31-trunk-amd64: SCSI warnings/errors with LSI SAS1064E controller)
Unfortunately, the patch doesn't solve this problem, at least not by itself. Are there any other options besides bisecting 2.6.30 to 2.6.31? I don't mind doing a bisect, but it's likely to take more time than I have available in the near future. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#534598: linux-image-2.6.30-1-amd64: Can also be fixed by Alsa settings
Package: linux-image-2.6.30-1-amd64 Version: 2.6.30-5 Severity: normal I was able to correct this by enabling the Beep,0 amixer setting, then specifying a non-zero value for that control, and finally setting a reasonable value for the Speaker,0 parameter. I had to downgrade the kernel due to an unrelated problem (an oops for which I wasn't able to collect the call trace, possibly swap related), but as for this bug, I suspect something has changed in the handling of the speaker device as of 2.6.30. -- Package-specific info: -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.29-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.30-1-amd64 depends on: ii debconf [debconf-2.0] 1.5.27 Debian configuration management sy ii initramfs-tools [linux-initra 0.93.4 tools for generating an initramfs ii module-init-tools 3.9-2 tools for managing Linux kernel mo linux-image-2.6.30-1-amd64 recommends no packages. Versions of packages linux-image-2.6.30-1-amd64 suggests: ii grub 0.97-55GRand Unified Bootloader (dummy pa ii grub-legacy [grub]0.97-55GRand Unified Bootloader (Legacy v pn linux-doc-2.6.30 none (no description available) -- debconf information excluded -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#464664: linux-image-2.6.24-1-amd64: X86_64 laptop hangs after logging powernow_k8 error while on battery
On Tue, May 20, 2008 at 04:27:09PM +0200, maximilian attems wrote: can we have an update for a recent kernel aka 2.6.25 from sid. installs just fine in testing. May 23 15:55:41 jpc kernel: [ 38.255997] powernow-k8: error - out of sync, fix 0x8 0x0, vid 0x6 0x12 uname -a Linux jpc 2.6.25-2-amd64 #1 SMP Wed May 14 14:04:05 UTC 2008 x86_64 GNU/Linux This might or might not be related: when I try to load acpi to obtain details of battery status: modprobe acpi FATAL: Error inserting acpi_cpufreq (/lib/modules/2.6.25-2-amd64/kernel/arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.ko): Device or resource busy I'll experiment with not loading the ondemand governor in /etc/modules. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#464664: linux-image-2.6.24-1-amd64: X86_64 laptop hangs after logging powernow_k8 error while on battery
On Fri, May 23, 2008 at 11:22:30AM +0200, maximilian attems wrote: please file upstream in bugzilla.kernel.org and let us know the bug number. Reported as bug 10784 at bugzilla.kernel.org. I cited this Debian bug in the kernel.org bug report and noted your request that the bug be taken upstream. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#464664: linux-image-2.6.24-1-amd64: X86_64 laptop hangs after logging powernow_k8 error while on battery
Package: linux-image-2.6.24-1-amd64 Version: 2.6.24-2 Severity: normal My laptop has an AMD Athlon64 processor. With recent kernels (at least 2.6.22 and 2.6.24, possibly earlier), if run on battery, the laptop eventually hangs. The error is as reported in the syslog output below. I am using the powernow-k8 module with the ondemand CPU frequency governor. When connected to AC power, the laptop does not encounter this problem. Feb 7 11:02:11 jpc kernel: ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3]) Feb 7 11:02:11 jpc kernel: powernow-k8: Found 1 AMD Athlon(tm) 64 Processor 3000+ processors (1 cpu cores) (version 2.20.00) Feb 7 11:02:11 jpc kernel: powernow-k8:0 : fid 0xa (1800 MHz), vid 0x2 Feb 7 11:02:11 jpc kernel: powernow-k8:1 : fid 0x8 (1600 MHz), vid 0x6 Feb 7 11:02:11 jpc kernel: powernow-k8:2 : fid 0x0 (800 MHz), vid 0x12 Feb 7 11:02:25 jpc kernel: powernow-k8: error - out of sync, fix 0xa 0x0, vid 0x2 0x12 Here is /proc/cpuinfo: processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 4 model name : AMD Athlon(tm) 64 Processor 3000+ stepping: 10 cpu MHz : 800.000 cache size : 1024 KB fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext lm 3dnowext 3dnow up rep_good bogomips: 1597.66 TLB size: 1024 4K pages clflush size: 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts fid vid ttp -- Package-specific info: ** Version: Linux version 2.6.24-1-amd64 (Debian 2.6.24-2) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080114 (prerelease) (Debian 4.1.2-19)) #1 SMP Thu Jan 31 19:46:44 UTC 2008 ** Command line: root=/dev/hda1 ro ** Not tainted ** Kernel log: swsusp: Marking nosave pages: 0009f000 - 0010 swsusp: Basic memory bitmaps created swsusp: Basic memory bitmaps freed SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled SGI XFS Quota Management subsystem XFS mounting filesystem hda1 usb 2-1: configuration #1 chosen from 1 choice Ending clean XFS mount for filesystem: hda1 pci_hotplug: PCI Hot Plug PCI Core version: 0.5 shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 sis96x_smbus :00:02.1: SiS96x SMBus base address: 0x0c00 input: Power Button (FF) as /class/input/input2 ACPI: Power Button (FF) [PWRF] input: Lid Switch as /class/input/input3 ACPI: Lid Switch [LID] input: Sleep Button (CM) as /class/input/input4 ACPI: Sleep Button (CM) [SLPB] input: Power Button (CM) as /class/input/input5 ACPI: Power Button (CM) [PWRB] ACPI: AC Adapter [AC0] (on-line) ACPI: Battery Slot [BAT0] (battery present) input: Video Bus as /class/input/input6 ACPI: Video Device [VGA] (multi-head: yes rom: no post: no) ACPI: PCI Interrupt :00:02.6[C] - GSI 18 (level, low) - IRQ 18 ACPI: PCI Interrupt :00:02.7[C] - GSI 18 (level, low) - IRQ 18 intel8x0_measure_ac97_clock: measured 55348 usecs intel8x0: clocking to 48000 Yenta: CardBus bridge found at :00:09.0 [1584:3005] Yenta O2: res at 0x94/0xD4: 00/ea Yenta O2: enabling read prefetch/write burst Yenta: ISA IRQ mask 0x0ab8, PCI irq 17 Socket status: 3006 Yenta: CardBus bridge found at :00:09.1 [1584:3005] Yenta: ISA IRQ mask 0x0ab8, PCI irq 17 Socket status: 3006 ACPI: PCI Interrupt :00:0b.0[A] - GSI 19 (level, low) - IRQ 19 ath5k_pci :00:0b.0: registered as 'phy0' usbcore: registered new interface driver usbserial drivers/usb/serial/usb-serial.c: USB Serial support registered for generic usbcore: registered new interface driver usbserial_generic drivers/usb/serial/usb-serial.c: USB Serial Driver core phy0: Selected rate control algorithm 'simple' input: PC Speaker as /class/input/input7 drivers/usb/serial/usb-serial.c: USB Serial support registered for MCT U232 mct_u232 2-1:1.0: MCT U232 converter detected usb 2-1: MCT U232 converter now attached to ttyUSB0 usbcore: registered new interface driver mct_u232 drivers/usb/serial/mct_u232.c: Magic Control Technology USB-RS232 converter driver z2.1 Synaptics Touchpad, model: 1, fw: 5.9, id: 0xa36eb3, caps: 0x904713/0x10008 irda_init() NET: Registered protocol family 23 input: SynPS/2 Synaptics TouchPad as /class/input/input8 ath5k phy0: Atheros AR5213A chip found (MAC: 0x59, PHY: 0x43) ath5k phy0: RF5112A multiband radio found (0x36) pnp: the driver 'parport_pc' has been registered parport_pc 00:08: reported by Plug and Play ACPI parport0: PC-style at 0x378 (0x778), irq 7, using FIFO [PCSPP,TRISTATE,COMPAT,EPP,ECP] pnp: the driver 'nsc-ircc' has been registered parport_pc 00:08: driver attached nsc_ircc_pnp_probe() : From PnP, found firbase 0x2F8 ; irq 3 ; dma 1. nsc-ircc 00:07: driver attached nsc-ircc, chip-init nsc-ircc, Found chip at base=0x02e nsc-ircc, driver loaded (Dag Brattli) nsc_ircc_open(),
