From: Michal Jaegermann <michal@ellpspace.math.ualberta.ca>
To: linux-kernel@vger.kernel.org
Subject: 2.4.1 not fully sane on Alpha - file systems
Date: Wed, 31 Jan 2001 23:49:25 -0700 [thread overview]
Message-ID: <20010131234925.A14300@ellpspace.math.ualberta.ca> (raw)
I just tried to boot 2.4.1 kernel on Alpha UP1100. This machine
happens to have two SCSI disks on sym53c875 controller and two IDE
drives hooked to a builtin "Acer Laboratories Inc. [ALi] M5229 IDE".
It boots and in the first moment makes even a pretty good impression
of beeing healthy. But an attempt to compile something causes the
whole setup to start behaving weird, with a compiler obviously unable
to find both itself and the right sources, and the whole thing ends in
a silent lockup.
On the second boot I tried to copy kernel sources from a SCSI to an
IDE drive. This time I got something in my logs and the same stuff
was printed on my screen before everything lockded up really tight
again (no sysrq). Here it is:
kernel: attempt to access beyond end of device
kernel: 08:05: rw=0, want=198500353, limit=5779456
kernel: attempt to access beyond end of device
kernel: 08:05: rw=0, want=4294934529, limit=5779456
kernel: attempt to access beyond end of device
kernel: 08:05: rw=0, want=198500353, limit=5779456
kernel: EXT2-fs error (device sd(8,5)): ext2_readdir: bad entry in
directory #250255: directory entry across blocks - offset=0,
inode=198505472, rec_len=32768, name_len=255
(and the machine dies at this point).
There is nothing wrong with this device and a file system on it.
Copying the same way, or compiling the same sources, but when booted
with 2.2.18 does not present a whiff of trouble and e2fsck, luckily
enough, finds my file systems still in place. One should be grateful
for small favours.
Anybody have seen something similar?
Michal
michal@harddata.com
p.s. I find a bit humorous the fact that the code required to
recognize that one has _some_ partition table (I happen to have two
kinds at the moment) is billed in a config file as ADVANCED.
It did the job anyway. :-)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-02-01 6:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-01 6:49 Michal Jaegermann [this message]
2001-02-01 15:46 ` 2.4.1 not fully sane on Alpha - file systems John Jasen
2001-02-01 16:23 ` Michal Jaegermann
2001-02-01 20:38 ` 2.4.x/alpha/ALI chipset/IDE problems summary " John Jasen
2001-02-01 22:18 ` Andre Hedrick
2001-02-02 16:30 ` John Jasen
2001-02-15 17:49 ` John Jasen
2001-02-15 19:48 ` Michal Jaegermann
2001-02-15 20:15 ` John Jasen
2001-02-15 20:47 ` Michal Jaegermann
2001-02-15 20:59 ` John Jasen
2001-02-02 7:39 ` Michal Jaegermann
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=20010131234925.A14300@ellpspace.math.ualberta.ca \
--to=michal@ellpspace.math.ualberta.ca \
--cc=linux-kernel@vger.kernel.org \
/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