Red Hat Bugzilla – Bug 116389
SMP kernel won't boot on A31p Thinkpad (required for oprofile)
Last modified: 2013-08-05 21:04:55 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030922
Description of problem:
Apparently the oprofile tool will only work with the SMP kernel.
This kernel fails to boot on my A31p ThinkPad.
It spits out some messages, and then simply freezes. The last message
has something to do with hugemem.
If there's some other way to get oprofile working, please let me know.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.up2date SMP kernel on A31p ThinkPad
I've been running the smp kernel on my A31p system for a long time now....
Hmmm, wonder if something broke in the newer kernel?
[tburke@tim tburke]$ uname -a
Linux tim.boston.redhat.com 2.4.21-5.ELsmp #1 SMP Mon Dec 1 17:20:05
EST 2003 i686 i686 i386 GNU/Linux
I see there's an even newer kernel now (2.4.21-9.0.1.EL). I'll try
that as well.
BTW, I write "hugemem" above, but I meant "HugeTLB".
I tried the latest kernel (2.4.21-9.0.1.ELsmp) and have the same problem.
tburke claims that 2.4.21-5.ELsmp worked on the A31p. How do I get my
hands on that?
Can you run /sbin/dmidecode and attach the output? I'm suspecting a
Created attachment 98166 [details]
Output from /usr/bin/dmidecode
Created attachment 98171 [details]
/sbin/dmidecode from tburke's A31p
I got the attached /sbin/dmidecode output from tburke. Diffing the two, I
notice two major differences: different BIOS rev (1.03 on the failing system,
1.02 on tburke's system) and different mainboard model numbers. This suggests
to me that any comparison between the failing system and tburke's
successfully-booting system may not be 100% meaningful.
Anthony - any updates on this issue?
Thanks for the ping. I didn't notice your update on 2004-03-01!
I've since had the mainboard replaced on my laptop (video failed, so
IBM swapped out the whole mainboard), and I haven't tried since. I'll
Anthony - have you had a chance to try this?
No news is good news; I presume it's working fine for you. Closing this as
CURRENTRELEASE under the assumption that the current release works on this hardware.