On Wed, 31 May 2006, Neil Brown wrote: > On Tuesday May 30, dean@xxxxxxxxxx wrote: > > On Tue, 30 May 2006, Neil Brown wrote: > > > > > Could you try this patch please? On top of the rest. > > > And if it doesn't fail in a couple of days, tell me how regularly the > > > message > > > kblockd_schedule_work failed > > > gets printed. > > > > i'm running this patch now ... and just after reboot, no freeze yet, i've > > already seen a handful of these: > > > > May 30 17:05:09 localhost kernel: kblockd_schedule_work failed > > May 30 17:05:59 localhost kernel: kblockd_schedule_work failed > > May 30 17:08:16 localhost kernel: kblockd_schedule_work failed > > May 30 17:10:51 localhost kernel: kblockd_schedule_work failed > > May 30 17:11:51 localhost kernel: kblockd_schedule_work failed > > May 30 17:12:46 localhost kernel: kblockd_schedule_work failed > > May 30 17:14:14 localhost kernel: kblockd_schedule_work failed > > 1 every minute or so. That's probably more than I would have > expected, but strongly lends evidence to the theory that this is the > problem. actually i think the rate is higher... i'm not sure why, but klogd doesn't seem to keep up with it: root@neemlark:~# grep -c kblockd_schedule_work /var/log/messages 31 root@neemlark:~# dmesg | grep -c kblockd_schedule_work 8192 i don't have CONFIG_PRINTK_TIME=y ... so i can't read timestamps from dmesg. but cool! if the dmesg spam seems to be a problem i can just comment it out of the patch... i'll let you know if it freezes again. thanks -dean - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
