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
On 27Jun, 2009, at 14:29 , Bruce Cran wrote:
On Fri, 26 Jun 2009 22:11:08 +0200
Søren Schmidt 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.
It's gre
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 I
Hi there!
I thought I finally had a motherboard using one of the Marvell SATA/
PATA chips coming in, but unfortunately the delivery has been
postponed to some unspecified date, oh well..
Thats where you come into the picture as I'd like to get another one,
but finding boards that uses the
Maybe I'll find a generic solution this time around.
I'll commit this patch for now, as you said, it doesn't hurt..
-Søren
On 11Jun, 2008, at 10:00 , Andrey V. Elsukov wrote:
Søren Schmidt wrote:
Well, as you can see I tried this when I added the PM code to AHCI,
however
Hi
Well, as you can see I tried this when I added the PM code to AHCI,
however one of the reasons I left it out again (for now) is that it
doesn't work on more than about 50% of the AHCI chipsets out there..
Modern HW in a nutshell, you win some you loose some ;)
-Søren
On 11Jun, 200
Joao Barros wrote:
On 11/20/07, Thierry Herbelot <[EMAIL PROTECTED]> wrote:
Le Tuesday 20 November 2007, Ari Suutari a écrit :
I have Promise TX2 (PDC20575). It didn't work with 7.0 betas
before, but with this patch things run as well as they did
on 6.x.
Ari S.
Hello,
Ha
Hi All!
I'd like to get the final verdict of the attached patch and if it fixes
the problem or not.
Please test and report, its a bit urgent if it need to get into R7 :)
-Søren
? promise-fix2
? promise-fix3
Index: ata-chipset.c
Ulf Lilleengen wrote:
I tried the patch, but I end up with the partition table being incorrectly
read (probably) on the drives connected to my TX4 card. Normally, there's
one partition on the drive, but when I apply the patch, the drive provider
(ad6) is all that shows up in /dev.
When I rever
Arno J. Klaassen wrote:
definitely an improvement, but not sufficient (for my setup ) :
amd64-releng_6 on an ASUS A8V UP (box ran rock-stable
for years i386-releng_5 with same hardware apart TX4 and
drives)
from dmesg :
atapci0: port 0xe000-0xe07f,0xd800-0xd8ff
mem 0xfbb0-0xfbb00fff,0xfb
Søren Schmidt wrote:
Good catch!
However from my quick glimpse at the Promise sources the limit seems
to be 32 Dwords ie 32*4 = 128bytes.
I'll investigate further and ask Promise for the gory details, stay
tuned...
I dont think the PRD count limitation is a real problem, I've newer
Alexander Sabourenkov wrote:
Hello.
I have ported the workaround for the hardware bug that causes data
corruption on Promise SATA300 TX4 cards to RELENG_7.
Bug description:
SATA300 TX4 hardware chokes if last PRD entry (in a dma transfer) is
larger than 164 bytes. This was found while analysing
Christian Brueffer wrote:
On Wed, Feb 14, 2007 at 10:36:51AM +0100, Søren Schmidt wrote:
LI Xin wrote:
Danny Braniss wrote:
Hi,
Just wondering if there is any planned support for this card (or similar)
I've added sos@ to Cc list, who may have interest to th
LI Xin wrote:
Danny Braniss wrote:
Hi,
Just wondering if there is any planned support for this card (or similar)
I've added sos@ to Cc list, who may have interest to this as well. Note
that developing drivers requires that the developer has his hands on
actual hardware and hardware sp
Reed A. Cartwright wrote:
Freebsd wouldn't recognize my hard drive contoler, so I modified a
patch I found on the "stable" list, adding all the device ids I found
in Intel's documentation. Please add this to the stable or current
branch.
Below is the patch, I made with respect to 6.1-Release
Sean Thomson wrote:
Howdy Folks,
I'm trying to find out what the current/future support for SATA hotplug, NCQ, and Port Multiplier is. Specifically, I'm tied to intel's ICH9 SATA controller and pegged to implement the features if they aren't planned or available. That last part is up in the air
Rick C. Petty wrote:
On Thu, Jul 06, 2006 at 03:26:17PM -0600, Scott Long wrote:
Has anyone had success with SATA300 controllers with FreeBSD 6.1? I've
been
trying Promise and nVidia nForce4 and I'm not having any luck. Using a
MSI
K8NGM2-L motherboard and others, but 6.1's installation ha
John-Mark Gurney wrote:
Gerald Heinig wrote this message on Fri, Jun 30, 2006 at 10:41 +0200:
On Fri, 2006-06-30 at 01:16 -0700, John-Mark Gurney wrote:
This has now been fixed by making the built in driver return a negative
value for the probe.. so your probe routine can return 0, a
On Tor, 2006-03-23 at 14:55 -0500, Alain Hebert wrote:
> Hi,
>
> I'm about to invest in some Tyan Transport GT20 B5350G20S2H-LC.
>
> But since my epic battle trying to make the Promise Fasttrak 2300TX
> (PDC20580?) works right in Raid1, 2 weeks ago I'm a bit concern about
> those ne
Daniel Valencia wrote:
Hi,
So, what's your last src/ cvsup date/time? is your machine dualcore? if
so, are you building using the SMP option?
yep:
CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4800+ (2412.37-MHz
K8-class CPU)
and yep:
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
Daniel Valencia wrote:
Hello,
I started a short thread a few weeks ago, pointing out a problem with my
dualcore athlon64, when detecting the second SATA disk (/dev/ad6)... my chipset
is an nForce4... The problem was narrowed down to a few commits performed at a
particular date and time. My
Ariff Abdullah wrote:
On Mon, 24 Feb 2003 00:26:11 -0800
[EMAIL PROTECTED] wrote:
Hmm, could it be that the data track is always the last track ?
Yes.
so that CD players would be able to play the disks? or does not
matter?
Correct. Most hardware cd player are designed to play only the first
Chiharu Shibata wrote:
At Sun, 12 Feb 2006 17:02:37 JST, you wrote...
To mount this DISC, your opinion is...
(1) at first, try "cdcontrol -f /dev/acd0c info" to make sure where
track is data area.
(2) type "mount_cd9660 -o rdonly /dev/acd0t13 /cdrom".
Is this right?
Yeah that used to work
Chiharu Shibata wrote:
[snip]
So, if we should rehash this again I'll need more details on what it is
that fails exactly doing what, CD layouts etc etc...
This is a sample DISC's rayout.
Starting track = 1, ending track = 13, TOC size = 114 bytes
track start duration block length
Norikatsu Shigemura wrote:
I heard from Chiharu Shibata <[EMAIL PROTECTED]> about kern/60163.
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/60163
(He knew that this pr was closed, recently)
I cannot believe sos's close reason.
**
might get into the picture ruining the transfer
rate...
2Gb right now. Does the 4Gb limit apply to amd64 as well?
Yes, the SiI3114 is a 32bit device..
Søren Schmidt
[EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
there ? more than 4G and
bounce buffering might get into the picture ruining the transfer rate...
Søren Schmidt
[EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe,
slowdown is yet...
You need to find out what the transfer rates are for the RAW disk, ie
by doing a dd from /dev/zero to the disk with a a resonable blocksize
say 1M to minimize overhead. Also read speed from disk to /dev/null
blocksize 1M would be helpfull.
Søren Schmidt
[
t, is that on the
raw disk device or though the filesystem ?
Søren Schmidt
[EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
initely shorten the
drive life.
Indeed, 55C is way to high for 24/7 usage, and it might be that the
drive is choking on it and barely is able to compensate..
What does SMART say ? any unusual like high correction rates or
anything ?
Søren
o write such a driver back when, but HW seemed to have
disappeared from all the vendors I've asked so it was pu ton the
backburner.
Anyhow I should have the docs somewhere so it should be possible to
get this working...
Søren Schmidt
[EMAIL PROTECTED]
_
Roger O. Svenning wrote:
On 14/09/2005, at 17:36, Roger O. Svenning wrote:
You should try 6.0-beta4 as that contains the solution to
whatever
ATA problems you might have on 5.x. Let me know how that goes.
Søren Schmidt
[EMAIL PROTECTED]
cvsup running as I'm writing this
Would I
On 14/09/2005, at 17:36, Roger O. Svenning wrote:
You should try 6.0-beta4 as that contains the solution to whatever
ATA problems you might have on 5.x. Let me know how that goes.
Søren Schmidt
[EMAIL PROTECTED]
cvsup running as I'm writing this
Would I waste my time trying to enable
ld try 6.0-beta4 as that contains the solution to whatever
ATA problems you might have on 5.x. Let me know how that goes.
Søren Schmidt
[EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-
On 22/08/2005, at 10:08, [EMAIL PROTECTED] wrote:
what would be the best approach to implement aps on FreeBSD?
I got an Accelerometer driver which will deliver data. First
Version is available at
https://sourceforge.net/project/showfiles.php?
group_id=138242&package_id=160977
We have to p
David Gilbert wrote:
"Søren" == Søren Schmidt <[EMAIL PROTECTED]> writes:
Søren> David Gilbert wrote:
"João" == João Carlos Mendes Luís <[EMAIL PROTECTED]> writes:
João> IIF they really have command queueing, I do believe. So, a
João> bridged SATA d
Stephen Montgomery-Smith wrote:
Thomas Wolf wrote:
Stephen Montgomery-Smith <[EMAIL PROTECTED]> schrieb:
FUJISHIMA Satsuki wrote:
Currently native SATA drives are still not so popular. There are:
Seagate Barracuda ATA V, 7200.7, 7200.8
I have one of these, and I am really impressed by its performa
David Gilbert wrote:
"João" == João Carlos Mendes Luís <[EMAIL PROTECTED]> writes:
João> IIF they really have command queueing, I do believe. So, a
João> bridged SATA drive will not have command queuing, right?
Well... from what I've read, the WD bridged drives do have queueing
because they had a
Steven Hartland wrote:
Ah just added TCQ but still bridged I stand corrected :)
Right, I guess they just pulled it out from the attic, they had it on
some PATA devices back when, but there it newer caught on either :)
--
-Søren
___
[EMAIL PROTECTED] mai
Steven Hartland wrote:
I believe the second gen Raptors ( 74Gb ) are also native SATA
nope.
Currently native SATA drives are still not so popular. There are:
Seagate Barracuda ATA V, 7200.7, 7200.8
Maxtor DiamondMax10, MaXLineIII
Fujitsu MHT20xxBH(2.5 inch)
Any other drives (as far as I know, of co
Yury Tarasievich wrote:
Do I understand right (after looking into sources) that 4-STABLE has no
support for serial ATA devices??
Almost none, it works with a few controllers that looks like stock ATA
ones (HPT fx).
Anyhow you want 5.3 to get real SATA support..
--
-Søren
Mikhail P. wrote:
On Sunday 10 October 2004 23:30, Mikhail P. wrote:
On Saturday 09 October 2004 17:01, Mikhail P. wrote:
I also got another message off-list, where author suggested to play with
UDMA values. I switched from UDMA100 to UDMA66. System's uptime is 12
hours, and no timeouts so far.. bu
Mikhail P. wrote:
Hi,
This question probably has been discussed numerous times, but I'm somewhat
unsure what really causes ATA failures..
I have pretty basic server here which has two IDE drives - each is 200GB.
System is FreeBSD-5.2.1-p9
That server has been setup about 9 months ago, and just a
Roman Kurakin wrote:
Hi,
I have some problems with printing from kernel.
At first I think that my problems was cause I use printf,
but changed all of them to log cause it safe to use from
interrupt handlers. The situation become better but I still
observe system lockup in case I output some deb
Ceri Davies wrote:
On Mon, Oct 04, 2004 at 08:27:45PM +1000, Dave Horsfall wrote:
On Mon, 4 Oct 2004, Dmitry Karasik wrote:
I just wonder, if 'rm' is so fearful to you, why bother changing rm(1)?
Write a simple wrapper around, as many sysadmins do for their needs, and
use it instead of rm.
Precise
DB wrote:
Hi all
I'm trying to install FreeBSD 5.3-Beta5 on a friend's server. He has a promise
fasttracks SX4000 raid controller (raid level 5), but when booting freebsd we
get a list of all the 4 disks. Is that right? (haven't tried installing freebsd
on a raid computer). I've tried install freeb
Marc Fonvieille wrote:
On Tue, Aug 10, 2004 at 04:08:48PM +0200, Søren Schmidt wrote:
I used in past your cdrecord version when it was available on your site.
Is there any new version freely available? :)
They are still at my site actually, butI havn't cared to update them
much (dont fix
Marc Fonvieille wrote:
On Tue, Aug 10, 2004 at 03:44:03PM +0200, Søren Schmidt wrote:
You meant a growisofs version that does not require ATAPICAM?
Yes, one that uses the ATA userland interface instead, just as I have
versions of cdrecord/cdrdao.
I used in past your cdrecord version when it was
Marc Fonvieille wrote:
On Tue, Aug 10, 2004 at 03:11:50PM +0200, Søren Schmidt wrote:
I used my own creation that at some point could replace burncd, but for
now it is just a skunkworks project (and no I wont hand out copies :) )
I would think that growisofs will work (I do have an ATA version
Marc Fonvieille wrote:
On Mon, Aug 09, 2004 at 10:29:35PM +0200, Søren Schmidt wrote:
Wilko Bulte wrote:
How standard are DVD writers these days? In the sense
of: can I expect an ATAPI DVDwriter to 'just work'
with FreeBSD or are there brands/models to avoid or
to prefer?
Any experien
Wilko Bulte wrote:
How standard are DVD writers these days? In the sense
of: can I expect an ATAPI DVDwriter to 'just work'
with FreeBSD or are there brands/models to avoid or
to prefer?
Any experiences with a NEC ND-2510 ? Good/bad?
Bought one of those a couble of weeks ago, it has burnt CDR, CDR
M. Warner Losh wrote:
In message: <[EMAIL PROTECTED]>
Søren Schmidt <[EMAIL PROTECTED]> writes:
: Liam J. Foy wrote:
: > Hey guys,
: >
: > I have also emailed this to freebsd-mobile@, so just writing to see if any of you guys have had any problems with an Orino
Liam J. Foy wrote:
Hey guys,
I have also emailed this to freebsd-mobile@, so just writing to see if any of
you guys have had any problems with an Orinoco Gold and a Linksys AP in -CURRENT. They
seem to both work fine in windows, just unable to ping each other in freebsd. Here is
the outp
Mark wrote:
Søren Schmidt wrote:
Find out what the controller is it might not be supported or may
need compiling into a custom kernel.
It is a fairly standard onboard Promise 20376 controller. Perhaps I
need to recompile the kernel? Something like:
"device ata2 at isa? port IO_WD3 irq 16
Mark wrote:
Søren Schmidt wrote:
Steven Hartland wrote:
Find out what the controller is it might not be supported or may
need compiling into a custom kernel.
It is a fairly standard onboard Promise 20376 controller. Perhaps I
need to recompile the kernel? Something like:
"device ata2 a
Mark wrote:
Steven Hartland wrote:
Find out what the controller is it might not be supported or may
need compiling into a custom kernel.
It is a fairly standard onboard Promise 20376 controller. Perhaps I need to recompile
the kernel? Something like:
"device ata2 at isa? port IO_WD3 irq 16"
You
Christoph P. Kukulies wrote:
It is now dumping and I'm at 2.7 GB meanwhile. No more errors since the
last one at LBA=67 . Are these LBS identical to the block #?
Yes.
Maybe I'll give it another try (when this pass is through) and dump
from the beginning.
I'm about to get me a second identica
Christoph P. Kukulies wrote:
Thanks for all the helpful tips so far. It is a DLTA 307045 (3.5")
Don't know whether this is a 75GXP.
It is one of the dreaded models experience shows that all models after
this has some kind of problems, no wonder they sold out :)
I'm getting either these:
ad2: TI
C. Kukulies wrote:
Today an important (no backup of course) 46 GB IBM Deskstar
IDE disk crashed. It has a FreeBSD 4.8 on it with important data and programs.
Yes, shame on me that I didn't care about doing backups on it but it
has happened.
I evend tend to expend the bucks to get it recovered but a
Steven Hartland wrote:
I'm looking to get the 374 working with 5.2 / 5.2.1 does anyone have
any info on this. Highpoint have a driver for all the old version but
no source / 5.2 download. Can we get the source or is their an
alternative.
The HPT374 has been supported for quite some time (it even i
Roman Kurakin wrote:
Hi,
I have some problems with my HDD (ST380021A). The problem was checked
on 5.2, 5.2.1, and some
5.Current (cvsuped about week or two).
At first I got this problem while system installation. I get trap and
message from ata after I start a commit:
FAILURE READ_DMA sta
Mark wrote:
Dear Sirs:
I currently run my FreeBSD 4.7R, perfectly, on a Promise 20276 (RAID 1).
However, this chipset does not appear on;
http://www.freebsd.org/relnotes/4-STABLE/hardware/i386/x27.html#AEN33
Now I am looking at the board based on the Promise 20378 (ATA133). That does
not appear o
Mark wrote:
Hello,
Does FreeBSD 4.7R support SATA drives? I was planning on using an ASUS
A7V600 motherboard, which has a serial ATA RAID configuration.
You need somthing much more up to date than 4.7R to get SATA support.
4.9 has limitted support for a few SATA controllers, but to get real
SATA s
Sean Hamilton wrote:
"Søren Schmidt" <[EMAIL PROTECTED]> wrote:
| These are not "hangs" these are "pauses" and happens because the
| kernel thinks there are devices on these channels (are there ? no
| dmesg provided) and waits for the 31secs the spec calls f
Sean Hamilton wrote:
"Soren Schmidt" <[EMAIL PROTECTED]> wrote:
| It seems Sean Hamilton wrote:
| | I have two Asus boards (A7V8X and A7V) which have in common a
| | Promise ATA controller. Both of these boards hang up for about a
| | minute during the boot of 5.1-RELEASE, and emit messages about
It seems Philipp Mergenthaler wrote:
> > @@ -24,6 +24,7 @@
> > #endif /* not lint */
>
> > #include
> > +#include
>
> Jörg Wunsch commented that adding "include " would be
> wrong and that this ioctl should be moved to sys/cdio.h instead.
> (I guess then it should be renamed to CDIOCREADSPEE
It seems Jan Mikkelsen wrote:
> Søren Schmidt wrote:
> > ... However the Serverworks ROSB4 chips is not one I
> > would recommend using, if you need serious ATA support on
> > such a board, install a Promise TX2 or later or a HPT370 or later ...
>
> I think I
It seems Terry Lambert wrote:
> Andrew Gallatin wrote:
> > Terry Lambert writes:
> > > > So.. Is PIO safe? Is there any sort of CRC being done on PIO data?
> > >
> > > He just said: if your chipset is programmed correctly
> > > by the BIOS, then there will not be a problem, but
> > > apparen
It seems Andrew Gallatin wrote:
> I have a few machines with the following ata controller:
>
> atapci0@pci0:15:1: class=0x01018a card=0x chip=0x0266 rev=0x00 hdr=0x00
> They're dual-boot FreeeBSD/linux boxes. After loosing 2 filesystems in
> linux, I did a web search and I found that
It seems Rogier R. Mulhuijzen wrote:
>
> >It sounds as if the default five seconds isn't always enough time for
> >your disk to do its job. (I've only done poweroff on an idle system so
> >I haven't run into such a problem myself.)
> >
> >I don't see it would hurt anything for this default to be
It seems Kristian K. Nielsen wrote:
> Hey Søren,
>
> Do you have any idea what to do with the problems I am experiencing with the
> Intel-series chipset?
Uhm, what Intel chipset exactly, or is it a VIA chipset for Intel you mean ?
Throw me a pciconf -l and I'll check..
-Søren
To Unsubscribe:
It seems Nils Holland wrote:
> root@poison> pciconf -r -b pci0:0:0 0x0:0xff
Thanks! this was a kernel without the corruption fix, and it shows
that you need it, the MWQ bug has been fixed in your BIOS...
I have a new improved patch in the works that covers more chipset
comboes, it'll go into -cu
It seems Nils Holland wrote:
> On Sat, Dec 29, 2001 at 10:42:20PM +0100, Søren Schmidt stood up and spoke:
> > It seems Matthew Dillon wrote:
> > > :Anyways could I have you guys read out all 256 PCI regs from the
> > > :main chip that is the 0x03051106
It seems Matthew Dillon wrote:
> :Anyways could I have you guys read out all 256 PCI regs from the
> :main chip that is the 0x03051106 one ?
> :
> :-Søren
>
> How is this done?
With pciconf, fx:
sos# pciconf -r -b pci0:0:0 0x0:0xff
06 11 05 03 06 00 10 22 03 00 00 06 00 08 00 00
08 00 0
It seems Alson van der Meulen wrote:
> S?ren Schmidt([EMAIL PROTECTED])@2001.12.29 10:15:03 +:
> > It seems S?ren Schmidt wrote:
> > > We already have support for the Fasttraks in the kernel (and have had that
> > > for a long time now), with code that is developed outside Promise.
> > > Howe
It seems Søren Schmidt wrote:
> We already have support for the Fasttraks in the kernel (and have had that
> for a long time now), with code that is developed outside Promise.
> However it still needs a bit of work, but with a little luck that should
> clear up soon..
BTW, it is in
It seems Alson van der Meulen wrote:
> When searching for FreeBSD support for the Promise 20265r (FastTrack
> RAID, ATA100, integrated on some mainboards), I came across this, it
> looks like a FreeBSD RAID driver for this controller. It doesn't seem to
> be an official released driver, this is th
It seems Matthew Dillon wrote:
> Note that we aren't complaining about your patch or anything, you
> are simply the closest thing we have to a VIA chip expert right now :-)
I know, I want to nail this as badly as you guys do, I just want to
have the info I use verified before I base any p
It seems Mike Silbersack wrote:
> Agreed, it looks like the "MWQ bug" isn't addressed by soren's patch. The
> decription at
> http://www.networking.tzo.com/net/software/readme/faqvl019.htm
> doesn't give enough info to patch it, but this post to the linux-kernel
> mailing list seems to shed more
It seems Matthew Dillon wrote:
> Ok, I have more information on Nils problem. First of all, Soren's
> patch greatly reduced the rate of corruption. It took 25 loops of
> Nils 'cp' test to generate the corruption.
Hmm, did the second change I posted change anything ?
> However,
It seems Glenn Johnson wrote:
> I have had this exact problem. I have an Epox 8KTA board with a
> 1GHz Athlon (Thunderbird) with 256MB of PC-133 memory. I would
> consistently get random errors, usually during a compilation, using
> the default BIOS settings. After fiddling with some of the BIO
It seems Greg Lehey wrote:
> Information that could be interesting is (here my values):
>
> Processor:AMD Duron 850
> Motherboard: ECS K7VZA
> Memory: 1 128 MB SIMM, 100 MHz.
What FreeBSD version are you using ? I have put a fix for the 686b
southbridge bug in -current, but it i
It seems Brandon S. Allbery KF8NH wrote:
> On Thu, 2001-12-27 at 15:20, ian j hart wrote:
> > Myself and others have had IDE related problems. Search
> > the stable and hardware mail archives for
> > UDMA and ICRC [and ianjhart] for examples.
> >
> > There is also the "only supports 16MxN RAM" f
It seems Matthew Dillon wrote:
> This is great news! I'm crossing my fingers and hoping that Nils can't
> reproduce the crash any more with Soren's fix.
Me too :)
I have a small change that can be used if performace suffers too badly,
it has not provoked the problem again on any of the
It seems Søren Schmidt wrote:
> > Does this mean that if you dont have the ATA drivers in the kernel then
> > you wont get the fix ? As the bug occurs under high PCI loads then this
> > can potentially affect people with large amounts of PCI activity on
> > SCSI drives t
It seems Pete French wrote:
> > Anyhow since this is not always the case I did the fix for -current,
> > granted it should not be in the ATA driver, but since nobody else
> > really cared at the time
>
> Does this mean that if you dont have the ATA drivers in the kernel then
> you wont get th
It seems Wilko Bulte wrote:
> On Thu, Dec 27, 2001 at 12:15:56AM +0100, Søren Schmidt wrote:
> > It seems Matthew Gilbert wrote:
> > > > So, general question to everyone having crashes during heavy
> > > > IDE workloads: Please post your /var/
It seems Danny Braniss wrote:
> > It seems Matthew Gilbert wrote:
> > > > So, general question to everyone having crashes during heavy
> > > > IDE workloads: Please post your /var/run/dmesg.boot
> > > > output.
> >
> > > atapci0: port 0xd000-0xd00f at device 7.1 on
> >
> > You hav
It seems Matthew Dillon wrote:
> Soren, if you post a patch for 4.x I will be happy to follow-up
> with Brady. I've been working with Brady for several days now trying
> to track down corruption in the vm_page array. I *really* want to know
> if a VIA chipset patch solves his p
It seems Matthew Dillon wrote:
> Sorry, I meant I'd follow up with Matthew Gilbert. Also, I've
> been trying to track down a crash in nfs_node that Nils Holland
> has been having - he appears to have the same chipset and could
> have the same problem, and he can reproduce the pan
It seems Matthew Gilbert wrote:
> > So, general question to everyone having crashes during heavy
> > IDE workloads: Please post your /var/run/dmesg.boot
> > output.
> atapci0: port 0xd000-0xd00f at device 7.1 on
You have the VIA 82c686b southbridge chip which is known to cause sev
It seems Matthew Dillon wrote:
> I am trying to determine if our ATA/VIA setup code may have issues. I
> did a google search and came up with a linux-quirks patch which may
> apply to the random corruption problems people have been reporting.
> Here is the URL:
>
>
>http://w
It seems Bjoern Fischer wrote:
> Hello,
>
> AFAIK it is possible to attach/detach an ata channel with atacontrol on
> -CURRENT. I am looking for a way to do this on -STABLE, too. Particularly
> I want to hot swap an ATA disk w/ an appropriate IDE drive bay. No RAID
> is involved at the moment.
>
It seems Zwane Mwaikambo wrote:
> On Sun, 2 Dec 2001, Greg Lehey wrote:
>
> > Note that there are other chips out there which return the same PCI
> > information but which appear to be capable of ATA 100. I recently
> > gave a patch to Richard Sharpe (copied) which he says was able to get
> > hi
It seems Richard Sharpe wrote:
> Attached is the patch I am using, which is based on what Greg gave me.
> It tries UDMA5 first, and steps down ...
The following patch is bogus, it doesn't set the chip to the prober
mode (always sets it to UDMA2), it just set the disk, this wont
work guys...
I
It seems Zwane Mwaikambo wrote:
> On Sat, 1 Dec 2001, Søren Schmidt wrote:
>
> > Ohhh, I need alot more info before I can tell whats going on..
> > I need at least the dmesg from a verbosely booted system and
> > also a pciconf -l to tell what chips you have.
>
>
It seems Zwane Mwaikambo wrote:
> Hi,
> I've got a box which boots up with UDMA33 but during the boot
> sequence gets write problems and ends up disabling it and i presume
> falling back to PIO4. I've tested the same box on Linux 2.4.2+ and have
> had no problems running it at UDMA33.
>
> H
It seems "."@babolo.ru wrote:
> > It seems [EMAIL PROTECTED] wrote:
> > > > > Are there any planes to support
> > > > > VIA 82231 south bridge
> > > > > for UDMA33/66/100 ?
> > OK, support has been added to -current, MFC will follow later...
> I extracted patch
>
> --- sys/dev/ata/ata-dma.c W
It seems [EMAIL PROTECTED] wrote:
> > > Are there any planes to support
> > > VIA 82231 south bridge
> > > for UDMA33/66/100 ?
OK, support has been added to -current, MFC will follow later...
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of
It seems Greg Lehey wrote:
> >> These "cheap controllers" don't have any algorithms at all to speak of;
> >> they're just ATA controllers with BIOS code that supposedly understands
> >> striping/mirroring.
> >
> > There is no algorithm to speak of involved with striping, and just
> > a little more
1 - 100 of 133 matches
Mail list logo
