Bug#958737: linux-image-5.5.0-2-amd64: Intel Cannon Point-LP audio controller no longer works
Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: xhci_hcd Kernel modules: xhci_pci ** USB devices: Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 002: ID 2188:0747 CalDigit Card Reader Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 2188:6533 CalDigit, Inc. CalDigit Thunderbolt 3 Audio Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 06cb:00bd Synaptics, Inc. Bus 001 Device 002: ID 04f2:b67c Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.5.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-5.5.0-2-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.136 ii kmod27+20200310-2 ii linux-base 4.6 Versions of packages linux-image-5.5.0-2-amd64 recommends: ii apparmor 2.13.4-1+b1 ii firmware-linux-free 20200122-1 Versions of packages linux-image-5.5.0-2-amd64 suggests: pn debian-kernel-handbook ii extlinux3:6.04~git20190206.bf6db5b4+dfsg1-2 ii grub-efi-amd64 2.04-6 pn linux-doc-5.5 Versions of packages linux-image-5.5.0-2-amd64 is related to: pn firmware-amd-graphics pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x ii firmware-brcm8021120190717-2 pn firmware-cavium ii firmware-intel-sound 20190717-2 pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv ii firmware-iwlwifi 20190717-2 pn firmware-libertas pn firmware-linux-nonfree ii firmware-misc-nonfree 20190717-2 pn firmware-myricom pn firmware-netxen pn firmware-qlogic pn firmware-realtek pn firmware-samsung pn firmware-siano pn firmware-ti-connectivity pn xen-hypervisor -- no debconf information -- brian m. carlson: Houston, Texas, US OpenPGP: https://keybase.io/bk2204 signature.asc Description: PGP signature
Bug#958126: linux-image-5.5.0-2-amd64: Alt-SysRq-x no longer lifts Secure Boot restrictions
On 2020-04-18 at 21:59:35, Ben Hutchings wrote: > Control: tag -1 wontfix > > On Sat, 2020-04-18 at 18:50 +0000, brian m. carlson wrote: > > Package: src:linux > > Version: 5.5.17-1 > > Severity: important > > > > By default, Debian ships kernels such that when booted with Secure Boot, > > that a user cannot hibernate their computer. However, the combination > > Alt-SysRq-x is documented in the wiki (which is linked to from the > > kernel) to lift these restrictions and allow the user to hibernate. > > > > However, in this kernel version that does not work, and the user must > > either disable secure boot or forego hibernation. When pressing > > Alt-SysRq-x, the following is printed: > > > > sysrq: HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) > > memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) > > show-backtrace-all-active-cpus(l) show-memory-usage(m) nice-all-RT-tasks(n) > > poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) > > show-task-states(t) unmount(u) force-fb(V) show-blocked-tasks(w) > > dump-ftrace-buffer(z) > [...] > > This was an intentional change listed in the changelog, fixing bug > #947021. Thanks for mentioning the wiki; I'll update that to reflect > current reality. It looks like Ubuntu allows people physically present to use the key still with their proposed patch. Is there a reason that patch can't be applied here? > If you can't live with the restrictions of Secure Boot, you'll have to > turn it off. Can you explain why this restriction is required in the first place? Other operating systems use Secure Boot and allow hibernation, so it can't be that it's an intrinsic limitation. I'd like to have the behavior where I know that my boot process hasn't been tampered with, but I don't need to be locked out of my system or have important features turned off. Surely that's a valid use case that should be supported. -- brian m. carlson: Houston, Texas, US OpenPGP: https://keybase.io/bk2204 signature.asc Description: PGP signature
Bug#958126: linux-image-5.5.0-2-amd64: Alt-SysRq-x no longer lifts Secure Boot restrictions
Kernel modules: xhci_pci 0d:00.0 Ethernet controller [0200]: Intel Corporation I210 Gigabit Network Connection [8086:1533] (rev 03) Subsystem: CalDigit, Inc. I210 Gigabit Network Connection [1ab6:0214] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: igb Kernel modules: igb 2d:00.0 USB controller [0c03]: Intel Corporation JHL6540 Thunderbolt 3 USB Controller (C step) [Alpine Ridge 4C 2016] [8086:15d4] (rev 02) (prog-if 30 [XHCI]) Subsystem: Lenovo JHL6540 Thunderbolt 3 USB Controller (C step) [Alpine Ridge 4C 2016] [17aa:2292] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: xhci_hcd Kernel modules: xhci_pci ** USB devices: Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 002: ID 2188:0747 CalDigit Card Reader Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 2188:6533 CalDigit, Inc. CalDigit Thunderbolt 3 Audio Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 06cb:00bd Synaptics, Inc. Bus 001 Device 002: ID 04f2:b67c Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.5.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-5.5.0-2-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.136 ii kmod27-2 ii linux-base 4.6 Versions of packages linux-image-5.5.0-2-amd64 recommends: ii apparmor 2.13.4-1+b1 ii firmware-linux-free 20200122-1 Versions of packages linux-image-5.5.0-2-amd64 suggests: pn debian-kernel-handbook ii extlinux3:6.04~git20190206.bf6db5b4+dfsg1-2 ii grub-efi-amd64 2.04-5 pn linux-doc-5.5 Versions of packages linux-image-5.5.0-2-amd64 is related to: pn firmware-amd-graphics pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x ii firmware-brcm8021120190717-2 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv ii firmware-iwlwifi 20190717-2 pn firmware-libertas pn firmware-linux-nonfree ii firmware-misc-nonfree 20190717-2 pn firmware-myricom pn firmware-netxen pn firmware-qlogic pn firmware-realtek pn firmware-samsung pn firmware-siano pn firmware-ti-connectivity pn xen-hypervisor -- no debconf information -- brian m. carlson: Houston, Texas, US OpenPGP: https://keybase.io/bk2204 signature.asc Description: PGP signature
Bug#777644: linux: UDF complains about inode size of file it just created
=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-image-3.18.0-trunk-amd64 depends on: ii cdebconf [debconf-2.0] 0.192 ii debconf [debconf-2.0] 1.5.55 ii initramfs-tools [linux-initramfs-tool] 0.118 ii kmod18-3 ii linux-base 3.5 ii module-init-tools 18-3 Versions of packages linux-image-3.18.0-trunk-amd64 recommends: ii firmware-linux-free 3.3 ii irqbalance 1.0.6-3 Versions of packages linux-image-3.18.0-trunk-amd64 suggests: pn debian-kernel-handbook none pn grub-pc | grub-efi | extlinux none pn linux-doc-3.18 none Versions of packages linux-image-3.18.0-trunk-amd64 is related to: pn firmware-atherosnone pn firmware-bnx2 none pn firmware-bnx2x none pn firmware-brcm80211 none ii firmware-intelwimax 0.43 pn firmware-ipw2x00none pn firmware-ivtv none ii firmware-iwlwifi0.43 pn firmware-libertas none pn firmware-linux none pn firmware-linux-nonfree none pn firmware-myricomnone pn firmware-netxen none pn firmware-qlogic none pn firmware-ralink none pn firmware-realteknone pn xen-hypervisor none -- debconf information: linux-image-3.18.0-trunk-amd64/prerm/removing-running-kernel-3.18.0-trunk-amd64: true linux-image-3.18.0-trunk-amd64/postinst/depmod-error-initrd-3.18.0-trunk-amd64: false linux-image-3.18.0-trunk-amd64/postinst/mips-initrd-3.18.0-trunk-amd64: -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187 signature.asc Description: Digital signature
Bug#725275: 725275 is reproducible
I can reproduce the inability to boot 3.11-trunk-amd64 (and the preceding 3.11-rc7-amd64) with initramfs-tools 0.114. With 0.113, everything works fine. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187 signature.asc Description: Digital signature
Bug#707311: initramfs-tools: nags about missing firmware that is not needed
Package: initramfs-tools Version: 0.112 Severity: wishlist On my server, I have an r8169 card which is functional without firmware. Since the firmware is not needed (and non-free), I have chosen not to install it. However, update-initramfs consistently informs me that the firmware is missing. It would be nice to have a documented option that tells initramfs-tools that I know the firmware is missing and just don't care. Please consider adding one. I have removed the system information because I am not sending this from the affected machine. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/mksh-static Versions of packages initramfs-tools depends on: ii cpio 2.11+dfsg-0.1 ii klibc-utils2.0.1-3.1 ii kmod 9-3 ii module-init-tools 9-3 ii udev 175-7.2 Versions of packages initramfs-tools recommends: ii busybox 1:1.20.0-8 Versions of packages initramfs-tools suggests: ii bash-completion 1:2.0-1 -- no debconf information -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187 signature.asc Description: Digital signature
Bug#693568: linux-image-3.6-trunk-amd64: audit subsystem is far too chatty
On Sun, Nov 18, 2012 at 12:36:44PM +0100, Bastian Blank wrote: On Sat, Nov 17, 2012 at 11:05:56PM +, brian m. carlson wrote: As you can see in the logs below, the audit subsystem logs entirely too many audit messages. It is rate limited. And one event every 30 seconds is not that much. I opened this at normal severity because it is rate-limited. If it were not, it would have been much worse. I still feel that potentially 2880 messages per day is too many for the kernel log without some sort of mechanism to disable the flow. Since I use chrome, which uses seccomp (apparently), this makes lots of useless noise in the logs, Chrome is not supported by Debian. Chromium is and does not show this behaviour in the latest available packages. That's because you're shipping version 22. Version 23 starts sandboxing all renderer processes, so you'll start seeing the bug soon enough. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187 signature.asc Description: Digital signature
Bug#693568: linux-image-3.6-trunk-amd64: audit subsystem is far too chatty
root hub Bus 003 Device 003: ID 147e:2016 Upek Biometric Touchchip/Touchstrip Fingerprint Sensor Bus 003 Device 004: ID 0a5c:217f Broadcom Corp. Bluetooth Controller Bus 003 Device 005: ID 04f2:b217 Chicony Electronics Co., Ltd Lenovo Integrated Camera (0.3MP) Bus 004 Device 005: ID 0781:5530 SanDisk Corp. Cruzer Bus 004 Device 003: ID 8086:0187 Intel Corp. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.6-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-3.6-trunk-amd64 depends on: ii cdebconf [debconf-2.0] 0.179 ii debconf [debconf-2.0] 1.5.46 ii initramfs-tools [linux-initramfs-tool] 0.109 ii kmod9-2 ii linux-base 3.5 ii module-init-tools 9-2 Versions of packages linux-image-3.6-trunk-amd64 recommends: ii firmware-linux-free 3.1 Versions of packages linux-image-3.6-trunk-amd64 suggests: pn debian-kernel-handbook none ii grub-pc 1.99-23.1 pn linux-doc-3.6 none Versions of packages linux-image-3.6-trunk-amd64 is related to: pn firmware-atherosnone pn firmware-bnx2 none pn firmware-bnx2x none pn firmware-brcm80211 none ii firmware-intelwimax 0.36 pn firmware-ipw2x00none pn firmware-ivtv none ii firmware-iwlwifi0.36 pn firmware-libertas none pn firmware-linux none pn firmware-linux-nonfree none pn firmware-myricomnone pn firmware-netxen none pn firmware-qlogic none pn firmware-ralink none pn firmware-realteknone pn xen-hypervisor none -- debconf information: linux-image-3.6-trunk-amd64/postinst/missing-firmware-3.6-trunk-amd64: linux-image-3.6-trunk-amd64/prerm/removing-running-kernel-3.6-trunk-amd64: true linux-image-3.6-trunk-amd64/postinst/ignoring-ramdisk: linux-image-3.6-trunk-amd64/postinst/depmod-error-initrd-3.6-trunk-amd64: false -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187 signature.asc Description: Digital signature
Bug#693568: closed by Ben Hutchings b...@decadent.org.uk (Re: Bug#693568: linux-image-3.6-trunk-amd64: audit subsystem is far too chatty)
On Sun, Nov 18, 2012 at 01:45:04AM +, Debian Bug Tracking System wrote: On Sat, 2012-11-17 at 23:05 +, brian m. carlson wrote: Package: src:linux Version: 3.6.6-1~experimental.1 Severity: normal As you can see in the logs below, the audit subsystem logs entirely too many audit messages. Since this is built into the kernel, I cannot unload the module to prevent it from logging. Since I use chrome, which uses seccomp (apparently), this makes lots of useless noise in the logs, preventing me from seeing important messages. Earlier versions of the kernel were not so verbose; please revert whatever change made the audit subsystem so chatty. [...] This is a bug in Chrome, please report it there. Last I checked, Chrome did not write to the kernel ring buffer. The kernel does not need to log every audit failure any more than it needs to log every time a process tries to read a file that it does not have permission to read or every segfault that occurs or every packet dropped. At the very least, there should be a file in procfs or sysfs that allows people to turn this off if they don't want their logs filled with useless crap. All sorts of unexpected behaviors are blocked on operating systems; very few of them deserve an entry in the kernel log. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187 signature.asc Description: Digital signature
Bug#645366: linux-image-3.1.0-rc7-amd64: suspend fails with process waiting for IO on unmounted drive
On Sat, Oct 15, 2011 at 05:25:26AM +0100, Ben Hutchings wrote: On Fri, 2011-10-14 at 22:52 +, brian m. carlson wrote: I don't understand why SIGINT would be delivered to ssh rather than to afio. Well, sshfs, not just ssh. afio is running under a shell script called tob (from the package of the same name). tob sets up the mount using: PRECMD='klist -5s || kinit bmc; sshfs bmc@castro:/media/backup/ /media/backup' When I hit Ctrl-C, something got sent SIGINT and tob cleaned itself up; part of the cleanup routine is to unmount the filesystem: POSTCMD='fusermount -u -z /media/backup' The command is called from a trap command in the shell script I believe. I'm not sure which program actually received the SIGINT itself, but /media/backup was eventually unmounted. * aborting disk IO requests when the underlying device disappears; [...] I believe this should have happened. Great. If the kernel were fixed so that happened, that would be satisfactory. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187 signature.asc Description: Digital signature
Bug#623290: Bug is fixed
I was just alerted that maximilian attems' message didn't get through, which has been fixed. Nevertheless, the bug can remain closed since it is working fine in 3.0 and 3.1-rc4. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187 signature.asc Description: Digital signature
Bug#630404: linux-image-3.0.0-rc2-amd64: uses a literal %d in wlan%d
min, 1000ns max) Interrupt: pin B routed to IRQ 17 Region 0: Memory at e4301000 (32-bit, non-prefetchable) [size=2K] Region 1: Memory at e4304000 (32-bit, non-prefetchable) [size=16K] Capabilities: access denied Kernel driver in use: firewire_ohci 16:00.0 Network controller [0280]: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller [14e4:4318] (rev 02) Subsystem: U.S. Robotics U.S.Robotics Wireless MAXg PC Card [16ec:0119] 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: 64 Interrupt: pin A routed to IRQ 16 Region 0: Memory at c400 (32-bit, non-prefetchable) [size=8K] Kernel driver in use: b43-pci-bridge ** USB devices: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) Bus 002 Device 003: ID 046d:c019 Logitech, Inc. Optical Tilt Wheel Mouse Bus 002 Device 004: ID 0a5c:4502 Broadcom Corp. Keyboard (Boot Interface Subclass) Bus 002 Device 005: ID 0a5c:4503 Broadcom Corp. Mouse (Boot Interface Subclass) Bus 002 Device 006: ID 0a5c:2148 Broadcom Corp. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-rc2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-3.0.0-rc2-amd64 depends on: ii cdebconf [debconf-2.0]0.155 Debian Configuration Management Sy ii debconf [debconf-2.0] 1.5.39 Debian configuration management sy ii initramfs-tools [linux-initra 0.99 tools for generating an initramfs ii linux-base3.2Linux image base package ii module-init-tools 3.16-1 tools for managing Linux kernel mo Versions of packages linux-image-3.0.0-rc2-amd64 recommends: ii firmware-linux-free 3 Binary firmware for various driver Versions of packages linux-image-3.0.0-rc2-amd64 suggests: ii grub-pc 1.99-6 GRand Unified Bootloader, version pn linux-doc-3.0.0 none (no description available) Versions of packages linux-image-3.0.0-rc2-amd64 is related to: pn firmware-bnx2 none (no description available) pn firmware-bnx2xnone (no description available) pn firmware-ipw2x00 none (no description available) pn firmware-ivtv none (no description available) ii firmware-iwlwifi 0.30 Binary firmware for Intel Wireless pn firmware-linuxnone (no description available) pn firmware-linux-nonfreenone (no description available) pn firmware-qlogic none (no description available) pn firmware-ralink none (no description available) pn xen-hypervisornone (no description available) -- debconf information: linux-image-3.0.0-rc2-amd64/postinst/depmod-error-initrd-3.0.0-rc2-amd64: false linux-image-3.0.0-rc2-amd64/postinst/ignoring-ramdisk: linux-image-3.0.0-rc2-amd64/postinst/missing-firmware-3.0.0-rc2-amd64: linux-image-3.0.0-rc2-amd64/prerm/removing-running-kernel-3.0.0-rc2-amd64: true -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187 signature.asc Description: Digital signature
Bug#624124: linux-image-2.6.39-rc4-amd64: no longer includes driver for iwl3945
: pin A routed to IRQ 46 Region 0: Memory at edf0 (32-bit, non-prefetchable) [size=4K] Capabilities: access denied Kernel driver in use: iwl3945 15:00.0 CardBus bridge [0607]: Texas Instruments PCIxx12 Cardbus Controller [104c:8039] Subsystem: Lenovo Device [17aa:202f] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 168, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 16 Region 0: Memory at e430 (32-bit, non-prefetchable) [size=4K] Bus: primary=15, secondary=16, subordinate=17, sec-latency=176 Memory window 0: e000-e3fff000 (prefetchable) Memory window 1: c400-c7fff000 I/O window 0: 8000-80ff I/O window 1: 8400-84ff BridgeCtl: Parity- SERR- ISA- VGA- MAbort- Reset+ 16bInt+ PostWrite+ 16-bit legacy interface ports at 0001 Kernel driver in use: yenta_cardbus 15:00.1 FireWire (IEEE 1394) [0c00]: Texas Instruments PCIxx12 OHCI Compliant IEEE 1394 Host Controller [104c:803a] (prog-if 10 [OHCI]) Subsystem: Lenovo Device [17aa:202e] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 64 (500ns min, 1000ns max) Interrupt: pin B routed to IRQ 17 Region 0: Memory at e4301000 (32-bit, non-prefetchable) [size=2K] Region 1: Memory at e4304000 (32-bit, non-prefetchable) [size=16K] Capabilities: access denied Kernel driver in use: firewire_ohci ** USB devices: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) Bus 002 Device 003: ID 046d:c019 Logitech, Inc. Optical Tilt Wheel Mouse Bus 002 Device 004: ID 0a5c:4502 Broadcom Corp. Keyboard (Boot Interface Subclass) Bus 002 Device 005: ID 0a5c:4503 Broadcom Corp. Mouse (Boot Interface Subclass) Bus 002 Device 006: ID 0a5c:2148 Broadcom Corp. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-2.6.39-rc4-amd64 depends on: ii cdebconf [debconf-2.0]0.155 Debian Configuration Management Sy ii debconf [debconf-2.0] 1.5.38 Debian configuration management sy ii initramfs-tools [linux-initra 0.98.8 tools for generating an initramfs ii linux-base3.2Linux image base package ii module-init-tools 3.12-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.39-rc4-amd64 recommends: ii firmware-linux-free 3 Binary firmware for various driver Versions of packages linux-image-2.6.39-rc4-amd64 suggests: ii grub-pc 1.99~rc1-13 GRand Unified Bootloader, version pn linux-doc-2.6.39 none (no description available) Versions of packages linux-image-2.6.39-rc4-amd64 is related to: pn firmware-bnx2 none (no description available) pn firmware-bnx2xnone (no description available) pn firmware-ipw2x00 none (no description available) pn firmware-ivtv none (no description available) ii firmware-iwlwifi 0.29 Binary firmware for Intel Wireless pn firmware-linuxnone (no description available) pn firmware-linux-nonfreenone (no description available) pn firmware-qlogic none (no description available) pn firmware-ralink none (no description available) pn xen-hypervisornone (no description available) -- debconf information: linux-image-2.6.39-rc4-amd64/postinst/depmod-error-initrd-2.6.39-rc4-amd64: false linux-image-2.6.39-rc4-amd64/postinst/ignoring-do-bootloader-2.6.39-rc4-amd64: * linux-image-2.6.39-rc4-amd64/postinst/missing-firmware-2.6.39-rc4-amd64: linux-image-2.6.39-rc4-amd64/prerm/removing-running-kernel-2.6.39-rc4-amd64: true -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
Bug#623290: linux-image-2.6.38-2-amd64: iwl3945 causes firmware errors
ii debconf [debconf-2.0] 1.5.38 Debian configuration management sy ii initramfs-tools [linux-initra 0.98.8 tools for generating an initramfs ii linux-base3.2Linux image base package ii module-init-tools 3.12-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.38-2-amd64 recommends: ii firmware-linux-free 3 Binary firmware for various driver Versions of packages linux-image-2.6.38-2-amd64 suggests: ii grub-pc 1.99~rc1-13 GRand Unified Bootloader, version pn linux-doc-2.6.38 none (no description available) Versions of packages linux-image-2.6.38-2-amd64 is related to: pn firmware-bnx2 none (no description available) pn firmware-bnx2xnone (no description available) pn firmware-ipw2x00 none (no description available) pn firmware-ivtv none (no description available) ii firmware-iwlwifi 0.29 Binary firmware for Intel Wireless pn firmware-linuxnone (no description available) pn firmware-linux-nonfreenone (no description available) pn firmware-qlogic none (no description available) pn firmware-ralink none (no description available) pn xen-hypervisornone (no description available) -- debconf information: linux-image-2.6.38-2-amd64/prerm/removing-running-kernel-2.6.38-2-amd64: true linux-image-2.6.38-2-amd64/postinst/ignoring-do-bootloader-2.6.38-2-amd64: linux-image-2.6.38-2-amd64/postinst/depmod-error-initrd-2.6.38-2-amd64: false linux-image-2.6.38-2-amd64/postinst/missing-firmware-2.6.38-2-amd64: -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187 signature.asc Description: Digital signature
Bug#599351: Caused by libdrm
I've done some testing on these bugs. After 599351, I moved back to
Linux 2.6.32-5-amd64, at which time I filed 599496 (because a very
similar problem occurred). I had installed libdrm{2,-intel1}
2.4.22~pre(something) and reverting back to 2.4.21-1~squeeze3 fixed the
problem.
I need to do some more testing to see if 2.4.22-1 will work properly,
and also whether 599351 disappears on 2.6.36-rc5 with the older libdrm
(or 2.4.22-1). Regardless of the results, neither of these bugs should
be closed, since the kernel should not allow processes to hang on syscalls
regardless of the data passed. Cloning 599351 to libdrm would be fine
with me.
--
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
signature.asc
Description: Digital signature
Bug#599496: linux-2.6: cannot kill process hung on syscall
Package: linux-2.6 Version: 2.6.32-22 Severity: normal Recently, I've had a problem with tasks that apparently get hung on a syscall. For example: Oct 8 02:57:54 lakeview kernel: [84840.484280] INFO: task Xorg:4560 blocked for more than 120 seconds. When this occurs, even sudo kill -9 4560 does not work. The kernel should properly and immediately terminate processes receiving a SIGKILL as root, even (especially) if that process is hung on a syscall. The inability to do this means that the machine becomes unusable when Xorg hangs. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187 signature.asc Description: Digital signature
Bug#599351: linux-2.6: [i915] task Xorg blocked for more than 120 seconds
+0x5f/0x6b Oct 6 19:28:19 lakeview kernel: [71520.520384] [81008a02] ? system_call_fastpath+0x16/0x1b Oct 6 19:28:19 lakeview kernel: [71520.520401] INFO: task compiz:4322 blocked for more than 120 seconds. Oct 6 19:28:19 lakeview kernel: [71520.520406] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Oct 6 19:28:19 lakeview kernel: [71520.520410] compizD 880037afe028 0 4322 4193 0x Oct 6 19:28:19 lakeview kernel: [71520.520418] 8800bb984420 0082 dead00200200 8800bd90b680 Oct 6 19:28:19 lakeview kernel: [71520.520426] 00014940 00014940 88009de37fd8 00014940 Oct 6 19:28:19 lakeview kernel: [71520.520433] 00014940 8800bb9846f8 8800bb984700 8800bb984420 Oct 6 19:28:19 lakeview kernel: [71520.520441] Call Trace: Oct 6 19:28:19 lakeview kernel: [71520.520448] [8130b66e] ? __mutex_lock_common+0x127/0x193 Oct 6 19:28:19 lakeview kernel: [71520.520467] [a066f1af] ? i915_gem_object_set_to_gtt_domain+0x8d/0x9c [i915] Oct 6 19:28:19 lakeview kernel: [71520.520474] [8130b7a6] ? mutex_lock+0x1a/0x33 Oct 6 19:28:19 lakeview kernel: [71520.520492] [a066efd0] ? i915_gem_busy_ioctl+0x4f/0xbf [i915] Oct 6 19:28:19 lakeview kernel: [71520.520509] [a061d220] ? drm_ioctl+0x24e/0x322 [drm] Oct 6 19:28:19 lakeview kernel: [71520.520527] [a066ef81] ? i915_gem_busy_ioctl+0x0/0xbf [i915] Oct 6 19:28:19 lakeview kernel: [71520.520534] [810f91c8] ? do_vfs_ioctl+0x4a2/0x4ef Oct 6 19:28:19 lakeview kernel: [71520.520541] [81064925] ? ktime_get_ts+0x66/0xab Oct 6 19:28:19 lakeview kernel: [71520.520547] [810f9260] ? sys_ioctl+0x4b/0x6f Oct 6 19:28:19 lakeview kernel: [71520.520553] [810fab17] ? sys_poll+0x45/0xaf Oct 6 19:28:19 lakeview kernel: [71520.520559] [81008a02] ? system_call_fastpath+0x16/0x1b Oct 6 19:28:19 lakeview kernel: [71520.520579] INFO: task kworker/u:1:24777 blocked for more than 120 seconds. Oct 6 19:28:19 lakeview kernel: [71520.520583] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Oct 6 19:28:19 lakeview kernel: [71520.520588] kworker/u:1 D 880037afe028 0 24777 2 0x Oct 6 19:28:19 lakeview kernel: [71520.520595] 8800589a2210 0046 8800589a24e8 8800bcdd4af0 Oct 6 19:28:19 lakeview kernel: [71520.520603] 00014940 00014940 8800626cffd8 00014940 Oct 6 19:28:19 lakeview kernel: [71520.520611] 00014940 8800589a24e8 8800589a24f0 8800589a2210 Oct 6 19:28:19 lakeview kernel: [71520.520618] Call Trace: Oct 6 19:28:19 lakeview kernel: [71520.520625] [8130b66e] ? __mutex_lock_common+0x127/0x193 Oct 6 19:28:19 lakeview kernel: [71520.520633] [8103db15] ? finish_task_switch+0x34/0xb4 Oct 6 19:28:19 lakeview kernel: [71520.520639] [8130b7a6] ? mutex_lock+0x1a/0x33 Oct 6 19:28:19 lakeview kernel: [71520.520657] [a066f830] ? i915_gem_retire_work_handler+0x27/0x96 [i915] Oct 6 19:28:19 lakeview kernel: [71520.520676] [a066f809] ? i915_gem_retire_work_handler+0x0/0x96 [i915] Oct 6 19:28:19 lakeview kernel: [71520.520684] [8105850e] ? process_one_work+0x1d1/0x2ee Oct 6 19:28:19 lakeview kernel: [71520.520691] [81059e70] ? worker_thread+0x12d/0x240 Oct 6 19:28:19 lakeview kernel: [71520.520697] [81059d43] ? worker_thread+0x0/0x240 Oct 6 19:28:19 lakeview kernel: [71520.520703] [81059d43] ? worker_thread+0x0/0x240 Oct 6 19:28:19 lakeview kernel: [71520.520710] [8105ccf4] ? kthread+0x7a/0x82 Oct 6 19:28:19 lakeview kernel: [71520.520717] [81009824] ? kernel_thread_helper+0x4/0x10 Oct 6 19:28:19 lakeview kernel: [71520.520724] [8105cc7a] ? kthread+0x0/0x82 Oct 6 19:28:19 lakeview kernel: [71520.520730] [81009820] ? kernel_thread_helper+0x0/0x10 This is the first time I've seen this behavior. If you need more information, just ask. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.36-rc6-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187 signature.asc Description: Digital signature
Bug#599351: linux-2.6: [i915] task Xorg blocked for more than 120 seconds
On Wed, Oct 06, 2010 at 10:38:48PM +0100, Ben Hutchings wrote: Please report this upstream at https://bugs.freedesktop.org under product 'DRI', component 'DRM/Intel'. Let us know the bug number or URL so we can track it. It's my opinion that the maintainers should forward bugs. I have no interest in yet another bugzilla account and with several papers that must be written *now* I simply don't have the time to forward bugs manually. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187 signature.asc Description: Digital signature
Bug#599351: linux-2.6: [i915] task Xorg blocked for more than 120 seconds
On Thu, Oct 07, 2010 at 01:53:27AM +0100, Ben Hutchings wrote: I can't reproduce your bug, so I can't answer any further questions that upstream has for you. If you don't wish to do that, I will simply close it and stop wasting your time. I'm not trying to be rude here. If you decide you want to forward it, I'm happy to be on the CC list so the fd.o maintainers can ask me questions if they need to. But it's not fair to users to force them to acquire huge numbers (at least 20 I can think of) of bugzilla accounts in order to report bugs in Debian. In general, I only take the time to forward bugs upstream when there's a specific patch that I really want to push. I am, unfortunately, unfamiliar with the DRI infrastructure and therefore will not be providing a patch in this case. If you want to close it, fine. There's nothing I can do to stop you. I figured the responsible thing to do was file a bug report instead of just complaining. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187 signature.asc Description: Digital signature
Bug#444182: ata_piix still buggy
reassign 444182 linux-2.6 reassign 463833 linux-2.6 found 444182 2.6.24-2 merge 444182 463833 kthxbye I have the exact same IDE controller (8086:27df) and this is still disabled (for no good reason that I can see). I'd like to be able to use my DVD drive as /dev/scd0, since I use both Debian and upstream kernels, and the latter has a functional ata_piix. Obviously, it's quite annoying to have to constantly switch /etc/fstab from /dev/hda to /dev/scd0. It looks like this was introduced with 2.6.20-3, but no explanation is given in either the changelog or the patch. Could you either remove this patch or please explain why it is necessary? -- brian m. carlson / brian with sandals: Houston, Texas, US +1 713 440 7475 | http://crustytoothpaste.ath.cx/~bmc | My opinion only troff on top of XML: http://crustytoothpaste.ath.cx/~bmc/code/thwack OpenPGP: RSA v4 4096b 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187 signature.asc Description: Digital signature
Bug#429064: Please apply the patch in 429064
Please apply the patch in #429064. It has been tagged as having a patch since July 18, the patch is trivial (and correct, IMHO), and this RC bug is breaking other packages (workbone; #427592). If, for some reason, this patch is unacceptable, please untag the bug and explain what is necessary for an acceptable patch (so that someone, maybe me, can implement one). Thank you. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 713 440 7475 | http://crustytoothpaste.ath.cx/~bmc | My opinion only a typesetting engine: http://crustytoothpaste.ath.cx/~bmc/code/thwack OpenPGP: RSA v4 4096b 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187 signature.asc Description: Digital signature
Bug#433413: linux-2.6: uhci-hcd causes nobody cared on resume or kexec boot
') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/bash -- brian m. carlson / brian with sandals: Houston, Texas, US +1 713 440 7475 | http://crustytoothpaste.ath.cx/~bmc | My opinion only OpenPGP: RSA v4 4096b 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187 signature.asc Description: Digital signature
Bug#433413: irqpoll causes NMI (reason a0)
I tried rebooting using kexec with irqfixup, as well as irqpoll. The output of dmesg in both cases is attached. Please note that using irqpoll causes an NMI (with reason a0), which AIUI is very, very bad. To correct an error I made before: the old IRQ 201 is actually now IRQ 16, not 17. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 713 440 7475 | http://crustytoothpaste.ath.cx/~bmc | My opinion only OpenPGP: RSA v4 4096b 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187 Linux version 2.6.22-1-amd64 (Debian 2.6.22-1) ([EMAIL PROTECTED]) (gcc version 4.1.3 20070629 (prerelease) (Debian 4.1.2-13)) #1 SMP Mon Jul 16 00:30:42 UTC 2007 Command line: root=/dev/mapper/lakeview-root ro libata.atapi_enabled=1 combined_mode=libata irqfixup BIOS-provided physical RAM map: BIOS-e820: 0100 - 0009f000 (usable) BIOS-e820: 0009f000 - 000a (reserved) BIOS-e820: 000d2000 - 000d4000 (reserved) BIOS-e820: 000dc000 - 0010 (reserved) BIOS-e820: 0010 - 3f6d (usable) BIOS-e820: 3f6d - 3f6df000 (ACPI data) BIOS-e820: 3f6df000 - 3f70 (ACPI NVS) BIOS-e820: 3f70 - 4000 (reserved) BIOS-e820: f000 - f400 (reserved) BIOS-e820: fec0 - fec1 (reserved) BIOS-e820: fed0 - fed00400 (reserved) BIOS-e820: fed14000 - fed1a000 (reserved) BIOS-e820: fed1c000 - fed9 (reserved) BIOS-e820: ff80 - 0001 (reserved) Entering add_active_range(0, 1, 159) 0 entries of 3200 used Entering add_active_range(0, 256, 259792) 1 entries of 3200 used end_pfn_map = 1048576 DMI present. ACPI: RSDP 000F67C0, 0024 (r2 LENOVO) ACPI: XSDT 3F6D13CE, 008C (r1 LENOVO TP-7C2170 LTP0) ACPI: FACP 3F6D1500, 00F4 (r3 LENOVO TP-7C2170 LNVO1) ACPI Warning (tbfadt-0434): Optional field Gpe1Block has zero address or length: 102C/0 [20070126] ACPI: DSDT 3F6D185E, D3BB (r1 LENOVO TP-7C2170 MSFT 10E) ACPI: FACS 3F6F4000, 0040 ACPI: SSDT 3F6D16B4, 01AA (r1 LENOVO TP-7C2170 MSFT 10E) ACPI: ECDT 3F6DEC19, 0052 (r1 LENOVO TP-7C2170 LNVO1) ACPI: TCPA 3F6DEC6B, 0032 (r2 LENOVO TP-7C2170 LNVO1) ACPI: APIC 3F6DEC9D, 0068 (r1 LENOVO TP-7C2170 LNVO1) ACPI: MCFG 3F6DED05, 003C (r1 LENOVO TP-7C2170 LNVO1) ACPI: HPET 3F6DED41, 0038 (r1 LENOVO TP-7C2170 LNVO1) ACPI: SLIC 3F6DEE62, 0176 (r1 LENOVO TP-7C2170 LTP0) ACPI: BOOT 3F6DEFD8, 0028 (r1 LENOVO TP-7C2170 LTP1) ACPI: SSDT 3F6F2697, 025F (r1 LENOVO TP-7C2170 INTL 20050513) ACPI: SSDT 3F6F28F6, 00A6 (r1 LENOVO TP-7C2170 INTL 20050513) ACPI: SSDT 3F6F299C, 04F7 (r1 LENOVO TP-7C2170 INTL 20050513) ACPI: SSDT 3F6F2E93, 01D8 (r1 LENOVO TP-7C2170 INTL 20050513) No NUMA configuration found Faking a node at -3f6d Entering add_active_range(0, 1, 159) 0 entries of 3200 used Entering add_active_range(0, 256, 259792) 1 entries of 3200 used Bootmem setup node 0 -3f6d Zone PFN ranges: DMA 1 - 4096 DMA324096 - 1048576 Normal1048576 - 1048576 early_node_map[2] active PFN ranges 0:1 - 159 0: 256 - 259792 On node 0 totalpages: 259694 DMA zone: 55 pages used for memmap DMA zone: 1019 pages reserved DMA zone: 2924 pages, LIFO batch:0 DMA32 zone: 3495 pages used for memmap DMA32 zone: 252201 pages, LIFO batch:31 Normal zone: 0 pages used for memmap ACPI: PM-Timer IO Port: 0x1008 ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Processor #0 (Bootup-CPU) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) Processor #1 ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) ACPI: IOAPIC (id[0x01] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 1, address 0xfec0, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. Setting APIC routing to flat ACPI: HPET id: 0x8086a201 base: 0xfed0 Using ACPI (MADT) for SMP configuration information swsusp: Registered nosave memory region: 0009f000 - 000a swsusp: Registered nosave memory region: 000a - 000d2000 swsusp: Registered nosave memory region: 000d2000 - 000d4000 swsusp: Registered nosave memory region: 000d4000 - 000dc000 swsusp: Registered nosave memory region: 000dc000 - 0010 Allocating PCI resources starting at 5000 (gap: 4000:b000) SMP: Allowing 2 CPUs, 0 hotplug CPUs PERCPU: Allocating 37896 bytes
Bug#402475: bcm43xx makes system unusable on NETDEV timeout
On Tue, Jan 16, 2007 at 10:52:44AM +0100, maximilian attems wrote: On Mon, Jan 15, 2007 at 09:03:57PM +, Brian M. Carlson wrote: The only problem I have with bcm43xx is that when it crashes as specified in the bug report, it makes the system unusable: my USB keyboard ceases to work, although my USB mouse works fine. Magic SysRq doesn't work either (because the keyboard doesn't), and I cannot shut down the system safely if the problem happens while the screensaver is on (which is usually when it happens). please test latest trunk snapshot: http://wiki.debian.org/DebianKernel it has an 2.6.18 with the 2.6.18.2 upstream fix and !netdev. After 14 hours, it seems to work fine. If it should crash, I will respond. Many thanks. -- Brian M. Carlson / Brian with Sandals: Houston, Texas, US Before emailing: http://crustytoothpaste.ath.cx/~bmc/me/contact/email There is no We: http://crustytoothpaste.ath.cx/~bmc/writings/tinw OpenPGP: RSA v3 2048 560553E7: FE82 7C9F EB21 5436 2F96 25BA 927B 0A51 signature.asc Description: Digital signature
Bug#402475: bcm43xx makes system unusable on NETDEV timeout
[Loic, I've CC'd you since the BTS doesn't seem to like me; feel free to pass this on.] The only problem I have with bcm43xx is that when it crashes as specified in the bug report, it makes the system unusable: my USB keyboard ceases to work, although my USB mouse works fine. Magic SysRq doesn't work either (because the keyboard doesn't), and I cannot shut down the system safely if the problem happens while the screensaver is on (which is usually when it happens). I also have to manually bring down the interface when the machine starts, since it seems to still occur if the interface is UP but not RUNNING. This is error-prone and inconvenient. I tried 2.6.18-2, and it didn't work either. I just put the card back in the machine after a while, so I haven't tested it since 2.6.16. The only difference is that the machine now is an amd64, while before it was an i386 (athlon). So while the current state is an improvement over earlier 2.6.18 kernels, it still renders the system useless at inappropriate and inopportune times. Thanks for considering. -- Brian M. Carlson / Brian with Sandals: Houston, Texas, US Before emailing: http://crustytoothpaste.ath.cx/~bmc/me/contact/email There is no We: http://crustytoothpaste.ath.cx/~bmc/writings/tinw OpenPGP: RSA v3 2048 560553E7: FE82 7C9F EB21 5436 2F96 25BA 927B 0A51 signature.asc Description: Digital signature
Bug#353516: Processed: Re: Bug#227386: libc6-dev: ENOTSUP==EOPNOTSUPP, which violates SUSv3
reopen 353516 thanks, control, and have a nice day On Sun, 2006-02-19 at 14:53 +0100, Bastian Blank wrote: bits/errno.h says: Linux has no ENOTSUP error code. and linux themself don't specify this. I understand that. However, SUSv3 requires that it exist[0]: The errno.h header shall provide a declaration for errno and give positive values for the following symbolic constants. Their values shall be unique except as noted below. The fact that it does not exist means that glibc defines it to be the same as EOPNOTSUPP, which is not allowed. The fact that they are the same when they should not be prohibits the use of error numbers in switch statements, which breaks actual code. It is actually easier for Linux to implement this than glibc, because if glibc assigns it a number, Linux may use that number for something else in the future, and then there's a conflict, and we go through this all over again. However, either Linux needs to implement it, or glibc does. Simply pointing fingers at each other or ignoring it won't cut it. Please don't close this bug again until it is decided which one will implement it. [0] http://www.opengroup.org/onlinepubs/95399/basedefs/errno.h.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
