On Jan 17, 2008 11:35 AM, Andrew Morton <[EMAIL PROTECTED]> wrote: > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.24-rc8/2.6.24-rc8-mm1/
I'm still seeing my mystery-crash that I had since 2.6.24-rc3-mm2. The crashed kernel was 2.6.24-rc8-mm1 with the following patches: * personal fix for the "do_md_run returned -22"-problem I'm just moving the analyze_sbs(mddev); above the test. * git-sched-fix-bug_on.patch * hotfix-libata-scsi-corruption.patch The crash (captured via serial console): Jan 25 21:40:01 treogen cron[6553]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons ) Jan 25 20:40:44 treogen syslog-ng[4839]: I/O error occurred while writing; fd='5', error='Input/output error (5)' [ 1242.319555] ------------[ cut here ]------------ [ 1242.319557] kernel BUG at lib/list_debug.c:33! [ 1242.319558] invalid opcode: 0000 [1] SMP [ 1242.319560] last sysfs file: /sys/devices/system/cpu/cpu3/cache/index2/shared_cpu_map [ 1242.319562] CPU 3 [ 1242.319563] Modules linked in: The cursor on the receiving machine stayed after the : in the last line, the crashed machine blinked caps lock and scroll lock. I don't have a clue what the syslog-ng error is about or why this line is one hour to early. At 20:40 this kernel wasn't even build yet and syslog-ng started with the correct timezone: Jan 25 21:26:26 treogen syslog-ng[4839]: syslog-ng starting up; version='2.0.6' As I'm seeing this bug during times of both network and hard disk activity, could this be related to the problem discussed in the thread "[PATCH rc8-mm1] hotfix libata-scsi corruption"? The line fixed in the mm-hotfix seems to be to new to cause this in -rc3-mm2, but these alignment problems seem to touch more than this and I'm not clear one how old this might be. (If this matters: The crashing system is running the smartd daemon from smartmontools version 5.37) I hope I will have time to try git-misc-tree on sunday... Torsten -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/