For test try to mount you system readonly from floppy and running hdparm
to turn DMA flag on and off.
Vladimir Dergachev
On Wed, 27 Jan 1999, Antti Sinisalo wrote:
>
> Kernel 2.2.0 destroyed filesystem
>
> I tried to upgrade my kernel from version 2.0.34 to 2.2.0, but this
> resulted in destruction of all linux partitions. This has happened
> previously on this same machine as I tested development kernels (2.1.126,
> 2.1.128 and 2.2.0-pre8) using Red Hat 5.0 and Debian hamm. This time I
> first upgraded all the software recommended in Documentation/Changes,
> although it didn't make any difference in the end.
>
> I've never run into this problem using series 2.0-kernels.
>
> For testing, I compiled the kernel as small as possible, with no modules,
> PnP-support or SCSI devices. I only configured it to support ext2- and
> iso9660 filesystems. After booting to new kernel it seemed to work fine,
> but when I ran 'make menuconfig' to configure a kernel with modules to
> work with, the compiler complained about being unable to write to the disk
> because filesystem was mounted read-only, and stopped. Login didn't work
> any more, perhaps because of user data being destroyed. I then rebooted
> the system, which showed many errors about the filesystem being mounted
> read-only.
>
> Bootup stopped in kernel panic:
> ---
> Partition check:
> hda:hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
> hda: set_mutlmode: error=0x04 { DriveStatusError }
> hda1 hda2 < hda5 hda6 hda7 hda8 >
> EXT2-fs error (device 03:06): ext2_check_descriptors: Inode bitmap for
> group 1 not in group (block 0!)
> EXT2-fs: group descriptors corrupted !
> [MS-DOS FS Rel. 12,FAT 0,check=n,conv=b,uid=0,gid=0,umask=022,bmap]
> [me=0x0,cs=0,#f=0,fs=0,fl=0,ds=0,de=0,data=0,se=0,ts=0,ls=0,rc=0,fc=4294967295]
> Transaction block size = 512
> Kernel panic VFS: Unable to mount root fs on 03:06
> ---
>
> By booting into a kernel on floppy I was able to run fsck, which found so
> many errors that I stopped it after ten minutes.
>
> My hardware:
> ---
> AMD K6 233Mhz
> Chaintech 5AGM mainboard with VIA VP3 (82C597AT/82C586B) chipset
> Seagate ST36531A Medalist 6531 IDE hard disk
> ---
>
> This is how I partitioned the disk:
> ---
> /dev/hda1 1 Gt FAT32 (win98)
> /dev/hda5 1 Gt FAT16 (data)
> /dev/hda6 3 Gt ext2 (linux /)
> /dev/hda7 64 Mt (linux swap)
> /dev/hda8 1 Gt ext2 (linux /home)
> ---
>
> And here is some information suggested in REPORTING-BUGS file.
>
> kernel version from /proc/version (this I used to compile 2.2.0)
> ---
> Linux version 2.0.34 (root@greathan) (gcc version 2.7.2.3)
> #2 Thu Jul 9 10:57:48 EST 1998
> ---
>
> output of ver_linux script (again, before compilation of 2.2.0)
> ---
> Linux pahakurki 2.0.34 #2 Thu Jul 9 10:57:48 EST 1998 i586 unknown
> Kernel modules 2.1.121
> Gnu C 2.7.2.3
> Binutils 2.9.1
> Linux C Library 2.0.7
> Dynamic linker ldd: version 1.9.9
> Procps 1.2.9
> Mount 2.7l
> Net-tools (1998-03-02)
> Kbd 0.96
> Sh-utils 1.16
> ---
>
> processor information from /proc/cpuinfo
> ---
> processor : 0
> cpu : 586
> model : 6
> vendor_id : AuthenticAMD
> stepping : 2
> fdiv_bug : no
> hlt_bug : no
> f00f_bug : no
> fpu : yes
> fpu_exception : yes
> cpuid : yes
> wp : yes
> flags : fpu vme de pse tsc msr mce cx8 mmx
> bogomips : 465.31
> ---
>
> No modules, no SCSI devices.
>
> I hope this information is useful to solve the problem. Also, I would be
> interested to hear if anyone else has had problems of this sort, I haven't
> heard of any?
>
> Best wishes,
> --- Antti Sinisalo --------- TNT 9 B114 ------ ____ -----
> --- aesinis@cc.jyu.fi ------ 40740 Jkl ------ / ,. \ ----
> --- www.jyu.fi/~aesinis/ ------------------- | \__/ | ---
> --- +358 400 999 429 ------------------------ \__U_/ ----
> --- +358 14 60 7151 -------------------------------------
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.rutgers.edu
> Please read the FAQ at http://www.tux.org/lkml/
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/