Bug#533493: linux-image-2.6.30-1-amd64: continual stream of errors on floppy drive
Hi there, I observe the same behavior. Workaround for me is to disable the floppy in the BIOS settings, but of course the drive does not work under linux (the floppy module is not even loaded). Motherboard is an Asus A8N-E. -- I tell them to turn to the study of mathematics, for it is only there that they might escape the lusts of the flesh. -- Thomas Mann, The Magic Mountain -- Caselle da 1GB, trasmetti allegati fino a 3GB e in piu' IMAP, POP3 e SMTP autenticato? GRATIS solo con Email.it http://www.email.it/f Sponsor: GRATIS: 250 Biglietti da Visita + 1 elegante Porta biglietti metallico! Spese di spedizione escluse. Offerta limitata, fai in fretta! Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=8956d=22-6 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#480034: linux-image-2.6.25-1-amd64: No sound after suspend-to-ram an wake-up (snd_hda_intel)
Dear all, some help came from the bugzilla.kernel.org page: http://bugzilla.kernel.org/show_bug.cgi?id=10662#c4 It worked for me and fixed the problem. Not sure now where to put this fix (alsa? kernel? udev?), if you need me to file another bugreport against a different package I'll be happy to do it. Thanks everyone for your interest, this bug can be closed, I think. -- Immanuel doesn't pun, he Kant. -- Email.it, the professional e-mail, gratis per te: http://www.email.it/f Sponsor: Fanatico di moto? Visita Motostorm.it: abbigliamento ed accessori per la tua moto delle migliori marche Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=7847d=1-6 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#480034: linux-image-2.6.25-1-amd64: No sound after suspend-to-ram an wake-up (snd_hda_intel)
I have filed bug #10662: http://bugzilla.kernel.org/show_bug.cgi?id=10662 Arnaud: I couldn't find which application was blocking snd_hda_intel so I didn't add that information to the bug report. If you can, please comment on the upstream bug. -- Jesus died to take our wibbles away, so now we can go to zonk. -- Email.it, the professional e-mail, gratis per te: http://www.email.it/f Sponsor: Motostorm.it vendita online di abbigliamento moto caschi ed accessori delle migliori marche a prezzi scontati Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=7846d=10-5 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#480034: linux-image-2.6.25-1-amd64: No sound after suspend-to-ram an wake-up (snd_hda_intel)
I'd like to report that I observe the same behaviour on my machine. With 2.6.24 sound after resume from suspend-to-ram works, while with 2.6.25 there's no output. Applications seem to work just fine, playing the tracks, but no sound comes out. I'm not sure how to help debugging this, any pointers welcome. -- Email.it, the professional e-mail, gratis per te: http://www.email.it/f Sponsor: Scopri le tue passioni con Leonardo.it! Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=7614d=20080509 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#480034: linux-image-2.6.25-1-amd64: No sound after suspend-to-ram an wake-up (snd_hda_intel)
Hello Maximilian, thank you for answering. how do you suspend? I just close the lid of the laptop. Just to complete information: [EMAIL PROTECTED]:~$ lspci | grep -i audio 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03) did you try: echo mem /sys/power/state I did and the machine went properly in sleep. When I woke it up, this is all I could find in /var/log/messages: May 9 13:47:38 vasquez kernel: [ 186.601919] PM: Syncing filesystems ... done. May 9 13:47:54 vasquez kernel: [ 188.092004] Freezing user space processes ... (elapsed 0.00 seconds) done. May 9 13:47:54 vasquez kernel: [ 188.092813] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done. May 9 13:47:54 vasquez kernel: [ 188.092974] Suspending console(s) May 9 13:47:54 vasquez kernel: [ 188.093498] ACPI: PCI interrupt for device :00:02.0 disabled May 9 13:47:54 vasquez kernel: [ 192.182003] sd 0:0:0:0: [sda] Synchronizing SCSI cache May 9 13:47:54 vasquez kernel: [ 192.182122] sd 0:0:0:0: [sda] Stopping disk May 9 13:47:54 vasquez kernel: [ 189.435728] ricoh-mmc: Suspending. May 9 13:47:54 vasquez kernel: [ 189.435755] ricoh-mmc: Controller is now re-enabled. May 9 13:47:54 vasquez kernel: [ 189.435855] ACPI: PCI interrupt for device :06:01.1 disabled May 9 13:47:54 vasquez kernel: [ 189.474817] sky2 eth1: disabling interface May 9 13:47:54 vasquez kernel: [ 189.506943] ACPI: PCI interrupt for device :02:00.0 disabled May 9 13:47:54 vasquez kernel: [ 189.566994] ACPI: PCI interrupt for device :03:00.0 disabled May 9 13:47:54 vasquez kernel: [ 190.104859] ACPI: PCI interrupt for device :00:1d.7 disabled May 9 13:47:54 vasquez kernel: [ 190.281801] ACPI: PCI interrupt for device :00:1d.2 disabled May 9 13:47:54 vasquez kernel: [ 190.281854] ACPI: PCI interrupt for device :00:1d.1 disabled May 9 13:47:54 vasquez kernel: [ 190.281907] ACPI: PCI interrupt for device :00:1d.0 disabled May 9 13:47:54 vasquez kernel: [ 190.491171] ACPI: PCI interrupt for device :00:1b.0 disabled May 9 13:47:54 vasquez kernel: [ 190.667848] ACPI: PCI interrupt for device :00:1a.7 disabled May 9 13:47:54 vasquez kernel: [ 190.758960] ACPI: PCI interrupt for device :00:1a.1 disabled May 9 13:47:54 vasquez kernel: [ 190.758992] ACPI: PCI interrupt for device :00:1a.0 disabled May 9 13:47:54 vasquez kernel: [ 190.762897] ACPI: Preparing to enter system sleep state S3 May 9 13:47:54 vasquez kernel: [ 190.765106] Disabling non-boot CPUs ... May 9 13:47:54 vasquez kernel: [ 190.878894] CPU 1 is now offline May 9 13:47:54 vasquez kernel: [ 190.878900] SMP alternatives: switching to UP code May 9 13:47:54 vasquez kernel: [ 190.882813] CPU1 is down May 9 13:47:54 vasquez kernel: [ 190.882883] Enabling non-boot CPUs ... May 9 13:47:54 vasquez kernel: [ 190.899022] SMP alternatives: switching to SMP code May 9 13:47:54 vasquez kernel: [ 190.900485] Booting processor 1/2 APIC 0x1 May 9 13:47:54 vasquez kernel: [ 194.664936] Initializing CPU#1 May 9 13:47:54 vasquez kernel: [ 194.664936] Calibrating delay using timer specific routine.. 4389.13 BogoMIPS (lpj=8778263) May 9 13:47:54 vasquez kernel: [ 194.664936] CPU: L1 I cache: 32K, L1 D cache: 32K May 9 13:47:54 vasquez kernel: [ 194.664936] CPU: L2 cache: 4096K May 9 13:47:54 vasquez kernel: [ 194.664936] CPU 1/1 - Node 0 May 9 13:47:54 vasquez kernel: [ 194.664936] CPU: Physical Processor ID: 0 May 9 13:47:54 vasquez kernel: [ 194.664936] CPU: Processor Core ID: 1 May 9 13:47:54 vasquez kernel: [ 194.664936] Intel(R) Core(TM)2 Duo CPU T7500 @ 2.20GHz stepping 0a May 9 13:47:54 vasquez kernel: [ 194.664936] CPU1 is up May 9 13:47:54 vasquez kernel: [ 191.057619] ACPI: PCI Interrupt :00:1a.0[A] - GSI 16 (level, low) - IRQ 16 May 9 13:47:54 vasquez kernel: [ 191.057675] usb usb3: root hub lost power or was reset May 9 13:47:54 vasquez kernel: [ 191.057706] ACPI: PCI Interrupt :00:1a.1[B] - GSI 17 (level, low) - IRQ 17 May 9 13:47:54 vasquez kernel: [ 191.057758] usb usb4: root hub lost power or was reset May 9 13:47:54 vasquez kernel: [ 191.070907] ACPI: PCI Interrupt :00:1a.7[C] - GSI 18 (level, low) - IRQ 18 May 9 13:47:54 vasquez kernel: [ 191.086954] ACPI: PCI Interrupt :00:1b.0[A] - GSI 21 (level, low) - IRQ 21 May 9 13:47:54 vasquez kernel: [ 191.087263] ACPI: PCI Interrupt :00:1d.0[A] - GSI 23 (level, low) - IRQ 23 May 9 13:47:54 vasquez kernel: [ 191.087314] usb usb5: root hub lost power or was reset May 9 13:47:54 vasquez kernel: [ 191.087332] ACPI: PCI Interrupt :00:1d.1[B] - GSI 19 (level, low) - IRQ 19 May 9 13:47:54 vasquez kernel: [ 191.087383] usb usb6: root hub lost power or was reset May 9 13:47:54 vasquez kernel: [ 191.087401] ACPI: PCI Interrupt :00:1d.2[C] - GSI 18 (level, low) - IRQ 18 May 9 13:47:54 vasquez kernel: [ 191.087452] usb usb7: root hub lost power or was reset
Bug#480034: linux-image-2.6.25-1-amd64: No sound after suspend-to-ram an wake-up (snd_hda_intel)
On Fri, 2008-05-09 at 14:19 +0200, maximilian attems wrote: hmm i have 2.6.25-rc1 + git4 running fine on my x61s you could test it too - http://photon.itp.tuwien.ac.at/~mattems/ Hello Maximilian, I did a couple more tests with both your 2.6.26-rc1 and vanilla 2.6.25.2. The latter is compiled using the .config from 2.6.25-1-amd64 from Debian. Additionally, I report the output in /var/log/messages from 2.6.24-1-amd64. Test metodology: 1) Boot the machine (Asus Z37E running Sid) 2) Start a media player (in my case Banshee) 3) Play a song 4) Pause the song 5) Close the lid to suspend 6) Resume 7) Press play again 2.6.24-1-amd64: sound comes back after the resume. May 9 23:58:04 vasquez gnome-power-manager: (jack) Suspending computer. Reason: The lid has been closed on battery power. May 9 23:58:08 vasquez kernel: sky2 eth1: disabling interface May 9 23:58:36 vasquez kernel: Syncing filesystems ... done. May 9 23:58:36 vasquez kernel: Freezing user space processes ... (elapsed 0.00 seconds) done. May 9 23:58:36 vasquez kernel: Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done. May 9 23:58:36 vasquez kernel: Suspending console(s) May 9 23:58:36 vasquez kernel: sd 0:0:0:0: [sda] Stopping disk May 9 23:58:36 vasquez kernel: ACPI: PCI interrupt for device :06:01.1 disabled May 9 23:58:36 vasquez kernel: ACPI: PCI interrupt for device :02:00.0 disabled May 9 23:58:36 vasquez kernel: ACPI: PCI interrupt for device :00:1d.7 disabled May 9 23:58:36 vasquez kernel: ACPI: PCI interrupt for device :00:1d.2 disabled May 9 23:58:36 vasquez kernel: ACPI: PCI interrupt for device :00:1d.1 disabled May 9 23:58:36 vasquez kernel: ACPI: PCI interrupt for device :00:1d.0 disabled May 9 23:58:36 vasquez kernel: ACPI: PCI interrupt for device :00:1b.0 disabled May 9 23:58:36 vasquez kernel: ACPI: PCI interrupt for device :00:1a.7 disabled May 9 23:58:36 vasquez kernel: ACPI: PCI interrupt for device :00:1a.1 disabled May 9 23:58:36 vasquez kernel: ACPI: PCI interrupt for device :00:1a.0 disabled May 9 23:58:36 vasquez kernel: Disabling non-boot CPUs ... May 9 23:58:36 vasquez kernel: CPU 1 is now offline May 9 23:58:36 vasquez kernel: SMP alternatives: switching to UP code May 9 23:58:36 vasquez kernel: CPU1 is down May 9 23:58:36 vasquez kernel: Enabling non-boot CPUs ... May 9 23:58:36 vasquez kernel: SMP alternatives: switching to SMP code May 9 23:58:36 vasquez kernel: Booting processor 1/2 APIC 0x1 May 9 23:58:36 vasquez kernel: Initializing CPU#1 May 9 23:58:36 vasquez kernel: Calibrating delay using timer specific routine.. 4388.84 BogoMIPS (lpj=8777699) May 9 23:58:36 vasquez kernel: CPU: L1 I cache: 32K, L1 D cache: 32K May 9 23:58:36 vasquez kernel: CPU: L2 cache: 4096K May 9 23:58:36 vasquez kernel: CPU 1/1 - Node 0 May 9 23:58:36 vasquez kernel: CPU: Physical Processor ID: 0 May 9 23:58:36 vasquez kernel: CPU: Processor Core ID: 1 May 9 23:58:36 vasquez kernel: Intel(R) Core(TM)2 Duo CPU T7500 @ 2.20GHz stepping 0a May 9 23:58:36 vasquez kernel: CPU1 is up May 9 23:58:36 vasquez kernel: ACPI: PCI Interrupt :00:02.0[A] - GSI 16 (level, low) - IRQ 16 May 9 23:58:36 vasquez kernel: ACPI: PCI Interrupt :00:1a.0[A] - GSI 16 (level, low) - IRQ 16 May 9 23:58:36 vasquez kernel: usb usb1: root hub lost power or was reset May 9 23:58:36 vasquez kernel: ACPI: PCI Interrupt :00:1a.1[B] - GSI 17 (level, low) - IRQ 17 May 9 23:58:36 vasquez kernel: usb usb2: root hub lost power or was reset May 9 23:58:36 vasquez kernel: ACPI: PCI Interrupt :00:1a.7[C] - GSI 18 (level, low) - IRQ 18 May 9 23:58:36 vasquez kernel: ACPI: PCI Interrupt :00:1b.0[A] - GSI 21 (level, low) - IRQ 21 May 9 23:58:36 vasquez kernel: ACPI: PCI Interrupt :00:1d.0[A] - GSI 23 (level, low) - IRQ 23 May 9 23:58:36 vasquez kernel: usb usb3: root hub lost power or was reset May 9 23:58:36 vasquez kernel: ACPI: PCI Interrupt :00:1d.1[B] - GSI 19 (level, low) - IRQ 19 May 9 23:58:36 vasquez kernel: usb usb4: root hub lost power or was reset May 9 23:58:36 vasquez kernel: ACPI: PCI Interrupt :00:1d.2[C] - GSI 18 (level, low) - IRQ 18 May 9 23:58:36 vasquez kernel: usb usb5: root hub lost power or was reset May 9 23:58:36 vasquez kernel: ACPI: PCI Interrupt :00:1d.7[A] - GSI 23 (level, low) - IRQ 23 May 9 23:58:36 vasquez kernel: ACPI: PCI Interrupt :00:1f.1[A] - GSI 19 (level, low) - IRQ 19 May 9 23:58:36 vasquez kernel: Coming out of suspend... May 9 23:58:36 vasquez kernel: ACPI: PCI Interrupt :02:00.0[A] - GSI 19 (level, low) - IRQ 19 May 9 23:58:36 vasquez kernel: ata2: SATA link down (SStatus 0 SControl 300) May 9 23:58:36 vasquez kernel: ata3: SATA link down (SStatus 0 SControl 300) May 9 23:58:36 vasquez kernel: ACPI: PCI Interrupt :06:01.1[B] - GSI 17 (level, low) - IRQ 17 May 9 23:58:36 vasquez kernel: ata4: SATA link down (SStatus 0 SControl 300) May 9 23:58:36 vasquez kernel: ata1: SATA
Re: iwl4965 and rf_kill switch [was: Re: 2.6.24-rc7 experimental upload]
With the most recent 2.6.24-rc8 wireless is turned on by default. The rf_kill switch is still not togglable (is that english?), but at least wireless works. -- Best Regards, Jack Linux User #264449 Powered by Debian GNU/Linux on AMD64 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: iwl4965 and rf_kill switch [was: Re: 2.6.24-rc7 experimental upload]
On Mon, 14 Jan 2008 19:00:25 +0100, maximilian attems wrote: yep iwlwifi is still quite a young driver, 2.6.24 inclusion uncovered quite some bugs (wpa, rfkill, led, ..). although it is already much better then the initial submission we had backported in 2.6.23. Dear Maximilian, thanks for the answer. I have managed to apply the second patch on the bugzilla report, but it does not work. I'll report back to the iwlwifi bugzilla. currently it looks more like a gob it all or not approach http://cvs.fedora.redhat.com/viewcvs/rpms/kernel/devel/linux-2.6- wireless-pending.patch?view=markup quite unsure to advocate aboves huge patch at that point for etch kernel also. so currently prefering to stay on mainline with it. I understand your point of view :) I'll try and get hold of Fedora sources and see if I can work something out. Currently I have a perfectly functioning 2.6.22, so I am not left in the cold and I can experiment freely. Again thanks for your work! -- Best Regards, Jack Linux User #264449 Powered by Debian GNU/Linux on AMD64 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: iwl4965 and rf_kill switch [was: Re: 2.6.24-rc7 experimental upload]
On Sat, 12 Jan 2008 00:20:19 +0100, Jack Malmostoso wrote: The iwlwifi bugzilla does not seem to help on the issue. I think I found a related bugreport: http://bughost.org/bugzilla/show_bug.cgi?id=1209 But the patches do not seem to apply cleanly to 2.6.24-rc7. -- Best Regards, Jack Linux User #264449 Powered by Debian GNU/Linux on AMD64 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
iwl4965 and rf_kill switch [was: Re: 2.6.24-rc7 experimental upload]
On Fri, 11 Jan 2008 18:20:11 +0100, maximilian attems wrote: i announce an 2.6.24-rc7 upload for tomorrow morning. Dear Maximilian, I was just downloading from kernel.org when I read your announcement. Thanks for sparing me a kernel compile :) This 2.6.24-rc7 seems to work just fine but I have an issue with the iwl4965 module. I'll describe my problem here, but if this is not the appropriate place please excuse me and kick me in the right direction. So, when I boot 2.6.24-rc7 on my intel-based laptop the wireless card gets correctly recognized and the iwl4965 module is loaded. The wlan0 interface is created BUT the software rf_kill switch is ON, preventing the card to work. So I check: vasquez:~# cat /sys/bus/pci/devices/\:03\:00.0/rf_kill 2 Ok, makes sense. Let's disable the switch: vasquez:~# echo 0 /sys/bus/pci/devices/\:03\:00.0/rf_kill vasquez:~# cat /sys/bus/pci/devices/\:03\:00.0/rf_kill 2 Nothing happened! Let's try with brute force: vasquez:~# rmmod iwl4965 vasquez:~# modprobe iwl4965 vasquez:~# cat /sys/bus/pci/devices/\:03\:00.0/rf_kill 0 Ha! Bingo! But: vasquez:~# ifconfig wlan0 wlan0: error fetching interface information: Device not found and /var/log/messages on modprobing iwl4965 says: Jan 11 23:39:24 vasquez kernel: iwl4965: Intel(R) Wireless WiFi Link 4965AGN driver for Linux, 1.1.17ks Jan 11 23:39:24 vasquez kernel: iwl4965: Copyright(c) 2003-2007 Intel Corporation Jan 11 23:39:24 vasquez kernel: ACPI: PCI Interrupt :03:00.0[A] - GSI 18 (level, low) - IRQ 18 Jan 11 23:39:24 vasquez kernel: iwl4965: Detected Intel Wireless WiFi Link 4965AGN Jan 11 23:39:24 vasquez kernel: iwl4965: Radio disabled by HW RF Kill switch Any advice on how to make this work? Maybe a patch that forces the driver to start with the killswitch OFF? The iwlwifi bugzilla does not seem to help on the issue. Thanks for any help you can give me, and for the great work! -- Best Regards, Jack Linux user #264449 Powered by Debian Sid AMD64 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Cannot build 2.6.23 from Debian sources on AMD64
Hello list, I was trying to compile 2.6.23 starting from Debian sources, pulled from the apt sources published here: http://wiki.debian.org/DebianKernel The 2.6.23 in those repos works a charm: [EMAIL PROTECTED]:~$ uname -a Linux vasquez 2.6.23-1-amd64 #1 SMP Sun Oct 14 03:58:39 UTC 2007 x86_64 GNU/Linux but I wanted to add the tickless option to my AMD64 kernel so I downloaded the hrt-1 patch from: http://www.kernel.org/pub/linux/kernel/people/tglx/hrtimers/2.6.23/ patch-2.6.23-hrt1.patch.bz2 applied it (no problems there), copied the .config file from the Debian kernel package 2.6.23 in /boot and added the option I needed through [EMAIL PROTECTED]:~$ make menuconfig Saved my new configuration and then issued [EMAIL PROTECTED]:~$ make-kpkg --initrd kernel_image After a few seconds I get this error: CC arch/x86_64/vdso/vma.o LDS arch/x86_64/vdso/vdso.lds AS arch/x86_64/vdso/vdso-start.o AS arch/x86_64/vdso/vdso-note.o CC arch/x86_64/vdso/vclock_gettime.o CC arch/x86_64/vdso/vgetcpu.o CC arch/x86_64/vdso/vvar.o SYSCALL arch/x86_64/vdso/vdso.so /usr/bin/ld: section .data [ff700900 - ff700917] overlaps section .text [ff700600 - ff700923] /usr/bin/ld: arch/x86_64/vdso/vdso.so: section .data lma 0xff700900 overlaps previous sections /usr/bin/ld: arch/x86_64/vdso/vdso.so: section .note lma 0xff700918 overlaps previous sections /usr/bin/ld: arch/x86_64/vdso/vdso.so: section .eh_frame_hdr lma 0xff700930 overlaps previous sections /usr/bin/ld: arch/x86_64/vdso/vdso.so: section .eh_frame lma 0xff700968 overlaps previous sections /usr/bin/ld: arch/x86_64/vdso/vdso.so: section .dynamic lma 0xff700a08 overlaps previous sections /usr/bin/ld: arch/x86_64/vdso/vdso.so: section .useless lma 0xff700af8 overlaps previous sections collect2: ld returned 1 exit status make[2]: *** [arch/x86_64/vdso/vdso.so] Error 1 make[1]: *** [arch/x86_64/vdso] Error 2 make[1]: Leaving directory `/usr/src/linux-source-2.6.23' make: *** [debian/stamp-build-kernel] Error 2 I have searched the interweb and it looks like a known problem, but it also says that it's been fixed in -rc8. I can post the complete log (including .config) if it's needed. Thanks for any help! [EMAIL PROTECTED]:~$ COLUMNS=200 dpkg -l linux-source* ii linux-source-2.6.23 2.6.23-1~experimental.1~snapshot.9653Linux kernel source for version 2.6.23 with Debian patches -- Best Regards, Jack Linux user #264449 Powered by Debian Sid AMD64 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#428399: Followup to #427514
Hi there Maximilian, I found this bug and I think that it's what's blocking my report #427514. I guess my 2.6.20 works because its initramfs has been created with the old version, while the newer kernels don't because of initramfs-tools = 0.88. Anyway, I have checked what has been suggested in the thread: /lib/udev/vol_id -t /dev/md0 and the output was LVM2_member To my surprise, since I never had LVM on this machine. In #427972 it was suggested that it could be the partitioner's fault: this machine has been partitioned only once at install time, with the d-i. Should this be reported against d-i or against (I think) parted? It is potentially very very troublesome... Anyway, I have tried to blank the sectors of the two partitions member of /dev/md0 as well as /dev/md0 itself, but with no luck, the output is still the same and the system does not boot. Is there any additional idea? It's worth noticing that if I mount manually the root: mount -t ext3 /dev/md0 /root and then exit the initramfs, the system boots just fine. That's why I think it's the same issue as the one of the OP here. Thanks again! -- I'm pretending I'm pulling in a TROUT! Am I doing it correctly?? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#427514: linux-image-2.6.21-1-amd64: System does not boot with 2.6.21-4
On Mon, 2007-06-04 at 22:30 +0200, maximilian attems wrote: please keep the bug report on cc for future mails, thanks. Sorry, I always forget about that :) hmm the question is if sda and sdb come up early enough for mdadm, did you try to boot with rootdelay=11 and no break arg? Yes they do, as /dev/md0 is created before the boot stops in busybox. And this happens without rootdelay too, so I guess the problem does not lie there. I compared the output before /sbin/init in 2.6.20 and 2.6.21 and they look absolutely the same. mdadm --examine --scan ARRAY /dev/md0 level=raid1 num-devices=2 UUID=877c34c4:dfed29c7:4338e75f:35082da1 ARRAY /dev/md1 level=raid1 num-devices=2 UUID=6f583480:58ae2560:eac2cfa7:882022da ARRAY /dev/md2 level=raid1 num-devices=2 UUID=9dae3f6b:a3e79fbb:6044c75b:9f1939bd The UUID match the ones in mdadm.conf, so I guess there's nothing corrupted. mdadm --assemble --scan --run --auto=yes md: md2 stopped md: bind sdb3 md: bind sda3 raid1: raid set md2 active with 2 out of 2 mirrors mdadm: /dev/md2 has been started with 2 drives md: md1 stopped md: bind sdb2 md: bind sda2 raid1: raid set md1 active with 2 out of 2 mirrors mdadm: /dev/md1 has been started with 2 drives And at this point in the initramfs I have /dev/md[0-2] ready to go... how could I mount them manually and resume the boot procedure? I tried to mount /dev/md0 /root but it does not work. -- Others will look to you for stability, so hide when you bite your nails. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#427514: linux-image-2.6.21-1-amd64: System does not boot with 2.6.21-4
Subject: linux-image-2.6.21-1-amd64: System does not boot with 2.6.21-4 Package: linux-image-2.6.21-1-amd64 Version: 2.6.21-5~snapshot.8808 Severity: critical Justification: breaks the whole system *** Please type your report below this line *** Hi there, since I have installed 2.6.21-4 from unstable I cannot boot my system anymore. First my configuration: an Asus A8N-E (nforce4) motherboard with two SATA disks. The disks are configured in a software RAID1 using mdadm: /dev/md0 is my / /dev/md1 is my swap /dev/md2 is my /home If I start the system with 2.6.20 it boots fine. Here's a picture of the end of the initramfs and the start of the normal boot: http://www.flickr.com/photos/[EMAIL PROTECTED]/530049031/ The system reaches /sbin/init and it boots just fine. Here is what happens with 2.6.21: http://www.flickr.com/photos/[EMAIL PROTECTED]/530049047/ Something goes wrong in the initramfs, and despite /dev/md0 is started, it can't be mounted. At this point I have tried to toy around in the initramfs, read the /scripts directory but couldn't understand how to make the system move along. (btw, I could really use a pager in there... I hate vi :D) It should be noted that I can start my other two RAID arrays without problems! Please ignore the fact that my 2.6.21 is now a snapshot from the Debian Kernel Team (btw, I have tried also 2.6.22rc3 but the problem is still there) as the problem arised with the upgrade from 2.6.21-3 and -4 from unstable. I don't recall any udev or initramfs-tools upgrade that could have broken the system, especially since 2.6.20 works just fine. Additionally the changelog between -3 and -4 is extremely short so no luck there. Thanks for any help you might give me. -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.20-1-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.21-1-amd64 depends on: ii e2fsprog 1.39+1.40-WIP-2007.04.07+dfsg-2 ext2 file system utilities and lib ii initramf 0.88tools for generating an initramfs ii module-i 3.3-pre11-1 tools for managing Linux kernel mo ii yaird [l 0.0.12-20 Yet Another mkInitRD linux-image-2.6.21-1-amd64 recommends no packages. -- debconf information: linux-image-2.6.21-1-amd64/prerm/removing-running-kernel-2.6.21-1-amd64: true shared/kernel-image/really-run-bootloader: true linux-image-2.6.21-1-amd64/postinst/bootloader-error-2.6.21-1-amd64: linux-image-2.6.21-1-amd64/preinst/abort-install-2.6.21-1-amd64: linux-image-2.6.21-1-amd64/prerm/would-invalidate-boot-loader-2.6.21-1-amd64: true linux-image-2.6.21-1-amd64/preinst/abort-overwrite-2.6.21-1-amd64: linux-image-2.6.21-1-amd64/preinst/overwriting-modules-2.6.21-1-amd64: true linux-image-2.6.21-1-amd64/postinst/create-kimage-link-2.6.21-1-amd64: true linux-image-2.6.21-1-amd64/preinst/lilo-initrd-2.6.21-1-amd64: true linux-image-2.6.21-1-amd64/postinst/old-initrd-link-2.6.21-1-amd64: true linux-image-2.6.21-1-amd64/postinst/old-system-map-link-2.6.21-1-amd64: true linux-image-2.6.21-1-amd64/postinst/old-dir-initrd-link-2.6.21-1-amd64: true linux-image-2.6.21-1-amd64/preinst/elilo-initrd-2.6.21-1-amd64: true linux-image-2.6.21-1-amd64/postinst/depmod-error-2.6.21-1-amd64: false linux-image-2.6.21-1-amd64/preinst/failed-to-move-modules-2.6.21-1-amd64: linux-image-2.6.21-1-amd64/preinst/lilo-has-ramdisk: linux-image-2.6.21-1-amd64/preinst/bootloader-initrd-2.6.21-1-amd64: true linux-image-2.6.21-1-amd64/preinst/initrd-2.6.21-1-amd64: linux-image-2.6.21-1-amd64/postinst/kimage-is-a-directory: * linux-image-2.6.21-1-amd64/preinst/already-running-this-2.6.21-1-amd64: linux-image-2.6.21-1-amd64/postinst/depmod-error-initrd-2.6.21-1-amd64: false linux-image-2.6.21-1-amd64/postinst/bootloader-test-error-2.6.21-1-amd64: -- BOFH excuse #38: secretary plugged hairdryer into UPS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#427514: linux-image-2.6.21-1-amd64: System does not boot with 2.6.21-4
On Mon, 2007-06-04 at 19:12 +0200, maximilian attems wrote: please post the output for check: cat /etc/fstab cat /proc/mdstat cat /etc/mdadm/mdadm.conf Hi Maximilian, thanks for the quick answer! Here's the output you asked for: [EMAIL PROTECTED]:~$ cat /etc/fstab # /etc/fstab: static file system information. # # file system mount point type options dump pass proc/proc procdefaults0 0 /dev/md0/ ext3user_xattr,errors=remount-ro 0 1 /dev/md2/home ext3user_xattr 0 2 /dev/hda/media/cdrom0 udf,iso9660 ro,user,noauto 0 0 /dev/fd0/media/floppy0 vfatrw,user,noauto 0 0 # Swap /dev/md1noneswapsw 0 0 # ia32 chroot /home /var/chroot/sid-ia32/home none bind0 0 /tmp/var/chroot/sid-ia32/tmp none bind0 0 proc/var/chroot/sid-ia32/proc proc defaults0 0 /dev/var/chroot/sid-ia32/dev none bind0 0 [EMAIL PROTECTED]:~$ cat /proc/mdstat Personalities : [raid1] md1 : active raid1 sda2[0] sdb2[1] 497920 blocks [2/2] [UU] md2 : active raid1 sda3[0] sdb3[1] 229046656 blocks [2/2] [UU] md0 : active raid1 sda1[0] sdb1[1] 14651136 blocks [2/2] [UU] unused devices: none [EMAIL PROTECTED]:~$ cat /etc/mdadm/mdadm.conf DEVICE partitions ARRAY /dev/md2 level=raid1 num-devices=2 UUID=9dae3f6b:a3e79fbb:6044c75b:9f1939bd ARRAY /dev/md1 level=raid1 num-devices=2 UUID=6f583480:58ae2560:eac2cfa7:882022da ARRAY /dev/md0 level=raid1 num-devices=2 UUID=877c34c4:dfed29c7:4338e75f:35082da1 MAILADDR root try to boot with break=mount and please check which devices are up adding rootdelay=9 should shorten the time to land into console also you have more as pager there in busybox ;) Uhm not really sure what you mean here: I saw /dev/sda and /dev/sdb and all the normal motherboard output. check inside too fstype /dev/md0 There it is: (initramfs) fstype /dev/md0 FSTYPE=ext3 FSSIZE=15002763264 Hope this helps, just ask for any additional info you might need! -- Have you seen the latest Japanese camera? Apparently it is so fast it can photograph an American with his mouth shut! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
