Hardware: Athlon64, Asus A8V, Promise SATA300 TX4, 2xSeagate 7200.10
320G, jumper-limited to SATA150.
Kernel : 2.6.22.9 amd64
Problem:
Heavy load causes errors and triggers oops.
History:
Problems were first encountered on kernel 2.6.19, both i686 (old
system) and amd64 (gentoo installation
Alexander Sabourenkov schrieb:
Hardware: Athlon64, Asus A8V, Promise SATA300 TX4, 2xSeagate 7200.10
320G, jumper-limited to SATA150.
Kernel : 2.6.22.9 amd64
Problem:
Heavy load causes errors and triggers oops.
Have you checked your memory already (memtest86)?
We have several applications
Clemens Koller wrote:
Alexander Sabourenkov schrieb:
Hardware: Athlon64, Asus A8V, Promise SATA300 TX4, 2xSeagate 7200.10
320G, jumper-limited to SATA150.
Kernel : 2.6.22.9 amd64
Problem:
Heavy load causes errors and triggers oops.
Have you checked your memory already (memtest86)?
Mark Lord wrote:
Linux kernel development is supposed to happen incrementally nowadays.
Get a nice working solution in place, and then enhance/tune it.
It's not about enhancing and tuning.
It's about me (and/or James B) having to __undo__ the current code, just
to get things working on an
Hi,
On 15 August 2007 Tejun Heo wrote:
You don't need to worry too much as long as errors are properly,
recovered. All commands are retried and you won't lose any data.
Please report if the spurious NCQ problem happens again. Thanks.
I've just received a logcheck mail with another one. I
Hello.
Alan Cox wrote:
Nobody commented when I asked for review earlier so it must be ok 8)
It's not that I've seen this before
so it must be ok 8)
Not by me at least, so let me NAK it. 8-)
Lets stick it in -mm to be sure
Now let's unstick it. :-)
Signed-off-by: Alan Cox
Hi, there!
Can someone please put some light on what happened here:
Short story:
linux kernel 2.6.18 block i/o on file access on reiserfs on raid1.
Long story:
Sorry, for the long mail... I just try to give all details.
On one of our old simple samba file servers, I ran into a
strange problem
Hello Tejun,
i am stuck with 2.6.22.1 because this is the latest version of your PMP
patchset...this is perfectly working but i can not apply these set
against newer versions of the kernel...could you update your homepage or
post a howto/message/link for instructions to get the patchset against
Daniel Schroeder wrote:
i am stuck with 2.6.22.1 because this is the latest version of your PMP
patchset...this is perfectly working but i can not apply these set
against newer versions of the kernel...could you update your homepage or
post a howto/message/link for instructions to get the
What is the difference between NA and RV? If the controller only has
access to 2 ports, does it matter which I set the nonexistent port
values to in the map?
NA is used for unimplemented ports of a valid configuration while RV is
used to mark invalid MAP value. So, NA should be mixed with
Tejun
netconsole, pritty nice debunging system... but (yes, there is
always a but) it does not get to run.
the method was well implemented, adding the acpi=off it sends the
information to the receiving machine (I can even see passing a
netconsole probing message in the machine under
Hello
(please CC me when replying)
On 27/09/2007, Tejun Heo [EMAIL PROTECTED] wrote:
Michal Suchanek wrote:
On 11/09/2007, Tejun Heo [EMAIL PROTECTED] wrote:
Michal Suchanek wrote:
What does 'smartctl -a /dev/sda' say?
Attaching output.
Hmmm... How often does the condition occur?
(please cc me, as i´m not subscribed to linux-kernel/ide - thanks)
hi,
we have some Fujitsu Siemens Celsius M450 workstations (Intel 975X Express
chipset)
running Linux Kernel 2.6.22 (Debian, Ubuntu) on an md raid 1 using two Western
Digital
Raptor drives, it´s the WD800ADFS which is an oem
2.6.18:
libata version 2.00 loaded.
sata_nv :00:07.0: version 2.0
ACPI: PCI Interrupt Link [LTID] enabled at IRQ 20
GSI 18 sharing vector 0xE9 and IRQ 18
ACPI: PCI Interrupt :00:07.0[A] - Link [LTID] - GSI 20 (level, low) -
IRQ 233
PCI: Setting latency timer of device :00:07.0 to 64
On Thursday 27 September 2007, Shane Huang wrote:
From: [EMAIL PROTECTED]
SB700 supports one physical IDE channel, but SB700 SATA controller
supports combined mode. When the SATA combined mode is enabled,
two SATA ports(port4 and port5) share one IDE channel from IDE
controller, and PATA
On Saturday 29 September 2007, Sergei Shtylyov wrote:
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()
Stop abusing ide_lock lock by switching to a private locking.
Fixes same issue as fixed by Alan Cox in atiixp host driver with
commit 6c5f8cc33eb2e10b6ab788bbe259fc142a068627.
Signed-off-by: Bartlomiej Zolnierkiewicz [EMAIL PROTECTED]
---
drivers/ide/legacy/ali14xx.c |6 --
1 file
Stop abusing ide_lock lock (switch to a private locking).
Fixes same issue as fixed by Alan Cox in atiixp host driver with
commit 6c5f8cc33eb2e10b6ab788bbe259fc142a068627.
Signed-off-by: Bartlomiej Zolnierkiewicz [EMAIL PROTECTED]
---
drivers/ide/legacy/dtc2278.c |6 --
1 file changed,
Stop abusing ide_lock lock (switch to a private locking).
Fixes same issue as fixed by Alan Cox in atiixp host driver with
commit 6c5f8cc33eb2e10b6ab788bbe259fc142a068627.
Signed-off-by: Bartlomiej Zolnierkiewicz [EMAIL PROTECTED]
---
drivers/ide/legacy/qd65xx.c | 17 +
1
* Stop abusing ide_lock lock (switch to a private locking).
Fixes same issue as fixed by Alan Cox in atiixp host driver with
commit 6c5f8cc33eb2e10b6ab788bbe259fc142a068627.
* Bump driver version.
Signed-off-by: Bartlomiej Zolnierkiewicz [EMAIL PROTECTED]
---
drivers/ide/pci/slc90e66.c |
* Stop abusing ide_lock lock (switch to a private locking).
Fixes same issue as fixed by Alan Cox in atiixp host driver with
commit 6c5f8cc33eb2e10b6ab788bbe259fc142a068627.
* Bump driver version.
Signed-off-by: Bartlomiej Zolnierkiewicz [EMAIL PROTECTED]
---
drivers/ide/pci/opti621.c |
Stop abusing ide_lock lock (switch to a private locking).
Fixes same issue as fixed by Alan Cox in atiixp host driver with
commit 6c5f8cc33eb2e10b6ab788bbe259fc142a068627.
cmd640 is a bit special cause we still need to leave ide_lock for
-set_pio_mode with 'pio' argument == 8/9 (prefetch
Signed-off-by: Bartlomiej Zolnierkiewicz [EMAIL PROTECTED]
---
drivers/ide/pci/cs5530.c |8 +---
1 file changed, 1 insertion(+), 7 deletions(-)
Index: b/drivers/ide/pci/cs5530.c
===
--- a/drivers/ide/pci/cs5530.c
+++
* Print PCI device Vendor ID, Device ID and revision in
ide_setup_pci_noise().
* Remove no longer needed PCI device revision printing from
ide_setup_pci_controller().
Signed-off-by: Bartlomiej Zolnierkiewicz [EMAIL PROTECTED]
---
drivers/ide/setup-pci.c |8 +++-
1 file changed, 3
* Remove dead code for handling IDE TCQ from ide_end_dequeued_request().
* Add 'dequeue' parameter to __ide_end_request().
* Use __ide_end_request() in ide_end_dequeued_request().
Signed-off-by: Bartlomiej Zolnierkiewicz [EMAIL PROTECTED]
---
drivers/ide/ide-io.c | 44
Signed-off-by: Bartlomiej Zolnierkiewicz [EMAIL PROTECTED]
---
drivers/ide/ide-taskfile.c | 23 ---
1 file changed, 23 deletions(-)
Index: b/drivers/ide/ide-taskfile.c
===
--- a/drivers/ide/ide-taskfile.c
+++
* Convert cmd64x, hpt366 and pdc202xx_old host drivers to use
pci_resource_start(hwif-pci_dev, 4) instead of hwif-dma_master.
* Remove no longer needed -dma_master field from ide_hwif_t.
Signed-off-by: Bartlomiej Zolnierkiewicz [EMAIL PROTECTED]
---
drivers/ide/ide-dma.c |7
* Remove dead code from ide_driveid_update().
While at it:
* Remove useless comment.
* s/HWIF(drive)/drive-hwif/
Signed-off-by: Bartlomiej Zolnierkiewicz [EMAIL PROTECTED]
---
drivers/ide/ide-iops.c | 26 +++---
1 file changed, 3 insertions(+), 23 deletions(-)
Index:
Bartlomiej Zolnierkiewicz wrote:
* Convert cmd64x, hpt366 and pdc202xx_old host drivers to use
pci_resource_start(hwif-pci_dev, 4) instead of hwif-dma_master.
Before using pci_resource_start(), the code should check
pci_resource_len() to ensure it is the appropriate size.
It would be very
On Monday 01 October 2007, Jeff Garzik wrote:
Bartlomiej Zolnierkiewicz wrote:
* Convert cmd64x, hpt366 and pdc202xx_old host drivers to use
pci_resource_start(hwif-pci_dev, 4) instead of hwif-dma_master.
Before using pci_resource_start(), the code should check
pci_resource_len() to
Hi,
I just pulled out my Marvell 7042 SATA controller here to give it a spin
and noticed that it no longer worked (i.e. init segvs when loading from
it), etc. 2.6.22 is fine.
Bisecting (just the file drivers/ata/sata_mv.c) resulted in
bdd4dddee325a7dce3e84cf48201a06aa8508aa4 popping out as the
Olof Johansson wrote:
Hi,
I just pulled out my Marvell 7042 SATA controller here to give it a spin
and noticed that it no longer worked (i.e. init segvs when loading from
it), etc. 2.6.22 is fine.
Bisecting (just the file drivers/ata/sata_mv.c) resulted in
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.
--
Robert
Jeff Garzik wrote:
Polling PMP 2.6.24 is completely unacceptable. It screws the 2.6.24 SAS
driver releases out of PMP.
Not merging PMP has about the same effect for SAS, right?
I pulled your last PMP patchset, and will now endeavor to fix the API
prior to 2.6.24 merge window opening.
I
Jeff Garzik wrote:
Mark Lord wrote:
Linux kernel development is supposed to happen incrementally nowadays.
Get a nice working solution in place, and then enhance/tune it.
It's not about enhancing and tuning.
It's about me (and/or James B) having to __undo__ the current code, just
to get
On Mon, 01 Oct 2007 01:30:59 +0100, Jonathan Bell
[EMAIL PROTECTED] wrote:
Hello
I've just purchased a brand spanking new G33/ICH9R based system for use
as a home fileserver with 4x ST3750840AS Seagate SATA drives as the main
grunt drives.
The problem is that all of the seagate drives
On Mon, Oct 01, 2007 at 06:37:44PM -0400, Jeff Garzik wrote:
Olof Johansson wrote:
Hardware config in my case:
Highpoint 2310 controller
PPC (big endian)
WD Raptor disk
Works fine with the other controller I've been using (SIL24), and works
fine if I revert the driver.
It also works fine
Have you checked your memory already (memtest86)?
[...]
Again... sounds like bad memory to me.
Nightly memtest86 run : 11 hours, 23 passes, 0 errors.
--
./lxnt
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a message to [EMAIL PROTECTED]
38 matches
Mail list logo