The word is that there is a problem but it is a software problem. For
some reason the virtual hub gives an IOERROR, but I haven't had the time
or seen the need to figure that one out.
It seems to be harmless though.
nick
> And what is the word on thise IOERROR's given by my kernel when its ini
On Fri, Jul 28, 2000 at 02:17:31PM -0700, Andrey A. Chernov wrote:
> I too. The only way I can avoid this panic is
>
> 1) Remove /erc/rc.shutdown (which write files)
> 2) Do several syns manually before reboot.
>
> In all other situations I got this panic.
Just another way (suggested
On Fri, Jul 28, 2000 at 11:36:26AM -0700, Scott Flatman wrote:
> On Fri, 28 Jul 2000, Brian Fundakowski Feldman wrote:
>
> > I havne't been able to reproduce this, but this case is going to have
> > more to do with analysis of the code than with "debugging", I think.
> > By chance are you running
On Fri, 28 Jul 2000, Brian Fundakowski Feldman wrote:
> I havne't been able to reproduce this, but this case is going to have
> more to do with analysis of the code than with "debugging", I think.
> By chance are you running with softupdates enabled on /? If I can
> reproduce it here, I will spe
I'm running with softupdates on /, and it has happened to me several times.
On Fri, 28 Jul 2000, Brian Fundakowski Feldman wrote:
> On Fri, 28 Jul 2000, Sheldon Hearn wrote:
>
> >
> > Just a quick note to let you two gentlement know that the problem
> > persists with rev 1.107 of buf.h.
> >
On Fri, 28 Jul 2000, Sheldon Hearn wrote:
>
> Just a quick note to let you two gentlement know that the problem
> persists with rev 1.107 of buf.h.
>
> Brian, these are realy easy for me to reproduce on my own box here. Do
> you want to send me the stuff for maintaining the queues that you sai
On Wed, 26 Jul 2000 16:43:04 MST, Kirk McKusick wrote:
> I have had a number of complaints of this sort which seem to be
> somehow related to recursive buffer locks. Since the recursive
> locks are only needed to prevent deadlock when mounting snapshots
> I decided to back out the use of recurs
On Wed, 26 Jul 2000, Sheldon Hearn wrote:
>
> Hi Kirk,
>
> On Tue, 25 Jul 2000 11:28:47 MST, Kirk McKusick wrote:
>
> > Modified files:
> > sys/kern vfs_bio.c
> > Log:
> > Now that buffer locks can be recursive, we need to delete the panics
> > that complain about them
Hi Kirk,
On Tue, 25 Jul 2000 11:28:47 MST, Kirk McKusick wrote:
> Modified files:
> sys/kern vfs_bio.c
> Log:
> Now that buffer locks can be recursive, we need to delete the panics
> that complain about them.
This looks related. I get it pretty consistently on shutdow
Wilko Bulte wrote:
> On Tue, Jul 25, 2000 at 12:12:20PM -0700, Mike Smith wrote:
> > > 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.0
On Tue, Jul 25, 2000 at 12:12:20PM -0700, Mike Smith wrote:
> > 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 por
> 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, IOERR
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
On Tue, 25 Jul 2000, Ollivier Robert wrote:
> According to Brian Fundakowski Feldman:
> > Actually, I'm pretty certain this is the fix:
>
> Well it won't panic but isn't it putting the problem under the carpet? I
> agree the panic seems to be here temporarely but...
No, I'm really certain this
According to Stephan van Beerschoten:
> But indeed.. isn't removing the panic cal just shifting the problem in
> stead of taking care of the panic-originator ?
That's what is bothering me :-)
> And what is the word on thise IOERROR's given by my kernel when its init'ing
> its usb stack.
It sta
On Tue, 25 Jul 2000, Brian Fundakowski Feldman wrote:
> Actually, I'm pretty certain this is the fix:
>
I have removed the panic-calls. I'll see if my system gets otherwise
unstable.. For now i'll be happy if I get enough time for my make world
to complete before my system hangt itself again :
According to Brian Fundakowski Feldman:
> Actually, I'm pretty certain this is the fix:
Well it won't panic but isn't it putting the problem under the carpet? I
agree the panic seems to be here temporarely but...
--
Ollivier ROBERT -=- Eurocontrol EEC/ITM -=- [EMAIL PROTECTED]
The Postman hits!
Actually, I'm pretty certain this is the fix:
Index: vfs_bio.c
===
RCS file: /usr2/ncvs/src/sys/kern/vfs_bio.c,v
retrieving revision 1.260
diff -u -r1.260 vfs_bio.c
--- vfs_bio.c 2000/07/11 22:07:43 1.260
+++ vfs_bio.c 2000/0
On Tue, 25 Jul 2000, Ollivier Robert wrote:
> I just got two panics tonight, the same each time. Current from yesterday,
> after the latest round of patch from Kirk. The second panic is exactly the
> same including the trace.
Welp, I didn't get em before, but I do now. I'll see what I can do to
On Tue, 25 Jul 2000, Jun Kuriyama wrote:
> At 25 Jul 2000 07:37:43 GMT,
> Ollivier Robert <[EMAIL PROTECTED]> wrote:
> > I just got two panics tonight, the same each time. Current from yesterday,
> > after the latest round of patch from Kirk. The second panic is exactly the
> > same including the
At 25 Jul 2000 07:37:43 GMT,
Ollivier Robert <[EMAIL PROTECTED]> wrote:
> I just got two panics tonight, the same each time. Current from yesterday,
> after the latest round of patch from Kirk. The second panic is exactly the
> same including the trace.
It seems I've got same panics. But sometim
panicstr: lockmgr: pid 5, not exclusive lock holder 0 unlocking
panic messages:
---
panic: bqrelse: multiple refs
syncing disks... panic: lockmgr: pid 5, not exclusive lock holder 0 unlocking
Uptime: 1h34m18s
iconv_mod_handler
#0 boot (howto=260) at ../../kern/kern_shutdown.c:303
#1 0xc016eb78 in
22 matches
Mail list logo
