I'm working on the same physical server as the original bug report. I also noticed this in the kern.log at the end of reboot kernel messages, which may or may not be relevant:
Jun 27 10:52:21 www kernel: [ 145.904725] mtrr: type mismatch for d0000000,1000000 old: write-back new: write-combining
Jun 27 10:52:38 www kernel: [ 163.650905] mtrr: type mismatch for d0000000,1000000 old: write-back new: write-combining
Jun 27 10:53:47 www kernel: [ 232.116870] mtrr: type mismatch for d0000000,1000000 old: write-back new: write-combining
I've also attached two additional Oopses, which occurred before the original bug report's Oops. Note the different affected processes.
These Oopses result in defunct processes which necessitate a reboot to restore services. Unfortunately, the reboot fails and we must physically power-cycle the box from the console - always fun on a production SCSI RAID server.
I'm working on the same physical server as the original bug report. I also noticed this in the kern.log at the end of reboot kernel messages, which may or may not be relevant:
Jun 27 10:52:21 www kernel: [ 145.904725] mtrr: type mismatch for d0000000,1000000 old: write-back new: write-combining
Jun 27 10:52:38 www kernel: [ 163.650905] mtrr: type mismatch for d0000000,1000000 old: write-back new: write-combining
Jun 27 10:53:47 www kernel: [ 232.116870] mtrr: type mismatch for d0000000,1000000 old: write-back new: write-combining
I've also attached two additional Oopses, which occurred before the original bug report's Oops. Note the different affected processes.
These Oopses result in defunct processes which necessitate a reboot to restore services. Unfortunately, the reboot fails and we must physically power-cycle the box from the console - always fun on a production SCSI RAID server.
Any help is most appreciated.