On Thu, Jul 18, 2013 at 9:26 AM, s m wrote:
> i have two question: does journaling cause to happen these errors?
Perhaps indirectly as increased load on a flaky disk/driver can cause
these. Mostly likely you have a failing drive though.
> and if i
> set hw.ata.ata_dma to 0, is it resolve the
t LBA=635411
ad3: WARNING - READ_DMA requeued due to channel reset LBA=635411
ata1: FAILURE - already active DMA on this device
ata1: setting up DMA failed
ad3: WARNING - WRITE_DMA requeued due to channel reset LBA=635411
ata1: FAILURE - already active DMA on this device
and these errors are
hello all,
i have FreeBSD8.2 on my system. occasionally, i see some strange errors in
startup and freebsd can not boot correctly. when i reset my system
everything is ok and freebsd boot successfully. these are errors which
appear in statrtup:
ata1: setting up DMA failed
ad3: WARNING - READ_DMA
ron kernel: bwn0 on siba_bwn0
Dec 21 13:06:12 apeiron kernel: bwn0: WLAN (chipid 0x4312 rev 15) PHY
(analog 6 type 5 rev 1) RADIO (manuf 0x17f ver 0x2062 rev 2)
Dec 21 13:06:12 apeiron kernel: bwn0: DMA (64 bits)
Dec 21 13:06:12 apeiron kernel: bwn0: Using 1 MSI messages
Dec 21 13:06:12 apeiron ker
[...]
>First of all: The disk is *not* dying. "SMART" won't reveal anything.
>The behaviour is perfectly normal for IBM-DJNA-3* type disks.
>
>When those disks are used in continuous operation (24/7), they
>will go into automatic maintenance mode after 6 days. This is
>kind of a short self-test
This is a reply to a very old thread.
I decided to reply because
1. nobody has mentioned the real cause of the problem yet
(some answers were misleading or even outright wrong),
2. I've experienced the same problem in the past few weeks,
3. my findings might be useful for other people wh
Daniel Eriksson wrote:
> Mark Stapper wrote:
>
>
>> So I see. Could this be why I haven't had any read errors anymore?
>> (After the zpool scrub that is)
>>
>
> Possibly, but in that case the SMART selftest should pass also. Have you
> tried a selftest after you did the scrub?
>
> /Daniel E
Mark Stapper wrote:
> So I see. Could this be why I haven't had any read errors anymore?
> (After the zpool scrub that is)
Possibly, but in that case the SMART selftest should pass also. Have you
tried a selftest after you did the scrub?
/Daniel Eriksson
_
Daniel Eriksson wrote:
> Mark Stapper wrote:
>
>
>> Yeah, i did the long SMART selftest three times now, each of which it
>> failed on the same LBA address.
>>
>
> I assume 'smartctl -a /dev/adX' reports that the read test failed at LBA
> XXX something?
>
Indeed it does. Always with the
Mark Stapper wrote:
> Yeah, i did the long SMART selftest three times now, each of which it
> failed on the same LBA address.
I assume 'smartctl -a /dev/adX' reports that the read test failed at LBA
XXX something?
> Why would I want to clear my driver before I run these tests?
In this case it's
Arthur Chance wrote:
Mark Stapper wrote:
[snip]
I ordered a "spare" drive so I'll wait until it arrives, replace the
faulty drive with this one by dd-ing data from one to the other (I have
only 4 SATA ports so I can't do "zpool replace").
zpool replace has two forms
zpool replace pool old
Mark Stapper wrote:
[snip]
I ordered a "spare" drive so I'll wait until it arrives, replace the
faulty drive with this one by dd-ing data from one to the other (I have
only 4 SATA ports so I can't do "zpool replace").
zpool replace has two forms
zpool replace pool old-device new-device
t; starts to generate more ATA errors.
>
Yeah, i did the long SMART selftest three times now, each of which it
failed on the same LBA address.
Did the scrub as well, took two hours, and no DMA errors were reported.
Why would I want to clear my driver before I run these tests?
I ordered a &qu
Mark Stapper wrote:
> People are REALLY pushing spinrite lately... I did get it though, just
to try it.
SpinRite is OK but it hasn't been updated in ages. It does not work on
large drives. 250GB works, 1TB does not. Haven't tried it on 500GB
drives.
If I were you I would 'zpool offline ...' the
>
>
>
>
> Since it's all throwing errors at the same LBA, I'd run a SMART
> diagnostics on the drive (i think it's port sysutils/smartmontools)
> and see if it's showing errors too. Looks like a failing/failed drive
> and I would recommend replacing it. I doubt (but you can try)
> spinrite will
On 8/31/09, Mark Stapper wrote:
> Good day to you,
>
> I'm having a bit of trouble with one of the disks in my zfs raidz1 pool.
> It's giving me dma read error, and zpool is reporting READ failures.
> However, data integrity is OK :-)
> Unfortunately I was in the mid
Good day to you,
I'm having a bit of trouble with one of the disks in my zfs raidz1 pool.
It's giving me dma read error, and zpool is reporting READ failures.
However, data integrity is OK :-)
Unfortunately I was in the middle of rearranging my backup media, so I'm
backup up e
hi, can anyone tell me what this message is related to?
WRITE_DMA UDMA ICRC error (retrying request) LBA=62939519
drive/hardware failing?
i am seeing a lot of it lately on a particular disk where i have tried a few
different installs and do not always
get this problem. i have seen it disappear af
On Thu, Apr 2, 2009 at 7:24 PM, Sergio de Almeida Lenzi <
lenzi.ser...@gmail.com> wrote:
> Em
>
>
>
> I've played another DVD which, I'm 100% sure, had copy protection in the
> same drive without any errors, but that was before upgrading my machine from
> 7.0-RELEASE to RELENG_7 on Feb 19, 2009.
ally when you are trying to play a protect dvd with some
> kind of protection...
>
> You are right, turn the dma to 0 (off) and play again
> or
> turn the dma to off, put the dvd in the drive,
> use the program K9copy (in the ports) to extract the DVD data .
> put a
ng happens except a non-stop hard drive activity. I suspected something
and checked /var/log/messages.
The following two lines are being constantly, non-stop added to
/var/log/messages:
Apr 1 17:04:30 rsx4 kernel: ata3: FAILURE - non aligned DMA transfer
attempted
Apr 1 17:04:30 rsx4 kernel: acd
except a non-stop hard drive activity. I suspected something
and checked /var/log/messages.
The following two lines are being constantly, non-stop added to
/var/log/messages:
Apr 1 17:04:30 rsx4 kernel: ata3: FAILURE - non aligned DMA transfer
attempted
Apr 1 17:04:30 rsx4 kernel: acd0: setting up DMA
ry
> >
> > This produced tons of error messages via syslog as
> >
> > Jul 11 13:45:30 rebelion kernel: ata0: FAILURE - non aligned DMA transfer
> > attempted
> > Jul 11 13:45:30 rebelion kernel: acd0: setting up DMA failed
> >
> > and the only wa
0: FAILURE - non aligned DMA transfer
> attempted
> Jul 11 13:45:30 rebelion kernel: acd0: setting up DMA failed
>
> and the only way to get the system back to a usable state was rebooting
> it;
>
> this is with FreeBSD-7.0R; what I have done wrong?
I have the same problem on a
Hello,
I wanted to add a file to an already written DVD+RW (written a day
before on the same system) with
# growisofs -M /dev/cd0 -r -T -J -joliet-long -v directory
This produced tons of error messages via syslog as
Jul 11 13:45:30 rebelion kernel: ata0: FAILURE - non aligned DMA transfer
Suddenly today all my attempts to burn DVDs with k3b result in a
continuous stream of the following error messages.
May 25 18:04:40 kestrel kernel: ata1: FAILURE - non aligned DMA transfer
attempted
May 25 18:04:40 kestrel kernel: acd0: setting up DMA failed
Quiting k3b doesn't stop the
Hello,
After having problems with DMA errors on my old PATA 200GB disks
because of a faulty harddisk, I switched to SATA 500GB disks. I used
fdisk to create slices and newfs them, then copied everything using
dump & restore to my new harddisks.
Now I have problems running into the
Hi,
I'm a happy FreeBSD user and I have it installed on my laptop (Toshiba
Tecra A4). However, I noticed recently that my iwi driver goes up and
down frequently then suddenly it stops working. When I check dmesg it says:
iwi0: could not allocate firmware DMA memory
Earlier on 6.1-RELEASE,
> Add the following to your kernel config:
> makeoptions DEBUG=-g
> options DDB, KDB, GDB
> options INVARIANTS
> options INVARIANT_SUPPORT
> options WITNESS_KDB
> options WITNESS_SKIPSPIN
> # Add this if you're using a firewire console
> options
>
> >> Did you use a 80- or 40-ATA cable?
> >> If you've configured your drives to do UATA-66 or faster then
> >> FreeBSD (or any other OS for that matter) will crash if
> you connect a
> >> second drive...
This is new one to me! I guess my 3 x UATA-100 are super drives of some sort
not t
Anish Mistry wrote:
On Thursday 13 April 2006 07:47, Wil Hatfield wrote:
I had a similar situation under 6.0. My secondary drive would
throw DMA read
errors at bootup, adding several minutes to the boot process, so
I ran it in
PIO mode. The upgrade to 6.1 solved it, both drives work fine as
On Thu, 13 Apr 2006 21:57:58 -, Wil Hatfield <[EMAIL PROTECTED]>
wrote:
Did you use a 80- or 40-ATA cable?
If you've configured your drives to do UATA-66 or faster then
FreeBSD (or
any other OS for that matter) will crash if you connect a second
drive...
It's an 80 wire. I have two dr
On Thursday 13 April 2006 18:01, Wil Hatfield wrote:
> > Do you have a backtrace?
>
> No. To be honest I have worked a little with the debugging but that
> was a long time ago. We ran 4.10 for eons and never needed to debug
> a thing. I got spoiled I guess. So now that I need to add debugging
> and
> Do you have a backtrace?
No. To be honest I have worked a little with the debugging but that was a
long time ago. We ran 4.10 for eons and never needed to debug a thing. I got
spoiled I guess. So now that I need to add debugging and backtrace to my
arsenal of knowledge could someone point me in
> Did you use a 80- or 40-ATA cable?
> If you've configured your drives to do UATA-66 or faster then
> FreeBSD (or
> any other OS for that matter) will crash if you connect a second drive...
It's an 80 wire. I have two drives on nearly all of my machines and never
had an issue with crashing until
On Thu, 13 Apr 2006 15:53:57 -, Anish Mistry <[EMAIL PROTECTED]> wrote:
On Thursday 13 April 2006 07:47, Wil Hatfield wrote:
> I had a similar situation under 6.0. My secondary drive would
> throw DMA read
> errors at bootup, adding several minutes to the boot process, s
On Thursday 13 April 2006 07:47, Wil Hatfield wrote:
> > I had a similar situation under 6.0. My secondary drive would
> > throw DMA read
> > errors at bootup, adding several minutes to the boot process, so
> > I ran it in
> > PIO mode. The upgrade to 6.1 solve
> I had a similar situation under 6.0. My secondary drive would
> throw DMA read
> errors at bootup, adding several minutes to the boot process, so
> I ran it in
> PIO mode. The upgrade to 6.1 solved it, both drives work fine as DMA now.
Looks like the DMA errors are back in 6.1-RC
On Thursday 13 April 2006 01:58, Perttu Laine wrote:
> I have problem with ATA drive having DMA TIMEOUTs.
> It might work day or two fine with DMA mode on but then system halts on
> those dma timeout problems.
>
> hardware is:
> [EMAIL PROTECTED]:5:0: class=0x018085 ca
I have problem with ATA drive having DMA TIMEOUTs.
It might work day or two fine with DMA mode on but then system halts on
those dma timeout problems.
hardware is:
[EMAIL PROTECTED]:5:0: class=0x018085 card=0x4d68105a chip=0x4d69105a
rev=0x02 hdr=0x00
vendor = 'Promise Technolog
I had a drive dying and it showed up just like this - it turned out to
be the daily scripts that scan for file changes, etc, and my backup
script were tickling a back sector of the disk. Have you run the
smartctl -t long /dev/ad0 command to have it perform a full self test?
You normally have
On Sun, 19 Feb 2006, Mike Tancsa wrote:
> On Sun, 19 Feb 2006 22:21:04 +, in sentex.lists.freebsd.questions
> you wrote:
>
>> On Thu, 16 Feb 2006, Mike Tancsa wrote:
>>
For the last 4-days, our (otherwise OK) 5.4-RELEASE machine has been
reporting:
Feb 12 12:08:05 : ad0: TI
On Sun, 19 Feb 2006 22:21:04 +, in sentex.lists.freebsd.questions
you wrote:
>On Thu, 16 Feb 2006, Mike Tancsa wrote:
>
>>> For the last 4-days, our (otherwise OK) 5.4-RELEASE machine has been
>>> reporting:
>>>
>>> Feb 12 12:08:05 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left)
>>> LBA=
On Thu, 16 Feb 2006, Mike Tancsa wrote:
>> For the last 4-days, our (otherwise OK) 5.4-RELEASE machine has been
>> reporting:
>>
>> Feb 12 12:08:05 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left)
>> LBA=2701279
>> Feb 13 00:08:51 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left)
>> LBA=2
Fabian Keil wrote:
"V.I.Victor" <[EMAIL PROTECTED]> wrote:
For the last 4-days, our (otherwise OK) 5.4-RELEASE machine has been
reporting:
Feb 12 12:08:05 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=2701279
Feb 13 00:08:51 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=2
"V.I.Victor" <[EMAIL PROTECTED]> wrote:
> For the last 4-days, our (otherwise OK) 5.4-RELEASE machine has been
> reporting:
>
> Feb 12 12:08:05 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left)
> LBA=2701279
> Feb 13 00:08:51 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left)
> LBA=2701279
On Thu, 16 Feb 2006 20:10:31 +, in sentex.lists.freebsd.questions
you wrote:
>For the last 4-days, our (otherwise OK) 5.4-RELEASE machine has been
>reporting:
>
>Feb 12 12:08:05 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left)
>LBA=2701279
>Feb 13 00:08:51 : ad0: TIMEOUT - WRITE_DMA retry
For the last 4-days, our (otherwise OK) 5.4-RELEASE machine has been
reporting:
Feb 12 12:08:05 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=2701279
Feb 13 00:08:51 : ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=2701279
Feb 13 12:09:38 : ad0: TIMEOUT - WRITE_DMA retrying (2 r
File a bug report for mplayer.
Ted
>-Original Message-
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>Sent: Tuesday, January 03, 2006 11:01 PM
>To: Ted Mittelstaedt
>Cc: freebsd-questions@freebsd.org
>Subject: Re: 6.0-R && DMA with Intel ICH6 UDMA100/SATA
El día Tuesday, January 03, 2006 a las 09:05:23PM -0800, Ted Mittelstaedt
escribió:
>
> If you play a movie file from the hard disk does the same thing happen?
Interestingly it only happens with Mplayer but not with ogle; before
yesterday I could not use ogle because the one from the ports coll
10:37 PM
>To: freebsd-questions@freebsd.org
>Subject: 6.0-R && DMA with Intel ICH6 UDMA100/SATA150 controller
>
>
>
>Hi,
>
>I've this configuration for the DVD device in my notebook:
>
>$ fgrep 'Jan 3' messages | egrep 'ata|ac
07:05:23 rebelion kernel: ata3: on atapci1
Jan 3 07:05:23 rebelion kernel: ata4: on atapci1
Jan 3 07:05:23 rebelion kernel: ata5: on atapci1
Jan 3 07:05:23 rebelion kernel: acd0: DVDR at
ata0-master UDMA33
Jan 3 07:05:23 rebelion kernel: ad4: 76319MB at
ata2-master SATA150
and DMA is activa
>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED] Behalf Of Mike Jeays
>Sent: Saturday, November 05, 2005 4:18 PM
>To: Ted Mittelstaedt
>Cc: freebsd-questions@freebsd.org
>Subject: RE: DMA errors
>
>
>On Mon, 2005-10-31 at 08:00, Mike J
> > >Cc: freebsd-questions@freebsd.org
> > >Subject: RE: DMA errors
> > >
> > >
> > >On Sat, 2005-10-29 at 19:48, Ted Mittelstaedt wrote:
> > >> Try a different disk drive.
> > >>
> > >> What motherboard is in use here?
>
solution was proposed.
Today I came across http://www.
czaplinski.net/FreeBSD/hpi386.html in which it was suggested that
EVO
510
CPU: 2.8 GHz P4; 1024MB RAM; i810 Intel integrated NIC (recognized
as EEPro100); i845 Intel integrated video...FreeBSD 5.1 loads, but only
after DMA is disabled in
On Mon, 2005-10-31 at 02:11, Ted Mittelstaedt wrote:
> >-Original Message-
> >From: Mike Jeays [mailto:[EMAIL PROTECTED]
> >Sent: Saturday, October 29, 2005 8:04 PM
> >To: Ted Mittelstaedt
> >Cc: freebsd-questions@freebsd.org
> >Subject: RE: DMA errors
>-Original Message-
>From: Mike Jeays [mailto:[EMAIL PROTECTED]
>Sent: Saturday, October 29, 2005 8:04 PM
>To: Ted Mittelstaedt
>Cc: freebsd-questions@freebsd.org
>Subject: RE: DMA errors
>
>
>On Sat, 2005-10-29 at 19:48, Ted Mittelstaedt wrote:
>> Try a
y, October 29, 2005 4:28 PM
> >To: freebsd-questions@freebsd.org
> >Subject: DMA errors
> >
> >
> >I have a 40GB Maxtor D740X-6L disk, and have been unable to install 5.4
> >or 6.0 on it. I get errors:
> >
> >ad0: FAILURE WRITE_DMA STATUS=51 erro
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Mike Jeays
> Sent: Saturday, October 29, 2005 4:28 PM
> To: freebsd-questions@freebsd.org
> Subject: DMA errors
>
>
> I have a 40GB Maxtor D740X-6L disk, and have been
Try a different disk drive.
What motherboard is in use here?
Ted
>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED] Behalf Of Mike Jeays
>Sent: Saturday, October 29, 2005 4:28 PM
>To: freebsd-questions@freebsd.org
>Subject: DMA errors
>
&g
I have a 40GB Maxtor D740X-6L disk, and have been unable to install 5.4
or 6.0 on it. I get errors:
ad0: FAILURE WRITE_DMA STATUS=51 error=84 (IRC,
ABORTED) LBA=..
as soon as I try to commmit the changes in sysinstall.
I have checked that the IDE cable is the 80-wire type, and cleaned up
the c
the ouput that Bonnie gave me lead me to believe that the drive
might not be using DMA at all, so I checked this using atacontrol:
[snip]
ATA channel 1:
Master: ad2 ATA/ATAPI revision 7
Slave: acd0 ATA/ATAPI revision 0
Master = UDMA66
Slave = UDMA33
[snip]
So much for this drive, but I
Hi,
I'm running 5-Stable as of Sept. 24th.
My sound card is an ESS Solo-1 (integrated
in the motherboard). I load the modules
sound.ko and snd_solo.ko.
When using realplayer or mplayer, sound
is very much distorted; also, the console
gets an endless stream of these kind of
messages:
request) LBA=0
ad0: FAILURE - READ_DMA status=51 error=84
LBA=0
I originally tried the install w/ 5.4, disabled ACPI, disabled DMA in my
bios -- no luck. I am now trying the latest 6.0-BETA, still giving me the
errors. Unsure where to go from here or what info to display.
Thanks,
mrkris
Hello,
I was following procedure2 of the gmirror howto located at:
http://people.freebsd.org/~rse/mirror/
and had got to the part where i was copying the data from the first to the
second disk. I did:
dump -L -0 -f- /usr | (cd /mnt/usr; restore -r -v -f-)
which went for a while then hung. Check
r.conf:
>hw.ata.ata_dma="0"
>
> This will force the harddisk to operate in slow
> PIO4 mode, but in my case the DMA trouble disappeared.
>
> Rob.
>
>
>
>
> __
> Celebrate Yahoo!'s 10th Birthday!
> Yahoo! Netro
a="0"
This will force the harddisk to operate in slow
PIO4 mode, but in my case the DMA trouble disappeared.
Rob.
__
Celebrate Yahoo!'s 10th Birthday!
Yahoo! Netrospective: 10
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:owner-freebsd-
> [EMAIL PROTECTED] On Behalf Of Luciano Musacchio
> Sent: Sunday, March 06, 2005 3:05
> To: freebsd-questions@freebsd.org
> Subject: dma/sysctl
>
> Hi,
> I've a fbsd machine that
Hi,
I've a fbsd machine that hangs once in a while, I've this
en /var/log/messages:
...
Mar 5 14:44:58 chiba kernel: ad2: WARNING - WRITE_DMA UDMA ICRC error
(retrying request) LBA=2949471
...
So, this means my hd is about to crash?
How can I tell the kernel to reboot on such cases? (via sysctl
I am running FreeBSD 5.3. I have it presently loaded on an older Compaq
5140 computer. For some unknown reason, I am having a problem getting
DMA turned on for my CDROM drive. I am also receiving an error message
regarding the 'slave'. I had FreeBSD 5.2.1 loaded previously and never
re
looked at the CPU load - and it was around 65%. I'm a freebsd novice -
could somebody please tell me how to tune DMA parameters?
Best wishes,
Andrew P.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questio
; 5.3. In addition, would it be possible for me to build a new kernel with
> this support already built into it?
The default *is* to use DMA.
Kris
pgplJ5Xa1rTYf.pgp
Description: PGP signature
In FreeBSD version 5.2.1, I used the following in the "loader.conf" file:
hw.ata.ata_dma=1
hw.ata.atapi_dma=0
I was wondering if that is still applicable in the latest version; i.e.,
5.3. In addition, would it be possible for me to build a new kernel with
this support already built into it?
Than
I have 2 discs on my Sata-controller card.
It's fully supported by FBSD but when it's handling alot of data, the
whole machine hangs.
I checked with atacontrol and my discs were SATA150, but the documentation says:
Currently supported modes are: BIOSDMA, PIO0 (alias BIOSPIO), PIO1,
PIO2, PIO3, PIO
On Mon, 5 Jul 2004 20:03:37 -0700 (PDT)
peter lageotakes <[EMAIL PROTECTED]> hit the keyboard and punched:
> --- Warren Block <[EMAIL PROTECTED]> wrote:
> >
> > -CURRENT (5.x) does have support for SATA, and may
> > (probably does)
> > work with the 8237. (I haven't tried it on this
> > motherb
> [...]
> > ad0: 156334MB [317632/16/63] at
> ata0-master UDMA133
> > ad4: DMA limited to UDMA33, non-ATA66 cable or
> device
> > ad4: 152627MB [310101/16/63] at
> ata2-master UDMA33
> >
> > How come FreeBSD kernel thinks my S-ATA disk is
> only cap
On Mon, 5 Jul 2004 18:35:52 -0600 (MDT)
Warren Block <[EMAIL PROTECTED]> hit the keyboard and punched:
> FreeBSD 4.x doesn't have specific support for the VIA 8237, and so
> doesn't properly realize that it should be able to do the faster DMA
> modes.
>
> My MS
On Tue, 6 Jul 2004, Rickard [ISO-8859-1] Borgmäster wrote:
atapci1: port 0xfc00-0xfc0f at device 15.1 on
pci0
ata0: at 0x1f0 irq 14 on atapci1
ata1: at 0x170 irq 15 on atapci1
[...]
ad0: 156334MB [317632/16/63] at ata0-master UDMA133
ad4: DMA limited to UDMA33, non-ATA66 cable or device
ad4
confusing message:
atapci1: port 0xfc00-0xfc0f at device 15.1 on
pci0
ata0: at 0x1f0 irq 14 on atapci1
ata1: at 0x170 irq 15 on atapci1
[...]
ad0: 156334MB [317632/16/63] at ata0-master UDMA133
ad4: DMA limited to UDMA33, non-ATA66 cable or device
ad4: 152627MB [310101/16/63] at ata2-master UDMA33
en I try to change to udma100
> > ---
> > atacontrol mode 0 udma100 biosdma
> > Master = UDMA33
> > Slave = BIOSPIO
> > -
> > console output after i use atacontrol
> > -
Me wrote:
---
When I try to change to udma100
---
atacontrol mode 0 udma100 biosdma
Master = UDMA33
Slave = BIOSPIO
-
console output after i use atacontrol
-
ad0: DMA
Hello everyone,
I have a problem with my Averatec Laptop, Freebsd
5.2.1 does not recognize udma100 on my hdd.
I've check the bios settings and have set varios
options.
auto, dma, 32bit mode, and PIO5 (on/off) but i still
cant get the drive to work at udma100.
the cdrom is in a diffrent IDE ch
Separator **
On Tuesday, January 27, 2004 12:59:23 AM [EMAIL PROTECTED] wrote:
Date: Fri, 16 Jan 2004 09:34:22 +0100 (CET)
From: "Roman Kennke" <[EMAIL PROTECTED]>
Subject: DMA problem with DVD drive
To: <[EMAIL PROTECTED]>
Message-ID:
<[EMAIL PROTECTED]&
Hi there,
I am not able to enable DMA for my DVD drive. When I issue 'atacontrol
mode 1 UDMA100 XXX' and access the drive, first the drive access hangs,
and after a view seconds the machine locks up completely. This also hold
true for all other DMA modes.
I am running FreeBSD 5.2 on
>> I am not able to enable DMA for my DVD drive.
> I have a similar drive on my Toshiba Satellite A30-514 and to set UDMA
> mode on boot I have put the following line in /boot/loader.conf:
>
> hw.ata.atapi_dma="1"
>
> Here's the relevant part of dmesg output
On Fri, Jan 16, 2004 at 09:33:57AM +0100, Roman Kennke wrote:
>
> Hi there,
>
> I am not able to enable DMA for my DVD drive. When I issue 'atacontrol
> mode 1 UDMA100 XXX' and access the drive, first the drive access hangs,
> and after a view seconds the machine lo
Hi there,
I am not able to enable DMA for my DVD drive. When I issue 'atacontrol
mode 1 UDMA100 XXX' and access the drive, first the drive access hangs,
and after a view seconds the machine locks up completely. This also hold
true for all other DMA modes.
I am running FreeBSD 5.2 on
Bert Lagaisse <[EMAIL PROTECTED]> writes:
> I did some stupid newbie things:
>
> I have 2 cdroms, a plextor 8/4/32A and a 50x aopen cdrom.
>
> I added the line hw.ata.atapi_dma="1" to loader.conf
> The plextor now uses WDMA2
> The aopen cdrom still uses
Hi,
I did some stupid newbie things:
I have 2 cdroms, a plextor 8/4/32A and a 50x aopen cdrom.
I added the line hw.ata.atapi_dma="1" to loader.conf
The plextor now uses WDMA2
The aopen cdrom still uses PIO4 (dma worked under wintendo 2000)
After I tried to enable DMA (using atacont
Please CC me on replies.
I arrived home this afternoon to find a box had rebooted and is
having trouble with its IDE drive. A screen shot is at
http://www.freebsddiary.org/tmp/ata-failure.jpg
My current plan:
1 - add a new IDE drive
2 - install FreeBSD on that
3 - run "fsck -y" each on each vo
cable because of length problems (speaking from
experience...).
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Ugo
> Bellavance
> Sent: Thursday, July 24, 2003 7:58 PM
> To: [EMAIL PROTECTED]
> Subject: DMA limited to UDMA3
There might be another possibility... I ran into a problem once where
Solaris would only allow me to use ATA33 on a Sis controller because
the controller driver was unstable at ATA66 in solaris. Perhaps its
down clocking so to speak.
I also had a problem with a promise pci ide controller card
#x27;t know how to test it (like hdparm in linux).
--Other data:
output from dmesg
atapci1: port
0x1010-0x101f,0x1024-0x1027,0x1028-0x102f,0x1030-0x1033,0x1038-0x103f
mem 0xf000-0xf000 irq 2 at device 8.0 on pci0
ad4: DMA limited to UDMA33, non-ATA66 cable or device
ad6: DMA limited to
mesg
>
> atapci1: port
> 0x1010-0x101f,0x1024-0x1027,0x1028-0x102f,0x1030-0x1033,0x1038-0x103f
> mem 0xf000-0xf000 irq 2 at device 8.0 on pci0
> ad4: DMA limited to UDMA33, non-ATA66 cable or device
> ad6: DMA limited to UDMA33, non-ATA66 cable or device
> ar0: 1907348M
and drives support
> udma100. I don't know if it is a bogus error, because
> I don't know how to test it (like hdparm in linux).
>
> --Other data:
>
> output from dmesg
>
> atapci1: port
> 0x1010-0x101f,0x1024-0x1027,0x1028-0x102f,0x1030-0x1033,0x1038-0x103f
&
-0x101f,0x1024-0x1027,0x1028-0x102f,0x1030-0x1033,0x1038-0x103f
> mem 0xf000-0xf000 irq 2 at device 8.0 on pci0
> ad4: DMA limited to UDMA33, non-ATA66 cable or device
> ad6: DMA limited to UDMA33, non-ATA66 cable or device
> ar0: 1907348MB [65535/255/63]
> status: READY subdisk
027,0x1028-0x102f,0x1030-0x1033,0x1038-0x103f
mem 0xf000-0xf000 irq 2 at device 8.0 on pci0
ad4: DMA limited to UDMA33, non-ATA66 cable or device
ad6: DMA limited to UDMA33, non-ATA66 cable or device
ar0: 1907348MB [65535/255/63]
status: READY subdisks:
0 READY ad4: 76319MB
[155061/16/6
fxp0: SCB timeout: 0xff 0xff 0xff 0x
fxp0: SCB timeout: 0xff 0xff 0xff 0x
fxp0: SCB timeout: 0xff 0xff 0xff 0x
fxp0: DMA timeout
==
I added the following line to /etc/rc.conf:
ifconfig_fxp0="DHCP"
Any help would be appreciated. I would like to g
This is less of a question and more of a solution to a problem I was having.
There were (apparently) some ATA DMA changes recently in -current that never
trickled down to 4.7-STABLE, which is what I had been running before trying
5.0. (My 4-STABLE install was working perfectly.) These DMA
n the drives with DMA turned on, my whole system
> freezes up but the tests run fine on the second drive. In addition,
> hdparm -i doesn't list UDMA-4 as one of the DMA modes for the first
> drive. Now that I have given you the scenario, I would like to ask
> you how can I disable
1 - 100 of 109 matches
Mail list logo
