Hi all!
After compiling a kernel, it seems some program dumped core on me; when I
tried to find out which program dumped core on me, I did a 'file core', which
raised the system load to 100%, and resulted in a process in some stuck
state.
I 'kill -9'd it, and tried again; this time it had another process in a
stuck state. Tired of this coredump I tried to remove it from my system,
before killing the 'file' process. This lead to a locked system.
The kernel still seems to be working though, pings are responded to, and the
to NICs inside do bridge traffic. The tcp/ip stack was also responding to
packets.
I'm going to reboot right now (o, how I love fsck's), and if the coredump
is still there, I'm going to try to reproduce this problem.
This all happened on a machine with the following hardware:
Dual P-II 350, 256 MB Ram, Intel PIIX4 chipset; 1 IDE HDD, 1 IDE CD-ROM, one
PCI NE2k-clone, one PCI RT8029 NIC, a [PCI] Ensoniq 1370 sound card a [PCI]
FlyVideo'98 videograbber and an AGP Matrox G200 Mystique, running a vanilla
2.3.12-SMP-kernel without a driver for the videograbber, but with all other
devices active. A .config is attached
It could have been flakey hardware, because of high temperatures, but this
machine never experienced any problems, and doesn't seem to be too hot.
After reboot, I'm able to 'file' the coredump.
Oh, and it seems there's something in the logs:
kernel: kmem_alloc: Bad slab magic (corrupt) (name=buffer_head)
That's all,
VrGr,
--
__ ___ __ C. Jasper Spaans <cj@dds.nl> -o)
/ //__ /\\
/__ __/ __/ _\_v
join the penguin force!
22:48pm up 8203 days, 14:35, 1 user, load average: 0.00, 0.00, 0.00
--a8Wt8u1KmwUX3Y2C
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename=config
CONFIG_EXPERIMENTAL=y
CONFIG_M686=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_X86_GOOD_APIC=y
CONFIG_1GB=y
CONFIG_MTRR=y
CONFIG_SMP=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_QUIRKS=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_SYSVIPC=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_SYSCTL=y
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=y
CONFIG_APM=y
CONFIG_APM_POWER_OFF=y
CONFIG_I2O=y
CONFIG_I2O_PCI=y
CONFIG_I2O_PROC=y
CONFIG_BLK_DEV_FD=y
CONFIG_BLK_DEV_IDE=y
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_BLK_DEV_IDECD=m
CONFIG_BLK_DEV_IDESCSI=m
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_BLK_DEV_PIIX=y
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_NBD=y
CONFIG_PARIDE_PARPORT=y
CONFIG_BLK_DEV_IDE_MODES=y
CONFIG_PACKET=y
CONFIG_NETLINK=y
CONFIG_RTNETLINK=y
CONFIG_NETLINK_DEV=y
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ALIAS=y
CONFIG_SKB_LARGE=y
CONFIG_IPV6=y
CONFIG_BRIDGE=y
CONFIG_SCSI=m
CONFIG_BLK_DEV_SR=m
CONFIG_CHR_DEV_SG=m
CONFIG_NETDEVICES=y
CONFIG_DUMMY=m
CONFIG_ETHERTAP=m
CONFIG_NET_ETHERNET=y
CONFIG_RTL8139=m
CONFIG_NET_EISA=y
CONFIG_NE2K_PCI=m
CONFIG_PPP=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_RTC=y
CONFIG_VIDEO_DEV=m
CONFIG_VIDEO_BT848=m
CONFIG_USB=y
CONFIG_USB_UHCI=y
CONFIG_USB_HUB=y
CONFIG_USB_MOUSE=y
CONFIG_USB_KBD=y
CONFIG_USB_AUDIO=y
CONFIG_USB_ACM=y
CONFIG_USB_PRINTER=y
CONFIG_USB_PROC=y
CONFIG_QUOTA=y
CONFIG_AUTOFS_FS=y
CONFIG_FAT_FS=y
CONFIG_MSDOS_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_SMB_FS=y
CONFIG_NLS=y
CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_CODEPAGE_850=y
CONFIG_NLS_ISO8859_1=y
CONFIG_NLS_ISO8859_15=y
CONFIG_VIDEO_SELECT=y
CONFIG_FB=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_VIDEO_SELECT=y
CONFIG_FB_MATROX=y
CONFIG_FB_MATROX_G100=y
CONFIG_FBCON_CFB8=y
CONFIG_FBCON_CFB16=y
CONFIG_FBCON_CFB24=y
CONFIG_FBCON_CFB32=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_SOUND=y
CONFIG_SOUND_ES1370=y
--a8Wt8u1KmwUX3Y2C--
-
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/