Hi,
Nicos, Thanks a lot for your reply!
On Mon, Jun 10, 2002 at 03:04:56PM +0200, Nicos Gollan wrote:
> On Sunday 09 June 2002 22:36, Joost van Baal wrote:
> >
> > [Please Cc me on replies, I'm not subscribed.]
> >
> > The short summary: When booting, my box gives up, stating:
> >
> > NET4: Unix domain sockets 1.0 for Linux NET4.0.
> > attempt to access beyond end of device
> > 03:02: rw=0, want=1023464393, limit=48384
> > dev 03:02 blocksize=1024 blocknr= ....
> > ...
>
> OK, from what I saw in the kernel source (drivers/block/ll_rw_blk.c,
> line 849):
The box is running `Linux version 2.2.20 (herbert@gondolin) (gcc version
2.7.2.3) #1 Sat Apr 20 11:45:28 EST 2002', as shipped with the woody
boot floppies.
>
> /* This may well happen - the kernel calls bread()
> without checking the size of the device, e.g.,
> when mounting a device. */
> printk(KERN_INFO
> "attempt to access beyond end of device\n");
> printk(KERN_INFO "%s: rw=%d, want=%ld, limit=%d\n",
> kdevname(bh->b_rdev), rw,
> (sector + count)>>1, minorsize);
>
> So it could be an error during mounting.
hmm.. It _does_ tell me `VFS: Mounted root (ext2 filesystem) readonly.',
and the errors seem to occur while running /etc/init.d/keymap.sh and
/etc/init.d/checkroot.sh . Apparently, mounting readonly succeeds, and
mounting read-write is not even tried. Or is the message `VFS: Mounted
root (ext2 filesystem) readonly.' misleading me, and did the mount fail
in some way?
> Device 03:02 should be hda2,
> your root partition. A failure to mount or properly recognize it would
> also explain all further errors. That's about all I can tell right now,
> but perhaps it helps in further troubleshooting. Anyone?
>
> My shot in the dark: it could be a bad BIOS call that fails to return
> the correct size of the disk or a bad <insert your choice>. Perhaps
> post the complete lines that you abbreviated.
Here are all the bits which I believe might be interesting:
-----------------
boot:
Loading Linux.........
Uncompressing Linux... Ok, booting the kernel.
Linux version 2.2.20 (herbert@gondolin) ...
BIOS-provided physical RAM map:
BIOS-e820: 0009fc00 @ 00000000 (usable)
BIOS-e820: 00000400 @ 0009fc00 (usable)
BIOS-e820: 02f00000 @ 00100000 (usable)
Detected 132634 kHz processor.
...
VFS: Diskquotas version dquot_6.4.0 initialized
...
PCI: PCI BIOS revision 2.10 entry at 0xfb230
...
PIIX3: IDE controller on PCI bus 00 dev 39
PIIX3: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:pio, hdb:pio
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:pio, hdd:pio
hda: QUANTUM BIGFOOT2100A, ATA DISK drive
hdc: 685A, ATAPI CDROM drive, 120kB Cache
...
scsi : detected total.
Partition check:
hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 >
apm: BIOS version 1.2 Flags 0x07 (Driver version 1.13)
apm: disabled on user request.
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 152k freed
INIT: version 2.84 booting
NET4: Unix domain sockets 1.0 for Linux NET4.0
attempt to access beyond end of device
03:02: rw=0, want=1023464393, limit=48384
dev 03:02 blksize=1024 blocknr=1023464392 sector=2046928784 size=1024 count=1
attempt to access beyond end of device
03:02: rw=0, want=1023464393, limit=48384
dev 03:02 blksize=1024 blocknr=1023464392 sector=2046928784 size=1024 count=1
attempt to access beyond end of device
03:02: rw=0, want=1016142892, limit=48384
dev 03:02 blksize=1024 blocknr=1016142891 sector=2032285782 size=1024 count=1
attempt to access beyond end of device
03:02: rw=0, want=65543, limit=48384
dev 03:02 blksize=1024 blocknr=65542 sector=131084 size=1024 count=1
/etc/init.d/rcS: line 38: 10 Segmentation fault loadkeys ${CONFDIR}/${CO
NFFILEROOT}.${EXT}.gz
Activating swap.
Adding Swap: 96764k swap-space (priority -1)
Checking root file system...
attempt to access beyond end of device
03:02: rw=0, want=49802217, limit=48384
dev 03:02 blksize=1024 blocknr=49802216 sector=99604432 size=1024 count=1
attempt to access beyond end of device
03:02: rw=0, want=2026144513, limit=48384
dev 03:02 blksize=1024 blocknr=-1211339136 sector=-242678272 size=1024 count=1
attempt to access beyond end of device
....
attempt to access beyond end of device
....
attempt to access beyond end of device
....
attempt to access beyond end of device
....
attempt to access beyond end of device
....
attempt to access beyond end of device
....
attempt to access beyond end of device
....
attempt to access beyond end of device
....
attempt to access beyond end of device
....
attempt to access beyond end of device
03:02: rw=0, want=200586302, limit=48384
dev 03:02 blksize=1024 blocknr=200586301 sector=401172602 size=1024 count=1
/etc/init.d/rcS: line 145: 19 Bus error fsck $spinner $force $f
ix /
fsck failed. Please repair manually and reboot. Please note
....
Give root password for maintenance
(or type Control-D for normal startup):
-----------------
> The "want" number
> indicates that there was a planned access somewhere after 976GB.
Yep, pretty ridiculous.
> Perhaps also make sure you don't need an obscure kernel workaround for
> some strange system component. The BIOSes used for P133 systems are...
> we.. strange.
Hm, would tweaking CONFIG_PCI_GOBIOS or CONFIG_PCI_QUIRKS possibly help?
/boot/config-2.2.20 has CONFIG_PCI_GOBIOS unset, and CONFIG_PCI_QUIRKS=y.
Furthermore,
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
are set.
Hm, I plan to compile a customized kernel anyway, maybe problems are no
longer there when running 2.4.18 ...
I did some grepping in kernel-doc-2.2.20's Documentation/ide.txt.gz , but
didn't find anything about this. (Maybe I didn't look careful enough though.)
BTW, the behaviour during boot is _very_ random: During the last couply of
days, I've had 7 failed boots and 8 succeeded boots. I didn't notice any
pattern. BTW, the system crashed never. I just rebooted to peek at the boot
messages of the day.
I'll keep you informed (and I welcome any more insight, of course.)
Thanks again, Bye,
Joost
--
. .
Joost van Baal . .
. . http://mdcc.cx/
. .
Attachment:
pgpDZHw1byggP.pgp
Description: PGP signature