| To: | Alvaro Figueroa <fede2@xxxxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: opps on xfs on a linear raid on a sparc64 box |
| From: | Steve Lord <lord@xxxxxxx> |
| Date: | 20 Mar 2002 09:25:58 -0600 |
| Cc: | XFS to linux port mailing list <linux-xfs@xxxxxxxxxxx> |
| In-reply-to: | <1016587272.19159.2.camel@lucy> |
| References: | <1016561155.19159.0.camel@lucy> <1016587272.19159.2.camel@lucy> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
On Tue, 2002-03-19 at 19:21, Alvaro Figueroa wrote:
> > Today, I'd tried to use xfs on a linear raid, and it oops'ses.
>
> I've just tried it with a raid5, and the same thing happen.
>
> (BTW, I did forgot to mention (sorry) that the same raid formated with
> ext2, even with the same kernel, works perfectly)
>
> Here is the oops for the raid5 test.
>
>
Both these oopses are the same thing, but why sparc64 sees this when
other platforms do not I really do not know. Do you have any way of
working out where in the function this address is on a sparc64?
__make_request+75c/760
i.e. which line of source. It might give us some clues.
Steve
--
Steve Lord voice: +1-651-683-3511
Principal Engineer, Filesystem Software email: lord@xxxxxxx
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Corrupted files on 2.4.18., Bas |
|---|---|
| Next by Date: | Re: Corrupted files on 2.4.18., Steve Lord |
| Previous by Thread: | Re: opps on xfs on a linear raid on a sparc64 box, Alvaro Figueroa |
| Next by Thread: | --enable-shared=no gives linking errors Was: New tarball error, Hundstad, Jeffrey E. |
| Indexes: | [Date] [Thread] [Top] [All Lists] |