Re: Crash & corrupted FS

Jim Bauer (jfbauer@home.com)
Mon, 10 Apr 2000 00:42:58 -0400

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Eric W. Biederman: "Re: Suggested dual human/binary interface for proc/devfs"
Previous message: Scott M. Ransom: "Strange IDE/RAID0 performance...."
Next in thread: Stephen C. Tweedie: "Re: Crash & corrupted FS"
Reply: Stephen C. Tweedie: "Re: Crash & corrupted FS"

I little while ago I wrote:
>I have a Mandrake 7.0 system with the original kernel (2.2.14 + ???).
>It has an Athlon CPU and a IDE disk (Maxtor 92720U8). I had just
>started up the seti@home program and it was running for less than
>5 minutes with the system rebooted. Nothing else was running. I was
>logged in remotely at the time so I wasn't able to see anything on the
>console.
>
>The reboot wasn't entirely successfull. I later noticed the tail end
>of an oops followed by:
>
> code 89 02 85 c0 74 03 89 50 04 b8 01 00 00 00 eb 03 90 31 c0 c7
> Aiee, Killing interrupt handler
> Kernel panic: attempting to kill the idle task
> In interrupt handler - not syncing
>
>I rebooted. During the fsck I got a bunch of errors like
>
> Setting file type for entry '<name>' in <dir> (<ino>) to 6.
>
>Among the files listed were old files in /tmp and a few files in
>/dev (i.e. /dev/printer /dev/gmpctl).
>
>I later noticed being logged after the reboot, error about "access beyond
>end of device". Wasn't that problem fixed a while ago?
>
>Shortly after that everything seemed to die and I could not log back in.
>It looked like the login program kept failing.
>
>I rebooted. The reboot failed right after init started. init complained
>that all the programs were re-spawning too fast.
>
>I rebooted off of the CD/floppy and tried to repair the filesystems.
>I think the non-root ones were ok, but root was a mess. It complained
>about block number being too large and that the FS had large files without
>the large files flag set in the super block. I through caution to the
>wind and told fsck to try and fix everything.
>
>fsck was happy I guess. However, the kernel could never find init after
>that. I even tried a few choices for "init=", not no luck.
>
>I reinstalled from the CD. I went to re-create the original problem
>with runing seti@home. After a few minutes, some message (without a newline)
>kept scrolling across the screen. I was unable to read it. The system
>then rebooted and had similar FS problems ("Setting filetype for ...").
>
>Any suggestions? There is nothing important on that system right now,
>so I am willing to do any needed testing.

Bit more info. Problem is repeatable on a plain 2.2.14 kernel. The
message that was scrolling by too fast to read was "Unable to handle
kernel paging request". SysRq dosn't work once the problem starts.
Also if it means anything, the system dosn not identify the correct
amount of memory. Says 64M really 256M. mem=256M does work.

It also failed on 2.3.99-pre3, but it took almost twice as long to do so.
I did manage to catch an oops with this. I had to type it in as it didn't
get logged, so beware of typos. I still have a jpg of the screen if anyone
wants it.

No modules in ksyms, skipping objects
Unable to handle kernel NULL pointer dereference at virtual address 00000018
c0135bd5
*pde = 00000000
Oops: 0002
CPU: 0
EIP: 0010:[<c0135bd5>]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010202
eax: 00000010 ebx: 00000010 ecx: ccf8b328 edx: cfd8dcc8
esi: 00000000 edi: 00000000 ebp: 00000001 esp: cfdb3e38
ds: 0018 es: 0018 ss: 0018
Process klogd (pid: 363, stackpage=cfdb3000)
Stack: ccf8b1a0 c0140a72 00000010 ccf8b1a0 c01412f1 ccf8b1a0 cd57d220 ccf8b1a0
cd57d220 c013f696 ccf8b1a0 c15a0e60 ccf8b1a0 c012fe4e cd57d220 c15a0e60
cd57d220 00000000 c012fe71 c15a0e60 c15a0e60 c15a0e60 c012ef6d c15a0e60
Call Trace: [<c0140a72>] [<c01412f1>] [<c013f696>] [<c012fe4e>] [<c012fe71>] [<c012ef6d>] [<c011c128>]
[<c010b422>] [<c0112ecc>] [<c01f8e5e>] [<c01e1e4a>] [<c0115077>] [<c010b09d>]
Code: ff 4b 00 0f 94 c0 84 74 41 83 7b 10 00 74 1b 68 aa 01 00

>>EIP; c0135bd5 <bdput+5/60> <=====
Trace; c0140a72 <clear_inode+b2/d0>
Trace; c01412f1 <iput+141/240>
Trace; c013f696 <dput+a6/160>
Trace; c012fe4e <__fput+3e/50>
Trace; c012fe71 <_fput+11/40>
Trace; c012ef6d <filp_close+5d/70>
Trace; c011c128 <do_exit+1b8/350>
Trace; c010b422 <die+42/50>
Trace; c0112ecc <do_page_fault+39c/4a0>
Trace; c01f8e5e <acpi_pci_tbl+272e/5aa0>
Trace; c01e1e4a <unix_dgram_sendmsg+2ba/320>
Trace; c0115077 <schedule+267/3d0>
Trace; c010b09d <error_code+2d/34>
Code; c0135bd5 <bdput+5/60>
00000000 <_EIP>:
Code; c0135bd5 <bdput+5/60> <=====
0: ff 4b 00 decl 0x0(%ebx) <=====
Code; c0135bd8 <bdput+8/60>
3: 0f 94 c0 sete %al
Code; c0135bdb <bdput+b/60>
6: 84 74 41 83 test %dh,0xffffff83(%ecx,%eax,2)
Code; c0135bdf <bdput+f/60>
a: 7b 10 jnp 1c <_EIP+0x1c> c0135bf1 <bdput+21/60>
Code; c0135be1 <bdput+11/60>
c: 00 74 1b 68 add %dh,0x68(%ebx,%ebx,1)
Code; c0135be5 <bdput+15/60>
10: aa stos %al,%es:(%edi)
Code; c0135be6 <bdput+16/60>
11: 01 00 add %eax,(%eax)

Here is the config for the 2.3.99-pre3 kernel.

CONFIG_X86=y
CONFIG_ISA=y
CONFIG_UID16=y
CONFIG_MK7=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_L1_CACHE_BYTES=32
CONFIG_X86_TSC=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_USE_3DNOW=y
CONFIG_X86_PGE=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_NOHIGHMEM=y
CONFIG_MTRR=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_MODULES=y
CONFIG_MODVERSIONS=y
CONFIG_KMOD=y
CONFIG_NET=y
CONFIG_PCI=y
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_NAMES=y
CONFIG_HOTPLUG=y
CONFIG_SYSVIPC=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_SYSCTL=y
CONFIG_KCORE_ELF=y
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=y
CONFIG_PM=y
CONFIG_ACPI=y
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
CONFIG_PNP=y
CONFIG_ISAPNP=y
CONFIG_BLK_DEV_FD=y
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_RAM=m
CONFIG_PACKET=y
CONFIG_NETFILTER=y
CONFIG_FILTER=y
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ALIAS=y
CONFIG_SYN_COOKIES=y
CONFIG_SKB_LARGE=y
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_BLK_DEV_IDECD=y
CONFIG_BLK_DEV_CMD640=y
CONFIG_BLK_DEV_RZ1000=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_IDE_MODES=y
CONFIG_NETDEVICES=y
CONFIG_DUMMY=m
CONFIG_NET_ETHERNET=y
CONFIG_NET_VENDOR_3COM=y
CONFIG_VORTEX=y
CONFIG_NET_PCI=y
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_SERIAL=y
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
CONFIG_MOUSE=y
CONFIG_PSMOUSE=y
CONFIG_DRM=y
CONFIG_DRM_TDFX=y
CONFIG_AUTOFS_FS=y
CONFIG_AUTOFS4_FS=y
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_PROC_FS=y
CONFIG_DEVPTS_FS=y
CONFIG_EXT2_FS=y
CONFIG_NFS_FS=y
CONFIG_NFSD=y
CONFIG_SUNRPC=y
CONFIG_LOCKD=y
CONFIG_MSDOS_PARTITION=y
CONFIG_NLS=y
CONFIG_NLS_CODEPAGE_437=m
CONFIG_NLS_ISO8859_1=m
CONFIG_VGA_CONSOLE=y
CONFIG_SOUND=m
CONFIG_SOUND_OSS=m
CONFIG_SOUND_TRACEINIT=y
CONFIG_SOUND_SB=m
CONFIG_MAGIC_SYSRQ=y

-- Jim Bauer, jfbauer@home.com

- 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/

Next message: Eric W. Biederman: "Re: Suggested dual human/binary interface for proc/devfs"
Previous message: Scott M. Ransom: "Strange IDE/RAID0 performance...."
Next in thread: Stephen C. Tweedie: "Re: Crash & corrupted FS"
Reply: Stephen C. Tweedie: "Re: Crash & corrupted FS"