Bug#902229: reassign rather than close?
Hello, I faced this very same issue today. googling this bug report was extremely useful: I deleted timidity, and now sound is back. Obviously this is no solution, as I (or someone else) will need timidity eventually. I understand this is not a kernel related issue, but it is still a serious issue anyway: timidity may grab the sound card at random moments, making sound unusable. I cannot tell who is actual package (timidity? systemd?) responsible for this nor how this can be corrected (maybe insert an extra delay before the timidity daemon is started?), but it sure requires a fix. So shouldn't this bug be reassigned rather than closed? Thanks! Best, Nick
Bug#683726: closed by Julien Cristau
As suggested, I replaced the nvidia driver with nouveau: now sleepresume work like breeze (prompter than with nvidia!). Even the glx acceleration is more than fair: I'll stick to nouveau. In conclusion, the kernel is fine, this breakage was a problem of the interaction with the closed-source driver: let the guys at nvidia find a fix... ;-) Thank you, ciao, N. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50408b35.1040...@mi.infm.it
Bug#683726: closed by Julien Cristau jcris...@debian.org (Re: Bug#683726: additional info)
I will remove the nvidia driver and retest everything under nouveau. However I have little hope that it will work, since prior to installing nvidia I had tested nouveau extensively: suspend-resume had never worked under the open-source driver. This bug is quite likely related to the graphic card restarting into a broken state, and this of course due to the nvidia driver, except it used to work fine with the previous kernel revision, so apparently it is some change in the kernel which causes a regression in this interaction. If anything interesting turns out with the nouveau driver, I'll report it here. Best, Nick -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/501cf80b.6030...@mi.infm.it
Bug#359266: linux-image-2.6.15-1-686: generates Bad page state at miscellaneous processes, sometime crashes
Moritz Muehlenhoff wrote: On Mon, Mar 27, 2006 at 04:53:04PM +0200, Nicola Manini wrote: Package: linux-image-2.6.15-1-686 Version: 2.6.15-8 Severity: normal *** Please type your report below this line *** Occasionally the kernel broadcasts a message such as: Message from sysl...@localhost at Mon Mar 27 14:19:59 2006 ... localhost kernel: Bad page state at free_hot_cold_page (in process 'XFree86', pa ge c13ff320) Does this error still occur with more recent kernel versions? No, never seen any more since 2.6.18 or maybe even earlier. Cheers, and season's greetings, Nick -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#360893: acknowledged by developer (Re: Bug#360893: udev takes too long to create /dev/hda... and system drops to a shell)
try to regnerate your initramfs with latest: update-initramfs -u I did: no change, even with initramfs-tool 0.60 well that will only update newest kernel so to update the 2.6.15, that would have to be specified with -k version aka update-initramfs -u -k 2.6.15-1-686 Hmm, first, before the kernel upgrade I did the suggested update-initramfs -u -k 2.6.15-1-686, and tried to reboot with no success. Next I did the kernel upgrade to 2.6.16, did not bother to update-initramfs -u, and this one worked fine. thanks for the feedback, closing bug report. OK, thank you for your kind help, ciao Nick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#360893: udev takes too long to create /dev/hda... and system drops to a shell
sure the rescue shell can't fix itself magically ;) Well, if you read my initial bug post, you see that before the upgrade it used to sort of fix itself up after a while. One could eventually boot 2.6.15 bu exiting the shell. Not any more. please post from the busybox shell: * the last line of messages you see * cat /proc/cmdline * cat /proc/modules before rebooting check that fstype recognises your root fs: # /usr/lib/klibc/bin/fstype /dev/hda1 I attach a file with all the required infos. The boot process makes a long pause (1-2 mins) after it writes Begin: Waiting for root file system... ... and then it quickly comes out with the ALERT and BusyBox lines. I hope that helps. Thank you, ciao, Nick OUTPUT OF cat /proc/cmdline in working 2.6.8: FSTYPE=ext3 FSSIZE=19998441472 root=/dev/hda1 ro OUTPUT OF cat /proc/modules in working 2.6.8: mousedev 10476 2 - Live 0xf8981000 psmouse 20360 0 - Live 0xf8a96000 ipv6 264772 10 - Live 0xf8b01000 ds 18756 0 - Live 0xf89d yenta_socket 21728 0 - Live 0xf8933000 pcmcia_core 70868 2 ds,yenta_socket, Live 0xf8aa2000 snd_via82xx 29540 1 - Live 0xf89c7000 snd_ac97_codec 69988 1 snd_via82xx, Live 0xf8a04000 snd_pcm_oss 55080 0 - Live 0xf89f5000 snd_mixer_oss 20096 2 snd_pcm_oss, Live 0xf897b000 snd_pcm 98728 2 snd_via82xx,snd_pcm_oss, Live 0xf89db000 snd_timer 25732 1 snd_pcm, Live 0xf89b5000 snd_page_alloc 11752 2 snd_via82xx,snd_pcm, Live 0xf892f000 gameport 4704 1 snd_via82xx, Live 0xf892c000 snd_mpu401_uart 7968 1 snd_via82xx, Live 0xf8886000 snd_rawmidi 25124 1 snd_mpu401_uart, Live 0xf8973000 snd_seq_device 8200 1 snd_rawmidi, Live 0xf8882000 snd 57156 9 snd_via82xx,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device, Live 0xf8985000 soundcore 10272 2 snd, Live 0xf884a000 ehci_hcd 32004 0 - Live 0xf891b000 uhci_hcd 33136 0 - Live 0xf8946000 usbcore 118980 4 ehci_hcd,uhci_hcd, Live 0xf8996000 sata_via 7428 0 - Live 0xf8847000 libata 41700 1 sata_via, Live 0xf893a000 scsi_mod 125228 1 libata, Live 0xf8953000 8139too 26112 0 - Live 0xf8924000 mii 5120 1 8139too, Live 0xf8844000 capability 4520 0 - Live 0xf8841000 commoncap 7232 1 capability, Live 0xf882c000 ide_cd 42656 0 - Live 0xf890f000 cdrom 40732 1 ide_cd, Live 0xf884e000 rtc 12760 0 - Live 0xf8838000 ext3 127240 2 - Live 0xf88a jbd 62616 1 ext3, Live 0xf888f000 mbcache 9348 1 ext3, Live 0xf881e000 ide_generic 1408 0 - Live 0xf883f000 via82cxxx 14332 1 - Live 0xf88c1000 ide_disk 19296 4 - Live 0xf8889000 ide_core 139940 4 ide_cd,ide_generic,via82cxxx,ide_disk, Live 0xf885e000 unix 28756 181 - Live 0xf882f000 font 8320 0 - Live 0xf8822000 vesafb 6656 0 - Live 0xf8815000 cfbcopyarea 3872 1 vesafb, Live 0xf881c000 cfbimgblt 3040 1 vesafb, Live 0xf881a000 cfbfillrect 3776 1 vesafb, Live 0xf8818000 OUTPUT OF /usr/lib/klibc/bin/fstype /dev/hda1 in working 2.6.8: FSTYPE=ext3 FSSIZE=19998441472 LAST FEW LINES OF MESSAGES BEFORE FAILURE OF BOOT 2.6.15: hda: Maxtor 6Y080L0, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 hdc: HL-DT-STDVD-ROM GDR8163B, ATAPI CD/DVD-ROM drive hdd: HL-DT-ST GCE-8526B, ATAPI CD/DVD-ROM drive ide1 at 0x170-0x177,0x376 on irq 15 Done. Begin: Mounting root file system... ... Begin: Running /scripts/local-top ... Done. Begin: Waiting for root file system... ... Done. ALERT! /dev/hda1 does not exist. Dropping to a shell! BusyBox v1.00-pre10 (Debian 20040623-1) Built-in shell (ash) Enter 'help' for a list of built-in commands. /bin/sh: can't access tty; job control turned off OUTPUT of cat /proc/cmdline in shell after boot failure of 2.6.15: root=/dev/hda1 ro OUTPUT of cat /proc/modules in shell after boot failure of 2.6.15: ide_generic 1120 0 [permanent], Live 0xf882f000 via82cxxx 8164 0 [permanent], Live 0xf881b000 generic 4260 0 [permanent], Live 0xf8832000 ide_core 112800 3 ide_generic,via82cxxx,generic, Live 0xf88d3000 sata_via 8260 0 - Live 0xf884d000 ehci_hcd 28904 0 - Live 0xf888c000 uhci_hcd 28016 0 - Live 0xf883c000 libata 51020 1 sata_via, Live 0xf887e000 scsi_mod 125736 1 libata, Live 0xf8896000 8139too 25088 0 - Live 0xf8845000 8139cp 19488 0 - Live 0xf8836000 mii 5056 2 8139too,8139cp, Live 0xf88e usbcore 113284 3 ehci_hcd,uhci_hcd, Live 0xf8851000 thermal 13416 0 - Live 0xf882a000 processor 22912 1 thermal, Live 0xf8823000 fan 4580 0 - Live 0xf8805000
Bug#360893: udev takes too long to create /dev/hda... and system drops to a shell
The kernel 2.6.8-2-686 cannot use the current udev but boots fine, except that X does not start, since it finds no mouse. sure there you would need to load mousedev by hand or have it listed in /etc/modules.. The first option works fine, the second option lets X come up, but the mouse is not responding. which version of initramfs-tools do you use? aka output of: dpkg -l initramfs-tools ii initramfs-tool 0.53c tools for generating an initramfs please try out the unstable initramfs-tools version 0.59b I did: complete disaster. After the udev checks, the scrips come up with a message Waiting for the root filesystem or something of that kind. Except that, afterwards, the /dev/hd* entries are never generated. Of course, after a few minutes the scripts drop out to a shell, but further waiting/exiting does not help. I left the computer up all night, with no success. So, I decided I had better go back to initramfs-tool 0.53c , but that also wouldn't help! I even forced a purge of both udev and initramfs-tool and reinstalled them, but the unbootability of kernel 2.6.15 persists! Also, the same yesterday unseen message about Waiting... pops up. This is extramely surprising, as I checked that I have successfully downgraded to ii initramfs-tools 0.53c tools for generating an initramfs Indeed, by booting on 2.6.8, when I grep Wait /usr/share/initramfs-tools/scripts/* I get nothing. However, when my 2.6.15 boot fails and I drop to the shell, instead I see that /scripts/local includes that message Waiting It goes as if the damn initramfs-tools 0.59b got somewhere hidden in the system and comes back, with very bad effects... Thank you for any help, Nick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#359266: linux-image-2.6.15-1-686: generates Bad page state at miscellaneous processes, sometime crashes
Package: linux-image-2.6.15-1-686 Version: 2.6.15-8 Severity: normal *** Please type your report below this line *** Occasionally the kernel broadcasts a message such as: Message from [EMAIL PROTECTED] at Mon Mar 27 14:19:59 2006 ... localhost kernel: Bad page state at free_hot_cold_page (in process 'XFree86', pa ge c13ff320) Message from [EMAIL PROTECTED] at Mon Mar 27 14:19:59 2006 ... localhost kernel: flags:0x8000 mapping:0010 mapcount:0 count:0 Message from [EMAIL PROTECTED] at Mon Mar 27 14:19:59 2006 ... localhost kernel: Backtrace: Message from [EMAIL PROTECTED] at Mon Mar 27 14:19:59 2006 ... localhost kernel: Trying to fix it up, but a reboot is needed Similar messages refer to different processes, not just XFree86, so this seems a true kernel problem. See the 3 following examples, extracted from recent /var/log/syslog.* : Mar 21 14:07:10 localhost kernel: Bad page state at free_hot_cold_page (in process 'gam_server', page c15b9420) Mar 21 14:07:10 localhost kernel: flags:0x8000 mapping:0012 mapcount:0 count:0 Mar 21 14:07:10 localhost kernel: Backtrace: Mar 21 14:07:10 localhost kernel: [bad_page+92/146] bad_page+0x5c/0x92 Mar 21 14:07:10 localhost kernel: [free_hot_cold_page+82/179] free_hot_cold_page+0x52/0xb3 Mar 21 14:07:10 localhost kernel: [poll_freewait+60/70] poll_freewait+0x3c/0x46 Mar 21 14:07:10 localhost kernel: [sys_poll+439/451] sys_poll+0x1b7/0x1c3 Mar 21 14:07:10 localhost kernel: [__pollwait+0/154] __pollwait+0x0/0x9a Mar 21 14:07:10 localhost kernel: [sysenter_past_esp+84/117] sysenter_past_esp+0x54/0x75 Mar 21 14:07:10 localhost kernel: Trying to fix it up, but a reboot is needed Mar 22 01:19:40 localhost kernel: Bad page state at free_hot_cold_page (in process 'kswapd0', page c1412420) Mar 22 01:19:40 localhost kernel: flags:0x8000 mapping:0040 mapcount:0 count:0 Mar 22 01:19:40 localhost kernel: Backtrace: Mar 22 01:19:40 localhost kernel: [bad_page+92/146] bad_page+0x5c/0x92 Mar 22 01:19:40 localhost kernel: [free_hot_cold_page+82/179] free_hot_cold_page+0x52/0xb3 Mar 22 01:19:40 localhost kernel: [kmem_freepages+114/140] kmem_freepages+0x72/0x8c Mar 22 01:19:40 localhost kernel: [slab_destroy+88/121] slab_destroy+0x58/0x79 Mar 22 01:19:40 localhost kernel: [free_block+131/183] free_block+0x83/0xb7 Mar 22 01:19:40 localhost kernel: [cache_flusharray+86/122] cache_flusharray+0x56/0x7a Mar 22 01:19:40 localhost kernel: [kmem_cache_free+39/56] kmem_cache_free+0x27/0x38 Mar 22 01:19:40 localhost kernel: [free_buffer_head+32/45] free_buffer_head+0x20/0x2d Mar 22 01:19:40 localhost kernel: [try_to_free_buffers+97/111] try_to_free_buffers+0x61/0x6f Mar 22 01:19:40 localhost kernel: [pg0+945721671/1070281728] ext3_releasepage+0x59/0x63 [ext3] Mar 22 01:19:40 localhost kernel: [shrink_list+603/899] shrink_list+0x25b/0x383 Mar 22 01:19:40 localhost kernel: [shrink_cache+228/514] shrink_cache+0xe4/0x202 Mar 22 01:19:40 localhost kernel: [get_dirty_limits+25/192] get_dirty_limits+0x19/0xc0 Mar 22 01:19:40 localhost kernel: [shrink_zone+176/206] shrink_zone+0xb0/0xce Mar 22 01:19:40 localhost kernel: [balance_pgdat+474/788] balance_pgdat+0x1da/0x314 Mar 22 01:19:40 localhost kernel: [kswapd+198/203] kswapd+0xc6/0xcb Mar 22 01:19:40 localhost kernel: [autoremove_wake_function+0/58] autoremove_wake_function+0x0/0x3a Mar 22 01:19:40 localhost kernel: [kswapd+0/203] kswapd+0x0/0xcb Mar 22 01:19:40 localhost kernel: [kernel_thread_helper+5/11] kernel_thread_helper+0x5/0xb Mar 22 01:19:40 localhost kernel: Trying to fix it up, but a reboot is needed Mar 22 16:03:01 localhost kernel: Bad page state at prep_new_page (in process 'sshd', page c1668520) Mar 22 16:03:01 localhost kernel: flags:0x8000 mapping:0080 mapcount:0 count:0 Mar 22 16:03:01 localhost kernel: Backtrace: Mar 22 16:03:01 localhost kernel: [bad_page+92/146] bad_page+0x5c/0x92 Mar 22 16:03:01 localhost kernel: [prep_new_page+54/94] prep_new_page+0x36/0x5e Mar 22 16:03:01 localhost kernel: [buffered_rmqueue+246/380] buffered_rmqueue+0xf6/0x17c Mar 22 16:03:01 localhost kernel: [get_page_from_freelist+115/140] get_page_from_freelist+0x73/0x8c Mar 22 16:03:01 localhost kernel: [__alloc_pages+74/625] __alloc_pages+0x4a/0x271 Mar 22 16:03:01 localhost kernel: [do_wp_page+248/627] do_wp_page+0xf8/0x273 Mar 22 16:03:01 localhost kernel: [__handle_mm_fault+281/364] __handle_mm_fault+0x119/0x16c Mar 22 16:03:01 localhost kernel: [do_page_fault+355/1184] do_page_fault+0x163/0x4a0 Mar 22 16:03:01 localhost kernel: [do_page_fault+0/1184] do_page_fault+0x0/0x4a0 Mar 22 16:03:01 localhost kernel: [error_code+79/84] error_code+0x4f/0x54 Mar 22 16:03:01 localhost kernel: Trying to fix it up, but a reboot is needed And, for further referece, the syslog for the XFree86 message reported above: Mar 27 14:19:59 localhost kernel: Bad page state at free_hot_cold_page (in process 'XFree86', page c13ff320) Mar 27 14:19:59 localhost
