lkml.org 
[lkml]   [2006]   [Jun]   [30]   [last100]   RSS Feed
Views: [more markup]  [less markup]  [headers]  [forward] 
 
Messages in this thread
/
DateFri, 30 Jun 2006 09:48:05 +0200
FromRalf Hildebrandt <>
SubjectRe: BUG: held lock freed! with 2.6.17-mm3 and 2.6.17-mm4
* Nathan Scott <nathans@sgi.com>:
> On Thu, Jun 29, 2006 at 10:38:09PM +0200, Ralf Hildebrandt wrote:
> > 2.6.17-mm3 and mm4 both report a "BUG: held lock freed!" while booting
> > up. Find the two dmesg outputs attached.
> 
> Thanks Ralf,
> 
> From the traces, looks like it happens during the unlinked inode list
> processing, just after log recovery (I assume you crashed / rebooted
> without unmounting before this boot?).

Absolutely. The root-fs could not be umounted correctly, since the -mm3 and
-mm4 Kernels sometime produce unkillable processes. One of these
processes had files open on /, thus the reboot left me with an unclean
XFS fs!

-- 
_________________________________________________
  Charité - Universitätsmedizin Berlin
_________________________________________________
  Ralf Hildebrandt
   i.A. Geschäftsbereich Informationsmanagement
   Campus Benjamin Franklin
   Hindenburgdamm 30 | Berlin
   Tel. +49 30 450 570155 | Fax +49 30 450 570962
   Ralf.Hildebrandt@charite.de
   http://www.charite.de
-
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/
\
 
 \ /
  Last update: 2006-06-30 09:50    [from the cache]
©2003-2008