There were two screen shots attached. The older one was outdated related to 2.6.32 kernel.
But the other was a recent panic. So here is another one. This time I could paste it from the log: last sysfs file: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/PNP0C09:00/PNP0C0A:00/power_supply/BAT0/energy_full Modules linked in: i2c_dev tp_smapi thinkpad_ec lib80211_crypt_wep lib80211_crypt_tkip lib80211_crypt_ccmp radeon ttm drm_kms_helper ehci_hcd ipw2200 libipw yenta_socket i2c_i801 uhci_hcd Pid: 1400, comm: kjournald Not tainted 2.6.36-hardened-r6 #1 1830W7F/1830W7F EIP: 0060:[<0014d697>] EFLAGS: 00010216 CPU: 0 EIP is at journal_commit_transaction+0x6f7/0xd00 EAX: 00e89222 EBX: cc7ae76d ECX: 00000000 EDX: 00000000 ESI: 00000005 EDI: 00000000 EBP: e9c1c4c0 ESP: f695bf04 DS: 0068 ES: 0068 FS: 0000 GS: 00e0 SS: 0068 Process kjournald (pid: 1400, ti=f695a000 task=f70bb0b0 task.ti=f695a000) Stack: 000028cd 26626a70 00029eaf f6ae6800 00000000 00000005 e3834c1c e10ed03c <0> 00000fc4 00000001 f55b1000 f6ae68c0 ebe65e9e 0000681e f7076064 00000000 <0> 10fe2a49 e62673c0 000293ec 000028ce e3e13910 f70bb0b0 005bb206 00000003 Call Trace: [<000028cd>] ? copy_thread+0x1d/0x140 [<00029eaf>] ? switched_to_idle+0x1f/0x60 [<0000681e>] ? write_ldt+0x10e/0x2d0 [<000293ec>] ? finish_task_switch.clone.120.clone.124+0x2c/0x90 [<000028ce>] ? copy_thread+0x1e/0x140 [<005bb206>] ? schedule+0x146/0x3e0 [<0014fb99>] ? kjournald+0x99/0x1b0 [<00046ad0>] ? autoremove_wake_function+0x0/0x40 [<0014fb00>] ? kjournald+0x0/0x1b0 [<000466a4>] ? kthread+0x74/0x80 [<00046630>] ? kthread+0x0/0x80 [<0000455e>] ? kernel_thread_helper+0x6/0x18 Code: 00 b9 03 00 00 00 89 ea e8 67 f7 ff ff 89 d8 ba 17 00 00 00 e8 1b 94 ef ff 89 d8 e8 f4 f3 f7 ff e9 ef fc ff ff 83 6d 40 01 8b 03 <ff> 40 34 71 04 ff 48 34 ce 8b 03 80 48 02 01 8b 44 24 4c 89 da EIP: [<0014d697>] journal_commit_transaction+0x6f7/0xd00 SS:ESP 0068:f695bf04 ---[ end trace 0f9efa514b41f93a ]--- It happens during IO activity. I wouldn't say heavy IO. The memory is OK, the harddrive is perfect. I can dd the whole hdd to my backup booting on a gentoo CD. Regards: Dw. -- dr Tóth Attila, Radiológus, 06-20-825-8057 Attila Toth MD, Radiologist, +36-20-825-8057 2010.December 26.(V) 21:06 időpontban [email protected] ezt írta: > On 26 Dec 2010 at 19:59, "Tóth Attila" wrote: > >> I don't know if it is related or not. I don't use ext4 and have no >> symptoms of disappearing root. I attach a photo taken using a recent >> kernel. The latest crashes I've experienced for the past few months >> prevented syncing, so didn't get logged. The other screen capture is >> older, may not be relevant nowdays. > > it's a different issue, the UDEREF changes haven't been incorporated into > grsec's .32 series yet. looks like some null deref in the filesystem sync > code, but i can't tell what may be causing this. is this something you can > reproduce at will? if so, can you try vanilla? > > >
