panic: driver error: busdma dflt_lock called

[Rob Garbutt]

Hi all!

I have 1/2 a rack spare in IFL1 (Manchester Computing centre in the Kilburn 
Building, Manchester).  I'm slicing it up into 1 and 2U's for £25 per month 
per 1U or £40 per month for a 2U.  This includes 10GB data transfer per 
month.  Is anybody interested?  Space is limited!

If you are, give myself or Mark a call on 0870 142 0950

cheers and apologies for the blanket mail

Rob Garbutt
Webstyle Internet Ltd


----- Original Message ----- 
From: "Malachi de Ælfweald" <malachid at gmail.com>
To: <freebsd-hardware at freebsd.org>
Sent: Monday, October 03, 2005 4:36 PM
Subject: panic: driver error: busdma dflt_lock called


I asked this question on the freebsd-question list about a week ago, but
still don't have a resolution. Maybe someone here knows?

Asus A8N-SLI Premium
4x250GB Hitachi SATAII on onboard nVidia raid controller configured as
RAID10(0+1)
4GB memory

at the partition screen, I see:
> ad10
> ad4
> ad6
> ad8
> ar0
>
> I assume that the ar0 is the raid, and the others are the drives that make
> up the raid
> I choose ar0
>
> I see a disk with 976784130 sectors (476945MB) so looks like ar0 is the
> right one
> did "A: Use Entire Disk" and "S: Set Bootable"
> chose FreeBSD BootManager
>
> label screen
> ar0s1a / 1024MB UFS2 Y
> ar0s1b swap 8192MB SWAP
> ar0s1d /var 2048MB UFS2+S Y
> ar0s1e /tmp 2048 UFS2+S Y
> ar0s1f /home 8192MB UFS2+S Y
> ar0s1g /burn/image 10240MB UFS2+S Y
> ar0s1h /burn/tmp 15360MB UFS2+S Y
> X /usr 100GB UFS2+S Y
> X /jail 319GB UFS2+S Y
>
> distribution: all
> media: cd/dvd
> commit:
>
> panic: driver error: busdma dflt_lock called
> uptime: ?missed it?
> cannot dump. no dump device defined.
> rebooting
>
_______________________________________________
freebsd-hardware at freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to "freebsd-hardware-unsubscribe at freebsd.org"