Bug#648364: linux-image-3.1.0-1-amd64: ath9k doesn't associate with my AP (but works with other AP's)
da:0129 Realtek Semiconductor Corp. Bus 004 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-3.1.0-1-amd64 depends on: ii debconf [debconf-2.0] 1.5.41 ii initramfs-tools [linux-initramfs-tool] 0.99 ii linux-base 3.3 ii module-init-tools 3.16-1 Versions of packages linux-image-3.1.0-1-amd64 recommends: ii firmware-linux-free 3 Versions of packages linux-image-3.1.0-1-amd64 suggests: pn extlinux 2:4.04+dfsg-7 pn grub-pc1.99-12 pn linux-doc-3.1 Versions of packages linux-image-3.1.0-1-amd64 is related to: pn firmware-bnx2 pn firmware-bnx2x pn firmware-ipw2x00 pn firmware-ivtv pn firmware-iwlwifi pn firmware-linux pn firmware-linux-nonfree pn firmware-qlogic pn firmware-ralink pn xen-hypervisor -- debconf information: linux-image-3.1.0-1-amd64/postinst/missing-firmware-3.1.0-1-amd64: linux-image-3.1.0-1-amd64/postinst/ignoring-ramdisk: linux-image-3.1.0-1-amd64/postinst/depmod-error-initrd-3.1.0-1-amd64: false linux-image-3.1.0-1-amd64/prerm/removing-running-kernel-3.1.0-1-amd64: true -- .''`. Julien Valroff ~ ~ : :' : Debian Developer & Free software contributor `. `'` http://www.kirya.net/ `- 4096R/ E1D8 5796 8214 4687 E416 948C 859F EF67 258E 26B1 -- 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/2010193649.ga7...@kirya.net
Bug#633595: OK !
Hi Ben, Le lundi 29 août 2011 à 14:07:44 (+0200 CEST), Ben Hutchings a écrit : > On Mon, 2011-08-29 at 00:35 +0200, Eloi COUTANT wrote: > > Hi. > > > > I confirm that Julien's patch is efficient on Samsung RC510. > > I have no problems anymore : one, two and three fingers are working, > > "wheels" too ! > [...] > > Julien, please can you provide a list of *upstream* changes. We will > not apply a large patch with no such references. I have not written that patch at all, just made available the "original" DKMS tree so that people can test it easily. The patch was written by Seth Forshee and is available on LaunchPad bug #681904 [0]. All the patches, Ubuntu builts and dkms .deb are available at: http://people.canonical.com/~sforshee/lp681904/ Hope this helps. Cheers, Julien [0] https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/681904 -- .''`. Julien Valroff ~ ~ : :' : Debian Developer & Free software contributor `. `'` http://www.kirya.net/ `- 4096R/ E1D8 5796 8214 4687 E416 948C 859F EF67 258E 26B1 signature.asc Description: Digital signature
Re: Bug#594554: linux-image-2.6.35-trunk-amd64: pl2303 module needs to be first unloaded to make my GPS data logger work
Le vendredi 27 août 2010 à 12:18:29 (+0200), Frédéric Boiteux a écrit : > Date: Fri, 27 Aug 2010 12:18:29 +0200 > From: Frédéric Boiteux > To: jul...@kirya.net > Cc: debian-kernel@lists.debian.org, 594...@bugs.debian.org > Subject: Re: Bug#594554: linux-image-2.6.35-trunk-amd64: pl2303 module > needs > to be first unloaded to make my GPS data logger work > Organization: Calistel > > Le Fri, 27 Aug 2010 08:59:40 +0200, > Julien Valroff a écrit : > > > when I plug this GPS into the usb port, the module is loaded > > automatically, but utility software such as gpsbabel and josm (just > > examples) cannot communicate with the device. > > > > I first need to unloaded the pl2303 module by hand, switch off the > > GPS, and switch it on again. The module is ten automatically loaded > > again and everything works as expected. > >Hello Julien, Hi Frédéric, > I had a problem similar to yours with a BGT-31 : when let it going in > 'navilink' mode (to download traces on a computer), I had problems > contacting it (it worked from time to time). > I finally discovered that I had installed the gpsd package, and when > plugging my GPS, udev not only loaded the pl2003 module, but also > launched 'gpsd' service, which locked access to the device ! > Perhaps you have the same problem ? I had to kill gpsd before using > navilink tool. Thanks for the tip, but I do not use gpsd. I have tried a new piece of software (dg100ctl - not in Debian), here are the error message I get before I unload the module (the -p command is used the get the current configuration of the device, hence, read only access I guess...): $ dg100ctl -p open /dev/ttyUSB0 failed: Input/output error dg_100_send: write failed: Bad file descriptor After unloading the module and switching on the device again, it works as exepected: $ dg100ctl -p Logging info : Position, speed, time, and altitude Mem free : 100% WAAS/EGNOS/MSAS: disabled Speed threshold: disabled Distance threshold : 2 m Logging modes: Mode A: by time, every 10.00 seconds Mode B: by time, every 3.00 seconds Mode C: by time, every 1.00 seconds Cheers, Julien -- Julien Valroff http://www.kirya.net GPG key: 1024D/9F71D449 17F4 93D8 746F F011 B845 9F91 210B F2AB 9F71 D449 -- 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/20100827122753.ga2...@kirya.net
Bug#594554: linux-image-2.6.35-trunk-amd64: pl2303 module needs to be first unloaded to make my GPS data logger work
Package: linux-2.6 Version: 2.6.35-1~experimental.2 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I have recently acquired a GlobalSat DG-100 Data Logger, reported to work perfectly with the pl2303 module. when I plug this GPS into the usb port, the module is loaded automatically, but utility software such as gpsbabel and josm (just examples) cannot communicate with the device. I first need to unloaded the pl2303 module by hand, switch off the GPS, and switch it on again. The module is ten automatically loaded again and everything works as expected. I have tried loading the pl2303 by hand before plugging the device or loading it via /etc/modules at boot, with no success in both cases. I attach the kernel log for the whole sequence (plugging the device, unloading the module, switching off & on the device). I also have this issue with the 2.6.32 kernel from unstable. I do not have any idea how to get more information on this, but I would be happy to test anything which might help you getting more details to understand what happens. Cheers, Julien - -- Package-specific info: ** Version: Linux version 2.6.35-trunk-amd64 (Debian 2.6.35-1~experimental.2) (m...@debian.org) (gcc version 4.4.5 20100728 (prerelease) (Debian 4.4.4-8) ) #1 SMP Tue Aug 17 08:22:25 UTC 2010 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.35-trunk-amd64 root=/dev/mapper/gaia-root ro quiet splash ** Tainted: (2048) ** Model information sys_vendor: Acer product_name: Aspire 1810TZ product_version: v1.3310 chassis_vendor: Chassis Manufacturer chassis_version: Chassis Version bios_vendor: INSYDE bios_version: v1.3310 board_vendor: Acer board_name: JM11-MS board_version: Base Board Version ** Loaded modules: Module Size Used by pl2303 11408 0 usbserial 33726 1 pl2303 btrfs 399431 0 zlib_deflate 19035 1 btrfs crc32c 2703 1 libcrc32c 1332 1 btrfs ufs58582 0 qnx47109 0 hfsplus66610 0 hfs38324 0 minix 22210 0 ntfs 166518 0 vfat8188 0 msdos 6567 0 fat44523 2 vfat,msdos jfs 141774 0 xfs 645404 0 exportfs3602 1 xfs reiserfs 202075 0 ext4 281059 0 jbd2 69077 1 ext4 cbc 2689 695 aes_x86_64 7808 697 aes_generic27263 1 aes_x86_64 acpi_cpufreq5893 0 mperf 1499 1 acpi_cpufreq cpufreq_conservative 9744 0 cpufreq_powersave 1026 0 cpufreq_stats 3052 0 cpufreq_userspace 2296 0 parport_pc 20766 0 ppdev 5800 0 lp 8959 0 parport32010 3 parport_pc,ppdev,lp sco 7932 2 bnep 10476 2 rfcomm 31435 0 l2cap 30128 6 bnep,rfcomm crc16 1659 2 ext4,l2cap bluetooth 49885 6 sco,bnep,rfcomm,l2cap vboxnetadp 4467 0 vboxnetflt 12207 0 vboxdrv 1766334 2 vboxnetadp,vboxnetflt binfmt_misc 7037 1 uinput 6891 1 fuse 57953 1 ext2 55901 1 coretemp5524 0 ecryptfs 87304 1 loop 13422 0 snd_hda_codec_intelhdmi 9434 1 uvcvideo 52022 0 snd_hda_codec_realtek 277128 1 videodev 41850 1 uvcvideo v4l1_compat11997 2 uvcvideo,videodev snd_hda_intel 22582 1 v4l2_compat_ioctl32 9658 1 videodev snd_hda_codec 84698 3 snd_hda_codec_intelhdmi,snd_hda_codec_realtek,snd_hda_intel snd_hwdep 5938 1 snd_hda_codec arc41401 2 snd_pcm_oss32706 0 ecb 1959 3 snd_mixer_oss 13090 1 snd_pcm_oss snd_pcm74024 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss snd_seq_midi4946 0 joydev 9301 0 snd_rawmidi19576 1 snd_seq_midi snd_seq_midi_event 6337 1 snd_seq_midi snd_seq47046 4 snd_seq_midi,snd_seq_midi_event iwlagn107714 0 iwlcore95515 1 iwlagn snd_timer 19068 2 snd_pcm,snd_seq snd_seq_device 5896 3 snd_seq_midi,snd_rawmidi,snd_seq snd59675 15 snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device mac80211 167373 2 iwlagn,iwlcore psmouse51060 0 tpm_tis 8758 0 wmi 8103 0 soundcore 6914 1 snd snd_page_alloc 7724 2 snd_hda_intel
Bug#572858: initramfs-tools: Doesn't resume from hibernation, restarts fresh
Hi, On Mon, 8 Mar 2010 12:01:42 +0100, Frédéric Boiteux wrote: > Hello, > > Is the 572858 bug a duplicate of mine, 568877 ? I got same problem > resuming from hibernation with the swap (and so hibernation image) in a > LVM2 partition. I think you are right, both bugs seem to describe the same issue. I let Maximilian check this and reassign #572858 to lvm2 and mark it as a duplicate just in case our guess is wrong. Cheers, Julien -- 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/cea8869a3acc603e86293f55b602c...@kirya.net
Bug#572858: initramfs-tools: Doesn't resume from hibernation, restarts fresh
hi, Le lundi 08 mars 2010 à 04:46 +0100, maximilian attems a écrit : > On Sun, 07 Mar 2010, Julien Valroff wrote: > > > > /etc/initramfs-tools/conf.d/resume > > > > RESUME=UUID=aa748dde-93f1-4e7f-887a-71fa58db6140 > > > > > > > /etc/fstab > > > > proc/proc procdefaults0 0 > > /dev/mapper/gaia-root / ext3errors=remount-ro 0 1 > > # /boot was on /dev/sda1 during installation > > UUID=08ff5fb8-82dd-4968-a05f-b7cd323e052f /boot ext2defaults > > 0 2 > > /dev/mapper/gaia-swap_1 noneswapsw 0 0 > > hmm no the bug is actually the other way round, > why is there an UUID in /etc/initramfs-tools/conf.d/resume > > can you please post: > cat /proc/swaps FilenameTypeSizeUsedPriority /dev/mapper/gaia-swap_1 partition 9928696 0 -1 Cheers, Julien -- 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/1268026010.2496.0.ca...@gaia.kirya.net
Bug#572858: initramfs-tools: Doesn't resume from hibernation, restarts fresh
Le dimanche 07 mars 2010 à 16:14 +0100, maximilian attems a écrit : > On Sun, 07 Mar 2010, Julien Valroff wrote: > > > Package: initramfs-tools > > Version: 0.93.4 > > Severity: normal > > > > Hi, > > > > If I do not specify my resume partition in the kernel command line, my > > computer doesn't resume from hibernation, but starts fresh instead. > > > > This wasn't the case until recently. > > > > I have found a similar issue in Ubuntu, which has a patch attached and > > which is now tagged as fixed. Please see > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/499940 for all the > > details. > > > > I haven't tried adapting the patch to the currernt Debian package as it > > doesn't apply cleanly and I fear I make some errors and break my complete > > boot process. > > I would be glad testing anyway if needed. > > > > Cheers, > > Julien > > please post the content of those 2 files on relevant box: > /etc/initramfs-tools/conf.d/resume RESUME=UUID=aa748dde-93f1-4e7f-887a-71fa58db6140 > /etc/fstab proc/proc procdefaults0 0 /dev/mapper/gaia-root / ext3errors=remount-ro 0 1 # /boot was on /dev/sda1 during installation UUID=08ff5fb8-82dd-4968-a05f-b7cd323e052f /boot ext2defaults 0 2 /dev/mapper/gaia-swap_1 noneswapsw 0 0 $ ls -l /dev/disk/by-uuid/ total 0 lrwxrwxrwx 1 root root 10 7 mars 08:24 08ff5fb8-82dd-4968-a05f-b7cd323e052f -> ../../sda1 lrwxrwxrwx 1 root root 24 7 mars 08:24 aa748dde-93f1-4e7f-887a-71fa58db6140 -> ../../mapper/gaia-swap_1 lrwxrwxrwx 1 root root 22 7 mars 08:24 e91cb78c-f290-4059-8d5c-8183e2adc177 -> ../../mapper/gaia-root It is worth noting this box was installed on Sunday last week (from the testing daily CD image and immedately upgraded to sid after the base installation) Cheers, Julien -- 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/1267975075.14675.2.ca...@gaia.kirya.net
Bug#572858: initramfs-tools: Doesn't resume from hibernation, restarts fresh
Package: initramfs-tools Version: 0.93.4 Severity: normal Hi, If I do not specify my resume partition in the kernel command line, my computer doesn't resume from hibernation, but starts fresh instead. This wasn't the case until recently. I have found a similar issue in Ubuntu, which has a patch attached and which is now tagged as fixed. Please see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/499940 for all the details. I haven't tried adapting the patch to the currernt Debian package as it doesn't apply cleanly and I fear I make some errors and break my complete boot process. I would be glad testing anyway if needed. Cheers, Julien -- Package-specific info: -- /proc/cmdline BOOT_IMAGE=/vmlinuz-2.6.33-2-amd64 root=/dev/mapper/gaia-root ro quiet video=i915:modeset=1 -- /proc/filesystems ext3 ext2 fuseblk ext4 reiserfs xfs jfs msdos vfat ntfs minix hfs hfsplus qnx4 ufs btrfs -- lsmod Module Size Used by btrfs 376896 0 zlib_deflate 17746 1 btrfs crc32c 2560 1 libcrc32c 1106 1 btrfs ufs58477 0 qnx46722 0 hfsplus65606 0 hfs37759 0 minix 21277 0 ntfs 163868 0 vfat7900 0 msdos 6202 0 fat40118 2 vfat,msdos jfs 140819 0 xfs 753853 0 exportfs3202 1 xfs reiserfs 196965 0 ext4 278926 0 jbd2 63225 1 ext4 cryptd 5504 0 aes_x86_64 7340 2 aes_generic25714 1 aes_x86_64 ppdev 5565 0 lp 8201 0 parport27314 2 ppdev,lp sco 7257 2 bridge 39813 0 stp 1440 1 bridge bnep9722 2 rfcomm 29762 0 l2cap 25274 4 bnep,rfcomm crc16 1319 2 ext4,l2cap bluetooth 42103 6 sco,bnep,rfcomm,l2cap acpi_cpufreq5787 0 cpufreq_conservative 7910 0 cpufreq_powersave902 0 cpufreq_stats 2659 0 cpufreq_userspace 2024 0 uinput 6687 1 fuse 50478 1 ext2 53966 1 ecryptfs 80321 0 acerhdf 6083 0 loop 11902 0 snd_hda_codec_intelhdmi14085 1 snd_hda_codec_realtek 243343 1 snd_hda_intel 20179 2 uvcvideo 52292 0 snd_hda_codec 57782 3 snd_hda_codec_intelhdmi,snd_hda_codec_realtek,snd_hda_intel snd_hwdep 5428 1 snd_hda_codec videodev 31744 1 uvcvideo snd_pcm_oss32790 0 snd_mixer_oss 12654 1 snd_pcm_oss snd_pcm61254 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss snd_seq_midi4432 0 snd_rawmidi15810 1 snd_seq_midi snd_seq_midi_event 4628 1 snd_seq_midi v4l1_compat11442 2 uvcvideo,videodev snd_seq43279 2 snd_seq_midi,snd_seq_midi_event arc41274 2 v4l2_compat_ioctl32 9160 1 videodev ecb 1841 2 snd_timer 15749 2 snd_pcm,snd_seq snd_seq_device 4493 3 snd_seq_midi,snd_rawmidi,snd_seq joydev 8546 0 iwlagn 79776 0 snd47090 16 snd_hda_codec_intelhdmi,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device iwlcore81927 1 iwlagn mac80211 140504 2 iwlagn,iwlcore cfg80211 105832 3 iwlagn,iwlcore,mac80211 soundcore 4822 1 snd snd_page_alloc 6313 2 snd_hda_intel,snd_pcm rfkill 13164 4 bluetooth,cfg80211 i2c_i8017814 0 atl1c 26334 0 psmouse45587 0 serio_raw 3960 0 tpm_tis 7336 0 tpm 9933 1 tpm_tis evdev 7384 25 pcspkr 1699 0 ac 2192 0 tpm_bios4521 1 tpm battery 4998 0 processor 29489 3 acpi_cpufreq wmi 5461 0 ext3 107181 1 jbd37789 1 ext3 mbcache 5050 3 ext4,ext2,ext3 dm_mod 55446 6 sd_mod 30459 3 crc_t10dif 1276 1 sd_mod uhci_hcd 18585 0 ahci 32182 2 libata133993 1 ahci ehci_hcd 31298 0 scsi_mod 123365 2 sd_mod,libata usbcore 126389 4 uvcvideo,uhc
Bug#558237: linux-source-2.6.32: X with xserver-xorg-video-intel does not work any longer
Followup-For: Bug #558237 Hi, A fix was committed this week: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=e6be8d9d17bd44061116f601fe2609b3ace7aa69 If 2.6.32 is to be the definitive kernel for squeeze, the fix should be backported if possible. Cheers, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#521083: b43-fwcutter: Lots of "b43-phy0 ERROR: PHY transmission error"
Le mercredi 25 mars 2009 à 21:16 +0100, Rene Engelhard a écrit : > reassign 521083 linux-2.6 > retitle 521083 Lots of b43-phy0 ERROR: PHY transmission error > forcemerge 505252 521083 > thanks > > Hi, > > Julien Valroff wrote: > > Using kernel 2.6.28 and latest b43-fwcutter from Lenny, I get a lot of > > "b43-phy0 ERROR: PHY transmission error" lines in my syslog. > > And it's a probably a driver problem. Already on the kernel buglist > as #505252 Thanks, I haven't been able to find it. However, this report doesn't mention the errors I see in my logs, hence *maybe* not the same issue. > > Head of dmesg | grep b43 gives: > > [2.407936] b43-pci-bridge :02:03.0: PCI INT A -> GSI 17 (level, > > low) -> IRQ 17 > > [ 11.363081] b43-phy0: Broadcom 4318 WLAN found > > [ 19.366913] input: b43-phy0 as /devices/virtual/input/input8 > > [ 19.476093] b43 ssb0:0: firmware: requesting b43/ucode5.fw > > [ 19.550248] b43 ssb0:0: firmware: requesting b43/pcm5.fw > > [ 19.578587] b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw > > [ 19.604072] b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw > > [ 19.744094] b43-phy0: Loading firmware version 410.2160 (2007-05-26 > > 15:32:10) > > > > I am quite surprised to see a firmware dated of 2007 is loaded (I have > > tried and run > > again install_bcm43xx_firmware.sh very recently, just to be sure I have the > > right firmware installed). > > That's the firmware you want to have. See the Homaepage. It says > you want 4.150.10.5 for >= 2.6.25, and 2.6.28 is >= 2.6.25. And I see 410.2160 in my log, how am I supposed to know that it is the correct version?! > Don't file bugs against s simple tool whose purpose is just to extract > the firmware files from binary files but against the actual *driver* > if there's a driver problem 8and that's be the kernel.). Can this be so hard? I was refering to bug #480053 in which the exact same error was reported, and fixed by installing another firmware. Sorry, but I cannot understand why you react as you do. Can this be so hard to be a bit more patient with users reporting bugs, even not against the right package? Cheers, Julien -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#473800: ehci-hcd: ehci reset
forwarded 473800 http://bugzilla.kernel.org/show_bug.cgi?id=10852 thanks Hi, Le mercredi 04 juin 2008 à 14:42 +0200, maximilian attems a écrit : > On Wed, Jun 04, 2008 at 01:52:49PM +0200, zsuzsi wrote: > > > > [ 2195.800254] scsi 16:0:0:0: Direct-Access SAMSUNG SP1213N > > TL10 PQ: 0 ANSI: 0 CCS > > [ 2195.812216] sd 16:0:0:0: [sda] 234493056 512-byte hardware sectors > > (120060 MB) > > [ 2195.812954] sd 16:0:0:0: [sda] Write Protect is off > > [ 2195.813056] sd 16:0:0:0: [sda] Assuming drive cache: write through > > [ 2195.814279] sd 16:0:0:0: [sda] 234493056 512-byte hardware sectors > > (120060 MB) > > [ 2195.815267] sd 16:0:0:0: [sda] Write Protect is off > > [ 2195.815344] sd 16:0:0:0: [sda] Assuming drive cache: write through > > [ 2195.815436] sda:<6>usb 1-1: reset high speed USB device using ehci_hcd > > and address 2 > > > > can one of you guys please report that upstream in bugzilla.kernel.org > and let us know the bug number. I have just opened bug #10852 on the upstream Bugzilla. Please do not hesitate to comment on my report, as I have only talked about my own issue. Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#473800: #473800- linux-image-2.6.24: Multiple "Reset high speed USB device using ehci_hcd"
Hi, I am having more or less the same issue with 2.6.25, using an USB card reader. I always get "Reset high speed USB device using ehci_hcd" entries in my logs, but after unplugging and re-plugging the device, they do not appear anymore. However, I haven't noticed any system crash wince I have acquired this card reader. I have tried disabling the USB auto-suspend, or changing the value of the idle-delay (default to 2 secs), without success. (log entries after booting, device connected) [...] Jun 1 09:54:03 athyr kernel: [ 95.238361] usb 7-3: reset high speed USB device using ehci_hcd and address 2 Jun 1 09:55:15 athyr kernel: [ 130.876600] usb 7-3: reset high speed USB device using ehci_hcd and address 2 Jun 1 09:55:53 athyr kernel: [ 149.873816] usb 7-3: reset high speed USB device using ehci_hcd and address 2 [...] [ 489.675592] usb 7-3: new high speed USB device using ehci_hcd and address 5 [ 489.713724] usb 7-3: configuration #1 chosen from 1 choice [ 489.713958] scsi9 : SCSI emulation for USB Mass Storage devices [ 489.714951] usb 7-3: New USB device found, idVendor=058f, idProduct=6362 [ 489.714955] usb 7-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 489.714957] usb 7-3: Product: Mass Storage Device [ 489.714959] usb 7-3: Manufacturer: Generic [ 489.714962] usb 7-3: SerialNumber: 058F312D81B [ 489.714968] usb-storage: device found at 5 [ 489.714970] usb-storage: waiting for device to settle before scanning [ 490.507881] usb-storage: device scan complete [ 409.114303] scsi 9:0:0:0: Direct-Access Generic USB SD Reader1.00 PQ: 0 ANSI: 0 [ 409.114983] scsi 9:0:0:1: Direct-Access Generic USB CF Reader1.01 PQ: 0 ANSI: 0 [ 409.115552] scsi 9:0:0:2: Direct-Access Generic USB SM Reader1.02 PQ: 0 ANSI: 0 [ 409.116177] scsi 9:0:0:3: Direct-Access Generic USB MS Reader1.03 PQ: 0 ANSI: 0 [ 409.117596] sd 9:0:0:0: [sdb] Attached SCSI removable disk [ 409.150537] sd 9:0:0:1: [sdc] Attached SCSI removable disk [ 490.567810] sd 9:0:0:2: [sdd] Attached SCSI removable disk [ 490.569921] sd 9:0:0:3: [sde] Attached SCSI removable disk # lsusb Bus 007 Device 004: ID 058f:6362 Alcor Micro Corp. Hi-Speed 21-in-1 Flash Card Reader/Writer (Internal/External) [...] Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#459445: initramfs-tools: update-initramfs does not consider latest kernel by default
Le dimanche 06 janvier 2008 à 19:18 +0100, maximilian attems a écrit : > > when running update-initramfs without specifying a kernel version (-k), the > > default version should be the latest kernel version (according to manpage). > > > > It is not in my case: > > $ ls /var/lib/initramfs-tools/ > > 2.6.22-3-amd64 2.6.23-1-amd64 > > > > $ ls /boot/initrd.* > > /boot/initrd.img-2.6.22-3-amd64 /boot/initrd.img-2.6.23-1-amd64 > > /boot/initrd.img-2.6.22-3-amd64.bak /boot/initrd.img-2.6.23-1-amd64.bak > > please send in output of > ls -l / drwxr-xr-x 2 root root 4096 2008-01-06 18:44 bin drwxr-xr-x 4 root root 1024 2008-01-06 16:58 boot lrwxrwxrwx 1 root root11 2007-07-29 15:07 cdrom -> media/cdrom drwxr-xr-x 16 root root 4100 2008-01-06 17:33 dev drwxr-xr-x 3 root root 4096 2007-07-29 15:33 emul drwxr-xr-x 116 root root 12288 2008-01-06 19:06 etc drwxr-xr-x 7 root root 4096 2007-11-10 10:36 home drwxr-xr-x 2 root root 4096 2007-07-29 15:08 initrd lrwxrwxrwx 1 root root30 2007-10-31 21:19 initrd.img -> boot/initrd.img-2.6.22-3-amd64 lrwxrwxrwx 1 root root30 2007-10-20 08:53 initrd.img.old -> boot/initrd.img-2.6.23-1-amd64 drwxr-xr-x 17 root root 12288 2008-01-05 12:31 lib lrwxrwxrwx 1 root root20 2007-09-04 18:03 lib32 -> /emul/ia32-linux/lib lrwxrwxrwx 1 root root 4 2007-09-04 18:05 lib64 -> /lib drwx-- 2 root root 16384 2007-07-29 15:07 lost+found drwxr-xr-x 5 root root 4096 2008-01-06 17:07 media drwxr-xr-x 2 root root 4096 2007-04-24 22:26 mnt dr-xr-xr-x 137 root root 0 2008-01-06 17:22 proc drwxr-xr-x 21 root root 4096 2007-12-28 20:28 root drwxr-xr-x 2 root root 4096 2008-01-06 18:44 sbin drwxr-xr-x 2 root root 4096 2007-07-29 15:08 srv drwxr-xr-x 11 root root 0 2008-01-06 17:22 sys drwxrwxrwt 17 root root 32768 2008-01-06 19:10 tmp drwxr-xr-x 11 root root 4096 2007-09-04 18:05 usr drwxr-xr-x 15 root root 4096 2007-10-19 18:43 var lrwxrwxrwx 1 root root27 2007-10-31 21:19 vmlinuz -> boot/vmlinuz-2.6.22-3-amd64 lrwxrwxrwx 1 root root27 2007-10-20 08:53 vmlinuz.old -> boot/vmlinuz-2.6.23-1-amd64 I think I now understand - but it is obscure for me why this is so as kernel 2.6.23 has been installed and configured after 2.6.22 (which is still present as a dependency for linux-image-2.6-amd64) Cheers, Julien
Bug#459445: initramfs-tools: update-initramfs does not consider latest kernel by default
Package: initramfs-tools Version: 0.91d Severity: normal Hi, when running update-initramfs without specifying a kernel version (-k), the default version should be the latest kernel version (according to manpage). It is not in my case: $ ls /var/lib/initramfs-tools/ 2.6.22-3-amd64 2.6.23-1-amd64 $ ls /boot/initrd.* /boot/initrd.img-2.6.22-3-amd64 /boot/initrd.img-2.6.23-1-amd64 /boot/initrd.img-2.6.22-3-amd64.bak /boot/initrd.img-2.6.23-1-amd64.bak $ uname -r 2.6.23-1-amd64 # update-initramfs -u update-initramfs: Generating /boot/initrd.img-2.6.22-3-amd64 Note that update_initramfs is set to "yes" in /etc/initramfs-tools/update-initramfs.conf. When changing this option to "all", the expected behaviour work. Cheers, Julien -- Package-specific info: -- /proc/cmdline root=/dev/mapper/athyr-root ro quiet pci=nommconf vga=795 -- /proc/filesystems ext3 -- lsmod Module Size Used by i915 31616 2 drm 100392 3 i915 binfmt_misc17292 1 rfcomm 49448 0 l2cap 32896 5 rfcomm bluetooth 65796 4 rfcomm,l2cap tun16384 0 ppdev 13832 0 parport_pc 42664 0 lp 17480 0 parport44428 3 ppdev,parport_pc,lp ac 10760 0 battery18064 0 ipv6 303336 24 dm_crypt 18192 0 snd_seq_dummy 8452 0 snd_seq_oss36736 0 snd_seq_midi 13376 0 snd_rawmidi30624 1 snd_seq_midi snd_seq_midi_event 12416 2 snd_seq_oss,snd_seq_midi snd_seq58752 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event snd_seq_device 12948 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq coretemp 12544 0 w83627ehf 28168 0 hwmon_vid 7296 1 w83627ehf vboxdrv 1646592 0 loop 23428 0 snd_hda_intel 339364 0 snd_pcm_oss48288 0 snd_mixer_oss 21376 1 snd_pcm_oss snd_pcm89864 2 snd_hda_intel,snd_pcm_oss snd_timer 28552 2 snd_seq,snd_pcm button 13856 0 i2c_i801 13980 0 psmouse45596 0 intel_agp 32160 1 i2c_core 30976 1 i2c_i801 snd65640 9 snd_seq_oss,snd_rawmidi,snd_seq,snd_seq_device,snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer soundcore 13216 1 snd snd_page_alloc 15248 2 snd_hda_intel,snd_pcm tsdev 13440 0 iTCO_wdt 17232 0 serio_raw 11908 0 evdev 15360 4 pcspkr 7808 0 ext3 137488 3 jbd68080 1 ext3 mbcache13952 1 ext3 dm_mirror 27008 0 dm_snapshot21960 0 dm_mod 64368 10 dm_crypt,dm_mirror,dm_snapshot sd_mod 33408 3 ide_cd 44704 0 cdrom 39592 1 ide_cd ata_piix 23044 2 usbhid 34144 0 hid33152 1 usbhid ata_generic13188 0 jmicron 8576 0 [permanent] firewire_ohci 22912 0 firewire_core 49600 1 firewire_ohci crc_itu_t 6656 1 firewire_core skge 46608 0 floppy 66984 0 ahci 30468 0 libata129840 3 ata_piix,ata_generic,ahci generic10372 0 [permanent] scsi_mod 164664 2 sd_mod,libata ide_core 149904 3 ide_cd,jmicron,generic ehci_hcd 38540 0 uhci_hcd 29984 0 thermal22176 0 processor 43624 1 thermal fan10248 0 -- /etc/kernel-img.conf # Kernel image management overrides # See kernel-img.conf(5) for details do_symlinks = yes relative_links = yes do_bootloader = no do_bootfloppy = no do_initrd = yes link_in_boot = no postinst_hook = update-grub postrm_hook = update-grub -- /etc/initramfs-tools/initramfs.conf MODULES=most BUSYBOX=y KEYMAP=n BOOT=local DEVICE=eth0 NFSROOT=auto -- /etc/crypttab # -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.23-1-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages initramfs-tools depends on: ii cpio 2.9-9 GNU cpio -- a program to manage ar ii findutils4.2.31-4utilities for finding files--find, ii klibc-utils 1.5.7-4 small statically-linked utilities ii module-init-tools3.3-pre11-4
