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 ?
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_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.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/