Bill Davidsen wrote:
> Jan Engelhardt wrote:
>> On Dec 1 2007 06:26, Justin Piszcz wrote:
>>> I ran the following:
>>>
>>> dd if=/dev/zero of=/dev/sdc
>>> dd if=/dev/zero of=/dev/sdd
>>> dd if=/dev/zero of=/dev/sde
>>>
>>> (as it is always a very good idea to do this with any new disk)
>>
>> Why wo
Justin Piszcz wrote:
> The badblocks did not do anything; however, when I built a software raid
> 5 and the performed a dd:
>
> /usr/bin/time dd if=/dev/zero of=fill_disk bs=1M
>
> [42332.936615] ata5.00: exception Emask 0x2 SAct 0x7000 SErr 0x0 action
> 0x2 frozen
> [42332.936706] ata5.00: spuri
Maciej Rutecki wrote:
> 2007/12/5, Jeff Garzik <[EMAIL PROTECTED]>:
>
>> _If_ libata is built into the kernel, and not a kernel module, then you
>> can supply "libata.noacpi=1" on the kernel command line. I don't think
>> that works with modules.
JFYI: fix for this and other ACPI issues is being
Alan Cox wrote:
> +/**
> + * sl82c105_qc_defer - implement serialization
> + * @qc: command
> + *
> + * We must issue one command per host not per channel because
> + * of the reset bug.
> + *
> + * Q: is the scsi host lock sufficient ?
> + */
> +
> +static int sl82c105_qc_def
(cc'ing Bartlomiej)
Hello,
[EMAIL PROTECTED] wrote:
> Dec 6 11:58:23 titanium kernel: WARNING: at kernel/irq/manage.c:158
> enable_irq()
> Dec 6 11:58:23 titanium kernel: [] enable_irq+0x6e/0xa2
> Dec 6 11:58:23 titanium kernel: [] probe_hwif+0x6d8/0x7c7
> [ide_core]
> Dec 6 11:58:23 titan
Chuck Ebbert wrote:
> On 12/05/2007 06:53 PM, Chuck Ebbert wrote:
>> With kernel 2.6.23 on an Acer 7220 notebook using nVidia MCP67 SATA,
>> hard drives are only detected after first booting from a CD.
>>
>> Boot from hard drive No drives detected
>>
>> Boot live CD Detected
>>
>>
Andrew Morton wrote:
> (argh, shit, resent. Please don't massage the cc list. Do reply-to-all)
>
> On Thu, 6 Dec 2007 01:33:16 + (UTC)
> Parag Warudkar <[EMAIL PROTECTED]> wrote:
>
>> Tom Lanyon gmail.com> writes:
>>
>>> scsi4: ahci
>>> ata5: SATA link up at 1.5 Gbps (SStatus 113 SControl
[EMAIL PROTECTED] wrote:
> Hello !
>
> on my old fujitsu-siemens lifebook, booting is at least 20 seconds slower as
> before.
>
> on ata_piix init i can see 2 longer delays of ~10 seconds each, which didn`t
> happen before.
>
> i`m using SuSE kernel of the day from
> http://ftp.suse.com/pub/p
Hello.
Bartlomiej Zolnierkiewicz wrote:
---
Many PIO modes at 55/66 MHz (as well as MDDMA modes at all clocks) are also
underclocked but I decided not to touch them, at least for the time being.
The patch is against the Linus' tree, with PIO0 setup time correct this time...
Since it is again
2007/11/21, noah <[EMAIL PROTECTED]>:
> 2007/11/21, Alan Cox <[EMAIL PROTECTED]>:
> > > I've had other freezes before but this was the first time I was able
> > > to see what was actually going on.
> > > IRQ 21 appears to be shared between sata_nv and ethernet.
> > >
> > > Does this mean my hardwar
Bartlomiej Zolnierkiewicz wrote:
Since PIO autotuning is now done always, there's no need anymore to program
the taskfile timings also on DMA modes, so chenge the IDE timing register
masks accordingly, "inverting the polarity" of the masks while at it...
Signed-off-by: Sergei Shtylyov <[EMAIL
Bartlomiej Zolnierkiewicz wrote:
set_io_32bit() (ide_procset_t function) can race against running
PIO transfers. Fix it by using ide_spin_wait_hwgroup().
Signed-off-by: Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]>
Acked-by: Sergei Shtylyov <[EMAIL PROTECTED]>
MBR, Sergei
-
To unsubscribe
Bartlomiej Zolnierkiewicz wrote:
Check for DRQ bit being cleared on the final status check.
Signed-off-by: Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]>
Acked-by: Sergei Shtylyov <[EMAIL PROTECTED]>
MBR, Sergei
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the b
Bartlomiej Zolnierkiewicz wrote:
ide_dump_status() may set HOB bit before ide_end_drive_cmd() is called.
Signed-off-by: Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]>
Acked-by: Sergei Shtylyov <[EMAIL PROTECTED]>
MBR, Sergei
-
To unsubscribe from this list: send the line "unsubscribe linux-
Bartlomiej Zolnierkiewicz wrote:
Signed-off-by: Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]>
Acked-by: Sergei Shtylyov <[EMAIL PROTECTED]>
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
Bartlomiej Zolnierkiewicz wrote:
Signed-off-by: Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]>
Acked-by: Sergei Shtylyov <[EMAIL PROTECTED]>
Index: b/drivers/ide/ide-taskfile.c
===
--- a/drivers/ide/ide-taskfile.c
+++ b/drivers/i
Bartlomiej Zolnierkiewicz wrote:
* Initialize rq->cmd_type in ide_wait_cmd(), ide_cmd_ioctl() and
set_pio_mode() (other callers were aleady over-riding rq->cmd_type).
* Remove no longer needed rq->cmd_type setup from ide_init_drive_cmd().
Signed-off-by: Bartlomiej Zolnierkiewicz <[EMAIL
Bartlomiej Zolnierkiewicz wrote:
Signed-off-by: Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]>
Acked-by: Sergei Shtylyov <[EMAIL PROTECTED]>
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
Bartlomiej Zolnierkiewicz wrote:
Don't enable local IRQs for PIO-in protocol in driver_cmd_intr().
While at it:
* Remove redundant rq->cmd_type check.
* Read status register after enabling local IRQs for no-data protocol.
Signed-off-by: Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]>
Business Kid wrote:
> Yeah, dd will do that but I'm not too sure whether that would be
> helpful.
>
> That's a bit rough! Hexedit with style? :-).
:-)
> The drive is triggering all sorts of errors. Can you post the
> result of 'smartctl -a /dev/sdX' where sdX is the offending
Bartlomiej Zolnierkiewicz wrote:
Don't check for READY_STAT bit being set for PIO-in protocol (makes the
final status check in drive_cmd_intr() match the one in task_in_intr()).
Also fix function name reported by ide_error() call while at it.
Signed-off-by: Bartlomiej Zolnierkiewicz <[EMAI
Kjartan Maraas wrote:
> ma., 10.12.2007 kl. 10.03 +0900, skrev Tejun Heo:
>> Kjartan Maraas wrote:
Hmmm... Ah.. okay. Wrongly splitted patch. Can you please do it one
more time?
>>> Attached.
>> Alright, it works now but it seems both dmesgs are from no-filter patch.
>> I'm pretty
ma., 10.12.2007 kl. 10.03 +0900, skrev Tejun Heo:
> Kjartan Maraas wrote:
> >> Hmmm... Ah.. okay. Wrongly splitted patch. Can you please do it one
> >> more time?
> >>
> > Attached.
>
> Alright, it works now but it seems both dmesgs are from no-filter patch.
> I'm pretty sure it works too beca
On Mon, Dec 10 2007, Tejun Heo wrote:
> There's one thing we can do to improve the situation tho. Several
> drives including raptors and 7200.11s suffer serious performance hit if
> sequential transfer is performed by multiple NCQ commands. My 7200.11
> can do > 100MB/s if non-NCQ command is used
On Mon, 2007-12-10 at 16:33 +0900, Tejun Heo wrote:
> There's one thing we can do to improve the situation tho. Several
> drives including raptors and 7200.11s suffer serious performance hit if
> sequential transfer is performed by multiple NCQ commands. My 7200.11
> can do > 100MB/s if non-NCQ c
Tejun Heo wrote:
..
Mark, how is marvell PMP support going?
..
It will be good once it happens -- the newer 6042/7042 chips support
full FIS-based switching, as well as command-based switching,
with large queues and all of the trimmings.
Currently stuck in legalese, though.
Cheers
-
To unsu
Jens Axboe wrote:
On Mon, Dec 10 2007, Tejun Heo wrote:
There's one thing we can do to improve the situation tho. Several
drives including raptors and 7200.11s suffer serious performance hit if
sequential transfer is performed by multiple NCQ commands. My 7200.11
can do > 100MB/s if non-NCQ co
Tejun Heo wrote:
..
NCQ is not more advanced than SCSI TCQ. NCQ is "native" and "advanced"
compared to old IDE style bus-releasing queueing support which was one
ugly beast which no one really supported well. The only example I can
remember which actually worked was first gen raptors paired wit
Linus Torvalds wrote:
On Sun, 9 Dec 2007, Robert Hancock wrote:
The obvious suspect with a filesystem problem would be the disk
controller driver, AHCI here. However, the controller appears to set the
flag to indicate that it supports 64-bit DMA, so it should be fine,
unless it lies of course
I'll try - it will take me a little while to get back to this - had to
reconfigure my target for a different test...more later~!
Tom
-Original Message-
From: Mark Lord [mailto:[EMAIL PROTECTED]
Sent: Monday, December 10, 2007 11:44 AM
To: Morrison, Tom
Cc: Jeff Garzik; linux-ide@vger.ke
Mark Lord schrieb:
AHCI is a pretty well tested driver, but 99%+ of all testers still
tend to have less than 4GB of memory. So I do *not* believe that the
highmem bits are all that well tested at all.
Can somebody who knows the driver send Marco a test-patch to just
limit DMA to the low 32 bi
Jens Axboe schrieb:
Hello Jens,
Thanks for help. I just applied the patch. Unfortunately it doesn't work.
Can you try and additionally boot with iommu=off as a boot parameter?
Yes. This is the end of getting any sata devices. See screenshots for
errors. It continued untill ata4. At the end no
On Mon, Dec 10 2007, Marco Gatti wrote:
> Jens Axboe schrieb:
> Hello Jens,
> Thanks for help. I just applied the patch. Unfortunately it doesn't
> work.
> >>>Can you try and additionally boot with iommu=off as a boot parameter?
> >>>
> >>Yes. This is the end of getting any sata device
On Mon, 10 Dec 2007, Marco Gatti wrote:
>
> I didn't compile completly.
>
> drivers/scsi/scsi_lib.c:1565:1: error: unterminated #else
Heh. That #else should be an #endif, of course.
It is a bit strange that it still tries to do IO to high memory. Either
the whole "64 bit capability" thing in
Business.kid using this address because gmail keeps bouncing linux-ide
for silly reasons.
On Mon, 2007-12-10 at 22:39 +0900, Tejun Heo wrote:
>
> > The drive is triggering all sorts of errors. Can you post the
> > result of 'smartctl -a /dev/sdX' where sdX is the offending drive. Also
Hi Boaz,
On Sun, 09 Dec 2007 11:43:31 +0200, Boaz Harrosh <[EMAIL PROTECTED]> wrote:
> >>> Index: 2.6.24-rc3-mm2/drivers/scsi/scsi_lib.c
>
> >> No I don't like it. The only client left for blk_end_request_callback()
> >> is bidi,
> >
> > ide-cd (cdrom_newpc_intr) is another client.
> > So I can'
On Mon, 10 Dec 2007 05:55:20 -0800 (PST)
[EMAIL PROTECTED] wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=9533
Another box-killing regression to track, please. Either ATA or ACPI.
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to [EMAIL PROTE
On Mon, 10 Dec 2007 12:52:43 -0800
Andrew Morton <[EMAIL PROTECTED]> wrote:
> On Mon, 10 Dec 2007 05:55:20 -0800 (PST)
> [EMAIL PROTECTED] wrote:
>
> > http://bugzilla.kernel.org/show_bug.cgi?id=9533
>
> Another box-killing regression to track, please. Either ATA or ACPI.
er, no, not box-killi
On 12/10/2007 03:52 PM, Andrew Morton wrote:
> On Mon, 10 Dec 2007 05:55:20 -0800 (PST)
> [EMAIL PROTECTED] wrote:
>
>> http://bugzilla.kernel.org/show_bug.cgi?id=9533
>
> Another box-killing regression to track, please. Either ATA or ACPI.
> -
> To unsubscribe from this list: send the line "uns
Linus Torvalds wrote:
On Mon, 10 Dec 2007, Marco Gatti wrote:
I didn't compile completly.
drivers/scsi/scsi_lib.c:1565:1: error: unterminated #else
Heh. That #else should be an #endif, of course.
It is a bit strange that it still tries to do IO to high memory. Either
the whole "64 bit capa
(linux-ide cc'ed)
trash can wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have tolerated this problem for a year and do not post to this list in
haste. I have posted on forums and searched the community over the past
year. I have looked at the list archive on gossamer-threads.com for
s
Hello,
For Junk Mail wrote:
>> I'm not aware of any specific issues with via + Segate drives. Have
>> pointers?
>
> Remember the infamous via 'hardware error' which via insist is a
> configuration error from the MPV3 chipset? This 8235 southbridge is the
> same southbridge basically, shrunk down
Hi all,
I have a SATA drive in a motherboard with an ATI SB600 chipset that
until now worked just fine.
The disk seems fine but after a while it start making noises (like
spinning up) and the computer freezes during 2 or 3 seconds. I think my
SATA drive is broken, or maybe the motherboard. Thi
43 matches
Mail list logo