From: Carsten Langgaard <carstenl@mips.com>
To: linux-mips@oss.sgi.com
Subject: Re: fsck fails on latest 2.4 kernel
Date: Wed, 16 Jan 2002 15:51:47 +0100 [thread overview]
Message-ID: <3C459383.5C8A6C8B@mips.com> (raw)
In-Reply-To: 3C454D61.ACF98623@mips.com
The problem turned out to be a compiler/binutils bug.
I'm using
ftp://oss.sgi.com/pub/linux/mips/crossdev/i386-linux/mipsel-linux/binutils-mipsel-linux-2.9.5-3.i386.rpm
and
ftp://oss.sgi.com/pub/linux/mips/crossdev/i386-linux/mipsel-linux/egcs-mipsel-linux-1.1.2-4.i386.rpm
, which seems to be the latest on the SGI FTP server.
What are the recommended toolchain ?
/Carsten
Carsten Langgaard wrote:
> I have checked out the latest 2.4 kernel sources and tried to run it on
> my Malta board with an IDE disk, but fsck fails.
> EPC points at __wake_up, which is called from __alloc_pages.
>
> Has anyone encountered a similar problem ?
>
> Checking root filesystem
> /dev/hda1 was not cleanly unmounted, check forced.
> Oops in fault.c:do_page_fault, line 204:
> $0 : 00000000 9000fc00 00000000 00000000 0000001a 802b5d0c 83b72000
> 811e94e0
> $8 : 00001000 00000001 801374c4 00000003 00000000 83b73ed0 00068db8
> 7fff7688
> $16: 00000000 9000fc00 00000001 9000fc01 802c0078 802bc628 00000001
> 83ce23c0
> $24: 00000000 0046a040 83b72000 83b73df0 83b73df0
> 8011239c
> Hi : 00000000
> Lo : 00000000
> epc : 801123ec Not tainted
> Status: 9000fc02
> Cause : 80800008
> Process fsck.ext2 (pid: 50, stackpage=83b72000)
> Stack: 83ce23c0 0000001f 00001000 83ce23c0 802c0a38 00000001 00000000
> 8115c320
> 802c08dc 802c0a2c 000001d0 8115c260 80131278 810140e4 000889c5
> 00000000
> 00001000 8115c260 80127928 00000002 81121b58 00000000 00000000
> 8115c320
> 00088a3d 00000000 00001000 80130e70 81121978 810140c0 00000000
> 8115c320
> 801285a0 8012847c 8025c1e0 00000001 802bf000 00000000 00000000
> 81163060
> ffffffea ...
> Call Trace: [<80131278>] [<80127928>] [<80130e70>] [<801285a0>]
> [<8012847c>] [<8
> 025c1e0>]
> [<80128a7c>] [<80128974>] [<80118c5c>] [<8013759c>] [<80137398>]
> [<8010d368>]
>
> Code: 12400004 00000000 8e100000 <5614ffcc> 8e05fffc 40016000
> 32730001 3421
> 0001 38210001
> [/sbin/fsck.ext2 -- /] fsck.ext2 -a /dev/hda1
> Warning... fsck.ext2 for device /dev/hda1 exited with signal 11.
> [FAILED]
>
> /Carsten
>
> --
> _ _ ____ ___ Carsten Langgaard Mailto:carstenl@mips.com
> |\ /|||___)(___ MIPS Denmark Direct: +45 4486 5527
> | \/ ||| ____) Lautrupvang 4B Switch: +45 4486 5555
> TECHNOLOGIES 2750 Ballerup Fax...: +45 4486 5556
> Denmark http://www.mips.com
--
_ _ ____ ___ Carsten Langgaard Mailto:carstenl@mips.com
|\ /|||___)(___ MIPS Denmark Direct: +45 4486 5527
| \/ ||| ____) Lautrupvang 4B Switch: +45 4486 5555
TECHNOLOGIES 2750 Ballerup Fax...: +45 4486 5556
Denmark http://www.mips.com
next prev parent reply other threads:[~2002-01-16 15:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-16 9:52 fsck fails on latest 2.4 kernel Carsten Langgaard
2002-01-16 14:51 ` Carsten Langgaard [this message]
2002-01-16 17:42 ` H . J . Lu
2002-01-16 22:26 ` Ralf Baechle
2002-01-17 7:25 ` Carsten Langgaard
2002-01-17 7:52 ` Ralf Baechle
2002-02-01 21:43 ` Matthew Dharm
2002-02-01 21:43 ` Matthew Dharm
2002-02-01 22:52 ` H . J . Lu
2002-02-01 23:03 ` Matthew Dharm
2002-02-01 23:03 ` Matthew Dharm
2002-02-02 1:08 ` Matthew Dharm
2002-02-02 1:08 ` Matthew Dharm
2002-02-02 1:47 ` H . J . Lu
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=3C459383.5C8A6C8B@mips.com \
--to=carstenl@mips.com \
--cc=linux-mips@oss.sgi.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