Description of Problem:
Performing a burn-in on a server the kernel Oopsed.
Using ctcs-1.2.5 after approximately 23 hours, the kernel crashed.
Unfortunately I did not have minicom going, so I missed some
of the data and had to copy the rest by hand. Oops attached.
Version-Release number of selected component (if applicable):
It took 23 hours to get to crash. Will continue burning in
sysreport output attached.
Summary of system:
Dual 1 GHz PIII
1 GHz ECC SDRAM
2 x U160 18.2 GB SCSI. SW RAID 1
RAM had been burnt-in the day before with 45 hours on memtest86.
Created attachment 37562 [details]
Any idea what modules are loaded ?
Maybe related to 47160? Are you running a VIA dual sock 370 board?
Interesting..bugzilla didn't send me your reply to just then when the extra
comment was added. Sorry, given how long ago that bug report was reported I'm
not even sure which machine it is. It would be something like:
w83781d 16832 0
i2c-proc 6496 0 [w83781d]
i2c-isa 1188 0 (unused)
i2c-dev 3872 0 (unused)
i2c-core 13760 0 [w83781d i2c-proc i2c-isa i2c-dev]
ipt_REJECT 3552 2 (autoclean)
ipt_state 1152 5 (autoclean)
ip_conntrack_ftp 4224 0 (autoclean) (unused)
ip_conntrack 18668 2 (autoclean) [ipt_state ip_conntrack_ftp]
ipt_limit 1600 1 (autoclean)
iptable_filter 2272 0 (autoclean) (unused)
ip_tables 11968 4 [ipt_REJECT ipt_state ipt_limit iptable_filter]
eepro100 18128 1
ext3 65760 4
jbd 44580 4 [ext3]
raid1 14340 5
aic7xxx 114784 10
sd_mod 11900 10
scsi_mod 101592 2 [aic7xxx sd_mod]
Though probably without the sensors at the time.
Yes it is a dual processor VIA board (Apollo pro 266 chipset). Anyway it
would have been upgraded long ago to a newer kernel, so I will close this bug.