Hi,
Lennart Sorensen wrote:
[...]
Isn't it more a matter of having a CF card that does do DMA and a
controller that does DMA, but a CF to IDE adapter that does not do DMA?
If it is really a case of a CF card that claims to do DMA but is
unstable if you try (I have found one model that does so
Hi,
Alan Cox wrote:
[...]
For the current kernel and libata you can use libata.dma=3, and it will
select DMA for disk (1) + CD (2) but not CF cards. With the older IDE it
should be sufficient to use hda=nodma
Thanks a lot, but it does not work:
If I use libata.dma=3 I get the following:
[
Hi,
Gabriel C wrote:
[...]
Also have a look at Documentation/ide.txt.
I read this already. Searching for "nodma" in this document gives only
one line:
"ide=nodma": disable DMA globally for the IDE subsystem.
If the documentation is correct hda=nodma and ideX=nodma should not
Hi,
Gabriel C wrote:
Oliver Joa wrote:
Hi,
Hi Oliver ,
how can I tell the kernel not to probe DMA for a specific harddisk (e.g.
hda). My first Drive (hda) is a Compact-Flash Card which can not do DMA.
The kernel tries at boot to switch to DMA but fails. If I use ide=nodma,
the kernel
Hi,
how can I tell the kernel not to probe DMA for a specific harddisk (e.g.
hda). My first Drive (hda) is a Compact-Flash Card which can not do DMA.
The kernel tries at boot to switch to DMA but fails. If I use ide=nodma,
the kernel boots about 2 minutes faster, but then I can not switch on
Hi,
David Chinner wrote:
On Tue, Mar 27, 2007 at 06:16:04PM +0200, Oliver Joa wrote:
Hi,
since some weeks i try to get my new hardware running:
Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz
Intel DP965LT Mainboard
Seagate SATA-Harddisk in AHCI-Mode
After some hours of running or after
Hi,
does anyone have a running Intel DP965LT Mainboard? I can not get this
Board running. You can see the Problems in the Thread "Corrupt
XFS-Filesystems on new Hardware and Kernel". Please can you give me a
running Kernel-Config?
Thanks a lot
Oliver
-
To unsubscribe from this list: send t
Hi,
David Chinner wrote:
[...]
Next time you get a shutdown, can you unmount the filesystems and
run xfs_check and then "xfs_repair -n" on the filesystem. These will
tell you the inode numbers that are bad. Can you post the errors
reported by these tools?
xfs_check gives this:
bad format 0
Hi,
Eric Sandeen wrote:
[...]
For one reason or another, xfs has detected a corrupted on-disk inode
format which it cannot recognize, and shuts down. It is likely the
result of something which has gone wrong previously. xfs_repair should
fix it. Are there other non-xfs messages in your lo
Hi,
David Chinner wrote:
[...]
What is the corruption message in the log from XFS?
Can you please post that? Without it we really can't help you.
Also, please check to see if there are any I/O errors
in the log around the time the corruption message appears.
Ok, here is a test:
test:/# fin
hi,
Paolo Ornati wrote:
[...]
What Seagate is it? (hdparm -I /dev/sda | head)
I have this one:
ATA device, with non-removable media
Model Number: ST380817AS
Serial Number: 4MR08EK8
Firmware Revision: 3.42
Model Number: ST3160827AS
ut to change
from xfs to ext2 but the filesystemcheck every 30 mounts lasts
a long time.
Do you have any Idea?
Which kernel is at the moment a so called stable? Stable enough
for my hardware?
Thanks a lot
Oliver Joa
-
To unsubscribe from this list: send the line "unsubscribe linux-kern
12 matches
Mail list logo
