Am Donnerstag, den 02.12.2010, 18:06 +0100 schrieb Borislav Petkov:
quoted text
> On Thu, Dec 02, 2010 at 11:21:12AM -0500, Tobias Karnat wrote:
> > Am Donnerstag, den 02.12.2010, 16:21 +0100 schrieb Borislav Petkov:
> > > Well, thanks for the photos. I don't have an idea what might cause this
> > > workqueue corruption I'm seeing, all reg/unreg paths look ok. The only
> > > change that came in between .35 and .36.1 I can think of being relevant
> > > is 00740c58541b6087d78418cebca1fcb86dc6077d. You could try backing that
> > > one out to see whether it fixes the issue.
> > 
> > Yes, reverting this fixed the issue!
> > 
> > But why?
> 
> Dang, I know why. This whole ->op_state fumbling is pretty fragile and
> needs de-fragilizing :o).
> 
> Please try out the one below after re-reverting
> 00740c58541b6087d78418cebca1fcb86dc6077d (i.e., ontop of .36.1).
> 
> Thanks.

This patch fixed it.
I have rebooted five times and it does not crash anymore.

Thank you.

Btw, are there any information available regarding the NMI option?

parm:	edac_op_state:EDAC Error Reporting state: 0=Poll,1=NMI (int)

In edac.txt NMI is listed under FUTURE HARDWARE SCANNING.

-Tobias

--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/