freebsd stable - Nov 2005 - Trouble with amd64

Since this references 6.0-RELEASE it should have been sent to -stable, or
since it references amd64 specifically it should have been sent to -amd64.
Rerouting to -stable.

On Wed, 23 Nov 2005, Nils Berzins wrote:
> Hi !
>
> Few days ago I downloaded release 6.0 ISOs, in hope that I will finally be
> able to run FreeBSD on my home computer. Unfortunately, booting from CD
dies
> with:
>
> > panic: sym: VTOBUS FAILED !
>
> Is there something I can do to get around this error, or do I just wait for
> more less stable 7.0 :-(
According to the code this panic occurs when there is a problem with the
DMA memory management. Typically we see this when the driver is not 64-bit
clean, but I'd find that hard to believe with amd64 since the same driver
runs on sparc64 fine (and must since many Sun machines have embedded sym
controllers).

Unfortunately it doesn't help that the sym driver has its own bizarre DMA
management. It uses busdma but its kinda bolted on over the old
memory-block management. Not going to make it any easier to debug.
> P.S. I have ASUS A8V-E Deluxe with Athlon 64D.
Can we get the dmesg from this system?

-- 
Doug White                    |  FreeBSD: The Power to Serve
dwhite@gumbysoft.com          |  www.FreeBSD.org

On Wed, Nov 30, 2005 at 02:05:55PM -0800, Doug White
wrote:
> On Wed, 23 Nov 2005, Nils Berzins wrote:
> 
> > Hi !
> >
> > Few days ago I downloaded release 6.0 ISOs, in hope that I will
finally be
> > able to run FreeBSD on my home computer. Unfortunately, booting from
CD dies
> > with:
> >
> > > panic: sym: VTOBUS FAILED !
> >
> > Is there something I can do to get around this error, or do I just
wait for
> > more less stable 7.0 :-(
> 
> According to the code this panic occurs when there is a problem with the
> DMA memory management. Typically we see this when the driver is not 64-bit
> clean, but I'd find that hard to believe with amd64 since the same
driver
> runs on sparc64 fine (and must since many Sun machines have embedded sym
> controllers).
> 
> Unfortunately it doesn't help that the sym driver has its own bizarre
DMA
> management. It uses busdma but its kinda bolted on over the old
> memory-block management. Not going to make it any easier to debug.
sym(4) devices don't work on amd64.  I sent one to scottl a while ago,
but the release has kept him busy.  If someone else want's to take a
shot at it, you can get LSI-Logic sym(4) cards for $40 or less if you
get a minimal white box OEM card.

-- Brooks

-- 
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529  9BF0 5D8E 8BE9 F238 1AD4
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :
http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20051130/67689a0c/attachment.bin

On Wed, Nov 30, 2005 at 03:24:08PM -0800, Brooks Davis
wrote:
> sym(4) devices don't work on amd64.
If the OP would please send a PR about this, it would at least let other
folks know that the problem exists.

This is probably also a good idea for whatever other drivers are not
64-bit clean (I do not know of anyplace else we are tracking that issue,
e.g. a project page?)

mcl