From: Mark Lord <liml@rtr.ca>
To: "Morrison, Tom" <tmorrison@empirix.com>
Cc: Jeff Garzik <jeff@garzik.org>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.23.1 - sata_mv (7042) hang with large file operations
Date: Wed, 14 Nov 2007 13:56:11 -0500 [thread overview]
Message-ID: <473B44CB.6010209@rtr.ca> (raw)
In-Reply-To: <BD261180E6D35F4D9D32F3E44FD3D9010AAE8585@EMPBEDEX.empirix.com>
Morrison, Tom wrote:
> -----Original Message-----
> From: Mark Lord [mailto:liml@rtr.ca]
> Sent: Wednesday, November 14, 2007 12:57 PM
> To: Morrison, Tom
> Cc: Jeff Garzik; linux-ide@vger.kernel.org; linux-kernel@vger.kernel.org
> Subject: Re: 2.6.23.1 - sata_mv (7042) hang with large file operations
>
> Morrison, Tom wrote:
> <snip >
>> The problem comes ONLY when I am doing large file operations
>> (e.g.: just copying a file) to/from the SATA drives behind
>> the subject line 7042....it just hangs after about 10-15
>> seconds into the copy...
>>
>> How large a file causes the hang - you ask - well, somewhere
>> between 100Meg & 500Meg...
>>
> <snip other drivel>
>
>
> ::: Can you give me exact details of how to set up and reproduce this?
> ::: -- Kernel version
>
> Linux-2.6.23.1
>
> NOTE: I am using ppc (arch/ppc instead of arch/powerpc)
>
> ::: -- number/config/model of drives
>
> 2x250GIG Western Digital - 3 partitions (largest (/dev/sda3
> ~200Gig - formatted to ext2).
>
> 7042 PEX on a MPC8548 Board
>
> ::: -- exact command line sequence to cause the failure
>
> NFS mount root file system (I am currently rebuild to take away
> the NFS file system dependency) - /dev/sda3 is drive in question...
..
MMmm.. I'd like to see that again without the rootfs-on-NFS.
What exactly do you mean when you say "it just hangs" ?
Everything (dead system)?
next prev parent reply other threads:[~2007-11-14 18:56 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 10:38 [patch 26/30] Support for Marvell 7042 Chip akpm
2007-03-06 12:01 ` Jeff Garzik
2007-03-06 12:42 ` Morrison, Tom
2007-03-06 13:10 ` Jeff Garzik
2007-10-31 15:41 ` Other Problems with Marvell Driver - 7042 (2.6.23) Morrison, Tom
2007-10-31 16:06 ` Jeff Garzik
2007-10-31 18:14 ` Update (Now a False Alarm) " Morrison, Tom
2007-11-14 17:49 ` 2.6.23.1 - sata_mv (7042) hang with large file operations Morrison, Tom
2007-11-14 17:56 ` Mark Lord
2007-11-14 18:09 ` Morrison, Tom
2007-11-14 18:30 ` Mark Lord
2007-11-14 20:12 ` Morrison, Tom
2007-11-14 18:37 ` Mark Lord
2007-11-14 18:56 ` Mark Lord [this message]
2007-11-14 21:12 ` Morrison, Tom
2007-11-14 22:29 ` Mark Lord
2007-11-14 22:31 ` Mark Lord
2007-11-15 15:43 ` Morrison, Tom
2007-11-15 16:26 ` Morrison, Tom
2007-11-15 16:39 ` Mark Lord
2007-11-15 21:46 ` Morrison, Tom
2007-11-15 22:14 ` Mark Lord
2007-11-16 0:07 ` Morrison, Tom
2007-11-16 13:00 ` Morrison, Tom
2007-11-16 17:07 ` Morrison, Tom
2007-12-06 13:57 ` Revisiting - 2.6.23.8 - Hang with sata_mv (7042) + Flat 4Gig (no holes) Memory Morrison, Tom
[not found] ` <475D6CC3.2080400@rtr.ca>
2007-12-10 16:46 ` Morrison, Tom
2007-12-11 17:28 ` Responding to 2 thread <2.6.23.8 - Hang with sata_mv (7042)...> AND <Bug: get EXT3-fs error Allocating block in system zone> Morrison, Tom
2007-12-11 17:42 ` Mark Lord
2007-12-11 17:53 ` Morrison, Tom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=473B44CB.6010209@rtr.ca \
--to=liml@rtr.ca \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tmorrison@empirix.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).