Date: Sat, 22 Feb 1997 14:06:46 -0800 From: Amancio Hasty <hasty@rah.star-gate.com> To: Randall Hopper <rhh@ct.picker.com> Cc: multimedia@FreeBSD.org Subject: Re: New BT848 driver 0.2 Message-ID: <199702222206.OAA09711@rah.star-gate.com> In-Reply-To: Your message of "Sat, 22 Feb 1997 16:44:18 EST." <19970222164418.44306@ct.picker.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Good info!
I will concentrate on the CAP_CONTINOUS functionality.
A cursory analysis of the interrupt status info that you send us seems to
indicate that you are getting excessive PCI errors.
Memory mapped location 0x100 (BKTR_INT_STAT) :
bit 15 Set when a parity error is detected while the initiator is
reading RISC instructions.
Here is a sample output from my P100:
Feb 22 05:51:20 cioloco /kernel: STATUS 0 d000206 30701c
Feb 22 05:51:20 cioloco /kernel: STATUS 0 d000a04 3077a4
Feb 22 05:51:20 cioloco /kernel: STATUS 0 d000a04 3077a4
Feb 22 05:51:20 cioloco /kernel: STATUS 0 c000206 30601c
Feb 22 05:51:20 cioloco /kernel: STATUS 0 c000206 30601c
Feb 22 05:51:20 cioloco /kernel: STATUS 0 c000a04 3067a4
Feb 22 05:51:20 cioloco /kernel: STATUS 0 c000a04 3067a4
Feb 22 05:51:20 cioloco /kernel: STATUS 0 d000206 30701c
Feb 22 05:51:20 cioloco /kernel: STATUS 0 d000206 30701c
Feb 22 05:51:20 cioloco /kernel: STATUS 0 d000a04 3077a4
Feb 22 05:51:20 cioloco /kernel: STATUS 0 d000a04 3077a4
Feb 22 05:51:20 cioloco /kernel: STATUS 0 c000206 30601c
Feb 22 05:51:20 cioloco /kernel: STATUS 0 c000206 30601c
Feb 22 05:51:20 cioloco /kernel: STATUS 0 c000a04 3067a4
Feb 22 05:51:20 cioloco /kernel: STATUS 0 c000a04 3067a4
Feb 22 05:51:20 cioloco /kernel: STATUS 0 d000206 30701c
Feb 22 05:51:20 cioloco /kernel: STATUS 0 d000206 30701c
Feb 22 05:51:20 cioloco /kernel: STATUS 0 d000a04 3077a4
Feb 22 05:51:20 cioloco /kernel: STATUS 0 d000a04 3077a4
Feb 22 05:51:20 cioloco /kernel: STATUS 0 c000206 30601c
Feb 22 05:51:20 cioloco /kernel: STATUS 0 c000206 30601c
^^^^^^^ BKTR_INT_STAT
BKTR_INT_STAT is the second value in the output as you can see
bit 15 is never set which means that the Bt848 is not having
problems accessing the host memory.
>From The Desk Of Randall Hopper :
> Amancio Hasty:
> |Has the driver been always this unstable with you or is it just this
> |version?
>
> I got some freezes with 0.1, but they were pretty sporatic. With 0.2, I
> can get regular freezes when 1) doing CAP_CONTINOUS and 2) DMAing straight
> to the video card. Disk I/O brings the lock-ups on sooner. But with 0.2,
> if I flip into CAP_SINGLE, the regular freezes go away.
>
> Randall
>
>
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199702222206.OAA09711>