Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 16 Dec 2010 13:27:14 -0600
From:      Adam Vande More <amvandemore@gmail.com>
To:        "Li-Lun Wang (Leland Wang)" <llwang@infor.org>
Cc:        freebsd-emulation@freebsd.org
Subject:   Re: kern/150186: [parallels] [panic] Parallels Desktop: CDROM disconnected leads to panic, eventually
Message-ID:  <AANLkTi=Pxe_PvNCXnvWvKVGcoX7QYwyV6TZ=%2Bn=HcZQF@mail.gmail.com>
In-Reply-To: <201012161920.oBGJKBIK051717@freefall.freebsd.org>
References:  <201012161920.oBGJKBIK051717@freefall.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Dec 16, 2010 at 1:20 PM, Li-Lun Wang (Leland Wang) <llwang@infor.org
> wrote:

>   I think I may have stumbled upon the same issue after I updated my
>  installed ports, including hald.  I run a FreeBSD 8.1-stable amd64 (not
>  the latest but a few months old) in virtual box on a windows 7 x64
>  host.  If I disable hald or the cdrom device in virtual box, or run the
>  same FreeBSD installation natively, the problem doesn't seem to occur.
>  When the problem does occur, I get the following messages (not
>  necessarily in any particular order):
>
>  ata0: WARNING - unknown CMD (0x4a) read data overrun 18>8
>  ata0: WARNING - READ_TOC read data overrun 18>12
>  ata0: WARNING - PREVENT_ALLOW read data overrun 18>0
>  ata0: WARNING - TEST_UNIT_READY read data overrun 18>0
>
>  These messages repeat seemingly at random for a few times.  Eventually
>  the box might panic.
>

Interesting, I also found the same to be true.  An additional point is that
I tried with atapicam loaded and there were also some strange behavior.  The
VM takes a couple of minutes to recognize /dev/cd0.

-- 
Adam Vande More



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTi=Pxe_PvNCXnvWvKVGcoX7QYwyV6TZ=%2Bn=HcZQF>