> That's hardly a solution or reason.
of course it's not, just that last successful boot had WITNESS configured,
and with the latest patches it hang, compiling without WITNESS allowed
the boot to proceed.
> Still please try the patch (or fresh
> 8-STABLE wit
Daniel Braniss wrote:
>> Daniel Braniss wrote:
On Fri, Jul 23, 2010 at 09:35:55AM +0300, Daniel Braniss wrote:
> It seems that the latest changes (last 7 days) introduced this problem:
> ...
> run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config
> run_inter
> Daniel Braniss wrote:
> >> On Fri, Jul 23, 2010 at 09:35:55AM +0300, Daniel Braniss wrote:
> >>> It seems that the latest changes (last 7 days) introduced this problem:
> >>> ...
> >>> run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config
> >>> run_interrupt_driven_hooks: stil
Daniel Braniss wrote:
>> On Fri, Jul 23, 2010 at 09:35:55AM +0300, Daniel Braniss wrote:
>>> It seems that the latest changes (last 7 days) introduced this problem:
>>> ...
>>> run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config
>>> run_interrupt_driven_hooks: still waiting af
> On Fri, Jul 23, 2010 at 09:35:55AM +0300, Daniel Braniss wrote:
> > It seems that the latest changes (last 7 days) introduced this problem:
> > ...
> > run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config
> > run_interrupt_driven_hooks: still waiting after 120 seconds for xpt
On Fri, Jul 23, 2010 at 09:35:55AM +0300, Daniel Braniss wrote:
> It seems that the latest changes (last 7 days) introduced this problem:
> ...
> run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config
> run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config
>
It seems that the latest changes (last 7 days) introduced this problem:
...
run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config
run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config
run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config
