KERNEL PANIC in 2.2.17 and 2.2.18

KERNEL PANIC in 2.2.17 and 2.2.18

Post by ouao » Sat, 30 Dec 2000 09:21:01



Hi,

I got a strange crash, totally unpredictable, several times, while using
linux kernel 2.2.17 and 2.2.18.

kernel: CPU 0: Machine Check Exception: 0000000000000004
kernel: Bank 1: b200000000000115<0>Kernel panic: CPU context corrupt

I checked on the linux kernel mailing list archives but found nothing
about it.
Here's my configuration:

Celeron 333 overclocked to 416 (5 x 83Mhz).
128 Megs of PC100 SDRAM
DC390 U2W SCSI adaptor
ATI RAGE XL AGP
ISA SB16
NE2000 PCI

The config file for 2.2.17 is there as attachement.

What is very strange is that it just worked very well on 2.2.16 (so for
the moment I stick to it).

If you happened to have had the same problem or know an explanation,
please contact me.

Thanks.
--
ouaou! fait le ouaou

[ linux-2.2.17.config 13K ]
#
# Automatically generated by make menuconfig: don't edit
#

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y

#
# Processor type and features
#
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
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_2GB is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_SMP is not set

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODVERSIONS=y
CONFIG_KMOD=y

#
# General setup
#
CONFIG_NET=y
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_QUIRKS=y
CONFIG_PCI_OPTIMIZE=y
CONFIG_PCI_OLD_PROC=y
# CONFIG_MCA is not set
# CONFIG_VISWS is not set
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
CONFIG_BINFMT_AOUT=m
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=y
# CONFIG_BINFMT_JAVA is not set
CONFIG_PARPORT=y
CONFIG_PARPORT_PC=y
# CONFIG_PARPORT_OTHER is not set
CONFIG_APM=y
# CONFIG_APM_IGNORE_USER_SUSPEND is not set
CONFIG_APM_DO_ENABLE=y
CONFIG_APM_CPU_IDLE=y
CONFIG_APM_DISPLAY_BLANK=y
# CONFIG_APM_IGNORE_SUSPEND_BOUNCE is not set
CONFIG_APM_RTC_IS_GMT=y
# CONFIG_APM_ALLOW_INTS is not set
CONFIG_APM_REAL_MODE_POWER_OFF=y
# CONFIG_TOSHIBA is not set

#
# Plug and Play support
#
# CONFIG_PNP is not set

#
# Block devices
#
CONFIG_BLK_DEV_FD=y
CONFIG_BLK_DEV_IDE=y
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=m
CONFIG_BLK_DEV_IDECD=m
CONFIG_BLK_DEV_IDETAPE=m
CONFIG_BLK_DEV_IDEFLOPPY=m
CONFIG_BLK_DEV_IDESCSI=m
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_VIA82C586 is not set
# CONFIG_BLK_DEV_CMD646 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_IDE_CHIPSETS is not set
CONFIG_BLK_DEV_LOOP=m
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_MD is not set
CONFIG_BLK_DEV_RAM=m
CONFIG_BLK_DEV_RAM_SIZE=4096
# CONFIG_BLK_DEV_XD is not set
# CONFIG_BLK_DEV_DAC960 is not set
CONFIG_PARIDE_PARPORT=y
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_DEV_HD is not set

#
# Networking options
#
CONFIG_PACKET=y
CONFIG_NETLINK=y
CONFIG_RTNETLINK=y
CONFIG_NETLINK_DEV=y
CONFIG_FIREWALL=y
# CONFIG_FILTER is not set
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_RTNETLINK=y
CONFIG_NETLINK=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_TOS=y
CONFIG_IP_ROUTE_VERBOSE=y
# CONFIG_IP_ROUTE_LARGE_TABLES is not set
# CONFIG_IP_ROUTE_NAT is not set
# CONFIG_IP_PNP is not set
CONFIG_IP_FIREWALL=y
CONFIG_IP_FIREWALL_NETLINK=y
CONFIG_NETLINK_DEV=y
CONFIG_IP_ROUTE_FWMARK=y
CONFIG_IP_TRANSPARENT_PROXY=y
CONFIG_IP_MASQUERADE=y
CONFIG_IP_MASQUERADE_ICMP=y
CONFIG_IP_MASQUERADE_MOD=y
CONFIG_IP_MASQUERADE_IPAUTOFW=m
CONFIG_IP_MASQUERADE_IPPORTFW=m
CONFIG_IP_MASQUERADE_MFW=m
# CONFIG_IP_ROUTER is not set
CONFIG_NET_IPIP=m
CONFIG_NET_IPGRE=m
CONFIG_NET_IPGRE_BROADCAST=y
CONFIG_IP_MROUTE=y
CONFIG_IP_PIMSM_V1=y
CONFIG_IP_PIMSM_V2=y
CONFIG_IP_ALIAS=y
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
# CONFIG_INET_RARP is not set
CONFIG_SKB_LARGE=y
# CONFIG_IPV6 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_BRIDGE is not set
# CONFIG_LLC is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_FASTROUTE is not set
# CONFIG_NET_HW_FLOWCONTROL is not set
# CONFIG_CPU_IS_SLOW is not set

#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set
# CONFIG_PHONE_IXJ is not set

#
# SCSI support
#
CONFIG_SCSI=y
CONFIG_BLK_DEV_SD=y
CONFIG_CHR_DEV_ST=m
CONFIG_BLK_DEV_SR=y
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=y
CONFIG_SCSI_MULTI_LUN=y
# CONFIG_SCSI_CONSTANTS is not set
CONFIG_SCSI_LOGGING=y

#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_7000FASST is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AHA152X is not set
# CONFIG_SCSI_AHA1542 is not set
# CONFIG_SCSI_AHA1740 is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_IN2000 is not set
# CONFIG_SCSI_AM53C974 is not set
# CONFIG_SCSI_MEGARAID is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_DTC3280 is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_DMA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_GENERIC_NCR5380 is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not set
# CONFIG_SCSI_NCR53C406A is not set
# CONFIG_SCSI_SYM53C416 is not set
# CONFIG_SCSI_SIM710 is not set
# CONFIG_SCSI_NCR53C7xx is not set
# CONFIG_SCSI_NCR53C8XX is not set
CONFIG_SCSI_SYM53C8XX=y
CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS=4
CONFIG_SCSI_NCR53C8XX_MAX_TAGS=32
CONFIG_SCSI_NCR53C8XX_SYNC=40
# CONFIG_SCSI_NCR53C8XX_PROFILE is not set
# CONFIG_SCSI_NCR53C8XX_IOMAPPED is not set
# CONFIG_SCSI_NCR53C8XX_PQS_PDS is not set
# CONFIG_SCSI_NCR53C8XX_SYMBIOS_COMPAT is not set
# CONFIG_SCSI_PAS16 is not set
# CONFIG_SCSI_PCI2000 is not set
# CONFIG_SCSI_PCI2220I is not set
# CONFIG_SCSI_PSI240I is not set
# CONFIG_SCSI_QLOGIC_FAS is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_SEAGATE is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_T128 is not set
# CONFIG_SCSI_U14_34F is not set
# CONFIG_SCSI_ULTRASTOR is not set
# CONFIG_SCSI_DEBUG is not set

#
# I2O device support
#
# CONFIG_I2O is not set
# CONFIG_I2O_PCI is not set
# CONFIG_I2O_BLOCK is not set
# CONFIG_I2O_SCSI is not set

#
# Network device support
#
CONFIG_NETDEVICES=y

#
# ARCnet devices
#
# CONFIG_ARCNET is not set
CONFIG_DUMMY=m
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_ETHERTAP is not set
# CONFIG_NET_SB1000 is not set

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set
# CONFIG_RTL8139 is not set
# CONFIG_NET_ISA is not set
CONFIG_NET_EISA=y
# CONFIG_PCNET32 is not set
# CONFIG_AC3200 is not set
# CONFIG_APRICOT is not set
# CONFIG_CS89x0 is not set
# CONFIG_DM9102 is not set
# CONFIG_DE4X5 is not set
# CONFIG_DEC_ELCP is not set
# CONFIG_DEC_ELCP_OLD is not set
# CONFIG_DGRS is not set
# CONFIG_EEXPRESS_PRO100 is not set
# CONFIG_LNE390 is not set
# CONFIG_NE3210 is not set
CONFIG_NE2K_PCI=y
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_SIS900 is not set
# CONFIG_ES3210 is not set
# CONFIG_EPIC100 is not set
# CONFIG_ZNET is not set
# CONFIG_NET_POCKET is not set

#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_SK98LIN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
CONFIG_PLIP=m
CONFIG_PPP=y
# CONFIG_SLIP is not set
# CONFIG_NET_RADIO is not set

#
# Token ring devices
#
# CONFIG_TR is not set
# CONFIG_NET_FC is not set
# CONFIG_RCPCI is not set
CONFIG_SHAPER=m

#
# Wan interfaces
#
# CONFIG_HOSTESS_SV11 is not set
# CONFIG_COSA is not set
# CONFIG_SEALEVEL_4021 is not set
# CONFIG_SYNCLINK_SYNCPPP is not set
# CONFIG_LANMEDIA is not set
# CONFIG_COMX is not set
# CONFIG_HDLC is not set
# CONFIG_DLCI is not set
# CONFIG_SBNI is not set

#
# Amateur Radio support
#
# CONFIG_HAMRADIO is not set

#
# IrDA (infrared) support
#
# CONFIG_IRDA is not set

#
# ISDN subsystem
#
# CONFIG_ISDN is not set

#
# Old CD-ROM drivers (not SCSI, not IDE)
#
# CONFIG_CD_NO_IDESCSI is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_SERIAL=y
CONFIG_SERIAL_CONSOLE=y
# CONFIG_SERIAL_EXTENDED is not set
# CONFIG_SERIAL_NONSTANDARD is not set
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=512
CONFIG_PRINTER=m
CONFIG_PRINTER_READBACK=y
CONFIG_MOUSE=y

#
# Mice
#
# CONFIG_ATIXL_BUSMOUSE is not set
# CONFIG_BUSMOUSE is not set
# CONFIG_MS_BUSMOUSE is not set
CONFIG_PSMOUSE=y
# CONFIG_82C710_MOUSE is not set
# CONFIG_PC110_PAD is not set

#
# Joysticks
#
CONFIG_JOYSTICK=m
CONFIG_JOY_ANALOG=m
# CONFIG_JOY_ASSASSIN is not set
# CONFIG_JOY_GRAVIS is not set
# CONFIG_JOY_LOGITECH is not set
# CONFIG_JOY_SIDEWINDER is not set
# CONFIG_JOY_THRUSTMASTER is not set
# CONFIG_JOY_CREATIVE is not set
# CONFIG_JOY_LIGHTNING is not set
# CONFIG_JOY_PCI is not set
# CONFIG_JOY_MAGELLAN is not set
# CONFIG_JOY_SPACEORB is not set
# CONFIG_JOY_SPACEBALL is not set
# CONFIG_JOY_WARRIOR is not set
# CONFIG_JOY_CONSOLE is not set
# CONFIG_JOY_DB9 is not set
# CONFIG_JOY_TURBOGRAFX is not set
# CONFIG_QIC02_TAPE is not set
CONFIG_WATCHDOG=y

#
# Watchdog Cards
#
CONFIG_WATCHDOG_NOWAYOUT=y
# CONFIG_WDT is not set
CONFIG_SOFT_WATCHDOG=m
# CONFIG_PCWATCHDOG is not set
# CONFIG_ACQUIRE_WDT is not set
# CONFIG_60XX_WDT is not set
# CONFIG_MIXCOMWD is not set
CONFIG_NVRAM=m
CONFIG_RTC=y

#
# Video For Linux
#
# CONFIG_VIDEO_DEV is not set
# CONFIG_DTLK is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set

#
# Filesystems
#
CONFIG_QUOTA=y
CONFIG_AUTOFS_FS=m
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
CONFIG_HFS_FS=m
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_UMSDOS_FS=m
CONFIG_VFAT_FS=y
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_MINIX_FS=m
# CONFIG_NTFS_FS is not set
# CONFIG_HPFS_FS is not set
CONFIG_PROC_FS=y
CONFIG_DEVPTS_FS=y
# CONFIG_QNX4FS_FS is not set
# CONFIG_ROMFS_FS is not set
CONFIG_EXT2_FS=y
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
# CONFIG_EFS_FS is not set

#
# Network File Systems
#
CONFIG_CODA_FS=m
CONFIG_NFS_FS=y
# ...

read more »

 
 
 

KERNEL PANIC in 2.2.17 and 2.2.18

Post by ouao » Sat, 30 Dec 2000 09:25:10



> Hi,

> I got a strange crash, totally unpredictable, several times, while using
> linux kernel 2.2.17 and 2.2.18.

> kernel: CPU 0: Machine Check Exception: 0000000000000004
> kernel: Bank 1: b200000000000115<0>Kernel panic: CPU context corrupt

> I checked on the linux kernel mailing list archives but found nothing
> about it.
> Here's my configuration:

> Celeron 333 overclocked to 416 (5 x 83Mhz).
> 128 Megs of PC100 SDRAM
> DC390 U2W SCSI adaptor
> ATI RAGE XL AGP
> ISA SB16
> NE2000 PCI

I forgot to write that the mobo is an Abit BH6 1.0

--
ouaou! fait le ouaou

 
 
 

KERNEL PANIC in 2.2.17 and 2.2.18

Post by Juergen Hein » Sat, 30 Dec 2000 09:37:36




>> Hi,

>> I got a strange crash, totally unpredictable, several times, while using
>> linux kernel 2.2.17 and 2.2.18.

>> kernel: CPU 0: Machine Check Exception: 0000000000000004
>> kernel: Bank 1: b200000000000115<0>Kernel panic: CPU context corrupt
[-]
>> Celeron 333 overclocked to 416 (5 x 83Mhz).

[-]
Try without running it beyond its specs.
 
 
 

KERNEL PANIC in 2.2.17 and 2.2.18

Post by Robert Redelmeie » Sat, 30 Dec 2000 13:36:36



> > I got a strange crash, totally unpredictable, several times, while
> > using linux kernel 2.2.17 and 2.2.18.

> > kernel: CPU 0: Machine Check Exception: 0000000000000004
> > kernel: Bank 1: b200000000000115<0>Kernel panic: CPU context corrupt

> > I checked on the linux kernel mailing list archives but found
> > nothing about it. Here's my configuration:

> > Celeron 333 overclocked to 416 (5 x 83Mhz).
> > 128 Megs of PC100 SDRAM
> > DC390 U2W SCSI adaptor
> > ATI RAGE XL AGP
> > ISA SB16
> > NE2000 PCI

Overclockers get very little attention from kernel developers,
right so IMHO and I overclock too.

The point is your hardware is being driven beyond it's specs
and can be expected to fail in interesting and puzzling ways.
The kernel guys have enough trouble chasing their real bugs
without ghosts and electronic gremlins.

One thing, your 5 * 83 MHz overclock is IMHO a fairly error
prone and dangerous speed.  The PCI bus will be at 41.7 MHz
which is 'way beyond spec (33).  Your SCSI adapter or AGP
card might be unhappy.  Or that NE2k.

In any case, it's up to _you_ to prove that your hardware
is stable at your selected speed.  This is not an easy task.
You can run md5sums on an unmounted partition.  I wrote
`burnP6`, `burnBX` and `burnMMX` asm testing utilities
to test CPUs,  memory and controllers.  You might find
them useful.

-- Robert  author `cpuburn`  http://users.ev1.net/~redelm

 
 
 

KERNEL PANIC in 2.2.17 and 2.2.18

Post by Hal R. Bran » Sun, 31 Dec 2000 12:11:42




> > > I got a strange crash, totally unpredictable, several times, while
> > > using linux kernel 2.2.17 and 2.2.18.

> > > kernel: CPU 0: Machine Check Exception: 0000000000000004
> > > kernel: Bank 1: b200000000000115<0>Kernel panic: CPU context corrupt

> > > I checked on the linux kernel mailing list archives but found
> > > nothing about it. Here's my configuration:

> > > Celeron 333 overclocked to 416 (5 x 83Mhz).
> > > 128 Megs of PC100 SDRAM
> > > DC390 U2W SCSI adaptor
> > > ATI RAGE XL AGP
> > > ISA SB16
> > > NE2000 PCI

> Overclockers get very little attention from kernel developers,
> right so IMHO and I overclock too.

> The point is your hardware is being driven beyond it's specs
> and can be expected to fail in interesting and puzzling ways.
> The kernel guys have enough trouble chasing their real bugs
> without ghosts and electronic gremlins.

> One thing, your 5 * 83 MHz overclock is IMHO a fairly error
> prone and dangerous speed.  The PCI bus will be at 41.7 MHz
> which is 'way beyond spec (33).  Your SCSI adapter or AGP
> card might be unhappy.  Or that NE2k.

> In any case, it's up to _you_ to prove that your hardware
> is stable at your selected speed.  This is not an easy task.
> You can run md5sums on an unmounted partition.  I wrote
> `burnP6`, `burnBX` and `burnMMX` asm testing utilities
> to test CPUs,  memory and controllers.  You might find
> them useful.

> -- Robert  author `cpuburn`  http://users.ev1.net/~redelm

OK, How about my first Linux kernel crash going back to
something like kernel 0.22. This is on a ASUS P2B (BX chipset)
running a Celeron 566 at specs (66 MHz FSB) with PC100 memory
and kernel 2.2.18. If anything, I'm underclocking the MB and
memory. Might just be my CPU dying, then again, might be
something real starting to show up. And, no, I didn't have a
crash while running 2.2.17 (which I ran pretty much from the
time it was released till the release of 2.2.18).

Kernel 2.2.18
Dec 26 20:38:27 c995785-b kernel: CPU 0: Machine Check Exception:
0000000000000004
Dec 26 20:38:27 c995785-b kernel: Bank 4: b200000000040151<0>Kernel panic: CPU
context corrupt

Full hardware and software specs available on request.
--
//*****************
// Hal Brand

//*****************

 
 
 

KERNEL PANIC in 2.2.17 and 2.2.18

Post by Robert Redelmeie » Sun, 31 Dec 2000 13:21:44



> OK, How about my first Linux kernel crash going back to
> something like kernel 0.22. This is on a ASUS P2B (BX chipset)
> running a Celeron 566 at specs (66 MHz FSB) with PC100 memory
> and kernel 2.2.18. If anything, I'm underclocking the MB and
> memory. Might just be my CPU dying, then again, might be
> something real starting to show up. And, no, I didn't have a
> crash while running 2.2.17 (which I ran pretty much from the
> time it was released till the release of 2.2.18).

> Kernel 2.2.18
> Dec 26 20:38:27 c995785-b kernel: CPU 0: Machine Check Exception:
> 0000000000000004
> Dec 26 20:38:27 c995785-b kernel: Bank 4: b200000000040151<0>
> Kernel panic: CPU context corrupt

This is far more interesting to kernel developers, particularly
if it's reproducible.  The basic dividing rule is that software
faults are reproducible [sometimes by a odd set of activities]
while hardware faults are not reproducible.  Not a perfect rule,
but a good starting point.

In your case, I would take the kernel at it's word and start
to look for memory faults.  Run memtest-86 at least overnight.
You could also try my `burnBX` or `burnMMX` in the larger sizes.

Quote:> Full hardware and software specs available on request.

The Asus P2B is a nice board, but there are lots of builder
issues:  grease on the CPU, good SDRAM, good power supply,
adequate mobo and case cooling, too hot a vidcard, etc.

-- Robert  author `cpuburn`  http://users.ev1.net/~redelm

 
 
 

KERNEL PANIC in 2.2.17 and 2.2.18

Post by Peter T. Breue » Sun, 31 Dec 2000 16:35:20




>> OK, How about my first Linux kernel crash going back to
>> something like kernel 0.22. This is on a ASUS P2B (BX chipset)
>> running a Celeron 566 at specs (66 MHz FSB) with PC100 memory
>> and kernel 2.2.18. If anything, I'm underclocking the MB and

I'm also running this board (plus onboard scsi). Haven't seen that
problem. I was running a celeron 700 at 75MHz pci. No problems.

It does have a tsc problem now that I have two PIII 550's in.
The cpu's seem to have their system clocks about 4 seconds off from one
another.

I have tried kernels 2.2.1[578]. Also "notsc" as a kernel parameter.

Quote:>> memory. Might just be my CPU dying, then again, might be
>> something real starting to show up. And, no, I didn't have a
>> crash while running 2.2.17 (which I ran pretty much from the
>> time it was released till the release of 2.2.18).

>> Kernel 2.2.18
>> Dec 26 20:38:27 c995785-b kernel: CPU 0: Machine Check Exception:
>> 0000000000000004
>> Dec 26 20:38:27 c995785-b kernel: Bank 4: b200000000040151<0>
>> Kernel panic: CPU context corrupt
> The Asus P2B is a nice board, but there are lots of builder
> issues:  grease on the CPU, good SDRAM, good power supply,
> adequate mobo and case cooling, too hot a vidcard, etc.

Peter