Re: Immediate fallouts from the big linux changes, and actions
On Fri, Dec 29, 2023 at 08:04:19AM +0100, Roland Clobus wrote: > Yesterday I published 3 fixes which got merged really quickly. [...] > Now Jenkins is running fine for the live sid images again :-) > In the next step, I'll check the trixie live builds. awesome, thank you! -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ 20230709: Today was the warmest day on earth in 125,000 years. Today was also the day with the most planes in the air at one time ever in history. By the time you read this both of these records have probably been broken. signature.asc Description: PGP signature
Re: Immediate fallouts from the big linux changes, and actions
Hi Roland, FYI, you might want to read the full thread! ;) On Sun, Dec 24, 2023 at 08:38:57AM +0100, Cyril Brulebois wrote: > This is mostly for information: linux went through a lot of big changes, > initially staged in experimental, and uploaded to unstable as of linux > 6.6.8-1. These impacted the installer in different ways. This is a > summary of the obvious impacts, there might be some others down the line > (just by glancing at hw-detect's massaging of module list by stripping > the .ko suffix). > > - kernel-image-* packages are now shipping /boot/vmlinuz-* (or > /boot/vmlinux-* depending on the arch), instead of just /boot/vmlinuz > (respectively /boot/vmlinux). [...] this change also lead to failing live-builds, for trixie (the unstable live-builds are of course also affected but fail earlier due to #1058994), this can be seen in https://jenkins.debian.net/job/reproducible_debian_live_build_xfce_trixie/35/console which failed with cp: cannot stat 'chroot/debian-installer/build/dest/cdrom/vmlinuz': No such file or directory -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ Just 100 companies are responsible for 71% of global emissions. https://www.theguardian.com/sustainable-business/2017/jul/10/100-fossil-fuel-companies-investors-responsible-71-global-emissions-cdp-study-climate-change signature.asc Description: PGP signature
Bug#866314: linux-image-4.9.0-3-686-pae: 100+ times slower disk writes on 4.x+/i386/16+RAM, compared to 3.x
On Wed, Jun 01, 2022 at 04:01:10PM +0200, Diederik de Haas wrote: > On Wednesday, 1 June 2022 15:11:37 CEST Holger Levsen wrote: > > On Wed, Jun 01, 2022 at 02:53:06PM +0200, Diederik de Haas wrote: > > > So it would be really helpful if this would be added to the upstream bug > > > report. > > then please do so?!? > > And with that I've lost any motivation to further reduce the Debian kernel > bug > list. Let's keep this and other pointless bug open for ever. > Well done. you seem to assume that I know how to report upstream bugs to the kernel. yet I don't know. -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ The past is over. signature.asc Description: PGP signature
Bug#866314: linux-image-4.9.0-3-686-pae: 100+ times slower disk writes on 4.x+/i386/16+RAM, compared to 3.x
On Wed, Jun 01, 2022 at 02:53:06PM +0200, Diederik de Haas wrote: > So it would be really helpful if this would be added to the upstream bug > report. then please do so?!? -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ Bottled water companies don't produce water, they produce plastic bottles. signature.asc Description: PGP signature
Bug#866314: linux-image-4.9.0-3-686-pae: 100+ times slower disk writes on 4.x+/i386/16+RAM, compared to 3.x
On Wed, Jun 01, 2022 at 01:27:32AM +0200, Diederik de Haas wrote: > What's the current status wrt this bug? we downgraded the memory of our nodes to 8gb to work around the issue... -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ So what CAN we actually do? Well, individual decisions (eating less meat, taking public transport, buying less fast fashion) are all important, but we also need to change the system. As you may know, just 100 companies are responsible for 71% of global emissions. (@JessicaTheLaw) https://www.theguardian.com/sustainable-business/2017/jul/10/100-fossil-fuel-companies-investors-responsible-71-global-emissions-cdp-study-climate-change signature.asc Description: PGP signature
Bug#866314: linux-image-4.9.0-3-686-pae: 100+ times slower disk writes on 4.x+/i386/16+RAM, compared to 3.x
Hi Salvatore, On Sun, May 02, 2021 at 11:39:05AM +0200, Salvatore Bonaccorso wrote: > Doing some maintenance on open bugs for src:linux to bring unnecessary > still open bugs down, this one appeared as well on the radar of older > bugs for older kernels. > > Do you still want to keep this bug open for some reason, or should we > close it? I'm fine either way, but here I wanted to ask epxlicitly, as > there was still some movements up to february 2020 in the referenced > upstream report. > > I just wonder if it will be worth off, but maybe yes. I suppose it might be time to reduce memory on our i386 nodes to 15gb and see how that goes. We're still seeing our i386 nodes hanging basically every other day and I hope reducing memory will fix that. I suppose it would be nice to keep this bug open but I don't care that much either way. I understand i386 with lots of memory is super uncommon. cc:ing Mattia for his opinion on this. -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C ⠈⠳⣄ signature.asc Description: PGP signature
Bug#866314: linux-image-4.9.0-3-686-pae: 100+ times slower disk writes on 4.x+/i386/16+RAM, compared to 3.x
On Wed, Jun 28, 2017 at 11:22:06PM +, Holger Levsen wrote: > (As a workaround I plan to use 8 machines with 15gb ram instead of 4 with 35…) actually this wont work here, there are not enough storage ressources to run 8 instead of 4 machines… -- cheers, Holger signature.asc Description: Digital signature
Bug#866314: linux-image-4.9.0-3-686-pae: 100+ times slower disk writes on 4.x+/i386/16+RAM, compared to 3.x
On Wed, Jun 28, 2017 at 10:35:39PM +0100, Ben Hutchings wrote: > I would say only 'normal', because this isn't a sensible configuration. I was saying today that there are probably 100 people running i386 with i386 kernels with more than 16gb ram in the world. And then corrected myself to "1000"… ;-) > Why don't you assign a smaller amount of RAM to the 32-bit VMs? Are > there packages that need this much to build? because there are up to ten builds running simulataneously on these machines. 5 on average, and usually between 3 and 7 I'd say… And hey, it used to work nicely. (As a workaround I plan to use 8 machines with 15gb ram instead of 4 with 35…) -- cheers, Holger signature.asc Description: Digital signature
Bug#866314: linux-image-4.9.0-3-686-pae: 100+ times slower disk writes on 4.x+/i386/16+RAM, compared to 3.x
package: linux-image-4.9.0-3-686-pae version: 4.9.30-2+deb9u2 # severity: important ? forwarded: https://bugzilla.kernel.org/show_bug.cgi?id=196157 Hi, upon upgrading the i386 build nodes for tests.reproducible-builds.org to Stretch I noticed a huge performance loss, which I could "fix" by installing linux-image-4.9.0-3-amd64:amd64 (version 4.9.30-2+deb9u2 too). (which btw is a nice example for Multiarchs's usefulness…) Today Vagrant pointed me to https://bugzilla.kernel.org/show_bug.cgi?id=196157 which is the upstream issue tracking this. I'm filing this bug for the benefit of other Debian users and for myself to benefit from the BTS subscription and tracking features… We want to run half of our i386 build nodes with a 32 bit kernel and the other half with an 64 bit kernel to test reproducibility under this variation, so I'm really looking forward to see this bug fixed soon. Other people can probably just keep running the amd64 kernel, thus I've decided for normal severity for this issue. Thanks for maintaining src:linux! -- cheers, Holger signature.asc Description: Digital signature
Bug#814648: linux kernel backports broken
On Tue, May 31, 2016 at 10:30:53PM +0200, Christian Seiler wrote: > This is not an issue with the package build, but with pbuilder (and by > extension) cowbuilder only supprt the build profile syntax with > 0.215+nmu4, whereas Jessie only has 0.215+nmu3. So if you either use > pbuilder from testing/sid FYI: pbuilder 0.224~bpo8+1 is also available in jessie-backports. -- cheers, Holger signature.asc Description: Digital signature
Bug#791868: closed by Milan Kupcevic <mi...@physics.harvard.edu> (Bug#741642: fixed in mkvmlinuz 37+deb8u1)
Hi Milan, thanks for fixing this bug in stable! It's great to see this bug seeing fixed, even despite I finally gave the hardware away a very few weeks ago… :) cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: [Reproducible-builds] Reproducibility vs signatures
Hi, On Montag, 3. August 2015, Ben Hutchings wrote: See https://lists.debian.org/debian-kernel/2013/08/msg00267.html. Thanks. That seems to say that a.) only the kernel team can sign kernels, so no user signed kernels?? and b.) only amd64, while I believe uefi arm mainboards are there already or will be soon? cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: [Reproducible-builds] Reproducibility vs signatures
Hi, On Montag, 3. August 2015, Ben Hutchings wrote: That sort of works as long as there's only one architecture we want to do this for. But the ability to verify modules is useful in general so I would like to turn that on for all architectures. how is this going to work for builds on buildds anyway? I suppose you are not planning to build+sign all arch manually? And who can sign those kernels anyway? I suppose anybody should stil be able to build+sign+boot kernels, or? cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: [Reproducible-builds] Reproducibility vs signatures
Hi, On Montag, 3. August 2015, Ben Hutchings wrote: Only the FTP team will be able to get shim signed by the Microsoft CA. Only the FTP team will be able to sign GRUB and the kernel using the private key for which the public part is embedded in shim. Users can add further trusted keys at boot time through the BIOS setup program or shim; then they can use their own signed kernels. Thanks for clarifying. About your original question, I dont have a good answer right now. I think it would be a good topic to discuss at DebConf...! Thanks for bringing this up to us already! cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#789037: Accepted linux-2.6 2.6.32-48squeeze12 (all source) into squeeze-lts
Hi Patrick, On Mittwoch, 17. Juni 2015, Patrick Matthäi wrote: We have got problems with the new version on all of our vSphere 5.1/5.5 VMs and dedicated hosts. It looks like our xen VMs are not affected. Here some snips of dmesg: to confirm #789037 - you've only seen this on 32bit archs (i386/powerpc) but not on amd64?! No, we just use amd64, so it is affected. And the bug author wrote: Affects PPC and ia32. Not know if other arches affected oh, wow, thanks for the update, cc'ing the bug now too. (thread start is on the debian-lts@ list.) cheers, Holger, who holds off some reboots now signature.asc Description: This is a digitally signed message part.
Bug#783381: upgrade from wheezy to jessie on a PowerMac G4 Silver
package: upgrade-reports, linux-image-3.16.0-4-powerpc tags: powerpc Hi, I've upgraded my old PowerMac from wheezy to jessie, which failed like shown below. On boot now, yaboots boots the correct kernel but then after loading the initramfs the fontsize switches to gigantic (8 lines, 25 chars per line or so) and it goes into a systemd rescue environment, I believe. I havent investigated further (it's my last powerpc, about to be decommissioned), so I'm filing this bug report so that this doesnt get lost: Setting up linux-image-3.16.0-4-powerpc (3.16.7-ckt9-3~deb8u1) ... vmlinux(/boot/vmlinux-3.16.0-4-powerpc ) points to /boot/vmlinux-3.16.0-4-powerpc (/boot/vmlinux-3.16.0-4-powerpc) -- doing nothing at /var/lib/dpkg/info/linux-image-3.16.0-4-powerpc.postinst line 263. initrd.img(/boot/initrd.img-3.16.0-4-powerpc ) points to /boot/initrd.img-3.16.0-4-powerpc (/boot/initrd.img-3.16.0-4-powerpc) -- doing nothing at /var/lib/dpkg/info/linux-image-3.16.0-4-powerpc.postinst line 263. /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-3.16.0-4-powerpc run-parts: /etc/kernel/postinst.d/mkvmlinuz exited with return code 20 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-3.16.0-4-powerpc.postinst line 634. dpkg: error processing package linux-image-3.16.0-4-powerpc (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of linux-image-powerpc: linux-image-powerpc depends on linux-image-3.16.0-4-powerpc; however: Package linux-image-3.16.0-4-powerpc is not configured yet. dpkg: error processing package linux-image-powerpc (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-3.16.0-4-powerpc linux-image-powerpc myframe:~# cat /proc/cpuinfo processor : 0 cpu : 7400, altivec supported temperature : 38-40 C (uncalibrated) clock : 466.65MHz revision: 2.9 (pvr 000c 0209) bogomips: 66.58 timebase: 33290001 platform: PowerMac model : PowerMac3,4 machine : PowerMac3,4 motherboard : PowerMac3,4 MacRISC2 MacRISC Power Macintosh detected as : 69 (PowerMac G4 Silver) pmac flags : 0010 L2 cache: 1024K unified pmac-generation : NewWorld Memory : 768 MB myframe:~# ls /boot/ System.map-3.16.0-4-powerpc config-3.16.0-4-powerpc initrd.img-3.16.0-4-powerpc vmlinux-3.16.0-4-powerpc System.map-3.2.0-4-powerpc config-3.2.0-4-powerpc initrd.img-3.2.0-4-powerpc vmlinux-3.2.0-4-powerpc cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#773467: efikamx: linux-image-3.2.0-4-mx5 is not upgraded to linux-image-armmp (and that one doesn't work)
Package: src:linux,upgrade-reports Version: 3.16.7-ckt2-1 Severity: important Dear maintainers, I've just upgraded my Genesi EfikaMX nettop from wheezy to jessie and the only package which wasn't upgraded was linux-image-3.2.0-4-mx5, so I had to install linux-image-armmp manually... I'm not really sure how to solve this sensibly, suggesting that linux-image-armmp should provide linux-image-3.2.0-4-mx5 seems strange. Besides that the upgrade when flawlessly, but the system only has 450 packages installed anyway. But still, very neat! Just this...: root@efikamx:~# apt-get install linux-image-armmp Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: linux-image-3.16.0-4-armmp Suggested packages: linux-doc-3.16 debian-kernel-handbook fdutils Recommended packages: irqbalance The following NEW packages will be installed: linux-image-3.16.0-4-armmp linux-image-armmp 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 24.6 MB of archives. After this operation, 104 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://ftp.de.debian.org/debian/ jessie/main linux-image-3.16.0-4-armmp armhf 3.16.7-ckt2-1 [24.6 MB Get:2 http://ftp.de.debian.org/debian/ jessie/main linux-image-armmp armhf 3.16+63 [5368 B] Fetched 24.6 MB in 7s (3394 kB/s) Preconfiguring packages ... Selecting previously unselected package linux-image-3.16.0-4-armmp. (Reading database ... 43566 files and directories currently installed.) Preparing to unpack .../linux-image-3.16.0-4-armmp_3.16.7-ckt2-1_armhf.deb ... Unpacking linux-image-3.16.0-4-armmp (3.16.7-ckt2-1) ... Selecting previously unselected package linux-image-armmp. Preparing to unpack .../linux-image-armmp_3.16+63_armhf.deb ... Unpacking linux-image-armmp (3.16+63) ... Setting up linux-image-3.16.0-4-armmp (3.16.7-ckt2-1) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-3.16.0-4-armmp flash-kernel: deferring update (trigger activated) /etc/kernel/postinst.d/zz-flash-kernel: flash-kernel: deferring update (trigger activated) Setting up linux-image-armmp (3.16+63) ... Processing triggers for flash-kernel (3.28) ... flash-kernel: installing version 3.16.0-4-armmp Generating kernel u-boot image... done. Taking backup of uImage. Installing new uImage. Generating initramfs u-boot image... done. Taking backup of uInitrd. Installing new uInitrd. Generating boot script u-boot image... done. Taking backup of boot.scr. Installing new boot.scr. root@efikamx:~# And now let's see how it reboots :-) ... It didn't come back, will need to attach a serial console and see if I see anything useful there... cheers, Holger -- Package-specific info: ** Version: Linux version 3.2.0-4-mx5 (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 Debian 3.2.63-2+deb7u2 ** Command line: console=ttymxc0,115200 console=tty1 rootwait rw ** Not tainted ** Kernel log: [1.634403] usb usb2: Product: Freescale On-Chip EHCI Host Controller [1.640871] usb usb2: Manufacturer: Linux 3.2.0-4-mx5 ehci_hcd [1.646730] usb usb2: SerialNumber: mxc-ehci.1 [1.651779] hub 2-0:1.0: USB hub found [1.655586] hub 2-0:1.0: 1 port detected [1.660144] mousedev: PS/2 mouse device common for all mice [1.666960] mc13xxx-rtc mc13892-rtc: rtc core: registered mc13892-rtc as rtc0 [1.674393] Registered led device: efikamx:green [1.674512] Registered led device: efikamx:red [1.674621] Registered led device: efikamx:blue [1.675527] usbcore: registered new interface driver usbhid [1.681119] usbhid: USB HID core driver [1.685750] TCP cubic registered [1.689003] NET: Registered protocol family 17 [1.693491] Registering the dns_resolver key type [1.698283] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 2 [1.707206] registered taskstats version 1 [1.711726] regulator_init_complete: VCAM: disabling [1.716931] regulator_init_complete: VAUDIO: disabling [1.722306] regulator_init_complete: VVIDEO: disabling [1.727723] regulator_init_complete: VSD: disabling [1.733070] mc13xxx-rtc mc13892-rtc: setting system clock to 2014-12-18 15:30:20 UTC (1418916620) [1.742030] Initializing network drop monitor service [1.747919] Freeing init memory: 128K [1.784810] usb 1-1: new high-speed USB device number 2 using mxc-ehci [1.835537] udevd[46]: starting version 175 [1.959704] usb 1-1: New USB device found, idVendor=0b95, idProduct=772a [1.966519] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [1.973672] usb 1-1: Product: AX88x72A [1.977464] usb 1-1: Manufacturer: ASIX Elec. Corp. [1.982355] usb 1-1: SerialNumber: 123456 [2.127645] imx-sdma imx35-sdma: firmware: agent aborted loading
Bug#773467: efikamx: linux-image-3.2.0-4-mx5 is not upgraded to linux-image-armmp (and that one doesn't work)
control: reopen -1 control: reassign -1 release-notes control: retitle -1 Efikamx plattform not supported in jessie anymore On Donnerstag, 18. Dezember 2014, Bill Allombert wrote: I think that bug should be reassigned to the release notes. Point taken, thanks. signature.asc Description: This is a digitally signed message part.
Re: Build squeeze debian-installer with 3.2 kernel from backports
Hi Sylvain, On Donnerstag, 4. September 2014, Sylvain Rabot wrote: I thought squeeze has became LTS ? yes, it has. Anyway I'm obliged to install squeeze because the software stack I will use has not been ported and tested on wheezy yet. makes quite some sense to me too! :) cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: Bug#742109: Soft lookup during port scan and IPTables log enabled
severity 742109 important reassign 742109 src:linux # also see #742014 thanks On Mittwoch, 19. März 2014, daniel.gas...@basf.com wrote: Package: base Severity: critical -- System Information: Debian Release: 7.4 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/16 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Description: We received an soft lookup (CPU#0 stuck for 23s!) during a port scan with a total of 20K packets and IPtables log enabled (without limits!) Detailed information: [2294091.216227] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/0:0:15620] [2294091.223575] Modules linked in: xt_limit ipt_LOG xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack xt_owner iptable_filter ip_tables x_tables autofs4 binfmt_misc nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc loop coretemp crc32c_intel radeon ttm drm_kms_helper drm snd_pcm power_supply ghash_clmulni_intel aesni_intel aes_x86_64 psmouse i2c_algo_bit aes_generic iTCO_wdt joydev evdev snd_page_alloc i2c_core snd_timer snd i7core_edac processor hpilo edac_core soundcore iTCO_vendor_support hpwdt button container acpi_power_meter serio_raw pcspkr cryptd ext3 mbcache jbd dm_mod sr_mod cdrom usbhid hid ata_generic sd_mod sg crc_t10dif uhci_hcd ata_piix libata ehci_hcd usbcore usb_common bnx2 thermal hpsa thermal_sys scsi_mod [last unloaded: scsi_wait_scan] [2294091.223627] CPU 0 [2294091.223629] Modules linked in: xt_limit ipt_LOG xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack xt_owner iptable_filter ip_tables x_tables autofs4 binfmt_misc nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc loop coretemp crc32c_intel radeon ttm drm_kms_helper drm snd_pcm power_supply ghash_clmulni_intel aesni_intel aes_x86_64 psmouse i2c_algo_bit aes_generic iTCO_wdt joydev evdev snd_page_alloc i2c_core snd_timer snd i7core_edac processor hpilo edac_core soundcore iTCO_vendor_support hpwdt button container acpi_power_meter serio_raw pcspkr cryptd ext3 mbcache jbd dm_mod sr_mod cdrom usbhid hid ata_generic sd_mod sg crc_t10dif uhci_hcd ata_piix libata ehci_hcd usbcore usb_common bnx2 thermal hpsa thermal_sys scsi_mod [last unloaded: scsi_wait_scan] [2294091.223667] [2294091.223669] Pid: 15620, comm: kworker/0:0 Tainted: GW 3.2.0-4-amd64 #1 Debian 3.2.54-2 HP ProLiant DL380 G7 [2294091.223673] RIP: 0010:[81046d8a] [81046d8a] arch_local_irq_restore+0x2/0x8 [2294091.223681] RSP: 0018:88011fc039d0 EFLAGS: 0246 [2294091.223683] RAX: 81767f9c RBX: 8134fd89 RCX: 0303 [2294091.223685] RDX: 8b4e RSI: 0046 RDI: 0246 [2294091.223687] RBP: 00e9 R08: R09: 0040 [2294091.223689] R10: R11: R12: 88011fc03948 [2294091.223691] R13: 8135585e R14: 00e9 R15: 0001 [2294091.223693] FS: () GS:88011fc0() knlGS: [2294091.223696] CS: 0010 DS: ES: CR0: 8005003b [2294091.223698] CR2: 7f15868d9f28 CR3: 01605000 CR4: 06f0 [2294091.223700] DR0: DR1: DR2: [2294091.223702] DR3: DR6: 0ff0 DR7: 0400 [2294091.223704] Process kworker/0:0 (pid: 15620, threadinfo 880036cde000, task 8801195c01c0) [2294091.223706] Stack: [2294091.230919] 81047a17 88010011 88011fc039ff 325b00010001 [2294091.230924] 322e313930343932 00205d3132333130 88011b3fd280 88011fc03b1c [2294091.230928] a0437263 a0433470 2bf867fd 0004 [2294091.230932] Call Trace: [2294091.238219] IRQ [2294091.245177] [81047a17] ? vprintk+0x39e/0x3d9 [2294091.245184] [8134958b] ? printk+0x43/0x48 [2294091.245188] [a0436ac4] ? ipt_log_packet+0x1f7/0x22a [ipt_LOG] [2294091.245191] [a0436b36] ? log_tg+0x3f/0x49 [ipt_LOG] [2294091.245195] [a02810e5] ? ipt_do_table+0x4d7/0x556 [ip_tables] [2294091.245201] [a0424aca] ? nf_conntrack_in+0x53a/0x607 [nf_conntrack] [2294091.245206] [812b1945] ? nf_iterate+0x41/0x77 [2294091.245210] [812b7aa2] ? xfrm4_policy_check.constprop.10+0x4f/0x4f [2294091.245213] [812b19e3] ? nf_hook_slow+0x68/0x101 [2294091.245216] [812b7aa2] ? xfrm4_policy_check.constprop.10+0x4f/0x4f [2294091.245219] [812b7aa2] ? xfrm4_policy_check.constprop.10+0x4f/0x4f [2294091.245222] [812b7a39] ? NF_HOOK.constprop.9+0x3c/0x56 [2294091.245225] [812b7767] ? ip_rcv_finish+0x3b/0x2d1 [2294091.245230] [8128e58b] ? __netif_receive_skb+0x3fb/0x42d [2294091.245233] [8128ff15] ?
Re: Bug#741893: general: System unresponsive after large torrent download to btrfs
control: severity -1 normal control: reassign -1 src:linux # I believe it's btrfs to blame, but maybe it's transmission? thanks On Montag, 17. März 2014, Mike wrote: Package: general Severity: important Dear Maintainer, Downloading a large torrent (30GB, 1 files) using transmission-gtk onto a btrfs filesystem (mounted as the root filesystem) causes the system to become unresponsive after a very short period of time. Tried marking the torrent directory with the no-COW attribute before starting, but that made no difference. System had to be powered off to shut down. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash signature.asc Description: This is a digitally signed message part.
space Re: base: I receive CPU type error traps from the kernel from time to time and with alarmingly greater frequency when I try to start X11 using startx
reassign 737616 src:linux retitle 737616 sparc: CPU type error traps from the kernel from time to time and with alarmingly greater frequency when I try to start X11 using startx thanks On Dienstag, 4. Februar 2014, Paul Llanyod wrote: Package: base Severity: normal -- System Information: Debian Release: 7.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: sparc (sparc64) Kernel: Linux 3.2.0-4-sparc64 Locale: LANG=en_ZA.UTF-8, LC_CTYPE=en_ZA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash I receive the following error or trap from time to time on my server (a Sunblade 2000) which is running in headless mode. When I try to start the GUI using startx the error occurs so frequently that I cannot use the console screen. My hardware seems to be functioning perfectly - I have not succeeded in starting the GUI (which I would like to do). The error repeats for a while once it occurs and is shown below. If I type startx from the command line the error does not stop as readily and I have to reboot the machine to put it in a stable state. Jan 30 12:11:42 debian kernel: [ 952.957402] ERROR(0): Cheetah error trap taken afsr[0002005b] afar[6cfd2e90] TL1(0) Jan 30 12:11:42 debian kernel: [ 952.957956] ERROR(0): TPC[5d1e90] TNPC[5d1e94] O7[4c1c8c] TSTATE[11001601] Jan 30 12:11:42 debian kernel: [ 952.958380] ERROR(0): TPCU3copy_to_user+0x190/0x500 Jan 30 12:11:42 debian kernel: [ 952.958724] ERROR(0): M_SYND(0), E_SYND(5b) Jan 30 12:11:42 debian kernel: [ 952.959003] ERROR(0): Highest priority error (0002) HW corrected system bus data ECC error for read Jan 30 12:11:42 debian kernel: [ 952.959617] ERROR(0): AFAR E-syndrome [J0304, pin 19] Jan 30 12:11:42 debian kernel: [ 952.959946] ERROR(0): D-cache idx[ee90] tag[0006cc1f] utag[4f07] stag[0006cc1e] Jan 30 12:11:42 debian kernel: [ 952.960531] ERROR(0): D-cache data0[b646cadc1a96df61] data1[080204020042] data2[fc0e771fb5c70a95] data3[ff82ede4] Jan 30 12:11:42 debian kernel: [ 952.961204] ERROR(0): I-cache idx[0] tag[] utag[] stag[] u[] l[] Jan 30 12:11:42 debian kernel: [ 952.962387] ERROR(0): I-cache INSN0[] INSN1[] INSN2[] INSN3[] Jan 30 12:11:42 debian kernel: [ 952.963058] ERROR(0): I-cache INSN4[] INSN5[] INSN6[] INSN7[] Jan 30 12:11:42 debian kernel: [ 952.963727] ERROR(0): E-cache idx[6cfd2e80] tag[00e7] Jan 30 12:11:42 debian kernel: [ 952.964109] ERROR(0): E-cache data0[bca1876cc1e4352a] data1[67fe78d2554431b2] data2[091f48b54a9e7b15] data3[a596f28215531bba] Jan 30 12:11:42 debian kernel: [ 953.010971] ERROR(0): Cheetah error trap taken afsr[0002005b] afar[6cfeee90] TL1(0) Jan 30 12:11:42 debian kernel: [ 953.011524] ERROR(0): TPC[5d1e90] TNPC[5d1e94] O7[4c1c8c] TSTATE[11001601] Jan 30 12:11:42 debian kernel: [ 953.011948] ERROR(0): TPCU3copy_to_user+0x190/0x500 Jan 30 12:11:42 debian kernel: [ 953.012292] ERROR(0): M_SYND(0), E_SYND(5b) Jan 30 12:11:42 debian kernel: [ 953.012572] ERROR(0): Highest priority error (0002) HW corrected system bus data ECC error for read Jan 30 12:11:42 debian kernel: [ 953.013185] ERROR(0): AFAR E-syndrome [J0304, pin 19] Jan 30 12:11:42 debian kernel: [ 953.013514] ERROR(0): D-cache idx[ee90] tag[0006cc1f] utag[4f07] stag[0006cc1e] Jan 30 12:11:42 debian kernel: [ 953.014098] ERROR(0): D-cache data0[b646cadc1a96df61] data1[080204020042] data2[fc0e771fb5c70a95] data3[ff82ede4] Jan 30 12:11:42 debian kernel: [ 953.014772] ERROR(0): I-cache idx[0] tag[] utag[] stag[] u[] l[] Jan 30 12:11:42 debian kernel: [ 953.015953] ERROR(0): I-cache INSN0[] INSN1[] INSN2[] INSN3[] Jan 30 12:11:42 debian kernel: [ 953.016625] ERROR(0): I-cache INSN4[] INSN5[] INSN6[] INSN7[] Jan 30 12:11:42 debian kernel: [ 953.017294] ERROR(0): E-cache idx[6cfeee80] tag[0090] Jan 30 12:11:42 debian kernel: [ 953.017678] ERROR(0): E-cache data0[820461d8c4066008] data1[8728a002c2004003] data2[83286018c227bf58] data3[8338601880a06065] Jan 30 12:11:54 debian kernel: [ 964.663357] /pci@8,70: Correctable Error, primary error type[DMA Read] Jan 30 12:11:54 debian kernel: [ 964.664223] /pci@8,70: bytemask[] qword_offset[1] SAFARI_AID[08] Jan 30 12:11:54 debian kernel: [ 964.664648] /pci@8,70: partial[0] owned_in[0] mtag[0] mtag_synd[0] ecc_sync[5b] Jan 30 12:11:54 debian kernel: [ 964.665124] /pci@8,70: CE
Re: Bug#735196: base: TCP offloading of network interface can not be deactivaed
control: reassign -1 src:linux # I believe this is the kernels fault, but # I might be wrong... thanks On Montag, 13. Januar 2014, michael wrote: Package: base Severity: normal Tags: upstream Dear Maintainer, * What led up to the situation? Checksum calcualtion for outgoing tcp packages had been moved from the kernel to the network interface card (ethX or wlanX). Thus when capturing data with tcpdump / Wireshark/ pcap invalid checksums occur. Thus it is no longer possible to determine which packages had invalid checksums and will be discarded. Therefore TCP-offloading needs to be manually deactivated with ethtool. * What exactly did you do (or not do) that was effective (or ineffective)? I deactivated all netwark card features and thus expected the kernel to calculate the outgoing checksums: su ethtool -K eth0 rx off tx off sg off tso off gso off * What was the outcome of this action? All features are activated according ethtool: ethtool -k eth0 Features for eth0: rx-checksumming: off tx-checksumming: off tx-checksum-ipv4: off [fixed] tx-checksum-unneeded: off [fixed] tx-checksum-ip-generic: off tx-checksum-ipv6: off [fixed] tx-checksum-fcoe-crc: off [fixed] tx-checksum-sctp: off [fixed] scatter-gather: off tx-scatter-gather: off tx-scatter-gather-fraglist: off [fixed] tcp-segmentation-offload: off tx-tcp-segmentation: off tx-tcp-ecn-segmentation: off [fixed] tx-tcp6-segmentation: off udp-fragmentation-offload: off [fixed] generic-segmentation-offload: off generic-receive-offload: off large-receive-offload: off [fixed] rx-vlan-offload: on tx-vlan-offload: on ntuple-filters: off [fixed] receive-hashing: off [fixed] highdma: on [fixed] rx-vlan-filter: on [fixed] vlan-challenged: off [fixed] tx-lockless: off [fixed] netns-local: off [fixed] tx-gso-robust: off [fixed] tx-fcoe-segmentation: off [fixed] fcoe-mtu: off [fixed] tx-nocache-copy: on loopback: off [fixed] I entered: wget www.heise.de While tracking the traffic with tcpdump (see incorrect for checksums of traffic in outgoing direction (Donald.fritz.box.43681 redirector.heise.de): tcpdump -i eth0 -vvv tcp tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes 18:57:13.399866 IP (tos 0x0, ttl 64, id 50216, offset 0, flags [DF], proto TCP (6), length 60) Donald.fritz.box.43681 redirector.heise.de.http: Flags [S], cksum 0xc4a8 (incorrect - 0x573c), seq 2174976360, win 14600, options [mss 1460,sackOK,TS val 345408 ecr 0,nop,wscale 6], length 0 18:57:13.413922 IP (tos 0x0, ttl 245, id 15109, offset 0, flags [DF], proto TCP (6), length 60) redirector.heise.de.http Donald.fritz.box.43681: Flags [S.], cksum 0x6a7a (correct), seq 3901327278, ack 2174976361, win 4356, options [mss 1452,nop,nop,TS val 2361400012 ecr 345408,sackOK,eol], length 0 18:57:13.413989 IP (tos 0x0, ttl 64, id 50217, offset 0, flags [DF], proto TCP (6), length 52) Donald.fritz.box.43681 redirector.heise.de.http: Flags [.], cksum 0xc4a0 (incorrect - 0x6e2d), seq 1, ack 1, win 14600, options [nop,nop,TS val 345412 ecr 2361400012], length 0 18:57:13.414200 IP (tos 0x0, ttl 64, id 50218, offset 0, flags [DF], proto TCP (6), length 160) Donald.fritz.box.43681 redirector.heise.de.http: Flags [P.], cksum 0x03dd (correct), seq 1:109, ack 1, win 14600, options [nop,nop,TS val 345412 ecr 2361400012], length 108 18:57:13.434350 IP (tos 0x0, ttl 245, id 15510, offset 0, flags [DF], proto TCP (6), length 544) redirector.heise.de.http Donald.fritz.box.43681: Flags [P.], cksum 0x7e69 (correct), seq 1:493, ack 109, win 4464, options [nop,nop,TS val 2361400030 ecr 345412], length 492 18:57:13.434438 IP (tos 0x0, ttl 64, id 50219, offset 0, flags [DF], proto TCP (6), length 52) Donald.fritz.box.43681 redirector.heise.de.http: Flags [.], cksum 0xc4a0 (incorrect - 0x680e), seq 109, ack 493, win 15544, options [nop,nop,TS val 345417 ecr 2361400030], length 0 18:57:13.434456 IP (tos 0x0, ttl 245, id 15512, offset 0, flags [DF], proto TCP (6), length 52) redirector.heise.de.http Donald.fritz.box.43681: Flags [F.], cksum 0x935a (correct), seq 493, ack 109, win 4464, options [nop,nop,TS val 2361400030 ecr 345412], length 0 18:57:13.434716 IP (tos 0x0, ttl 64, id 50220, offset 0, flags [DF], proto TCP (6), length 52) Donald.fritz.box.43681 redirector.heise.de.http: Flags [R.], cksum 0xc4a0 (incorrect - 0x6809), seq 109, ack 494, win 15544, options [nop,nop,TS val 345417 ecr 2361400030], length 0 18:57:13.436862 IP (tos 0x0, ttl 64, id 57218, offset 0, flags [DF], proto TCP (6), length 60) Donald.fritz.box.51718 www.heise.de.http: Flags [S], cksum 0xc4ad (incorrect - 0x4e36), seq 1372822219, win 14600, options [mss 1460,sackOK,TS val 345417 ecr 0,nop,wscale 6], length 0 18:57:13.452346 IP (tos 0x0,
Re: Bug#733651: general: Any USB card reader works only after being replugged.
severity 733651 important reassign 733651 src:linux thanks On Montag, 30. Dezember 2013, Miroslav Scaldov wrote: Package: general Severity: grave Justification: renders package unusable Dear Maintainer, *** Please consider answering these questions, where appropriate *** After system reboot or replugging USB card reader into USB slot, the SD or MMC or Memory Stick card appears in /dev/disks/by-id, say as /dev/sde, and in Nautilus panel. After unmounting it from Nautilus or from command line it disappears as it should. But if memory card is pulled out and inserted again, it does not appear again in Nautilus and dmesg shows no reaction. At the same time the device /dev/sde still exists, even if memory card is absent. If I issue fdisk -l /dev/sde with inserted card, it appears in Nautilus and in dmesg: [ 4713.404064] sd 6:0:0:0: [sde] 62666752 512-byte logical blocks: (32.0 GB/29.8 GiB) [ 4713.405183] sd 6:0:0:0: [sde] No Caching mode page found [ 4713.405191] sd 6:0:0:0: [sde] Assuming drive cache: write through [ 4713.407902] sd 6:0:0:0: [sde] No Caching mode page found [ 4713.407911] sd 6:0:0:0: [sde] Assuming drive cache: write through [ 4713.409345] sde: sde1 [ 4713.821575] EXT4-fs (sde1): recovery complete [ 4713.824733] EXT4-fs (sde1): mounted filesystem with ordered data mode. Opts: (null) If I unplug the mamory card, dmesg says: [ 4779.180564] sde: detected capacity change from 32085377024 to 0 This behaviour began in september 2013 as far as I remember. It was annoying, I thought my card reader was broken and I replaced it, but problem still remained. So it is a bug. Affects cryptdisks as the key is stored on SD card. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (630, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.12-1-amd64 (SMP w/6 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/201401030316.13353.hol...@layer-acht.org
Re: Bug#724672: base: Fails to auto-detect the need for the kernel module `asus-nb-wmi'
control: reassign -1 src:linux On Donnerstag, 26. September 2013, Diogo F. S. Ramos wrote: Package: base Severity: wishlist Dear Maintainer, Out of the box, the keyboard fn keys of an ASUS N46V laptop don't fully work. For them to work properly, I added the kernel module `asus-nb-wmi' to the file `/etc/modules'. Would it be possible to add some kind of auto-detection for this? -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.10-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash signature.asc Description: This is a digitally signed message part.
reassigning to sysvinit
control: reassign -1 src:linux control: tags -1 + moreinfo unreproducible Hi, Oliver, can you confirm this only happens on systems with bluetooth hardware enabled? Can you install a kernel from sid and see if its fixed there? cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#729707: reassigning
control: reassign -1 xserver-xorg-video-nouveau thanks This is a wild guess. Please support cleaning up bugs against the base system. This is clearly no base bug... Thanks. signature.asc Description: This is a digitally signed message part.
717215: wrong udp checksum with virtio: workaround and patch
merge 717215 717217 thanks Hi, so this bug is caused by the virtio driver not populating the UDP checksum and thus dhcpd complains about this, see https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/930962 for more background and a patch for dhcpd. From a user perspective the workaround is easy: use a different NIC driver, ie e1000 works with kvm. I wonder whether one of the two bugs should be reassigned to the kernel, as the root cause is in virtio and not dhcpd. Thanks to Daniel Swarbrick for making me aware of this issue. cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: Bug#721635: [kernel-package] error on shutdown
control: reassign -1 src:linux On Dienstag, 3. September 2013, Marco Righi wrote: The problem are born after apt-get dist-upgrade to the last kernel uname -a Linux gaia 3.10-2-amd64 #1 SMP Debian 3.10.7-1 (2013-08-17) x86_64 GNU/Linux It's a standard kernel. thanks for info, reassigning accordingly. cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: Bug#721316: base: NETDEV WATCHDOG: eth0 (igb): transmit queue 0 timed out
severity 721316 important reassign 721316 src:linux thanks On Freitag, 30. August 2013, Anton Pomozov wrote: Package: base Severity: critical Justification: breaks the whole system * What led up to the situation? Nothing special, unexpected fail network subsystem * What exactly did you do (or not do) that was effective (or ineffective)? I did nothing, my server works as a virtual hypervisor server. * What was the outcome of this action? One of two network interface has stopped working. Second one continues to work. servicve networking restart, ifconfig down/up, ip link, ifdown/ifup - nothing helped. * What outcome did you expect instead? I expected my server continues to run. -- System Information: Debian Release: 7.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-23-pve (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash error log: # grep 16:07 /var/log/messages Aug 29 16:07:33 proxve kernel: [ cut here ] Aug 29 16:07:33 proxve kernel: WARNING: at net/sched/sch_generic.c:267 dev_watchdog+0x28a/0x2a0() (Not tainted) Aug 29 16:07:33 proxve kernel: Hardware name: X9SRE/X9SRE-3F/X9SRi/X9SRi-3F Aug 29 16:07:33 proxve kernel: NETDEV WATCHDOG: eth0 (igb): transmit queue 0 timed out Aug 29 16:07:33 proxve kernel: Modules linked in: vzethdev vznetdev pio_nfs pio_direct pfmt_raw pfmt_ploop1 ploop simfs vzrst nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 vzcpt nf_conntrack vzdquota vzmon vzdev ip6t_REJECT ip6table_mangle ip6table_filter ip6_tables xt_length xt_hl xt_tcpmss xt_TCPMSS iptable_mangle iptable_filter xt_multiport xt_limit vhost_net tun macvtap xt_dscp macvlan ipt_REJECT kvm_intel ip_tables kvm fuse vzevent ib_iser rdma_cm ib_addr iw_cm ib_cm ib_sa ib_mad ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc ipv6 snd_pcsp snd_pcm snd_page_alloc sb_edac snd_timer snd serio_raw ioatdma iTCO_wdt i2c_i801 edac_core shpchp soundcore iTCO_vendor_support wmi acpi_pad ext3 mbcache jbd sg isci igb i2c_algo_bit i2c_core dca libsas scsi_transport_sas ahci [last unloaded: scsi_wait_scan] Aug 29 16:07:33 proxve kernel: Pid: 3785, comm: kvm veid: 0 Not tainted 2.6.32-22-pve #1 Aug 29 16:07:33 proxve kernel: Call Trace: Aug 29 16:07:33 proxve kernel: IRQ [8106f5a7] ? warn_slowpath_common+0x87/0xe0 Aug 29 16:07:33 proxve kernel: [8106f6b6] ? warn_slowpath_fmt+0x46/0x50 Aug 29 16:07:33 proxve kernel: [81489b8a] ? dev_watchdog+0x28a/0x2a0 Aug 29 16:07:33 proxve kernel: [8105aa4a] ? update_curr+0xba/0x160 Aug 29 16:07:33 proxve kernel: [81489900] ? dev_watchdog+0x0/0x2a0 Aug 29 16:07:33 proxve kernel: [81083b26] ? run_timer_softirq+0x176/0x370 Aug 29 16:07:33 proxve kernel: [81033655] ? native_apic_msr_write+0x35/0x40 Aug 29 16:07:33 proxve kernel: [8107930b] ? __do_softirq+0x11b/0x260 Aug 29 16:07:33 proxve kernel: [810abfb5] ? tick_dev_program_event+0x65/0xc0 Aug 29 16:07:33 proxve kernel: [810ac03a] ? tick_program_event+0x2a/0x30 Aug 29 16:07:33 proxve kernel: [8100c32c] ? call_softirq+0x1c/0x30 Aug 29 16:07:33 proxve kernel: [8100de95] ? do_softirq+0x75/0xb0 Aug 29 16:07:33 proxve kernel: [810795e5] ? irq_exit+0xc5/0xd0 Aug 29 16:07:33 proxve kernel: [815492c0] ? smp_apic_timer_interrupt+0x70/0x9b Aug 29 16:07:33 proxve kernel: [8100bcd3] ? apic_timer_interrupt+0x13/0x20 Aug 29 16:07:33 proxve kernel: EOI [a04783d7] ? kvm_arch_vcpu_ioctl_run+0x387/0xfd0 [kvm] Aug 29 16:07:33 proxve kernel: [a04783cb] ? kvm_arch_vcpu_ioctl_run+0x37b/0xfd0 [kvm] Aug 29 16:07:33 proxve kernel: [81064430] ? wake_up_state+0x10/0x20 Aug 29 16:07:33 proxve kernel: [810b9e6a] ? wake_futex+0x6a/0x90 Aug 29 16:07:33 proxve kernel: [810ba08a] ? futex_wake+0x10a/0x130 Aug 29 16:07:33 proxve kernel: [a045f8e3] ? kvm_vcpu_ioctl+0x2e3/0x580 [kvm] Aug 29 16:07:33 proxve kernel: [810bc469] ? do_futex+0x159/0xb10 Aug 29 16:07:33 proxve kernel: [8104f02f] ? __dequeue_entity+0x2f/0x50 Aug 29 16:07:33 proxve kernel: [811b352a] ? vfs_ioctl+0x2a/0xa0 Aug 29 16:07:33 proxve kernel: [811b3b5e] ? do_vfs_ioctl+0x7e/0x570 Aug 29 16:07:33 proxve kernel: [81012899] ? read_tsc+0x9/0x20 Aug 29 16:07:33 proxve kernel: [810a5563] ? ktime_get_ts+0xb3/0xf0 Aug 29 16:07:33 proxve kernel: [811b409f] ? sys_ioctl+0x4f/0x80 Aug 29 16:07:33 proxve kernel: [8109a509] ? sys_clock_gettime+0x69/0xa0 Aug 29 16:07:33 proxve kernel: [8100b182] ? system_call_fastpath+0x16/0x1b Aug 29 16:07:33 proxve kernel: ---[ end trace 3b2ef6752edd7cb1 ]--- # lspci 00:00.0 Host bridge: Intel Corporation Xeon E5/Core i7
Re: Bug#721310: installation-report: Wheezy + Testing setup on FSC Futro S450 w/ dualcore-CPU
reassign 721310 src:linux severity 721310 wishlist retitle 721310 please enable ACPI_INITRD_TABLE_OVERRIDE # waldi | h01ger: no. this is a firmware bug, which may be possible to # workaround with acpi table overrides # h01ger | waldi: so which package is providing that firmware? firmware- # linux? # jcristau | h01ger: the hardware thanks Hi Andreas, thanks for your installation-report, much appreciated! On Freitag, 30. August 2013, Andreas Glaeser wrote: [...] When the original CPU was replaced by an AMD Turion 64 TL-50, I found that this is not running in a stable manner and used up more energy than reasonable, because there were complaints at boot-time about missing ACPI-tables in the BIOS for Powernow-K8 frequency-scaling. So I built a kernel version with frequency-scaling disabled, that runs OK, so far, now in the second version already on an even newer Turion 64 TL-58 CPU. The upside of this is that the wattage is still very low, at a maximum of about 23 W. The downside is that the CPU runs at its minimum frequency, which results in unattractive latencies and low performance. When I configure the new 3.10 kernel-sources, I saw that there is an option to inject ACPI-tables from the initrd into the kernel instead of fetching them from the BIOS. So this is probably the way to unlock the CPU-potential with this thin-client hardware. The wattage will be about 10 W higher then, the CPU-speed should double at least and extra active cooling will be necessary. At this time I did not check yet, where to get those ACPI-tables from. I guess one could try to read them out of socket S1 notebook BIOSes, or get them directly from the technical specification from AMD. There was no further research about this yet. The following data show the system with the TL-50 CPU, that was present at installation-time. Current dmesg-output with newer kernel- and CPU-version is also attached. cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: Bug#721097: base: boot of encrypted LVM with USB inserted, passphrase is not recognized. removing USB stick solves problem.
reassign 721097 initramfs-tools thanks On Mittwoch, 28. August 2013, wim wrote: Package: base Severity: minor Dear Maintainer, * What led up to the situation? boot of system with USB stick present. * What exactly did you do (or not do) that was effective (or ineffective)? remove USB stick * What was the outcome of this action? after USB stick was removed, rebooted normally without problems -- System Information: Debian Release: 7.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash signature.asc Description: This is a digitally signed message part.
Re: Bug#720898: netinst cd on Haswell: No ethernet card detected
reassign 720898 src:linux thanks On Montag, 26. August 2013, Harald Dunkel wrote: Package: debian-installer Version: 20130613 Trying the Stable debian-installer on a Haswell PC (Intel DH87MC) I got no network connection. d-i said: No ethernet card detected Manually choosing the e1000 or e1000e did not help. Since Testing/Unstable is not an option in this case, this is a serious problem. Without network its _highly_ difficult to install the backports kernel. For the netinst CD this failure is fatal. I would suggest to improve compatibility to Haswell in d-i for Stable. Of course I understand that Haswell is still very new, but Wheezy is supposed to last for yet another year. Many thanx. Keep on your good work. Harri signature.asc Description: This is a digitally signed message part.
Re: Bug#720316: upgrade-reports: dist-upgrade form wheezy to jessie, kernel upgrade caused USB Logitech Opt Mouse to freeze
reassign 720316 src:linux thanks On Dienstag, 20. August 2013, Firefly wrote: Package: upgrade-reports Severity: normal Dear Maintainer, Lenovo 446226 notebook After dist-upgrade from wheezy to jessie. linux-image-3.2.0-4-686-pae was upgraded first to 3.9-1-686-pae then to 3.10-2-686-pae After upgrade and booting newer kernel image USB Logitech Optical Mouse freezes after a few movements. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=en_ZA.UTF-8, LC_CTYPE=en_ZA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Problem encountered only a Lenovo Box therefore posssibly either module or firmware related. Rolling back to linux-image-3.2.0-4-686-pae restored USB Mouse functionality. signature.asc Description: This is a digitally signed message part.
Re: Bug#718518: base: fails to mount vfat filesystem.
control: reassign -1 src:linux On Freitag, 2. August 2013, atar wrote: Package: base Severity: important When using Debian on a USB stick with the kive-boot project, after upgrading the kernel to version number: 2.6.32-5-686, the system isn't able to mount a vfat filesystem anymore. dmesg report the foolowing: vfat: Unknown symbol utf8s_to_utf16s_fixed -- System Information: Debian Release: 6.0.7 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (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 signature.asc Description: This is a digitally signed message part.
Bug#595124: workaround and more info about resume troubles on ATI Radeon RV250
Hi Moritz, On Montag, 22. Juli 2013, Moritz Muehlenhoff wrote: This fix was merged into 3.2.35 and is thus part of the Wheezy kernel. Can either of you confirm that it's working now? not right now, that machine is currently still running Squeeze and I don't see me upgrading it before September I guess... cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: Bug#715211: base: Problem with ethernet realtek driver r8169
reassign 715211 src:linux severity 715211 important thanks On Sonntag, 7. Juli 2013, kjabbe wrote: Package: base Severity: critical Justification: breaks the whole system Dear Maintainer, I have a problem with the realtek driver r8169. When upgrading to wheezy, and installing booting into kernel 3.2.0-4 i can not get a ethernet connection. Neither static or dhcp. Please se the dmsg: [7.810474] r8169 :05:00.0: eth0: link up [7.814064] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 18.600078] eth0: no IPv6 routers present [ 79.792029] [ cut here ] [ 79.792042] WARNING: at /build/linux-s5x2oE/linux-3.2.46/net/sched/sch_generic.c:256 dev_watchdog+0xf2/0x151() [ 79.792047] Hardware name: To be filled by O.E.M. [ 79.792050] NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out [ 79.792054] Modules linked in: nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc ext2 loop firewire_sbp2 snd_hda_codec_hdmi snd_hda_codec_realtek powernow_k8 mperf crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 aes_generic cryptd evdev nouveau fam15h_power pcspkr k10temp amd64_edac_mod edac_mce_amd edac_core mxm_wmi snd_hda_intel video snd_hda_codec sp5100_tco ttm i2c_piix4 snd_hwdep drm_kms_helper snd_pcm drm snd_page_alloc snd_timer power_supply snd i2c_algo_bit i2c_core soundcore wmi button processor thermal_sys ext4 crc16 jbd2 mbcache microcode ata_generic sg sd_mod crc_t10dif pata_atiixp ohci_hcd ahci libahci firewire_ohci libata r8169 mii scsi_mod firewire_core crc_itu_t ehci_hcd xhci_hcd usbcore usb_common [last unloaded: scsi_wait_scan] [ 79.792136] Pid: 0, comm: swapper/3 Not tainted 3.2.0-4-amd64 #1 Debian 3.2.46-1 [ 79.792139] Call Trace: [ 79.792142] IRQ [81046b75] ? warn_slowpath_common+0x78/0x8c [ 79.792156] [81046c21] ? warn_slowpath_fmt+0x45/0x4a [ 79.792163] [812a68c9] ? netif_tx_lock+0x40/0x75 [ 79.792173] [812a6a39] ? dev_watchdog+0xf2/0x151 [ 79.792179] [81052334] ? run_timer_softirq+0x19a/0x261 [ 79.792185] [812a6947] ? netif_tx_unlock+0x49/0x49 [ 79.792193] [810660a1] ? timekeeping_get_ns+0xd/0x2a [ 79.792199] [8104c1ac] ? __do_softirq+0xb9/0x177 [ 79.792205] [81355dac] ? call_softirq+0x1c/0x30 [ 79.792212] [8100f8cd] ? do_softirq+0x3c/0x7b [ 79.792217] [8104c414] ? irq_exit+0x3c/0x99 [ 79.792224] [810241c0] ? smp_apic_timer_interrupt+0x74/0x82 [ 79.792229] [8135461e] ? apic_timer_interrupt+0x6e/0x80 [ 79.792232] EOI [81023e88] ? lapic_next_event+0xe/0x13 [ 79.792243] [8102b36c] ? native_safe_halt+0x2/0x3 [ 79.792255] [a00cbc51] ? acpi_safe_halt+0x21/0x39 [processor] [ 79.792265] [a00cc0bd] ? acpi_idle_enter_c1+0x57/0xb3 [processor] [ 79.792276] [8126f91d] ? cpuidle_idle_call+0xec/0x179 [ 79.792282] [8100d243] ? cpu_idle+0xa5/0xf2 [ 79.792288] [81340cfe] ? start_secondary+0x1d5/0x1db [ 79.792292] ---[ end trace acd0b9ff985878ee ]--- [ 79.808603] r8169 :05:00.0: eth0: link up [ 151.808610] r8169 :05:00.0: eth0: link up [ 217.808622] r8169 :05:00.0: eth0: link up I have another system, running the same, CPU, debian version, kernel, and motherboard. Only difference i can find is in a newer version of BIOS. Best regards Jon-Anders Kabbe -- System Information: Debian Release: 7.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash signature.asc Description: This is a digitally signed message part.
Re: RFH: two base wheezy bugs
reassign 708158 src:linux
thanks
Hi,
On Sonntag, 16. Juni 2013, Andrei POPESCU wrote:
#708158
The submitter has posted a workaround ('options drm_kms_helper poll=N'
in a file under /etc/modprobe.d/). Reassign to src:linux?
right, thanks, Andrei!
On Montag, 17. Juni 2013, Neil McGovern wrote:
I'm at loss with what to do with #710047. (random freeze since wheezy)
For info, I'm also experiencing this. I'm having quite a bit of trouble
tracking it down, though I *suspect* at the moment it may have something
to do with the Intel graphics drivers on Thinkpads.
Leave that one with me, I'll try and triage and reassign as appropriate.
ok, thanks, Neil!
cheers,
Holger
signature.asc
Description: This is a digitally signed message part.
Re: Bug#710686: base: Wireless card stops working out of nothing.
Hi Ben, On Sonntag, 16. Juni 2013, Ben Hutchings wrote: sorry, I missed the usual disclaimer: sorry for just reassigning this bug, but I guess the atheros firmare maintainers know better how to deal with this bug But how do you know this is a firmware bug, not a driver bug? You don't. How would we fix a bug in sourceless firmware? We can't. How do we contact the upstream developers? We have no idea who they are, really. Our only contact is through the driver developers. So if you have a bug that might be in firmware or a driver it should always be assigned first to the driver (i.e. src:linux). Ok, thanks for explaining. I was (somehow foolishly) under the assumption that you don't really like unclear bug reports reassigned from src:base... Now I see how this is foolish, if you don't like to deal with bug reports you probably wouldnt (be able to) maintain src:linux ;-) Thanks for all your work btw, reading the wheezy 7.1 kernel changelog was quite impressive! cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: Bug#710686: base: Wireless card stops working out of nothing.
reassign 710686 firmware-atheros thanks On Samstag, 1. Juni 2013, Ygor Rodrigues Lhano wrote: Package: base Severity: normal Dear Maintainer, The wireless card simply stops working. Trying to activate it from the network manager gives the hardware disabled message. When it happens, restarting is the only option I found so far. Already tried to set the device up with ifconfig, and it returns a error about RFkill. Installed RFkill and it shows the card hard blocked. Trying to unblock with rfkill is useless, and the physical swich can only disable the card (pressing it once turns it off when is working, but never turns it on again) The card, listed with lspci is described as: Ethernet controller: Atheros Communications Inc. AR242x / AR542x Wireless Network Adapter (PCI-Express) I'm using a Acer Aspire One D250, with the standard buit-in wireless card. It used to work fine on squeeze. sorry for any inconvenience -- System Information: Debian Release: jessie/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash signature.asc Description: This is a digitally signed message part.
Re: Bug#710686: base: Wireless card stops working out of nothing.
Hi Ben, On Sonntag, 16. Juni 2013, Ben Hutchings wrote: On Sun, 2013-06-16 at 09:44 +0200, Holger Levsen wrote: reassign 710686 firmware-atheros How wid you decide that? sorry, I missed the usual disclaimer: sorry for just reassigning this bug, but I guess the atheros firmare maintainers know better how to deal with this bug cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: Bug#709176: base: kernel panic with swapper when interface flaps
reassign 709176 src:linux thanks On Dienstag, 21. Mai 2013, Daniel Petre wrote: Package: base Severity: critical Justification: breaks the whole system Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? debian squeeze box up-to-date but running kernel 3.8.13 with e1000e and tg3 interfaces with few gre tunnels and dual stack. * What exactly did you do (or not do) that was effective (or ineffective)? flapping a intel or broadcom nic will result in kernel panic * What was the outcome of this action? kernel panic with swapper (found by crash inspection on the vmcore) * What outcome did you expect instead? kernel should not be affected by the interface down/up.. -- System Information: Debian Release: 7.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash *** /home/dani/documents/kernel_panic.txt dani@crunchbang:~$ crash-7.0.0/crash s vmlinux vmcore.201305211445 crash sys KERNEL: vmlinux DUMPFILE: vmcore.201305211445 CPUS: 2 DATE: Tue May 21 14:45:16 2013 UPTIME: 00:31:25 LOAD AVERAGE: 0.00, 0.01, 0.05 TASKS: 105 NODENAME: server RELEASE: 3.8.13 VERSION: #3 SMP Mon May 20 13:09:05 EEST 2013 MACHINE: x86_64 (3000 Mhz) MEMORY: 1 GB PANIC: Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: 814d5fec crash bt PID: 0 TASK: 88003e06b8e0 CPU: 1 COMMAND: swapper/1 #0 [88003fd03798] machine_kexec at 81027430 #1 [88003fd037e8] crash_kexec at 8107da80 #2 [88003fd038b8] panic at 81540026 #3 [88003fd03938] __stack_chk_fail at 81037f77 #4 [88003fd03948] icmp_send at 814d5fec #5 [88003fd03b78] dev_hard_start_xmit at 8146e032 #6 [88003fd03bc8] sch_direct_xmit at 81487d66 #7 [88003fd03c08] __qdisc_run at 81487efd #8 [88003fd03c48] dev_queue_xmit at 8146e5a7 #9 [88003fd03c88] ip_finish_output at 814ab596 #10 [88003fd03ce8] __netif_receive_skb at 8146ed13 #11 [88003fd03d88] napi_gro_receive at 8146fc50 #12 [88003fd03da8] e1000_clean_rx_irq at 813bc67b #13 [88003fd03e48] e1000e_poll at 813c3a20 #14 [88003fd03e98] net_rx_action at 8146f796 #15 [88003fd03ee8] __do_softirq at 8103ebb9 #16 [88003fd03f38] call_softirq at 815c #17 [88003fd03f50] do_softirq at 810047dd #18 [88003fd03f80] do_IRQ at 81003f6c -- IRQ stack --- #19 [88003e097e58] ret_from_intr at 81542c2a [exception RIP: mwait_idle+95] RIP: 8100ad8f RSP: 88003e097f00 RFLAGS: 0246 RAX: RBX: 8154194e RCX: RDX: RSI: 88003e097fd8 RDI: 88003fd0d840 RBP: 8185be80 R8: R9: 0001 R10: R11: R12: R13: 88003e06b8e0 R14: 88003fd11000 R15: 88003e06b8e0 ORIG_RAX: ff1e CS: 0010 SS: 0018 #20 [88003e097f00] cpu_idle at 8100b126 crash signature.asc Description: This is a digitally signed message part.
Bug#706603: general: laptop freeze on adjusting brightness
Hi Jonathan, On Samstag, 4. Mai 2013, Jonathan Nieder wrote: Retitling to be more precise and reopening. thanks for doing so! cheers, Holger, sometimes to roughly gate-keeping... signature.asc Description: This is a digitally signed message part.
Re: Bug#706603: general: laptop freeze on adjusting brightness
tags 706603 + moreinfo reassign 706603 src:linux thanks Hi giri, we'll need more information on your machine: please send the output of dmesg lspci -nn lspci -v to this bug report. Also maybe mentioning the laptop name+model could help. On Donnerstag, 2. Mai 2013, giri wrote: Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? while adjusting screen brightness * What exactly did you do (or not do) that was effective (or ineffective)? used laptop dedicated buttons to adjust screen brightness * What was the outcome of this action? system freeze * What outcome did you expect instead? screen brightness to be adjusted without problems *** End of the template - remove these lines *** -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash cheers, Holger P.S.: there is a reportbug command to do this, but it's not mentioned on http://wiki.debian.org/DebianKernelReportingBugs signature.asc Description: This is a digitally signed message part.
Bug#706603: general: laptop freeze on adjusting brightness
Hi Giri, please mail 706...@bugs.debian.org when replying to this bug. On Donnerstag, 2. Mai 2013, Giri wrote: I am attaching the files u have requested. thanks! Also I am making changes /etc/default/grub as mentioned above to see if it gets fixed. and? Whats the result? Also must say thank u so much for the prompt replies guys. :-) likewise thanks for your prompt feedback! cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: Bug#703748: base: kobject_add_internal failed for threshold_bank0 with -EEXIST
reassign 703748 src:linux thanks On Samstag, 23. März 2013, Le Déchaîné wrote: Package: base Severity: normal I've installed Debian Squeeze one week ago (installed from CD on a new computer), and everytime I boot my system, I see these errors. Looks serious, but doesn't seem to affect my computer at all, since booting continues afterwards. [0.508968] Unpacking initramfs... [0.680304] Freeing initrd memory: 8584k freed [0.682379] Simple Boot Flag at 0x47 set to 0x1 [0.682643] [ cut here ] [0.682649] WARNING: at /build/buildd- linux-2.6_2.6.32-48squeeze1-i386-F95osd/linux-2.6-2.6.32/debian/build/sourc e_i386_none/fs/sysfs/dir.c:491 sysfs_add_one+0xa3/0xb8() [0.682652] Hardware name: SX2380 [0.682653] sysfs: cannot create duplicate filename '/devices/system/machinecheck/machinecheck1/threshold_bank0' [0.682654] Modules linked in: [0.682657] Pid: 1, comm: swapper Not tainted 2.6.32-5-686-bigmem #1 [0.682662] Call Trace: [0.682667] [c1036af9] ? warn_slowpath_common+0x5e/0x8a [0.682669] [c1036b57] ? warn_slowpath_fmt+0x26/0x2a [0.682672] [c10fc355] ? sysfs_add_one+0xa3/0xb8 [0.682674] [c10fc7c5] ? create_dir+0x3c/0x62 [0.682677] [c10fc814] ? sysfs_create_dir+0x29/0x3b [0.682680] [c113ee04] ? kobject_get+0xf/0x13 [0.682683] [c113ef02] ? kobject_add_internal+0xb0/0x149 [0.682685] [c113f0ba] ? kobject_add+0x44/0x47 [0.682687] [c113f0dc] ? kobject_create_and_add+0x1f/0x48 [0.682691] [c127c8bc] ? threshold_create_bank+0x136/0x21c [0.682694] [c11a66e3] ? misc_register+0xb3/0xec [0.682697] [c13e9e48] ? threshold_init_device+0x34/0x70 [0.682699] [c13e9e14] ? threshold_init_device+0x0/0x70 [0.682702] [c1003056] ? do_one_initcall+0x55/0x155 [0.682705] [c13e22e1] ? kernel_init+0x11a/0x167 [0.682707] [c13e21c7] ? kernel_init+0x0/0x167 [0.682709] [c1008d87] ? kernel_thread_helper+0x7/0x10 [0.682714] ---[ end trace da4c522e662efdd0 ]--- [0.682717] kobject_add_internal failed for threshold_bank0 with -EEXIST, don't try to register things with the same name in the same directory. [0.682758] Pid: 1, comm: swapper Tainted: GW 2.6.32-5-686-bigmem #1 [0.682759] Call Trace: [0.682762] [c113ef8b] ? kobject_add_internal+0x139/0x149 [0.682764] [c113f0ba] ? kobject_add+0x44/0x47 [0.682767] [c113f0dc] ? kobject_create_and_add+0x1f/0x48 [0.682769] [c127c8bc] ? threshold_create_bank+0x136/0x21c [0.682771] [c11a66e3] ? misc_register+0xb3/0xec [0.682774] [c13e9e48] ? threshold_init_device+0x34/0x70 [0.682776] [c13e9e14] ? threshold_init_device+0x0/0x70 [0.682778] [c1003056] ? do_one_initcall+0x55/0x155 [0.682780] [c13e22e1] ? kernel_init+0x11a/0x167 [0.682782] [c13e21c7] ? kernel_init+0x0/0x167 [0.682784] [c1008d87] ? kernel_thread_helper+0x7/0x10 [0.682786] kobject_create_and_add: kobject_add error: -17 [0.682789] [ cut here ] [0.682792] WARNING: at /build/buildd- linux-2.6_2.6.32-48squeeze1-i386-F95osd/linux-2.6-2.6.32/debian/build/sourc e_i386_none/fs/sysfs/dir.c:491 sysfs_add_one+0xa3/0xb8() [0.682794] Hardware name: SX2380 [0.682795] sysfs: cannot create duplicate filename '/devices/system/machinecheck/machinecheck1/threshold_bank1' [0.682796] Modules linked in: [0.682798] Pid: 1, comm: swapper Tainted: GW 2.6.32-5-686-bigmem #1 [0.682799] Call Trace: [0.682801] [c1036af9] ? warn_slowpath_common+0x5e/0x8a [0.682804] [c1036b57] ? warn_slowpath_fmt+0x26/0x2a [0.682806] [c10fc355] ? sysfs_add_one+0xa3/0xb8 [0.682808] [c10fc7c5] ? create_dir+0x3c/0x62 [0.682810] [c10fc814] ? sysfs_create_dir+0x29/0x3b [0.682813] [c113ee04] ? kobject_get+0xf/0x13 [0.682815] [c113ef02] ? kobject_add_internal+0xb0/0x149 [0.682817] [c113f0ba] ? kobject_add+0x44/0x47 [0.682819] [c113f0dc] ? kobject_create_and_add+0x1f/0x48 [0.682822] [c127c8bc] ? threshold_create_bank+0x136/0x21c [0.682824] [c11a66e3] ? misc_register+0xb3/0xec [0.682826] [c13e9e48] ? threshold_init_device+0x34/0x70 [0.682828] [c13e9e14] ? threshold_init_device+0x0/0x70 [0.682830] [c1003056] ? do_one_initcall+0x55/0x155 [0.682832] [c13e22e1] ? kernel_init+0x11a/0x167 [0.682834] [c13e21c7] ? kernel_init+0x0/0x167 [0.682836] [c1008d87] ? kernel_thread_helper+0x7/0x10 [0.682837] ---[ end trace da4c522e662efdd1 ]--- [0.682839] kobject_add_internal failed for threshold_bank1 with -EEXIST, don't try to register things with the same name in the same directory. [0.682878] Pid: 1, comm: swapper Tainted: GW 2.6.32-5-686-bigmem #1 [0.682879] Call Trace: [0.682882] [c113ef8b] ? kobject_add_internal+0x139/0x149 [0.682884] [c113f0ba] ? kobject_add+0x44/0x47 [0.682886] [c113f0dc] ?
Re: Bug#703134: base: Screen brightness dim on a Dell XPS M1710; can't change it
reassign 703134 src:linux severity 703134 normal thanks On Freitag, 15. März 2013, Damien wrote: Package: base Severity: important Dear Maintainer, I've been unable to change the screen brightness today, on a Dell XPS M1710 laptop. It stays dim. When changing from a virtual terminal to X, the screen is bright briefly, but immediately dims again. During boot, the brightness is correct for Grub but dims during the boot process. If I use the brightness keys to set the brighness to the minimum value, the screen doesn't brighten when I change to the graphical desktop from a text console (ie. ctrl+alt+f1), but when I set it to maximum it becomes bright for about 1/4 second when I change to the graphical desktop. The brightness keys don't work, nor does writing to /sys/class/backlight/acpi_video0/backlight. I've only seen this today, so maybe it's related to these package updates: Start-Date: 2013-03-15 17:02:14 Upgrade: xserver-xorg-video-ati:amd64 (6.14.4-7, 6.14.4-8), gstreamer0.10-alsa:a md64 (0.10.36-1, 0.10.36-1.1), linux-image-3.2.0-4-amd64:amd64 (3.2.35-2, 3.2.39 -2), linux-headers-3.2.0-4-amd64:amd64 (3.2.35-2, 3.2.39-2), linux-headers-3.2.0 -4-common:amd64 (3.2.35-2, 3.2.39-2), libgstreamer-plugins-base0.10-0:amd64 (0.1 0.36-1, 0.10.36-1.1), linux-libc-dev:amd64 (3.2.35-2, 3.2.39-2), xserver-xorg-vi deo-radeon:amd64 (6.14.4-7, 6.14.4-8), gstreamer0.10-plugins-base:amd64 (0.10.36 -1, 0.10.36-1.1) End-Date: 2013-03-15 17:03:02 I don't know whether the brightness controls worked before as the screen was always bright enough. I think this is the relevant part of 'lshw': *-display description: VGA compatible controller product: G71 [GeForce Go 7950 GTX] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list rom configuration: driver=nouveau latency=0 resources: irq:16 memory:ed00-edff memory:d000-dfff memory:ee00-eeff ioport:ef00(size=128) memory:efe0-efe1 Let me know if you need any more information. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/201303160848.19886.hol...@layer-acht.org
Re: Bug#702132: unblock: linux/3.2.39-2
Hi, does this include Juliens 3.2.0-4.drm patches? cheers, Holger
Re: Bug#701511: base: At boot, the wrong b43 driver is loaded. I installed compat-drivers-3.7.6-1
reassign 701511 src:linux-2.6 severity 701511 normal thanks On Sonntag, 24. Februar 2013, tomdean wrote: Package: base Severity: important The b43 driver installed at boot does not work. I have included a work around. I installed the b43 driver from compat-drivers-3.7.6-1 and it works. After boot, I can manually unload the b43 driver and reload it then ifup wlan0 works. Doing this in rc.local does not work unless I add sleep's locate b43.ko /lib/modules/2.6.32-5-686/kernel/drivers/net/wireless/b43/b43.ko /lib/modules/2.6.32-5-686/updates/drivers/net/wireless/b43/b43.ko cat /etc/rc.local /sbin/modprobe -v -r b43 /sbin/modprobe -v b43 /sbin/ifup wlan0 Does not work. cat /etc/rc.local sleep 2 /sbin/modprobe -v -r b43 sleep 2 /sbin/modprobe -v b43 sleep 2 /sbin/ifup wlan0 does work. -- System Information: Debian Release: 6.0.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash
Re: Bug#693720: base: shutdown with hwclock --systohc cause battery to drain.
reassign 693720 src:linux forwarded 693720 https://bugzilla.kernel.org/show_bug.cgi?id=47811 thanks On Montag, 19. November 2012, François Boisson wrote: Package: base Severity: normal -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.5.4-fb-aufs (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Lorsqu'on arrête la machine avec l'option HWCLOCKACCESS non précisé ou mise à yes (c'est pareil), donc lorsque la machine effectue un english version below... hwclock --systohc juste avant de s'arrêter, la batterie perd sa charge. En fait la consommation est à peu près celle d'une mise en veille. Si on met l'option HWCLOCKACCESS=no (par exemple dans /etc/default/hwclock) alors cette perte de charge n'a plus lieu. Un «sleep 1» juste après le hwclock ne résoud pas le problème. Ce bug arrive avec les noyaux 3.0 - 3.5.4. À noter que ce bug n'a pas lieu sur une Ubuntu (il faudrait voir si cette option est par défaut sur Ubuntu). J'ai constaté la présence de ce bug sur tous les Toshiba et sur d'autres machines. Voir à ce sujet https://bugzilla.kernel.org/show_bug.cgi?id=47811 (je pensais ce bug lié au noyau auparavant). English: Halt the computer with HWCLOCKACCESS not set or set to yes causes battery to drain. (Consumption is about the same that when the computer is in sleep mode). If we put HWCLOCKACCESS=yes in /etc/default/hwclock, then battery doesn't drain off then. So doing hwclock --systohc before halt causes battery to drain. Put «sleep 1» after hwclock doesn't change anything. This happens on various computers but not with the Ubuntu distribution. Look at https://bugzilla.kernel.org/show_bug.cgi?id=47811 for the first bug report when I thought that it was an ACPI bug. (Now I think it's a kernel bug in the gestion of RTC but may be I'm wrong). Regards
Re: Bug#684306: base: insertion of SD card in existing card reader does not trigger any event
reassign 684306 src:linux reassign 679978 src:linux # please read the full bug reports.. thanks
Re: Bug#649597: /dev/disk/by-id incomplete with two exactly same USB disks
reassign 649597 src:linux thanks On Dienstag, 22. November 2011, Alain SAURAT wrote: Package: base Severity: normal I have connected two USB disk which are exactly indentical. The disks are Iomega 320Go and their ID is ST332082_0AS_5F542FFF The 1st have 4 partitions and the 2nd only one. cat /dev/disk/by-id only show a disk with 4 partitions : usb-ST332082_0AS_5F542FFF-0:0 usb-ST332082_0AS_5F542FFF-0:0-part1 usb-ST332082_0AS_5F542FFF-0:0-part2 usb-ST332082_0AS_5F542FFF-0:0-part3 usb-ST332082_0AS_5F542FFF-0:0-part4 But there is cross references: If I make dd if=/dev/disk/by-id/usb-ST332082_0AS_5F542FFF-0\:0 of=ggg count=1 I can see with hd ggg that this is the 2nd disk partition table and not the 1st. idem if I test with usb-ST332082_0AS_5F542FFF-0:0-part1, but with 2,3 and 4 this is really the parts of the 1st disk. So I suppose that during detection of the 1st disk, id are created correctly and when the 2nd is detected id are re-writen with the same name. system Infos: wheezy/sid on Marvell sheevaplug Linux SheevaDaily 3.0.0-1-kirkwood #1 Sun Aug 28 14:30:35 UTC 2011 armv5tel GNU/Linux -- System Information: Debian Release: squeeze/sid APT prefers lucid-updates APT policy: (500, 'lucid-updates'), (500, 'lucid-security'), (500, 'lucid-backports'), (500, 'lucid') Architecture: i386 (i686) Kernel: Linux 2.6.32-35-generic-pae (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/dash
Re: Bug#696686: base: Touchpad on Thinkpad T520 did not move pointer on resume from hibernate
reassign 696686 src:linux severity 696686 normal thanks On Dienstag, 25. Dezember 2012, Matthew Flaschen wrote: Package: base Severity: important Sorry I didn't specify a package. Being a hardware/hibernation problem, I wasn't sure where in the stack the issue was. I hibernated the laptop, and on resume, the touchpad does not allow me to move the pointer. Normally, both the touchpad and the nipple in the center of the keyboard work. Sometimes I also use a USB mouse, but I was not when I hibernated. On resume, I can still use the nipple, and I can scroll with the touchpad. However, moving my finger normally on the touchpad does not move the pointer. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash
missing ata-modules for d-i on efikamx: no disk found, also with wheezy Beta4
clone 675017 -1 reassign -1 src:linux tags -1 + patch retitle -1 missing ata-modules for d-i on efikamx, breaking d-i wheezy Beta4 -1 blocks 675017 thanks Hi, the fix seems to be easy: $ svn info|grep URL URL: svn://svn.debian.org/svn/kernel/dists/trunk/linux/debian/installer $ echo -e libata\npata_imx armhf/modules/armhf-mx5/ata-modules cheers, Holger -- 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/201301011757.37175.hol...@layer-acht.org
Bug#697128: missing ata-modules for d-i on efikamx: no disk found, also with wheezy Beta4
Hi, On Mittwoch, 2. Januar 2013, Ben Hutchings wrote: The NOR flash only contains u-boot and its configuration, not any filesystem. Do those need to be written during installation? I believe so, there is a bootscript which needs to be (re-)written, as it might not exist / exist only in different form from previous installs. cheers, Holger -- 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/201301020112.30441.hol...@layer-acht.org
Re: Bug#696662: base: rt2800pci_mcu_status no hardware response due to radio enabled to early
reassign 696662 firmware-ralink thanks On Dienstag, 25. Dezember 2012, skx wrote: Package: base Severity: important Tags: upstream Dear Maintainer, Wheezy with firmware-ralink packagesinstalled for network controller RT2790 Wireless 802.11n 1T/2R PCIe network controller results in a [ 26.104901] phy0 - rt2800pci_mcu_status: error - MCU request failed no response from hardware This is probably due to the radio being enables to early when the network controller did not yet wake up as it ralink network controller is confirmed working in the end. See also my issue described in more detail on the Debian forum including dmesg and lspci logs and a potential patch from an other distro which tackles similar issue. http://forums.debian.net/viewtopic.php?f=30t=90523 This warning/error only occurs during a cold boot. Rebooting does not result in same error message as network controller is already woken up. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (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 -- 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/201212251306.34189.hol...@layer-acht.org
Re: Bug#696662: base: rt2800pci_mcu_status no hardware response due to radio enabled to early
reassign 696662 linux thanks On Dienstag, 25. Dezember 2012, skx wrote: Package: base Severity: important Tags: upstream Dear Maintainer, Wheezy with firmware-ralink packagesinstalled for network controller RT2790 Wireless 802.11n 1T/2R PCIe network controller results in a [ 26.104901] phy0 - rt2800pci_mcu_status: error - MCU request failed no response from hardware This is probably due to the radio being enables to early when the network controller did not yet wake up as it ralink network controller is confirmed working in the end. See also my issue described in more detail on the Debian forum including dmesg and lspci logs and a potential patch from an other distro which tackles similar issue. http://forums.debian.net/viewtopic.php?f=30t=90523 This warning/error only occurs during a cold boot. Rebooting does not result in same error message as network controller is already woken up. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (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 -- 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/201212252148.18950.hol...@layer-acht.org
Bug#693227: missing driver for ISCI (Intel C600 SAS) (not iscsi!)
forcemerge 690886 693227 # On Mittwoch, 14. November 2012, Ben Hutchings wrote: # This was already reported as #690886 and the fix is pending. thanks -- 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/201211142024.39828.hol...@layer-acht.org
Re: Bug#689433: base: Problem with edid checksum at boot sequence
reassign 689433 linux thanks On Dienstag, 2. Oktober 2012, geoffbou wrote: Package: base Severity: normal Dear Maintainer, I've got this at boot : drm error edid checksum is invalid 255 this repeats 4 or 5 times The system is starting correctly but there is this problem before I didn't found the good answer on google. I've got an intel graphic card -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/201210021749.06079.hol...@layer-acht.org
Re: Bug#685200: base: ftdi_sio stop working after several hours
severity 685200 normal reassgin 685200 linux-2.6 thanks # the formatting aint broken in the original report... On Samstag, 18. August 2012, Mathieu MD wrote: Package: base Severity: grave Justification: renders package unusable I control a four relays board throught an USB cable connected to a Xen Dom0 running Debian 6.0.5. It works great: I can switch on and off the relays through some echo into /dev/ttyUSB0 (echo -e \xff\x01\x01 /dev/ttyUSB0). I added a crontab to send such echo every 15 minutes. It works great at the begining. But after some hours, I get this error message in /var/log/syslog each time I echo to ttyUSB0: #-8--8-- Aug 18 09:04:32 zen kernel: [1677762.865609] ftdi_sio ttyUSB0: Unable to write latency timer: -62 Aug 18 09:04:32 zen kernel: [1677762.869623] ftdi_sio ttyUSB0: ftdi_set_termios FAILED to set databits/stopbits/parity Aug 18 09:04:32 zen kernel: [1677762.871604] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate Aug 18 09:04:32 zen kernel: [1677762.875622] ftdi_sio ttyUSB0: urb failed to clear flow control Aug 18 09:04:32 zen kernel: [1677762.879604] ftdi_sio ttyUSB0: urb failed to clear flow control Aug 18 09:04:32 zen kernel: [1677762.881620] ftdi_sio ttyUSB0: error from flowcontrol urb Aug 18 09:04:32 zen kernel: [1677762.885623] ftdi_sio ttyUSB0: Unable to write latency timer: -62 Aug 18 09:04:32 zen kernel: [1677762.889637] ftdi_sio ttyUSB0: ftdi_set_termios FAILED to set databits/stopbits/parity Aug 18 09:04:32 zen kernel: [1677762.891622] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate Aug 18 09:04:32 zen kernel: [1677762.895616] ftdi_sio ttyUSB0: urb failed to clear flow control Aug 18 09:04:32 zen kernel: [1677762.903189] ftdi_sio ttyUSB0: error from flowcontrol urb #-8--8-- I have to unplug the USB cable and plug it back to get it to work again. Unplug: #-8--8-- Aug 18 09:04:46 zen kernel: [167.053078] usb 3-3: USB disconnect, address 17 Aug 18 09:04:46 zen kernel: [167.053233] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 Aug 18 09:04:46 zen kernel: [167.053248] ftdi_sio 3-3:1.0: device disconnected #-8--8-- Plug: #-8--8-- Aug 18 09:04:49 zen kernel: [169.816320] usb 3-3: new full speed USB device using ohci_hcd and address 18 Aug 18 09:04:49 zen kernel: [169.998248] usb 3-3: New USB device found, idVendor=0403, idProduct=6001 Aug 18 09:04:49 zen kernel: [169.998260] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Aug 18 09:04:49 zen kernel: [169.998270] usb 3-3: Product: FT232R USB UART Aug 18 09:04:49 zen kernel: [169.998278] usb 3-3: Manufacturer: FTDI Aug 18 09:04:49 zen kernel: [169.998284] usb 3-3: SerialNumber: AH01IAGC Aug 18 09:04:49 zen kernel: [1677780.006100] usb 3-3: configuration #1 chosen from 1 choice Aug 18 09:04:49 zen kernel: [1677780.013642] ftdi_sio 3-3:1.0: FTDI USB Serial Device converter detected Aug 18 09:04:49 zen kernel: [1677780.013712] usb 3-3: Detected FT232RL Aug 18 09:04:49 zen kernel: [1677780.013720] usb 3-3: Number of endpoints 2 Aug 18 09:04:49 zen kernel: [1677780.013728] usb 3-3: Endpoint 1 MaxPacketSize 64 Aug 18 09:04:49 zen kernel: [1677780.013736] usb 3-3: Endpoint 2 MaxPacketSize 64 Aug 18 09:04:49 zen kernel: [1677780.013744] usb 3-3: Setting MaxPacketSize 64 Aug 18 09:04:49 zen kernel: [1677780.015289] usb 3-3: FTDI USB Serial Device converter now attached to ttyUSB0 #-8--8-- The first times I echo to ttyUSB0 after plugin it, the log shows this: #-8--8-- Aug 18 09:09:36 zen kernel: [1678067.020400] hub 3-0:1.0: port 3 disabled by hub (EMI?), re-enabling... Aug 18 09:09:36 zen kernel: [1678067.020439] usb 3-3: USB disconnect, address 21 Aug 18 09:09:36 zen kernel: [1678067.020793] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 Aug 18 09:09:36 zen kernel: [1678067.020839] ftdi_sio 3-3:1.0: device disconnected Aug 18 09:09:37 zen kernel: [1678067.292977] usb 3-3: new full speed USB device using ohci_hcd and address 22 Aug 18 09:09:37 zen kernel: [1678067.477915] usb 3-3: New USB device found, idVendor=0403, idProduct=6001 Aug 18 09:09:37 zen kernel: [1678067.477922] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Aug 18 09:09:37 zen kernel: [1678067.477927] usb 3-3: Product: FT232R USB UART Aug 18 09:09:37 zen kernel: [1678067.477930] usb 3-3: Manufacturer: FTDI Aug 18 09:09:37 zen kernel: [1678067.477933] usb 3-3: SerialNumber: AH01IAGC Aug 18 09:09:37 zen
Re: Bug#685200: base: ftdi_sio stop working after several hours
severity 685200 normal reassign 685200 linux-2.6 thanks # the formatting aint broken in the original report... On Samstag, 18. August 2012, Mathieu MD wrote: Package: base Severity: grave Justification: renders package unusable I control a four relays board throught an USB cable connected to a Xen Dom0 running Debian 6.0.5. It works great: I can switch on and off the relays through some echo into /dev/ttyUSB0 (echo -e \xff\x01\x01 /dev/ttyUSB0). I added a crontab to send such echo every 15 minutes. It works great at the begining. But after some hours, I get this error message in /var/log/syslog each time I echo to ttyUSB0: #-8--8-- Aug 18 09:04:32 zen kernel: [1677762.865609] ftdi_sio ttyUSB0: Unable to write latency timer: -62 Aug 18 09:04:32 zen kernel: [1677762.869623] ftdi_sio ttyUSB0: ftdi_set_termios FAILED to set databits/stopbits/parity Aug 18 09:04:32 zen kernel: [1677762.871604] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate Aug 18 09:04:32 zen kernel: [1677762.875622] ftdi_sio ttyUSB0: urb failed to clear flow control Aug 18 09:04:32 zen kernel: [1677762.879604] ftdi_sio ttyUSB0: urb failed to clear flow control Aug 18 09:04:32 zen kernel: [1677762.881620] ftdi_sio ttyUSB0: error from flowcontrol urb Aug 18 09:04:32 zen kernel: [1677762.885623] ftdi_sio ttyUSB0: Unable to write latency timer: -62 Aug 18 09:04:32 zen kernel: [1677762.889637] ftdi_sio ttyUSB0: ftdi_set_termios FAILED to set databits/stopbits/parity Aug 18 09:04:32 zen kernel: [1677762.891622] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate Aug 18 09:04:32 zen kernel: [1677762.895616] ftdi_sio ttyUSB0: urb failed to clear flow control Aug 18 09:04:32 zen kernel: [1677762.903189] ftdi_sio ttyUSB0: error from flowcontrol urb #-8--8-- I have to unplug the USB cable and plug it back to get it to work again. Unplug: #-8--8-- Aug 18 09:04:46 zen kernel: [167.053078] usb 3-3: USB disconnect, address 17 Aug 18 09:04:46 zen kernel: [167.053233] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 Aug 18 09:04:46 zen kernel: [167.053248] ftdi_sio 3-3:1.0: device disconnected #-8--8-- Plug: #-8--8-- Aug 18 09:04:49 zen kernel: [169.816320] usb 3-3: new full speed USB device using ohci_hcd and address 18 Aug 18 09:04:49 zen kernel: [169.998248] usb 3-3: New USB device found, idVendor=0403, idProduct=6001 Aug 18 09:04:49 zen kernel: [169.998260] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Aug 18 09:04:49 zen kernel: [169.998270] usb 3-3: Product: FT232R USB UART Aug 18 09:04:49 zen kernel: [169.998278] usb 3-3: Manufacturer: FTDI Aug 18 09:04:49 zen kernel: [169.998284] usb 3-3: SerialNumber: AH01IAGC Aug 18 09:04:49 zen kernel: [1677780.006100] usb 3-3: configuration #1 chosen from 1 choice Aug 18 09:04:49 zen kernel: [1677780.013642] ftdi_sio 3-3:1.0: FTDI USB Serial Device converter detected Aug 18 09:04:49 zen kernel: [1677780.013712] usb 3-3: Detected FT232RL Aug 18 09:04:49 zen kernel: [1677780.013720] usb 3-3: Number of endpoints 2 Aug 18 09:04:49 zen kernel: [1677780.013728] usb 3-3: Endpoint 1 MaxPacketSize 64 Aug 18 09:04:49 zen kernel: [1677780.013736] usb 3-3: Endpoint 2 MaxPacketSize 64 Aug 18 09:04:49 zen kernel: [1677780.013744] usb 3-3: Setting MaxPacketSize 64 Aug 18 09:04:49 zen kernel: [1677780.015289] usb 3-3: FTDI USB Serial Device converter now attached to ttyUSB0 #-8--8-- The first times I echo to ttyUSB0 after plugin it, the log shows this: #-8--8-- Aug 18 09:09:36 zen kernel: [1678067.020400] hub 3-0:1.0: port 3 disabled by hub (EMI?), re-enabling... Aug 18 09:09:36 zen kernel: [1678067.020439] usb 3-3: USB disconnect, address 21 Aug 18 09:09:36 zen kernel: [1678067.020793] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 Aug 18 09:09:36 zen kernel: [1678067.020839] ftdi_sio 3-3:1.0: device disconnected Aug 18 09:09:37 zen kernel: [1678067.292977] usb 3-3: new full speed USB device using ohci_hcd and address 22 Aug 18 09:09:37 zen kernel: [1678067.477915] usb 3-3: New USB device found, idVendor=0403, idProduct=6001 Aug 18 09:09:37 zen kernel: [1678067.477922] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Aug 18 09:09:37 zen kernel: [1678067.477927] usb 3-3: Product: FT232R USB UART Aug 18 09:09:37 zen kernel: [1678067.477930] usb 3-3: Manufacturer: FTDI Aug 18 09:09:37 zen kernel: [1678067.477933] usb 3-3: SerialNumber: AH01IAGC Aug 18 09:09:37 zen
Re: Bug#684516: kernel loads bluetooth module, without reason (no HW)
reassign 684516 linux-2.6 severity 684516 normal thanks On Freitag, 10. August 2012, asronche...@libero.it wrote: Package: base Severity: important Dear Maintainer, as i noticed here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683807#85 The kernel loads the bluetooth module also if i have no bluetooth hardware on this notebook. kernel is 3.2.0-3-amd64 #1 SMP x86_64 and i'm using debian wheezy bye, Asdrubale -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/201208101949.30851.hol...@layer-acht.org
Re: Linux kernel hardening - link restrictions
Hi, On Freitag, 2. März 2012, Kees Cook wrote: + * The new kernel version includes security restrictions on links, +These restrictions may cause some legitimate programs to fail. +In particular, if the 'at' package is installed, you should either: +- Upgrade it to at least version 3.1.13-1 (or a backport of that) +- Set sysctl fs.protected_hardlinks=0 (see /etc/sysctl.conf) It's a trivial patch[1] to fix at. How about just backporting that change to stable, to avoid that known trouble too? This is what Ubuntu did for the Lucid LTS release that was getting backported kernels (with link restrictions) built for it. sounds like a reasonable plan to me, cc:ing debian-release to get a comment on this, and cc:ing the at maintainer too. [1] http://anonscm.debian.org/gitweb/?p=collab-maint/at.git;a=commitdiff;h=f4114656c3a6c6f6070e315ffdf940a49eda3279 cheers, Holger -- 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/201203021147.16121.hol...@layer-acht.org
Re: Bug#658401: base: Atheros AR9285 Wi-Fi adapter not working on HP 630 notebook with Wheezy
reassign 658401 linux-2.6 thanks On Donnerstag, 2. Februar 2012, Illés Gábor wrote: Package: base Severity: important Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** I have a fresh install of Wheezy on my new laptop, and noticed that my Wi-Fi adapter doesn't work. I turned on and off several times the wireless switch on the laptop's keyboard - no effect. Issued rfkill list command shows that the switch does not do anything: phy0 is soft and hard blocked too at all time (the hp-wifi Wireless LAN on the other way is stucked soft - yes, hard - no state). I have Windows installed on a different partition, haven't experienced any problem with the adapter. The device is showing at lspci list: 03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01) and the ath9k module are present: lsmod: mac80211 183047 1 ath9k ath9k_common 12682 1 ath9k ath9k_hw 281405 2 ath9k,ath9k_common I have a wireless usb adapter - SMCWUSB-G type - and with the installation of the appropriate package (zd1211) from the repo it had worked perfectly - network manager and all that. Anyway, this is my first use of reportbug, so please excuse me, if i forget something to add. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=hu_HU.utf8, LC_CTYPE=hu_HU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/201202030133.05135.hol...@layer-acht.org
Bug#642703: Processed: Re: Bug#642703: general: Scan lines appear in drop-down menus. LibreOffice also shows artifacts when starting. Might be something to do with the version of fglrx.
unmerge 642703 reassign 642703 fglrx-driver thanks On Montag, 26. September 2011, Jonathan Nieder wrote: The reporter uses fglrx. How can these possibly be the same bug? pebkac, I misread 642703#34 sorry for the noise. -- 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/201109260846.34200.hol...@layer-acht.org
Bug#612463: still there in 6.0.2
Hi, this bug still exists in 6.0.2: myframe:~# vserver foo start can not change context: migrate kernel feature missing and 'compat' API disabled: Function not implemented /proc/uptime can not be accessed. Usually, this is caused by procfs-security. Please read the FAQ for more details http://linux-vserver.org/Proc-Security Failed to start vserver 'foo' myframe:~# /etc/init.d/util-vserver start vc_get_iattr(): Function not implemented /var/lib/vservers/foo/..: Function not implemented Starting Linux-VServers in background myframe:~# uname -a Linux myframe 2.6.32-5-vserver-powerpc #1 SMP Tue Jun 14 11:48:51 UTC 2011 ppc GNU/Linux myframe:~# dpkg -l |grep linux-image|grep vserver ii linux-image-2.6-vserver-powerpc 2.6.32+29 Linux 2.6 for uniprocessor 32-bit PowerPC (meta-package), Linux-VServer support ii linux-image-2.6.26-2-vserver-powerpc 2.6.26-26lenny2 Linux 2.6.26 image on uniprocessor 32-bit PowerPC, Linux-VServer support ii linux-image-2.6.32-5-vserver-powerpc 2.6.32-35 Linux 2.6.32 for uniprocessor 32-bit PowerPC, Linux-VServer support cheers, Holger, still happy to test -- 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/201106251832.15809.hol...@layer-acht.org
Re: Bug#631157: base: pcmcia card xircom (REM56G-100) won't work at boot, but will work after ejecting and reinstering
reassign 631157 linux-2.6 thanks On Dienstag, 21. Juni 2011, Hans Vereyken wrote: Package: base Severity: normal I have a XIRCOM Realport REM65G-100, pluged into Dell Inspiron 3700. I tried to install the card, drivers where present, the card is detected, but won't work. I found this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/45295 In this bugreport people are advising to eject the card and insert it while the laptop is on. It works! Quote: BTW, the Xircom card is a multi-device card (LAN and modem device) and the modem is detected and configured during boot, but not the LAN. The kernel module 'serial_cs' is loaded and bound to the device The kernel module 'xirc2ps_cs' is loaded but not bound !? Might the problem be related to udev ? - Patrick Frey 'lsmod' shows some lines that may be inetresting: xirc2ps_cs 10343 0 serial_cs 13924 1 pcmcia 16194 2 xir2c2ps_cs,serial_cs pcmcia_core 20150 5 xir2c2ps_cs,serial_cs,pcmcia,yenta_socket,rsrc_nonstatic 'dmesg' has some interesting lines too: [13.877155] pcmcia_socket pcmcia_socket0: pccard: PCMCIA card inserted into slot 0 [14.409329] pcmcia 0.0: pcmcia: registered new device pcmcia0.0 maybe 'find / -name xir*' can be interesting: /lib/modules/2.6.32-5-686/kernel/drivers/net/tulip/xircom_cb.ko /lib/modules/2.6.32-5-686/kernel/drivers/net/pcmcia/xirc2ps_cs.ko /sys/bus/pcmcia/drivers/xirc2ps_cs /sys/module/pcmcia_core/holders/xirc2ps_cs /sys/module/pcmcia/holders/xirc2ps_cs /sys/module/xirc2ps_cs Hopfully I can help resolving this bug. -- System Information: Debian Release: 6.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=nl_BE.utf8, LC_CTYPE=nl_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/201106210921.54677.hol...@layer-acht.org
Re: Bug#631080: general: No sound in Squezee, control volume dont found devices
reassign 631080 linux-2.6 thanks On Montag, 20. Juni 2011, David Jorge wrote: Package: general Severity: normal Tags: d-i On a new installation of Squezee, i dont have a sound. This is my sound device: lspci | grep -i audio 00:05.0 Audio device: nVidia Corporation MCP61 High Definition Audio (rev a2) nVidia Corporation MCP61 High Definition Audio (rev a2) Subsystem: Giga-byte Technology Device a002 Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 21 Memory at fe024000 (32-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: HDA Intel With gstreamer-properties, i cant get any sound too. -- System Information: Debian Release: 6.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=es_MX.utf8, LC_CTYPE=es_MX.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/201106201037.44279.hol...@layer-acht.org
Re: Bug#628670: general: Long waking up times on Intel HD gpu and rtl8192ce wireless drivers
reassign 628670 linux-2.6 thanks On Dienstag, 31. Mai 2011, Ben Hutchings wrote: On Tue, 2011-05-31 at 10:41 +0200, Michalxo wrote: Package: general Severity: important Hello, I am experiencing some problem with wifi drivers rtl8192ce supported by kernel 6.38-2-amd64. Waking up from suspend last probably 2-3minutes with all black screen. When system finally manages to wake up I see messages about kernel bugs reported to maintaniner, but I have no active connection that time, so nothing got send. I am 99% positive, that bug is connected to wifi driver, cause with realtek's official or no drivers it woke up in less then 5 secs. Please send the kernel log (output of dmesg) after booting, suspending and resuming. Ben. -- 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/201106021618.12753.hol...@layer-acht.org
Re: Linux 3.0
On Montag, 30. Mai 2011, Ben Hutchings wrote: against Linux 3.0 release candidates when they are uploaded to experimental (which will happen in the next few days). awesome. you posted this 5min _before_ I (jokingly) had the idea to ask when Debian will have linux 3.0! :-) /me bows to the whole kernel team! cheers! -- 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/201105301901.10249.hol...@layer-acht.org
Re: Bug#619326: upgrade-reports: x-server not working any longer after updating from 6.0.0 to 6.0.1
reassign 619326 linux-2.6 tags 619326 + moreinfo thanks Hi, please send the dmesg output to this bug. Thanks. On Dienstag, 22. März 2011, Mister_Ka wrote: Package: upgrade-reports Severity: important After updating from a working 6.0.0 standard version to 6.0.1 booting ends in a total black screen just illuminated by its backlight. Trying to change from x to any tty does not work. Looks like x-server is not working correct with the Intel 855GM graphics adapter on notebook. Using the standard recovery grub entry does end in the same situation without any possibility to change anything or any readable error message or checkbox. Seems as if the x-server does not really crash but ends in black. Computer is accessible by SSH and x-forwarding works! Same happens on another notebook (identical in construction) and another with this graphic chip after restarting after a successful new installation using the net-iso-image. Using a older DVD-ISO without network connection for install results in a working system - updating this to 6.0.1 kills it in the same way. Its likely its related to a known bug with the intel-drivers other distributions had some times ago based on x-server-org incompatibility and new kernel setting. Maybe releated to the i915.modeset and KMS Problems there around a year ago. -- System Information: Debian Release: 6.0.1 APT prefers squeeze-updates APT policy: (500, 'squeeze-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash signature.asc Description: This is a digitally signed message part.
Bug#619371: base: wake on lan does not work with some special type of machines (Fujitsu-Siemens Esprimo P5625)
Hi, On Donnerstag, 24. März 2011, Christian Andretzky wrote: Hmm - I'm not really sure what you want. I've installed reportbug (The bug-report was created using reportbug ;-) but I can't find a '-N' switch. reportbug from lenny doesnt have this switch, versions from squeeze and above do :) cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#618881: nfs-common: fails to install due to incorrect dependencies in init.d LSB header
Package: nfs-common Version: 1:1.2.2-5 Severity: serious User: debian...@lists.debian.org Usertags: piuparts piuparts.d.o User: initscripts-ng-de...@lists.alioth.debian.org Usertags: incorrect-dependency Hi, during a test with piuparts I noticed your package failed to install due to incorrect dependencies in the init.d LSB header. Some debian notes are available from at http://wiki.debian.org/LSBInitScripts From the attached log (scroll to the bottom...): 0m21.3s DEBUG: Starting command: ['chroot', '/org/piuparts.debian.org/tmp/tmpO7tGFW', 'apt-get', '-y', 'install', 'nfs-common'] 0m22.6s DUMP: Reading package lists... Building dependency tree... Reading state information... The following NEW packages will be installed: nfs-common 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 253 kB of archives. After this operation, 680 kB of additional disk space will be used. Get:1 http://piatti.debian.org/debian/ sid/main nfs-common amd64 1:1.2.2-5 [253 kB] debconf: delaying package configuration, since apt-utils is not installed Fetched 253 kB in 0s (0 B/s) Selecting previously deselected package nfs-common. (Reading database ... 6484 files and directories currently installed.) Unpacking nfs-common (from .../nfs-common_1%3a1.2.2-5_amd64.deb) ... Setting up nfs-common (1:1.2.2-5) ... Creating config file /etc/idmapd.conf with new version Creating config file /etc/default/nfs-common with new version insserv: Service portmap has to be enabled to start service nfs-common insserv: exiting now! update-rc.d: error: insserv rejected the script header dpkg: error processing nfs-common (--configure): subprocess installed post-installation script returned error exit status 1 configured to not write apport reports Errors were encountered while processing: nfs-common E: Sub-process /usr/bin/dpkg returned an error code (1) cheers, Holger Start: 2011-03-17 22:07:11 UTC Package: nfs-common Priority: standard Section: net Installed-Size: 664 Maintainer: Debian kernel team debian-kernel@lists.debian.org Architecture: amd64 Source: nfs-utils Version: 1:1.2.2-5 Replaces: mount ( 2.13~), nfs-client, nfs-kernel-server ( 1:1.0.7-5) Provides: nfs-client Depends: libc6 (= 2.3), libcap2 (= 2.10), libcomerr2 (= 1.01), libevent-1.4-2 (= 1.4.13-stable), libgssapi-krb5-2 (= 1.6.dfsg.2), libgssglue1, libk5crypto3 (= 1.6.dfsg.2), libkrb5-3 (= 1.6.dfsg.2), libnfsidmap2, librpcsecgss3, libwrap0 (= 7.6-4~), rpcbind | portmap, adduser, ucf, lsb-base (= 1.3-9ubuntu3), netbase (= 4.24), initscripts (= 2.86.ds1-38.1) Conflicts: nfs-client Filename: pool/main/n/nfs-utils/nfs-common_1.2.2-5_amd64.deb Size: 253218 MD5sum: 32f81c300623dd87e5526e25cd757918 SHA1: 32e4d81fb7720b418434d081f44ae8a461588a99 SHA256: f2bdb996b97f702ad91c9558ec5483e5bf163646fe2cb1faa970951019ce0179 Description: NFS support files common to client and server Use this package on any machine that uses NFS, either as client or server. Programs included: lockd, statd, showmount, nfsstat, gssd and idmapd. Homepage: http://nfs.sourceforge.net/ Tag: admin::filesystem, implemented-in::c, interface::commandline, interface::daemon, network::client, network::server, protocol::nfs, role::program Executing: sudo /org/piuparts.debian.org/sbin/piuparts --warn-symlinks --warn-on-others --skip-logrotatefiles-test --scriptsdir /etc/piuparts/scripts/ --tmpdir /org/piuparts.debian.org/tmp -ad sid -b sid.tar.gz --mirror http://piatti.debian.org/debian/ nfs-common Guessed: debian 0m0.0s INFO: -- 0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of this logfile. 0m0.0s INFO: FAQ available at http://wiki.debian.org/piuparts/FAQ 0m0.0s INFO: -- 0m0.0s INFO: piuparts version 0.40~201102250909 starting up. 0m0.0s INFO: Command line arguments: /org/piuparts.debian.org/sbin/piuparts --warn-symlinks --warn-on-others --skip-logrotatefiles-test --scriptsdir /etc/piuparts/scripts/ --tmpdir /org/piuparts.debian.org/tmp -ad sid -b sid.tar.gz --mirror http://piatti.debian.org/debian/ nfs-common 0m0.0s INFO: Running on: Linux piatti 2.6.32-5-amd64 #1 SMP Wed Jan 12 03:40:32 UTC 2011 x86_64 0m0.0s DEBUG: Created temporary directory /org/piuparts.debian.org/tmp/tmpO7tGFW 0m0.0s DEBUG: Unpacking sid.tar.gz into /org/piuparts.debian.org/tmp/tmpO7tGFW 0m0.0s DEBUG: Starting command: ['tar', '-C', '/org/piuparts.debian.org/tmp/tmpO7tGFW', '-zxf', 'sid.tar.gz'] 0m3.0s DEBUG: Command ok: ['tar', '-C', '/org/piuparts.debian.org/tmp/tmpO7tGFW', '-zxf', 'sid.tar.gz'] 0m3.0s DEBUG: Created policy-rc.d and chmodded it. 0m3.0s DEBUG: Starting command: ['chroot', '/org/piuparts.debian.org/tmp/tmpO7tGFW', 'apt-get', 'update'] 0m14.0s DUMP: Get:1 http://piatti.debian.org sid InRelease [147 kB] Ign http://piatti.debian.org sid/main amd64
Re: Bug#617694: general: rt2860sta reconnect fails wpa2 enterprise peap
reassign 617694 linux-2.6 tags 617694 + moreinfo thanks Hi, we need more information to process this bug report, please run reportbug -N 617694 and send the information to this bug report. Thanks, Holger On Donnerstag, 10. März 2011, reydecopas wrote: Package: general Severity: normal hi, When reconnect to a wpa2 enterprise peap wireless network the network-manager doesn't get connection. The solution I have tested is: right click in network-manager, disable wireless, modprobe -r rt2860sta, load the module again, and enable wireless in network-manager, then it works does it happen to anyone? Greetings -- System Information: Debian Release: 6.0 APT prefers squeeze-updates APT policy: (500, 'squeeze-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash signature.asc Description: This is a digitally signed message part.
Bug#617708: Acknowledgement (kernel crash during resume from hibernation on IBM TP R50p)
Hi Ian, from your dmesg output I cannot see if you have exactly the same radeon as my R51 has (ATI Radeon RV250), but take a look at #595124 and see if the workaround (disabling agpmode) also works for you. Also, did you report 617709 in error? It looks like a clone of 617708. cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: Bug#614326: Netgear FA-120 USB Ethernet asix driver fails with latest dist-upgrade
reassign 614326 linux-2.6 # there is also a follow-up in the bts thanks On Montag, 21. Februar 2011, Ken Yee wrote: Package: base Version: 2.6.37-1 The asix driver appears to be broken with the latest dist-upgrade code in the sid repository. The Netgear FA-120 USB ethernet adapter puts out these messages: [ 7.188171] asix 1-1:1.0: eth1: register 'asix' at usb-:00:12.2-1, Netgear FA-120 USB Ethernet, 00:0f:b5:82:65:39 [ 7.188199] usbcore: registered new interface driver asix [ 83.864173] asix 1-1:1.0: eth1: Failed to enable software MII access [ 88.864105] asix 1-1:1.0: eth1: Failed to enable hardware MII access [ 101.398096] asix 1-1:1.0: eth1: Failed to enable hardware MII access [ 106.398156] asix 1-1:1.0: eth1: Failed to enable software MII access [ 126.894078] asix 1-1:1.0: eth1: Failed to enable software MII access [ 131.894142] asix 1-1:1.0: eth1: Failed to enable hardware MII access [ 136.894081] asix 1-1:1.0: eth1: Failed to enable software MII access [ 147.895193] asix 1-1:1.0: eth1: Failed to enable software MII acces The airlink101 adapter (asix 88178 chip) hangs the entire system. And the Apple usb/ethernet adapter (also asix based) puts these stack dumps in syslog: [ 327.712025] [ cut here ] [ 327.712046] WARNING: at /tmp/buildd/linux-aptosid-2.6-2.6.37/debian/build/source_amd64_none/net/sch ed/sch_generic.c:258 dev_watchdog+0x238/0x250() [ 327.712053] Hardware name: System Product Name [ 327.712058] NETDEV WATCHDOG: eth1 (asix): transmit queue 0 timed out [ 327.712062] Modules linked in: vboxnetflt nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp ipt_REJECT ipt_ULOG xt_limit xt_state ipt_REDIRECT xt_tcpudp iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_filter ip_tables x_tables ppdev lp capifs sco bnep rfcomm l2cap crc16 bluetooth rfkill ntfs nls_utf8 nls_cp437 vfat fat ext3 jbd mbcache xfs exportfs vboxdrv psmouse powernow_k8 freq_table mperf hwmon_vid eeprom fuse dm_crypt lgdt330x cx88_dvb cx88_vp3054_i2c videobuf_dvb dvb_core ir_kbd_i2c rtc_isl1208 tuner_simple snd_hda_codec_hdmi tuner_types snd_hda_codec_realtek tda9887 tda8290 snd_hda_intel snd_hda_codec snd_hwdep cx88_alsa tuner ir_lirc_codec snd_pcm_oss lirc_dev snd_mixer_oss snd_pcm snd_seq_dummy cx8802 ir_sony_decoder radeon cx8800 snd_seq_oss ir_jvc_decoder cx88xx ir_rc6_decoder snd_seq_midi v4l2_common snd_rawmidi ir_rc5_decoder videodev ir_nec_decoder snd_seq_midi_event v4l1_compat ir_common v4l2_compat_ioctl32 ir_core snd_seq ttm asix usbnet drm_kms_helper tveeprom drm videobuf_dma_sg btcx_risc tpm_tis snd_timer tpm rtc_cmos videobuf_core i2c_algo_bit snd_seq_device tpm_bios i2c_piix4 pcspkr rtc_core snd evdev rtc_lib parport_pc k8temp asus_atk0110 shpchp parport i2c_core soundcore amd64_edac_mod edac_core snd_page_alloc pci_hotplug edac_mce_amd button processor wmi reiserfs raid1 md_mod dm_mirror dm_region_hash dm_log dm_mod sg sr_mod sd_mod cdrom usbhid crc_t10dif ata_generic pata_acpi hid ohci_hcd pata_atiixp ahci libahci libata ehci_hcd usbcore ssb firewire_ohci firewire_core mmc_core pcmcia crc_itu_t floppy r8169 mii scsi_mod pcmcia_core nls_base [last unloaded: vboxnetadp] core nls_base [last unloaded: vboxnetadp] [ 327.712296] Pid: 0, comm: kworker/0:0 Not tainted 2.6.37-1.slh.1-aptosid-amd64 #1 [ 327.712301] Call Trace: [ 327.712306] IRQ [8105093b] ? warn_slowpath_common+0x7b/0xc0 [ 327.712326] [81050a35] ? warn_slowpath_fmt+0x45/0x50 [ 327.712336] [811d12a2] ? strlcpy+0x42/0x50 [ 327.712344] [812dd418] ? dev_watchdog+0x238/0x250 [ 327.712353] [8105d2f3] ? lock_timer_base+0x33/0x70 [ 327.712361] [8105d424] ? mod_timer_pinned+0xf4/0x170 [ 327.712371] [810138e1] ? native_sched_clock+0x11/0x60 [ 327.712379] [8105d049] ? run_timer_softirq+0x139/0x250 [ 327.712386] [8104b0d9] ? scheduler_tick+0xd9/0x2e0 [ 327.712393] [812dd1e0] ? dev_watchdog+0x0/0x250 [ 327.712401] [81056ca6] ? __do_softirq+0xa6/0x140 [ 327.712408] [8100bddc] ? call_softirq+0x1c/0x30 [ 327.712416] [8100e0d5] ? do_softirq+0x65/0xa0 [ 327.712422] [81056b55] ? irq_exit+0x95/0xa0 [ 327.712431] [8102855a] ? smp_apic_timer_interrupt+0x6a/0xa0 [ 327.712439] [8100b893] ? apic_timer_interrupt+0x13/0x20 [ 327.712443] EOI [8102f762] ? native_safe_halt+0x2/0x10 [ 327.712459] [81071ecc] ? __atomic_notifier_call_chain+0x4c/0x70 [ 327.712467] [810140d3] ? default_idle+0x23/0x40 [ 327.712474] [810141e4] ? c1e_idle+0x54/0x120 [ 327.712484] [8100a0ce] ? cpu_idle+0x5e/0xb0 [ 327.712490] ---[ end trace cbaaca18bc9cfcc2 ]--- This doesn't appear to be kernel specific...same behavior in the 2.6.36-2 kernel and the latest 2.6.37-1 kernel. signature.asc Description: This is a digitally signed message part.
Re: Bug#613317: dmesg + Xorg logs wanted
reassign 613317 linux-2.6 # this is not an upgrade issue as it persists after upgrading # maybe its an xorg issue but I'm sure you (linux-2.6) can reassign ;) thanks Hi Eddy, On Mittwoch, 2. März 2011, Eddy Petrișor wrote: tags 613317 - moreinfo Attached. I also did some tests and the same problem is visible in fluxbox. Thanks, Holger signature.asc Description: This is a digitally signed message part.
Re: Bug#615543: base: Firmware files not found by boot process, despite specific files are there and readable for world
reassign 615543 linux-2.6 thanks On Sonntag, 27. Februar 2011, Hodosi Szabolcs wrote: Package: base Severity: important I have two DVB_T USB device, either or both of them can not read the firmware file, nowadays this issue occurs with an (Alcor DTV-1000) Afatech 9015 USB device. DMESG output: usb 1-7: New USB device found, idVendor=15a4, idProduct=9016 usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 1-7: Product: DVB-T 2 usb 1-7: Manufacturer: Afatech ata6: SATA link down (SStatus 0 SControl 310) Freeing unused kernel memory: 464k freed udev[117]: starting version 164 dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in cold state, will try to load a firmware dvb-usb: did not find the firmware file. (dvb-usb-af9015.fw) Please see linux/Documentation/dvb/ for more details on firmware-problems. (-2) dvb_usb_af9015: probe of 1-7:1.0 failed with error -2 lsusb out: root@torch:~# lsusb Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 06da:0003 Phoenixtec Power Co., Ltd Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 004: ID 15a4:9016 Afatech Technologies, Inc. AF9015 DVB-T USB2.0 stick Bus 001 Device 003: ID 2304:023d Pinnacle Systems, Inc. PCTV 340e Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub And the firmware file is there: root@torch:/lib/firmware# ls -l /lib/firmware/dvb-usb-af9015.fw -rw-r--r-- 1 root root 15913 2010 �pr 16 /lib/firmware/dvb-usb-af9015.fw Packages installed contains firmwares: root@torch:/lib/firmware# dpkg --list | grep firmware ii firmware-ivtv0.28 Binary firmware for iTVC15-family MPEG codecs (ivtv and pvrusb2 drivers) ii firmware-linux 0.28 Binary firmware for various drivers in the Linux kernel (meta-package) ii firmware-linux-free 2.6.32-30Binary firmware for various drivers in the Linux kernel ii firmware-linux-nonfree 0.28 Binary firmware for various drivers in the Linux kernel ii firmware-realtek 0.28 Binary firmware for Realtek wired and wireless network adapters Can you please look into why the boot process cannot read the firmware file, which exists and readable? Scope: Device is unable to use. Exclusion: Other firmwares are detected and loaded. User Status: Reboot didn't help. Poweroff, unplug the computer didn't help. Unplug the device then replug didn't helped. The device worked properly under Ubuntu 10.04 LTS Lucid Lynx with (almost) the same kernel (2.6.35.x). The system itself is a : root@torch:/lib/firmware# uname -a Linux torch 2.6.35.10-3 #1 SMP Mon Dec 27 19:56:08 CET 2010 x86_64 GNU/Linux Thank you very much for all the help, guideance. -- System Information: Debian Release: 6.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.35.10-3 (SMP w/4 CPU cores) Locale: LANG=hu_HU.UTF-8, LC_CTYPE=hu_HU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash signature.asc Description: This is a digitally signed message part.
Re: Bug#615048: base: After removing lvm snapshot got kernel BUG at /build/.../source_amd64_xen/arch/x86/xen/mmu.c:1649!
reassign 615048 linux-2.6 thanks On Freitag, 25. Februar 2011, root.kwp.malopolska wrote: Package: base Severity: normal Problems's started after changing version of Debian from Lenny to Squeeze. I'm using Xen with virtual hosts on LVM volumes. I make a snapshot of LVM volume and dump it to a file. After it I'm tring to remove snapshot. The operation fails and generates kernel error. After the error one of cpus is used in 100%. Neither shutdown(reboot) nor use many other command because seems like the system is high load or hung up. The same is on two other machines (I've got two HP DL360g5 and one DL380g7). Feb 25 03:32:05 xen3 kernel: [400058.329748] [ cut here ] Feb 25 03:32:05 xen3 kernel: [400058.329785] kernel BUG at /build/buildd-linux-2.6_2.6.32-30-amd64-d4MbNM/linux-2.6-2.6.32/debian/buil d/s ource_amd64_xen/arch/x86/xen/mmu.c:1649! Feb 25 03:32:05 xen3 kernel: [400058.329857] invalid opcode: [#1] SMP Feb 25 03:32:05 xen3 kernel: [400058.329900] last sysfs file: /sys/devices/pci:00/:00:01.0/:05:00.0/cciss0/c0d0/block/cciss!c 0d0/cciss!c0d0p2/size Feb 25 03:32:05 xen3 kernel: [400058.329965] CPU 1 Feb 25 03:32:05 xen3 kernel: [400058.330001] Modules linked in: dm_snapshot nfs lockd fscache nfs_acl auth_rpcgss sunrpc tun ip6table_fil ter ip6_tables ebtable_nat ebtables cpufreq_stats cpufreq_powersave cpufreq_conservative cpufreq_userspace xen_evtchn xenfs binfmt_misc f use bridge stp ipt_REJECT xt_state xt_physdev xt_tcpudp iptable_filter iptable_mangle iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack n f_defrag_ipv4 ip_tables x_tables loop psmouse joydev evdev hpwdt hpilo pcspkr serio_raw container power_meter button processor acpi_proce ssor ext3 jbd mbcache dm_mod sg sr_mod cdrom ata_generic usbhid hid ata_piix uhci_hcd libata ehci_hcd usbcore nls_base cciss bnx2 scsi_mo d thermal thermal_sys [last unloaded: scsi_wait_scan] Feb 25 03:32:05 xen3 kernel: [400058.330706] Pid: 20284, comm: udisks-dm-expor Not tainted 2.6.32-5-xen-amd64 #1 ProLiant DL380 G7 Feb 25 03:32:05 xen3 kernel: [400058.330765] RIP: e030:[8100c694] [8100c694] pin_pagetable_pfn+0x2d/0x36 Feb 25 03:32:05 xen3 kernel: [400058.330827] RSP: e02b:880256c53e08 EFLAGS: 00010282 Feb 25 03:32:05 xen3 kernel: [400058.330860] RAX: ffea RBX: 00115e50 RCX: 0001 Feb 25 03:32:05 xen3 kernel: [400058.330916] RDX: RSI: 0001 RDI: 880256c53e08 Feb 25 03:32:05 xen3 kernel: [400058.330976] RBP: 8802e8885780 R08: 0280 R09: ea0003cca180 Feb 25 03:32:05 xen3 kernel: [400058.331032] R10: 7ff0 R11: 0f7a1030 R12: 880114dc10a0 Feb 25 03:32:05 xen3 kernel: [400058.331089] R13: 88011c1465c0 R14: 8802e6e946a0 R15: 880114dc10a0 Feb 25 03:32:05 xen3 kernel: [400058.331149] FS: 7f9b42e6f7a0() GS:88000f78f000() knlGS: Feb 25 03:32:05 xen3 kernel: [400058.331211] CS: e033 DS: ES: CR0: 8005003b Feb 25 03:32:05 xen3 kernel: [400058.331249] CR2: 7f9b428143c0 CR3: 000105534000 CR4: 2660 Feb 25 03:32:05 xen3 kernel: [400058.331304] DR0: DR1: DR2: Feb 25 03:32:05 xen3 kernel: [400058.331357] DR3: DR6: 0ff0 DR7: 0400 Feb 25 03:32:05 xen3 kernel: [400058.331421] Process udisks-dm-expor (pid: 20284, threadinfo 880256c52000, task 8802e6e946a0) Feb 25 03:32:05 xen3 kernel: [400058.331482] Stack: Feb 25 03:32:05 xen3 kernel: [400058.331513] 0020de50 ea0003cca180 00115e50 Feb 25 03:32:05 xen3 kernel: [400058.331579] 0 8802e8885780 810cd4e2 8801334d8368 7f9b428143c0 Feb 25 03:32:05 xen3 kernel: [400058.331661] 0 0001334d8000 810cb394 88011c1465c0 7f9b428143c0 Feb 25 03:32:05 xen3 kernel: [400058.331764] Call Trace: Feb 25 03:32:05 xen3 kernel: [400058.331764] Call Trace: Feb 25 03:32:05 xen3 kernel: [400058.331803] [810cd4e2] ? __pte_alloc+0x6b/0xc6 Feb 25 03:32:05 xen3 kernel: [400058.331847] [810cb394] ? pmd_alloc+0x28/0x5b Feb 25 03:32:05 xen3 kernel: [400058.331888] [810cd60b] ? handle_mm_fault+0xce/0x80f Feb 25 03:32:05 xen3 kernel: [400058.331927] [8102ddc0] ? pvclock_clocksource_read+0x3a/0x8b Feb 25 03:32:05 xen3 kernel: [400058.331966] [8130f016] ? do_page_fault+0x2e0/0x2fc Feb 25 03:32:05 xen3 kernel: [400058.332005] [8130ceb5] ? page_fault+0x25/0x30 Feb 25 03:32:05 xen3 kernel: [400058.332042] Code: ec 28 89 3c 24 48 89 f7 e8 a2 fd ff ff 48 89 e7 48 89 44 24 08 be 01 00 00 00 31 d2 41 ba f0 7f 00 00 e8 b0 cc ff ff 85 c0 74 04 0f 0b eb fe 48 83 c4 28 c3 55 49 89 ca 48 89 d5 40 88 f1 48 89 Feb 25 03:32:05 xen3 kernel: [400058.332487] RIP [8100c694] pin_pagetable_pfn+0x2d/0x36 Feb 25 03:32:05 xen3
Re: Bug#613845: base: Speaker doesn't work but headphones works well. Laptop HP G62.
severity 613845 normal
reassign 613845 linux-2.6
tags 613845 + moreinfo
thanks
Hi Andrii,
please send you full dmesg output to 613845@bugs.d.o and give 2.6.37 from
unstable a try and report back as well. Thanks.
cheers,
Holger
On Donnerstag, 17. Februar 2011, Andrii Grytsenko wrote:
Package: base
Severity: important
Tags: squeeze
-- System Information:
Debian Release: 6.0
APT prefers squeeze-updates
APT policy: (500, 'squeeze-updates'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (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
I can't make my audio system works properly on my HP G62 laptop. I can hear
the sound only in my headphone, and my speaker and microphone don't work at
all.
Here some information:
# cat /proc/asound/card0/codec#* | grep Codec
Codec: Realtek ID 270
Codec: Intel G45 DEVIBX
# aplay -l output:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 3: INTEL HDMI [INTEL HDMI]
Subdevices: 1/1
Subdevice #0: subdevice #0
# lspci | grep -i audio
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High
Definition Audio (rev 05)
Alsa information:
# dpkg -l | grep alsa
ii alsa-base1.0.23+dfsg-2
ALSA driver configuration files ii alsa-utils
1.0.23-3 Utilities for configuring and using ALSA
ii bluez-alsa 4.66-3
Bluetooth ALSA support ii libsdl1.2debian-alsa 1.2.14-6.1
Simple DirectMedia Layer (with X11 and ALSA options)
Try to emulate such behave in console (without X). Run mpg123 and got the
same stuff - can only hear sound through headphones.
My /etc/modprobe.d/alsa-base.conf looks like:
# autoloader aliases
install sound-slot-0 /sbin/modprobe snd-card-0
install sound-slot-1 /sbin/modprobe snd-card-1
install sound-slot-2 /sbin/modprobe snd-card-2
install sound-slot-3 /sbin/modprobe snd-card-3
install sound-slot-4 /sbin/modprobe snd-card-4
install sound-slot-5 /sbin/modprobe snd-card-5
install sound-slot-6 /sbin/modprobe snd-card-6
install sound-slot-7 /sbin/modprobe snd-card-7
# Cause optional modules to be loaded above generic modules
install snd /sbin/modprobe --ignore-install snd { /sbin/modprobe --quiet
snd-ioctl32 ; /sbin/modprobe --quiet snd-seq ; } install snd-rawmidi
/sbin/modprobe --ignore-install snd-rawmidi { /sbin/modprobe --quiet
snd-seq-midi ; : ; } install snd-emu10k1 /sbin/modprobe --ignore-install
snd-emu10k1 { /sbin/modprobe --quiet snd-emu10k1-synth ; : ; }
# Prevent abnormal drivers from grabbing index 0
options bt87x index=-2
options cx88_alsa index=-2
options snd-atiixp-modem index=-2
options snd-intel8x0m index=-2
options snd-via82xx-modem index=-2
# Keep snd-pcsp from beeing loaded as first soundcard
options snd-pcsp index=-2
# Keep snd-usb-audio from beeing loaded as first soundcard
options snd-usb-audio index=-2
Appended to config next line:
options snd-hda-intel model=basic
then change it to
options snd-hda-intel model=hp
And even try to comment out:
options snd-intel8x0m index=-2
After any changes reboot the system or run alsa force-reload. But nothing
help me.
Also tried to delete pulseaudio:
apt-get purge pulseaudio
But this step was unsuccessful too.
signature.asc
Description: This is a digitally signed message part.
Re: Bug#613755: base: Laptop does not recover after suspend
reassign 613755 linux-2.6 tags 613755 + moreinfo thanks Hi Jorge, please send the output of dmesg and lspci -nn to 613...@bugs.debian.org cheers, Holger On Donnerstag, 17. Februar 2011, Jorge Ramos wrote: Package: base Severity: important The laptop is configured so that it will suspend when closing the lid. It does suspend as expected but when the lid is open again, the system wont recover. Instead it shows a black screen (as if X didn't recover and went to a terminal) but I can't do anything. The only thing that the displays shows is these 3 lines: [118.502991] btusb_intr_complete: hci0 usb 88015e415300 failed to resubmit(1) [118.503981] btusb_intr_complete: hci0 usb 88015e415480 failed to resubmit(1) [118.504986] btusb_intr_complete: hci0 usb 88015e4153c0 failed to resubmit(1) I have to restart ctrl-alt-delete 'ing it to take cotrol of the system again. It restarts normally and behaves as if nothing happened afterwards. -- System Information: Debian Release: 6.0 APT prefers squeeze-updates APT policy: (500, 'squeeze-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=es_MX.utf8, LC_CTYPE=es_MX.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash signature.asc Description: This is a digitally signed message part.
Bug#612463: linux-image-2.6.32-5-vserver-powerpc: Vserver functionality not working at all
Hi, I can confirm this bug and could also test patches or images. cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: Bug#612744: general: Keyboard input problem after somehow connected with win_key
severity 612744 normal reassign 612744 linux-2.6 thanks On Donnerstag, 10. Februar 2011, michalxo wrote: Package: general Severity: serious Justification: required I've described this bug here. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/397496 I am getting this error in debian too. Linux calypso 2.6.32-5-amd64 #1 SMP Wed Jan 12 03:40:32 UTC 2011 x86_64 GNU/Linux -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash signature.asc Description: This is a digitally signed message part.
Re: Bug#605032: general: Acer Aspire 5553g fails to resume after hibernate
reassign 605032 linux-2.6 thanks On Freitag, 26. November 2010, Sergey Chepurko wrote: Package: general Severity: normal When i use hibernate mode on my laptop Acer Aspire 5553g with closing my notebook i cant resume the session when open it later. It simply freezes. All i can do is force shut down using 5 sec press power button. There no other key is responsing. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/3 CPU cores) Locale: LANG=ru_RU.utf8, LC_CTYPE=ru_RU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash signature.asc Description: This is a digitally signed message part.
Re: Bug#605030: general: bluetooth adapter ar3011 on acer aspire 5553g don't start after shutdown
reassign 605030 linux-2.6 thanks On Freitag, 26. November 2010, Sergey Chepurko wrote: Package: general Severity: normal I am using Debian testing with latest updates installed. I have a atheros ar3011 bluetooth adapter on my laptop. The problem is next, when i shutdown my laptop and on first boot choose to run debian my adapter don't start. To get my adapter working i have to boot into my windows 7 second system and then reboot to debian. This steps allow me to use bluetooth untill next shutdown. When my adapter is unavailable i get empty output from 'hcitool dev' command. Nevertheless the output by 'lsusb' is this: Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 0cf3:3002 Atheros Communications, Inc. Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 0402:9665 ALi Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub. Here is my adapter on Bus 004. But system can't start it. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/3 CPU cores) Locale: LANG=ru_RU.utf8, LC_CTYPE=ru_RU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash signature.asc Description: This is a digitally signed message part.
Re: Bug#604013: base: ls -al on armel inside loopback mounted ISO image failes with -1 ENOMEM
reassign 604013 linux-2.6
user debian-...@lists.debian.org
usertag 604013 + eabi
thanks
On Freitag, 19. November 2010, Robert Heinzmann wrote:
Package: base
Severity: normal
** Please type your report below this line ***
I'm running Debian on Seagate Dockstar (Kirkwood platform). When I mount a
ISO image via loopback (mount -o loop myfile.iso /mnt) a ls inside this
mounted tree (ls -al /mnt/) failes with Cannot allocate memory.
This is a test on the Kirkwood machine:
r...@dockstar:/srv/tftp# md5sum systemrescuecd-x86-1.6.2.iso
b7662eb44b530d62c487dd367f2036ed systemrescuecd-x86-1.6.2.iso
r...@dockstar:/srv/tftp# uname -a
Linux dockstar.lab.elconas.de 2.6.32-5-kirkwood #1 Sat Sep 18 15:20:08 UTC
2010 armv5tel GNU/Linux
r...@dockstar:/srv/tftp# mount -o loop systemrescuecd-x86-1.6.2.iso
sysrescuecd r...@dockstar:/srv/tftp# ls -al sysrescuecd
ls: cannot access sysrescuecd/bootdisk: Cannot allocate memory
ls: cannot access sysrescuecd/bootprog: Cannot allocate memory
ls: cannot access sysrescuecd/isolinux: Cannot allocate memory
ls: cannot access sysrescuecd/ntpasswd: Cannot allocate memory
ls: cannot access sysrescuecd/sysrcd.dat: Cannot allocate memory
ls: cannot access sysrescuecd/sysrcd.md5: Cannot allocate memory
ls: cannot access sysrescuecd/usb_inst: Cannot allocate memory
ls: cannot access sysrescuecd/usb_inst.sh: Cannot allocate memory
ls: cannot access sysrescuecd/usbstick.htm: Cannot allocate memory
ls: cannot access sysrescuecd/version: Cannot allocate memory
total 6
dr-xr-xr-x 1 root root2048 Oct 11 20:09 .
drwxr-xr-x 22 tftp nogroup 4096 Nov 19 11:38 ..
?? ? ?? ?? bootdisk
?? ? ?? ?? bootprog
?? ? ?? ?? isolinux
?? ? ?? ?? ntpasswd
?? ? ?? ?? sysrcd.dat
?? ? ?? ?? sysrcd.md5
?? ? ?? ?? usb_inst
?? ? ?? ?? usb_inst.sh
?? ? ?? ?? usbstick.htm
?? ? ?? ?? version
dmesg ...
[49412.581257] ISO 9660 Extensions: Microsoft Joliet Level 3
[49412.581340] ISOFS: changing to secondary root
r...@dockstar:/srv/tftp# ldd /bin/ls
libselinux.so.1 = /lib/libselinux.so.1 (0x40005000)
librt.so.1 = /lib/librt.so.1 (0x40026000)
libacl.so.1 = /lib/libacl.so.1 (0x40036000)
libgcc_s.so.1 = /lib/libgcc_s.so.1 (0x40044000)
libc.so.6 = /lib/libc.so.6 (0x40058000)
libdl.so.2 = /lib/libdl.so.2 (0x40188000)
/lib/ld-linux.so.3 (0x2a00)
libpthread.so.0 = /lib/libpthread.so.0 (0x40193000)
libattr.so.1 = /lib/libattr.so.1 (0x401b3000)
r...@dockstar:/srv/tftp# file /bin/ls
/bin/ls: ELF 32-bit LSB executable, ARM, version 1 (SYSV), dynamically
linked (uses shared libs), for GNU/Linux 2.6.18, stripped
r...@dockstar:/srv/tftp# strace ls -al sysrescuecd/ntpasswd
.
open(/proc/filesystems, O_RDONLY|O_LARGEFILE) = 3
fstat64(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x4001e000 read(3, nodev\tsysfs\nnodev\trootfs\nnodev\tb..., 1024) = 286
read(3, , 1024) = 0
close(3)= 0
munmap(0x4001e000, 4096)= 0
ioctl(1, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo
...}) = 0 ioctl(1, TIOCGWINSZ, {ws_row=57, ws_col=190, ws_xpixel=0,
ws_ypixel=0}) = 0 lstat64(sysrescuecd/ntpasswd, 0x280b0) = -1 ENOMEM
(Cannot allocate memory) write(2, ls: , 4ls: ) = 4
write(2, cannot access sysrescuecd/ntpass..., 34cannot access
sysrescuecd/ntpasswd) = 34 write(2, : Cannot allocate memory, 24: Cannot
allocate memory) = 24 write(2, \n, 1
) = 1
close(1)= 0
close(2)= 0
exit_group(2) = ?
-
When I do the same thing on normal x86_64 everything is ok:
debian:/# md5sum systemrescuecd-x86-1.6.2.iso
b7662eb44b530d62c487dd367f2036ed systemrescuecd-x86-1.6.2.iso
debian:/# uname -a
Linux debian 2.6.32-5-amd64 #1 SMP Fri Sep 17 21:50:19 UTC 2010 x86_64
GNU/Linux
debian:/# mount -o loop /systemrescuecd-x86-1.6.2.iso /mnt/test/
debian:/# ls -al /mnt/test
insgesamt 227894
dr-xr-xr-x 1 root root 2048 11. Okt 20:09 .
drwxr-xr-x 9 root root 4096 11. Nov 12:26 ..
dr-xr-xr-x 1 root root 2048 11. Jun 21:15 bootdisk
dr-xr-xr-x 1 root root 2048 26. Mai 09:07 bootprog
dr-xr-xr-x 1 root root 2048 11. Okt 20:10 isolinux
dr-xr-xr-x 1 root root 2048 2. Mär 2010 ntpasswd
-r-xr-xr-x 1 root root 233328640 11. Okt 20:09 sysrcd.dat
-r-xr-xr-x 1 root root45 11. Okt 20:09 sysrcd.md5
dr-xr-xr-x 1 root root 2048 28. Jun 21:35 usb_inst
Re: Next Lenny Point Release (5.0.7)
Hi Philipp, thanks for taking care of stable point releases! Much appreciated! :-) On Samstag, 13. November 2010, Philipp Kern wrote: the next Lenny Point Release (5.0.7) is scheduled to happen on Saturday, November 27th. We will start at approximately 11 UTC. [...] If there's something that should still be in- or excluded, please contact us ASAP on `debian-rele...@lists.debian.org'. Another d-i respin is in the queue and will be hopefully done in time. ;-) What changes to d-i are planned? IOW: should Debian Edu release new lenny images too? cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#561764: Bug#600959: boot warnings too fast to read and not saved in any file nor dmesg
merge 600959 561764 thanks On Donnerstag, 21. Oktober 2010, Ben Hutchings wrote: This looks the same as #561764, reported by... you. signature.asc Description: This is a digitally signed message part.
Re: Bug#599901: base: System Crash with ata3.00 error
reassign 599901 linux-2.6
thanks
On Dienstag, 12. Oktober 2010, Kevin wrote:
Package: base
Severity: important
Tags: d-i
I encountered a serious problem of ata3.00 error when I was running the
system, /var/log/kernel.log:
kernel: [ 872.444136] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0
action 0x0
kernel: [ 872.444146] ata3.00: BMDMA stat 0x25
kernel: [ 872.444153] ata3.00: failed command: READ DMA
kernel: [ 872.444168] ata3.00: cmd c8/00:08:3c:44:22/00:00:00:00:00/ed tag
0 dma 4096 in
kernel: [ 872.444172] res 51/40:00:3f:44:22/00:00:00:00:00/ed
Emask 0x9 (media error)
kernel: [ 872.444180] ata3.00: status: { DRDY ERR }
kernel: [ 872.444185] ata3.00: error: { UNC }
kernel: [ 872.485549] ata3.00: configured for UDMA/133
kernel: [ 872.485578] ata3: EH complete
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
signature.asc
Description: This is a digitally signed message part.
Re: Bug#597817: base: Realtek RTL8111/8168B doesn't always work
reassign 597817 linux-2.6 thanks On Donnerstag, 23. September 2010, Aniruddha wrote: Package: base Severity: important Every other boot I don't have internet access, eth0 doesn't get an ip address assigned from the dhcp server. ifdown eth0 / ifup eth0 doens't work either. When I reboot everything works again. I have installed several distro's on this pc which didn't have this problems. I think the problem is with my Realtek network card. lspci | grep Eth 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03) $ lsmod Module Size Used by parport_pc 18855 0 ppdev 5030 0 lp 7462 0 parport27954 3 parport_pc,ppdev,lp powernow_k810946 0 cpufreq_stats 2659 0 cpufreq_userspace 1960 0 cpufreq_powersave902 0 vboxnetadp 4193 0 vboxnetflt 12525 0 vboxdrv 1723671 2 vboxnetadp,vboxnetflt cpufreq_conservative 5162 0 nfsd 253286 13 exportfs3138 1 nfsd nfs 240218 0 lockd 57475 2 nfsd,nfs fscache29594 1 nfs nfs_acl 2031 2 nfsd,nfs auth_rpcgss33396 2 nfsd,nfs sunrpc160837 12 nfsd,nfs,lockd,nfs_acl,auth_rpcgss loop 11767 0 firewire_sbp2 11434 0 snd_hda_codec_atihdmi 2251 1 snd_hda_codec_via 47887 1 snd_hda_intel 19955 3 snd_hda_codec 54244 3 snd_hda_codec_atihdmi,snd_hda_codec_via,snd_hda_intel snd_hwdep 5380 1 snd_hda_codec joydev 8411 0 snd_pcm60503 2 snd_hda_intel,snd_hda_codec btusb 9817 0 bluetooth 41763 1 btusb snd_seq42737 0 usbhid 33148 0 rfkill 12964 1 bluetooth hid62793 1 usbhid radeon572625 0 ttm39746 1 radeon snd_timer 15582 2 snd_pcm,snd_seq drm_kms_helper 20033 1 radeon asus_atk01107686 0 snd_seq_device 4493 1 snd_seq drm 142151 3 radeon,ttm,drm_kms_helper i2c_algo_bit4225 1 radeon i2c_piix4 8328 0 i2c_core 15680 5 radeon,drm_kms_helper,drm,i2c_algo_bit,i2c_piix4 snd 46414 14 snd_hda_codec_via,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_seq,snd _timer,snd_seq_device edac_core 29261 0 edac_mce_amd6401 0 button 4650 0 soundcore 4598 1 snd pcspkr 1699 0 psmouse49729 0 processor 30239 1 powernow_k8 serio_raw 3752 0 evdev 7352 17 snd_page_alloc 6169 2 snd_hda_intel,snd_pcm ext4 288329 2 mbcache 5050 1 ext4 jbd2 66759 1 ext4 crc16 1319 1 ext4 sg 18712 0 sr_mod 12602 0 cdrom 29415 1 sr_mod sd_mod 29713 4 crc_t10dif 1276 1 sd_mod ata_generic 2983 0 ahci 32310 3 ohci_hcd 19116 0 pata_atiixp 3457 0 libata133328 3 ata_generic,ahci,pata_atiixp ehci_hcd 30895 0 r8169 28765 0 mii 3210 1 r8169 scsi_mod 121861 5 firewire_sbp2,sg,sr_mod,sd_mod,libata firewire_ohci 19404 0 firewire_core 36656 2 firewire_sbp2,firewire_ohci thermal11674 0 crc_itu_t 1307 1 firewire_core thermal_sys11942 2 processor,thermal usbcore 121698 5 btusb,usbhid,ohci_hcd,ehci_hcd nls_base6377 1 usbcore -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash signature.asc Description: This is a digitally signed message part.
Re: Bug#597209: base: keyboard doesn't work properly
reassign 597209 linux-2.6 thanks On Freitag, 17. September 2010, rush wrote: Package: base Severity: normal Hello, I've an error in dmesg: $ dmesg | grep -i keyboard [0.430054] atkbd.c: Failed to enable keyboard on isa0060/serio0 [0.430174] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1 I think it is a reason, that LED indicators don't work at all: i can press caps lock or num lock, but it doesn't affect at LED at all, it affects only on keyboard behaviour. and this LED is my layout indicator. it's too hard to work without it :( By the way keyboard if Genius GK-04008/C and it worked perfect with old computer (there was debian since debian etch). This bug is only with new hardware. I tried to use this keyboard with old one and all is fine. New hardware is: AMD Athlon II X2 215 with Gigabyte M52L-S3P. Old one was AMD Athlon Dual Core 4050 with EliteGroup GeForce6100PMM2 SocketAM2. Also setleds from VT shows nothing about caps lock. it's always off. Others (num and scroll) it shows correct, but leds are always turned on. By the way, my keyboard configuration: $ grep -vE ^#|^$ /etc/default/keyboard XKBMODEL=pc105 XKBLAYOUT=us,ru XKBVARIANT=, XKBOPTIONS=grp:caps_toggle,grp_led:scroll I tried to change keyboard with dpkg-reconfigure keyboard-configuration, but it didn't help me. The last one, if it's matter anything my wm is awesome and i haven't any DE (like gnome/kde/etc). Thank you for your time and help. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash signature.asc Description: This is a digitally signed message part.
Bug#587887: linux-base: please suppress useless debconf messages on first install
Hi Ben,
for the record, this workaround works for me: build a custom udeb and put the
following into a file in /usr/lib/post-base-installer.d/$some_filename
# work around # 587887
grep -v cdrom /target/etc/fstab /target/etc/fstab.new
mv /target/etc/fstab /target/etc/fstab.bak
mv /target/etc/fstab.new /target/etc/fstab
# avoid warning that no boatloader is installed by installing one early
chroot /target apt-get -y install grub
mkdir -p /target/boot/grub
chroot /target update-grub
Preseeding that warning about no bootloader didnt work. I used:
linux-base linux-base/disk-id-manual-boot-loader error
On Freitag, 27. August 2010, Ben Hutchings wrote:
I think we've discussed this before.
Yes. In this report.
linux-base is supposed to be quiet
during a fresh system installation. It uses this heuristic:
# No upgrade work is necessary during a fresh system installation.
# But since linux-base is a new dependency of linux-image-* and did
# not exist until needed for the libata transition, we cannot simply
# test whether this is a fresh installation of linux-base. Instead,
# we test:
# - does /etc/fstab exist yet (this won't even work without it), and
# - are any linux-image-* packages installed yet?
sub is_fresh_installation {
if (-f '/etc/fstab') {
for (`dpkg-query 2/dev/null --showformat '\${status}\\n' -W
'linux-image-*'`) { return 0 if / installed\n$/;
}
}
return 1;
}
If you think this gives the wrong answer, please propose an alternative.
I cant come up with a reliable one. As we already discussed, not
having /var/log/installer must not mean anything :/
Note that if you hack the lenny installer to install a backported kernel
and suppress the libata transition code in linux-base, this may result
in configuration files that use unstable device names. You should
consider using the testing installer instead.
That's not feasable due to other customisations we've done. The above
workaround works for us, so...
cheers,
Holger
signature.asc
Description: This is a digitally signed message part.
Bug#587887: linux-base: please suppress useless debconf messages on first install
Hi, On Samstag, 3. Juli 2010, Bastian Blank wrote: Well, then its easy: don't create this useless entry. ok, I'm now using a post-base-installer hook in d-i to remove the cdrom entry from /etc/fstab and voila, an inserted CDROM still pops up in KDE, yay. But I still wonder why this linux-base postinst bothers about fstab entries for /media/cdrom and /media/floppy at all. Those will never work with UUIDs :) cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#587887: linux-base: please suppress useless debconf messages on first install
Hi, and I can still not preseed that warning away, that no bootloader has been detected... (Which is bad, as the .32-bpo is installed as part of the base system when this has been upgraded by d-i, but before the bootloader installation...) cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#587887: linux-base: please suppress useless debconf messages on first install
Hi Ben, On Donnerstag, 26. August 2010, Ben Hutchings wrote: It may complain about an ATAPI floppy, but not one handled by a platform floppy driver. As for /media/cdrom, its device should be specified as /dev/cdrom or similar. with the lenny installer, /dev/scd0 shall be mounted at /media/cdrom0 (using a vmware scsi CD-ROM drive..) cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#587887: linux-base: please suppress useless debconf messages on first install
On Donnerstag, 26. August 2010, Ben Hutchings wrote: with the lenny installer, /dev/scd0 shall be mounted at /media/cdrom0 (using a vmware scsi CD-ROM drive..) And that needs to be fixed. does the fix work with the kernels in lenny? signature.asc Description: This is a digitally signed message part.
Re: Bug#589667: base: ACPI Exception with power_meter-347 in logs
reassign 589667 linux-2.6 thanks On Montag, 19. Juli 2010, Juri Gurjanov wrote: Package: base Severity: normal Found a lots of error messages in logs, which shows: [278680.783048] ACPI Error: SMBus or IPMI write requires Buffer of length 42, found length 20 (20090903/exfield-286) [278680.904560] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PMI0._PMM] (Node 88031e04e7c0), AE_AML_BUFFER_LIMIT [278681.041304] ACPI Exception: AE_AML_BUFFER_LIMIT, Evaluating _PMM (20090903/power_meter-347) -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash signature.asc Description: This is a digitally signed message part.
Bug#587887: linux-base: please suppress useless debconf messages on first install
Hi Ben, On Freitag, 2. Juli 2010, Ben Hutchings wrote: [/var/log/installer] We can't use this test. Older installations don't have such a directory. I dont understand. Every lenny (at least) installation done with d-i has this directory?! How are older installations relevant? cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#587887: linux-base: please suppress useless debconf messages on first install
Hi, On Samstag, 3. Juli 2010, Julien Cristau wrote: On Sat, Jul 3, 2010 at 12:54:12 +0200, Holger Levsen wrote: How are older installations relevant? How are they not? Well, first I'm fairly very sure that even etch also created /var/log/installer... in that sense I dont think it matters, if you automatically install sarge with a 2.6.32.bpo kernel and get those warnings... cause I doubt anyone does that, thus I think those are not relevant. cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#587887: linux-base: please suppress useless debconf messages on first install
package: linux-base
version: 2.6.32-15
severity: wishlist
tags: patch
Hi,
first of all: thank you all for maintaining linux-2.6 - you're doing an
awesome job!
h01ger hi. i'm using .32.bpo on lenny, together with linux-base. so far so
good, works great. but i have an issue with automated installs (with d-i and
preseeding): linux-base informs me that /etc/fstab contains an entry
(/etc/scd0 iirc) which might not work in future versions. i couldnt care less
and would like to get rid of this warning,as it prevents fully automated
installations
bwh^ h01ger: I put a heuristic in there to work out whether this is a fresh
installation or upgrade
bwh^ h01ger: Maybe you can suggest how to improve it
bwh^ (the problem is that linux-base did not exist in lenny, so we cannot
check whether the package itself is being upgraded)
bwh^ Of course you should also be able to preseed the answer
h01ger i tried, using what debconf-get-selections |grep linux-base gave me
after an installation, but that didnt work
bwh^ weird
# make linux-base install quietly
#
# Boot loader configuration check needed
linux-base linux-base/disk-id-manual-boot-loader error
# Configuration files still contain deprecated device names
linux-base linux-base/disk-id-manual error
# Apply configuration changes to disk device IDs?
linux-base linux-base/disk-id-convert-plan-no-relabel boolean true
# Opdater diskenheds-id'er i systemkonfigurationen?
linux-base linux-base/disk-id-convert-auto boolean true
# Apply configuration changes to disk device IDs?
linux-base linux-base/disk-id-convert-plan boolean true
h01ger bwh, i wonder if your test fails as there were already .26 packages
installed...
h01ger ha! if /var/log/installer doesnt exist, its a fresh install. bingo
see attached patch
h01ger bwh, do you want a wishlist bug about this?
bwh^ h01ger: Yes, file a wishlist bug, please
cheers,
Holger
1578a1579,1581
if !(-d '/var/log/installer') {
return 0;
}
signature.asc
Description: This is a digitally signed message part.
