Bug#649890: linux-image-2.6-686: Kernel Oops during upgrade, X module FBCON not available after restart
Thanks. I believe you are right. There used to be occasional kernel oopses but I have not seen any kernel oops recently. Is there anything else you would like me to look for that might help narrow down this bug? Axel -- 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/alpine.DEB.2.00.1112281601040.402@localhost.localdomain
Bug#649890: linux-image-2.6-686: Kernel Oops during upgrade, X module FBCON not available after restart
Forwarded Message From: a...@users.sourceforge.net To: Ben Hutchings b...@decadent.org.uk Subject: Re: Bug#649890: linux-image-2.6-686: Kernel Oops during upgrade, X module FBCON not available after restart Date: Sat, 24 Dec 2011 22:33:25 +0100 (CET) Hi, Sorry for delay − very busy at work and a nasty cold. Here's all I could find; HIH. Merry Christmas :-) Axel Nov 24 06:36:55 flora kernel: [387010.699062] PM: Syncing filesystems ... done. Nov 24 06:36:55 flora kernel: [387011.012447] Freezing user space processes ... (elapsed 0.01 seconds) done. Nov 24 06:36:55 flora kernel: [387011.032067] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done. Nov 24 06:36:55 flora kernel: [387011.032112] PM: Preallocating image memory... done (allocated 695949 pages) Nov 24 06:36:55 flora kernel: [387017.081770] PM: Allocated 2783796 kbytes in 6.04 seconds (460.89 MB/s) Nov 24 06:36:55 flora kernel: [387017.081772] Suspending console(s) (use no_console_suspend to debug) Nov 24 06:36:55 flora kernel: [387017.082005] sd 5:0:0:0: [sdd] Synchronizing SCSI cache Nov 24 06:36:55 flora kernel: [387017.284008] sd 4:0:1:0: [sdc] Synchronizing SCSI cache Nov 24 06:36:55 flora kernel: [387017.284522] sd 4:0:0:0: [sdb] Synchronizing SCSI cache Nov 24 06:36:55 flora kernel: [387017.284600] sd 3:0:0:0: [sda] Synchronizing SCSI cache Nov 24 06:36:55 flora kernel: [387017.285200] serial 00:07: disabled Nov 24 06:36:55 flora kernel: [387017.285437] serial 00:06: disabled Nov 24 06:36:55 flora kernel: [387017.285513] pata_sil680 :03:02.0: PCI INT A disabled Nov 24 06:36:55 flora kernel: [387017.300011] advansys :03:00.0: PCI INT A disabled Nov 24 06:36:55 flora kernel: [387017.300108] ata_piix :00:1f.2: PCI INT B disabled Nov 24 06:36:55 flora kernel: [387017.300183] ata_piix :00:1f.1: PCI INT A disabled Nov 24 06:36:55 flora kernel: [387017.404048] HDA Intel :00:1b.0: PCI INT A disabled Nov 24 06:36:55 flora kernel: [387017.442739] ACPI: Preparing to enter system sleep state S4 Nov 24 06:36:55 flora kernel: [387017.443086] PM: Saving platform NVS memory Nov 24 06:36:55 flora kernel: [387017.451712] Disabling non-boot CPUs ... Nov 24 06:36:55 flora kernel: [387017.576008] CPU 1 is now offline Nov 24 06:36:55 flora kernel: [387017.576010] SMP alternatives: switching to UP code Nov 24 06:36:55 flora kernel: [387017.579728] PM: Creating hibernation image: Nov 24 06:36:55 flora kernel: [387017.580001] PM: Need to copy 40172 pages Nov 24 06:36:55 flora kernel: [387017.580001] PM: Restoring platform NVS memory Nov 24 06:36:55 flora kernel: [387017.580001] CPU0: Thermal monitoring enabled (TM2) Nov 24 06:36:55 flora kernel: [387017.580001] Enabling non-boot CPUs ... Nov 24 06:36:55 flora kernel: [387017.580001] SMP alternatives: switching to SMP code Nov 24 06:36:57 flora kernel: [387017.583077] Booting processor 1 APIC 0x1 ip 0x6000 Nov 24 06:36:57 flora kernel: [387017.579624] Initializing CPU#1 Nov 24 06:36:57 flora kernel: [387017.579624] CPU: L1 I cache: 32K, L1 D cache: 32K Nov 24 06:36:57 flora kernel: [387017.579624] CPU: L2 cache: 6144K Nov 24 06:36:57 flora kernel: [387017.579624] CPU: Physical Processor ID: 0 Nov 24 06:36:57 flora kernel: [387017.579624] CPU: Processor Core ID: 1 Nov 24 06:36:57 flora kernel: [387017.579624] CPU1: Thermal monitoring enabled (TM2) Nov 24 06:36:57 flora kernel: [387017.672085] CPU1: Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz stepping 0a Nov 24 06:36:57 flora kernel: [387017.672089] checking TSC synchronization [CPU#0 - CPU#1]: passed. Nov 24 06:36:57 flora kernel: [387017.720367] CPU1 is up Nov 24 06:36:57 flora kernel: [387017.721796] ACPI: Waking up from system sleep state S4 Nov 24 06:36:57 flora kernel: [387017.736403] No ACPI video bus found Nov 24 06:36:57 flora kernel: [387018.098788] HDA Intel :00:1b.0: PCI INT A - GSI 16 (level, low) - IRQ 16 Nov 24 06:36:57 flora kernel: [387018.098832] usb usb2: root hub lost power or was reset Nov 24 06:36:57 flora kernel: [387018.098872] usb usb3: root hub lost power or was reset Nov 24 06:36:57 flora kernel: [387018.098911] usb usb4: root hub lost power or was reset Nov 24 06:36:57 flora kernel: [387018.098950] usb usb5: root hub lost power or was reset Nov 24 06:36:57 flora kernel: [387018.098966] usb usb1: root hub lost power or was reset Nov 24 06:36:57 flora kernel: [387018.102849] ata_piix :00:1f.1: PCI INT A - GSI 18 (level, low) - IRQ 18 Nov 24 06:36:57 flora kernel: [387018.102875] ata_piix :00:1f.2: PCI INT B - GSI 19 (level, low) - IRQ 19 Nov 24 06:36:57 flora kernel: [387018.105153] advansys :03:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16 Nov 24 06:36:57 flora kernel: [387018.105159] saa7134[0]: board init: gpio is 0 Nov 24 06:36:57 flora kernel: [387018.232038] pata_sil680 :03:02.0: PCI INT A - GSI 18 (level, low) - IRQ 18 Nov 24 06:36:57 flora kernel: [387018.232059] sil680: 133MHz clock. Nov 24 06:36:57 flora kernel
Bug#649890: linux-image-2.6-686: Kernel Oops during upgrade, X module FBCON not available after restart
[Please reply-to-all.] On Sat, 2011-12-24 at 22:33 +0100, a...@users.sourceforge.net wrote: [...] Nov 24 07:19:26 flora kernel: [389572.200226] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled Nov 24 07:19:26 flora kernel: [389572.201271] SGI XFS Quota Management subsystem Nov 24 07:19:26 flora kernel: [389572.204530] JFS: nTxBlock = 8192, nTxLock = 65536 Nov 24 07:19:26 flora kernel: [389572.212056] NTFS driver 2.1.29 [Flags: R/W MODULE]. Nov 24 07:19:26 flora kernel: [389572.22] QNX4 filesystem 0.2.3 registered. Nov 24 07:19:26 flora kernel: [389572.236530] *pde = Nov 24 07:19:26 flora kernel: [389572.236537] Modules linked in: btrfs(+) zlib_deflate crc32c libcrc32c ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs exportfs reiserfs ext2 isofs udf crc_itu_t usblp nls_utf8 nls_cp437 vfat fat tun sermouse serport acpi_cpufreq cpufreq_stats cpufreq_userspace cpufreq_powersave cpufreq_conservative parport_pc ppdev lp parport sco bridge stp bnep rfcomm l2cap bluetooth rfkill binfmt_misc fuse ext4 jbd2 crc16 loop snd_hda_codec_realtek saa7134_alsa mt20xx tea5767 tda9887 tda8290 tuner snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_midi i915 snd_rawmidi snd_seq_midi_event drm_kms_helper snd_seq snd_timer snd_seq_device drm snd i2c_algo_bit soundcore snd_page_alloc video saa7134 ir_common v4l2_common videodev v4l1_compat videobuf_dma_sg i2c_i801 videobuf_core tveeprom i2c_core output evdev button rng_core pcspkr processor ext3 jbd mbcache usb_storage sg sd_mod crc_t10dif sr_mod cdrom ata_generic ata_piix floppy uhci_hcd pata_sil680 thermal thermal_sys Nov 24 07:19:26 flora kernel: r8169 mii libata ehci_hcd advansys scsi_mod usbcore nls_base [last unloaded: scsi_wait_scan] Nov 24 07:19:26 flora kernel: [389572.236608] Nov 24 07:19:26 flora kernel: [389572.236611] Pid: 10773, comm: modprobe Not tainted (2.6.32-5-686 #1) MS-7383 So the crash occurs when btrfs is loaded, presumably by os-prober. Nov 24 07:19:26 flora kernel: [389572.236613] EIP: 0060:[c113b801] EFLAGS: 00210282 CPU: 0 Nov 24 07:19:26 flora kernel: [389572.236616] EIP is at strcmp+0x6/0x19 Nov 24 07:19:26 flora kernel: [389572.236618] EAX: EBX: f6f40540 ECX: f6d23450 EDX: e616ea60 Nov 24 07:19:26 flora kernel: [389572.236620] ESI: EDI: e616ea60 EBP: d5e65510 ESP: e6bc1e94 Nov 24 07:19:26 flora kernel: [389572.236622] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 Nov 24 07:19:26 flora kernel: [389572.236627] e616ea60 d5e65510 c10f3aba d5e65510 e6bc1ed4 c10f3b78 d5e65420 fffe Nov 24 07:19:26 flora kernel: [389572.236632] 0 c10f3c0f e6bc1ed4 c10f3ce7 d5e65420 fffe d5e65510 f6d23450 c10f478b Nov 24 07:19:26 flora kernel: [389572.236637] 0 f6d23450 e6bc1f15 f40fde00 f6c02880 Nov 24 07:19:26 flora kernel: [389572.236647] [c10f3aba] ? sysfs_find_dirent+0x13/0x23 Nov 24 07:19:26 flora kernel: [389572.236650] [c10f3b78] ? __sysfs_add_one+0x10/0x69 Nov 24 07:19:26 flora kernel: [389572.236653] [c10f3c0f] ? sysfs_add_one+0x11/0xb8 Nov 24 07:19:26 flora kernel: [389572.236656] [c10f3ce7] ? sysfs_addrm_start+0x31/0x83 Nov 24 07:19:26 flora kernel: [389572.236660] [c10f478b] ? sysfs_do_create_link+0x97/0xed Nov 24 07:19:26 flora kernel: [389572.236663] [c10f47f1] ? sysfs_create_link+0x7/0xa Nov 24 07:19:26 flora kernel: [389572.236667] [c11b1a12] ? device_add+0x187/0x474 Nov 24 07:19:26 flora kernel: [389572.236670] [c113606a] ? kobject_init+0x33/0x69 Nov 24 07:19:26 flora kernel: [389572.236673] [c11b1d85] ? device_create_vargs+0x76/0x96 Nov 24 07:19:26 flora kernel: [389572.236676] [c11b1dc3] ? device_create+0x1e/0x22 Nov 24 07:19:26 flora kernel: [389572.236680] [c1195b53] ? misc_register+0xb3/0xec Nov 24 07:19:26 flora kernel: [389572.236695] [fdb9f000] ? init_btrfs_fs+0x0/0x7d [btrfs] Nov 24 07:19:26 flora kernel: [389572.236709] [fdb9f037] ? init_btrfs_fs+0x37/0x7d [btrfs] Nov 24 07:19:26 flora kernel: [389572.236713] [c100113e] ? do_one_initcall+0x55/0x155 Nov 24 07:19:26 flora kernel: [389572.236716] [c1057949] ? sys_init_module+0xa7/0x1d7 Nov 24 07:19:26 flora kernel: [389572.236719] [c10030fb] ? sysenter_do_call+0x12/0x28 Nov 24 07:19:26 flora kernel: [389572.236754] ---[ end trace 110ea9cfc3c05d58 ]--- [...] btrfs is registering a 'miscellaneous' device driver which is used for some filesystem administration. Its name is compared with the names of all the existing miscellaneous device drivers, but it seems that one of these names has become invalid. I can't found any references to such a bug being found and fixed. One possibility is memory corruption by the BIOS during suspend and resume. I don't think this is likely to be a problem any more since the kernel is careful to avoid using memory that may be overwritten by the BIOS. Also, that was 40 minutes before
Bug#649890: linux-image-2.6-686: Kernel Oops during upgrade, X module FBCON not available after restart
Forwarded Message From: a...@users.sourceforge.net To: Ben Hutchings b...@decadent.org.uk Subject: Re: Bug#649890: linux-image-2.6-686: Kernel Oops during upgrade, X module FBCON not available after restart Date: Sun, 27 Nov 2011 13:29:32 +0100 (CET) Hi, I hope this line from the log answers your question: upgrade linux-image-2.6.32-5-686 2.6.32-38 2.6.32-39 Axel On Fri, 25 Nov 2011, Ben Hutchings wrote: What was the previous version? All changes are logged to /var/log/dpkg.log, but not the source locations. Is there a place where I could find out about them so I can eliminate problematic packages before the upgrade to the next release? -- 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/1322419093.7454.10.camel@deadeye
Bug#649890: linux-image-2.6-686: Kernel Oops during upgrade, X module FBCON not available after restart
On Sun, 2011-11-27 at 13:29 +0100, a...@users.sourceforge.net wrote: Hi, I hope this line from the log answers your question: upgrade linux-image-2.6.32-5-686 2.6.32-38 2.6.32-39 Right. On Fri, 25 Nov 2011, Ben Hutchings wrote: What was the previous version? All changes are logged to /var/log/dpkg.log, but not the source locations. Is there a place where I could find out about them so I can eliminate problematic packages before the upgrade to the next release? If it's the kernel, there's not a whole lot you can do either. (We would like to move to a model where it's easy to keep a known-good version as a fallback, but we're not ready to do that yet.) Version 2.6.32-39 doesn't appear to have any fixes for bugs like the one you described, so this probably is still to be fixed. You said that the system was not completely hung after the 'oops' message, which means the message was probably included in the system log (/var/log/messages or one of the numbered older files). Please can you look for it there and provide the full message (there are start and end markers) plus any other kernel messages from the few minutes before. Ben. -- Ben Hutchings The two most common things in the universe are hydrogen and stupidity. signature.asc Description: This is a digitally signed message part
Bug#649890: linux-image-2.6-686: Kernel Oops during upgrade, X module FBCON not available after restart
Package: linux-image-2.6-686 Version: 2.6.32+29 Severity: important I ran 'aptitude safe-upgrade' (!) this morning a few minutes after waking up the computer from hibernation. During the installation process, a kernel oops was reported on all consoles and the installation process did not finish. After waiting for around twenty minutes, I tried to shut down the machine, but shutdown did not complete; it hang somewhere after Squid shutdown. I had to switch off power. After restarting the machine X cannot be starteed. Using either GDM 3 or Xinit will result in a blank screen. Switching to a console using CtrlAltF2 etc. is possible but GDM 3 or Xinit still have to be ended manually. Xinit reports 'module fbcon not available.' This means my system was rendered unusable by an automatic safe upgrade. -- System Information: Debian Release: 6.0.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-2.6-686 depends on: pn linux-image-2.6.32-5-686 none (no description available) linux-image-2.6-686 recommends no packages. linux-image-2.6-686 suggests no packages. -- no debconf information -- 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/2024160435.2955.66563.reportbug@flora
Bug#649890: linux-image-2.6-686: Kernel Oops during upgrade, X module FBCON not available after restart
On Thu, Nov 24, 2011 at 05:04:35PM +0100, Axel Stammler wrote: Package: linux-image-2.6-686 Version: 2.6.32+29 Severity: important I ran 'aptitude safe-upgrade' (!) this morning a few minutes after waking up the computer from hibernation. During the installation process, a kernel oops was reported on all consoles and the installation process did not finish. After waiting for around twenty minutes, I tried to shut down the machine, but shutdown did not complete; it hang somewhere after Squid shutdown. I had to switch off power. After restarting the machine X cannot be starteed. Using either GDM 3 or Xinit will result in a blank screen. Switching to a console using CtrlAltF2 etc. is possible but GDM 3 or Xinit still have to be ended manually. Xinit reports 'module fbcon not available.' This means my system was rendered unusable by an automatic safe upgrade. It means the old kernel version (or some module in it) was buggy. And there's really not much that we can do to mitigate a crash during the upgrade. Let us know if the new version is stable or not. Also, do you use any additional (out-of-tree) kernel modules? Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- 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/2024183819.gw3...@decadent.org.uk
