Hello,
1. Has it ever worked with the previous kernels?
I can't tell, this machine is new, and it never booted something that
was not a 2.6.20 or 2.6.21.
2. If you connect a harddisk to pata_jmicron, does it work?
3. Does applying the attached patch fix your problem?
Will do these two
Hello,
Your drive has some issues with NCQ and is scheduled to be blacklisted
such that it isn't enabled. libata used to ignore the
condition but now
considers it NCQ protocol violation and fails all pending commands.
OK, do you need an hdparm report to fully identify the disk ?
libata
Helo Tejun!
On Mon, Mar 05, 2007 at 01:10:10PM +0900, Tejun Heo wrote:
Philipp Matthias Hahn wrote:
As reported by John Williams and others like in
http://www.mail-archive.com/linux-ide@vger.kernel.org/msg03088.html
I too have a problem with 2.6.20.1 using ata_piix not detecting the
On 3/5/07, Tejun Heo [EMAIL PROTECTED] wrote:
Dale Blount wrote:
This will probably included in the next -stable iteration. Thanks.
--
tejun
I can confirm that sata_sil is working great under 2.6.21-rc1.
I have an onboard Silicon Image SATA RAID controller and a PCI Add-on
card, also
Eyal Lebedinsky wrote:
It is in the original thread on linux-raid, but here it is for this list.
This is the full dmesg. There were only MARKs in between.
I run a raid 'check' every Friday (cron). The last one reported some parity
errors.
*** last week check start:
[927080.617744] md:
Stephen Clark wrote:
Bill Davidsen wrote:
Stephen Clark wrote:
Bill Davidsen wrote:
Alan Cox wrote:
it seems broken to manipulate xfer_mask after returning from the
driver's -mode_filter hook.
this patch is more than just a speed-limited warning printk, afaics
I
Paul Rolland wrote:
Hello,
Your drive has some issues with NCQ and is scheduled to be blacklisted
such that it isn't enabled. libata used to ignore the
condition but now
considers it NCQ protocol violation and fails all pending commands.
OK, do you need an hdparm report to fully
Philipp Matthias Hahn wrote:
On Mon, Mar 05, 2007 at 01:10:10PM +0900, Tejun Heo wrote:
Philipp Matthias Hahn wrote:
As reported by John Williams and others like in
http://www.mail-archive.com/linux-ide@vger.kernel.org/msg03088.html
I too have a problem with 2.6.20.1 using ata_piix not
Hello, I wrote:
official == same as in the docs and vendor driver :-)
Erm, those look a bit doubtful...
I believe that they are correct - please see explanations below.
Yeah, sorry about that. Only SWDMA timings are suspicious.
Hm, too early to say sorry. I was
Tejun Heo a écrit :
Hi,
No, your drive isn't blacklisted yet. NCQ is still being enabled.
Sorry, I wasn't very clear: The NCQ blacklist patch is not in
the 2.6.21-rc tree, just in -mm. I tried a 2.6.21-rc2-mm1 and
the drive is blacklisted. The logs I pasted were from 2.6.20 and
2.6.21-rc1.
On Monday 05 March 2007, Sergei Shtylyov wrote:
Hello, I wrote:
official == same as in the docs and vendor driver :-)
Erm, those look a bit doubtful...
I believe that they are correct - please see explanations below.
Yeah, sorry about that. Only SWDMA timings are
Attached dmesg. config.gz. here's the OOPS part.
ata_piix :00:1f.2: version 2.10
ata_piix :00:1f.2: MAP [ P0 P2 P1 P3 ]
ACPI: PCI Interrupt :00:1f.2[B] - GSI 19 (level, low) - IRQ 19
ata: 0x1F0 IDE port busy
ata: conflict with ide0
BUG: at drivers/pci/pci.c:846 pcim_pin_device()
On Sun, 2007-02-25 at 18:34 -0500, Jeff Garzik wrote:
Just got sata_mv working under the new EH, on my 6041.
It probes and talks to disks just fine (chip doesn't support ATAPI),
and hotplug actually has a chance of working.
The 'mv-eh' branch of
Dave Dillow wrote:
On Sun, 2007-02-25 at 18:34 -0500, Jeff Garzik wrote:
Just got sata_mv working under the new EH, on my 6041.
It probes and talks to disks just fine (chip doesn't support ATAPI),
and hotplug actually has a chance of working.
The 'mv-eh' branch of
Dave Dillow wrote:
BUG: at drivers/ata/sata_mv.c:1245 mv_qc_issue()
BUG: at drivers/ata/sata_mv.c:1245 mv_qc_issue()
BUG: at drivers/ata/sata_mv.c:1245 mv_qc_issue()
BUG: at drivers/ata/sata_mv.c:1245 mv_qc_issue()
BUG: at drivers/ata/sata_mv.c:1291 mv_get_crpb_status()
Well, all these seem to
On Tue, 2007-03-06 at 01:01 -0500, Jeff Garzik wrote:
Dave Dillow wrote:
BUG: at drivers/ata/sata_mv.c:1245 mv_qc_issue()
BUG: at drivers/ata/sata_mv.c:1245 mv_qc_issue()
BUG: at drivers/ata/sata_mv.c:1245 mv_qc_issue()
BUG: at drivers/ata/sata_mv.c:1245 mv_qc_issue()
[snip]
Does the
On Tue, 6 Mar 2007, Jeff Garzik wrote:
Dave Dillow wrote:
BUG: at drivers/ata/sata_mv.c:1245 mv_qc_issue()
BUG: at drivers/ata/sata_mv.c:1245 mv_qc_issue()
BUG: at drivers/ata/sata_mv.c:1245 mv_qc_issue()
BUG: at drivers/ata/sata_mv.c:1245 mv_qc_issue()
BUG: at
Reading from the ATA shadow registers while we are in ADMA mode may cause
undefined behavior. Don't read the ATA status register when completing commands
for this reason, it shouldn't be needed as the controller will notify us if
the command failed. Also, don't allow commands with result taskfile
Hell Tejun,
I've boot-tested this yesterday, with no real luck...
1 - Tested on top of 2.6.21-rc2 (hope it's fine for you),
2 - Collected a full dmesg before and after
Extract is :
ata7: PATA max UDMA/100 cmd 0x00019c00 ctl 0x00019882 bmdma
0x00
019400 irq 16
ata8: PATA
19 matches
Mail list logo
