freeze after many hours up - kernel reports bug in blk-core.c

[ChrisLees]

I am currently in the process of ripping and encoding all my DVDs; as such I have my computer on and working constantly. At some point it will freeze, but only after working for many hours. (5-30 hours)

This has occurred when encoding h.264 multi-threaded in ffmpeg, extracting the contents of 3 DVDs simultaneously, or even just using the computer after performing those sorts of activities. It occurs when using KDE, Gnome or Fluxbox as window manager. I should also mention that I use the system as a casual Samba server too, but it never freezes when any clients are connected.

Parts of the user interface will freeze first, and then after a minute the rest of the computer (including mouse and emergency key combinations). No new programs can be opened while the system is partially frozen. Attempting to switch to a virtual terminal will immediately lock up the whole system, as will pressing Alt-SysRq-R. Only once has this freeze resulted in the keyboard lights flashing, and it's rare to get any kernel messages regarding it, making me believe that the kernel is stopping before being able to sync or actually run the panic function.

Extract from dmesg:

Jan 27 23:06:29 chris-desktop kernel: [42763.631277] GOT WX GET SCAN WX_SEM LOCKGOT WX GET SCAN WX_SEM LOCK<0>------------[ cut here ]------------
Jan 27 23:06:30 chris-desktop kernel: [42947.492918] kernel BUG at /build/buildd/linux-2.6.27/block/blk-core.c:1495!
Jan 27 23:06:30 chris-desktop kernel: [42947.492921] invalid opcode: 0000 [1] SMP
Jan 27 23:06:30 chris-desktop kernel: [42947.492924] CPU 1
Jan 27 23:06:30 chris-desktop kernel: [42947.492926] Modules linked in: nls_iso8859_1 nls_cp437 vfat fat usb_storage libusual isofs udf crc_itu_t arc4 ecb crypto_blkcipher ieee80211_crypt_wep_rtl af_packet binfmt_misc rfcomm sco bridge stp bnep l2cap bluetooth vboxdrv ppdev acpi_cpufreq cpufreq_conservative cpufreq_ondemand cpufreq_powersave cpufreq_stats freq_table cpufreq_userspace video output container pci_slot sbs sbshc wmi battery iptable_filter ip_tables x_tables ac coretemp w83627ehf hwmon_vid sbp2 parport_pc lp parport snd_hda_intel snd_pcm_oss snd_mixer_oss r8187 snd_pcm ieee80211_rtl ieee80211_crypt_rtl evdev nvidia(P) snd_seq_dummy i2c_core snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd soundcore iTCO_wdt iTCO_vendor_support snd_page_alloc intel_agp button pcspkr shpchp pci_hotplug ext3 jbd mbcache sd_mod crc_t10dif sr_mod cdrom pata_acpi ata_generic sg usbhid hid ohci1394 pata_jmicron ieee1394 r8169 mii ata_piix ahci libata scsi_mod sky2 dock ehci_hcd uhci_hcd
Jan 27 23:06:30 chris-desktop kernel: usbcore thermal processor fan fbcon tileblit font bitblit softcursor fuse
Jan 27 23:06:30 chris-desktop kernel: [42947.493001] Pid: 4261, comm: kjournald Tainted: P 2.6.27-11-generic #1
Jan 27 23:06:30 chris-desktop kernel: [42947.493003] RIP: 0010:[<ffffffff80392448>] [<ffffffff80392448>] submit_bio+0xb8/0x120
Jan 27 23:06:30 chris-desktop kernel: [42947.493010] RSP: 0018:ffff88012d12fd00 EFLAGS: 00010246
Jan 27 23:06:30 chris-desktop kernel: [42947.493012] RAX: 0000000000000001 RBX: ffff880105146500 RCX: 0000000000000000
Jan 27 23:06:30 chris-desktop kernel: [42947.493014] RDX: ffff880122f913a0 RSI: ffff880105146500 RDI: 0000000000000001
Jan 27 23:06:30 chris-desktop kernel: [42947.493016] RBP: ffff88012d12fd30 R08: 0000000000000000 R09: ffff880122f913a0
Jan 27 23:06:30 chris-desktop kernel: [42947.493018] R10: ffff880129db8000 R11: 00000000000001a8 R12: ffff880105146500
Jan 27 23:06:30 chris-desktop kernel: [42947.493021] R13: 0000000000000001 R14: ffff880102a77360 R15: 0000000000000200
Jan 27 23:06:30 chris-desktop kernel: [42947.493023] FS: 0000000000000000(0000) GS:ffff88012fc02980(0000) knlGS:0000000000000000
Jan 27 23:06:30 chris-desktop kernel: [42947.493025] CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
Jan 27 23:06:30 chris-desktop kernel: [42947.493027] CR2: 000000004266afc8 CR3: 0000000041602000 CR4: 00000000000006e0
Jan 27 23:06:30 chris-desktop kernel: [42947.493030] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Jan 27 23:06:30 chris-desktop kernel: [42947.493032] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Jan 27 23:06:30 chris-desktop kernel: [42947.493034] Process kjournald (pid: 4261, threadinfo ffff88012d12e000, task ffff88012b6a8000)
Jan 27 23:06:30 chris-desktop kernel: [42947.493036] Stack: ffff8800791e9540 0000000000000063 0000000000000001 ffff880102a77360
Jan 27 23:06:30 chris-desktop kernel: [42947.493041] ffff8800791e9540 ffff880105146500 ffff88012d12fd60 ffffffff80314a86
Jan 27 23:06:30 chris-desktop kernel: [42947.493045] 0000000000000200 ffff88012d1ac318 0000000000000063 ffff880080417380
Jan 27 23:06:30 chris-desktop kernel: [42947.493048] Call Trace:
Jan 27 23:06:30 chris-desktop kernel: [42947.493053] [<ffffffff80314a86>] submit_bh+0xf6/0x130
Jan 27 23:06:30 chris-desktop kernel: [42947.493062] [<ffffffffa01caa46>] journal_submit_data_buffers+0x336/0x350 [jbd]
Jan 27 23:06:30 chris-desktop kernel: [42947.493068] [<ffffffffa01cacc4>] journal_commit_transaction+0x264/0xd00 [jbd]
Jan 27 23:06:30 chris-desktop kernel: [42947.493072] [<ffffffff8025a85b>] ? lock_timer_base+0x3b/0x70
Jan 27 23:06:30 chris-desktop kernel: [42947.493076] [<ffffffff80267060>] ? autoremove_wake_function+0x0/0x40
Jan 27 23:06:30 chris-desktop kernel: [42947.493078] [<ffffffff8025a8ef>] ? try_to_del_timer_sync+0x5f/0x70
Jan 27 23:06:30 chris-desktop kernel: [42947.493085] [<ffffffffa01ceed9>] kjournald+0xe9/0x250 [jbd]
Jan 27 23:06:30 chris-desktop kernel: [42947.493088] [<ffffffff80267060>] ? autoremove_wake_function+0x0/0x40
Jan 27 23:06:30 chris-desktop kernel: [42947.493094] [<ffffffffa01cedf0>] ? kjournald+0x0/0x250 [jbd]
Jan 27 23:06:30 chris-desktop kernel: [42947.493097] [<ffffffff80266c2e>] kthread+0x4e/0x90
Jan 27 23:06:30 chris-desktop kernel: [42947.493100] [<ffffffff80213c99>] child_rip+0xa/0x11
Jan 27 23:06:30 chris-desktop kernel: [42947.493102] [<ffffffff80266be0>] ? kthread+0x0/0x90
Jan 27 23:06:30 chris-desktop kernel: [42947.493105] [<ffffffff80213c8f>] ? child_rip+0x0/0x11
Jan 27 23:06:30 chris-desktop kernel: [42947.493106]
Jan 27 23:06:30 chris-desktop kernel: [42947.493107]
Jan 27 23:06:30 chris-desktop kernel: [42947.493108] Code: 44 00 00 48 c7 c0 80 28 7a 80 48 63 d6 65 48 8b 0c 25 08 00 00 00 48 01 54 08 08 eb c5 66 0f 1f 44 00 00 85 c9 0f 85 75 ff ff ff <0f> 0b eb fe 0f 1f 40 00 48 8b 7b 10 48 8d 75 d0 e8 33 18 fb ff
Jan 27 23:06:30 chris-desktop kernel: [42947.493140] RIP [<ffffffff80392448>] submit_bio+0xb8/0x120
Jan 27 23:06:30 chris-desktop kernel: [42947.493144] RSP <ffff88012d12fd00>
Jan 27 23:06:30 chris-desktop kernel: [42947.493148] ---[ end trace 6bba117c7614c770 ]---
Jan 27 23:07:00 chris-desktop kernel: [42978.239031] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Jan 27 23:07:00 chris-desktop kernel: [42978.239041] ata3.00: cmd a0/01:00:00:00:fc/00:00:00:00:00/a0 tag 0 dma 131072 in
Jan 27 23:07:00 chris-desktop kernel: [42978.239043] cdb 28 00 00 18 da 5a 00 00 40 00 00 00 00 00 00 00
Jan 27 23:07:00 chris-desktop kernel: [42978.239044] res 40/00:02:00:08:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
Jan 27 23:07:00 chris-desktop kernel: [42978.239046] ata3.00: status: { DRDY }
Jan 27 23:07:00 chris-desktop kernel: [42978.239053] ata3: hard resetting link
Jan 27 23:07:01 chris-desktop kernel: [42978.712549] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Jan 27 23:07:01 chris-desktop kernel: [42978.736682] ata3.00: configured for UDMA/133
Jan 27 23:07:01 chris-desktop kernel: [42978.736698] ata3: EH complete

-------
I have seen the traceback on one previous occasion, where Plasma was listed as the running process. Of course, I've had the crash when not running KDE. I have established that the crash is not related to thermal issues or high memory use, and I do not get the crash unless the machine has been on for some hours.

I am running Ubuntu 8.10 64-bit, fully updated from the Proposed repository except for the kernel, which is "2.6.27-11-generic #1 SMP Fri Dec 19 16:29:35 UTC 2008 x86_64 GNU/Linux"

[ChrisLees (christopher-lees)]

Occurred again - just 2.5 hours after resuming from suspend. I had been ripping DVDs to hard disk, then started encoding video files. I also copied a DVD using K9copy which finished before the freeze, and had one Samba client connected. When I realised there was no data going to the Samba client I came through and found the system fully frozen.

I'm attaching the traceback now, and will try disabling the Nvidia driver.

[ChrisLees (christopher-lees)]

Crash still occurs after upgrading to Proposed's latest kernel and running with a completely untainted kernel. In fact it appears to be happening after only a short time of hard work. Since the last time I posted there has been no information printed to dmesg at the time of each freeze.

[ChrisLees (christopher-lees)]

Dmesg's panic reports often list kswap as the crashing process... whenever there is a crash report, of course.

The crashing happens when ripping three DVDs simultaneously, but it has so far not happened when ripping 2 simultaneously.

The latest crash occurred after moving a number of files individually from one hard disk into the trash on KDE 4, in other words when disk use was high. I also managed to consistently crash the computer when running the "iozone" test in Phoronix Test Suite. Disabling swap space seemed to solve the problem for a few days but it is back.

Attached is the dmesg from the last crash. Some programs became unresponsive, with more becoming unresponsive after a few more seconds. Pressing Control-Alt-Backspace froze the machine.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Triaged a while ago but has not had any updated comments for quite some time. Please let us know if this issue remains in the current Ubuntu release, http://www.ubuntu.com/getubuntu/download . If the issue remains, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[ChrisLees (christopher-lees)]

Problem was caused by faulty memory.

[Jeremy Foshee (jeremyfoshee)]

ChrisLees,
    Thank you for following up on this bug. It is always good to know what solves an issue. I am glad that you were able to get the issue fixed for you.

Thanks!

-JFo