point.
Reported to fix https://bugzilla.redhat.com/show_bug.cgi?id=351451
Signed-off-by: Robert Hancock <[EMAIL PROTECTED]>
--- linux-2.6.24/drivers/ata/sata_nv.c 2008-01-24 16:58:37.0 -0600
+++ linux-2.6.24edit/drivers/ata/sata_nv.c 2008-01-29 18:39:37.0
-0600
@@ -2
Tejun Heo wrote:
Tuomas Jormola wrote:
00:08.0 IDE interface [0101]: nVidia Corporation MCP61 SATA Controller
[10de:03f6] (rev a2)
00:08.1 IDE interface [0101]: nVidia Corporation MCP61 SATA Controller
[10de:03f6] (rev a2)
That's MCP61 which is GENERIC variant in sata_nv which does not suppo
Alexander wrote:
Hello!
The problem described at https://bugzilla.redhat.com/show_bug.cgi?id=351451 and
at http://ubuntuforums.org/showthread.php?t=655772 and supposedly fixed by the
patch http://kerneltrap.org/mailarchive/linux-kernel/2007/11/25/445094 is still
there. I have compiled 2.6.24-rc7
Mark Lord wrote:
Robert Hancock wrote:
Luben Tuikov wrote:
--- On Mon, 1/28/08, Robert Hancock <[EMAIL PROTECTED]> wrote:
The trick is that if an ATAPI device is connected, we (as
far as I'm aware) can't use ADMA mode, so we have to switch that
port into legacy mode.
Can
Tejun Heo wrote:
Robert Hancock wrote:
This patch is based on an original patch from Kuan Luo of NVIDIA,
posted under subject "fixed a bug of adma in rhel4u5 with HDS7250SASUN500G".
His description follows. I've reworked it a bit to avoid some unnecessary
repeated checks b
Luben Tuikov wrote:
--- On Mon, 1/28/08, Robert Hancock <[EMAIL PROTECTED]> wrote:
The trick is that if an ATAPI device is connected, we (as
far as I'm
aware) can't use ADMA mode, so we have to switch that
port into legacy
mode.
Can you double check this with the HW archite
en bit is set
then ADMA indicates that command with corresponding tag number completed
execution.
So i added the check notifier code. Sometimes i saw that the notifier
reg set some bits , but the adma status set NV_ADMA_STAT_CMD_COMPLETE
,not NV_ADMA_STAT_DONE. So i added the NV_ADMA_STAT_CMD_COMPLE
We've got a bit of a problem with the sata_nv driver that I'm trying to
figure out a decent solution to (hence all the lists CCed). This is the
situation:
The nForce4 ADMA hardware has 2 modes: legacy mode, where it acts like a
normal ATA controller with 32-bit DMA limits, and ADMA mode where
Kuan Luo wrote:
Robert worte.
Kuan, does this patch (using the notifiers to see if the command is
really done) still work if one port on the controller has
ADMA disabled
because it's in ATAPI mode? I seem to recall Allen Martin mentioning
that notifiers wouldn't work in this case.
I just
(linux-ide cc'ed)
Ignacy Gawedzki wrote:
On Fri, Jan 25, 2008 at 09:03:02PM -0600, thus spake Robert Hancock:
Ignacy Gawedzki wrote:
Hi everyone,
I'm having trouble to determine the cause of the following behavior. I'm
not
even sure that I'm supposed to hot plug and unpl
Jeff Garzik wrote:
Robert Hancock wrote:
Jeff Garzik wrote:
Ping... sata_nv status is still a bit open for 2.6.24, and I would
like to move us forward a bit.
* Kuan's patch... it has been confirmed (and is needed), correct?
can someone work up a good patch for 2.6.24? The only
Kuan Luo wrote:
First thank davide to help to send the attachment.
Robert,
The patch is to solve the error message "ata1: CPB flags CMD err,
flags=0x11" when testing HDS7250SASUN500G in rhel4u5.
I tested this hd in 2.6.24-rc7 which needed to remove the mask in
blacklist to run the ncq and the s
Jeff Garzik wrote:
Ping... sata_nv status is still a bit open for 2.6.24, and I would like
to move us forward a bit.
* Kuan's patch... it has been confirmed (and is needed), correct? can
someone work up a good patch for 2.6.24? The only one I ever received
was badly word-wrapped, and at t
Tejun Heo wrote:
Jake wrote:
http://marc.info/?l=linux-ide&m=120069298104580&w=4
It has been 2 weeks here hunting for some solutions,
can you recommend anything that I should try? Thank you.
Can you please post full boot log from the working kernel && broken
kernel? It seems you were using id
James Bottomley wrote:
On Sun, 2008-01-13 at 16:29 +, Alan Cox wrote:
Yes, I concur for the short term. The other two possible courses of
action either involve long discussions (the different device one) or
you'll never quite be sure you got all the paths (the GFP_DMA32 one).
At least with
Kuan Luo wrote:
Robert hancock wrote:
What problem does this resolve? I tested it against the cache
flush/NCQ
write switching problem we've been trying to solve, and it
doesn't look
like it fixes that one - if I apply this patch and then remove the
udelay(20) in sata_nv.c that I a
James Bottomley wrote:
On Sat, 2008-01-12 at 17:04 -0600, Robert Hancock wrote:
I don't think the problem is that there's some buffer which is getting
allocated above 4GB and never bounced, since the problem goes away if
ADMA is disabled entirely and the DMA mask remains 32-bit
James Bottomley wrote:
With mem<=4098M or sata_nv.adma=0 it still mounts and works ok.
As I wrote, it would appear that somehow the blk_queue_bounce_limit
setting that the driver has made is not being respected and the block
layer is still trying to feed it addresses over 4GB. Any ideas anyone?
Alexander wrote:
Robert Hancock wrote:
There's this patch which was intended to fix it:
http://lkml.org/lkml/2007/11/22/148
I applied this patch to 2.6.24-rc7. Now at boot time my DVD-RW is
normaly detected as:
sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
Gabor Gombas wrote:
On Mon, Jan 07, 2008 at 06:10:29PM -0600, Robert Hancock wrote:
Gabor, I just noticed you said that it worked OK in 2.6.20, yet 2.6.22
fails. 2.6.20 had ADMA support as well, so I wonder what change started
causing the problem. Would it be possible for you to do a git
Kuan Luo wrote:
hi robert,
I have fixed a bug in rhel4u5 2.6.9-55 when running adma mode
with HDS7250SASUN500G.
Could you check this code and if no problem, then help me to
submit to the newest kernel.
What problem does this resolve? I tested it against the cache flush/NCQ
wr
Kuan Luo wrote:
hi robert,
I have fixed a bug in rhel4u5 2.6.9-55 when running adma mode
with HDS7250SASUN500G.
Could you check this code and if no problem, then help me to
submit to the newest kernel.
It seems like a reasonable change - I'm sure you guys would know better
tha
TAPI devices
where it is limited to 32-bit DMA.. Could that be breaking or
insufficient somehow?
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line "
if (dev)
ata_scsi_dev_config(sdev, dev);
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
t
Tejun Heo wrote:
How about putting a bunch of printks inside the interrupt handler? That
would tell us if it's even reaching the interrupt handler..
If you give me a patch, I'll apply it and cause lock up and report the
result. Just shoot the patches my way. But maybe reproducing the lock
up
Tejun Heo wrote:
Tejun Heo wrote:
Robert Hancock wrote:
Tejun Heo wrote:
Tejun Heo wrote:
[ 34.466899] testing NMI watchdog ... <4>WARNING: CPU#0: NMI appears
to be stuck (0->0)!
[ 34.555056] WARNING: CPU#1: NMI appears to be stuck (0->0)!
Oops, missed that. I'll se
Guillaume Laurès wrote:
Le 8 janv. 08 à 01:29, Robert Hancock a écrit :
From your report:
ata5: EH in ADMA mode, notifier 0x0 notifier_error 0x0 gen_ctl
0x1501000 status 0x400
ata5: CPB 0: ctl_flags 0x1f, resp_flags 0x1
ata5: CPB 1: ctl_flags 0x1f, resp_flags 0x2
ata5: CPB 2: ctl_flags
Tejun Heo wrote:
Tejun Heo wrote:
[ 34.466899] testing NMI watchdog ... <4>WARNING: CPU#0: NMI appears
to be stuck (0->0)!
[ 34.555056] WARNING: CPU#1: NMI appears to be stuck (0->0)!
Oops, missed that. I'll see whether there's IRQ storm going on.
I made the nv irq handler to print messa
Tejun Heo wrote:
Tejun Heo wrote:
Robert Hancock wrote:
Okay, just succeeded on the current #upstream-fixes, attaching the log.
The machine is a brick after the crash.
I assume the cable got reconnected at 325 seconds? It looks like that
was during error handling for the previous unplug?
I
Tejun Heo wrote:
Tejun Heo wrote:
Robert Hancock wrote:
This has only been reported on one person's MSI board. Apparently
another revision of the same board is reported to work, and I can't
duplicate the problem on my Asus board, so it could just be some
hardware problem on that m
ller is waiting for a response. The timeout is
30 seconds, so that means the drive failed to service those queued
commands for that length of time.
It may be that your drive has a poor NCQ implementation that can starve
some of the pending commands for a long time under heavy load?
--
Robert
Tejun Heo wrote:
Robert Hancock wrote:
Mark Lord wrote:
Tejun Heo wrote:
Hello, guys.
We still have three problems with ADMA.
* hard lockup during resume * occasional hard lockup after
hotplug or other erros (probably related to the above?)
This has only been reported on one person'
Allen Martin wrote:
Dunno about the NVidia version.
Theirs works rather differently - the GO bit is there, but there's
another append register which is used to tell the controller
that a new
tag has been added to the CPB list.
The only thing we currently use the GO bit for is to switch
be
Mark Lord wrote:
Tejun Heo wrote:
Hello, guys.
We still have three problems with ADMA.
* hard lockup during resume
* occasional hard lockup after hotplug or other erros (probably related
to the above?)
This has only been reported on one person's MSI board. Apparently
another revision of the
oth support (SAS & SATA) some type of port-multiplier/
multiplexor/ option to allow more disks/port.
However, (please correct?) SATA uses a hub type architecture while
SAS uses a switch architecture. My experience with network hubs vs.
switches is that network hubs can be much slower if ther
Linda Walsh wrote:
Robert Hancock wrote:
Looks like the drive reports ERR/ABRT (command aborted), meaning it
likely doesn't support those commands.
---
Except the PATA version of the drive does (same capacity, & other
specs). Seagate would
disable "advanced" fe
Allen Martin wrote:
Dunno about the NVidia version.
Theirs works rather differently - the GO bit is there, but there's
another append register which is used to tell the controller
that a new
tag has been added to the CPB list.
The only thing we currently use the GO bit for is to switch
be
Linda Walsh wrote:
I seem to remember reading about some problems with Promise SATA & ACPI.
Does this address that or is that a separate issue? (Am using no-acpi for
now, but would like to try acpi again if it may be fixed (last time I tried
it with this card, "sdb" went "offline" (once it un
Linda Walsh wrote:
Robert Hancock wrote:
Linda Walsh wrote:
Alan Cox wrote:
rate began falling; at 128k block-reads-at-a-time or larger, it
drops below
20MB/s (only on buffered SATA).
Try disabling NCQ - see if you've got a drive with the 'NCQ = no
readahead' flaw.
http:
Benjamin Herrenschmidt wrote:
Another thing about the PacDigi core: one has to be very careful
to avoid sequential accesses to sequential PCI locations when
programming the chip -- it cannot handle merged register writes.
So for any group of sequentially laid out registers, the code has
to ensu
Mark Lord wrote:
Robert Hancock wrote:
..
From some of the traces I took previously (posted on LKML as "sata_nv
ADMA controller lockup investigation" way back in Feb 07), what seems
to occur is that when the second command is issued very rapidly
(within less than 20 micros
uot; REVISION "\n");
It's been 7.00alpha2 for god knows how long, so clearly this version
number is not useful..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from
Tejun Heo wrote:
Robert Hancock wrote:
Jeff Garzik wrote:
Tejun Heo wrote:
Thanks a lot for the detailed explanation. Nvidia ppl, any ideas?
FLUSH is used regularly. We really need to fix this.
I reiterate my opinion :) ... We should remove ADMA support from
sata_nv. It's only
Or were
you referring to SATA's general hot/warm plug ability (if my hardware
setup, drive-slots, etc, permitted removability)?
I think they were referring to physically hotplugging the drive. This is
more practical if you have a removable drive caddy, or if the drive is
hooked up through
when the second command is issued very rapidly (within
less than 20 microseconds, or potentially longer) after the previous
command's completion, the ADMA status changes from 0x500 (STOPPED and
IDLE) to 0x400 (just IDLE) as it typically does, but then it sticks
there, no interrupt is
Jeff Garzik wrote:
Tejun Heo wrote:
Thanks a lot for the detailed explanation. Nvidia ppl, any ideas?
FLUSH is used regularly. We really need to fix this.
I reiterate my opinion :) ... We should remove ADMA support from
sata_nv. It's only in a few chips, it's not appearing in any new c
Robert Hancock wrote:
Tejun Heo wrote:
[cc'ing Robert Hancock and NVidia people]
Whole thread can be read from the following URL.
http://thread.gmane.org/gmane.linux.ide/21710
In a nutshell, with ADMA enabled, FLUSH_EXT occasionally times out. I
first suspected faulty disk (realloc
Tejun Heo wrote:
[cc'ing Robert Hancock and NVidia people]
Whole thread can be read from the following URL.
http://thread.gmane.org/gmane.linux.ide/21710
In a nutshell, with ADMA enabled, FLUSH_EXT occasionally times out. I
first suspected faulty disk (reallocation failure on flush
Linda Walsh wrote:
Robert Hancock wrote:
Have you tried using a different block size to see how that effects
the results? There might be some funny interaction there.
There is some interaction with the large block size (but only on the
SATA
disk). Counts were adjusted to keep the
Robert Hancock wrote:
Jeff Garzik wrote:
Robert Hancock wrote:
This fixes some problems with ATAPI devices on nForce4 controllers in
ADMA mode
on systems with memory located above 4GB. We need to delay setting
the 64-bit
DMA mask until the PRD table and padding buffer are allocated so that
ious completion check was removed since it was broken, so this
error shouldn't happen anymore.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line "un
oblem continues to occur repeatedly, you don't
have to worry about it.
Yes, if it didn't recur, was likely just a transient glitch.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To u
t where we decided that one
board always choked on an empty channel. Maybe it's not that and it's
just another case of the same issue where our resetting default timing
values on the controller before calling _GTM would choke the _GTM method?
--
Robert Hancock Saskatoon, SK, Can
in the
ATAPI CDB, or at least we think it is?
You are sure that this drive still works with older kernels using
drivers/ide, and that the hardware didn't break at some point, I assume?
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECT
will actually work (no memory above 4GB)..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of
Tejun Heo wrote:
Robert Hancock wrote:
And you're quite right in your comment that we are often too quick to
blacklist hardware instead of looking into why it really is failing.
ACPI is one of those areas where we often just need to figure out how to
be bug-to-bug compatibile with what Wi
for that
channel are irrelevant..
And you're quite right in your comment that we are often too quick to
blacklist hardware instead of looking into why it really is failing.
ACPI is one of those areas where we often just need to figure out how to
be bug-to-bug compatibile with what Windows is
Jeff Garzik wrote:
Robert Hancock wrote:
This fixes some problems with ATAPI devices on nForce4 controllers in
ADMA mode
on systems with memory located above 4GB. We need to delay setting the
64-bit
DMA mask until the PRD table and padding buffer are allocated so that
they don't
it worked on the original Hitachi disk, but I've upgraded it to a
newer Samsung). I'd say if the drive returns command aborted on one of
these, we should just ignore that command and continue to the next one
without trying to retry or disabling the ACPI support entirely.
--
Robert
ce. Such interfaces are PIO 0 and
* shared IRQ.
*/
I assume that with old IDE this would use ide_cs.c, but I'm drawing a
blank on what modes that supports..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www
ves, but I think there theory is
that it's some other timing problem or some such, given the number of
drives across all makers which are reported to do this. I believe Tejun
is investigating?
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL P
Jeff Garzik wrote:
Robert Hancock wrote:
This fixes some problems with ATAPI devices on nForce4 controllers in
ADMA mode
on systems with memory located above 4GB. We need to delay setting the
64-bit
DMA mask until the PRD table and padding buffer are allocated so that
they don't
graded and thus be worthless in
a raid5 configuration.
Can anyone offer any insight here?
Thank you,
Justin.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send t
likely. For a
level-triggered interrupt, an unhandled interrupt will keep interrupting
forever since nobody knows how to clear it (until we decide to disable
the IRQ entirely).
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http:
attempt to
try and issue NCQ commands with result taskfile requested, since the hardware
doesn't allow this.
Signed-off-by: Robert Hancock <[EMAIL PROTECTED]>
--- linux-2.6.24-rc3-git1edit/drivers/ata/sata_nv.c.before2 2007-11-25
16:28:58.0 -0600
+++ linux-2.6.24-rc3-git1e
Jeff Garzik wrote:
Robert Hancock wrote:
Based on a quick look at sata_mv it appears it sets a 64-bit DMA mask
unconditionally, but for non-ATA_PROT_DMA commands (which includes all
ATAPI), it just falls back to ata_qc_issue_prot which issues via the
legacy SFF interface and can only handle
ounce limit
depending on the connected device, unless there is really a way to issue
ATAPI commands with this EDMA interface, as the TODO list in sata_mv.c
suggests may be possible..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
() if we try
and send result taskfile commands while NCQ commands are still active, since the
hardware doesn't allow this.
Signed-off-by: Robert Hancock <[EMAIL PROTECTED]>
--- linux-2.6.24-rc3-git1/drivers/ata/sata_nv.c 2007-11-20 17:40:09.0
-0600
+++ linux-2.6.24-rc3-git1edit/
ch is needed for ATAPI
devices).
Signed-off-by: Robert Hancock <[EMAIL PROTECTED]>
--- linux-2.6.24-rc3-git1edit/drivers/ata/sata_nv.c.before2 2007-11-22
19:42:28.0 -0600
+++ linux-2.6.24-rc3-git1edit/drivers/ata/sata_nv.c 2007-11-22
19:48:25.0 -0600
@@ -2
Tejun Heo wrote:
Hello, Robert.
Robert Hancock wrote:
This fixes some problems with ATAPI devices on nForce4 controllers in ADMA
mode on systems with memory located above 4GB. We need to delay setting the
64-bit DMA mask until the PRD table and padding buffer are allocated so that
they don&#
Vincent Fortier wrote:
Le mardi 20 novembre 2007 à 18:56 -0600, Robert Hancock a écrit :
This fixes some problems with ATAPI devices on nForce4 controllers in ADMA
mode on systems with memory located above 4GB. We need to delay setting the
64-bit DMA mask until the PRD table and padding buffer
or-handling case where we care if we abort outstanding commands and
the normal case with a RESULT_TF command where we do)..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list
ch is needed for
ATAPI devices). Also, explicitly set a 32-bit DMA mask before allocating the
legacy buffers since setting the DMA mask affects both ports and we need to
ensure the second port's buffers are allocated properly (fixes a problem
with the previous version of this patch).
Signed-off-
Tejun Heo wrote:
Robert Hancock wrote:
Tejun Heo wrote:
Robert Hancock wrote:
This fixes some problems with ATAPI devices on nForce4 controllers in
ADMA mode
on systems with memory located above 4GB. We need to delay setting
the 64-bit
DMA mask until the PRD table and padding buffer are
Tejun Heo wrote:
Jeff Breidenbach wrote:
I read with interest I. Straford's current trials and tribulations
with the Promise SATA300 TX4. Do people have a favorite
alternative to this card that plays well with Linux? I've read the
chipset compatibility list, but am not sure how to boil that
info
Tejun Heo wrote:
Robert Hancock wrote:
This fixes some problems with ATAPI devices on nForce4 controllers in ADMA mode
on systems with memory located above 4GB. We need to delay setting the 64-bit
DMA mask until the PRD table and padding buffer are allocated so that they don't
get allo
ch is needed for ATAPI
devices).
Signed-off-by: Robert Hancock <[EMAIL PROTECTED]>
--- linux-2.6.24-rc1-git10edit/drivers/ata/sata_nv.c.before 2007-11-13
19:04:18.0 -0600
+++ linux-2.6.24-rc1-git10edit/drivers/ata/sata_nv.c2007-11-13
19:02:34.0 -0600
@@ -2
: Robert Hancock <[EMAIL PROTECTED]>
--- linux-2.6.24-rc1-git10/drivers/ata/sata_nv.c2007-11-01
20:01:32.0 -0600
+++ linux-2.6.24-rc1-git10edit/drivers/ata/sata_nv.c2007-11-13
19:01:09.0 -0600
@@ -791,11 +797,13 @@
static void nv_adma_tf_read(struct ata_po
Tejun Heo wrote:
Could be done.. but, I don't want to constrain the ADMA APRD/CPB area in
that way (there are some dual-socket Opteron boxes with this controller,
forcing an allocation below 4GB for this could force a non-optimal node
allocation I think..) To do this I'd have to raise the mask fo
Tejun Heo wrote:
How about always initialize DMA mask to ATA_DMA_MASK regardless of ADMA
mode such that PRD and PAD buffers are always accessible by register
mode and just raising PCI dma mask and queue bounce limit if ADMA mode
is active?
Could be done.. but, I don't want to constrain the ADMA
-by: Robert Hancock <[EMAIL PROTECTED]>
--- linux-2.6.24-rc1-git10/drivers/ata/sata_nv.c2007-11-01
20:01:32.0 -0600
+++ linux-2.6.24-rc1-git10edit/drivers/ata/sata_nv.c2007-11-10
19:57:47.0 -0600
@@ -247,6 +247,7 @@
void __iomem*ctl
reinforce...
sata_nv support and bug fixes are primarily done right now through the
valiant efforts of Robert Hancock (with assists from Alan, Tejun, and
others).
Robert's job is difficult, because he has no hardware documentation[1],
and NVIDIA does not seem to be helping out much with d
I checked
the system log (or whatever it's called) on my notebook and is clean
but I'm not sure it's using NCQ (I don't even know if it'd log
spurious completions somewhere).
Which driver is installed for the SATA controller in Windows, the
chipset-manufacturer-provided AHCI driver
y, and the card indicates DMA support,
which libata tries to use but which doesn't work. It looks like it never
tried falling back to PIO after DMA failed. Seems like a deficiency in
the speed-down logic?
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [E
drives goes into hard reset
failures), .config, lspci -v output.
Are there any chances that using 2.6.23 will improve/fix this? Any other
suggestions?
I would consider it an hardware problem, but since it started at one big
io thingy and is persistent since then I am a bit sceptic.
--
Robert
something seems fishy with this. It seems unlikely that
this many drives from multiple vendors would have the exact same,
relatively obscure problem..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
T
Alan Cox wrote:
On Mon, 29 Oct 2007 22:17:40 -0600
Robert Hancock <[EMAIL PROTECTED]> wrote:
In the sata_nv driver, when running in ADMA mode, we can do 64-bit DMA.
However, when an ATAPI device like a DVD drive is connected, we can't
use ADMA mode, and so we have to abide by the r
potentially be switched out on the port, so the mask might need to be
updated at runtime..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line "unsubscri
ls, but our burn engine is differentiating
IDE and read-good-old-SCSI devices and handles them sometimes in a
different way, so this differenciation is really important for us.
-> How can I detect the real physical device type now?
I don't have a great answer off the top of my head..
-
Len Brown wrote:
On Tuesday 09 October 2007 20:01, Robert Hancock wrote:
Some people with certain Supermicro boards (at least the H8DCE, it
seems) have reported that the sata_nv driver fails to attach to some of
the controllers due to resource conflicts:
https://bugzilla.redhat.com
ct with the ACPI resource
reservations?
I wonder how Windows deals with this, if it even does on these boards?
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line &qu
Andrew Morton wrote:
libata-add-human-readable-error-value-decoding-v3.patch
I think I own this now. Will send to jgarzik then drop it if it doesn't
stick.
Another plug for this one, as the author. I really don't think one can
object to it, and it definitely seems useful.
command aborted if the device
does not support the Power Management feature set." Whereas TEST UNIT
READY is required for SCSI. It seems the SAT authors didn't consider
this case.
I assume we can tell from the identify data that the device doesn't
support power management a
It looks like you have some CONFIG_IDE options enabled in your kernel
configuration that result in drivers/ide trying to drive part or all of
that controller, preventing libata from doing so. Likely the easiest
thing to do is just set CONFIG_IDE=n entirely..
--
Robert Hancock Saskatoon,
Lieven Marchand wrote:
Tejun Heo <[EMAIL PROTECTED]> writes:
It seems klogd clipped some messages. Can you please turn on printk
timestamp, enlarge printk log buffersize and post the result of 'dmesg'
after errors?
[ 34.576963] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 34.
Tejun Heo wrote:
[cc'ing Robert Hancock and quoting the whole message for him]
Lieven Marchand wrote:
Hi,
the following drive
Aug 12 12:26:15 black kernel: Vendor: ATA Model: Maxtor 7H500F0Rev:
HA43
Aug 12 12:26:15 black kernel: Type: Direct-Access
Can someone post an ASL code snippet how ACPI actually access the disk
and in which parts/functions, pls.
Again, it's not believed that this is being done via AML, but via a BIOS
SMM trap on the ACPI sleep state hardware IO port. We have no real
ability to find out what the BIOS is do
Henrique de Moraes Holschuh wrote:
On Tue, 07 Aug 2007, Robert Hancock wrote:
You *do* have to worry about it in any box you turn off daily. Desktop
HDs will croak fast in that scenario, laptop HDs less so, but still too
fast. A very good laptop HD can last about 20k emergency unloads (this
is to blacklist the hell out of that crap and patch their DSDT into
something remotely sane.
I do mean snooping the ACPI methods that *return* a taskset to send to the
driver, and we send that taskset ourselves in libata and libpata(?).
--
Robert Hancock Saskatoon, SK, Canada
To emai
the heads over the landing zone. I don't
think arbitrary power-offs make too much difference on those drives.
(However, these generally aren't rated to handle as many start/stop
cycles, which is why laptop drives generally use load/unload instead.)
--
Robert Hancock Saskatoon, SK
1 - 100 of 190 matches
Mail list logo
