Have *you* disabled Firewire?

[Sean Bruno]

I'm seeing evidence that the Firewire stack has been problematic for a
small, but growing set of users out there.  I see from a perusal of the
mailing lists, that some users are disabling their Firewire stack after
they cannot boot or install FreeBSD.  This usually is due to a panic
preceded by the message:"
        "run_interrupt_driven_hooks - waiting for xpt_config"

This log message was added in the past to provide a diagnostic
indication of a failure.  

If you are one of these folks who have disabled their Firewire driver,
please let me know.  Also get me the following:
        Full boot dmesg output (bootverbose)
        Can you load "firewire"?(in kernel? after boot via module?)
        Can you load "sbp"?(in kernel? after boot via module?)
        *anything* else you might thing is relevant?

Sean


_______________________________________________
freebsd-firewire@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-firewire
To unsubscribe, send any mail to "freebsd-firewire-unsubscribe@..."

[Julian Stecklina-4]

Sean Bruno <sean.bruno@...> writes:

> I'm seeing evidence that the Firewire stack has been problematic for a
> small, but growing set of users out there.  I see from a perusal of the
> mailing lists, that some users are disabling their Firewire stack after
> they cannot boot or install FreeBSD.  This usually is due to a panic
> preceded by the message:"
> "run_interrupt_driven_hooks - waiting for xpt_config"

Panic? Most people reported hangs, haven't they?

> This log message was added in the past to provide a diagnostic
> indication of a failure.  
>
> If you are one of these folks who have disabled their Firewire driver,
> please let me know.  Also get me the following:
> Full boot dmesg output (bootverbose)
> Can you load "firewire"?(in kernel? after boot via module?)
> Can you load "sbp"?(in kernel? after boot via module?)
> *anything* else you might thing is relevant?

I did provide this some months ago for my AMD 780G-based board. Was
there anything that looked suspicious? Is it worth retrying?

Regards,
--
Julian Stecklina

The day Microsoft makes something that doesn't suck is probably the day
they start making vacuum cleaners - Ernst Jan Plugge

_______________________________________________
freebsd-firewire@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-firewire
To unsubscribe, send any mail to "freebsd-firewire-unsubscribe@..."

[Sean Bruno]

[ removing -current ]

On Thu, 2009-08-20 at 23:51 +0200, Julian Stecklina wrote:

> Sean Bruno <sean.bruno@...> writes:
>
> > I'm seeing evidence that the Firewire stack has been problematic for a
> > small, but growing set of users out there.  I see from a perusal of the
> > mailing lists, that some users are disabling their Firewire stack after
> > they cannot boot or install FreeBSD.  This usually is due to a panic
> > preceded by the message:"
> > "run_interrupt_driven_hooks - waiting for xpt_config"
>
> Panic? Most people reported hangs, haven't they?
>

Hangs yes.  If one waits long enough(2 minutes I think), it will panic.

> > This log message was added in the past to provide a diagnostic
> > indication of a failure.  
> >
> > If you are one of these folks who have disabled their Firewire driver,
> > please let me know.  Also get me the following:
> > Full boot dmesg output (bootverbose)
> > Can you load "firewire"?(in kernel? after boot via module?)
> > Can you load "sbp"?(in kernel? after boot via module?)
> > *anything* else you might thing is relevant?
>
> I did provide this some months ago for my AMD 780G-based board. Was
> there anything that looked suspicious? Is it worth retrying?
>
> Regards,

I'm trying to gather information, thanks for the reminder about your
specific hardware. (JMicron based)

I've got the same failures reported with JMicron and NVidia based
controllers.  I will peruse the logs of all the failures and try to come
up with something soon.  :)

Sean

_______________________________________________
freebsd-firewire@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-firewire
To unsubscribe, send any mail to "freebsd-firewire-unsubscribe@..."

[Julian Stecklina-4]

Sean Bruno <sean.bruno@...> writes:

> I'm trying to gather information, thanks for the reminder about your
> specific hardware. (JMicron based)
>
> I've got the same failures reported with JMicron and NVidia based
> controllers.  I will peruse the logs of all the failures and try to come
> up with something soon.  :)

This would be much appreciated! If there is any way to support you on
this, just say so.

Regards,
--
Julian Stecklina

The day Microsoft makes something that doesn't suck is probably the day
they start making vacuum cleaners - Ernst Jan Plugge

_______________________________________________
freebsd-firewire@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-firewire
To unsubscribe, send any mail to "freebsd-firewire-unsubscribe@..."

[Andrew Reilly-3]

On Thu, Aug 20, 2009 at 01:15:14AM -0700, Sean Bruno wrote:

> I'm seeing evidence that the Firewire stack has been problematic for a
> small, but growing set of users out there.  I see from a perusal of the
> mailing lists, that some users are disabling their Firewire stack after
> they cannot boot or install FreeBSD.  This usually is due to a panic
> preceded by the message:"
> "run_interrupt_driven_hooks - waiting for xpt_config"
>
> This log message was added in the past to provide a diagnostic
> indication of a failure.  
>
> If you are one of these folks who have disabled their Firewire driver,
> please let me know.  Also get me the following:
> Full boot dmesg output (bootverbose)
> Can you load "firewire"?(in kernel? after boot via module?)
> Can you load "sbp"?(in kernel? after boot via module?)
> *anything* else you might thing is relevant?

I get the xpt_config waits, but I have not disabled firewire: I
just work around the problem by manually disconnecting the
external drive in question and re-attaching it after the boot
has failed and falled into single-user mode.  It seems to work
fine for post-boot arrival.

Want my bootverbose logs?  (I think that I posted them before,
the first time around, but can probably make a new set.)

Also: this does seem to be a race condition kind of thing,
because in the intervening time I *have* had at least one
successful, hands-off boot.

Cheers,

--
Andrew
_______________________________________________
freebsd-firewire@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-firewire
To unsubscribe, send any mail to "freebsd-firewire-unsubscribe@..."

[Sean Bruno]

> I get the xpt_config waits, but I have not disabled firewire: I
> just work around the problem by manually disconnecting the
> external drive in question and re-attaching it after the boot
> has failed and falled into single-user mode.  It seems to work
> fine for post-boot arrival.
>
> Want my bootverbose logs?  (I think that I posted them before,
> the first time around, but can probably make a new set.)
>
> Also: this does seem to be a race condition kind of thing,
> because in the intervening time I *have* had at least one
> successful, hands-off boot.
>
> Cheers,
>

If you can send me your bootverbose dmesg output, that would be great.

Sean

_______________________________________________
freebsd-firewire@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-firewire
To unsubscribe, send any mail to "freebsd-firewire-unsubscribe@..."