Bug#469693: Turned out to be a topology problem
On Fri 07.11.2008 21:01:02 Moritz Muehlenhoff wrote: Could you file a bug report on this at bugzilla.kernel.org and post the bug number to this bug report? Sorry, it would be too expensive to make a high quality upstream report. I suggest to close the current bug, 2.6.26 is outdated anyhow and there is a work-around. The only real and relevant message behind the problem is just: For some possibly broken USB hardware Win (2003) possibly does better error recovery. Thanks, Jürgen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#505545: [linux-image-2.6.26-1-xen-amd64] linux-image-2.6.26-1-xen-amd64 floppy mount problem
Package: linux-image-2.6.26-1-xen-amd64 Version: 2.6.26-8 Severity: important --- Please enter the report below this line. --- When trying to mount a floppy while running the XEN-kernel the mount process fails. The kernel without xen in lenny (linux-image-2.6.26-1-amd64) can mount the floppy without any problems. The following lines comes in dmesg: [ 914.603561] floppy0: unexpected interrupt [ 914.604012] floppy0: sensei repl[0]=80 [ 914.606460] floppy0: -- FDC reply errorfloppy0: Unable to send byte 8 to FDC. Fdc=0 Status=d0 [ 916.002170] [ 916.002170] floppy driver state [ 916.002170] --- [ 916.002170] now=4295121149 last interrupt=4295121149 diff=0 last called handler=a00b570f [ 916.002170] timeout_message=floppy start [ 916.002170] last output bytes: [ 916.002170] 0 90 4295121003 [ 916.002170] 0 90 4295121003 [ 916.002170] 0 90 4295121003 [ 916.002170] 1 90 4295121003 [ 916.002170] 5 90 4295121003 [ 916.002170] 2 90 4295121003 [ 916.002170] 1c 90 4295121003 [ 916.002170] ff 90 4295121003 [ 916.002170] 3 80 4295121104 [ 916.002170] c1 90 4295121104 [ 916.002170] 11 90 4295121104 [ 916.002170] e6 80 4295121104 [ 916.002170] 0 90 4295121104 [ 916.002170] 0 90 4295121104 [ 916.002170] 0 90 4295121104 [ 916.002170] 1 90 4295121104 [ 916.002170] 2 90 4295121104 [ 916.002170] 14 90 4295121104 [ 916.002170] 1c 90 4295121104 [ 916.002170] ff 90 4295121104 [ 916.002170] last result at 4295121149 [ 916.002170] last redo_fd_request at 4295121099 [ 916.002170] [ 916.002170] status=d0 [ 916.002170] fdc_busy=1 [ 916.002170] fd_timer.function=a00b63fd [ 916.002170] timer_function=a00b9bf8 [ 916.002170] expires=700 [ 916.002170] now=4295121149 [ 916.002170] cont=a00be940 [ 916.002170] current_req=8800f12e7658 [ 916.002170] command_status=-1 [ 916.002170] [ 916.002170] floppy0: get result error. Fdc=0 Last status= Read bytes=0 [ 916.002170] [ 916.002170] floppy driver state [ 916.002170] --- [ 916.002170] now=4295121149 last interrupt=4295121149 diff=0 last called handler=a00b570f [ 916.002170] timeout_message=floppy start [ 916.002170] last output bytes: [ 916.002170] 0 90 4295121003 [ 916.002170] 0 90 4295121003 [ 916.002170] 0 90 4295121003 [ 916.002170] 1 90 4295121003 [ 916.002170] 5 90 4295121003 [ 916.002170] 2 90 4295121003 [ 916.002170] 1c 90 4295121003 [ 916.002170] ff 90 4295121003 [ 916.002170] 3 80 4295121104 [ 916.002170] c1 90 4295121104 [ 916.002170] 11 90 4295121104 [ 916.002170] e6 80 4295121104 [ 916.002170] 0 90 4295121104 [ 916.002170] 0 90 4295121104 [ 916.002170] 0 90 4295121104 [ 916.002170] 1 90 4295121104 [ 916.002170] 2 90 4295121104 [ 916.002170] 14 90 4295121104 [ 916.002170] 1c 90 4295121104 [ 916.002170] ff 90 4295121104 [ 916.002170] last result at 4295121149 [ 916.002170] last redo_fd_request at 4295121099 [ 916.002170] [ 916.002170] status=d0 [ 916.002170] fdc_busy=1 [ 916.002170] fd_timer.function=a00b63fd [ 916.002170] timer_function=a00b9bf8 [ 916.002170] expires=700 [ 916.002170] now=4295121149 [ 916.002170] cont=a00be940 [ 916.002170] current_req=8800f12e7658 [ 916.002170] command_status=-1 [ 916.002170] [ 916.022488] floppy0: unexpected interrupt repl[0]=40 repl[1]=10 repl[2]=0 repl[3]=0 repl[4]=0 repl[5]=1 repl[6]=2 [ 916.203869] floppy0: Unable to send byte 8 to FDC. Fdc=0 Status=d0 [ 916.203869] [ 916.203869] floppy driver state [ 916.203869] --- [ 916.203869] now=4295121200 last interrupt=4295121200 diff=0 last called handler=a00b570f [ 916.203869] timeout_message=floppy start [ 916.203869] last output bytes: [ 916.203869] 0 90 4295121155 [ 916.203869] 13 80 4295121155 [ 916.203869] 0 90 4295121155 [ 916.203869] 1a 90 4295121155 [ 916.203869] 0 90 4295121155 [ 916.203869] 3 80 4295121155 [ 916.203869] c1 90 4295121155 [ 916.203869] 11 90 4295121156 [ 916.203869] 7 80 4295121156 [ 916.203869] 0 90 4295121156 [ 916.203869] 8 81 4295121156 [ 916.203869] e6 80 4295121156 [ 916.203869] 0 90 4295121156 [ 916.203869] 0 90 4295121156 [ 916.203869] 0 90 4295121156 [ 916.203869] 1 90 4295121156 [ 916.203869] 2 90 4295121156 [ 916.203869] 14 90 4295121156 [ 916.203869] 1c 90 4295121156 [ 916.203869] ff 90 4295121156 [ 916.203869] last result at 4295121200 [ 916.203869] last redo_fd_request at 4295121155 [ 916.203869] [ 916.203869] status=d0 [ 916.203869] fdc_busy=1 [ 916.203869] fd_timer.function=a00b63fd [ 916.203869] timer_function=a00b9bf8 [ 916.203869] expires=705 [ 916.203869] now=4295121200 [ 916.203869] cont=a00be940 [ 916.203869] current_req=8800f12e7658 [ 916.203869] command_status=-1 [ 916.203869] [ 916.203869] floppy0: get result error. Fdc=0 Last status= Read bytes=0 [ 916.203869] [ 916.203869] floppy driver state [
Processed: severity of 505545 is normal
Processing commands for [EMAIL PROTECTED]: severity 505545 normal Bug#505545: [linux-image-2.6.26-1-xen-amd64] linux-image-2.6.26-1-xen-amd64 floppy mount problem Severity set to `normal' from `important' End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#433640: Confirm, can be closed
Yes, I can also confirm that the problem does not occur anymore. -- Stefan Frings, TOP-I Operations Engineer Vodafone D2 GmbH Mannesmannufer 3 40213 Duesseldorf Tel.: +49 211 533 7930 Mobile: +49 172 245 3666 eMail: [EMAIL PROTECTED] Vodafone D2 GmbH Am Seestern 1, D-40547 Duesseldorf, P.O.Box D-40543 Duesseldorf Executives: Friedrich Joussen (chairman), Jan Geldmacher, Hartmut Kremling, Frank Rosenberger, Dr. Volker Ruloff, Michele Angelo Verna, Achim Weusthoff Chairman of supervisory board: Vittorio Colao Place of business: Duesseldorf, Amtsgericht Duesseldorf, HRB 24644 WEEE-Reg.-Nr.: DE 91435957
Bug#505435: linux-2.6: The Build-Depends on kernel-package needs upgrading (leads to FTBFS)
On Wed, Nov 12, 2008 at 12:13:35PM +0200, Eric Pozharski wrote: Build against 11.0011 (current in testing) succeeds. The version in question does not use kernel-package to build i386 packages. No idea what you do. Bastian -- Insufficient facts always invite danger. -- Spock, Space Seed, stardate 3141.9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#436260: closed by maximilian attems m...@stro.at (Re: linux-support-2.6.22-1: Support for exernal module packages broken)
On Wed, Nov 12, 2008 at 11:03:55PM +0100, Moritz Muehlenhoff wrote: On Mon, Jun 30, 2008 at 02:13:33PM +0200, maximilian attems wrote: if you can reproduce it with 2.6.25 or newer snapshots. i'm all ears unless so it is assumed fixed. Mark, does the problem still exist for you with the current Lenny packages? Given that it took until six months after I'd left the job where I encountered the bug for the patch to get looked at you may as well close it - I don't really have the combination of time and enthusiam required to do so myself. -- You grabbed my hand and we fell into it, like a daydream - or a fever. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#505401: linux-2.6: acpi-cpufreq limits core 2 duo 1.6G to 1.2G with kernel ondemand governor
On Tue, Nov 11, 2008 at 11:10:56PM -0500, Bob Skaroff wrote: Subject: linux-2.6: acpi-cpufreq limits core 2 duo 1.6G to 1.2G Package: linux-2.6 Version: 2.6.26-5 Upgrade, -10 is current. incorrect scaling_max_freq is set by acpi-cpufreq and cannot be changed with cpufreq-set -u or echo 160/sys/devices/system/cpu/cpuX/cpufreq/scaling_max_freq scaling_max_freq can be changed to 800MHz doesn't matter which governor is active Check if your BIOS is uptodate. This values are often modified by ACPI themself. My notebook for example changes them if it gets too hot. Bastian -- Klingon phaser attack from front! 100% Damage to life support -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#505519: marked as done (linux-image-2.6.26-1-686: after Bios check system halt with wrong compressed format)
Your message dated Thu, 13 Nov 2008 11:59:07 +0100 with message-id [EMAIL PROTECTED] and subject line Re: Bug#505519: linux-image-2.6.26-1-686: after Bios check system halt with wrong compressed format has caused the Debian Bug report #505519, regarding linux-image-2.6.26-1-686: after Bios check system halt with wrong compressed format to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 505519: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=505519 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.26-1-686 Version: 2.6.26-10 Severity: grave Justification: renders package unusable after the latest update to 2.6.26-10 booting stops after the bios check with wrong compressed format -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.25-2-686 (SMP w/1 CPU core) Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.26-1-686 depends on: ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy ii initramfs-tools [linux-initra 0.92l tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.26-1-686 recommends: ii libc6-i6862.7-16 GNU C Library: Shared libraries [i Versions of packages linux-image-2.6.26-1-686 suggests: ii lilo 1:22.8-6.4 LInux LOader - The Classic OS load pn linux-doc-2.6.26 none (no description available) -- debconf information: linux-image-2.6.26-1-686/preinst/abort-overwrite-2.6.26-1-686: linux-image-2.6.26-1-686/postinst/bootloader-error-2.6.26-1-686: linux-image-2.6.26-1-686/postinst/depmod-error-initrd-2.6.26-1-686: false linux-image-2.6.26-1-686/postinst/old-system-map-link-2.6.26-1-686: true linux-image-2.6.26-1-686/prerm/would-invalidate-boot-loader-2.6.26-1-686: true linux-image-2.6.26-1-686/preinst/elilo-initrd-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/old-dir-initrd-link-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/kimage-is-a-directory: linux-image-2.6.26-1-686/postinst/create-kimage-link-2.6.26-1-686: true linux-image-2.6.26-1-686/preinst/overwriting-modules-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/depmod-error-2.6.26-1-686: false shared/kernel-image/really-run-bootloader: true linux-image-2.6.26-1-686/prerm/removing-running-kernel-2.6.26-1-686: true linux-image-2.6.26-1-686/preinst/abort-install-2.6.26-1-686: linux-image-2.6.26-1-686/preinst/lilo-has-ramdisk: linux-image-2.6.26-1-686/preinst/bootloader-initrd-2.6.26-1-686: true linux-image-2.6.26-1-686/preinst/lilo-initrd-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/old-initrd-link-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/bootloader-test-error-2.6.26-1-686: linux-image-2.6.26-1-686/preinst/failed-to-move-modules-2.6.26-1-686: linux-image-2.6.26-1-686/preinst/initrd-2.6.26-1-686: ---End Message--- ---BeginMessage--- On Thu, Nov 13, 2008 at 10:31:31AM +0100, bernhard kleine wrote: after the latest update to 2.6.26-10 booting stops after the bios check with wrong compressed format Known bug in lilo. Use the large-memory option. Bastian -- ... bacteriological warfare ... hard to believe we were once foolish enough to play around with that. -- McCoy, The Omega Glory, stardate unknown ---End Message---
Bug#505519: linux-image-2.6.26-1-686: after Bios check system halt with wrong compressed format
Package: linux-image-2.6.26-1-686 Version: 2.6.26-10 Severity: grave Justification: renders package unusable after the latest update to 2.6.26-10 booting stops after the bios check with wrong compressed format -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.25-2-686 (SMP w/1 CPU core) Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.26-1-686 depends on: ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy ii initramfs-tools [linux-initra 0.92l tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.26-1-686 recommends: ii libc6-i6862.7-16 GNU C Library: Shared libraries [i Versions of packages linux-image-2.6.26-1-686 suggests: ii lilo 1:22.8-6.4 LInux LOader - The Classic OS load pn linux-doc-2.6.26 none (no description available) -- debconf information: linux-image-2.6.26-1-686/preinst/abort-overwrite-2.6.26-1-686: linux-image-2.6.26-1-686/postinst/bootloader-error-2.6.26-1-686: linux-image-2.6.26-1-686/postinst/depmod-error-initrd-2.6.26-1-686: false linux-image-2.6.26-1-686/postinst/old-system-map-link-2.6.26-1-686: true linux-image-2.6.26-1-686/prerm/would-invalidate-boot-loader-2.6.26-1-686: true linux-image-2.6.26-1-686/preinst/elilo-initrd-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/old-dir-initrd-link-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/kimage-is-a-directory: linux-image-2.6.26-1-686/postinst/create-kimage-link-2.6.26-1-686: true linux-image-2.6.26-1-686/preinst/overwriting-modules-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/depmod-error-2.6.26-1-686: false shared/kernel-image/really-run-bootloader: true linux-image-2.6.26-1-686/prerm/removing-running-kernel-2.6.26-1-686: true linux-image-2.6.26-1-686/preinst/abort-install-2.6.26-1-686: linux-image-2.6.26-1-686/preinst/lilo-has-ramdisk: linux-image-2.6.26-1-686/preinst/bootloader-initrd-2.6.26-1-686: true linux-image-2.6.26-1-686/preinst/lilo-initrd-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/old-initrd-link-2.6.26-1-686: true linux-image-2.6.26-1-686/postinst/bootloader-test-error-2.6.26-1-686: linux-image-2.6.26-1-686/preinst/failed-to-move-modules-2.6.26-1-686: linux-image-2.6.26-1-686/preinst/initrd-2.6.26-1-686: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: remove moreinfo tag, info was provided
Processing commands for [EMAIL PROTECTED]: tag 504709 - moreinfo Bug#504709: Xen console problems Tags were: moreinfo Tags removed: moreinfo thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#505579: kernel's loading taking 2 or 3 minutes
Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-9 Severity: normal I've had problems booting with Lilo: kernel's loading take 2 or 3 minutes (may be even more). The whole system is on LVM, using Debian Sid.. It's a brand new install on a Dell Latitude 131L laptop, using a new hard drive (after a crash of the previous HD). This new hard drive is of the same model as the previous one, except the size which is double. Previously the laptop was running (fine) Debian Sid but without LVM. I'm not able to give more details because currently the system is unbootable after an upgrade to version 2.6.26-10. See bugs not yet reported with subjects: 1. Unbootable after kernel upgrade: Lilo can't load kernel 2. Kernel unable to mount file system and to execute init regards -- Xavier [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#505592: virtualbox-ose-modules-2.6.26-1-amd64: Debian packaged modules are different version than vbox, downgrade installed version
Package: virtualbox-ose-modules-2.6.26-1-amd64 Version: 2.6.26+1.6.2-dfsg-4 Severity: normal Virtualbox-ose and virtualbox-ose-modules are different versions. An `apt-get update ; apt-get dist-upgrade` today replaced my current modules with an outdated copy: Preparing to replace virtualbox-ose-modules-2.6.26-1-amd64 1.6.6-dfsg-3+2.6.26-8 (using .../virtualbox-ose-modules-2.6.26-1-amd64_2.6.26+1.6.2-dfsg-4_amd64.deb) ... Unpacking replacement virtualbox-ose-modules-2.6.26-1-amd64 ... Setting up virtualbox-ose-modules-2.6.26-1-amd64 (2.6.26+1.6.2-dfsg-4) ... This leads to different versions of virtualbox and virtualbox modules: independence:/home/james$ dpkg -l | grep virtualbox ii virtualbox-ose1.6.6-dfsg-3 x86 virt ualization solution - binaries ii virtualbox-ose-modules-2.6.24-1-amd64 1.6.2-dfsg-1+2.6.24-7 VirtualB ox modules for Linux (kernel 2.6.24- ii virtualbox-ose-modules-2.6.25-2-amd64 2.6.25+1.6.2-dfsg-5 PC virtu alization solution modules for Linux ii virtualbox-ose-modules-2.6.26-1-amd64 2.6.26+1.6.2-dfsg-4 PC virtu alization solution for Linux 2.6.26 ii virtualbox-ose-source 1.6.6-dfsg-3 x86 virt ualization solution - kernel module independence:/home/james# Forcing the user to repair the installation by rebuilding from source before virtualbox can be used. apt-cache policy virtualbox-ose virtualbox-ose: Installed: (none) Candidate: 1.6.6-dfsg-3 Version table: 1.6.6-dfsg-3 0 500 http://ftp.us.debian.org lenny/main Packages apt-cache policy virtualbox-ose-modules-2.6.26-1-amd64 virtualbox-ose-modules-2.6.26-1-amd64: Installed: (none) Candidate: 2.6.26+1.6.2-dfsg-4 Version table: 2.6.26+1.6.2-dfsg-4 0 500 http://ftp.us.debian.org lenny/main Packages -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-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 Versions of packages virtualbox-ose-modules-2.6.26-1-amd64 depends on: ii linux-image-2.6.26-1-amd64 [l 2.6.26-8 Linux 2.6.26 image on AMD64 virtualbox-ose-modules-2.6.26-1-amd64 recommends no packages. virtualbox-ose-modules-2.6.26-1-amd64 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#505609: Unbootable after kernel upgrade: Lilo can't load kernel
Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-10 Severity: critical I've did an upgrade on 2008-11-09, on a new installed system, upgrading kernel 2.6.26-09 to 2.6.26.10. Apt was also upgraded. I've seen nothing strange during upgrade and in the apt and dpkg logs. The system is entirely on LVM partitions. When reboting I obtain this message from Lilo: Loading LinuxEBDA is big; kernel setup stack overlaps LILO second stage. and the computer halt. regards -- Xavier [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#410817: Upstream fix in 2.6.26?
Moritz Muehlenhoff wrote: On Thu, Sep 18, 2008 at 12:31:04PM +0100, Simon Waters wrote: dann frazier wrote: On Thu, Sep 18, 2008 at 12:09:00AM +0100, Simon Waters wrote: http://bugzilla.kernel.org/show_bug.cgi?id=6695 2.6.26 is in lenny/sid - can someone test it to confirm? 2.6.26-1-686 from lenny boots my DELL SC400 with 6.62 firmware on the megaraid card. The boot was quite slow, but I'm comparing to a bespoke kernel without initrd, so that is not surprising. I have hacked on the box in the past to include additional megaraid drivers in the initrd config, so I can't say it a completely clean test, but I'd regard this as a fix (Stock 2.6.25 no boot, stock 2.6.26 boots). I will attempt a reinstall soon. Have you tested a reinstall already? No. I hope to do it next week as I have a week off from being a system admin next week ?! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#505613: Kernel unable to mount file system and to execute init
Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-9 Severity: critical I've downgraded my kernel from 2.6.26-10 to 2.6.26-9 after the system became unbootable (see bug report #505609). Now the system boot, but stop before mounting the file system and executing init. See below for the output. The system is entirely on LVM. Partitions comes from the same Volume Group: / (root file system) /tmp /usr /var /home /usr/local swap /media/empty While the system was unbootable (see bug report #505609), I've used the rescue mode of the Debian installer CD-ROM to boot, to mount the root and the /var partitions (and also /proc et /sys) and reinstall the package linux- image-2.6.26-1-amd64-2.6.26-9.deb (which was still on the hard drive). There was no errors in the output. I've rebooted, Lilo launch the new kernel, as slow as before (see my bug report 505579), the kernel boot and failed to mount filesystem and execute init. Here's the output: - Begin: Mounting root file system... Begin: Running /scripts/local-top... [ 6.588232] device-mapper: uevent: version 1.03 [ 6.588970] device-mapper: ioctl: 4.13.0-ioctl (2007-10-18) initialized: dm- [EMAIL PROTECTED] 8 logical volume(s) in volume group debian now active done. Begin: Running /scripts/local-premount... kinit: name_to_dev_t (/dev/mapper/debian-swap) = dm-5 (254,5) kinit: trying to resume from /dev/mapper/debian-swap [ 6.819292] PM: Starting manual resume from disk kinit: no resume image, doing normal boot... resume: libgcrypt version 1.4.1 done. mount: mounting /dev/root on /root failed: No such device Begin: Running /scripts/local-bottom... done. done. Begin: Running /scripts/init-bottom... mount: mounting /dev on /root/dev failed: No such file or directory done. mount: mounting /sys on /root/sys failed: No such file or directory mount: mounting /proc on /root/proc failed: no such file or directory Target file system doesn't have /sbin/init No init found. Try passing init=bootarg. - Then I got a shell in the initrd image. cat /proc/cmdline: BOOT_IMAGE=Linux ro root=fd00 (which is correct, Lilo -q -v5 shows me that 0xFD00 is /dev/debian/root) I've rebooted the system using Debian installer, and tried to: reinstall kernel run mkinitramfs run lilo but nothing change after that. please tell me if you need more informations. regards -- Xavier [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#505609: Unbootable after kernel upgrade: Lilo can't load kernel
On Thu, 2008-11-13 at 20:54 +0100, Xavier Brochard wrote: Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-10 Severity: critical I've did an upgrade on 2008-11-09, on a new installed system, upgrading kernel 2.6.26-09 to 2.6.26.10. Apt was also upgraded. I've seen nothing strange during upgrade and in the apt and dpkg logs. The system is entirely on LVM partitions. When reboting I obtain this message from Lilo: Loading LinuxEBDA is big; kernel setup stack overlaps LILO second stage. and the computer halt. I think this might be bug 479607 http://bugs.debian.org/479607. Did you add large-memory to /etc/lilo.conf? If not, does that fix the problem? Ben. signature.asc Description: This is a digitally signed message part
Booting Debian in 14 seconds
Dear Debian Kernel people, I'm writing to let you know about an article that I've written for Debian Administration about improving boot time: http://www.debian-administration.org/articles/620 I have been thinking about how a general-purpose distribution like Debian can get some of the benefits which, at first sight, may seem possible only in locked down systems. If you have any feedback you're welcome to use the article's comments section, or to follow up on this list, or to email me directly. Regards, Phil. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#469693: marked as done (linux-image-2.6.24-1-686: Got better but still looses USB devs (mouse/keyb))
Your message dated Thu, 13 Nov 2008 23:28:41 +0100 with message-id [EMAIL PROTECTED] and subject line Re: Turned out to be a topology problem has caused the Debian Bug report #469693, regarding linux-image-2.6.24-1-686: Got better but still looses USB devs (mouse/keyb) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 469693: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=469693 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.24-1-686 Severity: important Hi, compared to kernel 2.6.22 it got better, now I can enable my motherboard's USB card reader and still write this bug-report. In 2.6.22 USB became unuable after about 30s, now it takes longer. Of course it depends on hardware: this system has ATI SB600 and 690G chips, motherboard/barebone is ASUS Pundit. Also ... The problem is related to heavy USB load. Example: when I write GBytes of data to a USB disk (or Flash card or USB stick) the kernel logs a message like low speed usb device reset or so. After this time it has forgotten mouse and keyboard. It does not help to reconnect the USB cable. Again: with kernel 2.6.22 it was not possible (under my hardware) to enable the card reader or the write GBytes to an USB stick. With the new kernel it often takes 30 min or so to cause the problem. The system used here was even booted from an SD card, but KDE for example cannot be used, the mouse/kdb would get lost. -- System Information: Debian Release: lenny/sid Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- On Thu, Nov 13, 2008 at 11:41:22AM +0100, Dr. Jürgen Pfennig wrote: On Fri 07.11.2008 21:01:02 Moritz Muehlenhoff wrote: Could you file a bug report on this at bugzilla.kernel.org and post the bug number to this bug report? Sorry, it would be too expensive to make a high quality upstream report. I suggest to close the current bug, 2.6.26 is outdated anyhow and there is a work-around. Doing so. Cheers, Moritz ---End Message---
Bug#436260: marked as done (linux-support-2.6.22-1: Support for exernal module packages broken)
Your message dated Thu, 13 Nov 2008 23:32:43 +0100 with message-id [EMAIL PROTECTED] and subject line Re: Bug#436260: closed by maximilian attems [EMAIL PROTECTED] (Re: linux-support-2.6.22-1: Support for exernal module packages broken) has caused the Debian Bug report #436260, regarding linux-support-2.6.22-1: Support for exernal module packages broken to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 436260: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=436260 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-support-2.6.22-1 Version: 2.6.22-3 Severity: important Attempting to build a module module package such as linux-modules-extra-2.6 which uses gencontrol.py fails even when using the copy of gencontrol.py included in the package as /usr/src/linux-support-2.6.22-1/modules/gencontrol.py since the interface provided by lib/python/debian_linux has changed but gencontrol.py has not been updated to match the new interface. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: powerpc (ppc) Kernel: Linux 2.6.22-1-powerpc Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-support-2.6.22-1 depends on: ii python2.4-minimal 2.4.4-5A minimal subset of the Python lan linux-support-2.6.22-1 recommends no packages. -- no debconf information ---End Message--- ---BeginMessage--- On Thu, Nov 13, 2008 at 10:55:11AM +, Mark Brown wrote: On Wed, Nov 12, 2008 at 11:03:55PM +0100, Moritz Muehlenhoff wrote: On Mon, Jun 30, 2008 at 02:13:33PM +0200, maximilian attems wrote: if you can reproduce it with 2.6.25 or newer snapshots. i'm all ears unless so it is assumed fixed. Mark, does the problem still exist for you with the current Lenny packages? Given that it took until six months after I'd left the job where I encountered the bug for the patch to get looked at you may as well close it Doing so. Cheers, Moritz ---End Message---
Processed: bug 497392 is forwarded to http://bugzilla.kernel.org/show_bug.cgi?id=11998
Processing commands for [EMAIL PROTECTED]: forwarded 497392 http://bugzilla.kernel.org/show_bug.cgi?id=11998 Bug#497392: e1000e driver does not initialize correctly Noted your statement that Bug has been forwarded to http://bugzilla.kernel.org/show_bug.cgi?id=11998. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491522: linux-image-2.6.25-2-686 freezes on a HP laptop
On Sat, Jul 26, 2008 at 02:08:21PM +0200, Andreas Schroth wrote: Hello, I note the same problem on an HP Compact nc6320 laptop. The system eventually freezes, however, the time it freezes varies. Sometimes it happens during bootup, sometimes well after login. There are no error masages. Booting with kernel parameters noapic or acpi=off does not help. Removing the package klaptop doesn't work either. I'm happy to supply further information if necessary. #479709 was reported to be fixed in version 2.6.26-9. Does this fix the problem for you as well? Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#419034: linux-image-2.6-sparc32: kernel panic when module sd_mod is loaded before esp
On Fri, Apr 13, 2007 at 02:11:22PM +0200, nobody wrote: Package: linux-image-2.6-sparc32 Version: 2.6.18+6 Severity: critical Justification: breaks the whole system Loading module esp after sd_mod on a Sparc 4 causes a kernel panic. The behaviour is the same when the modules are loaded at boot time, and when the modules are manually loaded afterwards. Does this error still occur with more recent kernel versions? If you're running Etch, could you try to reproduce this bug with the 2.6.24 based kernel added in 4.0r4? http://packages.qa.debian.org/l/linux-2.6.24.html Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#452429: linux-image-2.6.22-3-amd64: Oops in udf_statfs
On Wed, Jul 02, 2008 at 05:07:42PM +0200, maximilian attems wrote: I had a USB2 DVD drive attached, with a DVD mounted (automatically), and I had mencoder running. I ran df -h, and got the following oops: can you reproduce it with 2.6.26-rc8 it has a severly reworked udf? old udf version are known to be easily oopsable. see trunk apt lines http://wiki.debian.org/DebianKernel thanks for feedback Josh, did you test this bug with a later kernel version? Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#455785: linux-image-2.6.18-5-686: machine fails to boot with usb cable connected
On Tue, Dec 11, 2007 at 11:22:24PM +0100, maximilian attems wrote: [ please keep bug report on cc ;-] On Tue, Dec 11, 2007 at 02:07:54PM -0800, Karen Brady wrote: The usb cable is attached to a ups backup battery. The program used to communicate with the battery is apcupsd. maximilian attems [EMAIL PROTECTED] wrote: On Tue, Dec 11, 2007 at 02:15:51PM -0600, kbrady wrote: Applied linux-image 2.6.18.dfsg.1-13etch5 this morning. Machine locked up on reboot. Last message displayed includes running scripts/local-top. Ran fine with linux-image 2.6.18.dfsg.1-13etch4. Machine has usb to ups cable plugged in. If usb cable is unplugged the machine boots fine. If cable is plugged in after boot machine also locks up. SIS usb controller. that would mean that your box hangs on loading acpi modules very early in boot. you may want to try out 2.6.22 from backports.org we will soon a newer alternative linux image to etch so you will be able soon to user newer directly. Does this error still occur with more recent kernel versions? If you're running Etch, could you try to reproduce this bug with the 2.6.24 based kernel added in 4.0r4? http://packages.qa.debian.org/l/linux-2.6.24.html Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#324724: dismally slow throughput to usb flash drive
On Fri, Oct 27, 2006 at 02:55:55PM -0400, Chris Roddy wrote: I installed linux-image-2.6.18-1-686 version 2.6.18-3 from sid earlier today, rebooted, and tested the exact same pieces of hardware as I was using in the initial report. There does not appear to be any significant change in write throughput when the device is mounted using the 'sync' option: disk writes are at about 46 kB/sec. As before, writes are fast when the device is not mounted 'sync', and reads are fast in either case. Shall I build linux-source-2.6.18 version 2.6.18-3 and try that? Or is there something else? Does this error still occur with more recent kernel versions? If you're running Etch, could you try to reproduce this bug with the 2.6.24 based kernel added in 4.0r4? http://packages.qa.debian.org/l/linux-2.6.24.html Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#492852: Wireless connects, but not to N networks
On Sun, Aug 17, 2008 at 07:50:42PM +0200, Sjoerd Hardeman wrote: Hi, I have problems connecting to my home network with the 2.6.25 kernel, to which I can connect flawlessly with the 2.6.24 kernel. On my system, it does bind to the network, but the following dhcp request fails due to a time-out. Connecting under the 2.6.25 kernel on my work network (which does not support the N-mode wifi) does work fine. I really have no idea about what kind of additional information I should send. In /var/log/syslog nothing more than the dhcp-time-outs appears. Please give me some clues on what to send, so that I can help sorting out the problem. Thanks in advance! There have been plenty of lwlwifi fixes in 2.6.26. Does updating to the current Lenny kernels fix the problem for you? Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#417927: parisc: SCSI devices get randomly offlined
On Thu, Apr 05, 2007 at 04:04:03PM +0200, Thibaut VARENE wrote: Package: linux-image-2.6-parisc64 Version: 2.6.18+5 Severity: important A bug which affects all parisc kernels since 2.6.18-rc2 affects the debian parisc kernel as well. Under some random circumstances, SCSI devices (such as the root disk) will get offlined, rendering the box totally unuseable: Does this error still occur with more recent kernel versions? Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#407792: Seen on 2.6.21 also
On Tue, Jul 03, 2007 at 09:41:23AM +1000, Hamish Moffatt wrote:
I am having this issue (cdrom drive appears confused) with
2.6.21-2-amd64 with this drive:
Jul 2 10:15:29 bach kernel: hda: LITE-ON DVDRW LH-18A1P, ATAPI CD/DVD-ROM
drive
Jul 2 15:22:19 bach kernel: hda: cdrom_pc_intr: The drive appears confused
(ireason = 0x01). Trying to recover by ending request.
Jul 2 15:32:23 bach kernel: hda: cdrom_pc_intr: The drive appears confused
(ireason = 0x01). Trying to recover by ending request.
Jul 2 15:32:23 bach kernel: hda: status error: status=0x58 { DriveReady
SeekComplete DataRequest }
Jul 2 15:32:23 bach kernel: ide: failed opcode was: unknown
Jul 2 15:32:23 bach kernel: hda: drive not ready for command
Jul 2 15:32:25 bach kernel: hda: status error: status=0x58 { DriveReady
SeekComplete DataRequest }
Jul 2 15:32:25 bach kernel: ide: failed opcode was: unknown
Jul 2 15:32:25 bach kernel: hda: drive not ready for command
Jul 2 15:32:25 bach kernel: hda: status error: status=0x58 { DriveReady
SeekComplete DataRequest }
[and on, every 2 seconds as polled by hald]
Does this error still occur with more recent kernel versions?
Cheers,
Moritz
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#350879: linux-image-2.6.15-1-k7: ide-floppy does not create hdx4 device for iomega ATA zip drive
On Wed, Feb 01, 2006 at 11:07:15PM +1300, Srdjan wrote: Package: linux-image-2.6.15-1-k7 Version: 2.6.15-3 Severity: normal This is what dmesg says: VP_IDE: IDE controller at PCI slot :00:04.1 VP_IDE: chipset revision 16 VP_IDE: not 100% native mode: will probe irqs later VP_IDE: VIA vt82c686a (rev 22) IDE UDMA66 controller on pci:00:04.1 ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:DMA ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:pio, hdd:pio Does this error still occur with more recent kernel versions? Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#408746: closed by maximilian attems m...@stro.at (re: snd* modules are not autoloaded when udev is installed)
On Fri, May 30, 2008 at 02:31:34AM +0200, Vincent Lefevre wrote: reopen 408746 found 408746 2.6.25-4 thanks While I didn't have any problem with linux-image-2.6.25-2-powerpc 2.6.25-3 (at the same time, udev was installed due to dependencies, because I had to replace the buggy yaird by initramfs-tools) just after installing it and rebooting on it, the problem reappeared since, though I didn't change anything in the config of the machine. However /dev/mixer disappeared for an unknown reason (see below). Does this error still occur with the current Lenny kernel? Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#411098: number of crashes reduced but not completely disappeared
On Fri, Feb 16, 2007 at 10:37:59AM +0100, Wolfram Sieber wrote: Yesterday, I mentioned I didn't encounter any crashes anymore after uninstalling hal and acpid package. -- Well, the crashes are still there, despite much less frequently. Does this error still occur with more recent kernel versions? If you're running Etch, could you try to reproduce this bug with the 2.6.24 based kernel added in 4.0r4? http://packages.qa.debian.org/l/linux-2.6.24.html Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#505639: udev loads rndis_host for ACM modem and crash the kernel
reassign 505639 linux-2.6 thanks On Nov 14, Michelle Konzack [EMAIL PROTECTED] wrote: So it seems, my device is CDC ethernet capable but there is definitively a bug in udev/modprobe/kernel. Yes, in the kernel. It's typical of bugs which crash it. While reading the documentation from udev I have nothing found, HOW to blacklist the modules Maybe because it is a function of module-init-tools. -- ciao, Marco signature.asc Description: Digital signature
Processed: Re: Bug#505639: udev loads rndis_host for ACM modem and crash the kernel
Processing commands for [EMAIL PROTECTED]: reassign 505639 linux-2.6 Bug#505639: udev loads rndis_host for ACM modem and crash the kernel Bug reassigned from package `udev' to `linux-2.6'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#357065: linux-image-2.6-r4k-ip22 immediately reboots on Indy 200MHz R4400
On Mon, Mar 27, 2006 at 07:02:16PM +0200, Thomas Jahns wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On 2006-03-27 18:15, Frans Pop wrote: On Monday 27 March 2006 16:58, Thomas Jahns wrote: Please comment. But with non-working PS/2 keyboard and non-working /etc/fstab for both kernel version, the 2.6.16 image is pretty worthless to me at this moment. You could try using the rescue mode [1] of the Etch Beta 2 release [2] of Debian Installer to correct your /etc/fstab. I'm not too keen on constantly swapping two incompatible versions of /etc/fstab. And since I expect it'll take some time before all drivers which are working in 2.4.27 also do in 2.6 that would be necessary for too long to be practical. Does this error still occur with more recent kernel versions? Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Scheduling linux-2.6 2.6.26-10
In #364672 it has been reported that suspend problems with the snd-intel8x0 driver can be resolved by disabling CONFIG_SND_AC97_POWER_SAVE (which is marked as EXPERIMENTAL after all). Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#499953: linux-image-2.6.26-1-amd64: Webcam hangs
Hi Luis, On Wed, Sep 24, 2008 at 12:15:52AM +0200, Luis Carlos Oliveira Carvalheiro wrote: Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-5 Severity: important When I try to use my webcam (motion eye webcam in a sony vaio vgn-fe41s) with cheese, xawtv and others, sometimes it hangs (webcam light doesn't even turn on) and I get the drivers/media/video/videobuf-core.c:137 bug in syslog The upstream bug tracker contains a patch for this issue: http://bugs.mediati.org/r5u870/issue19 Can you verify that it fixes the problem for you? Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
