On Thu, 03 Jun 2010 10:44:32 +0300
Alexander Motin wrote:
> Bruce Cran wrote:
> > I've been setting up an amd64 VirtualBox machine with the latest
> > 9-CURRENT and got the following panic when booting it (another
> > machine updated and booting at the same time didn't panic):
> >
> > ata1: WARN
On 6/3/2010 12:43 AM, Alexander Motin wrote:
Matthew Jacob wrote:
Hmm. I just fixed that at Panasas, and I'm pretty sure that I gave the
patch to Alexander Motin to put in.
Do you mean one committed at r207221 or something else?
yes
Bruce Cran wrote:
> I've been setting up an amd64 VirtualBox machine with the latest
> 9-CURRENT and got the following panic when booting it (another machine
> updated and booting at the same time didn't panic):
>
> ata1: WARNING - READ_TOC read data overrun 18>12
> panic: mtx_lock of destroyed mu
Matthew Jacob wrote:
> Hmm. I just fixed that at Panasas, and I'm pretty sure that I gave the
> patch to Alexander Motin to put in.
Do you mean one committed at r207221 or something else?
>> I've been setting up an amd64 VirtualBox machine with the latest
>> 9-CURRENT and got the following panic
Hmm. I just fixed that at Panasas, and I'm pretty sure that I gave the
patch to Alexander Motin to put in.
I've been setting up an amd64 VirtualBox machine with the latest
9-CURRENT and got the following panic when booting it (another machine
updated and booting at the same time didn't panic):
I've been setting up an amd64 VirtualBox machine with the latest
9-CURRENT and got the following panic when booting it (another machine
updated and booting at the same time didn't panic):
ata1: WARNING - READ_TOC read data overrun 18>12
panic: mtx_lock of destroyed mutex @ /usr/src/sys/kern/kern_s
