On 15Jul, 2009, at 11:33 , Marat N.Afanasyev wrote:
Søren Schmidt wrote:
Over the past months I've gotten huge amounts of requests for ATA
related things, so I've whipped up what I use here for FreeBSD 7.2-
Release.
This is a total replacement of the ATA driver, modulerized as in -
current
On 27Jun, 2009, at 14:29 , Bruce Cran wrote:
On Fri, 26 Jun 2009 22:11:08 +0200
Søren Schmidt s...@deepcore.dk wrote:
This is a total replacement of the ATA driver, modulerized as in -
current, but based on my WIP not from what might have happend to -
current since I gave up maintainership
Over the past months I've gotten huge amounts of requests for ATA
related things, so I've whipped up what I use here for FreeBSD 7.2-
Release.
This is a total replacement of the ATA driver, modulerized as in -
current, but based on my WIP not from what might have happend to -
current since
On 10Dec, 2008, at 10:11 , Victor Balada Diaz wrote:
Thanks for explaining me what the flags do. I'm not skilled enough
to create
the DMA quirks but if you could give me some patches i'll test them.
Also
if you have any other idea on what could i test or how can i debug
this
it would be
On 7Nov, 2008, at 20:12 , Peter Wemm wrote:
On Thu, Nov 6, 2008 at 11:17 PM, Jeremy Chadwick
[EMAIL PROTECTED] wrote:
[..]
As stated, FreeBSD's ATA command timeout is hard-set to 5 seconds,
and
is not adjustable without editing the ATA code yourself and
increasing
the value. The FreeNAS
I'll look into it
-Søren
--
On 31/10/2008, at 00.00, Michael Butler [EMAIL PROTECTED]
wrote:
Jeremy Chadwick wrote:
On Thu, Oct 30, 2008 at 01:47:48PM -0700, Xin LI wrote:
Personally I don't really think ICH7M is capable to do SATA-300.
Intel
datasheet 307013, page 191 says:
On Thu, Oct 23, 2008 at 9:03 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote:
On Thu, Oct 23, 2008 at 02:01:55PM -0400, David Boyd wrote:
I am attempting to install 7.1-BETA2 (from CD) onto a PC with a Promise
SX4060 RAID controller and two Seagate 120GB ATA disk drives.
The boot from CD
On 10Oct, 2008, at 13:58 , Jeremy Chadwick wrote:
On Sun, Oct 05, 2008 at 10:12:11PM -0700, Jeremy Chadwick wrote:
On Mon, Oct 06, 2008 at 09:03:20AM +0400, Andrey V. Elsukov wrote:
Jeremy Chadwick wrote:
Also, does your patch include any fixes (intentional or
inadvertent) for
Intel
On 5Oct, 2008, at 13:04 , Marius Strobl wrote:
On Sat, Oct 04, 2008 at 07:38:09PM +0400, Andrey V. Elsukov wrote:
Hi, All.
I prepared patch to make MFC of ata(4) driver into RELENG_7
before 7.1-RELEASE. Depending on results of the testing patch
will be commited or not (if some regressions
Hi
I'll look into that providing I can find HW to work on, IIRC I have
one in the ATA collection but I have to verify when I get to the lab.
-Søren
On 1Jul, 2008, at 11:01 , Daniel Eriksson wrote:
I am having problems with silent data corruption on (some) drives
connected to an MCP55
Hi
OK, the only modern nVidia board I have is MCP51 based, however it
uses the same codepath as the MCP55.
Anyhow, there has been fixes fro these in -current, thats not in any
of the releng's yet.
Please try the attached patch, or even better try a -current kernel.
-Søren
ff
On 25Jan, 2008, at 15:05 , John Baldwin wrote:
On Wednesday 23 January 2008 03:52:39 pm Søren Schmidt wrote:
On 23Jan, 2008, at 21:09 , Xin LI wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yoshihiko Sarumaru wrote:
Hello,
I updated my Geode GX1 PC from RELENG_6_2 to RELENG_6_3
On 23Jan, 2008, at 21:09 , Xin LI wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yoshihiko Sarumaru wrote:
Hello,
I updated my Geode GX1 PC from RELENG_6_2 to RELENG_6_3 and found
root mount failed after reboot.
This problem was caused by a change to ata-pci.c to pick up wider old
ata
Ian Smith wrote:
On Sat, 3 Nov 2007, Henrik Brix Andersen wrote:
On Sun, Nov 04, 2007 at 02:59:36AM +1100, Ian Smith wrote:
any particular/new issues with RELENG_7 on the Soekris net4801?
Thought I should check before upgrading my T23 as a build platform ..
I haven't done this
Bruce M Simpson wrote:
Hi,
My laptop drive might be dying. It is a Samsung MP0804H which I have
used for around 28 months without issue.
Every now and then it will click and sound as though it is thermally
recalibrating itself.
I ran SMART diagnostics from smartmontools, and Samsung's own
Zahemszky Gábor wrote:
Hi!
I'd like to know, is it possible to use FreeBSD on on Intel DG9655SS
motherboard with PATA devices. It has 1 PATA and 2 SATA ports,
but the 6-stable kernel doesn't see any devices on PATA. It
doesn't see neither my disk, nor my DVD-writer. I tried with normal
mode,
SMART say on corrected errors etc (if the drive has that info).
-Søren
Please, advise. Thanks!
-mi
On Wednesday 01 March 2006 11:07, Mikhail Teterin wrote:
= On Wednesday 01 March 2006, Søren Schmidt wrote:
= = dd if=/dev/ad8 of=/dev/null bs=1m
=
= Well, as I said, there is no obvious
Mikhail Teterin wrote:
On Monday 26 March 2007 15:21, Søren Schmidt wrote:
= What HW was this again, there has been alot of updates/changes over the
= last year ?
It is now a quad core (dual CPU) Opteron-275 using IWill's DK8X motherboard.
http://www.google.com/search?q=iwill+dk8x
Juraj Lutter wrote:
On 2/27/07, Bruce M. Simpson [EMAIL PROTECTED] wrote:
Søren Schmidt wrote:
The problem is that your BIOS registers the resources used for AHCI
operation but apparently hasn't really enabled them.
Look for an option in the BIOS to turn on/off AHCI mode
Bruce M. Simpson wrote:
Hi,
I have experienced the same regression since 6.2 was branched on an
ASUS amd64 Vintage-PE1 box.
Juraj Lutter wrote:
Feb 26 21:45:25 river kernel: atapci0: AcerLabs M5229 UDMA133
controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at
device 31.0 on
Peter Ankerstål wrote:
Pietro Cerutti wrote:
On 1/14/07, Peter Ankerstål [EMAIL PROTECTED] wrote:
ad0: FAILURE - READ_DMA timed out LBA=1000941
This kind of errors usually denote a hardware problem, either at the
disk or at the controller level.
Check sysutils/smartmontools in the ports.
Luigi Rizzo wrote:
summary: there was some discussion on how to
fix the problem, in 6.x, with burncd -f /dev/acd0 -v blank getting
stuck with this message
blanking CD, please wait..
This used to work on 4.x.
6.x changes in two places:
* the ioctl handler, acd_get_progress() in
Jon Passki wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey all,
(I'm off list, please include me in any replies)
(Søren, please let me know if you do not want to be emailed in the
future directly! You seem to be the ATA RAID FreeBSD goto guy.
Apologies if you did not want to be
Lin Jui-Nan Eric wrote:
Hi,
On 10/19/06, Søren Schmidt [EMAIL PROTECTED] wrote:
Nothing else that that it should work. I dont own any HW that uses this
chip so I cannot test it out. The current support was done for the ARM
port IIRC so things might be different on other systems.
At any rate
Jeremy Chadwick wrote:
On Wed, Oct 18, 2006 at 10:46:21PM +0800, Lin Jui-Nan Eric wrote:
We have a Dell Powervault 745N and want to install FreeBSD 6.1-R.
But the installer complains that it can not find out any hard disk.
Since the dmesg contains ata2~5, I think the controller is
Joao Barros wrote:
Hi all,
I was contacted by Chris who had the same problem.
Since I didn't follow up on my problem he asked me if it was solved
and indeed it was solved by Søren and the fix has been committed to
CURRENT:
http://lists.freebsd.org/pipermail/cvs-all/2006-September/188353.html
I plan to bacport *all* of ATA, as there are so many bugfixes that a resync
is needed.
ATA from -current fits right into 6-stable so its a nobrainer it just need a
little more exposure...
-Søren
On 8/22/06, Ruslan Ermilov [EMAIL PROTECTED] wrote:
On Mon, Aug 21, 2006 at 03:23:37PM -0400,
Give me a few days and I'll get to it if I dont get any serious issues
before that...
-Søren
On 8/22/06, Ruslan Ermilov [EMAIL PROTECTED] wrote:
Hi Soren,
On Tue, Aug 22, 2006 at 10:56:19AM +0200, S?ren Schmidt wrote:
I plan to bacport *all* of ATA, as there are so many bugfixes that a
Mikhail Teterin wrote:
Hello!
We have an amd64 machine with an nVidia3 SATA controller on motherboard.
The drive just came from the manufacturer and the self-tests initiated
via smartctl show no problems:
atapci1: nVidia nForce3 Pro SATA150 controller port
On Tor, 2006-03-30 at 11:09 +0100, Adam Retter wrote:
Soren,
I am using FreeBSD 6-STABLE and have a problem with the atapicam driver,
I have been in contact with Thomas Quinot through the FreeBSD stable
mailing list (his name was on the code for atapicam), I have sent him
boot -v -h output
On Tor, 2006-03-30 at 12:07 +0100, Adam Retter wrote:
On Thu, 2006-03-30 at 12:42 +0200, Søren Schmidt wrote:
On Tor, 2006-03-30 at 11:09 +0100, Adam Retter wrote:
Soren,
I am using FreeBSD 6-STABLE and have a problem with the atapicam driver,
I have been in contact with Thomas
Mike Tancsa wrote:
At 11:38 PM 13/03/2006, Mike Tancsa wrote:
Hi,
I was trying out a recent RELENG_6 on a VIA mini ITX board with built
in CF reader. If a CF is present, the box panics at boot (tried with 2
separate boards and different CFs just in case it was hardware). This
is with a
Wilko Bulte wrote:
On Wed, Feb 08, 2006 at 10:44:05PM +0100, Sren Schmidt wrote..
Wilko Bulte wrote:
On Wed, Feb 08, 2006 at 10:02:08PM +0100, Sren Schmidt wrote..
Wilko Bulte wrote:
Hi Soren,
I just went to 6.1-PRE on my main machine, coming from 6.0-STABLE
of roughly end of december.
And
Wilko Bulte wrote:
On Thu, Feb 09, 2006 at 03:37:07PM +0100, Sren Schmidt wrote..
Wilko Bulte wrote:
On Wed, Feb 08, 2006 at 10:44:05PM +0100, Sren Schmidt wrote..
Wilko Bulte wrote:
On Wed, Feb 08, 2006 at 10:02:08PM +0100, Sren Schmidt wrote..
Wilko Bulte wrote:
Hi Soren,
I just went to
Wilko Bulte wrote:
On Thu, Feb 09, 2006 at 03:45:53PM +0100, Sren Schmidt wrote..
Wilko Bulte wrote:
On Thu, Feb 09, 2006 at 03:37:07PM +0100, Sren Schmidt wrote..
Wilko Bulte wrote:
On Wed, Feb 08, 2006 at 10:44:05PM +0100, Sren Schmidt wrote..
Wilko Bulte wrote:
On Wed, Feb 08, 2006 at
Wilko Bulte wrote:
Hi Soren,
I just went to 6.1-PRE on my main machine, coming from 6.0-STABLE
of roughly end of december.
And I hit some stuff that really worries me:
- the freshly built kernel keels over with (hand transcribed):
ata3: reiniting channel SATA connect ...
SATA connected
Wilko Bulte wrote:
On Wed, Feb 08, 2006 at 10:02:08PM +0100, Sren Schmidt wrote..
Wilko Bulte wrote:
Hi Soren,
I just went to 6.1-PRE on my main machine, coming from 6.0-STABLE
of roughly end of december.
And I hit some stuff that really worries me:
- the freshly built kernel keels over
Vulpes Velox wrote:
On Sun, 29 Jan 2006 16:46:52 +1030
Daniel O'Connor [EMAIL PROTECTED] wrote:
I am looking at getting a motherboard based on nForce 3 or 4, and I
am wondering if the RAID will be usable?
I don't mind if I have to use the BIOS to setup/rebuild the array,
but I don't want to
Michael Butler wrote:
1) the ata-raid driver currently leaks ata_composite and ata_request
structures into neverland in a mirrored configuration. This can be
observed using sysctl -a | grep ^ata_ and noting the increasing
in-use count as time goes on. Eventually, this causes the kernel to
run
Enrique Ayesta Perojo wrote:
El Jueves 10 Noviembre 2005 16:06, Michael Butler escribió:
David Taylor wrote:
| [snip]
|
| I'm still seeing (lots) of these messages (below) on 6.0-RELEASE.
| Should I just file a PR about it, and is there anything else that
| would be useful to track down
On 07/11/2005, at 18:10, Michael Butler wrote:
| I wrote:
| | cvsup'd and built: FreeBSD 6.0-STABLE #4: Fri Nov 4 18:07:30
EST 2005
|
| ~ [ .. ]
|
| | Nov 6 16:43:27 mail kernel: DOH! ata_alloc_request failed!
| | Nov 6 16:43:27 mail kernel: FAILURE - out of memory in
|
I've just committed a fix for this a few hours ago..
Søren Schmidt
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
is not completely broken at least :)
Get me the output from dmesg so I can see whats under the hood, might
help explain things.
Søren Schmidt
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
On 23/08/2005, at 19:19, Dmitry Morozovsky wrote:
Hi there Soeren,
using parallel ATA drive at our new TYAN motherboard I see
[EMAIL PROTECTED]:/usr/src# atacontrol mode 0
atacontrol: Invalid device 0
the same for other channel-related commands such as
[EMAIL PROTECTED]:/usr/src#
On 22/08/2005, at 22:24, Mike Tancsa wrote:
I updated one of our boxes from RELENG_5 to 6. Couple of things I
noticed was that the smartmontools and atacontrol seems to be
broken now. I updated smartmon to the latest in the ports, but same
problem.
The ioctl ABI to ATA has changed,
On 10/08/2005, at 17:44, Scot Hetzel wrote:
On 8/10/05, Karl Denninger [EMAIL PROTECTED] wrote:
On Wed, Aug 10, 2005 at 09:51:03AM -0400, Mike Tancsa wrote:
At 09:31 AM 10/08/2005, Karl Denninger wrote:
Also, I've yet to see a developer commit on the list that they
WILL fix it
if
such
On 10/08/2005, at 20:05, Scot Hetzel wrote:
Since I came in late in this, I need to know what kind of controller
we are talking about, and if the problem is still present in 6.0.
I plan to backport ATA from 6.0 to 5-stable when it has settled, so
6.0 is the one and only (pre)release to test
On 10/08/2005, at 20:29, J. T. Farmer wrote:
Scot Hetzel wrote:
On 8/10/05, Søren Schmidt [EMAIL PROTECTED] wrote:
Since I came in late in this, I need to know what kind of controller
we are talking about, and if the problem is still present in 6.0.
I plan to backport ATA from 6.0 to 5
On 10/08/2005, at 22:51, Karl Denninger wrote:
Since I came in late in this, I need to know what kind of controller
we are talking about, and if the problem is still present in 6.0.
I plan to backport ATA from 6.0 to 5-stable when it has settled, so
6.0 is the one and only (pre)release to test
On 11/08/2005, at 0:28, Randy Bush wrote:
As I said I need reports on 6.0, the ATA driver as is in 5.4 is not
supported by me unless you use the ATA mkIII patches..
you know, we just upgraded a system from 4.11 to 7.0 and see problems.
we have been chasing cables, and never considered that
On 24/07/2005, at 23:28, Mike Jakubik wrote:
I'm curious if the Promise Supertrak SX6000 is still not bootable
under FreeBSD 5.4 or 6. The man page never stated this before, and
it would be nice to know.
I don't think so, the problem is in our boot code, not in the sx6000.
That said, some
Nate Lawson wrote:
If you've been having memory modified after free panics on -current
and have a Thinkpad, the attached patch should fix things for you. A
quick check of RELENG_5 indicates that the bug is probably there also
but I haven't tested for it there.
The bug is triggered by
Nate Lawson wrote:
Søren Schmidt wrote:
Nate Lawson wrote:
If you've been having memory modified after free panics on -current
and have a Thinkpad, the attached patch should fix things for you. A
quick check of RELENG_5 indicates that the bug is probably there also
but I haven't tested
On 25/05/2005, at 4:17, alan bryan wrote:
--- Søren Schmidt [EMAIL PROTECTED] wrote:
Is there anything in -CURRENT that would help this
to
work better than 5-STABLE plus the ATA mkIII n
patches?
Yes, I've done quite a bit of changes that affects
this on -current.
However its done
On 24/05/2005, at 5:01, alan bryan wrote:
Here's a recap of all the things I've tried and
discovered in a bunch of testing today.
Tried mkIII m patches and that doesn't show atapici1
or atapici2 - they just show as GENERIC with drives as
UDMA33
Tried mkIII n patches and then atapici1 shows
+0200, Søren Schmidt wrote:
Depends on what BIOS you have on there, several exists for the SiI
chips, -current or mkIII would tell you which. Just null out the last
63 sectors on the disks and you should be fine since all possible
formats are in that range...
I know how to do this using dd from
On 21/05/2005, at 0:52, Peter Jeremy wrote:
On Fri, 2005-May-20 14:53:09 -0600, Elliot Finley wrote:
From: Peter Jeremy [EMAIL PROTECTED]
On Fri, 2005-May-20 08:25:58 -0600, Elliot Finley wrote:
I took the -L option off of my dump command in my daily dump
script. I've
gone two days
On 21/05/2005, at 1:10, Joe Rhett wrote:
On Thu, May 19, 2005 at 08:21:13AM +0200, Søren Schmidt wrote:
On 19/05/2005, at 2.20, Joe Rhett wrote:
Soren, I've just retested all of this with 5.4-REL and most of the
problems
listed here are solved. The only problems appear to be related
On 22/05/2005, at 2:36, Thomas Hurst wrote:
* Søren Schmidt ([EMAIL PROTECTED]) wrote:
No, my only advise is to use the ATA mkIII patches or better yet -
current..
In a similar vein, I'm seeing the same WRITE_DMA timeouts and system
lockups using ATA mkIII patches as I did using
On 19/05/2005, at 2.20, Joe Rhett wrote:
Soren, I've just retested all of this with 5.4-REL and most of the
problems
listed here are solved. The only problems appear to be related to
these
ghost arrays that appear when it finds a drive that was taken offline
earlier. For example, pull a
Elliot Finley wrote:
This has been happening since 5.3-R, I've been tuning different parameters
to no avail. I've taken the disks off of the onboard ICH5 controller and
put them a promise TX4 S150 controller, but still the same thing happens.
The system freezes, but isn't totally dead. It'll
Gheorghe Ardelean wrote:
Hi Soeren,
I have to thank you for the work you put in the ata driver.
Thanks!
After patching the 5.4 sources with the new ata mkIII
(http://people.freebsd.org/~sos/ATA)
I am able to use the RAID 1 with my Adaptec SATA 1210SA.
Good :) let me know if you run into problems
Andrew Heybey wrote:
I just tried RELENG_5 as of last week and the latest (April 13) ATA
mkIII patches from http://people.freebsd.org/~sos/ATA/ on my laptop.
Unfortunately, it breaks suspend-to-RAM (S3).
History:
I first tried RELENG_5 on the laptop (a Toshiba Tecra M2V) in January
and suspend
tofik suleymanov wrote:
Good day Soren,
i've applied ATA mkIII patch on freshly cvsuped 5.4-STABLE and
experienced
problems with onboard sata controller.Here is a fragment from dmesg output:
atapci1: nVidia nForce3 Pro SATA150 controller port
I've just uploaded the latest ATA mkIII patches for releng_5 (and
releng_5_4 for that matter).
Since this work is now in -current there will only be releng_5 patches
now and then if there is sufficient interest.
Anyhow, they are on http:/people.freebsd.org/~sos/ATA
Enjoy!
--
-Søren
Nate Lawson wrote:
If you've been having memory modified after free panics on -current
and have a Thinkpad, the attached patch should fix things for you. A
quick check of RELENG_5 indicates that the bug is probably there also
but I haven't tested for it there.
The bug is triggered by timeouts
Nate Lawson wrote:
Søren Schmidt wrote:
Nate Lawson wrote:
If you've been having memory modified after free panics on -current
and have a Thinkpad, the attached patch should fix things for you. A
quick check of RELENG_5 indicates that the bug is probably there also
but I haven't tested
Søren Schmidt wrote:
http://people.freebsd.org/~sos/ata-mk3k.diff-releng5.gz
http://people.freebsd.org/~sos/ata-mk3k.diff-current.gz
http://people.freebsd.org/~sos/ata-mk3k.tar.gz
New version available for testing:
http://people.freebsd.org/~sos/ata-mk3l.diff-releng5.gz
http://people.freebsd.org
Marcus Grando wrote:
My problem persist...
Any other patch? or idea?
Hmm, does it work without apic ? without ACPI ?
And your cabling is correct and spec conformant ?
The 686A' I have in the lab works just dandy...
--
-Søren
___
[EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
Marcus Grando wrote:
My problem persist...
Any other patch? or idea?
Hmm, does it work without apic ? without ACPI ?
And your cabling is correct and spec conformant ?
The 686A' I have in the lab works just dandy...
Just an observation, but my
Marcus Grando wrote:
Hi
Søren Schmidt wrote:
Hmm, does it work without apic ? without ACPI ?
And your cabling is correct and spec conformant ?
The 686A' I have in the lab works just dandy...
I test all combinations (with/without apic | with/without ACPI), and
problems persist.
OK
Marcus Grando wrote:
I test another disk (SAMSUNG SV8004H) in secondary and work with UDMA66.
OK, so the problem is not general of nature...
Have you tried this disk on another board ?
I have another computer with 4.11-STABLE / QUANTUM FIREBALLlct10 30 and
occurs same problem.
--
ad0s1g: UDMA
Maxim Konovalov wrote:
Hi,
On Thu, 17 Feb 2005, 10:32+0100, S?ren Schmidt wrote:
S?ren Schmidt wrote:
http: //people.freebsd.org/~sos/ata-mk3k.diff-releng5.gz
http: //people.freebsd.org/~sos/ata-mk3k.diff-current.gz
http: //people.freebsd.org/~sos/ata-mk3k.tar.gz
New version available for
Takahashi Yoshihiro wrote:
In article [EMAIL PROTECTED]
Søren Schmidt [EMAIL PROTECTED] writes:
2. A geometry translation for pc98 is NOT enough.
Currently, it works only under 4.3GB disk.
Same a 1.
No. See kern/61960.
Wrong, ATA mk3 does solve the problem but using the current geomtry
set
Takahashi Yoshihiro wrote:
ATA-mkIII has three big problems.
I'd call it minor issues on PC98 :)
1. It seems that CHS mode is broken.
Only in the case of virtual geometry as used by PC98 only.
The problem is that the the real not virtual geometry is used for the
tranlation from LBA to CHS.
2. A
Emanuel Strobl wrote:
Am Mittwoch, 9. Februar 2005 15:00 schrieb Søren Schmidt:
[...]
As always, enjoy and let me know how it goes...
It's running here on several RELENG_5 machines. Like with j I also can't find
any problems with k :)
But the strange 16MB/s limit on my ICH2 (i815 B-step
Tim Welch wrote:
A problem still exists with 48-bit addressing. This url details a fix
I've been using for the last 4 months or so with no issues yet.
http://lists.freebsd.org/pipermail/freebsd-hackers/2004-October/008821.html
Are you stil experiencing problems with atamkIII ?
In that case its a
Søren Schmidt wrote:
http://people.freebsd.org/~sos/ata-mk3j.diff-releng5.gz
http://people.freebsd.org/~sos/ata-mk3j.diff-current.gz
http://people.freebsd.org/~sos/ata-mk3j.tar.gz
New version that fixes known problems so far etc now available:
http://people.freebsd.org/~sos/ata-mk3k.diff-releng5
Randy Bush wrote:
After suspend, my ThinkPad X40 now hangs with following logs (copied
by hand):
Hmm, do you have ATA compiled in or as modules. I could easily imagine
that modules could have problems, but as built in nothing really
changed...
my patched t41, current with ata in the kernel,
Randy Bush wrote:
diff -u -r1.20 ata-all.c
--- ata-all.c 2005/02/03 17:02:31 1.20
+++ ata-all.c 2005/02/07 14:27:57
@@ -630,7 +630,7 @@
void
ata_udelay(int interval)
{
-if (1 || interval (100/hz) || ata_delayed_attach)
+if (interval (100/hz) || ata_delayed_attach)
Randy Bush wrote:
Since I cannot debug this, I have no way of finding out whats wrong.
I will look at it when ACPI allows me to use suspend/resume again, until
then I'll concentrated on things that I can work on...
where's my refund? :-)
more seriously, shall we do a fund to get you a laptoy
Dag-Erling Smørgrav wrote:
Søren Schmidt [EMAIL PROTECTED] writes:
http://people.freebsd.org/~sos/ata-mk3j.diff-releng5.gz
http://people.freebsd.org/~sos/ata-mk3j.diff-current.gz
http://people.freebsd.org/~sos/ata-mk3j.tar.gz
sys/dev/ata/ata-all.c rev 1.235 conflicts, could you please update
Hideyuki KURASHINA wrote:
Hi, Søren
I've tested your patches using same config file as before, and it seems
work fine except on resume.
Hmm, thats one corner I cant test, suspend/resume dies horribly in ACPI
on all 3 notebooks I have since september last year or thereabouts...
After suspend, my
Ben Stuyts wrote:
On 3 Feb 2005, at 21:52, Søren Schmidt wrote:
o ATA RAID can only read metadata not write them. This means that
arrays can be picked up from the BIOS, but they cannot be created
from FreeBSD. This is being worked on for the final release as is
RAID5
ATA-mkIII first official snapshot.
This is the much rumoured ATA update that I've been working on for some time.
It contains a number of new things, and lacks a few features of the old code.
New items include:
o ATA is now fully newbus'd and split into modules.
This means that on a
Pertti Kosunen wrote:
My READ_DMA timeout problem with 160GB disk partitially solved. Asus
A7A266 southbridge (ALi 1535D+) don't support DMA with LBA48. This is
somehow worked around with Windows drivers, so is same possible in
FreeBSD also?
I guess their workaround is to use PIO mode to access
Doug White wrote:
On Mon, 13 Dec 2004, Joe Rhett wrote:
This is why I don't trust ATA RAID for fault tolerance -- it'll save your
data, but the system will tank. Since the disk state is maintained by
the OS and not abstracted by a separate processor, if a disk dies in a
particularly bad way the
Peter Radcliffe wrote:
Sren Schmidt [EMAIL PROTECTED] probably said:
Well, you probably should take care of your sister first :)
And no I dont have a paypal account, so far I've got by fine without it,
by using other means as checks, wiretransfers etc etc...
Do you have a list of things
Rob wrote:
Hi guys,
This is the first post I have seen on stable about SATA. (ok, maybe I'm
not subscribed to the right lists) Anyway I bought a brand new
beautiful Plextor DVD+RW SATA drive (PX712SA) for use on my AMD64+3800
machine. Win XP64-beta won't recognize it, and neither will
Peter Radcliffe wrote:
Sren Schmidt [EMAIL PROTECTED] probably said:
SATA ATAPI devices are not supported yet.
There are a few gotcha's though. Not all SATA controllers does support
SATA ATAPI even if out driver would, so its a mixed blessing for now.
Anyhow, as soon as I can get my hands on a
Garance A Drosihn wrote:
At 9:49 PM +0100 12/9/04, Søren Schmidt wrote:
I'm going to work on it soon thats for sure, however I have lots
on the burner currently so its no rush. However all kinds of
(S)ATA/ATAPI gear is always most welcome here in the lab, the
levels of support I can provide
Garance A Drosihn wrote:
At 1:01 AM -0600 12/7/04, Tim Welch wrote:
I'm getting NID not found/DMA errors on 5-STABLE with a Seagate 200gb
sata drive:
ad2: FAILURE - WRITE_DMA status=51READY,DSC,ERROR
error=10NID_NOT_FOUND LBA=268435455
This appears to be a result of 48-bit addressing. Any
It seems Eugene Grosbein wrote:
[ Charset KOI8-R unsupported, converting... ]
S?ren Schmidt wrote:
Of cause it should, and belive me I'm doing all I can to try get this
nailed. But I do have a real life as well, and a fulltime job, 3 kids,
vife and lots of other important things to care
It seems Dmitry Morozovsky wrote:
Hello there Soren,
any chances patch for ata subsystem at
date: 2002/04/18 19:11:45;
that fixes tagged support for ata(4) will be MFC'd before 4.6-R?
If you mean the patch that went into -current it doesn't apply to
the -stable branch at all, it fixed
It seems Dmitry Morozovsky wrote:
SS If you mean the patch that went into -current it doesn't apply to
SS the -stable branch at all, it fixed a problem introduced by the
SS busdma integration, not the problem that apparently hit some on -stable.
Well then it's another problem in -stable,
It seems Mike Tancsa wrote:
Yet, when I go to do a rebuild,
raidtest3# atacontrol rebuild ar0
atacontrol: ioctl(ATARAIDREBUILD): Operation not supported by device
raidtest3#
I guess there needs to be some way to tell the controller to use ad6 as
part of the rebuild no ?
You need to do
It seems Mike Tancsa wrote:
I guess there needs to be some way to tell the controller to use ad6 as
part of the rebuild no ?
You need to do a atacontrol detach on the failed device, then an
atacontrol attach on the new disk. BTW you dont need to boot
inbetween :)
atacontrol:
It seems Mike Tancsa wrote:
At 08:58 AM 4/2/02 +0200, Søren Schmidt wrote:
If a disk in a RAID1 goes bad, the driver will continue to use the
good half of the mirror, and log the fact that the mirror is now
in degraded mode. You can then use atacontrol to detach the disk,
add a new one
It seems Mike Tancsa wrote:
It looks like something in stable seem to break High Point 404 support
using the vendor's drivers and RAID administrator software.
http://www.highpoint-tech.com/rr404_down.htm
Highpoint's driver are for FreeBSD-4.5.
They wont work with -stable and what is to
It seems Kevin Oberman wrote:
I saw that new versions of several ATA programs including ata-all.c
had been loaded into stable. I hoped that this would fix the trap 12
when resuming from a suspend. No luck. Ian Dowses patches worked fine,
but the code in stable still crashes.
The fixes that I
1 - 100 of 106 matches
Mail list logo
