Re: [opensuse] Novell Bugzilla - At it Again - Bugs Apparently Dismissed Without Sufficient Investigation
![](https://seccdn.libravatar.org/avatar/27aacf61a13c66fcc083fcf8a84823bc.jpg?s=120&d=mm&r=g)
John Andersen wrote:
On Sat, Apr 5, 2008 at 12:08 AM, David C. Rankin
I'll take a look at the link, thanks. I suspect we haven't heard the last of this issue.
try the single word "nohpet" (no quotes) on the boot prompt. Supposedly imposes this option in most of the cases in which it is needed, but I still have it hardcoded in my /boot/grub/menu.lst for my core 2 duo.
Thanks John! No difference however. I passed nohpet to the kernel last night and still received an mce: See the last (5:03 am) entry in: http://www.3111skyline.com/download/lockup_x86-64/messages -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/27aacf61a13c66fcc083fcf8a84823bc.jpg?s=120&d=mm&r=g)
David C. Rankin wrote:
Thanks John!
No difference however. I passed nohpet to the kernel last night and still received an mce: See the last (5:03 am) entry in:
Listmates, Latest MCE has the following text with a new twist. The Address referenced by MCE can't be resolved by mcelog? What? The address is ffff802ac930 and the report is "No matching memory address found for ffff802ac930 in SMBIOS" I'm still no closer to figuring out what is going on. Current boot parameters: noapic, nolapic with manual irq selected in the BIOS. Apr 7 18:15:01 nirvana mcelog: HARDWARE ERROR. This is *NOT* a software problem! Apr 7 18:15:01 nirvana mcelog: Please contact your hardware vendor Apr 7 18:15:01 nirvana mcelog: CPU 1 1 instruction cache Apr 7 18:15:01 nirvana mcelog: TSC 10da31ff516c Apr 7 18:15:01 nirvana mcelog: ADDR ffff802ac930 Apr 7 18:15:01 nirvana mcelog: Apr 7 18:15:01 nirvana mcelog: memory/cache error 'instruction fetch mem transaction, instruction transaction, level 1' Apr 7 18:15:01 nirvana mcelog: STATUS 9400000000000151 MCGSTATUS 0 Apr 7 18:15:01 nirvana mcelog: Resolving address ffff802ac930 using SMBIOS Apr 7 18:15:01 nirvana mcelog: No matching memory address found for ffff802ac930 in SMBIOS Does this mean anything to anyone?? -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/b1a0edc535182bc18779eac72052bd7a.jpg?s=120&d=mm&r=g)
David C. Rankin wrote:
David C. Rankin wrote:
Thanks John!
No difference however. I passed nohpet to the kernel last night and still received an mce: See the last (5:03 am) entry in:
Listmates,
Latest MCE has the following text with a new twist. The Address referenced by MCE can't be resolved by mcelog? What? The address is ffff802ac930 and the report is "No matching memory address found for ffff802ac930 in SMBIOS" I'm still no closer to figuring out what is going on.
Current boot parameters: noapic, nolapic with manual irq selected in the BIOS.
Apr 7 18:15:01 nirvana mcelog: HARDWARE ERROR. This is *NOT* a software problem! Apr 7 18:15:01 nirvana mcelog: Please contact your hardware vendor Apr 7 18:15:01 nirvana mcelog: CPU 1 1 instruction cache Apr 7 18:15:01 nirvana mcelog: TSC 10da31ff516c Apr 7 18:15:01 nirvana mcelog: ADDR ffff802ac930 Apr 7 18:15:01 nirvana mcelog: Apr 7 18:15:01 nirvana mcelog: memory/cache error 'instruction fetch mem transaction, instruction transaction, level 1' Apr 7 18:15:01 nirvana mcelog: STATUS 9400000000000151 MCGSTATUS 0 Apr 7 18:15:01 nirvana mcelog: Resolving address ffff802ac930 using SMBIOS Apr 7 18:15:01 nirvana mcelog: No matching memory address found for ffff802ac930 in SMBIOS
Does this mean anything to anyone??
Hi David, in order to make any real sense of this problem you need to attach a remote debugger to your kernel. The info from mcelog, tells you that there is something there but it can't tell you what it is. I am guessing it is an interrupt vector pointing to a random memory location and it is to do with video. I'm looking for a suitable debugger and I will post my results. If anyone else knows more please help, my knowledge of linux is not that great yet. Regards Dave Plater -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (2)
-
Dave Plater
-
David C. Rankin