It seems Alexandr Listopad wrote:
Hello!
What about subj?
Did FreeBSD support HPT366 in the CURRENT???
Yes it does.
And if "yes" then what shall I do for it???
Use the ata driver.
If I boot from floppies - then error and reboot after 15sec, and don't
find this drive on IDE... what
It seems Maxim Sobolev wrote:
Sheldon Hearn wrote:
On Fri, 19 Nov 1999 01:16:55 +0200, Maxim Sobolev wrote:
Does anybody can explain why kernel with NewATA driver booted on machine
with ISA based IDE adapter trying to mount wd* as root f/s, while
exactly *the same* kernel booted
It seems Julian Elischer wrote:
I am ready to do my megga-commit to add the first stage of KSE-threading support
to
the kernel. If there is any argument as to the wisdom of this move,
then this is the time to speak up!
At this stage a commit would break alpha and ia64 until
they are
It seems [EMAIL PROTECTED] wrote:
For the last two days, my kernel builds have been failing with:
linking kernel.debug
ata-all.o: In function `ataioctl':
/usr/src/sys/dev/ata/ata-all.c(.text+0x791): undefined reference to
`atapi_queue _cmd'
*** Error code 1
I'm looking
It craps out with:
ACPI-0170: *** Error: AcpiLoadTables: Could not get RSDP, AE_NO_ACPI_TABLES
ACPI-0222: *** Error: AcpiLoadTables: Could not load tables: AE_NO_ACPI_TABLES
ACPI: table load failed: AE_NO_ACPI_TABLES
Needless to say, -current is now unusable on this latitude CPi since
suspend
It seems Mike Smith wrote:
Outstanding issues:
- The ACPI timecounter does not work on some ALi chipsets.
- ACPI mode results in some PCI devices not being configured
by the BIOS.
Power off on some VIA based boards (Epox8kta3 etc) doesn't work (reboot).
Suspend on some VIA based
Due to new ioctl's and a rearrange of the old ones make sure
that burncd kernel is in sync or wierd things can happen.
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
It seems Brian Fundakowski Feldman wrote:
After updating my system I can't burn CD-Rs successfully. Can anyone else?
What happens is pretty simple:
{/home/green/toxicity}$ burncd -s 8 -d audio /dev/null $(ls | trackclassify
burncd: ioctl(CDRIOCINITWRITER): Input/output error
acd0:
It seems Brian F. Feldman wrote:
OK, try this patch (kernel burncd need both to be remade)
I don't know... I got a page fault during an attempt to burncd and it seems
there are no messages in dmesg but acd0's softc was freed. I can't test any
more because my CD-RW doesn't probe on boot
It seems Brian F. Feldman wrote:
Søren Schmidt [EMAIL PROTECTED] wrote:
It seems Brian Fundakowski Feldman wrote:
After updating my system I can't burn CD-Rs successfully. Can anyone else?
What happens is pretty simple:
{/home/green/toxicity}$ burncd -s 8 -d audio /dev/null
It seems Maxim Sobolev wrote:
Hi Soren,
It seems that after a commit to reduce stack usage in ata driver some CDIO
ioctl's stopped working. Particularly, CDIOCREADSUBCHANNEL now returns an
'Invalid argument'. This could be verified by executing `cdcontrol stat'.
Uhm:
sos cdcontrol -f acd0
Kernel and burncd must be in sync again, a make kernel followed
by a make world should do it.
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
It seems Scott Long wrote:
On Mon, Oct 01, 2001 at 10:50:17AM +0200, Georg-W. Koltermann wrote:
I also was able to suspend and resume my machine (DELL Inspiron 7500)
with APM being configured (and ACPI being active by default). Sound
is dead after a resume,
What sound card?
PCMCIA
It seems John Baldwin wrote:
I found that I am no longer able to boot -current kernel on my machine. The
system panices right after initialising ed0 driver:
[...]
ed0: NE2000 PCI Ethernet (RealTek 8029) port 0xe800-0xe81f irq 9 at device
9.0 on pci0
panic: inthand_add: can't
It seems Matthew Jacob wrote:
I have experimented a bit with it for ATA disks, and have some very
rough code to deal with simple SMART commands, but nothing official
yet. However it is on my TODO list for items to support in the not
too distant future, its more a question of me having time to
Well, I finally got to it, please report back to me if this
works for you on newer SiS chipsets, especially:
SiS 630, 633, 635, 730, 733 and 735
Also, support for the older:
SiS 530, 540 and 620
Should be in place now.
Anyhow If you have one of the above, please test with a new -current,
It seems Greg Lehey wrote:
for n in 1 2 3 4 5
do
dd if=/dev/adX of=/dev/null bs=512K count=1
Don't you mean
dd if=/dev/ad$n of=/dev/null bs=512K count=1
?
No, I mean it exactly as written (X is the number of the disk to test).
-Søren
To Unsubscribe: send mail to
It seems Miklos Niedermayer wrote:
On Mon, Dec 03, 2001 at 09:28:26AM +0100, S_ren Schmidt wrote:
No, I mean it exactly as written (X is the number of the disk to test).
Ah, you mean just do it 5 times?
Yeps, the idea here is that I want the drive to cache the data, so that
I
It seems Miklos Niedermayer wrote:
I think they are idle (looking at vmstat -i), but i can't be sure.
However i have 2 machines here with VIA 82C596 chipset...
atapci0: VIA 82C596 ATA66 controller port 0xd800-0xd80f at device 4.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ad0: 28629MB
It seems nuzrin yaapar wrote:
Hmm, yes that looks somewhat on the low side...
Well, two things, the older VIA chips are not the best performers, but
I still think it should be better than that, I'll run some tests here,
I might have messed up something...
Are we talking -current or
It seems Matthew Dillon wrote:
:Hmm, I've just played around a bit, it seems we are hit by interrupt
:latency or something, if you limit the transfer to 128k, which allows
:the ATA controller to fetch it in one go, you will see the expected
:transfer rates. Now I dont see this on PCI based
I've just added VCD/SVCD support and that needs the kernel
and burncd to be in sync.
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
It seems Peter Wemm wrote:
Yes there are two problems. The physical failure problem seems to
be mostly restricted to the 75GXP. However the electronics/bandwidth/
density/whatever-it-is problem is uniform across the entire DTLA line.
We stopped using 75GXP's at work a while back, but we
It seems Stephen McKay wrote:
Now that burncd msinfo returns the correct values I noticed another small
problem: it displays the result on stderr instead of stdout.
Hmm, that was intentional...
Since very few people (nobody?) would be using this option yet because
of the previous problem,
It seems Stephen McKay wrote:
Are these changes intended for 4.5? I'm hoping the small change I
proposed would be accepted into 4.5, before anybody starts using
burncd msinfo in practice. I think this is sensible, even if
a much improved burncd is scheduled for 4.6.
You should ask
It seems Søren Schmidt wrote:
It seems Stephen McKay wrote:
Are these changes intended for 4.5? I'm hoping the small change I
proposed would be accepted into 4.5, before anybody starts using
burncd msinfo in practice. I think this is sensible, even if
a much improved burncd
It seems Mike Brancato wrote:
I'm running -current and have a Maxtor 160GB hdd hooked to the promise
ata133 card that came with it it will flake out for no apparent
reason. any clues? maybe bad hardware? anyone else getting these?
ad4: READ command timeout tag=0 serv=0 - resetting
In order to make some real progress on the ATA RAID support code I've
also made some rather trivial but many changes all over the ATA subsystem,
so if behavior changes on ordinary system I'd like to know...
In short - you have been warned ...
-Søren
To Unsubscribe: send mail to [EMAIL
It seems Tom Servo wrote:
Hi!
I checked and compiled the recent -CURRENT tree,
buildworld and buildkernel goes all fine.
When booting it seems to crash on initialization of my
Promise controller and get bad ivar request (4). I
stripped all possible drivers out of the kernelconfig,
It seems Tom Servo wrote:
The bad ivar request (4) message does *not*?come
from the ATA driver, you must have something else
that is ruining your day... Does it boot if you
take out the promise board ?
I was in a hurry yesterday and let the kernel compile
w/o the ata driver while
It seems Tom Servo wrote:
Hmm, I need alot more info the, board chipset, what
exact
Promise controller etc etc, and of cause the usual
dmesg
Here's the box:
Asus CUV4X-D mainboard, VIA 694X, dual-capable
2x P3-933, 768MB PC133 RAM in 3 DIMM(s)
Two IBM IC35L 60.1GB disks on first
It seems Tom Servo wrote:
I finally pulled the Promise out and it boots. Since I
need it for some Windows apps on the same box I put it
back in and commented some lines in ata driver
regarding the detection of Promise Fasttrak
controllers and it boots now w/o detecting it.
This is strange,
It seems Gerhard Sittig wrote:
On Thu, Feb 07, 2002 at 12:38 +0100, Søren Schmidt wrote:
[ snipped ATAPI - SCSI conversion ]
Doesn't burncd work for you on -current ?
Well, since you asked about it ... :)
I asked for *problems* not cosmetic issues :)
The bug (talking about a few
It seems Tom Servo wrote:
The bad ivar request (4) message does *not*?come
from the ATA driver, you must have something else
that is ruining your day... Does it boot if you
take out the promise board ?
I was in a hurry yesterday and let the kernel compile
w/o the ata driver while
It seems Tom Servo wrote:
I finally pulled the Promise out and it boots. Since I
need it for some Windows apps on the same box I put it
back in and commented some lines in ata driver
regarding the detection of Promise Fasttrak
controllers and it boots now w/o detecting it.
This is strange,
It seems Gerhard Sittig wrote:
On Thu, Feb 07, 2002 at 12:38 +0100, Søren Schmidt wrote:
[ snipped ATAPI - SCSI conversion ]
Doesn't burncd work for you on -current ?
Well, since you asked about it ... :)
I asked for *problems* not cosmetic issues :)
The bug (talking about a few
It seems Andrey A. Chernov wrote:
Currently SC_MOUSE_CHAR occupes 0xd0-0xd4 range which produce conflict
with several languages code tables. I plan to redefine it by default to
0x03-0x07 leaving possibility to redefine it to any range as currently
present. This way minimizes arcane
It seems Brian F. Feldman wrote:
Welp, this is the n-dozenth time that the ATA driver has wedged large parts
of my entire system because it feels it needs to reset my CD-R when I'm
trying to start burning a CD. I get the good old
acd0: WRITE_BIG command timeout - resetting
ata3:
It seems [EMAIL PROTECTED] wrote:
Which ports break?
There are no other consumers (AFAIK) than atacontrol (yet)
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
I've decided to do a quick poll on which CDR/CDRW drives people
have that either work or doesn't work.
I'll collect all the info and make a web page that will show
which drives are supported, and which are not, and hopefully
this will help me find a solution that works for all.
Please send a
As promised I've made up a list of reports I've received so far go to
http://freebsd.dk/ and follow the link.
I also have a patch for the Yamaha's (yamaha-cdr.p1) which also
can be found via the above URL. Let me know if that make things
work...
-Søren
To Unsubscribe: send mail to [EMAIL
It seems Terry Lambert wrote:
Jonathan Smith wrote:
That's good enough. :) Thanks
Maybe _that_ will keep that ata code from over-riding
the bios to disable dma (or maybe the bios just wasn't
doing it's job right ;)
This won't work.
Someone was having the same problem the
It seems Terry Lambert wrote:
Søren Schmidt wrote:
This won't work.
Someone was having the same problem the other day, and
I suggested the same soloution, but after probe, the
damn driver enabled UDMA at attach time anyway.
Just set hw.ata.ata_dma=0 in /boot/loader.conf
It seems [EMAIL PROTECTED] wrote:
After applaying the next patch I can now see
in dmesg output:
ad4: 19574MB IBM-DPTA-372050 [39770/16/63] at ata2-master tagged UDMA66
ad6: 19623MB IC35L020AVER07-0 [39870/16/63] at ata3-master tagged UDMA66
.
It seems Nickolay N. Dudorov wrote:
The diskid (IC...) has me somewhat stumped though, I would have thougt
the used something like all other IBM disks. Is this a genuine IBM disk
or is it some kind of OEM/rebadged device ?
Yes, this IS genuine IBM disk.
See:
I'm having problems with both an internal VIA'686 and a PCI base
ESS Solo1, both seem to loose interrupts. The interrupts doesn't
even show up in a vmstat -i / systat so something is definitly
wrong. BTW the exact same HW work just fine with -stable ?
Cameron ? anyone ?
-Søren
To Unsubscribe:
It seems Cameron Grant wrote:
I'm having problems with both an internal VIA'686 and a PCI base
ESS Solo1, both seem to loose interrupts. The interrupts doesn't
even show up in a vmstat -i / systat so something is definitly
wrong. BTW the exact same HW work just fine with -stable ?
It seems Makoto MATSUSHITA wrote:
% atacontrol info 0
Master: ad0 IBM-DJSA-220/JS4OAC3A ATA/ATAPI rev 5
Slave: no device present
% atacontrol info 1
Master: no device present
Slave: no device present
% atacontrol info 2
%
Hmm, ata driver says there are two buses.
sos make
In current as of 5 mins ago:
cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi
-g -nostdinc -I- -I. -I../.. -I../../dev -I../../contrib/dev/acpica
It seems Makoto MATSUSHITA wrote:
sos Thats because of the runtime attach/detach code in current, if the
sos channel HW is there, its attached so you can add a device later
sos with atacontrol without having to boot. In -stable the channel is
sos not attached if no devices are present at
It seems Gerhard Sittig wrote:
On Sat, Jun 23, 2001 at 11:25 +0100, Matthew Frost wrote:
On Tue, May 29, 2001 at 10:12:35AM -0500, Ken Wills wrote:
This patch (well, yamaha-cdr.p2), allows my Yamaha 2100E to
fixate disks now! Thanks Soren and others!
Yes. It's fixed it for our
It seems Maxim Sobolev wrote:
[ Charset KOI8-R unsupported, converting... ]
Hi,
Is there a way to forcefully power-down one of the IDE HDD drives
attached to the system? On my primary workstation I have two - one for
FreeBSD and second for W2K, so it would be nice to suspend one that is
It seems Samuel Tardieu wrote:
With recent -CURRENT kernels (including one from yesterday), I get
random strange behaviours as far as my ATA disk is concerned:
- the disk light stays on;
- I can read from the disk but cannot write anything to it (sync
blocks, writes from vi block,
One gets the first DMA buffer full, then the process hangs...
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
It seems Richard Todd wrote:
I found much the same thing; specifically, the problematic change is this one:
jhb 2001/08/10 14:08:57 PDT
Modified files:
sys/kern kern_synch.c
Log:
Work around a race between msleep() and endtsleep() where it was possible
Revision ChangesPath
1.154 +24 -4 src/sys/kern/kern_synch.c
Yups, reverting this, even in a newer kernel makes sound work again,
well the VIA support is still not sounding proberly, but it didn't
before as well so thats not related to this bogon...
Perhaps the bug
It seems Alexander Leidinger wrote:
On 19 Aug, Søren Schmidt wrote:
Yups, reverting this, even in a newer kernel makes sound work again,
well the VIA support is still not sounding proberly, but it didn't
before as well so thats not related to this bogon...
Perhaps the bug
It seems Jim Bryant wrote:
Yups, reverting this, even in a newer kernel makes sound work again,
well the VIA support is still not sounding proberly, but it didn't
before as well so thats not related to this bogon...
Perhaps the bug in the chipset^wPCI-spec?
I dont think so, before the
It seems John Baldwin wrote:
In servalan.mailinglist.fbsd-current Maxim Sobolev writes:
I found that after reverting the following deltas (jhb's 10 August commit)
sound starts working again:
[list of deltas deleted]
I found much the same thing; specifically, the problematic change
It seems David O'Brien wrote:
diskcheckd is very annoying. Many doubt its usefulness in detecting
errors before it is too late. It thinks 40% of my disks are bad (which
I don't). I've turned it off, I know many that have.
I would like to remove it from the base system and put it in
It seems Kenneth D. Merry wrote:
On Thu, Feb 28, 2002 at 10:49:18 -0800, Julian Elischer wrote:
This is definitly something that is needed..
The question is whether the CAM and ATAPI authors feel it is
right. We are guided by them (even though we desperatly need this).
Personally
It seems Matthew N. Dodd wrote:
On Thu, 28 Feb 2002, Søren Schmidt wrote:
I'll quit the ATA/ATAPI development/maintenance if this goes in quickly.
What? Are you looking at the same patches that everyone else is?
Read the rest of my mail, the problem is not the patches as much
as it is all
It seems Kenneth Culver wrote:
Hmm, why do we need to add new layers and loss of functionality
to the ATAPI devices ?
Many many many people would like to be able to use cdrecord to burn data
to cd's so that all the front-ends to cdrecord will work. It's much nicer
than memorizing mkisofs
It seems Scott Long wrote:
As I have stated several times, I have no problem with ATAPI being
sent through CAM as long as the usual way stays (some of us cannot
afford the weight of those extra layers, nor loose functionality).
I'd do the integration somewhat differently to even further
It seems Justin T. Gibbs wrote:
What functionality is lost by this ability?
Compare the features of the ATAPI vs SCSI CD drivers..
This is exactly why I'd like to see this code merged. The hardware
changes too rapidly. The specs change too rapidly but MMC is MMC.
Exactly.
More of us
It seems Scott Long wrote:
I'm mainly raising my hand to take the abuse that will no doubt happen
once in a while.
Sure, maybe we should make Thomas a committer so he could look after
it himself ? Interested ? Got the time ? I'm all ears for volounteers...
Ummm, I'm
It seems Max Khon wrote:
On Thu, Feb 28, 2002 at 09:58:00PM +0100, S?ren Schmidt wrote:
Hmm, why do we need to add new layers and loss of functionality
to the ATAPI devices ?
Many many many people would like to be able to use cdrecord to burn data
to cd's so that all the
As some might have noticed I've done some significant work on
the ATA RAID support (for Promise Highpoint controllers)
all thanks to Advanis which has made this possible.
The code as it is now in -current allows for RAID1's (mirrors)
to be properly handled when a disk dies, that means the
For those that have problems with burncd or simply cannot live
without, I've put up the source for an ATAPI enabled cdrecord on:
ftp://freebsd.dk/pub/ATA/cdrtools-1.10-ATA.tgz
On -stable it needs the ATA driver update I did a yesterday.
It does *not* need CAM or the atapicam patches, it uses
It seems Samuel Tardieu wrote:
Has the ATAPICAM patch entered the kernel sources already? I cannot
seem to find the option in LINT.
No, Justin has called for a timeout on that
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the
It seems Thomas Quinot wrote:
Le 2002-03-19, Søren Schmidt écrivait :
ftp://freebsd.dk/pub/ATA/cdrtools-1.10-ATA.tgz
On -stable it needs the ATA driver update I did a yesterday.
It does *not* need CAM or the atapicam patches, it uses the
ATA driver directly..
Alternatively
It seems Kenneth Culver wrote:
Oh yes, I forgot, there is also a cdrdao on:
ftp://freebsd.dk/pub/ATA/cdrdao-1.1.5-ATA.tgz
Again no CAM or atapicam needed :)
Is this a competition??? :-)
Not that I know of, but I recently got permission to share the
(very limitted BTW) changes I did
It seems Stijn Hoop wrote:
You and Thomas rock! Any chance of a cdparanoia-ATA.tgz ? :)
No idea what it is, I cant seem to find it in ports either...
URL ?
Does it work on FreeBSD already with CAM or ?
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current
It seems Kenneth Culver wrote:
Not that I know of, but I recently got permission to share the
(very limitted BTW) changes I did to cdrecord/cdrdao over a year
ago, and now that the infrastructure for using it is in both
-stable and -current, it seemed worthwhile to release it to
the
It seems Thomas Quinot wrote:
Le 2002-03-19, Søren Schmidt écrivait :
ftp://freebsd.dk/pub/ATA/cdrdao-1.1.5-ATA.tgz
Again no CAM or atapicam needed :)
Hum this package does not compile out of the box:
c++ -DHAVE_CONFIG_H -I.. -I. -I/usr/local/include/pccts -O -pipe -c
It seems Kenneth Culver wrote:
It puts its stuff in /usr/local/bin
Wierd, for me it put everything in /opt/schily/blah...
I hate it when people do that. :-)
I've put up a new version with the default changed to /usr/local...
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
It seems Thomas Quinot wrote:
Le 2002-03-19, Søren Schmidt écrivait :
gmake[1]: *** [TocParser.o] Error 1
You need to have pccts installed to compile cdrdao
I do, and as I mentioned in my first message, the compileation completed
after a gmake distclean.
okies...
These utils
It seems Scott Long wrote:
In the past you've objected to ATAPI-CAM on two grounds, fear that it
won't be done right, and fear that it will add more work to yourself. I
think that there are enough highly intelligent people interested in the
project that the first issue can be put to rest.
It seems Thomas Quinot wrote:
Le 2002-03-20, Søren Schmidt écrivait :
I thought there was work on this already ? Justin called for a timeout
to get it done the right way in CAM, I was sort of expecting to
hear about how that should integrate in the ATA/ATAPI world...
Well I have
It seems NAKAJI Hiroyuki wrote:
I checked the difference between them to find that ata device on HPT370 is
not detected,
+pcib2: device atapci0 requested unsupported I/O range 0x0-0x9c00 (decoding
0x9000-0xafff)
+ata2: probe allocation failed
You need the
options
It seems Steve Kargl wrote:
=== sbin/atacontrol
cc -O -pipe -c /usr/src/sbin/atacontrol/atacontrol.c
/usr/src/sbin/atacontrol/atacontrol.c: In function `cap_print':
/usr/src/sbin/atacontrol/atacontrol.c:121: structure has no member named `lba_size'
It seems Alexander Leidinger wrote:
Something about a missing or wrong ELF header. I thought it was a
general problem so everyone would see it, but it turned out to be a
problem in the ata driver. After turning off tagged queuing everything
was fine. I'm not the only one with problems with
It seems Alexander Leidinger wrote:
On 9 Apr, Søren Schmidt wrote:
Søren, as a data point: a Mar 12 kernel was fine for me, a Mar 27 kernel
too, but a Apr 6-8 kernel spills alot of tag related errors (I think you
already have those errors from someone else, no need to repeat them
here
It seems Terry Lambert wrote:
Giorgos Keramidas wrote:
ad0: READ command timeout tag=1 serv=1 - resetting
ata0: resetting devices .. ad0: invalidating queued requests
done
Turn off tagged queing. S?ren knows about this error and tries to
reproduce it (but fails as far as I
It seems Alexander Leidinger wrote:
I've seen this quite a few times, but I can't reliably reproduce it
yet. It seems to hit me a lot when the ad0 drive spins like crazy
doing stuff that is heavy on disk I/O. Disabling tag queueing now to
see if this fixes things. But even if it does,
It seems Alexander Leidinger wrote:
On 15 Apr, Søren Schmidt wrote:
Some people see this after the mega MFC on -stable too.
Could I have you guys try this simple patch ?
Does not work.
As in:
No change or breaks completely (if so how)...
-Søren
To Unsubscribe: send mail
It seems Terry Lambert wrote:
Søren Schmidt wrote:
Is your drive perchance an IBM DTLA?
It's known to have these problems.
Cool! would you like to share where that information is available so
I can possibly work around the problem ??
IBM DTLA drives are known to be problematic
It seems Terry Lambert wrote:
IBM DTLA drives are known to be problematic. If you use that
in a search engine, it will find numerous references to the
drive electronics being too slow for sustained access to the
sectors closes to the spindle.
This thread is about tagged queueing
It seems Terry Lambert wrote:
Søren Schmidt wrote:
For a more scientific test, downloading the firmware tool and
setting the DMA transfer rate down, and checking for problems,
would be pretty overwhelming evidence. Personally, I don't have
any of the buggers lying around to test
It seems Giorgos Keramidas wrote:
On 2002-04-14 23:46, Terry Lambert wrote:
Is your drive perchance an IBM DTLA?
It's known to have these problems.
Nay. A Western Digital disk I bought about 2.5 years ago.
Hmm, AFAIK WD newer had a disk that worked right with tags,
and I've newer been
It seems Andrey A. Chernov wrote:
This mega-commit:
date: 2002/04/05 13:13:XX; author: sos;
Make the ATA driver compile work on the sparc64 platform.
breaks i386 ATA at least for following card:
atapci0: Intel ICH2 ATA100 controller port 0xb800-0xb80f at device 31.1
It seems Andrey A. Chernov wrote:
On Wed, Apr 17, 2002 at 21:42:19 +0200, Alexander Leidinger wrote:
If you are running with tagged queing: turn it off. I got the same
Thanks, turning tags off helps!
It means that sparc64 ATA commit breaks tags. They work nice before it.
I know, I
It seems Terry Lambert wrote:
My other hunch is that there will need to be a channel reserved
for reset commands to be queued to the disk, so that you can
queue more commands to it later (e.g. can't connect to send the
reset because of the already disconnected commands in progress).
Terry,
It seems Doug Barton wrote:
Given the impending 4.6-release, might it make sense to back off ata in
The busdma/sparc64 code is *not* in stable...
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
It seems Alexander Leidinger wrote:
On 18 Apr, Doug Barton wrote:
Given the impending 4.6-release, might it make sense to back off ata in
-stable to the last known-good state?
We have some time until the code freeze, so give him some days to track
it down. If he is able to fix it: fine,
It seems Terry Lambert wrote:
Søren Schmidt wrote:
It seems Terry Lambert wrote:
My other hunch is that there will need to be a channel reserved
for reset commands to be queued to the disk, so that you can
queue more commands to it later (e.g. can't connect to send the
reset
It seems Matthias Schuendehuette wrote:
I didn't mean for the reset itself, I meant for the process. You
can't take back writes that are in progress and not acknowledged,
in order to retry them after the reset, so as to not lose data.
Oh yes you can, the ATA driver does just that in
It seems Terry Lambert wrote:
Søren Schmidt wrote:
I didn't mean for the reset itself, I meant for the process. You
can't take back writes that are in progress and not acknowledged,
in order to retry them after the reset, so as to not lose data.
Oh yes you can, the ATA driver does
It seems Terry Lambert wrote:
Hmm, since I havn't been able to get my hands on the problem
(I've been running 3 systems here with tags all over since the
first report, not a single hickup yet :( ) I can't tell whats
going on, it might be that the drive somehow gets really confused
I
It seems Alexander Leidinger wrote:
On 18 Apr, Søren Schmidt wrote:
What's your theory on it?
None so far, I've instrumented the code here, and I simply cannot
see what should go wrong (yet).
Does it make sense to give this instrumentation to someone who can
reproduce
1 - 100 of 106 matches
Mail list logo
