Bug#490903: regression: kernel panic on boot with megaraid_mbox driver
Package: linux-image-2.6.25-2-686 Version: 2.6.25-6 Severity: important I just attempted to upgrade to 2.6.25-2-686 and discovered that if .25 were released as is, I'd be unable to use debian on this system. The kernel panics during boot. It happens after entering cryptsetup password and occurs in the megaraid_mbox driver. Based on when it happens and the driver it happens to I am guessing it is a result of the st tape driver (the part that (used to?) gives the block count and such. (The inital st driver load seems to be okay, although the messages scroll by too quickly for me to be sure, but if it loads at the same time as before the load of st driver succeeds, but when it tries to attach to a specific drive it panics. This is a Dell PERC3/DC RAID controller which is basically an AMI MegaRAID Elite 1600. I, however, have one channel for the RAID, and a second channel for a scanner and tape drive (non-RAID). It works fine with 2.6.24-1-686 which I am back to using for now. -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.25-2-686 depends on: ii debconf [debconf-2.0] 1.5.22 Debian configuration management sy ii initramfs-tools [linux-initra 0.92e 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.25-2-686 recommends: ii libc6-i6862.7-10 GNU C Library: Shared libraries [i -- debconf information: shared/kernel-image/really-run-bootloader: true linux-image-2.6.25-2-686/preinst/abort-install-2.6.25-2-686: linux-image-2.6.25-2-686/preinst/overwriting-modules-2.6.25-2-686: true linux-image-2.6.25-2-686/prerm/would-invalidate-boot-loader-2.6.25-2-686: true linux-image-2.6.25-2-686/preinst/elilo-initrd-2.6.25-2-686: true linux-image-2.6.25-2-686/postinst/bootloader-test-error-2.6.25-2-686: linux-image-2.6.25-2-686/postinst/depmod-error-initrd-2.6.25-2-686: false linux-image-2.6.25-2-686/preinst/bootloader-initrd-2.6.25-2-686: true linux-image-2.6.25-2-686/preinst/lilo-has-ramdisk: linux-image-2.6.25-2-686/postinst/old-initrd-link-2.6.25-2-686: true linux-image-2.6.25-2-686/prerm/removing-running-kernel-2.6.25-2-686: true linux-image-2.6.25-2-686/postinst/bootloader-error-2.6.25-2-686: linux-image-2.6.25-2-686/preinst/initrd-2.6.25-2-686: linux-image-2.6.25-2-686/preinst/lilo-initrd-2.6.25-2-686: true linux-image-2.6.25-2-686/postinst/old-system-map-link-2.6.25-2-686: true linux-image-2.6.25-2-686/postinst/create-kimage-link-2.6.25-2-686: true linux-image-2.6.25-2-686/postinst/old-dir-initrd-link-2.6.25-2-686: true linux-image-2.6.25-2-686/preinst/abort-overwrite-2.6.25-2-686: linux-image-2.6.25-2-686/preinst/failed-to-move-modules-2.6.25-2-686: linux-image-2.6.25-2-686/postinst/kimage-is-a-directory: linux-image-2.6.25-2-686/postinst/depmod-error-2.6.25-2-686: false -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#490906: linux-modules-nonfree-2.6: fglrx-module is outdated
tags 490906 +pending forwarded 490906 [EMAIL PROTECTED] thanks Hi, will be fixed by binNMU. Regards, Daniel -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: [EMAIL PROTECTED] Internet: http://people.panthera-systems.net/~daniel-baumann/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: linux-modules-nonfree-2.6: fglrx-module is outdated
Processing commands for [EMAIL PROTECTED]: tags 490906 +pending Bug#490906: linux-modules-nonfree-2.6: fglrx-module is outdated There were no tags set. Tags added: pending forwarded 490906 [EMAIL PROTECTED] Bug#490906: linux-modules-nonfree-2.6: fglrx-module is outdated Noted your statement that Bug has been forwarded to [EMAIL PROTECTED] 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#490959: linux-image-2.6.25-2-amd64: upgrade from 2.6.24 to 2.6.25 changes drive identities
Package: linux-image-2.6.25-2-amd64 Version: 2.6.25-6 Severity: important When upgrading to 2.6.25, the linux kernel re-assigns drive letters with respect to how it is done in 2.6.24. In my particular case, /dev/sdc is swapped with /dev/sdb. This will make a remote reboot unreliable and/or impossible, parameters used by the boot loader and fstab must be updated and even then the system keeps complaining about special devices which should be normal devices. This also happened, in reverse order, when upgrading from 2.6.18 to above. Nothing is changed in the BIOS. Booting into 2.6.24 says the root file system is on /dev/sdc, booting into 2.6.25 says the root file system is on /dev/sdb. -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.24-1-amd64 (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/bash Versions of packages linux-image-2.6.25-2-amd64 depends on: ii debconf [debconf-2.0] 1.5.22 Debian configuration management sy ii initramfs-tools [linux-initra 0.92e tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo linux-image-2.6.25-2-amd64 recommends no packages. -- debconf information: shared/kernel-image/really-run-bootloader: true linux-image-2.6.25-2-amd64/preinst/abort-overwrite-2.6.25-2-amd64: linux-image-2.6.25-2-amd64/prerm/removing-running-kernel-2.6.25-2-amd64: true linux-image-2.6.25-2-amd64/postinst/old-initrd-link-2.6.25-2-amd64: true linux-image-2.6.25-2-amd64/postinst/create-kimage-link-2.6.25-2-amd64: true linux-image-2.6.25-2-amd64/preinst/failed-to-move-modules-2.6.25-2-amd64: linux-image-2.6.25-2-amd64/preinst/abort-install-2.6.25-2-amd64: linux-image-2.6.25-2-amd64/postinst/kimage-is-a-directory: linux-image-2.6.25-2-amd64/postinst/depmod-error-2.6.25-2-amd64: false linux-image-2.6.25-2-amd64/postinst/bootloader-test-error-2.6.25-2-amd64: linux-image-2.6.25-2-amd64/postinst/old-system-map-link-2.6.25-2-amd64: true linux-image-2.6.25-2-amd64/prerm/would-invalidate-boot-loader-2.6.25-2-amd64: true linux-image-2.6.25-2-amd64/preinst/overwriting-modules-2.6.25-2-amd64: true linux-image-2.6.25-2-amd64/postinst/depmod-error-initrd-2.6.25-2-amd64: false linux-image-2.6.25-2-amd64/postinst/old-dir-initrd-link-2.6.25-2-amd64: true linux-image-2.6.25-2-amd64/preinst/elilo-initrd-2.6.25-2-amd64: true linux-image-2.6.25-2-amd64/postinst/bootloader-error-2.6.25-2-amd64: linux-image-2.6.25-2-amd64/preinst/lilo-initrd-2.6.25-2-amd64: true linux-image-2.6.25-2-amd64/preinst/lilo-has-ramdisk: linux-image-2.6.25-2-amd64/preinst/initrd-2.6.25-2-amd64: linux-image-2.6.25-2-amd64/preinst/bootloader-initrd-2.6.25-2-amd64: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#490959: marked as done (linux-image-2.6.25-2-amd64: upgrade from 2.6.24 to 2.6.25 changes drive identities)
Your message dated Tue, 15 Jul 2008 17:52:30 +0200 with message-id [EMAIL PROTECTED] and subject line Re: Bug#490959: linux-image-2.6.25-2-amd64: upgrade from 2.6.24 to 2.6.25 changes drive identities has caused the Debian Bug report #490959, regarding linux-image-2.6.25-2-amd64: upgrade from 2.6.24 to 2.6.25 changes drive identities 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.) -- 490959: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=490959 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.25-2-amd64 Version: 2.6.25-6 Severity: important When upgrading to 2.6.25, the linux kernel re-assigns drive letters with respect to how it is done in 2.6.24. In my particular case, /dev/sdc is swapped with /dev/sdb. This will make a remote reboot unreliable and/or impossible, parameters used by the boot loader and fstab must be updated and even then the system keeps complaining about special devices which should be normal devices. This also happened, in reverse order, when upgrading from 2.6.18 to above. Nothing is changed in the BIOS. Booting into 2.6.24 says the root file system is on /dev/sdc, booting into 2.6.25 says the root file system is on /dev/sdb. -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.24-1-amd64 (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/bash Versions of packages linux-image-2.6.25-2-amd64 depends on: ii debconf [debconf-2.0] 1.5.22 Debian configuration management sy ii initramfs-tools [linux-initra 0.92e tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo linux-image-2.6.25-2-amd64 recommends no packages. -- debconf information: shared/kernel-image/really-run-bootloader: true linux-image-2.6.25-2-amd64/preinst/abort-overwrite-2.6.25-2-amd64: linux-image-2.6.25-2-amd64/prerm/removing-running-kernel-2.6.25-2-amd64: true linux-image-2.6.25-2-amd64/postinst/old-initrd-link-2.6.25-2-amd64: true linux-image-2.6.25-2-amd64/postinst/create-kimage-link-2.6.25-2-amd64: true linux-image-2.6.25-2-amd64/preinst/failed-to-move-modules-2.6.25-2-amd64: linux-image-2.6.25-2-amd64/preinst/abort-install-2.6.25-2-amd64: linux-image-2.6.25-2-amd64/postinst/kimage-is-a-directory: linux-image-2.6.25-2-amd64/postinst/depmod-error-2.6.25-2-amd64: false linux-image-2.6.25-2-amd64/postinst/bootloader-test-error-2.6.25-2-amd64: linux-image-2.6.25-2-amd64/postinst/old-system-map-link-2.6.25-2-amd64: true linux-image-2.6.25-2-amd64/prerm/would-invalidate-boot-loader-2.6.25-2-amd64: true linux-image-2.6.25-2-amd64/preinst/overwriting-modules-2.6.25-2-amd64: true linux-image-2.6.25-2-amd64/postinst/depmod-error-initrd-2.6.25-2-amd64: false linux-image-2.6.25-2-amd64/postinst/old-dir-initrd-link-2.6.25-2-amd64: true linux-image-2.6.25-2-amd64/preinst/elilo-initrd-2.6.25-2-amd64: true linux-image-2.6.25-2-amd64/postinst/bootloader-error-2.6.25-2-amd64: linux-image-2.6.25-2-amd64/preinst/lilo-initrd-2.6.25-2-amd64: true linux-image-2.6.25-2-amd64/preinst/lilo-has-ramdisk: linux-image-2.6.25-2-amd64/preinst/initrd-2.6.25-2-amd64: linux-image-2.6.25-2-amd64/preinst/bootloader-initrd-2.6.25-2-amd64: true ---End Message--- ---BeginMessage--- On Tue, Jul 15, 2008 at 05:22:15PM +0200, Rutger ter Borg wrote: Package: linux-image-2.6.25-2-amd64 Version: 2.6.25-6 Severity: important When upgrading to 2.6.25, the linux kernel re-assigns drive letters with respect to how it is done in 2.6.24. In my particular case, /dev/sdc is swapped with /dev/sdb. This will make a remote reboot unreliable and/or impossible, parameters used by the boot loader and fstab must be updated and even then the system keeps complaining about special devices which should be normal devices. This also happened, in reverse order, when upgrading from 2.6.18 to above. Nothing is changed in the BIOS. Booting into 2.6.24 says the root file system is on /dev/sdc, booting into 2.6.25 says the root file system is on /dev/sdb. right device names are userspace policy never guaranteed to stay stable. use UUID to prevent that. grub by default now uses UUID. just mv menu.lst and regenerate it with update-grub. sorry for the trouble, but known fact and errata of d-i. best regards -- maks ---End Message---
Possible problems in your Debian packages
=== linux-2.6: = 2 bug(s) that should be fixed for the next Debian release: - #440445 http://bugs.debian.org/440445 linux-2.6 - dies after some time on t2000 since .22 - #490910 http://bugs.debian.org/490910 linux-2.6: CVE-2008-0598 information disclosure interesting stuff probably ends here This is an automated mail. These mails are sent two times per month. For more information about these mails, refer to http://wiki.debian.org/qa.debian.org/DdpoByMail We are sorry if this mail was useless for you. If you think it was avoidable (that we can detect easily that the problems weren't actually problems), please reply to it and let us know. If you don't want to receive this type of mail any more, you can reply to this mail and use one of the following commands at the beginning of the mail: - only1permonth email You will only receive this mail once per month, not twice. - unsubscribe email You will no longer receive any mail for any package. If you received this email because you are subscribed to packages on the PTS, this won't remove your PTS subscription. - ignore package email You will no longer receive information about that package in those mails. So if that package is the only one with problems, you won't receive anything. - ignore bug email You will no longer receive information about this bug. All commands are manually processed, but you will receive confirmation. The commands are just here so that we know precisely what you want. A more detailed status of your packages is available from the DDPO. See: http://qa.debian.org/[EMAIL PROTECTED] Don't hesitate to reply to this mail if you have questions. The wiki page will be updated with useful information. -- DDPOMail, run by Lucas Nussbaum -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#486365: linux-source-2.6.25: ntfs works again in 2.6.25-7
Package: linux-source-2.6.25 Followup-For: Bug #486365 The problem is gone after recompiling my kernel from the Debian sources version 2.6.25-7. Thanks! -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.25-flo (SMP w/2 CPU cores; PREEMPT) 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 linux-source-2.6.25 depends on: ii binutils2.18.1~cvs20080103-7 The GNU assembler, linker and bina ii bzip2 1.0.5-0.1high-quality block-sorting file co Versions of packages linux-source-2.6.25 recommends: ii gcc 4:4.3.1-2 The GNU C compiler ii libc6-dev [libc-dev] 2.7-12 GNU C Library: Development Librari ii make 3.81-5 The GNU version of the make util -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Bug#490816: tulip has no link detection, under VirtualPC and Hyper-V)
Processing commands for [EMAIL PROTECTED]: notforwarded 490816 Bug#490816: network-manager: Disconnects wired interface when started, under VirtualPC and Hyper-V Bug is not marked as having been forwarded. retitle 490816 linux-image-2.6-686: tulip has no detection under VirtualPC and Hyper-V Bug#490816: network-manager: Disconnects wired interface when started, under VirtualPC and Hyper-V Changed Bug title to `linux-image-2.6-686: tulip has no detection under VirtualPC and Hyper-V' from `network-manager: Disconnects wired interface when started, under VirtualPC and Hyper-V'. reassign 490816 linux-image-2.6-686 Bug#490816: linux-image-2.6-686: tulip has no detection under VirtualPC and Hyper-V Bug reassigned from package `network-manager' to `linux-image-2.6-686'. 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#490984: linux-image-2.6-686: / is busy causes EXT3-fs: INFO: recovery required on readonly filesystem
Package: linux-image-2.6-686 Version: 2.6.25+14 Severity: normal Thanks for maintaining debian's kernel packages. They're a remarkable technology in more ways than one. Here's how I duplicate the bug. 1.) $ shutdown -r now 2.) ctl-alt-F7 3.) look quickly for something like mount: / is busy 4.) After the system has rebooted, if the root filesystem is EXT3, look for EXT3-fs: INFO: recovery required on readonly filesystem. in /var/log/messages. If the root filesystem is EXT2, I get a long, slow fsck recovery. It seems to me that this can be partially explained by the shutdown command running a script named /etc/init.d/umountroot which calls the mount command to remount the root file system as read only. It fails, and complains that / is busy Since the root file system wasn't cleanly unmounted, it'll be recovered during the next boot. I investigated other processes interfering with the root file system, without result. However, it seems that inserting cat /proc/mounts just before the (re)mount command in /etc/init.d/umountroot usually allows mount to complete. As an aside, the words mount and remount occur hundreds of times in the changelog for 2.6.26. Frankly, I'm a little worried about data corrutpion. Thanks, Kingsley -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.25-2-686 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages linux-image-2.6-686 depends on: ii linux-image-2.6.25-2-686 2.6.25-6 Linux 2.6.25 image on PPro/Celeron linux-image-2.6-686 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#385553: Bug#484019: Bug#385553: linux-modules-extra-2.6: Please provide pre-built ndiswrapper modules
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi :) Uploading to ftp-master (via ftp to ftp-master.debian.org): ndiswrapper_1.53-1.dsc: done. ndiswrapper_1.53.orig.tar.gz: done. ndiswrapper_1.53-1.diff.gz: done. ndiswrapper-common_1.53-1_all.deb: done. ndiswrapper-source_1.53-1_all.deb: done. ndiswrapper-utils-1.9_1.53-1_amd64.deb: done. ndiswrapper_1.53-1_amd64.changes: done. Successfully uploaded packages. Cheers, Bernd - -- Bernd Zeimetz Debian GNU/Linux Developer GPG Fingerprint: 06C8 C9A2 EAAD E37E 5B2C BE93 067A AD04 C93B FF79 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkh9BsYACgkQBnqtBMk7/3ky1ACggPdnkqAapmSD/l0usZjYtHY6 D3QAn3bc+ssIsYiXoEq1CO4LspE8XPVC =mM1Y -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#490994: gspca-modules-2.6.25-2-686: After dist upgrade webcam stop working (15.08.2008) 2.6.25-2
Package: gspca-modules-2.6.25-2-686 Version: 2.6.25+01.00.20-5 Severity: important Hello, After upgrade system (aptitude dist-upgrade) my webcam stop working. Webcam model -Vimicro zc301 Please fix this. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages gspca-modules-2.6.25-2-686 depends on: ii linux-image-2.6.25-2-686 [lin 2.6.25-6 Linux 2.6.25 image on PPro/Celeron gspca-modules-2.6.25-2-686 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: 490816 forwarded
Processing commands for [EMAIL PROTECTED]: forwarded 490816 http://bugzilla.kernel.org/show_bug.cgi?id=11092 Bug#490816: linux-image-2.6-686: tulip has no detection under VirtualPC and Hyper-V Noted your statement that Bug has been forwarded to http://bugzilla.kernel.org/show_bug.cgi?id=11092. 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]
Processed: Re: Bug#490994: gspca-modules-2.6.25-2-686: After dist upgrade webcam stop working (15.08.2008) 2.6.25-2
Processing commands for [EMAIL PROTECTED]: reassign 490994 gspca-source Bug#490994: gspca-modules-2.6.25-2-686: After dist upgrade webcam stop working (15.08.2008) 2.6.25-2 Bug reassigned from package `gspca-modules-2.6.25-2-686' to `gspca-source'. 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#486365: marked as done (linux-source-2.6.25: unable to mount ntfs partitions: OOPS ntfs:load_system_files+0x6ce/0x1892)
Your message dated Wed, 16 Jul 2008 01:18:05 +0200 with message-id [EMAIL PROTECTED] and subject line Re: Bug#486365: linux-source-2.6.25: ntfs works again in 2.6.25-7 has caused the Debian Bug report #486365, regarding linux-source-2.6.25: unable to mount ntfs partitions: OOPS ntfs:load_system_files+0x6ce/0x1892 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.) -- 486365: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=486365 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-source-2.6.25 Version: 2.6.25-5 Severity: normal Hi, the transition from 2.6.25-4 to 2.6.25-5 broke mounting of NTFS partitions for me. (I did not change my kernel configuration.) Here is the relevant part of my syslog: NTFS driver 2.1.29 [Flags: R/W MODULE]. BUG: unable to handle kernel paging request at c2001053e000 IP: [882bcd57] :ntfs:load_system_files+0x6ce/0x1892 PGD 3f12f067 PUD 3f130067 PMD 3eaa4067 PTE 0 Oops: [1] PREEMPT SMP CPU 0 Modules linked in: nls_utf8 ntfs fuse dm_crypt crypto_blkcipher dm_snapshot dm_mirror dm_mod snd_hda_intel snd_pcm_oss snd_mixer_oss snd_pcm snd_timer i2c_i801 parport_pc snd psmouse parport i2c_core rtc serio_raw soundcore iTCO_wdt snd_page_alloc button intel_agp dcdbas evdev ext3 jbd mbcache sg sr_mod cdrom sd_mod ide_pci_generic ide_core usbhid hid ata_piix ata_generic libata scsi_mod dock tg3 ehci_hcd uhci_hcd thermal processor fan Pid: 1941, comm: mount Not tainted 2.6.25-flo #1 RIP: 0010:[882bcd57] [882bcd57] :ntfs:load_system_files+0x6ce/0x1892 RSP: 0018:81003d85dbf8 EFLAGS: 00010287 RAX: c2001053f000 RBX: RCX: 0001fffe RDX: RSI: 0001 RDI: c2001051e000 RBP: 81003ebd2000 R08: 0e00 R09: 8000 R10: 8100b000 R11: 882b1980 R12: 0020 R13: 81003ee17178 R14: 81003e2d9400 R15: FS: 7fe8b111f7e0() GS:8051a000() knlGS: CS: 0010 DS: ES: CR0: 8005003b CR2: c2001053e000 CR3: 3da68000 CR4: 06e0 DR0: DR1: DR2: DR3: DR6: 0ff0 DR7: 0400 Process mount (pid: 1941, threadinfo 81003d85c000, task 81003db76810) Stack: c2001053dfff 81003d85dc88 8163 80201c20 1053e000 c2001053e000 00043f12f000 0001 e20664e8 81003e2d9400 0020 81003e2d9400 Call Trace: [882bf1d0] ? :ntfs:generate_default_upcase+0x44/0xdc [882be7cf] ? :ntfs:ntfs_fill_super+0x8b4/0xd03 [8028b6cc] ? set_bdev_super+0x0/0xf [882bdf1b] ? :ntfs:ntfs_fill_super+0x0/0xd03 [8028c8ba] ? get_sb_bdev+0x107/0x155 [8028c4f7] ? vfs_kern_mount+0x95/0x11a [8028c5cf] ? do_kern_mount+0x43/0xdd [8029ff51] ? do_new_mount+0x5b/0x95 [802a0f2b] ? do_mount+0x1b1/0x1de [8041f56f] ? _spin_lock+0xe/0x24 [80267fae] ? __get_free_pages+0xe/0x4d [802a0fe2] ? sys_mount+0x8a/0xd8 [8020bdeb] ? system_call_after_swapgs+0x7b/0x80 Code: 3d 97 8d 01 00 48 85 ff 74 7f 8b 45 78 be 00 00 01 00 3d 00 00 01 00 0f 42 f0 31 db 31 c9 eb 19 48 8b 85 80 00 00 00 66 8b 14 08 8b 04 0f 48 83 c1 02 66 39 c2 75 06 ff c3 39 f3 7c e3 39 f3 75 RIP [882bcd57] :ntfs:load_system_files+0x6ce/0x1892 RSP 81003d85dbf8 CR2: c2001053e000 ---[ end trace c5fe78e7733adca5 ]--- I have found an upstream bug, a regression reported against 2.6.26-rc5, which may be related: http://bugzilla.kernel.org/show_bug.cgi?id=10865 -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.25-flo (SMP w/2 CPU cores; PREEMPT) 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 linux-source-2.6.25 depends on: ii binutils2.18.1~cvs20080103-6 The GNU assembler, linker and bina ii bzip2 1.0.5-0.1high-quality block-sorting file co Versions of packages linux-source-2.6.25 recommends: ii gcc 4:4.3.0-8 The GNU C compiler ii libc6-dev [libc-dev] 2.7-12 GNU C Library: Development Librari ii make 3.81-5 The GNU version of the make util -- no debconf information ---End Message--- ---BeginMessage--- Version:
Bug#490293: marked as done (linux-image-2.6.24-etchnhalf.1-686: CONFIG_SMB_FS is not set)
Your message dated Wed, 16 Jul 2008 01:28:07 +0200 with message-id [EMAIL PROTECTED] and subject line Re: Bug#490293: linux-image-2.6.24-etchnhalf.1-686: CONFIG_SMB_FS is not set has caused the Debian Bug report #490293, regarding linux-image-2.6.24-etchnhalf.1-686: CONFIG_SMB_FS is not set 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.) -- 490293: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=490293 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.24-etchnhalf.1-686 Version: 2.6.24-6~etchnhalf.3 Severity: wishlist CONFIG_SMB_FS is not set in the kernel config. it would be nice to have smbfs -- Package-specific info: -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable'), (103, 'proposed-updates') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.21-1-k7 Locale: LANG=hu_HU.UTF-8, LC_CTYPE=hu_HU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Versions of packages linux-image-2.6.24-etchnhalf.1-686 depends on: ii debconf [debconf-2.0]1.5.11etch1 Debian configuration management sy ii initramfs-tools [linux-initr 0.85h tools for generating an initramfs ii module-init-tools3.3-pre4-2 tools for managing Linux kernel mo Versions of packages linux-image-2.6.24-etchnhalf.1-686 recommends: ii libc6-i686 2.3.6.ds1-13etch5 GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.24-etchnhalf.1-686/postinst/depmod-error-2.6.24-etchnhalf.1-686: false linux-image-2.6.24-etchnhalf.1-686/postinst/old-dir-initrd-link-2.6.24-etchnhalf.1-686: true linux-image-2.6.24-etchnhalf.1-686/preinst/initrd-2.6.24-etchnhalf.1-686: linux-image-2.6.24-etchnhalf.1-686/postinst/kimage-is-a-directory: linux-image-2.6.24-etchnhalf.1-686/preinst/abort-install-2.6.24-etchnhalf.1-686: linux-image-2.6.24-etchnhalf.1-686/prerm/removing-running-kernel-2.6.24-etchnhalf.1-686: true linux-image-2.6.24-etchnhalf.1-686/preinst/lilo-has-ramdisk: linux-image-2.6.24-etchnhalf.1-686/postinst/bootloader-error-2.6.24-etchnhalf.1-686: linux-image-2.6.24-etchnhalf.1-686/postinst/old-initrd-link-2.6.24-etchnhalf.1-686: true linux-image-2.6.24-etchnhalf.1-686/preinst/bootloader-initrd-2.6.24-etchnhalf.1-686: true linux-image-2.6.24-etchnhalf.1-686/preinst/elilo-initrd-2.6.24-etchnhalf.1-686: true shared/kernel-image/really-run-bootloader: true linux-image-2.6.24-etchnhalf.1-686/preinst/abort-overwrite-2.6.24-etchnhalf.1-686: linux-image-2.6.24-etchnhalf.1-686/prerm/would-invalidate-boot-loader-2.6.24-etchnhalf.1-686: true linux-image-2.6.24-etchnhalf.1-686/preinst/overwriting-modules-2.6.24-etchnhalf.1-686: true linux-image-2.6.24-etchnhalf.1-686/postinst/old-system-map-link-2.6.24-etchnhalf.1-686: true linux-image-2.6.24-etchnhalf.1-686/postinst/depmod-error-initrd-2.6.24-etchnhalf.1-686: false linux-image-2.6.24-etchnhalf.1-686/preinst/lilo-initrd-2.6.24-etchnhalf.1-686: true linux-image-2.6.24-etchnhalf.1-686/preinst/failed-to-move-modules-2.6.24-etchnhalf.1-686: linux-image-2.6.24-etchnhalf.1-686/postinst/bootloader-test-error-2.6.24-etchnhalf.1-686: linux-image-2.6.24-etchnhalf.1-686/postinst/create-kimage-link-2.6.24-etchnhalf.1-686: true ---End Message--- ---BeginMessage--- On Fri, 11 Jul 2008, Hámorszky Balázs wrote: Package: linux-image-2.6.24-etchnhalf.1-686 Version: 2.6.24-6~etchnhalf.3 Severity: wishlist CONFIG_SMB_FS is not set in the kernel config. it would be nice to have smbfs deprecated, use cifs. -- maks ---End Message---
Bug#489190: ps/2 mouse not working in 2.6.24
On Thu, 10 Jul 2008, Guillaume Morin wrote: I also have an i8042 chip. The reports seem to have all this in common. I tried the few workarounds in the ubuntu thread posted to noavail. But after some more digging, I triedpassing i8042.nomux i8042.noloop to the kernel command line and it fixed problem! This should definitely be passed on to the maintainer of the i8042 driver. can you please file upstream in bugzilla.kernel.org and let us know the bug number. thanks -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#490698: marked as done (linux-image-2.6.24-1-amd64: Linux-image 2.6.xx_AMD_64 - no bigmem version)
Your message dated Wed, 16 Jul 2008 01:25:18 +0200 with message-id [EMAIL PROTECTED] and subject line Re: Bug#490698: linux-image-2.6.24-1-amd64: Linux-image 2.6.xx_AMD_64 - no bigmem version has caused the Debian Bug report #490698, regarding linux-image-2.6.24-1-amd64: Linux-image 2.6.xx_AMD_64 - no bigmem version 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.) -- 490698: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=490698 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.24-1-amd64 Version: 2.6.24-5 Severity: wishlist ON debian repositories there is no bigmem version for amd_64 kernels. It will be beautiful to see it. Apt-cache says that bigmem versions are only for 686 arch. Nowadays it's easy to see computer with more than 6GB of ram and having a built version will be very useful. If someone can please add it !! it will be very appreciated. thanks in advance -- Package-specific info: ** Version: Linux version 2.6.24-1-amd64 (Debian 2.6.24-5) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080308 (prerelease) (Debian 4.1.2-21)) #1 SMP Thu Mar 27 16:52:38 UTC 2008 ** Command line: root=/dev/sda1 ro quiet ** Not tainted ** Loaded modules: Module Size Used by usbhid 35168 0 hid41792 1 usbhid ipt_REJECT 9216 0 xt_hashlimit 15768 3 ip6_tables 20040 1 xt_hashlimit ipt_REDIRECT6528 1 iptable_mangle 7424 1 xt_MARK 7296 5 xt_tcpudp 7936 22 xt_state7040 32 ipt_LOG10880 11 xt_limit7680 8 nf_nat_ftp 7936 0 nf_conntrack_irc 12192 0 nf_conntrack_ftp 14504 1 nf_nat_ftp iptable_nat12036 1 nf_nat 25644 3 ipt_REDIRECT,nf_nat_ftp,iptable_nat nf_conntrack_ipv4 24208 34 iptable_nat nf_conntrack 77936 7 xt_state,nf_nat_ftp,nf_conntrack_irc,nf_conntrack_ftp,iptable_nat,nf_nat,nf_conntrack_ipv4 iptable_filter 7680 1 ip_tables 25576 3 iptable_mangle,iptable_nat,iptable_filter x_tables 24712 11 ipt_REJECT,xt_hashlimit,ip6_tables,ipt_REDIRECT,xt_MARK,xt_tcpudp,xt_state,ipt_LOG,xt_limit,iptable_nat,ip_tables sbs20880 0 dock 16032 0 ac 11400 0 battery19976 0 video 25620 0 output 8704 1 video container 9856 0 loop 22788 0 firewire_sbp2 20624 0 snd_hda_intel 362024 0 snd_pcm89352 1 snd_hda_intel iTCO_wdt 17488 0 snd_timer 28552 1 snd_pcm snd65896 3 snd_hda_intel,snd_pcm,snd_timer i2c_i801 13852 0 soundcore 13216 1 snd shpchp 38428 0 i2c_core 29824 1 i2c_i801 snd_page_alloc 15248 2 snd_hda_intel,snd_pcm i5000_edac 14728 0 pcspkr 7808 0 evdev 17024 0 sbshc 12032 1 sbs button 13984 0 edac_core 53776 3 i5000_edac pci_hotplug35504 1 shpchp ext3 139024 9 jbd55976 1 ext3 mbcache13952 1 ext3 raid0 12032 1 md_mod 84380 2 raid0 sd_mod 33536 14 ide_cd 44704 0 cdrom 39464 1 ide_cd ata_piix 25092 12 ata_generic13060 0 libata162736 2 ata_piix,ata_generic scsi_mod 170296 3 firewire_sbp2,sd_mod,libata piix 13316 0 [permanent] e1000 127296 0 firewire_ohci 24192 0 firewire_core 49472 2 firewire_sbp2,firewire_ohci crc_itu_t 6656 1 firewire_core generic 9732 0 [permanent] ide_core 144920 3 ide_cd,piix,generic uhci_hcd 30112 0 ehci_hcd 39692 0 e1000e118692 0 thermal22688 0 processor 45032 1 thermal fan 9864 0 ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 5000X Chipset Memory Controller Hub [8086:25c0] (rev 31) Subsystem: Intel Corporation Device [8086:7270] Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast
Re: [Pkg-xen-devel] Xen status in lenny?
On Tue, Jul 15, 2008 at 05:22:55PM +0300, Pasi Kärkkäinen wrote: snip Hopefully Jeremy Fitzhardinge (from Xensource) and others can get the important Xen kernel features ported to pv_ops framework and integrated into vanilla linus kernels soon.. Status/todo: http://wiki.xensource.com/xenwiki/XenParavirtOps Redhat/Fedora pv_ops Xen kernel dom0 support status: http://fedoraproject.org/wiki/Features/XenPvopsDom0 SLES 11 will include Linux 2.6.26 with Xen patches - packages should be available any day now from ftp://ftp.suse.com/pub/projects/kernel/kotd/SL110_BRANCH/i386/. Is it possible that those patches will be usable in lenny, as I believe the kernel team expects to release with Linux 2.6.26? Ben. -- Ben Hutchings Beware of bugs in the above code; I have only proved it correct, not tried it. - Donald Knuth signature.asc Description: Digital signature
Bug#490903: linux-image-2.6.25-2-686: It's the scanner that confuses the kernel
Package: linux-image-2.6.25-2-686 Version: 2.6.25-6 Followup-For: Bug #490903 I just did a boot with the SCSI-2 scanner disconnected and 2.6.25-2 boots sucessfully in that configuration with the megaraid. I suspect it is the SCSI-2 scanner as a non-RAID device on channel 2 that is confusing the megaraid_mbox driver. It worked with 2.6.24-1 though, so it is still a regression, just not as serious since it means I can't use my scanner, but can use my tape drive and channel 1 raid array. The scanner is connected with adaptors and cable that allow the SE SCSI-2 scanner to connect to the LVD Ultra-2 RAID controller (not custom stuff though) (with the controller configured for SCSI-2 Fast). -- Package-specific info: ** Version: Linux version 2.6.25-2-686 (Debian 2.6.25-6) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Fri Jun 27 03:23:20 UTC 2008 ** Command line: root=/dev/mapper/Brennin-Root ro rootdelay=10 ** Not tainted ** Kernel log: [ 10.888197] sd 1:0:0:0: [sdb] Assuming drive cache: write through [ 10.888197] sdb: sdb1 [ 10.894878] sd 1:0:0:0: [sdb] Attached SCSI removable disk [ 11.379653] sd 2:0:0:0: [sdc] 7870464 512-byte hardware sectors (4030 MB) [ 11.386496] sd 2:0:0:0: [sdc] Write Protect is off [ 11.386496] sd 2:0:0:0: [sdc] Mode Sense: 03 00 00 00 [ 11.386496] sd 2:0:0:0: [sdc] Assuming drive cache: write through [ 11.396434] sd 2:0:0:0: [sdc] 7870464 512-byte hardware sectors (4030 MB) [ 11.401293] sd 2:0:0:0: [sdc] Write Protect is off [ 11.401293] sd 2:0:0:0: [sdc] Mode Sense: 03 00 00 00 [ 11.401293] sd 2:0:0:0: [sdc] Assuming drive cache: write through [ 11.401298] sdc: sdc1 [ 11.411373] sd 2:0:0:0: [sdc] Attached SCSI removable disk [ 15.882880] device-mapper: uevent: version 1.0.3 [ 15.885300] device-mapper: ioctl: 4.13.0-ioctl (2007-10-18) initialised: [EMAIL PROTECTED] [ 35.433628] PM: Starting manual resume from disk [ 35.479727] EXT3-fs: INFO: recovery required on readonly filesystem. [ 35.479727] EXT3-fs: write access will be enabled during recovery. [ 35.489013] kjournald starting. Commit interval 5 seconds [ 35.489013] EXT3-fs: recovery complete. [ 35.510703] EXT3-fs: mounted filesystem with ordered data mode. [ 37.793889] udevd version 124 started [ 39.362024] Linux agpgart interface v0.103 [ 39.398057] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [ 39.435851] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [ 39.478260] agpgart: Detected an Intel 845G Chipset. [ 39.485786] agpgart: AGP aperture is 128M @ 0xf000 [ 39.590967] ACPI: PCI Interrupt :00:1f.3[B] - GSI 17 (level, low) - IRQ 17 [ 39.631742] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.02 (26-Jul-2007) [ 39.631895] iTCO_wdt: failed to reset NO_REBOOT flag, reboot disabled by hardware [ 39.631966] iTCO_wdt: No card detected [ 39.668223] input: Power Button (FF) as /class/input/input1 [ 39.696295] ACPI: Power Button (FF) [PWRF] [ 39.696462] input: Power Button (CM) as /class/input/input2 [ 39.728300] ACPI: Power Button (CM) [PWRB] [ 39.932366] intel_rng: FWH not detected [ 41.193428] usblp0: USB Bidirectional printer dev 4 if 0 alt 0 proto 2 vid 0x04B8 pid 0x0005 [ 41.199192] usblp1: USB Bidirectional printer dev 5 if 0 alt 0 proto 2 vid 0x03F0 pid 0x3F17 [ 41.199301] usbcore: registered new interface driver usblp [ 41.638203] input: PC Speaker as /class/input/input3 [ 41.975523] rtc_cmos 00:05: rtc core: registered rtc_cmos as rtc0 [ 41.975621] rtc0: alarms up to one month [ 42.241961] gameport: NS558 PnP Gameport is pnp00:10/gameport0, io 0x200, speed 774kHz [ 42.524894] input: ImPS/2 Logitech Wheel Mouse as /class/input/input4 [ 42.536707] ACPI: PCI Interrupt :00:1f.5[B] - GSI 17 (level, low) - IRQ 17 [ 42.536845] PCI: Setting latency timer of device :00:1f.5 to 64 [ 42.555706] parport_pc 00:09: reported by Plug and Play ACPI [ 42.555825] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE] [ 42.860415] intel8x0_measure_ac97_clock: measured 54912 usecs [ 42.860480] intel8x0: clocking to 48000 [ 43.039919] no PnP irq, using polling [ 48.545068] st0: Block limits 1 - 16777215 bytes. [ 49.385680] EXT3 FS on dm-1, internal journal [ 49.722337] loop: module loaded [ 50.020367] QEMU Accelerator Module version 1.3.0, Copyright (c) 2005-2007 Fabrice Bellard [ 50.020507] KQEMU installed, max_locked_mem=518140kB. [ 50.082655] tun: Universal TUN/TAP device driver, 1.6 [ 50.082655] tun: (C) 1999-2004 Max Krasnyansky [EMAIL PROTECTED] [ 50.151384] fuse init (API version 7.9) [ 50.250178] aufs 20080609 [ 53.985367] kjournald starting. Commit interval 5 seconds [ 53.994289] EXT3 FS on sda1, internal journal [ 53.994289] EXT3-fs: mounted filesystem with ordered data mode. [ 54.066703] kjournald starting. Commit interval 5 seconds [ 54.085339] EXT3 FS on dm-7, internal journal [ 54.085339] EXT3-fs:
