Hello,
> Ok, so that's just a message irritation, not actually bothersome
> otherwise?
It is somewhat painful, because delays involved are quite long, and
it is not possible to explain the machine to "ignore" the port, and
skip to the next one...
> > The second problem is a Jmicron363 control
Martin Mailand wrote:
> Our main problem is that we can not switch to the 2.6.20 kernel, we must
> use the standart Suse kernel 2.6.18.2-34-bigsmp.
> Is there any workaround / fix or new fimrware known to fix this freeze
> issue?
Probably opening a bug report at bugzilla.novell.com and assigning i
Richard Scobie wrote:
> Hi,
>
> This may already be addressed, but in case anyone is interested.
>
> Fedora Core 6 2.6.19-1.2911.6.5, NVIDIA MCP55 based board using sata_nv.
>
> When querying a drive using smartctl and SMART is not enabled on the
> drive, I get the following error:
>
> ata3.00:
Hello, Berck.
Berck E. Nash wrote:
> Tejun Heo wrote:
>> Berck E. Nash wrote:
>>> Testing the new libata ICH PATA drivers. There's one PATA port on this
>>> chip, and I've got two optical drives connected to it. The master drive
>>> fails to detect. The slave detects and works properly.
>> Can
Of course I forgot to CC. :-) Quoting whole message for Justin.
Tejun Heo wrote:
> Hello, Linus.
>
> Linus Torvalds wrote:
>> On Sun, 11 Mar 2007, Paul Rolland wrote:
>>> My machine is having two problems : the one you are describing above,
>>> which is due to a SIL controler being connected to
Hello, Linus.
Linus Torvalds wrote:
> On Sun, 11 Mar 2007, Paul Rolland wrote:
>> My machine is having two problems : the one you are describing above,
>> which is due to a SIL controler being connected to one port of the ICH7
>> (at least, it seems to), and probing it goes timeout, but nothing i
Hello,
Russ Weeks wrote:
> Thanks, Jim, Tejun. Upgrading to 2.6.20 solved all my problems.
Great.
> What I observe now is that once the drive is plugged in again, 2-3
> minutes may pass before the device entry appears in /dev. This isn't a
> problem for me, but if you have time to explain I'd
On Mar 12, 2007 04:27 +0100, Jan Engelhardt wrote:
> Assume this partition table on my current HD:
>
> Disk /dev/hdc: 251.0 GB, 251000193024 bytes
> 255 heads, 63 sectors/track, 30515 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
> Device Start
On Mar 11 2007 22:45, Ric Wheeler wrote:
> Jan Engelhardt wrote:
>> On Mar 11 2007 18:51, Ric Wheeler wrote:
>>
>> > During the recent IO/FS workshop, we spoke briefly about the
>> > coming change to a 4k sector size for disks on linux. If I
>> > recall correctly, the general feeling was that the
Jan Engelhardt wrote:
On Mar 11 2007 18:51, Ric Wheeler wrote:
During the recent IO/FS workshop, we spoke briefly about the
coming change to a 4k sector size for disks on linux. If I
recall correctly, the general feeling was that the impact was
not significant since we already do most file
Alan Cox wrote:
Are there other concerns in the IO or FS stack that we should bring up
with vendors? I have been asked to summarize the impact of 4k sectors
on linux for a disk vendor gathering and want to make sure that I put
all of our linux specific items into that summary...
We ne
Jeff Garzik wrote:
Alan Cox wrote:
I would be interested to know what the disk vendors intend to use as
their strategy when (with ATA) they have a 512 byte write from an older
file system/setup into a 4K block. The case where errors magically
appear
Well, you have logical and physical secto
On Sun, Mar 11, 2007 at 01:02:13AM +0100, Bartlomiej Zolnierkiewicz wrote:
>
> Hi,
>
> It seems that the generic IDE host driver is loaded first
> (CONFIG_IDE_GENERIC=y/m) and "steals" resources needed by cy82c693.
>
> Please try again without the generic IDE host driver so the proper
> driver c
On Sun, 11 Mar 2007, Paul Rolland wrote:
>
> My machine is having two problems : the one you are describing above,
> which is due to a SIL controler being connected to one port of the ICH7
> (at least, it seems to), and probing it goes timeout, but nothing is
> connected on it.
Ok, so that's ju
Alan Cox wrote:
I would be interested to know what the disk vendors intend to use as
their strategy when (with ATA) they have a 512 byte write from an older
file system/setup into a 4K block. The case where errors magically appear
Well, you have logical and physical sector size changes.
First
On Mar 11 2007 18:51, Ric Wheeler wrote:
>
> During the recent IO/FS workshop, we spoke briefly about the
> coming change to a 4k sector size for disks on linux. If I
> recall correctly, the general feeling was that the impact was
> not significant since we already do most file system IO in 4k
> p
> Are there other concerns in the IO or FS stack that we should bring up
> with vendors? I have been asked to summarize the impact of 4k sectors
> on linux for a disk vendor gathering and want to make sure that I put
> all of our linux specific items into that summary...
We need to make sure
During the recent IO/FS workshop, we spoke briefly about the coming
change to a 4k sector size for disks on linux. If I recall correctly,
the general feeling was that the impact was not significant since we
already do most file system IO in 4k page sizes and should be fine as
long as we parti
Hello,
> > Nope... I tried several patches from Tejun, and also some
> that Jeff posted
> > to linux-ide, but no luck. The only way to have this DVD-RW
> working is to
> > use irqpoll on the command line...
>
> So it has *never* worked? That's what I'm trying to see - you had a
> "before" and
This patch changes sata_promise so that the PATA ports
on TX2plus chips are bound to the pdc_pata_ops structure.
This means that operations called from the SATA ops
structures don't need any SATA-vs-PATA tests any more.
Instead, operations that depend on a port being SATA or
PATA are separated into
The recent change which moved cable detection from
pdc_pre_reset() to the new ->cable_detect hook only
added the hook for SATAII chips, leaving SATAI chips
and the 20619 without the hook. Fixed by this patch.
Signed-off-by: Mikael Pettersson <[EMAIL PROTECTED]>
---
drivers/ata/sata_promise.c |
On Sun, 11 Mar 2007, Paul Rolland wrote:
>
> Nope... I tried several patches from Tejun, and also some that Jeff posted
> to linux-ide, but no luck. The only way to have this DVD-RW working is to
> use irqpoll on the command line...
So it has *never* worked? That's what I'm trying to see - you
Just one point that may be interesting, as it seems that this is IRQ
related : at the beginning of the dmesg, it seems that IRQ16 is used
for sky2/Yukon , but when reading /proc/interrupts, it has been remapped
to IRQ 505... Could this also affect libata ?
Regards,
Paul
Paul Rolland, rol(at)as291
Paul,
do I understand correctly that the *only* difference between the working
setup is that you applied (by hand) the libata patch that Jeff sent out?
So plain 2.6.21-rc2 works fine, but with the patch applied, you get no
interrupts on the DVD drive?
On Sun, 11 Mar 2007, Paul Rolland wrote:
Tejun Heo wrote:
> Berck E. Nash wrote:
>> Testing the new libata ICH PATA drivers. There's one PATA port on this
>> chip, and I've got two optical drives connected to it. The master drive
>> fails to detect. The slave detects and works properly.
>
> Can you test 2.6.20.1 and post full dmesg?
Hello,
> It seems like IRQ is not getting through. The first IRQ
> driven command is failing for you.
H
> Extract is :
> ata7: PATA max UDMA/100 cmd 0x00019c00 ctl 0x00019882 bmdma
> 0x00019400 irq 16
> ata8: PATA max UDMA/100 cmd 0x00019800 ctl 0x00
26 matches
Mail list logo
