Bug#402701: marked as done (linux-image-2.6.18-3-amd64: Nvidia driver does no longer work on amd64-Debian due to IOMMU config)
Your message dated Tue, 12 Dec 2006 08:22:23 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#402701: linux-image-2.6.18-3-amd64: Nvidia driver does no longer work on amd64-Debian due to IOMMU config has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: linux-image-2.6.18-3-amd64 Version: 2.6.18-7 Severity: normal Hi all, yesterday I upgraded my amd64 machine from kernel 2.6.17-2 to 2.6.18-3. After compiling the Nvidia driver the X server produces the following error messages (happens with driver version 8776 and 9631) : (EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device PCI:1:0:0. (EE) NVIDIA(0): Please see the COMMON PROBLEMS section in the README for (EE) NVIDIA(0): additional information.(EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device! (EE) NVIDIA(0): *** Aborting *** The kernel is sometimes showing this in syslog: titan kernel: NVRM: loading NVIDIA Linux x86_64 Kernel Module 1.0-9631 Thu Nov 9 17:35:27 PST 2006 titan kernel: NVRM: RmInitAdapter failed! (0x25:0x:1039) titan kernel: NVRM: rm_init_adapter(0) failed After some googleing I found a thread in a Gentoo forum saying that the IOMMU flag is set by default on the AMD64 kernels forcing the kernel agp driver to use instead of the nvagp from the Nvidia driver. The intermittent solution is to adjust the file arch/x86_64/Kconfig within the Linux source: replace this line... bool "IOMMU support" if EMBEDDED by ... bool "IOMMU support" and disable "IOMMU" in the kernel config. After compiling the kernel the Nvidia driver works like expected again. Regards, Joerg. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages linux-image-2.6.18-3-amd64 depends on: ii coreutil 5.97-5.2The GNU core utilities ii debconf 1.5.2 Debian configuration management sy ii e2fsprog 1.39+1.40-WIP-2006.11.14+dfsg-1 ext2 file system utilities and lib ii initramf 0.85b tools for generating an initramfs ii module-i 3.3-pre3-1 tools for managing Linux kernel mo linux-image-2.6.18-3-amd64 recommends no packages. -- debconf information: shared/kernel-image/really-run-bootloader: true linux-image-2.6.18-3-amd64/postinst/old-system-map-link-2.6.18-3-amd64: true linux-image-2.6.18-3-amd64/preinst/initrd-2.6.18-3-amd64: linux-image-2.6.18-3-amd64/postinst/bootloader-test-error-2.6.18-3-amd64: linux-image-2.6.18-3-amd64/postinst/kimage-is-a-directory: linux-image-2.6.18-3-amd64/preinst/abort-overwrite-2.6.18-3-amd64: linux-image-2.6.18-3-amd64/postinst/depmod-error-initrd-2.6.18-3-amd64: false linux-image-2.6.18-3-amd64/preinst/lilo-initrd-2.6.18-3-amd64: true linux-image-2.6.18-3-amd64/postinst/bootloader-error-2.6.18-3-amd64: linux-image-2.6.18-3-amd64/postinst/old-dir-initrd-link-2.6.18-3-amd64: true linux-image-2.6.18-3-amd64/preinst/bootloader-initrd-2.6.18-3-amd64: true linux-image-2.6.18-3-amd64/postinst/old-initrd-link-2.6.18-3-amd64: true linux-image-2.6.18-3-amd64/preinst/failed-to-move-modules-2.6.18-3-amd64: linux-image-2.6.18-3-amd64/preinst/elilo-initrd-2.6.18-3-amd64: true linux-image-2.6.18-3-amd64/prerm/removing-running-kernel-2.6.18-3-amd64: true linux-image-2.6.18-3-amd64/preinst/overwriting-modules-2.6.18-3-amd64: true linux-image-2.6.18-3-amd64/postinst/depmod-error-2.6.18-3-amd64: false linux-image-2.6.18-3-amd64/prerm/would-invalidate-boot-loader-2.6.18-3-amd64: true linux-image-2.6.18-3-amd64/postinst/create-kimage-link-2.6.18-3-amd64: true linux-image-2.6.18-3-amd64/preinst/lilo-has-ramdisk: linux-image-2.6.18-3-amd64/preinst/already-running-this-2.6.18-3-amd64: linux-image-2.6.18-3-amd64/preinst/abort-install-2.6.18-3-amd64: --- End Message --- --- Begin Message --- On Tue, Dec 12, 2006 at 07:44:04AM +0100, Joerg Morbitzer wrote: > yesterday I upgraded my amd64 machine from kernel 2.6.17-2 to > 2.6.18-3. After compiling the Nvidia driver the X server > produces the following error messages (happens with > driver version 8776 and 9631) : You have a tainted kernel, we can't support that in any way. Bastian -- No one wants war. -- Kirk, "Errand of Mercy", stardate 3201.7 --- End Message ---
Bug#402701: linux-image-2.6.18-3-amd64: Nvidia driver does no longer work on amd64-Debian due to IOMMU config
Package: linux-image-2.6.18-3-amd64 Version: 2.6.18-7 Severity: normal Hi all, yesterday I upgraded my amd64 machine from kernel 2.6.17-2 to 2.6.18-3. After compiling the Nvidia driver the X server produces the following error messages (happens with driver version 8776 and 9631) : (EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device PCI:1:0:0. (EE) NVIDIA(0): Please see the COMMON PROBLEMS section in the README for (EE) NVIDIA(0): additional information.(EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device! (EE) NVIDIA(0): *** Aborting *** The kernel is sometimes showing this in syslog: titan kernel: NVRM: loading NVIDIA Linux x86_64 Kernel Module 1.0-9631 Thu Nov 9 17:35:27 PST 2006 titan kernel: NVRM: RmInitAdapter failed! (0x25:0x:1039) titan kernel: NVRM: rm_init_adapter(0) failed After some googleing I found a thread in a Gentoo forum saying that the IOMMU flag is set by default on the AMD64 kernels forcing the kernel agp driver to use instead of the nvagp from the Nvidia driver. The intermittent solution is to adjust the file arch/x86_64/Kconfig within the Linux source: replace this line... bool "IOMMU support" if EMBEDDED by ... bool "IOMMU support" and disable "IOMMU" in the kernel config. After compiling the kernel the Nvidia driver works like expected again. Regards, Joerg. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages linux-image-2.6.18-3-amd64 depends on: ii coreutil 5.97-5.2The GNU core utilities ii debconf 1.5.2 Debian configuration management sy ii e2fsprog 1.39+1.40-WIP-2006.11.14+dfsg-1 ext2 file system utilities and lib ii initramf 0.85b tools for generating an initramfs ii module-i 3.3-pre3-1 tools for managing Linux kernel mo linux-image-2.6.18-3-amd64 recommends no packages. -- debconf information: shared/kernel-image/really-run-bootloader: true linux-image-2.6.18-3-amd64/postinst/old-system-map-link-2.6.18-3-amd64: true linux-image-2.6.18-3-amd64/preinst/initrd-2.6.18-3-amd64: linux-image-2.6.18-3-amd64/postinst/bootloader-test-error-2.6.18-3-amd64: linux-image-2.6.18-3-amd64/postinst/kimage-is-a-directory: linux-image-2.6.18-3-amd64/preinst/abort-overwrite-2.6.18-3-amd64: linux-image-2.6.18-3-amd64/postinst/depmod-error-initrd-2.6.18-3-amd64: false linux-image-2.6.18-3-amd64/preinst/lilo-initrd-2.6.18-3-amd64: true linux-image-2.6.18-3-amd64/postinst/bootloader-error-2.6.18-3-amd64: linux-image-2.6.18-3-amd64/postinst/old-dir-initrd-link-2.6.18-3-amd64: true linux-image-2.6.18-3-amd64/preinst/bootloader-initrd-2.6.18-3-amd64: true linux-image-2.6.18-3-amd64/postinst/old-initrd-link-2.6.18-3-amd64: true linux-image-2.6.18-3-amd64/preinst/failed-to-move-modules-2.6.18-3-amd64: linux-image-2.6.18-3-amd64/preinst/elilo-initrd-2.6.18-3-amd64: true linux-image-2.6.18-3-amd64/prerm/removing-running-kernel-2.6.18-3-amd64: true linux-image-2.6.18-3-amd64/preinst/overwriting-modules-2.6.18-3-amd64: true linux-image-2.6.18-3-amd64/postinst/depmod-error-2.6.18-3-amd64: false linux-image-2.6.18-3-amd64/prerm/would-invalidate-boot-loader-2.6.18-3-amd64: true linux-image-2.6.18-3-amd64/postinst/create-kimage-link-2.6.18-3-amd64: true linux-image-2.6.18-3-amd64/preinst/lilo-has-ramdisk: linux-image-2.6.18-3-amd64/preinst/already-running-this-2.6.18-3-amd64: linux-image-2.6.18-3-amd64/preinst/abort-install-2.6.18-3-amd64: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#336153: RC? Kernel 2.6 dm-crypt fs corruption
Shouldn't this "well known" bug in dm-crypt be fixed in both sarge and etch? Isn't fs corruption release critical? For others, see http://lists.debian.org/debian-kernel/2006/12/msg00099.html which points to http://www.spinics.net/lists/dm-crypt/msg00481.html Someone should ask if it should be queued for 2.6.16 too. Thanks, Drew Daniels Resume: http://www.boxheap.net/ddaniels/resume.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#402676: unable to handle kernel NULL pointer dereference at virtual address 00000100
Package: linux-source-2.6.18 Version: 2.6.18-7 Severity: normal Dec 12 02:00:22 kernel: BUG: unable to handle kernel NULL pointer dereference at virtual address 0100 Dec 12 02:00:22 kernel: printing eip: Dec 12 02:00:22 kernel: c0130adb Dec 12 02:00:22 kernel: *pde = Dec 12 02:00:22 kernel: Oops: [#1] Dec 12 02:00:22 kernel: Modules linked in: af_packet nfs nfsd exportfs lockd nfs_acl sunrpc ipt_LOG xt_limit xt_state xt_multiport iptable_filter ipt_REDIRECT xt_tcpudp iptable_nat ip_tables x_tables ip_nat_ftp ip_nat ip_conntrack_ftp ip_conntrack nfnetlink ext2 dm_mod floppy ne pcspkr ext3 jbd mbcache ide_cd cdrom ide_disk ide_generic generic ide_core 3c59x mii ne2k_pci 8390 crc32 unix Dec 12 02:00:22 kernel: CPU:0 Dec 12 02:00:22 kernel: EIP:0060:[]Not tainted VLI Dec 12 02:00:22 kernel: EFLAGS: 00010006 (2.6.18-7.pentium1.1 #1) Dec 12 02:00:22 kernel: EIP is at find_get_page+0x1b/0x30 Dec 12 02:00:22 kernel: eax: c0fa04d8 ebx: c88f1cd0 ecx: 0100 edx: Dec 12 02:00:22 kernel: esi: edi: c0fa04d4 ebp: esp: c2c27ec8 Dec 12 02:00:22 kernel: eax: c0fa04d8 ebx: c88f1cd0 ecx: 0100 edx: Dec 12 02:00:22 kernel: esi: edi: c0fa04d4 ebp: esp: c2c27ec8 Dec 12 02:00:22 kernel: ds: 007b es: 007b ss: 0068 Dec 12 02:00:22 kernel: Process find (pid: 9113, ti=c2c26000 task=c7fe6050 task.ti=c2c26000) Dec 12 02:00:22 kernel: Stack: c0132ef2 c0fa04d4 c88f1cd0 c7c6f3e0 c88efcdd Dec 12 02:00:22 kernel:c0fa04d4 c88f1cd0 1605 fd03 Dec 12 02:00:22 kernel:41ed 0004 Dec 12 02:00:22 kernel: Call Trace: Dec 12 02:00:22 kernel: [] read_cache_page+0x32/0x160 Dec 12 02:00:22 kernel: [] ext2_readpage+0x0/0x20 [ext2] Dec 12 02:00:22 kernel: [] ext2_get_page+0x1d/0x290 [ext2] Dec 12 02:00:22 kernel: [] ext2_readpage+0x0/0x20 [ext2] Dec 12 02:00:22 kernel: [] ext2_readdir+0xd3/0x2c0 [ext2] Dec 12 02:00:22 kernel: [] vfs_readdir+0x5f/0x80 Dec 12 02:00:22 kernel: [] filldir64+0x0/0xd0 Dec 12 02:00:22 kernel: [] sys_getdents64+0x63/0xc0 Dec 12 02:00:22 kernel: [] filldir64+0x0/0xd0 Dec 12 02:00:22 kernel: [] syscall_call+0x7/0xb Dec 12 02:00:22 kernel: Code: eb dd 8d b4 26 00 00 00 00 8d bc 27 00 00 00 00 fa 8b 44 24 04 8b 4c 24 08 83 c0 04 51 50 e8 2d 9e 06 00 89 c1 58 85 c9 5a 74 0c <8b> 01 89 ca f6 c4 40 75 07 ff 42 04 fb 89 c8 c3 8b 51 0c eb f4 Dec 12 02:00:22 kernel: [] syscall_call+0x7/0xb Dec 12 02:00:22 kernel: Code: eb dd 8d b4 26 00 00 00 00 8d bc 27 00 00 00 00 fa 8b 44 24 04 8b 4c 24 08 83 c0 04 51 50 e8 2d 9e 06 00 89 c1 58 85 c9 5a 74 0c <8b> 01 89 ca f6 c4 40 75 07 ff 42 04 fb 89 c8 c3 8b 51 0c eb f4 Dec 12 02:00:22 kernel: EIP: [] find_get_page+0x1b/0x30 SS:ESP 0068:c2c27ec8 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#402682: linux-image-2.6.18-3-amd64: emu10k1 and Audigy 4: Line mixer should be a playback mixer
Package: linux-image-2.6.18-3-amd64 Version: 2.6.18-7 Severity: normal I have an Creative Audigy 4 sound card which uses the snd-emu10k1 module from the Linux kernel. In the kernel versions 2.6.17 and before the line mixer used to be a playback mixer. But with 2.6.18 this changed and now it is a capture mixer. As a result I can no longer use the mixer in my TV and radio applications and I am not able to change the volume. My TV card uses the line input as its sound output. Maybe this is not a kernel bug and should be fixed in the TV and radio applications (kdetv and kradio in my case), but all sound cards I used before had the line mixer as playback mixer. So there was never a problem. The attached patch fixes the problem in the emu10k1 module by not rename the line mixer (as it was before). Regards, Markus --- linux-source-2.6.18/sound/pci/emu10k1/emumixer.c.org 2006-12-12 01:19:05.0 +0100 +++ linux-source-2.6.18/sound/pci/emu10k1/emumixer.c 2006-12-12 01:20:59.0 +0100 @@ -836,8 +836,6 @@ "Phone Playback Volume", "Phone Capture Volume", "Mic Playback Switch", "Mic Capture Switch", "Mic Playback Volume", "Mic Capture Volume", - "Line Playback Switch", "Line Capture Switch", - "Line Playback Volume", "Line Capture Volume", "CD Playback Switch", "CD Capture Switch", "CD Playback Volume", "CD Capture Volume", "Aux Playback Switch", "Aux Capture Switch",
Bug#402667: linux-image-2.6.18-3-686: IBM ThinkPad X40 (APM) fails to power off on shutdown
Package: linux-image-2.6.18-3-686 Version: 2.6.18-7 Severity: normal Hoping to fix some Xorg problems, I recently upgraded from a 2.6.15 kernel to the latest 2.6.18 kernel. Unfortunately, using the new kernel, my machine no longer powers off when executing shutdown -h now As shown in the attached output of dmesg, I added some apm stuff to the kernel command line: root=/dev/hda1 ro apm=on apm=power-off vga=792 cachesize=1024 acpi=off but this had no effect. Power off on shutdown worked fine on my 2.6.15 kernel. If you want, I can install 2.6.16 and 2.6.17 and tell you exactly where things went off the rails. Please let me know if there's any other information I can provide that would help diagnose the problem. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (50, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages linux-image-2.6.18-3-686 depends on: ii coreutils 5.97-5 The GNU core utilities ii debconf [debconf-2.0] 1.5.8 Debian configuration management sy ii initramfs-tools [linux-initra 0.85b tools for generating an initramfs ii module-init-tools 3.3-pre3-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.18-3-686 recommends: ii libc6-i686 2.3.6.ds1-8 GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.18-3-686/postinst/bootloader-error-2.6.18-3-686: linux-image-2.6.18-3-686/postinst/old-dir-initrd-link-2.6.18-3-686: true linux-image-2.6.18-3-686/postinst/kimage-is-a-directory: linux-image-2.6.18-3-686/postinst/old-system-map-link-2.6.18-3-686: true linux-image-2.6.18-3-686/postinst/create-kimage-link-2.6.18-3-686: true linux-image-2.6.18-3-686/postinst/bootloader-test-error-2.6.18-3-686: linux-image-2.6.18-3-686/preinst/abort-overwrite-2.6.18-3-686: linux-image-2.6.18-3-686/postinst/old-initrd-link-2.6.18-3-686: true shared/kernel-image/really-run-bootloader: true linux-image-2.6.18-3-686/preinst/elilo-initrd-2.6.18-3-686: true linux-image-2.6.18-3-686/preinst/lilo-initrd-2.6.18-3-686: true linux-image-2.6.18-3-686/postinst/depmod-error-initrd-2.6.18-3-686: false linux-image-2.6.18-3-686/preinst/bootloader-initrd-2.6.18-3-686: true linux-image-2.6.18-3-686/prerm/removing-running-kernel-2.6.18-3-686: true linux-image-2.6.18-3-686/prerm/would-invalidate-boot-loader-2.6.18-3-686: true linux-image-2.6.18-3-686/preinst/abort-install-2.6.18-3-686: linux-image-2.6.18-3-686/preinst/overwriting-modules-2.6.18-3-686: true linux-image-2.6.18-3-686/preinst/initrd-2.6.18-3-686: linux-image-2.6.18-3-686/preinst/lilo-has-ramdisk: linux-image-2.6.18-3-686/preinst/already-running-this-2.6.18-3-686: linux-image-2.6.18-3-686/postinst/depmod-error-2.6.18-3-686: false linux-image-2.6.18-3-686/preinst/failed-to-move-modules-2.6.18-3-686: Linux version 2.6.18-3-686 (Debian 2.6.18-7) ([EMAIL PROTECTED]) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-20)) #1 SMP Mon Dec 4 16:41:14 UTC 2006 BIOS-provided physical RAM map: BIOS-e820: - 0009f000 (usable) BIOS-e820: 0009f000 - 000a (reserved) BIOS-e820: 000dc000 - 0010 (reserved) BIOS-e820: 0010 - 5f6e (usable) BIOS-e820: 5f6e - 5f6f7000 (ACPI data) BIOS-e820: 5f6f7000 - 5f6f9000 (ACPI NVS) BIOS-e820: 5f70 - 6000 (reserved) BIOS-e820: fec0 - fec1 (reserved) BIOS-e820: fee0 - fee01000 (reserved) BIOS-e820: ff80 - 0001 (reserved) 630MB HIGHMEM available. 896MB LOWMEM available. On node 0 totalpages: 390880 DMA zone: 4096 pages, LIFO batch:0 Normal zone: 225280 pages, LIFO batch:31 HighMem zone: 161504 pages, LIFO batch:31 DMI present. Allocating PCI resources starting at 7000 (gap: 6000:9ec0) Detected 1196.163 MHz processor. Built 1 zonelists. Total pages: 390880 Kernel command line: root=/dev/hda1 ro apm=on apm=power-off vga=792 cachesize=1024 acpi=off Found and enabled local APIC! mapped APIC to d000 (fee0) Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 PID hash table entries: 4096 (order: 12, 16384 bytes) Console: colour dummy device 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 1542120k/1563520k available (1543k kernel code, 20108k reserved, 574k data, 196k init, 646016k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 2393.92 BogoMIPS (lpj=4787854) Security Framework v1.0.0 initialized SELinux: Disabled at bo
Bug#402648: kernel-image-2.6.8-3-k7: USB System hangs when I use my webcam
On Mon, Dec 11, 2006 at 09:50:57PM +0100, ??ngel Rodr??guez S??nchez wrote: > Package: kernel-image-2.6.8-3-k7 > Version: 2.6.8-16sarge6 > Severity: normal > > > I have got an USB webcam Easy Snap Home with a chip stv680. With Windows > it > worked well, but I changed to Debian Linux. The kernel find the device and > when I start to use > it, it works, but after sometimes it hangs all the USB > system on my laptop. I think that its not a hardware problem, because > it > worked well with windows. I tried with pencam2, gqcam and xawtv. Its unlikely that this issue will be fixed in sarge, given that the next release of Debian should occur within the next month. I suggest upgrading to etch if you can. If the problem still occurs, please let us know. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.18 - Xen coredump problem
Am Montag, 11. Dezember 2006 12:32 schrieb Bastian Blank: > Hi folks > > Our 2.6.18 i386 xen images sometimes dies on coredumps[1]. Fedora, which > uses the same patch, does not have this problem. The main different is > PAE, Fedora don't longer ships kernels without. I asked the Fedora Xen > maintainer but did not get a response on this problem yet. I did a quick > check with our kernel, and the problem did not show up with PAE enabled. > > We have the following possibilities: > - Ignore it. Each i386 xen machine can be crashed by a simple program. > - Switch the i386 image(s) to PAE. > - With ABI bump. > - Without ABI bump but new package names. Hi Bastian & "folks", what about a thrid possibility (but I don't know if it's possible at all): - Have the kernel decice at boot time if pae is needed or not. If the system has >3.5 gb of ram, then use pae, else use non-pae. I am not sure if pae in general is really a good idea, because I got some problems with pae and xen on quite usual serverhardware in the past (xen 3.0.0 & 3.0.1). For example the 3ware 9xxx controllers seems to have some ugly problems with 36bit wide adressspace (pae) and until I recieved a patch from Ian Pratt for the xen hypervisor, xen was not really useable. Ian's words in this context: "PAE is a damn crook. Just a cheap hack... I hate it! Don't use it, if you don't need it." If I remember it correctly, using pae also costs a bit of performance, so it would be not wise to use it if not really needed. Bastian, have you asked the xen-devel ml if they have a clou why #399113 happens? Maybe they can help. > Bastian > > [1]: #399113 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#402634: marked as done (Installation of linux-image-2.6.18-3-ixp4xx on Linksys NSLU2 fails)
Your message dated Mon, 11 Dec 2006 22:32:33 +0100 with message-id <[EMAIL PROTECTED]> and subject line No bug after all has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: linux-image-2.6.18-3-ixp4xx Version: 2.6.18-7 System: Linksys NSLU2 running: Linux mysys 2.6.17-2-ixp4xx #1 Thu Sep 14 13:29:00 UTC 2006 armv5tel GNU/Linux Libc version: libc-2.3.6.so Trying to install the latest testing updates fails and gives two error messages: - symbolic link /lib/modules/2.6.18-3-ixp4xx/source does not exist - post-install hook flash_kernel is missing The log of this install is: . The following extra packages will be installed: linux-image-2.6.18-3-ixp4xx Suggested packages: linux-doc-2.6.18 The following NEW packages will be installed: linux-image-2.6.18-3-ixp4xx 0 upgraded, 1 newly installed, 0 to remove and 7 not upgraded. 1 not fully installed or removed. Need to get 0B/8902kB of archives. After unpacking 25.7MB of additional disk space will be used. Do you want to continue [Y/n]? Preconfiguring packages ... Selecting previously deselected package linux-image-2.6.18-3-ixp4xx. (Reading database ... 31251 files and directories currently installed.) Unpacking linux-image-2.6.18-3-ixp4xx (from .../linux- image-2.6.18-3-ixp4xx_2.6.18-7_arm.deb) ... Done. Setting up linux-image-2.6.18-3-ixp4xx (2.6.18-7) ... Hmm. The package shipped with a symbolic link /lib/modules/2.6.18-3-ixp4xx/source However, I can not read the target: No such file or directory Therefore, I am deleting /lib/modules/2.6.18-3-ixp4xx/source Running depmod. Finding valid ramdisk creators. Using mkinitramfs-kpkg to build the ramdisk. Could not find postinst hook script [flash_kernel]. Looked in: '/bin', '/sbin', '/usr/bin', '/usr/sbin' dpkg: error processing linux-image-2.6.18-3-ixp4xx (--configure): subprocess post-installation script returned error exit status 2 dpkg: dependency problems prevent configuration of linux-image-2.6-ixp4xx: linux-image-2.6-ixp4xx depends on linux-image-2.6.18-3-ixp4xx; however: Package linux-image-2.6.18-3-ixp4xx is not configured yet. dpkg: error processing linux-image-2.6-ixp4xx (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-2.6.18-3-ixp4xx linux-image-2.6-ixp4xx E: Sub-process /usr/bin/dpkg returned an error code (1) --- End Message --- --- Begin Message --- After re-reading the upgrade instructions on http://www.cyrius.com/debian/nslu2/upgrade.html I realized the error was mine: I put a line flash_kernel into /etc/kernel-image.conf So please ignore my ignorance, some fuzz about nothing Ger Kersten --- End Message ---
Bug#402534: udev: Upgrade to version 0.103-1 fails
reassign 402534 lilo stop On Mon, Dec 11, 2006 at 12:24:40PM -0600, Reid Priedhorsky wrote: > >lilo -t > > 24 [~]$ lilo -t > Fatal: Duplicate "disk =" definition for /dev/sdb > > >cat /etc/lilo.conf > > 25 [~]$ cat /etc/lilo.conf > boot=/dev/hda > root=/dev/hda1 > compact > lba32 > install=menu > map=/boot/map > vga=normal > delay=50 > read-only > append="hdc=ide-scsi" > > disk=/dev/sda > inaccessible > disk=/dev/sdb > inaccessible > > # Stock kernel shipped by Debian > image=/vmlinuz > label=debian > initrd=/initrd.img > > # My 2.4 kernels > image=/boot/bzImage-2.4.32 > label=2.4.32 > image=/boot/bzImage-2.4.31.new > label=2.4.31.new > image=/boot/bzImage-2.4.31 > label=2.4.31 > image=/boot/bzImage-2.4.29.new > label=2.4.29.new > > ... I don't see sdb in there twice, though. ??? (/dev/sda and /dev/sdb > are USB mass storage and usually not present.) > > I changed from 2.4 to 2.6 a few weeks ago and added the disk=/dev/sdb > line at that time due to complaints about /dev/sdb being inacessible. i have zero idea if that behaviour changed lately, reassigning to the lilo guys that they take a look. also note that ide-scsi is deprecated for 2.6. > >>>cat /etc/kernel-img.conf > >>reidster:/tmp# cat /etc/kernel-img.conf > >># Kernel Image management overrides > >># See kernel-img.conf(5) for details > >>do_symlinks = Yes > > > >if you are using lilo you want to add the following line so that lilo > >gets invoked automaticaly on new install of an linux image: > >do_bootloader = yes > > Hmm, I'll look into that. > > Looking at the bug reports for lilo makes me ponder switching to grub, > though... yes grub is much more comfortable. lilo is only needed on boxes with bad bios, there lilo has better workarounds. > Thanks again, > > Reid best regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#402534: udev: Upgrade to version 0.103-1 fails
Processing commands for [EMAIL PROTECTED]: > reassign 402534 lilo Bug#402534: udev: Upgrade to version 0.103-1 fails Bug reassigned from package `initramfs-tools' to `lilo'. > stop 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#402648: kernel-image-2.6.8-3-k7: USB System hangs when I use my webcam
Package: kernel-image-2.6.8-3-k7 Version: 2.6.8-16sarge6 Severity: normal I have got an USB webcam Easy Snap Home with a chip stv680. With Windows it worked well, but I changed to Debian Linux. The kernel find the device and when I start to use it, it works, but after sometimes it hangs all the USB system on my laptop. I think that its not a hardware problem, because it worked well with windows. I tried with pencam2, gqcam and xawtv. I have read the /var/log/debug file and this is the text: Nov 9 21:41:09 localhost kernel: usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd pencam2 rqt 192 rq 134 len 16 ret -110 Nov 9 21:41:10 localhost kernel: usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd pencam2 rqt 192 rq 128 len 2 ret -110 Nov 9 21:41:12 localhost kernel: usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd pencam2 rqt 192 rq 134 len 16 ret -110 Nov 9 21:41:13 localhost kernel: usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd pencam2 rqt 192 rq 128 len 2 ret -110 Nov 9 21:41:16 localhost kernel: usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd pencam2 rqt 192 rq 134 len 16 ret -110 Nov 9 21:41:18 localhost kernel: usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd pencam2 rqt 192 rq 128 len 2 ret -110 Nov 9 21:41:19 localhost kernel: usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd pencam2 rqt 192 rq 134 len 16 ret -110 Nov 9 21:41:20 localhost kernel: usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd pencam2 rqt 192 rq 128 len 2 ret -110 Nov 9 21:41:22 localhost kernel: usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd pencam2 rqt 192 rq 134 len 16 ret -110 Nov 9 21:41:23 localhost kernel: usb 1-2.4: usbfs: USBDEVFS_CONTROL failed cmd pencam2 rqt 192 rq 128 len 2 ret -110 -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.8-3-k7 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages kernel-image-2.6.8-3-k7 depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii initrd-tools 0.1.81.1 tools to create initrd image for pii module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo -- no debconf information __ LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: conglomeration modules for ivtv-source & zaptel-source
Daniel Baumann wrote: > Bastian Blank wrote: >> And the kernel team may overtake it. waldi granted me svn write access, so I can help out on l-m-e. In return, I commited l-m-c/n to the svn a few minutes ago. This is really good, now all conglomeration packages are maintained in the same place. Thanks waldi, really appreciated. -- 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: Still cannot install in Sarge
Processing commands for [EMAIL PROTECTED]: > found 400544 2.6.18-8 Bug#400544: Fails to install properly on Sarge Bug marked as found in version 2.6.18-8. > 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#400544: Still cannot install in Sarge
found 400544 2.6.18-8 thanks The upgrade error still seems to exist in the configuration script. There is no -m available in readlink in Sarge. Error occurs is in the postinst, as indicated. Please either remove the -m from readlink OR update dependencies such that newer readlink is installed prior to postinst running. (Reading database ... 55452 files and directories currently installed.) Preparing to replace linux-image-2.6.18-3-vserver-k7 2.6.18-7 (using linux-image-2.6.18-3-vserver-k7_2.6.18-8_i386.deb) ... The directory /lib/modules/2.6.18-3-vserver-k7 still exists. Continuing as directed. Done. Unpacking replacement linux-image-2.6.18-3-vserver-k7 ... Setting up linux-image-2.6.18-3-vserver-k7 (2.6.18-8) ... Hmm. The package shipped with a symbolic link /lib/modules/2.6.18-3-vserver-k7/source However, I can not read the target: No such file or directory Therefore, I am deleting /lib/modules/2.6.18-3-vserver-k7/source Running depmod. Finding valid ramdisk creators. Using mkinitrd.yaird to build the ramdisk. yaird warning: consider upgrading to mdadm 2.2 or newer to support changes in device boot ordering readlink: invalid option -- m Try `readlink --help' for more information. readlink: invalid option -- m Try `readlink --help' for more information. Failed to symbolic-link initrd.img-2.6.18-3-vserver-k7 to initrd.img. dpkg: error processing linux-image-2.6.18-3-vserver-k7 (--install): subprocess post-installation script returned error exit status 17 Errors were encountered while processing: linux-image-2.6.18-3-vserver-k7 polaris:~# dpkg --configure --pending -a Setting up linux-image-2.6.18-3-vserver-k7 (2.6.18-8) ... Running depmod. Finding valid ramdisk creators. Using mkinitrd.yaird to build the ramdisk. yaird warning: consider upgrading to mdadm 2.2 or newer to support changes in device boot ordering readlink: invalid option -- m Try `readlink --help' for more information. readlink: invalid option -- m Try `readlink --help' for more information. Failed to symbolic-link initrd.img-2.6.18-3-vserver-k7 to initrd.img. dpkg: error processing linux-image-2.6.18-3-vserver-k7 (--configure): subprocess post-installation script returned error exit status 17 Errors were encountered while processing: linux-image-2.6.18-3-vserver-k7 polaris:~# -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#402634: Installation of linux-image-2.6.18-3-ixp4xx on Linksys NSLU2 fails
Package: linux-image-2.6.18-3-ixp4xx Version: 2.6.18-7 System: Linksys NSLU2 running: Linux mysys 2.6.17-2-ixp4xx #1 Thu Sep 14 13:29:00 UTC 2006 armv5tel GNU/Linux Libc version: libc-2.3.6.so Trying to install the latest testing updates fails and gives two error messages: - symbolic link /lib/modules/2.6.18-3-ixp4xx/source does not exist - post-install hook flash_kernel is missing The log of this install is: . The following extra packages will be installed: linux-image-2.6.18-3-ixp4xx Suggested packages: linux-doc-2.6.18 The following NEW packages will be installed: linux-image-2.6.18-3-ixp4xx 0 upgraded, 1 newly installed, 0 to remove and 7 not upgraded. 1 not fully installed or removed. Need to get 0B/8902kB of archives. After unpacking 25.7MB of additional disk space will be used. Do you want to continue [Y/n]? Preconfiguring packages ... Selecting previously deselected package linux-image-2.6.18-3-ixp4xx. (Reading database ... 31251 files and directories currently installed.) Unpacking linux-image-2.6.18-3-ixp4xx (from .../linux- image-2.6.18-3-ixp4xx_2.6.18-7_arm.deb) ... Done. Setting up linux-image-2.6.18-3-ixp4xx (2.6.18-7) ... Hmm. The package shipped with a symbolic link /lib/modules/2.6.18-3-ixp4xx/source However, I can not read the target: No such file or directory Therefore, I am deleting /lib/modules/2.6.18-3-ixp4xx/source Running depmod. Finding valid ramdisk creators. Using mkinitramfs-kpkg to build the ramdisk. Could not find postinst hook script [flash_kernel]. Looked in: '/bin', '/sbin', '/usr/bin', '/usr/sbin' dpkg: error processing linux-image-2.6.18-3-ixp4xx (--configure): subprocess post-installation script returned error exit status 2 dpkg: dependency problems prevent configuration of linux-image-2.6-ixp4xx: linux-image-2.6-ixp4xx depends on linux-image-2.6.18-3-ixp4xx; however: Package linux-image-2.6.18-3-ixp4xx is not configured yet. dpkg: error processing linux-image-2.6-ixp4xx (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-2.6.18-3-ixp4xx linux-image-2.6-ixp4xx E: Sub-process /usr/bin/dpkg returned an error code (1)
Bug#402534: udev: Upgrade to version 0.103-1 fails
lilo -t 24 [~]$ lilo -t Fatal: Duplicate "disk =" definition for /dev/sdb cat /etc/lilo.conf 25 [~]$ cat /etc/lilo.conf boot=/dev/hda root=/dev/hda1 compact lba32 install=menu map=/boot/map vga=normal delay=50 read-only append="hdc=ide-scsi" disk=/dev/sda inaccessible disk=/dev/sdb inaccessible # Stock kernel shipped by Debian image=/vmlinuz label=debian initrd=/initrd.img # My 2.4 kernels image=/boot/bzImage-2.4.32 label=2.4.32 image=/boot/bzImage-2.4.31.new label=2.4.31.new image=/boot/bzImage-2.4.31 label=2.4.31 image=/boot/bzImage-2.4.29.new label=2.4.29.new ... I don't see sdb in there twice, though. ??? (/dev/sda and /dev/sdb are USB mass storage and usually not present.) I changed from 2.4 to 2.6 a few weeks ago and added the disk=/dev/sdb line at that time due to complaints about /dev/sdb being inacessible. cat /etc/kernel-img.conf reidster:/tmp# cat /etc/kernel-img.conf # Kernel Image management overrides # See kernel-img.conf(5) for details do_symlinks = Yes if you are using lilo you want to add the following line so that lilo gets invoked automaticaly on new install of an linux image: do_bootloader = yes Hmm, I'll look into that. Looking at the bug reports for lilo makes me ponder switching to grub, though... Thanks again, Reid -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#401358: marked as done (System freezes under heavy disk IO)
Your message dated Mon, 11 Dec 2006 19:21:07 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#401358: System freezes under heavy disk IO) has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: linux-image-2.6.18-3-k7 Version: 2.6.18-6 After installing the version 2.6.18-6 of the kernel, my machine (SMP, AthlonMP) just freezes under heavy disk IO (not immediately, but after a few minutes). I tried the modules dpt_i2o and i2o_block for my Adaptec 2400A raid controller, and even tried JFS instead of XFS as filesystem, but it didn't make any difference. Well, the only difference was the time it took until the machine froze (actually with JFS it happened faster than with XFS). I went back to the version 2.6.17-9 and the machine seems to run stable again, even with more IO than needed to crash 2.6.18-6. So, it looks like somehwere between those versions, a SMB related bug was introduced in a more generic place, since the crashes happened across drivers and filesystems. regards, Peter - Peter Hirdina Frauenstrasse 128 [EMAIL PROTECTED] 89073 Ulm / Germany - --- End Message --- --- Begin Message --- Version: 2.6.18-6 Sorry, my fault. There is no bug in the kernel. Doing some further testing in this area, I noticed that APIC isn't properly implemented on that board. Booting a kernel with "nosmp" just spills out a lot of APIC errors, but boots just fine with "nosmp noapic". Therefor I tried the "noapic" parameter also for SMP mode. And surprise, the system suddenly runs rock solid under heady disk IO. So, it was no code problem, just a hardware issue, and that could be solved by using the kernel parameter "noapic". cheers, Peter - Peter Hirdina Frauenstrasse 128 [EMAIL PROTECTED] 89073 Ulm / Germany - --- End Message ---
Bug#402534: udev: Upgrade to version 0.103-1 fails
Hi Maks,
Thanks for your help.
dpkg -l initramfs-tools
reidster:/tmp# dpkg -l initramfs-tools
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:
uppercase=bad)
||/ Name VersionDescription
+++-==-==-
ii initramfs-tool 0.85b tools for generating an initramfs
sh -x update-initramfs -u
reidster:/tmp# sh -x update-initramfs -u
sh: Can't open update-initramfs
reidster:/tmp# sh -x /usr/sbin/update-initramfs -u
+ STATEDIR=/var/lib/initramfs-tools
+ BOOTDIR=/boot
+ CONF=/etc/initramfs-tools/update-initramfs.conf
+ KPKGCONF=/etc/kernel-img.conf
+ set -e
+ [ -r /etc/initramfs-tools/update-initramfs.conf ]
+ . /etc/initramfs-tools/update-initramfs.conf
+ update_initramfs=yes
+ backup_initramfs=yes
+ verbose=0
+ yes=0
+ takeover=0
+ getopts k:cudyvtb:h? flag
+ mode=u
+ getopts k:cudyvtb:h? flag
+ [ -z u ]
+ [ = all ]
+ update
+ [ yes = no ]
+ [ -z ]
+ set_linked_version
+ [ -L /initrd.img ]
+ readlink /initrd.img
+ basename boot/initrd.img-2.6.18-3-k7
+ linktarget=initrd.img-2.6.18-3-k7
+ [ -L /boot/initrd.img ]
+ [ -z initrd.img-2.6.18-3-k7 ]
+ version=2.6.18-3-k7
+ [ -z 2.6.18-3-k7 ]
+ [ -z 2.6.18-3-k7 ]
+ [ -z 2.6.18-3-k7 ]
+ set_initramfs
+ initramfs=/boot/initrd.img-2.6.18-3-k7
+ ro_boot_check
+ [ -r /proc/mounts ]
+ awk /boot/{if (match($4, /ro/) && $2 == "/boot")
print "ro"} /proc/mounts
+ boot_opts=
+ [ -n ]
+ altered_check
+ [ 0 = 0 ]
+ compare_sha1
+ sha1sum /boot/initrd.img-2.6.18-3-k7
+ diff /var/lib/initramfs-tools/2.6.18-3-k7 -
+ return 0
+ backup_initramfs
+ [ ! -r /boot/initrd.img-2.6.18-3-k7 ]
+ initramfs_bak=/boot/initrd.img-2.6.18-3-k7.dpkg-bak
+ [ -r /boot/initrd.img-2.6.18-3-k7.dpkg-bak ]
+ rm -f /boot/initrd.img-2.6.18-3-k7.dpkg-bak
+ mv -f /boot/initrd.img-2.6.18-3-k7 /boot/initrd.img-2.6.18-3-k7.dpkg-bak
+ verbose Keeping /boot/initrd.img-2.6.18-3-k7.dpkg-bak
+ [ 0 = 1 ]
+ generate_initramfs
+ echo update-initramfs: Generating /boot/initrd.img-2.6.18-3-k7
update-initramfs: Generating /boot/initrd.img-2.6.18-3-k7
+ OPTS=-o
+ [ 0 = 1 ]
+ mkinitramfs -o /boot/initrd.img-2.6.18-3-k7 2.6.18-3-k7
+ set_sha1
+ sha1sum /boot/initrd.img-2.6.18-3-k7
+ run_bootloader
+ [ -x /sbin/grub ]
+ [ -e /boot/grub/menu.lst ]
+ [ -x /usr/sbin/grub ]
+ [ -r /etc/lilo.conf ]
+ [ -x /sbin/lilo ]
+ run_lilo
+ lilo -t
HTH. Let me know how else I can help.
Thanks,
Reid
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#402534: udev: Upgrade to version 0.103-1 fails
On Mon, Dec 11, 2006 at 10:10:05AM -0600, Reid Priedhorsky wrote: > maximilian attems wrote: > > >which bootloader are you using lilo or grub? > > lilo, v. 1:22.6.1-9 why does the lilo run fail than? please send the output of: lilo -t cat /etc/lilo.conf > >cat /etc/kernel-img.conf > > reidster:/tmp# cat /etc/kernel-img.conf > # Kernel Image management overrides > # See kernel-img.conf(5) for details > do_symlinks = Yes if you are using lilo you want to add the following line so that lilo gets invoked automaticaly on new install of an linux image: do_bootloader = yes best regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#402534: udev: Upgrade to version 0.103-1 fails
maximilian attems wrote: which bootloader are you using lilo or grub? lilo, v. 1:22.6.1-9 cat /etc/kernel-img.conf reidster:/tmp# cat /etc/kernel-img.conf # Kernel Image management overrides # See kernel-img.conf(5) for details do_symlinks = Yes Thanks, Reid -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#402605: boot hanging, ICH7: ata2: port failed to respond
Package: linux-image-2.6.18-3-686 Version: 2.6.18-7 Severity: important Tags: patch Hi all! 2.6.18 hangs on ICH7 SCSI_ATA_PIIX with these messages: ata1: SATA max UDMA/133 cmd 0xFE00 ctl 0xFE12 bmdma 0xFEA0 irq 18 ata2: SATA max UDMA/133 cmd 0xFE20 ctl 0xFE32 bmdma 0xFEA8 irq 18 scsi0 : ata_piix ata1.00: ATA-7, max UDMA/133, 15625 sectors: LBA48 NCQ (depth 0/32) ata1.00: ata1: dev 0 multi count 8 ata1.00: configured for UDMA/133 scsi1 : ata_piix ata2: port is slow to respond, please be patient ata2: port failed to respond (30 secs) ata2: SRST failed (status 0xFF) ata2: SRST failed (err_mask=0x100) ata2: softreset failed, retrying in 5 secs ata2: SRST failed (status 0xFF) ata2: SRST failed (err_mask=0x100) ata2: softreset failed, retrying in 5 secs ata2: SRST failed (status 0xFF) ata2: SRST failed (err_mask=0x100) ata2: reset failed, giving up This is well known, and due to included into upstream kernel, but I dont know whether it will make it into etch! For a patch see http://thread.gmane.org/gmane.linux.ide/13408/focus=13439 Best wishes Norbert -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (990, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-686 Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15) Versions of packages linux-image-2.6.18-3-686 depends on: ii coreutils 5.97-5 The GNU core utilities ii debconf [debconf-2.0] 1.5.8 Debian configuration management sy ii initramfs-tools [linux-initra 0.85b tools for generating an initramfs ii module-init-tools 3.3-pre3-1 tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.12-18 Yet Another mkInitRD Versions of packages linux-image-2.6.18-3-686 recommends: ii libc6-i686 2.3.6.ds1-8 GNU C Library: Shared libraries [i -- debconf information: shared/kernel-image/really-run-bootloader: true linux-image-2.6.18-3-686/postinst/bootloader-error-2.6.18-3-686: linux-image-2.6.18-3-686/postinst/old-dir-initrd-link-2.6.18-3-686: true linux-image-2.6.18-3-686/postinst/kimage-is-a-directory: linux-image-2.6.18-3-686/preinst/elilo-initrd-2.6.18-3-686: true linux-image-2.6.18-3-686/postinst/old-system-map-link-2.6.18-3-686: true linux-image-2.6.18-3-686/preinst/lilo-initrd-2.6.18-3-686: true linux-image-2.6.18-3-686/postinst/depmod-error-initrd-2.6.18-3-686: false linux-image-2.6.18-3-686/preinst/bootloader-initrd-2.6.18-3-686: true linux-image-2.6.18-3-686/prerm/removing-running-kernel-2.6.18-3-686: true linux-image-2.6.18-3-686/postinst/create-kimage-link-2.6.18-3-686: true linux-image-2.6.18-3-686/prerm/would-invalidate-boot-loader-2.6.18-3-686: true linux-image-2.6.18-3-686/preinst/abort-install-2.6.18-3-686: linux-image-2.6.18-3-686/preinst/overwriting-modules-2.6.18-3-686: true linux-image-2.6.18-3-686/preinst/initrd-2.6.18-3-686: linux-image-2.6.18-3-686/preinst/lilo-has-ramdisk: linux-image-2.6.18-3-686/preinst/already-running-this-2.6.18-3-686: linux-image-2.6.18-3-686/postinst/bootloader-test-error-2.6.18-3-686: linux-image-2.6.18-3-686/preinst/abort-overwrite-2.6.18-3-686: linux-image-2.6.18-3-686/postinst/old-initrd-link-2.6.18-3-686: true linux-image-2.6.18-3-686/postinst/depmod-error-2.6.18-3-686: false linux-image-2.6.18-3-686/preinst/failed-to-move-modules-2.6.18-3-686: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#402534: udev: Upgrade to version 0.103-1 fails
On Mon, Dec 11, 2006 at 10:00:04AM -0600, Reid Priedhorsky wrote: > + [ -x /sbin/lilo ] > + run_lilo > + lilo -t > > HTH. Let me know how else I can help. which bootloader are you using lilo or grub? also please post cat /etc/kernel-img.conf -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: reassign 401183 to linux-2.6, forcibly merging 402581 401183, severity of 401183 is important
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.26 > reassign 401183 linux-2.6 Bug#401183: linux-image-2.6.17-2-xen-686.postinst not idempotent Warning: Unknown package 'linux-image-2.6.17-2-xen-686' Bug reassigned from package `linux-image-2.6.17-2-xen-686' to `linux-2.6'. > forcemerge 402581 401183 Bug#402581: linux-image-2.6.18-8-xen-*.postinst not idempotent Bug#401183: linux-image-2.6.17-2-xen-686.postinst not idempotent Forcibly Merged 401183 402581. > severity 401183 important Bug#401183: linux-image-2.6.17-2-xen-686.postinst not idempotent Bug#402581: linux-image-2.6.18-8-xen-*.postinst not idempotent Severity set to `important' from `serious' > 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#402584: kernel: [ACPI] brightness controll on laptop don't work since 2.6.18
Package: kernel Severity: normal Since kernel version 2.6.18 i can't control the brightness of my laptop anymore. It is a Fujitsu S7110 and brightness is set by a combination with Fn-key. Other Fn-keys-combinations work properly. With acpi=off brightness controll works fine. With Kernel 2.6.17 brightness controll worked with enabled acpi. Thank you. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#391867: "port is slow to respond" on computer with SATA disk
Same problem here, running linux-image-2.6.18-3-686 (version 2.6.18-7) on a Dell Optiplex GX620. I'm not attaching the dmesg output, since it's virtually identical with the ones already reported, but I'd like to point out that this seems to have a patch ready upstream. Here's the discussion thread: http://comments.gmane.org/gmane.linux.ide/13283 And here's the patch submission request (it even seems to have been applied upstream): http://thread.gmane.org/gmane.linux.ide/13408 Cheers! -=[david]=- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: 401183 affects linux-image-2.6.18-3-xen-* as well
Processing commands for [EMAIL PROTECTED]: > clone 401183 -1 Bug#401183: linux-image-2.6.17-2-xen-686.postinst not idempotent Bug 401183 cloned as bug 402581. > reassign -1 linux-2.6 2.6.18-8 Bug#402581: linux-image-2.6.17-2-xen-686.postinst not idempotent Warning: Unknown package 'linux-image-2.6.17-2-xen-686' Bug reassigned from package `linux-image-2.6.17-2-xen-686' to `linux-2.6'. > retitle -1 linux-image-2.6.18-8-xen-*.postinst not idempotent Bug#402581: linux-image-2.6.17-2-xen-686.postinst not idempotent Changed Bug title. > 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#400220: marked as done (linux-modules-extra-2.6: source package does not compile due to missing build dependencies (squafs/unionfs))
Your message dated Mon, 11 Dec 2006 06:39:25 -0500 with message-id <[EMAIL PROTECTED]> and subject line Close has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: linux-modules-extra-2.6 Version: 2.6.17-2 Severity: serious Justification: no longer builds from source The source package depends on the 'squashfs-source' and 'unionfs-source' package, which are not available in etch. Looking at packages.debian.org: 'squashfs-source' is only available in unstable and 'unionfs-source' only in stable and unstable, but _not_ testing! As far as I remember, by removing all the relevant rules for building the unionfs/squasfs related modules-packages, the 'redhat-cluster-modules' and 'spca5xx-modules' are building fine (at least on amd64). -- System Information: Debian Release: 4.0 Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-dolly-aar81xx Locale: LANG=C, LC_CTYPE=en_US (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968) --- End Message --- --- Begin Message --- Sorry for the first close; I was confused by the bug title. --- End Message ---
Re: Hint for autodir (closes RC) and comments about linux-kernel-headers
On Mon, Dec 11, 2006 at 12:22:18PM +0100, Andreas Barth wrote: > can we please have some comment on that from the kernel side? linux-kernel-headers is not the domain auf the kernel team but of the glibc team. > > FYI: #399454 is essentially a bug in the auto_fs4.h header > > file, as resulted by talking with autofs and autodir upstreams (API > > breakage due to a change in a union used both in v4 and > > v5). The issue potentially impact any program built on > > 2.6.17+ and depending on auto_fs4.h. autofs_packet_union was changed, but this will only affect the size of the whole thing. Also it changes the version to 5 always. > > autofs upstream is fixing on his side for the kernel, but I > > wonder if we need to fix as well etch linux-kernel-headers Bug the glibc people. They will likely just remove that header. Bastian -- Each kiss is as the first. -- Miramanee, Kirk's wife, "The Paradise Syndrome", stardate 4842.6 signature.asc Description: Digital signature
2.6.18 - Xen coredump problem
Hi folks Our 2.6.18 i386 xen images sometimes dies on coredumps[1]. Fedora, which uses the same patch, does not have this problem. The main different is PAE, Fedora don't longer ships kernels without. I asked the Fedora Xen maintainer but did not get a response on this problem yet. I did a quick check with our kernel, and the problem did not show up with PAE enabled. We have the following possibilities: - Ignore it. Each i386 xen machine can be crashed by a simple program. - Switch the i386 image(s) to PAE. - With ABI bump. - Without ABI bump but new package names. Bastian [1]: #399113 -- What kind of love is that? Not to be loved; never to have shown love. -- Commissioner Nancy Hedford, "Metamorphosis", stardate 3219.8 signature.asc Description: Digital signature
Re: Hint for autodir (closes RC) and comments about linux-kernel-headers
Hi, can we please have some comment on that from the kernel side? Cheers, Andi * Francesco P. Lovergine ([EMAIL PROTECTED]) [061211 12:18]: > After about 20 days of work with both autodir and autofs4 upstream > a final fix for autodir is available (closes #399454). > Incidentally 0.9.8 is almost the same of 0.9.7 (integrating my previous fix > for an header file and an initial trial to fix the above bug) at upstream > level > and we are quite confident it does not impact stability in respect with > 0.9.7. > Just in case I could provide a 1:0.9.7-1 if required (0.9.7 was the last > available > version in testing AFAIK). > > About the fix, as communicated in #debian-kernel, just FYI: > > FYI: #399454 is essentially a bug in the auto_fs4.h header > file, as resulted by talking with autofs and autodir upstreams (API > breakage due to a change in a union used both in v4 and > v5). The issue potentially impact any program built on > 2.6.17+ and depending on auto_fs4.h. > any program which still uses v4 protocol, indeed > autofs upstream is fixing on his side for the kernel, but I > wonder if we need to fix as well etch linux-kernel-headers > of course this is not a problem for debian binaries, but i > think developers would not appreciate a broken header in etch for their > buildings and the issue is quite obscure > > No answer :-( > > This is an issue at kernel headers level, but Ian Kent > has not still provided a final fix for mainstream kernel. > Incidentally not every program which uses auto_fs4.h and the kernel > module is exposed to the breakage, and probably very few programs use autofs4. > Maybe documenting all the issue (but where? linux-kernel-headers is probably > the best choice) and providing the old auto_fs4.h is at this time the most > reasonable thing to do. > > -- > Francesco P. Lovergine > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#402499: initramfs-tools: depmod wastes space and time, please replace it with a modules.dep file
On Monday 11 December 2006 20:57, maximilian attems <[EMAIL PROTECTED]> wrote: > > The major issue is that the depmod > > program is simply larger than a full modules.dep file when compressed. > > Given that most sane configurations will not have the complete set of > > kernel modules (I use modules=list for a very small set of modules) the > > modules.dep file will often be smaller than depmod when uncompressed. > > > > Using the modules.dep file saves initramfs size in every case, and saves > > memory in some common cases. > > first of all MODULES=most is the default, so that is the common case! > the case you brought up had a small 1k difference, > so that's not the place to optimize. MODULES=most will give a smaller modules.dep than the one that lives under /lib/modules. The modules.dep that comes from /lib/modules will take up less space when compressed than depmod, so the MODULES=most case will save even more space. > > > i really don't see your antipathy on BUSYBOX=n > > > there you can get rid of glibc which is taking a _huge_ > > > place on initramfs. > > > > I use lvm root over a software RAID-1 on all my important machines (apart > > hmm ok, i thought you were squeezing for some embedded board. Just generally squeezing because I don't like wasting space. > sure by default any etch user will have glibc on initramfs due to > busysbox, udev and module-init-tools. OK, as the default requires glibc therefore doing everything in busybox will save space. Long-term we should consider getting modprobe and other programs included in busybox (modprobe used to be there for 2.4.x, we can do it again). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#402562: Please support newer 3ware controllers
Package: linux-2.6
Version: 2.6.18-7
Severity: wishlist
Please apply the attached patch to add support for the 9650SE
controllers. All changes should be relatively low-risk.
(The patch is part of 2.6.19. It applies to 2.6.17 and later as-is.)
commit 4039c30ef5d9189ff8dc72aaf610d1c933877e20
Author: adam radford <[EMAIL PROTECTED]>
Date: Thu Oct 26 18:01:06 2006 -0700
[SCSI] 3ware 9000 add support for 9650SE
Updates the 3ware 9000 driver:
- Free irq handler in __twa_shutdown().
- Serialize reset code.
- Add support for 9650SE controllers.
Signed-off-by: Adam Radford <[EMAIL PROTECTED]>
Signed-off-by: James Bottomley <[EMAIL PROTECTED]>
diff --git a/drivers/scsi/3w-9xxx.c b/drivers/scsi/3w-9xxx.c
index 5f8c26c..b091a0f 100644
--- a/drivers/scsi/3w-9xxx.c
+++ b/drivers/scsi/3w-9xxx.c
@@ -66,6 +66,9 @@
2.26.02.006 - Fix 9550SX pchip reset timeout.
Add big endian support.
2.26.02.007 - Disable local interrupts during kmap/unmap_atomic().
+ 2.26.02.008 - Free irq handler in __twa_shutdown().
+ Serialize reset code.
+ Add support for 9650SE controllers.
*/
#include
@@ -89,7 +92,7 @@
#include "3w-9xxx.h"
/* Globals */
-#define TW_DRIVER_VERSION "2.26.02.007"
+#define TW_DRIVER_VERSION "2.26.02.008"
static TW_Device_Extension *twa_device_extension_list[TW_MAX_SLOT];
static unsigned int twa_device_extension_count;
static int twa_major = -1;
@@ -566,9 +569,9 @@ static int twa_check_srl(TW_Device_Extension *tw_dev, int
*flashed)
goto out;
}
- tw_dev->working_srl = fw_on_ctlr_srl;
- tw_dev->working_branch = fw_on_ctlr_branch;
- tw_dev->working_build = fw_on_ctlr_build;
+ tw_dev->tw_compat_info.working_srl = fw_on_ctlr_srl;
+ tw_dev->tw_compat_info.working_branch = fw_on_ctlr_branch;
+ tw_dev->tw_compat_info.working_build = fw_on_ctlr_build;
/* Try base mode compatibility */
if (!(init_connect_result & TW_CTLR_FW_COMPATIBLE)) {
@@ -590,10 +593,23 @@ static int twa_check_srl(TW_Device_Extension *tw_dev, int
*flashed)
}
goto out;
}
- tw_dev->working_srl = TW_BASE_FW_SRL;
- tw_dev->working_branch = TW_BASE_FW_BRANCH;
- tw_dev->working_build = TW_BASE_FW_BUILD;
- }
+ tw_dev->tw_compat_info.working_srl = TW_BASE_FW_SRL;
+ tw_dev->tw_compat_info.working_branch = TW_BASE_FW_BRANCH;
+ tw_dev->tw_compat_info.working_build = TW_BASE_FW_BUILD;
+ }
+
+ /* Load rest of compatibility struct */
+ strncpy(tw_dev->tw_compat_info.driver_version, TW_DRIVER_VERSION,
strlen(TW_DRIVER_VERSION));
+ tw_dev->tw_compat_info.driver_srl_high = TW_CURRENT_DRIVER_SRL;
+ tw_dev->tw_compat_info.driver_branch_high = TW_CURRENT_DRIVER_BRANCH;
+ tw_dev->tw_compat_info.driver_build_high = TW_CURRENT_DRIVER_BUILD;
+ tw_dev->tw_compat_info.driver_srl_low = TW_BASE_FW_SRL;
+ tw_dev->tw_compat_info.driver_branch_low = TW_BASE_FW_BRANCH;
+ tw_dev->tw_compat_info.driver_build_low = TW_BASE_FW_BUILD;
+ tw_dev->tw_compat_info.fw_on_ctlr_srl = fw_on_ctlr_srl;
+ tw_dev->tw_compat_info.fw_on_ctlr_branch = fw_on_ctlr_branch;
+ tw_dev->tw_compat_info.fw_on_ctlr_build = fw_on_ctlr_build;
+
retval = 0;
out:
return retval;
@@ -631,7 +647,7 @@ static int twa_chrdev_ioctl(struct inode *inode, struct
file *file, unsigned int
goto out2;
/* Check data buffer size */
- if (driver_command.buffer_length > TW_MAX_SECTORS * 512) {
+ if (driver_command.buffer_length > TW_MAX_SECTORS * 2048) {
retval = TW_IOCTL_ERROR_OS_EINVAL;
goto out2;
}
@@ -680,13 +696,6 @@ static int twa_chrdev_ioctl(struct inode *inode, struct
file *file, unsigned int
/* Now wait for command to complete */
timeout = wait_event_timeout(tw_dev->ioctl_wqueue,
tw_dev->chrdev_request_id == TW_IOCTL_CHRDEV_FREE, timeout);
- /* See if we reset while waiting for the ioctl to complete */
- if (test_bit(TW_IN_RESET, &tw_dev->flags)) {
- clear_bit(TW_IN_RESET, &tw_dev->flags);
- retval = TW_IOCTL_ERROR_OS_ERESTARTSYS;
- goto out3;
- }
-
/* We timed out, and didn't get an interrupt */
if (tw_dev->chrdev_request_id != TW_IOCTL_CHRDEV_FREE) {
/* Now we need to reset the board */
@@ -694,11 +703,6 @@ static int twa_chrdev_ioctl(struct inode *inode, struct
file *file, unsigned int
tw_dev->host->host_no, TW_DRIVER, 0xc,
cmd);
retval = TW_IOCTL_ERROR_OS_EIO;
- spin_lock_irqsave(tw_dev->host->host_lock, flag
Bug#402499: initramfs-tools: depmod wastes space and time, please replace it with a modules.dep file
On Mon, 11 Dec 2006, Russell Coker wrote: > On Monday 11 December 2006 08:23, maximilian attems <[EMAIL PROTECTED]> > wrote: > > nice idea, but in initramfs the depmod call is blazingly fast! > > this can be easily timed in a qemu image. > > so nacked. > > The execution time is a minor issue. it was brought forward multiple times and showed to be false. > The major issue is that the depmod > program is simply larger than a full modules.dep file when compressed. Given > that most sane configurations will not have the complete set of kernel > modules (I use modules=list for a very small set of modules) the modules.dep > file will often be smaller than depmod when uncompressed. > > Using the modules.dep file saves initramfs size in every case, and saves > memory in some common cases. first of all MODULES=most is the default, so that is the common case! the case you brought up had a small 1k difference, so that's not the place to optimize. > > i really don't see your antipathy on BUSYBOX=n > > there you can get rid of glibc which is taking a _huge_ > > place on initramfs. > > > I use lvm root over a software RAID-1 on all my important machines (apart > from > laptops which use LVM-root but no RAID). Therefore glibc is required in the > initramfs for both LVM and RAID. If I'm going to have glibc there anyway > then I might as well take advantages of the benefits that busybox offers! > > If there were klibc versions of mdadm and vgchange then things would be > different. hmm ok, i thought you were squeezing for some embedded board. there i would consider also aboves possibility othere than that i don't see an improvement. > Given that the quality of support for root on LVM and RAID has increased > significantly for etch (was it even in the installer before etch?) and that > cryptsetup (which is dynamically linked) is now supported for root it seems > likely that a very large portion of etch users will have glibc in their > initramfs, in fact a majority of users might have it. sure by default any etch user will have glibc on initramfs due to busysbox, udev and module-init-tools. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: reassign 402552 to kernel-package
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.26 > reassign 402552 kernel-package Bug#402552: initramfs-tools: Invalid option to readlink: missing depends on newer version? Bug reassigned from package `initramfs-tools' to `kernel-package'. > 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#401916: initramfs-tools: [powerpc64] i-t tries to mount RAID/LVM stuff before the disk are up -> unbootable
On Sun, Dec 10, 2006 at 10:39:45AM +0100, maximilian attems wrote: > On Wed, 06 Dec 2006, Sven Luther wrote: > > > Package: initramfs-tools > > Severity: critical > > Justification: breaks the whole system > > hmm yes i know of that situation it affects a certain range of roots. > > > > Today i went to the datacenter to reboot the xserve G5 i have there, for > > some > > random reason, and what was not my surprise to notice that the box didn't > > come > > up anymore. > > > > After some dmesg examination, i noticed that the sata disks did come up only > > after i-t tried to bring up the RAID and LVM stuff, which is really not > > nice. > > the trouble is that udevsellte exists to early that mean when > the scsi/usb discs are not up yet. > hitting raid/lvm2 roots on those devices and more general lilo boots > as there you have no root dev to wait for. > i notified udev upstream for it, but got no response i'll reask privately. > http://marc.theaimsgroup.com/?l=linux-scsi&m=116189244404693&w=2 Yeah, please do, we really need to fix this before etch is out, i don't think that having a server who cannot reboot sometimes is something we want to ship in etch. > > Furthermore, playing offline without any info with the box, i was not able > > to > > convince i-t to mount the partition and investigate, but well, i guess i > > would > > have been able to do so if i had the code available, or more time to > > investigate. > > you should have rerun the early initramfs-tools stages, see init. > than it works. Ah, that was the missing info. I searched a bit, but didn't find easily what to do, and then i had to leave. I will be at the box on thursday again. Now, as a temporary workaround, maybe one solution, if RAID/LVM was not found is to delay for a given time (1/2 minute ? a configurable time ?), and then try again. Another nice thing would be able to rerun the early initramfs-tools stages, or maybe even have a stamp of each completed stage, and a single command which allow to restart the detection from there ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#402552: initramfs-tools: Invalid option to readlink: missing depends on newer version?
Package: initramfs-tools Version: 0.85b Severity: normal Setting up linux-image-2.6.18-3-686 (2.6.18-7) ... Hmm. The package shipped with a symbolic link /lib/modules/2.6.18-3-686/source However, I can not read the target: No such file or directory Therefore, I am deleting /lib/modules/2.6.18-3-686/source Running depmod. Finding valid ramdisk creators. Using mkinitramfs-kpkg to build the ramdisk. readlink: invalid option -- m Try `readlink --help' for more information. readlink: invalid option -- m Try `readlink --help' for more information. initrd.img() points to (/boot/initrd.img-2.6.17-2-686) -- doing nothing at /var /lib/dpkg/info/linux-image-2.6.18-3-686.postinst line 585. readlink: invalid option -- m Try `readlink --help' for more information. readlink: invalid option -- m Try `readlink --help' for more information. vmlinuz() points to (/boot/vmlinuz-2.6.17-2-686) -- doing nothing at /var/lib/d pkg/info/linux-image-2.6.18-3-686.postinst line 585. Running postinst hook script /sbin/update-grub. -- Package-specific info: -- /proc/cmdline root=/dev/mapper/diskvg-rootlv ro console=ttyS1,115200n8 console=tty0 -- /proc/filesystems cramfs ext3 -- lsmod Module Size Used by ipv6 222304 20 ppdev 8516 0 lp 10852 0 smbfs 57176 3 tcp_diag1824 0 inet_diag 11048 5 tcp_diag dummy 2948 0 mousedev 10788 1 tsdev 7392 0 i2c_i8018236 0 i2c_core 19552 1 i2c_i801 parport_pc 32132 1 parport33160 3 ppdev,lp,parport_pc floppy 54276 0 i82875p_edac6244 0 edac_mc12964 1 i82875p_edac sg 30972 0 psmouse34600 0 serio_raw 6596 0 8250_pnp8704 0 evdev 9088 0 intel_agp 21116 1 agpgart29864 1 intel_agp shpchp 34272 0 pci_hotplug27196 1 shpchp pcspkr 3040 0 rtc12340 1 ext3 118568 2 jbd50292 1 ext3 mbcache 8324 1 ext3 dm_mirror 18928 0 dm_snapshot16032 0 dm_mod 50424 5 dm_mirror,dm_snapshot raid10 20928 0 raid6 102416 0 raid5 29824 1 xor14184 2 raid6,raid5 raid1 20416 1 raid0 7712 0 multipath 8224 0 linear 5504 0 md_mod 68916 9 raid10,raid6,raid5,raid1,raid0,multipath,linear ide_generic 1376 0 [permanent] sd_mod 18592 12 ide_cd 35680 0 cdrom 32448 1 ide_cd uhci_hcd 20424 0 ehci_hcd 28040 0 mptspi 16236 9 mptscsih 21504 1 mptspi e1000 100248 0 usbcore 111616 3 uhci_hcd,ehci_hcd mptbase46208 2 mptspi,mptscsih scsi_transport_spi 22176 1 mptspi scsi_mod 123080 5 sg,sd_mod,mptspi,mptscsih,scsi_transport_spi piix9476 0 [permanent] generic 4420 0 [permanent] ide_core 111016 4 ide_generic,ide_cd,piix,generic 3c59x 40232 0 mii 5312 1 3c59x thermal12904 0 processor 25512 1 thermal fan 4516 0 -- kernel-img.conf do_symlinks = yes relative_links = yes do_bootloader = no do_bootfloppy = no do_initrd = yes link_in_boot = no postinst_hook = /sbin/update-grub postrm_hook = /sbin/update-grub -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (400, 'testing'), (300, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.17-2-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=UTF-8) Versions of packages initramfs-tools depends on: ii busybox-cvs-static20040623-1 Standalone rescue shell with tons ii cpio 2.5-1.3GNU cpio -- a program to manage ar ii klibc-utils 1.4.30-1 small statically-linked utilities ii module-init-tools 3.3-pre3-1 tools for managing Linux kernel mo ii udev 0.103-1/dev/ and hotplug management daemo -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
