https://bugzilla.novell.com/show_bug.cgi?id=445442 Cyril Hrubis changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |kernel-maintainers@forge.provo.novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=445442 User kq8z67r6309fo9001@sneakemail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=445442#c2 Henryk Hecht changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|kq8z67r6309fo9001@sneakemail.com | --- Comment #2 from Henryk Hecht 2008-12-09 21:09:01 MST --- I've tried .18 about two dozen times since comment #1, and have been unable to duplicate this even once. It certainly happened thrice before, but I can't get it to happen again. Maybe it depends on something accessing the disk during shutdown (updatedb?), but even trying to make sure there was some extra I/O happening didn't help. Hardware checks out, at least insofar as memtest, smartctl, etc. don't find any problems. In any case, I'm not sure there was a kernel oops, the "oops" is actually printed by the init script, which might be a poor choice of words. I remain a little concerned about this given the consequences, but as I'm not having any luck reproducing it anymore, so maybe it is best to INVALID or WORKSFORME it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.