Bug#704073: [multipath-tools-boot] error when update-initramfs
On Friday 29 March 2013 01:04 AM, Ritesh Raj Sarraf wrote: Can you paste the logs when you hit the command? The init script denies stopping the daemon since root in on multipath. But I guess, your installation would have completed. Can you also paste the output of dpkg -l | grep -i multipath-tools Guy, Sorry to bug but I would appreciate if you could provide me some feedback. I am relying on your results before I propose to push this for Wheezy. -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com Necessity is the mother of invention. signature.asc Description: OpenPGP digital signature
Bug#704073: [multipath-tools-boot] error when update-initramfs
Le 29/03/2013 08:20, Ritesh Raj Sarraf a écrit : On Friday 29 March 2013 01:04 AM, Ritesh Raj Sarraf wrote: Can you paste the logs when you hit the command? The init script denies stopping the daemon since root in on multipath. But I guess, your installation would have completed. Can you also paste the output of dpkg -l | grep -i multipath-tools Guy, Sorry to bug but I would appreciate if you could provide me some feedback. I am relying on your results before I propose to push this for Wheezy. Hi, This is what i get : LM05q:~# ls *deb kpartx_0.4.9+git0.4dfdaf2b-7_amd64.deb multipath-tools_0.4.9+git0.4dfdaf2b-7_amd64.deb multipath-tools-boot_0.4.9+git0.4dfdaf2b-7_all.deb LM05q:~# LANG=C dpkg -i *deb (Reading database ... 31699 files and directories currently installed.) Preparing to replace kpartx 0.4.9+git0.4dfdaf2b-7 (using kpartx_0.4.9+git0.4dfdaf2b-7_amd64.deb) ... Unpacking replacement kpartx ... Preparing to replace multipath-tools 0.4.9+git0.4dfdaf2b-6 (using multipath-tools_0.4.9+git0.4dfdaf2b-7_amd64.deb) ... [] Root is on a multipathed device, multipathd can not be stopped:invoke-rc.d: initscript multipath-tools, action stop failed. dpkg: warning: subprocess old pre-removal script returned error exit status 1 dpkg: trying script from the new package instead ... [] Root is on a multipathed device, multipathd can not be stopped:invoke-rc.d: initscript multipath-tools, action stop failed. dpkg: error processing multipath-tools_0.4.9+git0.4dfdaf2b-7_amd64.deb (--install): subprocess new pre-removal script returned error exit status 1 [ ok ] Starting multipath daemon: multipathd. Preparing to replace multipath-tools-boot 0.4.9+git0.4dfdaf2b-7 (using multipath-tools-boot_0.4.9+git0.4dfdaf2b-7_all.deb) ... Unpacking replacement multipath-tools-boot ... Setting up kpartx (0.4.9+git0.4dfdaf2b-7) ... dpkg: dependency problems prevent configuration of multipath-tools-boot: multipath-tools-boot depends on multipath-tools (= 0.4.9+git0.4dfdaf2b-7); however: Version of multipath-tools on system is 0.4.9+git0.4dfdaf2b-6. dpkg: error processing multipath-tools-boot (--install): dependency problems - leaving unconfigured Processing triggers for man-db ... Errors were encountered while processing: multipath-tools_0.4.9+git0.4dfdaf2b-7_amd64.deb multipath-tools-boot LM05q:~# dpkg -l | grep -i multipath-tools ii multipath-tools0.4.9+git0.4dfdaf2b-6 amd64maintain multipath block device access iU multipath-tools-boot 0.4.9+git0.4dfdaf2b-7 all Support booting from multipath devices LM05q:~# Guy -- 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/51554dd8.4030...@teledetection.fr
Bug#704207: linux-image-3.2.0-4-686-pae: soft lockup after suspend to disk
Package: src:linux Version: 3.2.39-2 Severity: important Dear Maintainer, -- Package-specific info: ** Version: Linux version 3.2.0-4-686-pae (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-15) ) #1 SMP Debian 3.2.39-2 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-686-pae root=UUID=b2ab74ed-fc01-4d81-99d1-bcad9228433b ro splash acpi_osi=Linux acpi_backlight=vendor quiet ** Not tainted ** Kernel log: [ 47.162902] cfg80211: (549 KHz - 571 KHz @ 4 KHz), (N/A, 2700 mBm) [ 58.018904] wlan0: no IPv6 routers present [ 209.505682] PM: Marking nosave pages: 0009c000 - 0010 [ 209.505686] PM: Basic memory bitmaps created [ 209.700702] Syncing filesystems ... done. [ 209.701573] Freezing user space processes ... (elapsed 0.01 seconds) done. [ 209.714781] PM: Preallocating image memory... done (allocated 154381 pages) [ 209.847941] PM: Allocated 617524 kbytes in 0.13 seconds (4750.18 MB/s) [ 209.847943] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. [ 209.862545] Suspending console(s) (use no_console_suspend to debug) [ 209.872483] sd 0:0:0:0: [sda] Synchronizing SCSI cache [ 210.401574] PM: freeze of devices complete after 539.922 msecs [ 210.401870] PM: late freeze of devices complete after 0.292 msecs [ 210.402322] ACPI: Preparing to enter system sleep state S4 [ 210.544772] PM: Saving platform NVS memory [ 210.545563] Disabling non-boot CPUs ... [ 210.649049] CPU 1 is now offline [ 210.752838] CPU 2 is now offline [ 210.856658] CPU 3 is now offline [ 210.857081] Extended CMOS year: 2000 [ 210.857156] PM: Creating hibernation image: [ 210.958915] PM: Need to copy 153414 pages [ 210.958918] PM: Normal pages needed: 45812 + 1024, available pages: 181795 [ 210.857188] PM: Restoring platform NVS memory [ 210.857723] Extended CMOS year: 2000 [ 210.857769] Enabling non-boot CPUs ... [ 210.857911] Booting Node 0 Processor 1 APIC 0x4 [ 210.857912] smpboot cpu 1: start_ip = 98000 [ 210.868100] Initializing CPU#1 [ 210.868919] Calibrating delay loop (skipped) already calibrated this CPU [ 210.889391] NMI watchdog enabled, takes one hw-pmu counter. [ 210.890127] CPU1 is up [ 210.890647] Booting Node 0 Processor 2 APIC 0x1 [ 210.890654] smpboot cpu 2: start_ip = 98000 [ 210.900840] Initializing CPU#2 [ 210.901670] Calibrating delay loop (skipped) already calibrated this CPU [ 210.922339] NMI watchdog enabled, takes one hw-pmu counter. [ 210.922818] CPU2 is up [ 210.923189] Booting Node 0 Processor 3 APIC 0x5 [ 210.923193] smpboot cpu 3: start_ip = 98000 [ 210.92] Initializing CPU#3 [ 210.934201] Calibrating delay loop (skipped) already calibrated this CPU [ 210.954775] NMI watchdog enabled, takes one hw-pmu counter. [ 210.955302] CPU3 is up [ 210.958171] ACPI: Waking up from system sleep state S4 [ 211.321285] PM: early restore of devices complete after 0.632 msecs [ 211.361809] i915 :00:02.0: setting latency timer to 64 [ 211.361813] ehci_hcd :00:1a.0: setting latency timer to 64 [ 211.361828] snd_hda_intel :00:1b.0: setting latency timer to 64 [ 211.361837] usb usb1: root hub lost power or was reset [ 211.365785] ehci_hcd :00:1a.0: cache line size of 64 is not supported [ 211.365796] snd_hda_intel :00:1b.0: irq 42 for MSI/MSI-X [ 211.365799] ehci_hcd :00:1d.0: setting latency timer to 64 [ 211.365812] usb usb2: root hub lost power or was reset [ 211.369782] ehci_hcd :00:1d.0: cache line size of 64 is not supported [ 211.369806] pci :00:1e.0: setting latency timer to 64 [ 211.369817] ahci :00:1f.2: setting latency timer to 64 [ 211.382878] sd 0:0:0:0: [sda] Starting disk [ 211.687845] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 211.695835] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 211.698494] ata5.00: configured for UDMA/100 [ 211.715829] usb 1-1: reset high-speed USB device number 2 using ehci_hcd [ 211.739714] ata1.00: configured for UDMA/100 [ 211.959399] usb 2-1: reset high-speed USB device number 2 using ehci_hcd [ 212.126556] wlan0: deauthenticated from 00:24:01:21:02:e6 (Reason: 6) [ 212.150154] cfg80211: Calling CRDA to update world regulatory domain [ 212.378774] usb 2-1.5: reset high-speed USB device number 3 using ehci_hcd [ 212.727334] PM: restore of devices complete after 1367.984 msecs [ 212.747957] Restarting kernel threads ... done. [ 212.748111] snapshot_ioctl: ioctl '4004330c' is deprecated and will be removed soon, update your suspend-to-disk utilities [ 212.748113] Restarting tasks ... done. [ 212.760045] cfg80211: World regulatory domain updated: [ 212.760048] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 212.760052] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 212.760055] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [ 212.760058] cfg80211: (2474000 KHz - 2494000 KHz @
Bug#704223: linux-source-3.8: Please add support for m68k and cross-compiling
Package: linux-source-3.8 Version: 3.8.3-1~experimental.1 Severity: normal Dear Maintainer, the builddeb script does not support m68k nor cross-compiling. The following patch fixes this, the second part comes from this report: https://patchwork.kernel.org/patch/752622/ Please apply, if this is the correct way to add support. thanks, Christian --- scripts/package/builddeb.orig 2013-03-14 19:27:14.0 +0100 +++ scripts/package/builddeb2013-03-29 19:34:05.311940456 +0100 @@ -28,7 +28,7 @@ # Attempt to find the correct Debian architecture local forcearch= debarch= case $UTS_MACHINE in - i386|ia64|alpha) + i386|ia64|alpha|m68k) debarch=$UTS_MACHINE ;; x86_64) debarch=amd64 ;; @@ -254,6 +254,12 @@ rm -f $objtree/debian/hdrsrcfiles $objtree/debian/hdrobjfiles arch=$(dpkg --print-architecture) +if [ -n $KBUILD_DEBARCH ] ; then + arch=$KBUILD_DEBARCH +else + arch=$(dpkg --print-architecture) +fi + cat EOF debian/control Package: $kernel_headers_packagename -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing'), (200, 'experimental'), (100, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-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-source-3.8 depends on: ii binutils 2.22-8 ii bzip2 1.0.6-4 Versions of packages linux-source-3.8 recommends: ii gcc 4:4.7.2-1 ii libc6-dev [libc-dev] 2.13-38 ii make 3.82-1 Versions of packages linux-source-3.8 suggests: ii libncurses5-dev [ncurses-dev] 5.9-10 ii libqt4-dev 4:4.8.2+dfsg-11 ii pkg-config 0.26-1 -- no debconf information -- 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/20130329190642.7941.26442.report...@guido.earth.sol
Bug#704073: [multipath-tools-boot] error when update-initramfs
On Friday 29 March 2013 01:46 PM, Guy Roussin wrote: multipath-tools_0.4.9+git0.4dfdaf2b-7_amd64.deb) ... [] Root is on a multipathed device, multipathd can not be stopped:invoke-rc.d: initscript multipath-tools, action stop failed. dpkg: warning: subprocess old pre-removal script returned error exit status 1 I thought a little more about this. And looks like I have done a big mistake in my assumptions here. In the current config, never will a rooted multipath setup be able to upgrade multipath-tools package, effective living a broken system. What we need to do when called in the stop) target is to: * Detect that the root device is on a multipathed device * If yes, log the information stating that you will not kill the daemon. * exit 0 and stay clean so that no external processes behave havoc. -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com Necessity is the mother of invention. signature.asc Description: OpenPGP digital signature
Bug#704073: [multipath-tools-boot] error when update-initramfs
On Saturday 30 March 2013 01:13 AM, Ritesh Raj Sarraf wrote: On Friday 29 March 2013 01:46 PM, Guy Roussin wrote: multipath-tools_0.4.9+git0.4dfdaf2b-7_amd64.deb) ... [] Root is on a multipathed device, multipathd can not be stopped:invoke-rc.d: initscript multipath-tools, action stop failed. dpkg: warning: subprocess old pre-removal script returned error exit status 1 I thought a little more about this. And looks like I have done a big mistake in my assumptions here. In the current config, never will a rooted multipath setup be able to upgrade multipath-tools package, effective living a broken system. What we need to do when called in the stop) target is to: * Detect that the root device is on a multipathed device * If yes, log the information stating that you will not kill the daemon. * exit 0 and stay clean so that no external processes behave havoc. I have put up a new package (same version) with the fix, at the same location. Could you please test and report back your results? -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com Necessity is the mother of invention. signature.asc Description: OpenPGP digital signature
Processed: tagging 697619
Processing commands for cont...@bugs.debian.org: tags 697619 - moreinfo Bug #697619 [src:linux] USB keyboard no longer works at initramfs passphrase prompt Removed tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 697619: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697619 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.136459038030726.transcr...@bugs.debian.org
Processed: Re: Bug#695968: linux-image-3.2.0-4-amd64: ath.ko starts printing thousands of error messages several minutes after boot
Processing control commands: tag -1 unreproducible Bug #695968 [src:linux] linux-image-3.2.0-4-amd64: ath.ko starts printing thousands of error messages several minutes after boot Bug #695969 [src:linux] linux-image-3.2.0-4-amd64: ath.ko prints thousands of error messages and wireless connection goes down Added tag(s) unreproducible. Added tag(s) unreproducible. -- 695968: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695968 695969: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695969 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.b695968.136459484129947.transcr...@bugs.debian.org
Bug#695968: linux-image-3.2.0-4-amd64: ath.ko starts printing thousands of error messages several minutes after boot
Control: tag -1 unreproducible
On Thu, 2013-03-28 at 19:42 -0400, Joel Diaz wrote:
After looking at this some more, my bisect has left me between these two
commits:
The last good commit:
[db9d8c60266a5010e905829e10cd722519e14777] Merge
git://git.kernel.org/pub/scm/linux/kernel/git/davem/net
The last bad commit:
[45e7715922217493f01c8238d8c9eff5c3fea5a2] Merge tag
'pinctrl-for-v3.7-late' of
git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl
Both of these show up as 3.6.0-rc6 kernels
Bisecting these leaves me at:
[70418e6efcf4f8652cc08e3f2ab8ae35f0948fd9] NFC: pn533: Fix mem leak in
pn533_in_dep_link_up
This leaves me with a 3.6.0-rc1 kernel (according to the root Makefile)
that behaves far differently than the two first commits listed above. I
don't have much confidence in using the bisect since things that worked
before (like X Windows) don't work, and there's all these 'tty_init_dev:
XX callbacks suppressed' messages that weren't there before.
So I pulled each individual patch between the last good and last bad
commit and started applying them individually. It looks like commit
'38c1a01cf10c6e4049b4ffbd4a6af655df2a46e1 wireless: add back sysfs
directory' is the one that fixes things.
But that's fixing an *entirely* different problem.
After applying this patch, the machine will run for days without
incident. Reverting the patch lets the failure appear in under 1 hour.
Now looking at the Wheezy 3.2.x kernel, the code from that patch is
already included, but some of the code is hidden behind
CONFIG_WIRELESS_EXT_SYSFS and Wheezy's config file has '#
CONFIG_WIRELESS_EXT_SYSFS is not set' where my working 3.7.x kernel has
the equivalent setting ('CONFIG_CFG80211') enabled to pull in the code.
Flipping the Wheezy config to 'y' and rebuilding has allowed the machine
to run the Wheezy 3.2.39 kernel for a full day without incident.
This option does not affect the behaviour of the driver and therefore
cannot have fixed the bug.
Until you find a *reliable* way to reproduce the bug, bisection cannot
find the fix. I'm sorry I can't be more helpful.
Ben.
--
Ben Hutchings
I'm not a reverse psychological virus. Please don't copy me into your sig.
signature.asc
Description: This is a digitally signed message part
Processed: severity of 704223 is wishlist
Processing commands for cont...@bugs.debian.org: severity 704223 wishlist Bug #704223 [linux-source-3.8] linux-source-3.8: Please add support for m68k and cross-compiling Severity set to 'wishlist' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 704223: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704223 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.13645959375111.transcr...@bugs.debian.org
Bug#697619: USB keyboard no longer works at initramfs passphrase prompt
Control: retitle -1 Many HID drivers not included in initramfs Control: reassign -1 initramfs-tools 0.109 Control: severity -1 serious On Wed, 2013-03-27 at 14:02 -0700, Josh Triplett wrote: found 697619 3.8.2-1~experimental.1 thanks On Sun, Jan 20, 2013 at 01:12:52AM +, Ben Hutchings wrote: On Sat, 2013-01-19 at 16:16 -0800, Josh Triplett wrote: On Sat, Jan 19, 2013 at 10:37:43PM +, Ben Hutchings wrote: On Mon, 2013-01-07 at 09:23 -0800, Josh Triplett wrote: Package: src:linux Version: 3.7.1-1~experimental.1 Severity: grave The 3.7 kernel in experimental no longer accepts input from a USB keyboard at the initramfs passphrase prompt for an encrypted root. This works fine with the 3.6 kernel currently in latest unstable, which I booted to make this report. [...] [1.555303] usb 1-1.3: new low-speed USB device number 4 using xhci_hcd [1.585030] usb 1-1.3: New USB device found, idVendor=17ef, idProduct=6009 [1.585129] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [1.585202] usb 1-1.3: Product: ThinkPad USB Keyboard with TrackPoint [1.585263] usb 1-1.3: Manufacturer: Lite-On Technology Corp. Keyboard is detected. [1.585475] usb 1-1.3: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes [1.585553] usb 1-1.3: ep 0x82 - rounding interval to 64 microframes, ep desc says 80 microframes This looks suspicious. This doesn't appear anymore. [...] [ 67.355998] input: Lite-On Technology Corp. ThinkPad USB Keyboard with TrackPoint as /devices/pci:00/:00:1c.6/:0e:00.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input4 [ 67.356067] lenovo_tpkbd 0003:17EF:6009.0001: input,hidraw0: USB HID v1.10 Keyboard [Lite-On Technology Corp. ThinkPad USB Keyboard with TrackPoint] on usb-:0e:00.0-1.3/input0 [ 67.356223] Bluetooth: SCO socket layer initialized [ 67.359576] input: Lite-On Technology Corp. ThinkPad USB Keyboard with TrackPoint as /devices/pci:00/:00:1c.6/:0e:00.0/usb1/1-1/1-1.3/1-1.3:1.1/input/input5 [ 67.360128] lenovo_tpkbd 0003:17EF:6009.0002: input,hiddev0,hidraw1: USB HID v1.10 Mouse [Lite-On Technology Corp. ThinkPad USB Keyboard with TrackPoint] on usb-:0e:00.0-1.3/input1 [...] Could you test with the keyboard plugged into a non-USB 3 port, assuming there is one? Usually the USB 3 ports are distinguished by some blue colouration. Fairly certain that the USB port on the dock that I plugged it into did not do USB3, but I tried it on a port that I *know* doesn't do USB3 and it still didn't work. Got it: this device is now handled by the new hid-lenovo-tpkbd module, which isn't included in the initramfs. This isn't really a new problem, though - it's just affecting yet another device that got a special driver not on the list. The hid driver has an option to use the generic code for all HID devices, so you should be able to work around this by putting hid.ignore_special_drivers=1 on the kernel command line. But initramfs-tools should not set this option because there's no way to switch over to the specialised module once the real root is mounted. I think that instead of including specific hid modules, initramfs-tools must include everything under drivers/hid, but exclude those that are known not to be keyboard drivers. This is basically the same approach that's used for network drivers now. Ben. -- Ben Hutchings I'm not a reverse psychological virus. Please don't copy me into your sig. signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#697619: USB keyboard no longer works at initramfs passphrase prompt
Processing control commands: retitle -1 Many HID drivers not included in initramfs Bug #697619 [src:linux] USB keyboard no longer works at initramfs passphrase prompt Changed Bug title to 'Many HID drivers not included in initramfs' from 'USB keyboard no longer works at initramfs passphrase prompt' reassign -1 initramfs-tools 0.109 Bug #697619 [src:linux] Many HID drivers not included in initramfs Bug reassigned from package 'src:linux' to 'initramfs-tools'. No longer marked as found in versions linux/3.7.1-1~experimental.1. Ignoring request to alter fixed versions of bug #697619 to the same values previously set Bug #697619 [initramfs-tools] Many HID drivers not included in initramfs Marked as found in versions initramfs-tools/0.109. severity -1 serious Bug #697619 [initramfs-tools] Many HID drivers not included in initramfs Severity set to 'serious' from 'important' -- 697619: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697619 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.b697619.136459838822763.transcr...@bugs.debian.org
Bug#697619: USB keyboard no longer works at initramfs passphrase prompt
On Fri, Mar 29, 2013 at 11:06:11PM +, Ben Hutchings wrote: Control: retitle -1 Many HID drivers not included in initramfs Control: reassign -1 initramfs-tools 0.109 Control: severity -1 serious On Wed, 2013-03-27 at 14:02 -0700, Josh Triplett wrote: found 697619 3.8.2-1~experimental.1 thanks On Sun, Jan 20, 2013 at 01:12:52AM +, Ben Hutchings wrote: On Sat, 2013-01-19 at 16:16 -0800, Josh Triplett wrote: On Sat, Jan 19, 2013 at 10:37:43PM +, Ben Hutchings wrote: On Mon, 2013-01-07 at 09:23 -0800, Josh Triplett wrote: Package: src:linux Version: 3.7.1-1~experimental.1 Severity: grave The 3.7 kernel in experimental no longer accepts input from a USB keyboard at the initramfs passphrase prompt for an encrypted root. This works fine with the 3.6 kernel currently in latest unstable, which I booted to make this report. [...] [1.555303] usb 1-1.3: new low-speed USB device number 4 using xhci_hcd [1.585030] usb 1-1.3: New USB device found, idVendor=17ef, idProduct=6009 [1.585129] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [1.585202] usb 1-1.3: Product: ThinkPad USB Keyboard with TrackPoint [1.585263] usb 1-1.3: Manufacturer: Lite-On Technology Corp. Keyboard is detected. [1.585475] usb 1-1.3: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes [1.585553] usb 1-1.3: ep 0x82 - rounding interval to 64 microframes, ep desc says 80 microframes This looks suspicious. This doesn't appear anymore. [...] [ 67.355998] input: Lite-On Technology Corp. ThinkPad USB Keyboard with TrackPoint as /devices/pci:00/:00:1c.6/:0e:00.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input4 [ 67.356067] lenovo_tpkbd 0003:17EF:6009.0001: input,hidraw0: USB HID v1.10 Keyboard [Lite-On Technology Corp. ThinkPad USB Keyboard with TrackPoint] on usb-:0e:00.0-1.3/input0 [ 67.356223] Bluetooth: SCO socket layer initialized [ 67.359576] input: Lite-On Technology Corp. ThinkPad USB Keyboard with TrackPoint as /devices/pci:00/:00:1c.6/:0e:00.0/usb1/1-1/1-1.3/1-1.3:1.1/input/input5 [ 67.360128] lenovo_tpkbd 0003:17EF:6009.0002: input,hiddev0,hidraw1: USB HID v1.10 Mouse [Lite-On Technology Corp. ThinkPad USB Keyboard with TrackPoint] on usb-:0e:00.0-1.3/input1 [...] Could you test with the keyboard plugged into a non-USB 3 port, assuming there is one? Usually the USB 3 ports are distinguished by some blue colouration. Fairly certain that the USB port on the dock that I plugged it into did not do USB3, but I tried it on a port that I *know* doesn't do USB3 and it still didn't work. Got it: this device is now handled by the new hid-lenovo-tpkbd module, which isn't included in the initramfs. This isn't really a new problem, though - it's just affecting yet another device that got a special driver not on the list. The hid driver has an option to use the generic code for all HID devices, so you should be able to work around this by putting hid.ignore_special_drivers=1 on the kernel command line. But initramfs-tools should not set this option because there's no way to switch over to the specialised module once the real root is mounted. I think that instead of including specific hid modules, initramfs-tools must include everything under drivers/hid, but exclude those that are known not to be keyboard drivers. This is basically the same approach that's used for network drivers now. Makes sense, though it seems unfortunate that the generic HID driver can't hand off to a more specialized one after boot, given that the generic driver has all the functionality needed to enter a passphrase. - Josh Triplett -- 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/20130329235506.GA7326@jtriplet-mobl1
[PATCH 1/2] hook-functions: Include more HID drivers in base
Currently we're not including all the HID drivers that support keyboards. Further, there are occasional regressions when a keyboard that was previously handled by the generic code gets a specialised drivers that's not on our list. Instead of trying to list all the HID driver modules, include the whole drivers/hid tree and exclude specific modules that we know don't support keyboards. Signed-off-by: Ben Hutchings b...@decadent.org.uk Closes: #697619 --- For linux-image-3.2.0-4-amd64, this includes: hid hid-apple hid-belkin hid-cherry hid-chicony hid-ezkey hid-hyperv hid-keytouch hid-logitech hid-logitech-dj hid-microsoft hid-monterey hid-ortek hid-primax hid-prodikeys hid-roccat hid-roccat-arvo hid-roccat-common hid-samsung hid-sjoy hid-sunplus hid-topseed usbhid For linux-image-3.8-trunk-amd64, this includes: hid hid-apple hid-aureal hid-belkin hid-cherry hid-chicony hid-ezkey hid-generic hid-holtek-kbd hid-hyperv hid-keytouch hid-lenovo-tpkbd hid-logitech hid-logitech-dj hid-microsoft hid-monterey hid-ortek hid-primax hid-prodikeys hid-roccat hid-roccat-arvo hid-roccat-common hid-roccat-isku hid-roccat-lua hid-roccat-savu hid-samsung hid-sjoy hid-sunplus hid-topseed usbhid I believe this change is needed for wheezy. Ben. hook-functions | 20 +--- 1 file changed, 17 insertions(+), 3 deletions(-) diff --git a/hook-functions b/hook-functions index 354d24f..f090256 100644 --- a/hook-functions +++ b/hook-functions @@ -424,13 +424,27 @@ auto_add_modules() base) modules=$modules ehci-pci ehci-hcd ohci-hcd uhci-hcd usbhid modules=$modules xhci xhci-hcd - modules=$modules hid-apple hid-cherry hid-generic - modules=$modules hid-logitech hid-logitech-dj - modules=$modules hid-microsoft hid-sunplus modules=$modules btrfs ext2 ext3 ext4 ext4dev modules=$modules isofs jfs reiserfs udf xfs modules=$modules nfs nfsv2 nfsv3 nfsv4 modules=$modules af_packet atkbd i8042 virtio_pci + + # Include all HID drivers unless we're sure they + # don't support keyboards. hid-*ff covers various + # game controllers with force feedback. + copy_modules_dir kernel/drivers/hid \ + 'hid-*ff.ko' hid-a4tech.ko hid-cypress.ko \ + hid-dr.ko hid-elecom.ko hid-gyration.ko \ + hid-icade.ko hid-kensington.ko hid-kye.ko \ + hid-lcpower.ko hid-magicmouse.ko \ + hid-multitouch.ko hid-ntrig.ko \ + hid-petalynx.ko hid-picolcd.ko hid-pl.ko \ + hid-ps3remote.ko hid-quanta.ko \ + 'hid-roccat-ko*.ko' hid-roccat-pyra.ko \ + hid-saitek.ko hid-sensor-hub.ko hid-sony.ko \ + hid-speedlink.ko hid-tivo.ko hid-twinhan.ko \ + hid-uclogic.ko hid-wacom.ko hid-waltop.ko \ + hid-wiimote.ko hid-zydacron.ko ;; net) copy_modules_dir kernel/drivers/net \ signature.asc Description: This is a digitally signed message part
[PATCH 2/2] hook-functions: Exclude more unnecessary net drivers
Exclude drivers for: - software devices: dummy, ifb, tun, veth. - layered devices: macvlan, macvtap, team - physical devices unlikely to be useful at boot: hippi/*, sb1000, xen-netback Signed-off-by: Ben Hutchings b...@decadent.org.uk --- Some of the existing exclusions should perhaps be reconsidered - USB Ethernet is depressingly common - but I think these additions are safe. Ben. hook-functions |7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/hook-functions b/hook-functions index f090256..817d06c 100644 --- a/hook-functions +++ b/hook-functions @@ -448,8 +448,11 @@ auto_add_modules() ;; net) copy_modules_dir kernel/drivers/net \ - appletalk arcnet bonding can hamradio irda \ - pcmcia tokenring usb wan wimax wireless + appletalk arcnet bonding can dummy.ko \ + hamradio hippi ifb.ko irda macvlan.ko \ + macvtap.ko pcmcia sb1000.ko team tokenring \ + tun.ko usb veth.ko wan wimax wireless \ + xen-netback.ko ;; ide) copy_modules_dir kernel/drivers/ide signature.asc Description: This is a digitally signed message part
