From: Rudmer van Dijk <rudmer@legolas.dynup.net>
To: Dave Jones <davej@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.5.10-dj1
Date: Sun, 28 Apr 2002 13:45:38 +0200 [thread overview]
Message-ID: <200204281145.g3SBjJJ20178@smtp2.wanadoo.nl> (raw)
In-Reply-To: <20020427030823.GA21608@suse.de> <200204271313.g3RDD4024060@smtp1.wanadoo.nl> <20020427155116.I14743@suse.de>
On Saturday 27 April 2002 15:51, Dave Jones wrote:
> On Sat, Apr 27, 2002 at 02:51:21PM +0200, Rudmer van Dijk wrote:
> > compiled fine, but after booting the system does not respond to the
> > keyboard (I can see the message "serio: i8042 KBD port at 0x60,0x64 irq
> > 1" om my screen)
>
> There are some reports that ACPI is having a bad interaction with the
> keyboard controller. For now, disabling it may fix this.
I have no ACPI or APM enabled (mobo does not know what it is)
> > The system also hangs after fscking my root partition (fsck completed
> > without errors)
> > After my harddisks went to sleep I switched the system off and after
> > booting the kernel (2.4.19-pre7) panics (and the caps- and scroll-lock
> > leds are blinking) as it can not mount the root fs due to the following
> > errors: EXT2-fs error (device ide0(3,1)): ext2_check_descriptors: Block
> > bitmap for group 0 not in group (block 0)!
> > EXT2-fs: group descriptors corrupted!
>
> This is somewhat disturbing. I'll look over the VFS changes, but I'm not
> aware of anything added specifically to my tree that could cause this,
> so it may be either an ext2 issue in mainline, or one of the drivers.
It happens after fsck (1.27) examined the root partition (hda1) finished and
the bootscripts executed the next command (fsck hdc1)
with exactly the same fsck on 2.4.19-pre7 everything is fine (after repairing
the damage done in 2.5.10-dj1)
luckily I do not have a cdrom or floppy drive attached so it was easy to
recover :), going to create a 'rescue' partition...
BTW, I had this same problem with 2.5.9-dj1... not tried with 2.5.9 or 2.5.10.
> IDE ? SCSI ?
IDE
frodo:~ # lspci
00:00.0 Host bridge: Intel Corporation 430FX - 82437FX TSC [Triton I] (rev 02)
00:07.0 ISA bridge: Intel Corporation 82371FB PIIX ISA [Triton I] (rev 02)
00:08.0 VGA compatible controller: S3 Inc. 86c764/765 [Trio32/64/64V+]
00:11.0 Ethernet controller: Advanced Micro Devices [AMD] 79c970 [PCnet
LANCE] (rev 16)
IDE/ATA part of my .config:
CONFIG_BLK_DEV_IDE=y
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_BLK_DEV_IDEPCI=y
# CONFIG_BLK_DEV_IDEDMA_PCI is not set
CONFIG_BLK_DEV_IDEDMA_PCI and CONFIG_BLK_DEV_PIIX were set in 2.5.9-dj1 but
that generated the same problem.
Rudmer
next prev parent reply other threads:[~2002-04-28 11:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-27 3:08 Dave Jones
2002-04-27 5:32 ` A Guy Called Tyketto
2002-04-27 12:51 ` Rudmer van Dijk
2002-04-27 13:51 ` Dave Jones
2002-04-28 11:45 ` Rudmer van Dijk [this message]
2002-04-28 19:53 ` Alexander Hoogerhuis
2002-04-28 20:38 ` Dave Jones
2002-04-28 22:47 ` Vojtech Pavlik
2002-04-28 20:49 ` Rudmer van Dijk
2002-04-28 23:51 ` ext2 free blocks count corrupted (was Re: Linux 2.5.10-dj1) Petr Vandrovec
2002-04-29 1:26 ` Linux 2.5.10-dj1 Chris Wright
2002-04-27 18:34 ` Adrian Bunk
2002-04-27 18:46 ` Dave Jones
2002-04-29 9:14 ` Adrian Bunk
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=200204281145.g3SBjJJ20178@smtp2.wanadoo.nl \
--to=rudmer@legolas.dynup.net \
--cc=davej@suse.de \
--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
all inboxes | Powered by JetHome®