Messages in this thread | | | Date | Mon, 31 Jan 2000 00:09:29 +0100 | From | Simen <> | Subject | Kernel BUG at file.c |
| |
Today I received 3 times this message :
Jan 30 23:28:33 simens kernel: kernel BUG at file.c:92! Jan 30 23:28:33 simens kernel: invalid operand: 0000 Jan 30 23:28:33 simens kernel: CPU: 0 Jan 30 23:28:33 simens kernel: EIP: 0010:[fat_get_block+96/220] Jan 30 23:28:33 simens kernel: EFLAGS: 00010282 Jan 30 23:28:33 simens kernel: eax: 00000019 ebx: 00000000 ecx: 00000014 edx: 00000027 Jan 30 23:28:33 simens kernel: esi: 00000000 edi: c351e2e0 ebp: c3bb8600 esp: c3c0be20 Jan 30 23:28:33 simens kernel: ds: 0018 es: 0018 ss: 0018 Jan 30 23:28:33 simens kernel: Process wine (pid: 3364, stackpage=c3c0b000) Jan 30 23:28:33 simens kernel: Stack: c01f64c7 c01f6647 0000005c 00000000 c3c0be90 00000200 00000000 c3c0bf38 Jan 30 23:28:33 simens kernel: c012c0e1 c351e2e0 00000000 c3bb8600 00000001 00000000 00004000 00000000 Jan 30 23:28:33 simens kernel: 00000000 c0232f00 c014979c c0b77000 c3bb8600 c3c0be90 00000200 00000000 Jan 30 23:28:33 simens kernel: Call Trace: [cprt+20199/76374] [cprt+20583/76374] [block_write_zero_range+313/864] [fat_get_block+0/220] [block_write_cont_page+198/220] [fat_write_partial_page+0/172] [fat_write_partial_page+160/172] Jan 30 23:28:33 simens kernel: [fat_write_partial_page+0/172] [generic_file_write+688/964] [default_fat_file_write+35/88] [fat_write_partial_page+0/172] [fat_file_write+37/44] [sys_write+184/216] [system_call+52/56] Jan 30 23:28:33 simens kernel: Code: 0f 0b 83 c4 0c b8 fb ff ff ff eb 69 8b 47 74 0f b7 48 58 89
It (as you can see from the Oops happened running WINE) it happened when I ran the windows netscape with wine and after a while, wine stopped responding and I had to stop it with Ctrl-C. The behaviour of other things was just file and the machine seems to not be affected. Maybe it has something to do with the FAT filesystem (as are the functions in the oops and actually the netscape binary was on my windows fat drive and surely made writes to it ). I've seen a similar bug message posted today on this list, but it had something to do with the ethernet card, but seemd pretty the same.
I'm running RedHat6.1 on an AMD K6 200, with 64MB ram, no SCSI, just an 4.3 GB IDE hd,. kernel 2.3.41
here is my .config (i removed all the uncommented lines, to save some space):
CONFIG_X86=y CONFIG_ISA=y CONFIG_UID16=y
CONFIG_EXPERIMENTAL=y
CONFIG_MK6=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_TSC=y CONFIG_NOHIGHMEM=y
CONFIG_MODULES=y
CONFIG_NET=y CONFIG_PCI=y CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y CONFIG_PCI_NAMES=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_PNP=y CONFIG_ISAPNP=y
CONFIG_BLK_DEV_FD=y CONFIG_BLK_DEV_IDE=y
CONFIG_BLK_DEV_IDEDISK=y CONFIG_BLK_DEV_IDECD=y
CONFIG_BLK_DEV_IDEPCI=y CONFIG_BLK_DEV_IDEDMA_PCI=y CONFIG_IDEDMA_PCI_AUTO=y
CONFIG_IDEDMA_PCI_EXPERIMENTAL=y CONFIG_BLK_DEV_IDEDMA=y CONFIG_IDEDMA_AUTO=y
CONFIG_BLK_DEV_NBD=y
CONFIG_PACKET=y CONFIG_PACKET_MMAP=y CONFIG_NETLINK=y CONFIG_NETLINK_DEV=m CONFIG_UNIX=y CONFIG_INET=y
CONFIG_NETDEVICES=y
CONFIG_DUMMY=y
CONFIG_NET_ETHERNET=y CONFIG_NET_ISA=y CONFIG_NE2000=m
CONFIG_PPP=m CONFIG_PPP_ASYNC=m CONFIG_PPP_DEFLATE=m CONFIG_PPP_BSDCOMP=m
CONFIG_VT=y CONFIG_VT_CONSOLE=y CONFIG_SERIAL=y CONFIG_UNIX98_PTYS=y CONFIG_UNIX98_PTY_COUNT=256
CONFIG_NVRAM=y
CONFIG_AUTOFS_FS=y CONFIG_AUTOFS4_FS=y CONFIG_FAT_FS=y CONFIG_MSDOS_FS=y CONFIG_UMSDOS_FS=y CONFIG_VFAT_FS=y 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_ISO8859_2=m
CONFIG_VGA_CONSOLE=y CONFIG_VIDEO_SELECT=y
CONFIG_SOUND=m CONFIG_SOUND_OSS=m CONFIG_SOUND_SB=m CONFIG_SOUND_YM3812=m
I compiled my kernel with egcs-2.91.66
Simen Zamecnik
- 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/
| |