Bug#658759: disable l2 cache on kirkwood devices (workaround #658904)
Hi Ian, On Aug 30, 2012, Ian Campbell wrote: I've just tried injecting the following onto the head of the zImage (in a similar manner to flash-kernel's set_machine_id function): [...] This works around the issue on my dreamplug (this is effectively the same code sequence as what the u-boot fix does). I can see two ways of distributing this fix. Either a kernel patch gated on CONFIG_ARCH_KIRKWOOD to some early bit of code or use devio in flash-kernel + the installer build. Sorry I missed this before. That sounds like an excellent idea for a kernel patch. A kind user on the linux-arm-kernel@ list[1] recently mentioned he'd be willing to test patches, if you need a guinea pig, and I assume once a patch is written and tested it should be possible to get useful feedback from the list. Thanks, Jonathan [1] http://thread.gmane.org/gmane.linux.ports.arm.kernel/185621/focus=185879 -- 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/20120911060940.GA2124@mannheim-rule.local
Bug#687254: linux-image-3.2.0-3-amd64: Using i915, after login from gdm, screen goes black, and only a reboot helps.
Package: src:linux Version: 3.2.23-1 Severity: critical Justification: breaks the whole system Dear Maintainer, My computer with an intel i7 cpu most times works properly, but sometimes it gets stuck in a black screen after loggin in from gdm. The relevant lines, from kern.log (I think) are: Sep 11 10:56:39 kielo kernel: [6.885218] fbcon: inteldrmfb (fb0) is primary device Sep 11 10:56:39 kielo kernel: [8.326401] Console: switching to colour frame buffer device 240x67 Sep 11 10:56:39 kielo kernel: [8.335424] fb0: inteldrmfb frame buffer device Sep 11 10:56:39 kielo kernel: [8.335427] drm: registered panic notifier Sep 11 10:56:39 kielo kernel: [8.335446] No ACPI video bus found Something along these lines is scattered across the internet, and I manage to consistently boot with either of the solutions: * Give acpi=off as kernel parameter * set i915 options modeset=0 in modprobe.d Neither of these workaround is satisfactory, because then I don't have the full resolution nor proper gnome 3. I also tried with kernel 2.6.32-5-amd64, which didn't go into a black screen, but didn't give proper video support either. Daniel Landau -- Package-specific info: ** Version: Linux version 3.2.0-3-amd64 (Debian 3.2.23-1) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-8) ) #1 SMP Mon Jul 23 02:45:17 UTC 2012 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-3-amd64 root=UUID=217d0928-12cc-46ae-859b-431bacf49356 ro quiet ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [4.732068] ACPI: Power Button [PWRF] [4.732954] ACPI: Requesting acpi_cpufreq [4.742355] i801_smbus :00:1f.3: PCI INT C - GSI 18 (level, low) - IRQ 18 [4.743816] input: PC Speaker as /devices/platform/pcspkr/input/input3 [4.753845] [drm] Initialized drm 1.1.0 20060810 [4.754155] iTCO_vendor_support: vendor-support=0 [4.755435] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07 [4.755508] iTCO_wdt: Found a Cougar Point TCO device (Version=2, TCOBASE=0x0460) [4.755572] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [4.769954] cfg80211: Calling CRDA to update world regulatory domain [4.770170] i915 :00:02.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [4.770173] i915 :00:02.0: setting latency timer to 64 [4.775632] alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni) [4.781808] rtl8192ce :02:00.0: PCI INT A - GSI 18 (level, low) - IRQ 18 [4.781816] rtl8192ce :02:00.0: setting latency timer to 64 [4.811372] cfg80211: World regulatory domain updated: [4.811374] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [4.811376] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [4.811377] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [4.811379] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [4.811380] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) [4.811382] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [4.812104] mtrr: type mismatch for c000,1000 old: write-back new: write-combining [4.812106] [drm] MTRR allocation failed. Graphics performance may suffer. [4.812506] i915 :00:02.0: irq 44 for MSI/MSI-X [4.812510] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [4.812511] [drm] Driver supports precise vblank timestamp query. [4.812548] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [4.82] ieee80211 phy0: Selected rate control algorithm 'rtl_rc' [4.823627] rtlwifi: wireless switch is on [4.867246] input: A4Tech PS/2+USB Mouse as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/input/input4 [4.867369] a4tech 0003:09DA:000A.0001: input,hidraw2: USB HID v1.10 Mouse [A4Tech PS/2+USB Mouse] on usb-:00:1a.0-1.1/input0 [4.870987] Linux media interface: v0.10 [4.889318] Linux video capture interface: v2.00 [4.900300] usbcore: registered new interface driver snd-usb-audio [4.900305] uvcvideo: Found UVC 1.00 device USB Video Device (058f:3832) [4.903598] input: USB Video Device as /devices/pci:00/:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0/input/input5 [4.903793] usbcore: registered new interface driver uvcvideo [4.903796] USB Video Class driver (1.1.1) [6.885218] fbcon: inteldrmfb (fb0) is primary device [8.326401] Console: switching to colour frame buffer device 240x67 [8.335424] fb0: inteldrmfb frame buffer device [8.335427] drm: registered panic notifier [8.335446] No ACPI video bus found [8.335517] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [8.335598] snd_hda_intel :00:1b.0: PCI INT A - GSI 22 (level, low) - IRQ 22 [8.335667] snd_hda_intel :00:1b.0: irq 45 for MSI/MSI-X [8.335697]
Bug#658759: disable l2 cache on kirkwood devices (workaround #658904)
On Mon, 2012-09-10 at 23:09 -0700, Jonathan Nieder wrote: Hi Ian, On Aug 30, 2012, Ian Campbell wrote: I've just tried injecting the following onto the head of the zImage (in a similar manner to flash-kernel's set_machine_id function): [...] This works around the issue on my dreamplug (this is effectively the same code sequence as what the u-boot fix does). I can see two ways of distributing this fix. Either a kernel patch gated on CONFIG_ARCH_KIRKWOOD to some early bit of code or use devio in flash-kernel + the installer build. Sorry I missed this before. That sounds like an excellent idea for a kernel patch. A kind user on the linux-arm-kernel@ list[1] recently mentioned he'd be willing to test patches, if you need a guinea pig, and I assume once a patch is written and tested it should be possible to get useful feedback from the list. My main concern with doing this on the kernel side is that it will eventually fall foul of the attempts to reduce everything to a single kernel image, since the code will necessarily be quite kirkwood specific and run very early on. Martin's testing of di on ARM[0] suggests this issue isn't all that widespread, which lead me to conclude that the risk of making a change like this (either in the kernel or the installer/flash-kernel) for Wheezy was not worth the chance of breaking some other kirkwood device. Ian. [0] https://lists.debian.org/debian-boot/2012/09/msg00052.html -- Ian Campbell Current Noise: Crowbar - To Build A Mountain Sex is like air. It's only a big deal if you can't get any. -- 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/1347355043.5305.137.ca...@zakaz.uk.xensource.com
Bug#665881: [wheezy] module ath5k is blocking wlan-card
Am Montag, 10. September 2012 schrieb Jonathan Nieder: Hans-J. Ullrich wrote: Hi Jonathan, 1. The described behaviour appears EVERY TIME, when I started Windows 7 on this system, and rebooted to linux again. That's very good to hear. Can you reproduce this with 3.5.y from experimental? Well, I installed now 3.5-trunk-amd64 from experimental. First tests are showing good results. I still could not reproduce the behaviour with this kernel. But it is too early, to make a final conclusion. So I will test it now for a few days and will then send a report. If so, please send a description of the symptoms to linux-wirel...@vger.kernel.org, cc-ing ath5k-de...@lists.ath5k.org, Nick Kossifidis mickfl...@gmail.com, and either me or this bug log so we can track it. Be sure to mention - steps to reproduce, expected result, actual result, and how the difference indicates a bug (should be simple enough) - which kernel versions you have tested and what happened with each - full dmesg output from booting and trying to use wireless in the affected state, as an attachment - any other weird symptoms or observations Yes, if any strange behaviours occure, I will send them to the list. My current system is debian-testing, which I am running on several computers (mostly daily updated). These are 2 x amd64-cpus (a notebook Acer Aspire 7520G and a Desktop PC) and my Asus EEEPC 1005 HGO (i386). Hopefully the symptoms will ring a bell for someone, who can provide instructions or a patch to track down the cause further. Yeah, that might be great! Hope that helps, Jonathan Thanky for the help. Best regards Hans -- 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/201209111252.15179.hans.ullr...@loop.de
Bug#658759: disable l2 cache on kirkwood devices (workaround #658904)
Ian Campbell wrote: My main concern with doing this on the kernel side is that it will eventually fall foul of the attempts to reduce everything to a single kernel image, since the code will necessarily be quite kirkwood specific and run very early on. Is it possible to do something reasonable if the extra features register is read first? (Please forgive my ignorance.) Martin's testing of di on ARM[0] suggests this issue isn't all that widespread, which lead me to conclude that the risk of making a change like this (either in the kernel or the installer/flash-kernel) for Wheezy was not worth the chance of breaking some other kirkwood device. I think that's ok --- the change would be valuable upstream anyway, and it can filter into mainline and wheezy whenever it has had an appropriate amount of testing. Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120911105734.GA2356@mannheim-rule.local
Bug#665881: [wheezy] module ath5k is blocking wlan-card
Hans-J. Ullrich wrote: Well, I installed now 3.5-trunk-amd64 from experimental. First tests are showing good results. Drat. Am I correct in guessing that the prebuilt 3.3.6 package from http://snapshot.debian.org/package/linux-2.6/ reproduces it, while 3.4.1 does not? Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2012090131.GB2356@mannheim-rule.local
Bug#665881: [wheezy] module ath5k is blocking wlan-card
Am Dienstag, 11. September 2012 schrieb Jonathan Nieder: Hans-J. Ullrich wrote: Well, I installed now 3.5-trunk-amd64 from experimental. First tests are showing good results. Drat. Am I correct in guessing that the prebuilt 3.3.6 package from http://snapshot.debian.org/package/linux-2.6/ reproduces it, while 3.4.1 does not? Huh, I did not test those versions. I just tested 3.2-xx (stock debian testing) and now at your advice version 3.5. (experimental) If 3.5 will work, I can test 3.3 and 3.4, too, if needed. Jonathan Hans -- 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/201209111309.22992.hans.ullr...@loop.de
Bug#687254: linux-image-3.2.0-3-amd64: Using i915, after login from gdm, screen goes black, and only a reboot helps.
Control: severity -1 important On Tue, Sep 11, 2012 at 11:12:35AM +0300, Daniel Landau wrote: ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Loaded modules: vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) We don't support systems in this state. Please remove the virtual box modules and try again. The vbox modules does nasty things to the system. If it happens again, please provide the following: - Complete kernel log (/var/log/kern.log have a copy) from the start of the kernel until the problem. - Complete Xorg log (/var/log/gdm3 I think in this case). Bastian -- Hailing frequencies open, Captain. -- 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/2012093518.ga18...@wavehammer.waldi.eu.org
Processed: Re: Bug#687254: linux-image-3.2.0-3-amd64: Using i915, after login from gdm, screen goes black, and only a reboot helps.
Processing control commands: severity -1 important Bug #687254 [src:linux] linux-image-3.2.0-3-amd64: Using i915, after login from gdm, screen goes black, and only a reboot helps. Severity set to 'important' from 'critical' -- 687254: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687254 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.b687254.13473633241241.transcr...@bugs.debian.org
Processed (with 1 errors): d-i, os-prober need fuse module to detect other OS's
Processing commands for cont...@bugs.debian.org: clone 686927 -1 Bug #686927 [installation-reports] installation does not detect existing Lubuntu Bug 686927 cloned as bug 687286 retitle 686927 unable to install grub into any partition Bug #686927 [installation-reports] installation does not detect existing Lubuntu Changed Bug title to 'unable to install grub into any partition' from 'installation does not detect existing Lubuntu' tags 686927 moreinfo Bug #686927 [installation-reports] unable to install grub into any partition Added tag(s) moreinfo. retitle 684265 debian-installer: os-prober needs fuse module to detect other OS's Bug #684265 [installation-reports] installation-reports: yaboot.conf missing existing root partitions -- sources.list still has deb cdrom from installation Changed Bug title to 'debian-installer: os-prober needs fuse module to detect other OS's' from 'installation-reports: yaboot.conf missing existing root partitions -- sources.list still has deb cdrom from installation' forcemerge 684265 -1 Bug #684265 [installation-reports] debian-installer: os-prober needs fuse module to detect other OS's Bug #687286 [installation-reports] installation does not detect existing Lubuntu Severity set to 'important' from 'normal' Merged 684265 687286 reassign 684265 linux Bug #684265 [installation-reports] debian-installer: os-prober needs fuse module to detect other OS's Bug #687286 [installation-reports] installation does not detect existing Lubuntu Bug reassigned from package 'installation-reports' to 'linux'. Bug reassigned from package 'installation-reports' to 'linux'. Ignoring request to alter found versions of bug #684265 to the same values previously set Ignoring request to alter found versions of bug #687286 to the same values previously set Ignoring request to alter fixed versions of bug #684265 to the same values previously set Ignoring request to alter fixed versions of bug #687286 to the same values previously set forcemerge 684265 686631 Bug #684265 [linux] debian-installer: os-prober needs fuse module to detect other OS's Bug #687286 [linux] installation does not detect existing Lubuntu Bug #686631 [linux] Please add the fuse module to d-i kernel packages Severity set to 'important' from 'normal' Bug #687286 [linux] installation does not detect existing Lubuntu Merged 684265 686631 687286 affects 684265 debian-installer installation-reports Bug #684265 [linux] debian-installer: os-prober needs fuse module to detect other OS's Bug #686631 [linux] Please add the fuse module to d-i kernel packages Bug #687286 [linux] installation does not detect existing Lubuntu Added indication that 684265 affects debian-installer and installation-reports Added indication that 686631 affects debian-installer and installation-reports Added indication that 687286 affects debian-installer and installation-reports tags d-i thanks Stopping processing here. Please contact me if you need assistance. -- 684265: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684265 686631: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686631 686927: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686927 687286: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687286 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.134736926814887.transcr...@bugs.debian.org
Debian and Netapp NFSv4 locks/owner exhaustion
Hi all,
We're currently having a highly intermittent (and seemingly random)
problem with our 20 Debian clients running courier POP3 and IMAPd
connecting to a Netapp filer using NFSv4, whereby locks/owner objects
are being maxed out on the filer, causing the clients to start to have
very high load.
Netapp think that this is a bug with the implementation of NFS in our
Debian kernel - please see part of an email they sent us below:
---
Thanks for providing all the data
from the sync core and the lock status data provided indicated you have
a linux client bug. equivalent to redhat bugzilla 620502/621304 .
https://bugzilla.redhat.com/show_bug.cgi?id=620502 2.6.18 kernel
https://bugzilla.redhat.com/show_bug.cgi?id=621304 2.6.32 kernel.
Basically there is a know linux kernel bug where it request a new owner
id everytime a new lock request is submitted. There are linux upstream
fixed that prevents new owner lock id and reuse existing ones.
Analyses from the sync core
As previously mentioned NFSv4 has 4 items StateID/ClientID and OwnerID
limits.
StateID
kgdb-amd64-7.4-54) p v4lock_states_free_count
$8 = {16789, 32768}
There are free states available.
ClientID
(kgdb-amd64-7.4-54) p v4lock_clients_free[0]
$10 = {{cqh_first = 0xff04cd2cda00, cqh_last = 0xff04cd4caf00}
there are free clients
OwnerID
(kgdb-amd64-7.4-54) p v4lock_owners_free[0]
$9 = {{cqh_first = 0xa25f2640, cqh_last = 0xa25f2640}
there are no free owners
(kgdb-amd64-7.4-54) print_owner_htab_count
total:10240
total owner objects in use:10240
(kgdb-amd64-7.4-54) p v4owner_table_size/2
$527 = 10240
per node max owners value reached
Lets correlate this to the lock status output provided.
(fed15:samuell:/x/eng/cs-data/2003058003/20120821_sync_core/mailstorage04
grep Free owners mailstorage04-lock-v*
mailstorage04-lock-v-201208210605:Free owners 3; In-Use Owners 10237 *
mailstorage04-lock-v-201208210610:Free owners -3; In-Use Owners 10243 *
mailstorage04-lock-v-201208210615:Free owners -2; In-Use Owners 10242
mailstorage04-lock-v-201208210620:Free owners 0; In-Use Owners 10240
mailstorage04-lock-v-201208210625:Free owners 3; In-Use Owners 10237
mailstorage04-lock-v-201208210630:Free owners -7; In-Use Owners 10247
mailstorage04-lock-v-201208210635:Free owners 1; In-Use Owners 10239
mailstorage04-lock-v-201208210640:Free owners -3; In-Use Owners 10243
mailstorage04-lock-v-201208210645:Free owners 4; In-Use Owners 10236
mailstorage04-lock-v-201208210650:Free owners -1; In-Use Owners 10241
mailstorage04-lock-v-201208210655:Free owners 4; In-Use Owners 10236
mailstorage04-lock-v-201208210700:Free owners -1; In-Use Owners 10241
mailstorage04-lock-v-201208210705:Free owners -4; In-Use Owners 10244
As you can see the filer is reporting MAX of 10240 and in some event it
was over subscribed.
Corrective action is to make sure you use a kernel release from your
distro that has upstream patch
The diff can be found here
https://bugzilla.redhat.com/attachment.cgi?id=436801action=diff
Redhat has provided an errata fix int he kernel patch
http://rhn.redhat.com/errata/RHSA-2011-0542.html;
---
Some info on our platform:
Clients:
20 of, running Squeeze 6.0.1, but with backported kernel
3.2.0-0.bpo.1-amd64.
nfs-common 1:1.2.2-4
The application is courier IMAP and POP3.
Server:
Netapp FAS3170 running 8.0.1P1 7-Mode
The main question I have is whether the bugs Netapp mentioned in the
Redhat kernel have been fixed in the backported Debian kernel we are
running, and if so, what version the fixes have been introduced in (and
if not, what version the fixes *will* be introduced in)?
Otherwise, if anyone has any other suggestions as to what else the
problem could be, I'd be happy to hear them :)
Thanks,
Richard
--
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/504f38b5.3050...@plus.net
Bug#684265: linux: d-i, os-prober need fuse module to detect other OS's
tags 684265 patch thanks Debian installer os-prober needs fuse module to look into various partitions for already installed operating systems. Patch is attached. Milan Index: debian/installer/package-list === --- debian/installer/package-list (revision 19377) +++ debian/installer/package-list (working copy) @@ -332,6 +332,12 @@ This package contains core modules for the kernel, that will almost always be needed. +Package: fuse-modules +Depends: kernel-image +Priority: standard +Description: FUSE support modules + This package contains filesystem in userspace support modules. + Package: acpi-modules Depends: kernel-image Priority: extra Index: debian/installer/modules/fuse-modules === --- debian/installer/modules/fuse-modules (revision 0) +++ debian/installer/modules/fuse-modules (revision 0) @@ -0,0 +1 @@ +fuse smime.p7s Description: S/MIME Cryptographic Signature
Processed: linux: d-i, os-prober need fuse module to detect other OS's
Processing commands for cont...@bugs.debian.org: tags 684265 patch Bug #684265 [linux] debian-installer: os-prober needs fuse module to detect other OS's Bug #686631 [linux] Please add the fuse module to d-i kernel packages Bug #687286 [linux] installation does not detect existing Lubuntu Added tag(s) patch. Added tag(s) patch. Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 684265: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684265 686631: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686631 687286: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687286 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.134736980619575.transcr...@bugs.debian.org
Bug#658759: disable l2 cache on kirkwood devices (workaround #658904)
On Tue, 2012-09-11 at 03:57 -0700, Jonathan Nieder wrote: Ian Campbell wrote: My main concern with doing this on the kernel side is that it will eventually fall foul of the attempts to reduce everything to a single kernel image, since the code will necessarily be quite kirkwood specific and run very early on. Is it possible to do something reasonable if the extra features register is read first? (Please forgive my ignorance.) I'm afraid I don't know either. Is this extra features register ARM architectural or specific to the Kirkwood devices? I think the cache control registers are implementation defined, so this code would need to know it is running on a specific set of processors before it would be safe to run it. Martin's testing of di on ARM[0] suggests this issue isn't all that widespread, which lead me to conclude that the risk of making a change like this (either in the kernel or the installer/flash-kernel) for Wheezy was not worth the chance of breaking some other kirkwood device. I think that's ok --- the change would be valuable upstream anyway, and it can filter into mainline and wheezy whenever it has had an appropriate amount of testing. Ian. -- Ian Campbell Current Noise: Faal - My Body Glows Red A soft drink turneth away company. -- 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/1347370061.5305.147.ca...@zakaz.uk.xensource.com
Bug#665881: [wheezy] module ath5k is blocking wlan-card
Hans-J. Ullrich wrote: Am Dienstag, 11. September 2012 schrieb Jonathan Nieder: Drat. Am I correct in guessing that the prebuilt 3.3.6 package from http://snapshot.debian.org/package/linux-2.6/ reproduces it, while 3.4.1 does not? Huh, I did not test those versions. I just tested 3.2-xx (stock debian testing) and now at your advice version 3.5. (experimental) If 3.5 will work, I can test 3.3 and 3.4, too, if needed. Ah, I think I see where I misunderstood. When you said The described behavior appears EVERY TIME, did you mean that it appears after a while (how long?), and not necessarily the first time you try to use wireless after rebooting out of Windows 7 into Linux? Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120911133951.GA2443@mannheim-rule.local
Bug#665881: [wheezy] module ath5k is blocking wlan-card
Am Dienstag, 11. September 2012 schrieb Jonathan Nieder: Ah, I think I see where I misunderstood. When you said The described behavior appears EVERY TIME, did you mean that it appears after a while (how long?), and not necessarily the first time you try to use wireless after rebooting out of Windows 7 into Linux? No, I meant it this way: I started Windows 7, then rebooted and started again choosing Linux, then the bahviour appeared every time (hmm, maybe each time might be the better English expression). So I guessed, that Windows switched something in the wirelesscard or the bus. Jonathan Hans -- 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/201209111550.38404.hans.ullr...@loop.de
Bug#665881: [wheezy] module ath5k is blocking wlan-card
Hans-J. Ullrich wrote: Am Dienstag, 11. September 2012 schrieb Jonathan Nieder: Ah, I think I see where I misunderstood. When you said The described behavior appears EVERY TIME, did you mean that it appears after a while (how long?), and not necessarily the first time you try to use wireless after rebooting out of Windows 7 into Linux? No, I meant it this way: I started Windows 7, then rebooted and started again choosing Linux, then the bahviour appeared every time (hmm, maybe each time might be the better English expression). Ok, that is how I understood it the first time. My question still stands: when it happened every time, did it happen right away? If it did, and assuming you rebooted out of Windows 7 to try it, there is no need to test 3.5.y any more. We already know it doesn't reproduce the bug under the same circumstances as 3.2.y did. Hoping that clarifies, Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120911143520.GA2957@mannheim-rule.local
Bug#665881: [wheezy] module ath5k is blocking wlan-card
Ok, that is how I understood it the first time. My question still stands: when it happened every time, did it happen right away? Yes, it happened at once. Right after I booted Win7 and then booted into Linux again. It happened also, when I booted Win 7, shut down the computer, powered off (power supply and power cell), and then started Linux. Did I describe it now better? If it did, and assuming you rebooted out of Windows 7 to try it, there is no need to test 3.5.y any more. We already know it doesn't reproduce the bug under the same circumstances as 3.2.y did. So you know the reasons. That is really good news! I read about, that 3.5 changed several things in bus strategies. Hoping that clarifies, Jonathan Thank you very much! Hans -- 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/201209111640.58551.hans.ullr...@loop.de
Bug#665881: [wheezy] module ath5k is blocking wlan-card
Hans-J. Ullrich wrote: Yes, it happened at once. Right after I booted Win7 and then booted into Linux again. Ok, very good. [...] If it did, and assuming you rebooted out of Windows 7 to try it, there is no need to test 3.5.y any more. We already know it doesn't reproduce the bug under the same circumstances as 3.2.y did. So you know the reasons. No. We know the above because of the information you provided! * 3.2.y triggers the bug reproducibly * 3.5.y does not trigger the bug reproducibly I have my guesses about causes, but I am keeping them to myself until we have the additional information I asked about, namely how 3.3.6 and 3.4.1 do. Thanks for your patience, and sorry for the lack of clarity. Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120911152638.GA3006@mannheim-rule.local
Bug#687308: linux-image-3.2.0-2-686-pae: When insert usb yota lte modem or usb mouse both devices failed to work.
Package: src:linux Version: 3.2.20-1 Severity: important Dear Maintainer, Sometimes when I insert device, both of them fail to work. The only solution is to reboot laptop, which is bad. Last line in dmesg are: Sep 11 21:34:08 localhost kernel: [18653.975474] usb 2-1.2: new low-speed USB device number 8 using ehci_hcd Sep 11 21:34:08 localhost kernel: [18654.072262] usb 2-1.2: New USB device found, idVendor=045e, idProduct=00cb Sep 11 21:34:08 localhost kernel: [18654.072268] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Sep 11 21:34:08 localhost kernel: [18654.072273] usb 2-1.2: Product: Microsoft Basic Optical Mouse v2.0 Sep 11 21:34:08 localhost kernel: [18654.072276] usb 2-1.2: Manufacturer: Microsoft Sep 11 21:34:08 localhost kernel: [18654.076391] input: Microsoft Microsoft Basic Optical Mouse v2.0 as /devices/pci:00/:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/input/input16 Sep 11 21:34:08 localhost kernel: [18654.076793] generic-usb 0003:045E:00CB.0002: input,hidraw0: USB HID v1.11 Mouse [Microsoft Microsoft Basic Optical Mouse v2.0 ] on usb-:00:1d.0-1.2/input0 Sep 11 21:35:09 localhost kernel: [18714.942458] usb 2-1.3: USB disconnect, device number 5 Sep 11 21:35:09 localhost kernel: [18714.942585] rndis_host 2-1.3:1.0: eth1: unregister 'rndis_host' usb-:00:1d.0-1.3, RNDIS device Sep 11 21:35:11 localhost kernel: [18717.048667] usb 2-1.3: new high-speed USB device number 9 using ehci_hcd Sep 11 21:35:11 localhost kernel: [18717.152258] ehci_hcd :00:1d.0: fatal error Sep 11 21:35:11 localhost kernel: [18717.156193] ehci_hcd :00:1d.0: HC died; cleaning up Sep 11 21:35:11 localhost kernel: [18717.159056] ehci_hcd :00:1d.0: force halt; handshake f8224824 4000 4000 - -110 Sep 11 21:35:11 localhost kernel: [18717.159060] ehci_hcd :00:1d.0: HC died; cleaning up Sep 11 21:35:11 localhost kernel: [18717.159156] usb 2-1.3: device descriptor read/all, error -108 Sep 11 21:35:11 localhost kernel: [18717.159165] hub 2-1:1.0: cannot disable port 3 (err = -19) Sep 11 21:35:11 localhost kernel: [18717.159180] hub 2-1:1.0: cannot reset port 3 (err = -19) Sep 11 21:35:11 localhost kernel: [18717.159187] hub 2-1:1.0: cannot disable port 3 (err = -19) Sep 11 21:35:11 localhost kernel: [18717.159198] hub 2-1:1.0: cannot reset port 3 (err = -19) Sep 11 21:35:11 localhost kernel: [18717.159205] hub 2-1:1.0: cannot disable port 3 (err = -19) Sep 11 21:35:11 localhost kernel: [18717.159216] hub 2-1:1.0: cannot reset port 3 (err = -19) Sep 11 21:35:11 localhost kernel: [18717.159222] hub 2-1:1.0: cannot disable port 3 (err = -19) Sep 11 21:35:11 localhost kernel: [18717.159228] hub 2-1:1.0: unable to enumerate USB device on port 3 Sep 11 21:35:11 localhost kernel: [18717.159234] hub 2-1:1.0: cannot disable port 3 (err = -19) Sep 11 21:35:11 localhost kernel: [18717.159245] usb 2-1.2: USB disconnect, device number 8 Sep 11 21:35:11 localhost kernel: [18717.288370] usb 2-1.6: USB disconnect, device number 3 Sep 11 21:35:11 localhost kernel: [18717.340275] usb 2-1: USB disconnect, device number 2 -- Package-specific info: ** Version: Linux version 3.2.0-2-686-pae (Debian 3.2.20-1) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-7) ) #1 SMP Mon Jun 11 18:27:04 UTC 2012 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-2-686-pae root=UUID=2df64c86-d83f-4dba-800d-699a1b3bb259 ro quiet ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [9.536006] [drm] nouveau :01:00.0: Attempting to load BIOS image from PROM [9.536016] [drm] nouveau :01:00.0: ... BIOS signature not found [9.536018] [drm] nouveau :01:00.0: Attempting to load BIOS image from PCIROM [9.545817] nouveau :01:00.0: Invalid ROM contents [9.545909] [drm] nouveau :01:00.0: ... BIOS signature not found [9.545912] [drm] nouveau :01:00.0: Attempting to load BIOS image from ACPI [ 10.074032] input: FSPPS/2 Sentelic FingerSensingPad as /devices/platform/i8042/serio1/input/input14 [ 13.289958] [drm] nouveau :01:00.0: ... appears to be valid [ 13.289962] [drm] nouveau :01:00.0: BIT BIOS found [ 13.289965] [drm] nouveau :01:00.0: Bios version 70.08.19.00 [ 13.289969] [drm] nouveau :01:00.0: TMDS table version 2.0 [ 13.289971] [drm] nouveau :01:00.0: Found Display Configuration Block version 4.0 [ 13.289974] [drm] nouveau :01:00.0: Raw DCB entry 0: 02014300 [ 13.289976] [drm] nouveau :01:00.0: Raw DCB entry 1: 000e [ 13.289979] [drm] nouveau :01:00.0: DCB connector table: VHER 0x40 5 16 4 [ 13.289981] [drm] nouveau :01:00.0: 0: 0x0340: type 0x40 idx 0 tag 0xff [ 13.289983] [drm] nouveau :01:00.0: 1: 0x1061: type 0x61 idx 1 tag 0x07 [ 13.289985] [drm] nouveau :01:00.0: 2: 0x0147: type 0x47 idx 2 tag 0xff [ 13.289987] [drm] nouveau :01:00.0: 3: 0x00202346: type 0x46 idx 3 tag 0x08 [ 13.289989] [drm]
Bug#687309: linux-image-3.5-trunk-686-pae: USB keyboard not available at boot for cryptsetup
Package: src:linux Version: 3.5-1~experimental.1 Severity: normal Usertags: pca.it-boot Hi there! The Samsung NP-Q1u [1] has on-device (slightly difficult for everyday usage) and USB-external keyboards. Starting from 3.5-1~experimental.1 this latter is no more available at the cryptsetup prompt, while it works as expected in GRUB-2 and GNOME-3. [1] http://bugs.debian.org/682737 The same behavior happens with 3.5.2-1~experimental.1, but it did not with 3.4.4-1~experimental.1 or 3.2.23-1. However, the differences in the initrd content does not seem relevant: --8---cut here---start-8--- --- initrd.img-3.4-trunk-686-pae_files.find.sed 2012-09-11 16:08:21.960755897 +0200 +++ initrd.img-3.5-trunk-686-pae_files.find.sed 2012-09-11 16:08:09.800695591 +0200 @@ -140,9 +140,11 @@ ./usr/share/plymouth/themes/joy/background.png ./usr/share/plymouth/themes/joy/progress_dot_off.png ./usr/share/plymouth/themes/joy/debian_logo.png +./usr/share/plymouth/themes/joy/password_dot16.png ./usr/share/plymouth/themes/joy/joy.plymouth ./usr/share/plymouth/themes/joy/password_field.png ./usr/share/plymouth/themes/joy/progress_dot_off16.png +./usr/share/plymouth/themes/joy/password_dot.png ./usr/share/plymouth/debian-logo.png ./usr/share/plymouth/plymouthd.defaults ./usr/share/fonts @@ -543,6 +545,7 @@ ./lib/modules/linuxtrunk-686-pae/kernel/drivers/net/team/team.ko ./lib/modules/linuxtrunk-686-pae/kernel/drivers/net/team/team_mode_activebackup.ko ./lib/modules/linuxtrunk-686-pae/kernel/drivers/net/team/team_mode_roundrobin.ko +./lib/modules/linuxtrunk-686-pae/kernel/drivers/net/team/team_mode_loadbalance.ko ./lib/modules/linuxtrunk-686-pae/kernel/drivers/net/phy ./lib/modules/linuxtrunk-686-pae/kernel/drivers/net/phy/lxt.ko ./lib/modules/linuxtrunk-686-pae/kernel/drivers/net/phy/micrel.ko @@ -824,8 +827,6 @@ ./lib/modules/linuxtrunk-686-pae/kernel/drivers/ssb/ssb.ko ./lib/modules/linuxtrunk-686-pae/kernel/drivers/thermal ./lib/modules/linuxtrunk-686-pae/kernel/drivers/thermal/thermal_sys.ko -./lib/modules/linuxtrunk-686-pae/kernel/drivers/power -./lib/modules/linuxtrunk-686-pae/kernel/drivers/power/power_supply.ko ./lib/modules/linuxtrunk-686-pae/kernel/drivers/misc ./lib/modules/linuxtrunk-686-pae/kernel/drivers/misc/cb710 ./lib/modules/linuxtrunk-686-pae/kernel/drivers/misc/cb710/cb710.ko --8---cut here---end---8--- --8---cut here---start-8--- diff -Naur initrd.img-3.4-trunk-686-pae_files/conf/modules initrd.img-3.5-trunk-686-pae_files/conf/modules --- initrd.img-3.4-trunk-686-pae_files/conf/modules 2012-09-11 16:04:11.035511620 +0200 +++ initrd.img-3.5-trunk-686-pae_files/conf/modules 2012-09-11 15:58:24.825794859 +0200 @@ -1,2 +1 @@ i915 modeset=1 -unix diff -Naur initrd.img-3.4-trunk-686-pae_files/etc/udev/udev.conf initrd.img-3.5-trunk-686-pae_files/etc/udev/udev.conf --- initrd.img-3.4-trunk-686-pae_files/etc/udev/udev.conf 2012-09-11 16:04:11.031511607 +0200 +++ initrd.img-3.5-trunk-686-pae_files/etc/udev/udev.conf 2012-09-11 15:58:24.821794836 +0200 @@ -1,4 +1,7 @@ # The initial syslog(3) priority: err, info, debug or its # numerical equivalent. For runtime debugging, the daemons internal # state can be changed with: udevadm control --log-priority=value. +# +# udevd is started in the initramfs, so when this file is modified the +# initramfs should be rebuilt. udev_log=err --8---cut here---end---8--- I also tried to add usbhid to /etc/initramfs-tools/modules, but nothing changed. Any ideas? Thx, bye, Gismo / Luca -- Package-specific info: ** Version: Linux version 3.5-trunk-686-pae (Debian 3.5-1~experimental.1) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-8) ) #1 SMP Thu Aug 2 17:56:18 UTC 2012 ** Command line: BOOT_IMAGE=/vmlinuz-3.5-trunk-686-pae root=/dev/mapper/kappei-root ro quiet splash ** Not tainted ** Kernel log: [ 47.551797] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null) [ 50.917672] udevd[381]: starting version 175 [ 52.377713] ACPI: AC Adapter [ADP1] (off-line) [ 52.395135] ACPI: Requesting acpi_cpufreq [ 52.397318] ACPI: Battery Slot [BAT1] (battery present) [ 52.406151] Marking TSC unstable due to TSC halts in idle [ 52.406185] ACPI: acpi_idle registered with cpuidle [ 52.427336] Switching to clocksource hpet [ 52.789087] input: PC Speaker as /devices/platform/pcspkr/input/input5 [ 53.758238] cfg80211: Calling CRDA to update world regulatory domain [ 53.791360] Bluetooth: Core ver 2.16 [ 53.791416] NET: Registered protocol family 31 [ 53.791422] Bluetooth: HCI device and connection manager initialized [ 53.791910] Bluetooth: HCI socket layer initialized [ 53.791917] Bluetooth: L2CAP socket layer initialized [ 53.791931] Bluetooth: SCO socket layer initialized [ 53.806275] ACPI Warning: 0x18a0-0x18bf SystemIO
Bug#665881: [wheezy] module ath5k is blocking wlan-card
I have my guesses about causes, but I am keeping them to myself until we have the additional information I asked about, namely how 3.3.6 and 3.4.1 do. I would like to help. Can you tell me, where I find the packages of 3.3 and 3.4 images? I did not find them in the debian repositories. Thanks for your patience, and sorry for the lack of clarity. No problem. Jonathan Hans -- 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/201209111827.07024.hans.ullr...@loop.de
Bug#687338: firmware-nonfree: [INTL:de] Initial German debconf translation
Package: firmware-nonfree Version: 0.37 Severity: wishlist Tags: l10n patch Hi, please find attached the German translation of firmware-nonfree. Kind regards, Chris # Translation of the firmware-linux-nonfree debconf template to German. # Copyright (C) see http://packages.debian.org/changelogs/pool/non-free/f/ #firmware-nonfree/firmware-nonfree_0.36/firmware-linux-nonfree.copyright # This file is distributed under the same license as the # firmware-linux-nonfree package. # Translated by Chris Leick 2012. msgid msgstr Project-Id-Version: firmware-nonfree 0.37\n Report-Msgid-Bugs-To: firmware-nonf...@packages.debian.org\n POT-Creation-Date: 2012-09-03 12:15+0200\n PO-Revision-Date: 2012-09-03 22:41+0200\n Last-Translator: Chris Leick c.le...@vollbio.de\n Language-Team: de debian-l10n-ger...@lists.debian.org\n Language: de\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n #. Type: boolean #. Description #: ../templates/templates.license.in:2001 msgid Do you agree to the \@license-title@\? msgstr Stimmen Sie der »@license-title@« zu? #. Type: boolean #. Description #: ../templates/templates.license.in:2001 msgid In order to install this package, you must agree to the following terms, the \@license-title@\. If you do not agree, the installation will be canceled. msgstr Um dieses Paket zu installieren, müssen Sie den folgenden Bedingungen der »@license-title@« zustimmen. Falls Sie nicht zustimmen, wird die Installation abgebrochen. #. Type: error #. Description #: ../templates/templates.license.in:3001 msgid Declined @license-title@ msgstr @license-title@ abgelehnt #. Type: error #. Description #: ../templates/templates.license.in:3001 msgid If you do not agree to the \@license-title@\ license terms you cannot install this software. msgstr Falls Sie den »@license-title@«-Lizenzbedingungen nicht zustimmen, können Sie diese Software nicht installieren. #. Type: error #. Description #: ../templates/templates.license.in:3001 msgid The installation of this package has been canceled. msgstr Die Installation dieses Pakets wurde abgebrochen.
Processed: Re: Bug#685360: Acknowledgement (AMD SB 750 + Logitech USB keyboard broken and system unbootable with Linux 3.2 (regression from 2.6.38))
Processing control commands: retitle -1 AMD SB 750 + Logitech USB keyboard brokenness with Linux 3.2 (regression from 3.1) Bug #685360 [src:linux] AMD SB 750 + Logitech USB keyboard brokenness with Linux 3.2 (regression from 2.6.38) Changed Bug title to 'AMD SB 750 + Logitech USB keyboard brokenness with Linux 3.2 (regression from 3.1)' from 'AMD SB 750 + Logitech USB keyboard brokenness with Linux 3.2 (regression from 2.6.38)' -- 685360: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685360 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.b685360.134740359611508.transcr...@bugs.debian.org
Bug#685360: Acknowledgement (AMD SB 750 + Logitech USB keyboard broken and system unbootable with Linux 3.2 (regression from 2.6.38))
Control: retitle -1 AMD SB 750 + Logitech USB keyboard brokenness with Linux 3.2 (regression from 3.1) On Mon, Aug 20, 2012 at 06:26:42PM +0200, Josip Rodin wrote: I'll try to bisect this now with my config. It looks like it's definitely in some way related with the introduction of CONFIG_HID_LOGITECH_DJ in 3.2+, because 3.1.0 works fine... -- 2. That which causes joy or happiness. -- 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/20120911224629.ga32...@entuzijast.net
Bug#685360: Acknowledgement (AMD SB 750 + Logitech USB keyboard broken and system unbootable with Linux 3.2 (regression from 2.6.38))
On Wed, Sep 12, 2012 at 12:46:29AM +0200, Josip Rodin wrote:
On Mon, Aug 20, 2012 at 06:26:42PM +0200, Josip Rodin wrote:
I'll try to bisect this now with my config.
It looks like it's definitely in some way related with the introduction of
CONFIG_HID_LOGITECH_DJ in 3.2+, because 3.1.0 works fine...
The dmesg difference between 3.1.0 (working) and 3.2.0 (broken) is a bit
confusing - on one USB port, there's no change, but on the other the new
module reports a failure (this output is with hid.debug=1 and is a bit fuzzy
because of random harmless changes like spelling fixes or device indices
5 vs 3):
-usb 2-5: new high speed USB device number 2 using ehci_hcd
-usb 5-1: new low speed USB device number 2 using ohci_hcd
+usb 2-5: new high-speed USB device number 2 using ehci_hcd
+usb 3-1: new low-speed USB device number 2 using ohci_hcd
drivers/hid/usbhid/hid-core.c: HID probe called for ifnum 0
-input: Logitech USB Receiver as
/devices/pci:00/:00:12.0/usb5/5-1/5-1:1.0/input/input3
+input: Logitech USB Receiver as
/devices/pci:00/:00:12.0/usb3/3-1/3-1:1.0/input/input3
generic-usb 0003:046D:C51B.0001: input: USB HID v1.11 Mouse [Logitech USB
Receiver] on usb-:00:12.0-1/input
drivers/hid/usbhid/hid-core.c: HID probe called for ifnum 1
drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0110
wIndex=0x0001 wLength=7
generic-usb 0003:046D:C51B.0002: claimed by neither input, hiddev nor hidraw
-usb 5-2: new full speed USB device number 3 using ohci_hcd
+usb 3-2: new full-speed USB device number 3 using ohci_hcd
drivers/hid/usbhid/hid-core.c: HID probe called for ifnum 0
-drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Set_Report wValue=0x0200
wIndex=0x wLength=1
-input: Logitech USB Receiver as
/devices/pci:00/:00:12.0/usb5/5-2/5-2:1.0/input/input4
-generic-usb 0003:046D:C52B.0003: input: USB HID v1.11 Keyboard [Logitech USB
Receiver] on usb-:00:12.0-2/in
+drivers/hid/hid-logitech-dj.c: logi_dj_probe called for ifnum 0
+drivers/hid/hid-logitech-dj.c: logi_dj_probe: ignoring ifnum 0
drivers/hid/usbhid/hid-core.c: HID probe called for ifnum 1
-input: Logitech USB Receiver as
/devices/pci:00/:00:12.0/usb5/5-2/5-2:1.1/input/input5
-generic-usb 0003:046D:C52B.0004: input: USB HID v1.11 Mouse [Logitech USB
Receiver] on usb-:00:12.0-2/input
+drivers/hid/hid-logitech-dj.c: logi_dj_probe called for ifnum 1
+drivers/hid/hid-logitech-dj.c: logi_dj_probe: ignoring ifnum 1
drivers/hid/usbhid/hid-core.c: HID probe called for ifnum 2
+drivers/hid/hid-logitech-dj.c: logi_dj_probe called for ifnum 2
drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0110
wIndex=0x0002 wLength=7
drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0111
wIndex=0x0002 wLength=20
drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0120
wIndex=0x0002 wLength=15
drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0121
wIndex=0x0002 wLength=32
-generic-usb 0003:046D:C52B.0005: claimed by neither input, hiddev nor hidraw
-usb 2-5: reset high speed USB device number 2 using ehci_hcd
+logitech-djreceiver 0003:046D:C52B.0005: claimed by neither input, hiddev nor
hidraw
+logitech-djreceiver 0003:046D:C52B.0005: logi_dj_probe:hid_hw_start returned
error:-19
Now where did the devices 0003:046D:C52B.000[34] go with the new kernel?
Are they the ones that logi_dj_probe sees as 0 and 1?
The code says:
/* Ignore interfaces 0 and 1, they will not carry any data, dont create
* any hid_device for them */
if (intf-cur_altsetting-desc.bInterfaceNumber !=
LOGITECH_DJ_INTERFACE_NUMBER) {
dbg_hid(%s: ignoring ifnum %d\n, __func__,
intf-cur_altsetting-desc.bInterfaceNumber);
return -ENODEV;
}
Well, that probably explains it. But why does it do that?
lsusb -v says the following about the hardware:
Bus 005 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x046d Logitech, Inc.
idProduct 0xc52b Unifying Receiver
bcdDevice 12.01
iManufacturer 1 Logitech
iProduct2 USB Receiver
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 84
bNumInterfaces 3
bConfigurationValue 1
iConfiguration 4 RQR12.01_B0019
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 98mA
Interface Descriptor:
bLength 9
Processed (with 1 errors): reassign 687309 to initramfs-tools, merging 682340 687309
Processing commands for cont...@bugs.debian.org:
reassign 687309 initramfs-tools 0.107
Bug #687309 [src:linux] linux-image-3.5-trunk-686-pae: USB keyboard not
available at boot for cryptsetup
Bug reassigned from package 'src:linux' to 'initramfs-tools'.
No longer marked as found in versions linux/3.5-1~experimental.1.
Ignoring request to alter fixed versions of bug #687309 to the same values
previously set
Bug #687309 [initramfs-tools] linux-image-3.5-trunk-686-pae: USB keyboard not
available at boot for cryptsetup
Marked as found in versions initramfs-tools/0.107.
merge 682340 687309
Bug #682340 [initramfs-tools] USB keyboard unavailable for crypto with Linux 3.5
Unable to merge bugs because:
severity of #687309 is 'normal' not 'important'
Failed to merge 682340: Did not alter merged bugs
Debbugs::Control::set_merged('transcript', 'GLOB(0x204f458)',
'requester', 'Ben Hutchings b...@decadent.org.uk', 'request_addr',
'cont...@bugs.debian.org', 'request_msgid',
'1347414141-1659-bts-...@decadent.org.uk', 'request_subject', ...) called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 537
eval {...} called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 536
Debbugs::Control::Service::control_line('line', 'merge 682340 687309',
'clonebugs', 'HASH(0x1fc89e8)', 'limit', 'HASH(0x1fc8430)',
'common_control_options', 'ARRAY(0x1fc8478)', 'errors', ...) called at
/usr/lib/debbugs/service line 471
thanks
Stopping processing here.
Please contact me if you need assistance.
--
682340: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682340
687309: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687309
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.13474141472511.transcr...@bugs.debian.org
Processed: forcibly merging 682340 687309
Processing commands for cont...@bugs.debian.org: forcemerge 682340 687309 Bug #682340 [initramfs-tools] USB keyboard unavailable for crypto with Linux 3.5 Bug #687309 [initramfs-tools] linux-image-3.5-trunk-686-pae: USB keyboard not available at boot for cryptsetup Severity set to 'important' from 'normal' Added tag(s) pending. Merged 682340 687309 thanks Stopping processing here. Please contact me if you need assistance. -- 682340: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682340 687309: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687309 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.134741635017464.transcr...@bugs.debian.org
