Re: sata scsi suggestion for make menuconfig
(added Cc linux-ide)
Folkert van Heusden wrote:
A popup makes some sense, but I don't know if menuconfig knows how to
do popup warnings... and it needs to be done for all *configs,
not just menuconfig.
Maybe add a new type?
How about
comment Note: 'SCSI disk support' is required for SATA/PATA HDDs!
depends on ATA !BLK_DEV_SD
Yes! Maybe create some status-line at the bottom of the screen in which
these hints scrollby. Like powertop does.
'comment' is already supported by make {menu,x,g}config and AFAIK by
make oldconfig too. It is not effective in make oldconfig though
because it will scroll off the screen quickly.
I am not a friend of 'select', but maybe the following actually helps.
I didn't follow all of this and previous related discussions, so I guess
somebody else suggested something like this before:
# drivers/ata/Kconfig
config ATA
[...]
comment Controller drivers
[...low-level drivers go here...]
comment Storage device drivers
config ATA_SD
tristate SATA/PATA HDD support (via SCSI disk support)
depends on ATA
select BLK_DEV_SD
help
'SCSI disk support' is required to access SATA HDDs. It is
also necessary for parallel ATA (IDE) HDDs if you use the
experimental parallel ATA option.
You can say Y or M here to select SCSI disk support, or you
can do so in the 'SCSI device support' section.
[...ditto for CD/DVD-ROMs, tapes, and generic support...]
--
Stefan Richter
-=-=-=== =--= -=---
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: sata scsi suggestion for make menuconfig
On Sep 8 2007 09:05, Stefan Richter wrote: config ATA [...] comment Controller drivers [...low-level drivers go here...] comment Storage device drivers config ATA_SD tristate SATA/PATA HDD support (via SCSI disk support) depends on ATA select BLK_DEV_SD help 'SCSI disk support' is required to access SATA HDDs. It is also necessary for parallel ATA (IDE) HDDs if you use the experimental parallel ATA option. You can say Y or M here to select SCSI disk support, or you can do so in the 'SCSI device support' section. [...ditto for CD/DVD-ROMs, tapes, and generic support...] And what uses ATA_SD, or is the user supposed to manually enable it? Jan -- - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: libata not working for sis5533
On Sep 2 2007 11:40, Alan Cox wrote: i've been out for a week, but found no notice, did i lost any email or no activity on this issue? I tagged it onto the obscure IDE report pile. It doesn't contain any really useful information and its probably not an IDE layer bug as of itself. But its on the todo list for further investigation and to see if patterns emerge I shall give this a spin too, since I happen to have sis5513. Just booted this fresh ata-enabled system (a matter of mkinitrd). It has not exploded yet. Jan -- - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: sata scsi suggestion for make menuconfig
Jan Engelhardt wrote: On Sep 8 2007 09:05, Stefan Richter wrote: config ATA_SD tristate SATA/PATA HDD support (via SCSI disk support) depends on ATA select BLK_DEV_SD help 'SCSI disk support' is required to access SATA HDDs. It is [...] You can say Y or M here to select SCSI disk support, or you can do so in the 'SCSI device support' section. [...] And what uses ATA_SD, or is the user supposed to manually enable it? It is merely there to produce the prompt which people asked for. CONFIG_ATA_SD (or CONFIG_ATA_BLK_DEV_SD or whatever) won't turn up in any Makefile or source code. Note, I'm not fond of 'select' nor of dummy Kconfig variables. Plus I can personally live very well with the current solution (sd_mod et al are mentioned in the help text at CONFIG_ATA). That's why I posted only the example instead of a complete patch. -- Stefan Richter -=-=-=== =--= -=--- http://arcgraph.de/sr/ - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 2.6.23-rc5] ata_piix: replace spaces with tabs
On Fri, 7 Sep 2007 17:21:03 -0700 Jason Gaston [EMAIL PROTECTED] wrote: This patch removes some incorrect formatting spaces and replaces them with tabs. Signed-off-by: Jason Gaston [EMAIL PROTECTED] Reviewed-by: Alan Cox [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: libata not working for sis5533
On Sep 8 2007 11:38, Patrizio Bassi wrote: Jan Engelhardt wrote: I shall give this a spin too, since I happen to have sis5513. Just booted this fresh ata-enabled system (a matter of mkinitrd). It has not exploded yet. don't you have the irq 14 issue? No, does not seem so. can you post here your .config? http://rafb.net/p/vfTX0966.html Maybe it is solved in 2.6.22.3? (I don't remember what your version was.) Jan -- - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
[1/2] 2.6.23-rc5: known regressions with patches v2
Hi all, Here is a list of some known regressions in 2.6.23-rc5 with patches available. Feel free to add new regressions/remove fixed etc. http://kernelnewbies.org/known_regressions List of Aces NameRegressions fixed since 21-Jun-2007 Adrian Bunk10 Linus Torvalds 6 Andi Kleen 5 Hugh Dickins 5 Trond Myklebust5 Andrew Morton 4 Al Viro3 Alan Stern 3 Alexey Starikovskiy3 Cornelia Huck 3 David S. Miller3 Jens Axboe 3 Stephen Hemminger 3 Tejun Heo 3 Some of these patches are available in -krf (known regressions fixes) tree http://www.stardust.webpages.pl/files/patches/krf/2.6.23-rc5-git1/linux-2.6.23-rc5-git1-krf1.patch.bz2 http://www.stardust.webpages.pl/files/patches/krf/2.6.23-rc5-git1/linux-2.6.23-rc5-git1-krf1.tar.bz2 Unclassified Subject : 8250 claims non existing device blocking IO port References : http://lkml.org/lkml/2007/8/18/20 Last known good : ? Submitter : Andrey Borzenkov [EMAIL PROTECTED] Caused-By : ? Handled-By : Bjorn Helgaas [EMAIL PROTECTED] Patch : http://lkml.org/lkml/2007/8/21/291 Status : patch available Subject : Oops while modprobing phy fixed module References : http://lkml.org/lkml/2007/7/14/63 Last known good : ? Submitter : Gabriel C [EMAIL PROTECTED] Caused-By : ? Handled-By : Satyam Sharma [EMAIL PROTECTED] Vitaly Bordug [EMAIL PROTECTED] Patch1 : http://lkml.org/lkml/2007/7/18/506 Status : patch available FS Subject : NFSv3 server error in LOOKUP after READDIRPLUS Call References : http://bugzilla.kernel.org/show_bug.cgi?id=8966 Last known good : ? Submitter : Peter Kovar [EMAIL PROTECTED] Caused-By : ? Handled-By : Neil Brown [EMAIL PROTECTED] Patch : http://bugzilla.kernel.org/attachment.cgi?id=12689 Status : patch available IDE Subject : linux-2.6.23-rc4 ppc build failure References : http://lkml.org/lkml/2007/8/29/154 Last known good : ? Submitter : Bret Towe [EMAIL PROTECTED] Caused-By : ? Handled-By : Tony Breeds [EMAIL PROTECTED] Patch : http://lkml.org/lkml/2007/8/31/1 Status : patch was suggested Regards, Michal -- LOG http://www.stardust.webpages.pl/log/ - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 2/4] hpt366: MWDMA filter for SATA cards
Hello, I wrote:
Sergei Shtylyov wrote:
The patch was 4/4 of course. :-
Probably I was too esctatic about the code. ;-)
Or rarher me. :-)
The Marvell bridge chips used on HighPoint SATA cards do not seem to
support
the MWDMA modes (at least that caould be seen in their so-called
drivers :-),
so the driver needs to account for this -- to achieve this:
- add mdma_filter() method from the original patch by Bartlomiej
Zolnierkewicz
with his consent, also adding the method callout to ide_rate_filter();
- installed the method for all chips to only return empty mask if a
SATA drive
is detected onHPT372{AN]/374 chips...
Signed-off-by: Sergei Shtylyov [EMAIL PROTECTED]
---
This patch against the current Linus' tree and unfortunately I was
able to only
compile test it since that tree gives MODPOST warning and dies early
on bootup.
Will hopefully try to test if/when I have time... :-)
And it was still the same -- I'd bisected if I had time...
Index: linux-2.6/drivers/ide/pci/hpt366.c
===
--- linux-2.6.orig/drivers/ide/pci/hpt366.c
+++ linux-2.6/drivers/ide/pci/hpt366.c
@@ -1,5 +1,5 @@
/*
- * linux/drivers/ide/pci/hpt366.cVersion 1.12Aug 25, 2007
+ * linux/drivers/ide/pci/hpt366.cVersion 1.13Aug 22, 2007
Errr... and version shuold Aug 02 -- thought I've fixed that. :-/
Hehe, thanks. Those versions turned to be quite PITA a to keep.
MBR, Sergei
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 3/4] ide: make ide_rate_filter() also respect PIO and SW/MW DMA mode masks (take 2)
Once I quothed: Make ide_rate_filter() also respect PIO/SWDMA/MWDMA mode masks. While at it, make the udma_filter() method calls take precedence over using the mode masks. This one not looking to pretty -- I've geve some thought on how to beautify all these switch fallthoughs but haven't got something much better then uour original approach (AKA Occam's razor :-). Signed-off-by: Sergei Shtylyov [EMAIL PROTECTED] Farewell! - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 5/10] hpt366: remove -init_setup
Bartlomiej Zolnierkiewicz wrote:
* Split off hpt{374,371,366}_init() helper from init_setup_hpt{374,371,366}().
* Merge init_setup_{374,372n,371,372a,302,366}() into hpt366_init_one().
While at it:
* Use HPT36x name for HPT366/HPT368 chipsets.
* Add .chip_name to struct hpt_info and use it to set set d-name.
* Convert .max_ultra in struct hpt_info to .udma_mask and use it to set
d-udma_mask.
* Fix hpt302 to use HPT302_ALLOW_ATA133_6 define.
I haven't found that change...
* Change HPT366/HPT374 interrupt fixup message from KERN_WARNING to KERN_INFO.
* Use the second hpt366_chipsets[] entry for HPT37x chipsets using HPT36x PCI
device ID and fix .enablebits/.host_flags for HPT36x hpt366_chipsets[] entry.
Well, if you're ruining my nearly perfect desigh...
* Bump driver version.
... it's worth to label it 1.20. :-)
+ d = hpt366_chipsets[idx];
+
+ d.name = /info-chip_name;
+ d.udma_mask = info-udma_mask;
+
+ pci_set_drvdata(dev, info);
+
+ if (info == hpt36x || info == hpt374)
+ dev2 = pci_get_slot(dev-bus, dev-devfn + 1);
+
+ if (dev2) {
+ int ret;
+
+ pci_set_drvdata(dev2, info);
+
+ if (info == hpt374)
+ hpt374_init(dev, dev2);
+ else {
+ if (hpt36x_init(dev, dev2))
+ d.host_flags |= IDE_HFLAG_BOOTABLE;
+ }
+
+ ret = ide_setup_pci_devices(dev, dev2, d);
+ if (ret 0)
+ pci_dev_put(dev2);
+ return ret;
+ }
- return d.init_setup(dev, d);
+ return ide_setup_pci_device(dev, d);
}
NAK the patch because it's breaking the HPT374 code. Those chips are
*signle* function, and sit in perfect copule (and why I alsway mistype in this
word :o) on 2 DEVSELs behind i960.
MBR, Sergei
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Bug#419482: Kernel 2.6.18 - ALI15X3 driver too optmistic about UDMA
if (m5229_revision = 0x20) {
return 0;
} else if ((m5229_revision 0xC2)
So 0xC1 takes this path
Looking back at the equivalent code in 2.4.27 (the previous kernel
this machine ran), that's rather different:
if (m5229_revision 0xC1) {/* According to ALi */
return 0;
} else if ((m5229_revision 0xC2)
And 0xC1 takes the same path.
So it would seem there has been a regression here - the assumption now
is that versions between 0x20 and 0xC1 can use UDMA fine unless there
is a WDC drive attached, but the old code wouldn't try UDMA at all on
chips older than rev C1.
There are no versions between 0x21 and 0xC0.
I have the machine out and ready to experiment with if any more
details are needed to help solve this problem.
Interesting report as we've had essentially no corruption reports
equivalent to this on common architectures for a long time and the
hardware is in a huge number of PC systems. Also UDMA transfers are CRC
protected by hardware at each end.
That makes me wonder if you have a platform or endian bug, or indeed your
firmware isn't setting up all the chipset as required by the ALi chipset
and BIOS documentation (which unfortunately is NDA)
Alan
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 5/13] ide: add IDE_HFLAG_ERROR_STOPS_FIFO host flag
On Thu, 6 Sep 2007 04:13:56 -0400 Jeff Garzik [EMAIL PROTECTED] wrote: On Wed, Sep 05, 2007 at 11:52:57PM +0200, Bartlomiej Zolnierkiewicz wrote: Add IDE_HFLAG_ERROR_STOPS_FIFO host flag and use it instead of hwif-err_stops_fifo. As a side-effect this change fixes hwif-err_stops_fifo not being restored by ide_hwif_restore(). Signed-off-by: Bartlomiej Zolnierkiewicz [EMAIL PROTECTED] --- drivers/ide/ide-io.c |3 ++- drivers/ide/pci/pdc202xx_new.c |3 +-- drivers/ide/pci/pdc202xx_old.c |8 include/linux/ide.h|3 ++- 4 files changed, 9 insertions(+), 8 deletions(-) Hum, I wonder if libata needs something like this. You'd have to add the drain data on error hack first, right now we will reset in that case (which for one or two devices has another problem in that it won't clear a stuck FIFO) Alan - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 5/13] ide: add IDE_HFLAG_ERROR_STOPS_FIFO host flag
You'd have to add the drain data on error hack first, right now we will reset in that case (which for one or two devices has another problem in that it won't clear a stuck FIFO) Nod. There was nothing ever wrong with Mark's drain patch, I just never saw a solid justification for it outside of root You don't need to be root, any user can do this with the right commands via SG_IO - and it happens on errors occassionally for real. - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: sata scsi suggestion for make menuconfig
Stefan Richter wrote:
(added Cc linux-ide)
Folkert van Heusden wrote:
A popup makes some sense, but I don't know if menuconfig knows how to
do popup warnings... and it needs to be done for all *configs,
not just menuconfig.
Maybe add a new type?
How about
comment Note: 'SCSI disk support' is required for SATA/PATA HDDs!
depends on ATA !BLK_DEV_SD
Yes! Maybe create some status-line at the bottom of the screen in which
these hints scrollby. Like powertop does.
'comment' is already supported by make {menu,x,g}config and AFAIK by
make oldconfig too. It is not effective in make oldconfig though
because it will scroll off the screen quickly.
I am not a friend of 'select', but maybe the following actually helps.
I didn't follow all of this and previous related discussions, so I guess
somebody else suggested something like this before:
The problem with 'select' here is that it will enable BLK_DEV_SD,
but if SCSI is not enabled, it will not become enabled -- i.e.,
select does not follow the dependency chain. So usually the
kernel will not build unless SCSI is enabled by the user.
# drivers/ata/Kconfig
config ATA
[...]
comment Controller drivers
[...low-level drivers go here...]
comment Storage device drivers
config ATA_SD
tristate SATA/PATA HDD support (via SCSI disk support)
depends on ATA
select BLK_DEV_SD
help
'SCSI disk support' is required to access SATA HDDs. It is
also necessary for parallel ATA (IDE) HDDs if you use the
experimental parallel ATA option.
You can say Y or M here to select SCSI disk support, or you
can do so in the 'SCSI device support' section.
[...ditto for CD/DVD-ROMs, tapes, and generic support...]
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 5/13] ide: add IDE_HFLAG_ERROR_STOPS_FIFO host flag
Alan Cox wrote: You'd have to add the drain data on error hack first, right now we will reset in that case (which for one or two devices has another problem in that it won't clear a stuck FIFO) Nod. There was nothing ever wrong with Mark's drain patch, I just never saw a solid justification for it outside of root You don't need to be root, any user can do this with the right commands via SG_IO - and it happens on errors occassionally for real. Which commands? Jeff - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: sata scsi suggestion for make menuconfig
Randy Dunlap wrote: Stefan Richter wrote: I am not a friend of 'select', but maybe the following actually helps. ... The problem with 'select' here is that it will enable BLK_DEV_SD, but if SCSI is not enabled, it will not become enabled -- i.e., select does not follow the dependency chain. So usually the kernel will not build unless SCSI is enabled by the user. ... config ATA_SD tristate SATA/PATA HDD support (via SCSI disk support) depends on ATA select BLK_DEV_SD help 'SCSI disk support' is required to access SATA HDDs. It is ... I checked the dependencies. ATA depends on SCSI (actually, selects SCSI), so all is well. Otherwise I would have added more dependencies to ATA_SD. -- Stefan Richter -=-=-=== =--= -=--- http://arcgraph.de/sr/ - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: sata scsi suggestion for make menuconfig
On Sat, 08 Sep 2007 18:44:46 +0200 Stefan Richter wrote: Randy Dunlap wrote: Stefan Richter wrote: I am not a friend of 'select', but maybe the following actually helps. ... The problem with 'select' here is that it will enable BLK_DEV_SD, but if SCSI is not enabled, it will not become enabled -- i.e., select does not follow the dependency chain. So usually the kernel will not build unless SCSI is enabled by the user. ... config ATA_SD tristate SATA/PATA HDD support (via SCSI disk support) depends on ATA select BLK_DEV_SD help 'SCSI disk support' is required to access SATA HDDs. It is ... I checked the dependencies. ATA depends on SCSI (actually, selects SCSI), so all is well. Otherwise I would have added more dependencies to ATA_SD. Ah, that's good, then. Thanks. --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code *** - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] libata: Add a drivers/ide style DMA disable
Jeff Garzik wrote: FWIW -- as I noted to Alan personally at KS, I would rather drop the pata_ and have it apply to all, PATA or SATA. Having the distinction between sata and pata is also nice tho considering many modern machines mix the two and use the P part for ATAPI, CF kind of stuff. It's all just masks anyway, we can easily do both. As an aside, it would be nice to get the EH in shape where it can pause all ports, so we can finally allow userspace to submit SET FEATURES - XFER MODE and have it handled cleanly and properly. Aye aye sir, bumping up in the to-do list. BTW, I'm currently on airplane and won't be back home in about ten days. PMP patchset is regenerated but it has some problem integrating with the AN support and I need my gears to iron it out, so PMP patches will have to wait a bit more. FWIW, openSUSE 10.3 defaults to libata drivers and contains the PMP patches. It already received quite a bit of testing going through two betas, so I don't think the PMP patches would introduce too many serious regressions for non-PMP users. Thanks. -- tejun - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: CF as IDE on ICH6M using libata
Mark Lord wrote: Tejun Heo wrote: Eddie Hung wrote: However, I think we can conclude that ICH6M (which on the X41, has a SATA-PATA bridge to connect a PATA drive) does not seem to support MWDMA It isn't clear whether the fault is at the driver or the CF device. It's probably the bridge chip -- we've run through that one before just recently (early summer?) on this list. A particular bridge that doesn't work at all with MWDMA. Hmmm... How do we solve this situation? Till now, we've been blacklisting the device IDs but it doesn't work for broken bridges. Maybe we should default to not using MWDMA by default? -- tejun - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: shut down msg
Bruno Buys wrote: Hi, I am using debian sid in an acer notebook, and I do see the spin down msg referred in http://linux-ata.org/shutdown.html. Linux is 2.6.22-1-686 and hd is sata. Am I to worry? Thanks! You better update your shutdown program. Especially so if your drive makes funny sound during shutdown. On shutdown, the drives should make about the same sound as running 'hdparm -y' on it. -- tejun - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [2.6.22.5] irq X: nobody cared but X is successfully used by libata
Paul Rolland wrote: Hello, My machine (an ASUS P5W-DH-Deluxe, Core2, 4Go RAM, 3 SATA and 2IDE) is reporting a : irq 23: nobody cared (try booting with the irqpoll option) together with a Call Trace, but : - irqpoll is present on the command line, - the irq is reported to be used by libata, - the irqpoll option is mandatory if I want _some_ of my SATA disks to be accessible. So, if you don't add the 'irqpoll' option, IO to disks don't work at all after nobody cared message, right? -- tejun - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Fwd: Intel 82801G (ICH7) SATA port reset
Joris wrote:
Hello List,
I have a rather annoying problem.
On an Intel S3000AHLX
(http://www.intel.com/design/servers/boards/s3000ah/index.htm)
motherboard, I can't seem to utilize all SATA interfaces to the
maximum.
The first sata interface frequently resets every few seconds under
heavy IO, the net result being ridiculous slow transfers (attach:
dmesg_random_collection_of_errors)
Running debian unstable and it's version of 2.6.22. System contains a
xeon 3210 and an adaptec scsi controller from which I currently boot.
There is little logic in the symptoms:
* if there is no or light IO, no resets occur.
* it's always the sda port that resets (changing cables or disks
doesn't make a difference).
* only specific combinations of disk-usage on the sata disks (attach:
disk_combinations_causing_reset), just using sda alone does not cause
resets.
* reading is enough, writing is (subjectively) worse. dd
if=/dev/sd{a,b,c,d} of=/dev/null guarantees trouble.
* when the port resets, the disk makes a clearly audible clicking noise
I tried numerous things:
* having the board exchanged with intel for the latest revision
(thanks to my hardware supplier), updating to the latest bios and to a
bios version 6 months old.
* booting with older versions of the linux kernel, 2.6.18 and 2.6.21.
* Using all possible combinations of the bios' matrix/lsi fakeraid and
non-raid modes (always ignoring the raid and using the disks
directly), and enable/disable the one PATA port in the bios.
* asked seagate for a drive firmware update, to no avail.
The only workable solution so far is to leave the first sata interface
unused (remove the disk), which is obviously not a very nice solution.
Any hints or suggestions would be welcome, I'd be more than happy to
try out new things.
things. I'm a bit at a loss on how to proceed at the moment.
Wheee... the link to sda is going up and down (PHY RDY changed) even
when sda itself isn't being accessed. I bet the clunking sound is head
doing emergency unloading. There are two possibilities: 1. the harddisk
is dying or 2. the power which gets fed to the drive sucks (ie.
fluctuates too much when other drives suck more power causing sda to do
emergency unload and PHY link loss.)
You can rule out #1 by exchanging disk positions. You can rule out #2
by connecting the harddrive to a separate PSU or exchanging power
connectors to different disks.
--
tejun
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: HSM violation on bootup, ICH7 + ata_piix 2.6.22
Eamonn Hamilton wrote: Hi, I'm looking ta a Dell SC440 system for a friend, and it's giving HSM violations at startup. The system itself has an ICH7 chipset, with two seagate ST3160812AS drives attached along with a single ST3400832AS, running kernel 2.6.22 and the ata_piix driver. I'm guessing this isn't good :( Anybody gt any suggestions? The violations are : ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata1.00: cmd b0/d2:f1:00:4f:c2/00:00:00:00:00/00 tag 0 cdb 0x0 data 123392 in res 50/00:f1:00:4f:c2/00:00:00:00:00/00 Emask 0x202 (HSM violation) Please disable or upgrade smartd. -- tejun - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: a disk timeout and a disk state
Raz wrote: Jeff Hello We have in our machines several sata (mostly maxtor-segate) disks in an array. These disks generate too many ata-io errors at clients sites. From raid1 code I have learned that a re-write sometimes fixes a disk. Question: Why ? Question: Does it always work ? Question: Does rewriting a slow sector also reduces a disk error rate, does it make any sense ? You need to post much more information to get anyone on the list interested. * lspci -nn * boot log (/var/log/boot.msg on some distros or the result of dmesg after boot) * kernel error messages (dmesg after errors) -- tejun - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] Asynchronous scan support for libata
Matthew Wilcox wrote: Last December, I posted this: http://lwn.net/Articles/213635/ Here's an updated version. It shaves 5 seconds off boot time on my configuration (qla2xxx, emulex, two ata_piix, dual fusion), but could save more or less on other setups. I think I can remove the 'sync' argument and code from ata_scsi_scan_host() now, but wanted to send out this update today. --- Some of the drivers (AHCI was mentioned to me as a culprit) take a long time to discover all the devices attached to them. Even for ones which are relatively quick, if you put a lot of them in a machine, it will take a long time in aggregate. This can be fixed by adding support for asynchronous scsi scans, which causes the time-consuming portions of initialisation to take place in threads. Signed-off-by: Matthew Wilcox [EMAIL PROTECTED] I think it's generally okay although it would need to spend quite some time in -mm and we'll need to exclude several drivers which require host-wide silence for mode programming (the current code is buggy but sequential probing hides it pretty well) till host-wide exclusion is implemented. Thanks. -- tejun - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] Remove sync waiting code from libata
Matthew Wilcox wrote: By using the scsi async probing code, we can remove the 'sync' argument from ata_scsi_scan_host(): Hmmm... How so? @sync is there to keep device numbering stable even when SCSI scan fails due to allocation failure. I don't see how async probing changes that. -- tejun - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] Remove sync waiting code from libata
On Sat, Sep 08, 2007 at 05:14:21PM +0900, Tejun Heo wrote: Matthew Wilcox wrote: By using the scsi async probing code, we can remove the 'sync' argument from ata_scsi_scan_host(): Hmmm... How so? @sync is there to keep device numbering stable even when SCSI scan fails due to allocation failure. I don't see how async probing changes that. async probing also keeps device numbering stable. As long as the device responds within ten seconds (and the current code has half a second as the timeout), it'll get the same number it would have had, even though other hosts have successfully completed their probes during that time. -- Intel are signing my paycheques ... these opinions are still mine Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step. - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] Asynchronous scan support for libata
On Sat, Sep 08, 2007 at 05:10:27PM +0900, Tejun Heo wrote: I think it's generally okay although it would need to spend quite some time in -mm and we'll need to exclude several drivers which require host-wide silence for mode programming (the current code is buggy but sequential probing hides it pretty well) till host-wide exclusion is implemented. Can you tell me a bit more about these drivers? Would it be possible to convert them to one host/many channels, which would give us the exclusion we want? -- Intel are signing my paycheques ... these opinions are still mine Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step. - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] Asynchronous scan support for libata
Matthew Wilcox wrote: Can you tell me a bit more about these drivers? Would it be possible to convert them to one host/many channels, which would give us the exclusion we want? As a tangent, I would prefer a more natural representation than current, where there is a 1-1 correspondence between scsi_host and ATA controller instance, and a 1-1 correspondence between SCSI channels and ATA ports. Alas _any_ change to the current setup requires special attention, because it is tied intimately into master/slave exclusion and scheduling. I occasionally ponder what it would take to create an intelligent request scheduling framework that takes into account inflexible hardware bottlenecks like simplex (one command per controller, $n ports, $m devices), master/slave (one command port, $m devices), NCQ ($n commands per port, $m devices), port multipliers with their own bottlenecks, etc. I see a lot of common code patterns in this area, but we are all sorta doing our own thing at a low level in drivers, because of subtle (and not-so-subtle) differences in hardware queueing support. Jeff, thinking out loud - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] Remove sync waiting code from libata
Matthew Wilcox wrote: On Sat, Sep 08, 2007 at 05:14:21PM +0900, Tejun Heo wrote: Matthew Wilcox wrote: By using the scsi async probing code, we can remove the 'sync' argument from ata_scsi_scan_host(): Hmmm... How so? @sync is there to keep device numbering stable even when SCSI scan fails due to allocation failure. I don't see how async probing changes that. async probing also keeps device numbering stable. As long as the device responds within ten seconds (and the current code has half a second as the timeout), it'll get the same number it would have had, even though other hosts have successfully completed their probes during that time. The @sync parameter is to work around GFP_ATOMIC allocation in SCSI scan code. A libata SCSI host can have upto 15 devices with PMP and with multiple devices allocation failure is not so rare, probably because libata SCSI scanning is done back-to-back in rapid succession. The proper fix is probably to make SCSI scanning code not use GFP_ATOMIC (there doesn't seem to be any reason to) but @sync is the bandaid till that happens. Thanks. -- tejun - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
What's in libata-dev.git?
The following is the current contents of git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git (recently rebased) The 'upstream' branch is what I will push upstream for 2.6.24, once the merge window opens. I also have a pile in my inbox I need to go over, while I was away at conference. At least one fix still pending for 2.6.23-rc that needs to go up. list of branches ALL contents of: upstream, sil680-mmio, new-eh * master mv-ahci-pata rough draft Marvell 6141 PATA support mv-ncqrough draft sata_mv NCQ support new-ehnew EH conversion for sata_qstor, sata_sx4 pmask proto_mask implementation sii-lbt SiI 311x large block transfer (LBT) support sil680-mmio pata_sil680 MMIO support from benh upstream queued for 2.6.24 Branch 'upstream' (queued for 2.6.24) Alan Cox (11): libata: Correct IORDY handling libata-core: Document some limits/assumptions about ID_ATA libata: Note that our cache flush code needs fixing up pata_cmd64x: Set up MWDMA modes properly [libata] add ACPI cable detect API libata pata_amd: ACPI checks for 80wire cable libata pata_via: ACPI checks for 80wire cable libata: Switch most of the remaining SFF drivers to ata_sff_port_start libata-portmap: Remove unused definitions libata: Spot bridge chips libata: Strict checking for identify reporting Albert Lee (2): libata: move ata_altstatus() to pio data xfer functions libata: pata_pdc2027x PLL detection minor cleanup Andrew Morton (1): libata-add-irq_flags-to-struct-pata_platform_info-fix Christian Lamparter (1): ata_piix: disallow UDMA 133 on ICH5 ICH7 Jeff Garzik (4): [libata] pdc_adma: convert to new exception handling (EH) framework [libata] Remove -irq_ack() hook, and ata_dummy_irq_on() [libata] Remove -port_disable() hook [libata] ata_piix: Use more-robust form of array initialization Kristen Carlson Accardi (3): [libata] check for SATA async notify support [libata] ahci: send event when AN received ahci: Store interrupt value Kristoffer Nyborg Gregertsen (1): AVR32 PATA driver Mark Lord (1): libata: add support for ATA_16 on ATAPI Sonic Zhang (1): libata driver for bf548 on chip ATAPI controller. Tejun Heo (18): libata-link: introduce ata_link libata-link: implement and use link/device iterators libata-link: linkify PHY-related functions libata-link: linkify EH action helpers libata-link: linkify reset libata-link: linkify config/EH related functions libata-link: make two port flags HRST_TO_RESUME and SKIP_D2H_BSY link flags libata-link: separate out link initialization functions libata-link: implement ata_link_abort() libata-link: add PMP links libata-link: update ata_scsi_error() to handle PMP links libata-link: update EH to deal with PMP links libata-link: update hotplug to handle PMP links libata-link: update Power Management to handle PMP links libata: use ata_port_printk() in ata_wait_idle() libata: add printf format attribute to ehi desc functions libata: implement and use ata_port_desc() to report port configuration libata: move EH repeat reporting into ata_eh_report() drivers/ata/Kconfig | 25 drivers/ata/Makefile |2 drivers/ata/ahci.c | 109 +- drivers/ata/ata_generic.c| 16 drivers/ata/ata_piix.c | 52 - drivers/ata/libata-acpi.c| 63 + drivers/ata/libata-core.c| 669 -- drivers/ata/libata-eh.c | 647 + drivers/ata/libata-scsi.c| 258 +++-- drivers/ata/libata-sff.c | 69 - drivers/ata/libata.h |7 drivers/ata/pata_ali.c | 17 drivers/ata/pata_amd.c | 43 drivers/ata/pata_artop.c | 20 drivers/ata/pata_at32.c | 441 + drivers/ata/pata_atiixp.c|9 drivers/ata/pata_bf54x.c | 1627 +++ drivers/ata/pata_cmd640.c|4 drivers/ata/pata_cmd64x.c| 43 drivers/ata/pata_cs5520.c| 27 drivers/ata/pata_cs5530.c|4 drivers/ata/pata_cs5535.c|4 drivers/ata/pata_cypress.c |4 drivers/ata/pata_efar.c | 11 drivers/ata/pata_hpt366.c|4 drivers/ata/pata_hpt37x.c| 28 drivers/ata/pata_hpt3x2n.c | 11 drivers/ata/pata_hpt3x3.c| 10 drivers/ata/pata_icside.c| 39 drivers/ata/pata_isapnp.c|8 drivers/ata/pata_it8213.c| 11
Re: [PATCH] Asynchronous scan support for libata
Matthew Wilcox wrote: On Sat, Sep 08, 2007 at 05:10:27PM +0900, Tejun Heo wrote: I think it's generally okay although it would need to spend quite some time in -mm and we'll need to exclude several drivers which require host-wide silence for mode programming (the current code is buggy but sequential probing hides it pretty well) till host-wide exclusion is implemented. Can you tell me a bit more about these drivers? Would it be possible to convert them to one host/many channels, which would give us the exclusion we want? IIRC, sata_promise is of this type and there probably are a few old PATA ones. Ports on the host are mostly independent. There's no need for cross-port synchronization for most of the time but configuring transfer mode requires host-wide quiescence. Currently, the planned way to fix the problem is to implement host-wide exclusion mechanism in the error handler (summon EH of all other threads and wait till all of them are parked) and it's on top of the TODO list, so I don't think it will take too long. Thanks. -- tejun - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: drivers/ata/ahci.c driver questions / recommendations
several of the various AHCI / Sata II controllers on PCI express card and build up a test suite. Any pointers or recommendations would be greatly appreciated. I would suggest taking that path as quite a few AHCI controllers aren't quite AHCI compliant. Alan - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: sata scsi suggestion for make menuconfig
Randy Dunlap wrote: On Sat, 08 Sep 2007 18:44:46 +0200 Stefan Richter wrote: Randy Dunlap wrote: The problem with 'select' here is that it will enable BLK_DEV_SD, but if SCSI is not enabled, it will not become enabled -- i.e., select does not follow the dependency chain. So usually the kernel will not build unless SCSI is enabled by the user. ... I checked the dependencies. ATA depends on SCSI (actually, selects SCSI), so all is well. Otherwise I would have added more dependencies to ATA_SD. Ah, that's good, then. Not completely though. Whenever a 'select' is inserted into the dependency graph, the whole thing becomes more fragile WRT future changes. -- Stefan Richter -=-=-=== =--= -=--- http://arcgraph.de/sr/ - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] Asynchronous scan support for libata
Jeff Garzik wrote: Matthew Wilcox wrote: Can you tell me a bit more about these drivers? Would it be possible to convert them to one host/many channels, which would give us the exclusion we want? As a tangent, I would prefer a more natural representation than current, where there is a 1-1 correspondence between scsi_host and ATA controller instance, and a 1-1 correspondence between SCSI channels and ATA ports. Currently, the biggest problem is the EH thread. SCSI EH is per host and entering entering SCSI EH means host-wide quiescence. Alas _any_ change to the current setup requires special attention, because it is tied intimately into master/slave exclusion and scheduling. I occasionally ponder what it would take to create an intelligent request scheduling framework that takes into account inflexible hardware bottlenecks like simplex (one command per controller, $n ports, $m devices), master/slave (one command port, $m devices), NCQ ($n commands per port, $m devices), port multipliers with their own bottlenecks, etc. I see a lot of common code patterns in this area, but we are all sorta doing our own thing at a low level in drivers, because of subtle (and not-so-subtle) differences in hardware queueing support. Amen. It's slow but things are being shifted from SCSI to block. EH can be shifted to block and made per-queue. Mapping the current SCSI EH architecture to it will take some work but after that changing ATA host - SCSI host mapping shouldn't be too difficult. Thanks. -- tejun - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] Remove sync waiting code from libata
Alan Cox wrote: async probing also keeps device numbering stable. As long as the device responds within ten seconds (and the current code has half a second as the timeout), it'll get the same number it would have had, even though other hosts have successfully completed their probes during that time. The usual probe time for a device which is spun down is nearer 30 seconds. libata probing is done differently tho. It goes like... 1. libata EH probes all hardware. Things can take quite long here but SCSI isn't really involved. 2. After libata EH is finished, SCSI host scan is invoked. It doesn't do much. When SCSI probing command reaches libata-scsi, it just fakes the replies from the information gathered in #1 - No actual ATA reset or command is issued. If there are multiple devices on a host (ATA port), this rapid probing makes SCSI host scan code fail GFP_ATOMIC allocation from time to time. This is why the @sync hack was used. Thanks. -- tejun - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Port Multiplier Patch 2.6.22.1 on Alpha
Tom Evans wrote: I decided to put the Norco 4618 card into the first PCI slot of my DS20. It and the PMP support seem to like that location much better - I'm successfully creating an array at the moment. The system still responds, but accessing currently running filesystems (another array and the local scsi boot disk) seems to freeze for 20-30 seconds. Does kernel complain anything during the freeze? I was able to move the graphics card to another slot (which for a period in the past was also limited to the first PCI slot). Maybe this will make sense to some folks out there - thanks! To me, not much yet. :-( -- tejun - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Port Multiplier Patch 2.6.22.1 on Alpha
No real performance change, but the # of unaligned kernel goes from ~14 to zero on my system. It's really just cosmetic I believe. ...tom Tejun Heo wrote: Tom Evans wrote: In sil24_config_port, the writel's for /* zero error counters */ should be writew's - they are 16bit control registers. Only PORT_DECODE_ERR_THRESH and PORT_CRC_ERR_THRESH appear to be unaligned, but why risk a stl when a stw (on platforms that support it) can be used. That part of the code was taken verbatim from the Silicon Image sample driver, which I'm sure have been tested only on x86s. Those error threshold feature isn't really used and using writew's should be fine. Do things work better after changing to writew's? - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Port Multiplier Patch 2.6.22.1 on Alpha
Tejun Heo wrote: Does kernel complain anything during the freeze? I do not see any console or syslog messages at the time - perhaps I do not have a debug level set appropriately? Also, as an aside, I noticed that the device scan on the remote array shows this device: Sep 8 00:15:12 chronictown kernel: [4194044.507921] ata4.05: ATA-6: Config Disk, PLS12052, max UDMA/133 Sep 8 00:15:12 chronictown kernel: [4194044.507921] ata4.05: 640 sectors, multi 1: LBA Sep 8 00:15:12 chronictown kernel: [4194044.507921] ata4.05: device is on DMA blacklist, disabling DMA Sep 8 00:15:12 chronictown kernel: [4194044.507921] ata4.05: configured for PIO4 I couldn't find any reference - is this firmware for the PMP or something like that? Thanks, ...tom - To unsubscribe from this list: send the line unsubscribe linux-ide in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
