RE: mmotm 2008-12-09-15-24: e1000e mutex contention

[Graham, David]

Yes we've got a lot (about 150 on kernelmoops last time I looked), of these reports now, all warnings. They are different than the double-release of a mutex that was found & fixed Yesterday by Andrew Morton, as these are in-e1000e-driver warnings from a mutex_trylock(), and have not, as far as I know, been flagged by LOCKDEP. I am reviewing all the reports to see if the total set of warnings show that driver is at risk for a deadlock. If so, obviously we'll fix it. If not, we might just remove the trylock warning. 

Dave

-----Original Message-----
From: Brandeburg, Jesse 
Sent: Wednesday, December 10, 2008 8:50 AM
To: Jiri Slaby; Kirsher, Jeffrey T; David Miller
Cc: Allan, Bruce W; Waskiewicz Jr, Peter P; Ronciak, John; e1000-devel@xxxxxxxxxxxxxxxxxxxxx; Andrew Morton; Linux kernel mailing list; Graham, David
Subject: RE: mmotm 2008-12-09-15-24: e1000e mutex contention

Jiri Slaby wrote:
> during bootup, I got ton of these:
>
> WARNING: at drivers/net/e1000e/ich8lan.c:413
> e1000_acquire_swflag_ich8lan+0x43/0xf0()
> Hardware name: To Be Filled By O.E.M.
> e1000e mutex contention. Owned by pid -1

I think these are probably due to akpm's patches yesterday.  I think 
they've already been dropped.  The original issue still exists however, as 
reported by Arjan (kerneloops) and others.

We have Dave Graham here working on this, he is not done yet but he is 
making progress.  We hope to have something to post soon.

Jesse
¢éì®&Þ~º&¶¬–+-±éÝ¥Šw®žË±Êâmébžìdz¹Þ)í…æèw*jg¬±¨¶‰šŽŠÝj/êäz¹ÞŠà2ŠÞ¨è­Ú&¢)ß«a¶Úþø®G«éh®æj:+v‰¨Šwè†Ù>Wš±êÞiÛaxPjØm¶ŸÿÃ-»+ƒùdš_