From owner-freebsd-current Tue Jul 25 12: 3: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id 6671837B878; Tue, 25 Jul 2000 12:03:01 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id MAA31510; Tue, 25 Jul 2000 12:12:20 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007251912.MAA31510@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Dampure, Pierre Y." Cc: Stephan van Beerschoten , Brian Fundakowski Feldman , Ollivier Robert , "FreeBSD Current Users' list" , mckusick@mckusick.com Subject: Re: Panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking In-reply-to: Your message of "Tue, 25 Jul 2000 16:27:46 BST." <397DB1F2.F62858@alveley.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 25 Jul 2000 12:12:20 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Stephan van Beerschoten wrote: > > > > And what is the word on thise IOERROR's given by my kernel when its init'ing > > its usb stack. > > > > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > > uhub0: 2 ports with 2 removable, self powered > > uhub0: port 1 power on failed, IOERROR > > uhub0: port 2 power on failed, IOERROR > > > > Funny you should mention that :-) I asked the same question to N. Hibma > a while ago (I get the same problem on my Intel OR840), but so far > haven't had an answer. That's because the message is completely harmless; ignore it. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message