mactel-linux-users

[Mactel-linux-users] lost one cpu core when upgraded to RHEL 5.5

[Geoffrey <li...@se...>]

Anyone out there running 64 bit OS on a macbook pro 4,1.  I upgraded 
from 32 bit Red Hat EL 5.4 to 64 bit RHEL 5.4, then again to 64 bit RHEL 
5.5, which is actually still in beta.  I don't know if I lost the core 
in the 64 bit 5.4 or not.  I see the following from dmesg:

SMP: Allowing 2 CPUs, 0 hotplug CPUs
.
.
SMP alternatives: switching to UP code
.
.
SMP motherboard not detected.
.
.
SMP disabled

-- 
Until later, Geoffrey

"I predict future happiness for America if they can prevent
the government from wasting the labors of the people under
the pretense of taking care of them."
- Thomas Jefferson

Re: [Mactel-linux-users] lost one cpu core when upgraded to RHEL 5.5

[Geoffrey <li...@se...>]

Geoffrey wrote:
> Anyone out there running 64 bit OS on a macbook pro 4,1.  I upgraded 
> from 32 bit Red Hat EL 5.4 to 64 bit RHEL 5.4, then again to 64 bit RHEL 
> 5.5, which is actually still in beta.  I don't know if I lost the core 
> in the 64 bit 5.4 or not.  I see the following from dmesg:
> 
> SMP: Allowing 2 CPUs, 0 hotplug CPUs
> .
> .
> SMP alternatives: switching to UP code
> .
> .
> SMP motherboard not detected.
> .
> .
> SMP disabled

Thought I'd update the list with a recent success:

For whatever reason, I could not get the initial installation RHEL 5.4 
disk to even boot until I stumbled across a link that suggested the 
following boot parms:

acpi=force noapic irqpoll

I don't know why they worked, but they did.  Once installed, I found 
that I had to add them to my grub.conf to get the install to boot, but 
all was happy.  After moving to 64bit, I lost one core of my two core 
processor.  After much discussion with RH, I revisited these parameters 
and found that by removing the noapic, parm, my macbook would still boot 
and I got both cores.  The weird thing is, I've tried every combination 
of these parms before in order to remove them from my boot process in 
the past, but my macbook would not boot.  There must be something about 
the latest RHEL 5.5 kernel that resolved that issue.

The weird thing is, I did not have this issue on 32bit RHEL 5.4.  That 
is, I had both cores using all these parms.

-- 
Until later, Geoffrey

"I predict future happiness for America if they can prevent
the government from wasting the labors of the people under
the pretense of taking care of them."
- Thomas Jefferson

Re: [Mactel-linux-users] lost one cpu core when upgraded to RHEL 5.5

[Justin P. m. <jus...@gm...>]

On 04/13/2010 07:57 AM, Geoffrey wrote:
> Geoffrey wrote:
>> Anyone out there running 64 bit OS on a macbook pro 4,1.  I upgraded
>> from 32 bit Red Hat EL 5.4 to 64 bit RHEL 5.4, then again to 64 bit RHEL
>> 5.5, which is actually still in beta.  I don't know if I lost the core
>> in the 64 bit 5.4 or not.  I see the following from dmesg:
>>
>> SMP: Allowing 2 CPUs, 0 hotplug CPUs
>> .
>> .
>> SMP alternatives: switching to UP code
>> .
>> .
>> SMP motherboard not detected.
>> .
>> .
>> SMP disabled
>
> Thought I'd update the list with a recent success:
>
> For whatever reason, I could not get the initial installation RHEL 5.4
> disk to even boot until I stumbled across a link that suggested the
> following boot parms:
>
> acpi=force noapic irqpoll
>
> I don't know why they worked, but they did.  Once installed, I found
> that I had to add them to my grub.conf to get the install to boot, but
> all was happy.  After moving to 64bit, I lost one core of my two core
> processor.  After much discussion with RH, I revisited these parameters
> and found that by removing the noapic, parm, my macbook would still boot
> and I got both cores.  The weird thing is, I've tried every combination
> of these parms before in order to remove them from my boot process in
> the past, but my macbook would not boot.  There must be something about
> the latest RHEL 5.5 kernel that resolved that issue.
>
> The weird thing is, I did not have this issue on 32bit RHEL 5.4.  That
> is, I had both cores using all these parms.
>

this doesn't seem right..
you need apic etc... they must be
doing something in there configs somewhere
(COFNIG_SMP=y if set gives you both cores
(but could be wrong)).

Justin P. Mattock

Re: [Mactel-linux-users] lost one cpu core when upgraded to RHEL 5.5

[cyberdork33 <cyb...@gm...>]

This was a bug in Ubuntu awhile ago, but only affected 5,2 and newer hardware... I am not sure if it was ever resolved or not. Similar sounding issues though.


On Apr 13, 2010, at 1:24 PM, Justin P. mattock wrote:

> On 04/13/2010 07:57 AM, Geoffrey wrote:
>> Geoffrey wrote:
>>> Anyone out there running 64 bit OS on a macbook pro 4,1.  I upgraded
>>> from 32 bit Red Hat EL 5.4 to 64 bit RHEL 5.4, then again to 64 bit RHEL
>>> 5.5, which is actually still in beta.  I don't know if I lost the core
>>> in the 64 bit 5.4 or not.  I see the following from dmesg:
>>> 
>>> SMP: Allowing 2 CPUs, 0 hotplug CPUs
>>> .
>>> .
>>> SMP alternatives: switching to UP code
>>> .
>>> .
>>> SMP motherboard not detected.
>>> .
>>> .
>>> SMP disabled
>> 
>> Thought I'd update the list with a recent success:
>> 
>> For whatever reason, I could not get the initial installation RHEL 5.4
>> disk to even boot until I stumbled across a link that suggested the
>> following boot parms:
>> 
>> acpi=force noapic irqpoll
>> 
>> I don't know why they worked, but they did.  Once installed, I found
>> that I had to add them to my grub.conf to get the install to boot, but
>> all was happy.  After moving to 64bit, I lost one core of my two core
>> processor.  After much discussion with RH, I revisited these parameters
>> and found that by removing the noapic, parm, my macbook would still boot
>> and I got both cores.  The weird thing is, I've tried every combination
>> of these parms before in order to remove them from my boot process in
>> the past, but my macbook would not boot.  There must be something about
>> the latest RHEL 5.5 kernel that resolved that issue.
>> 
>> The weird thing is, I did not have this issue on 32bit RHEL 5.4.  That
>> is, I had both cores using all these parms.
>> 
> 
> this doesn't seem right..
> you need apic etc... they must be
> doing something in there configs somewhere
> (COFNIG_SMP=y if set gives you both cores
> (but could be wrong)).
> 
> Justin P. Mattock
> 
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Mactel-linux-users mailing list
> Mac...@li...
> https://lists.sourceforge.net/lists/listinfo/mactel-linux-users

Re: [Mactel-linux-users] lost one cpu core when upgraded to RHEL 5.5

[Justin P. m. <jus...@gm...>]

On 04/13/2010 12:37 PM, cyberdork33 wrote:
> This was a bug in Ubuntu awhile ago, but only affected 5,2 and newer hardware... I am not sure if it was ever resolved or not. Similar sounding issues though.
>

hmm.. I wonder if this is bisectable!?

Justin P. Mattock

Re: [Mactel-linux-users] lost one cpu core when upgraded to RHEL 5.5

[Geoffrey <li...@se...>]

Justin P. mattock wrote:
> On 04/13/2010 07:57 AM, Geoffrey wrote:
>> Geoffrey wrote:
>>> Anyone out there running 64 bit OS on a macbook pro 4,1.  I upgraded
>>> from 32 bit Red Hat EL 5.4 to 64 bit RHEL 5.4, then again to 64 bit RHEL
>>> 5.5, which is actually still in beta.  I don't know if I lost the core
>>> in the 64 bit 5.4 or not.  I see the following from dmesg:
>>>
>>> SMP: Allowing 2 CPUs, 0 hotplug CPUs
>>> .
>>> .
>>> SMP alternatives: switching to UP code
>>> .
>>> .
>>> SMP motherboard not detected.
>>> .
>>> .
>>> SMP disabled
>>
>> Thought I'd update the list with a recent success:
>>
>> For whatever reason, I could not get the initial installation RHEL 5.4
>> disk to even boot until I stumbled across a link that suggested the
>> following boot parms:
>>
>> acpi=force noapic irqpoll
>>
>> I don't know why they worked, but they did.  Once installed, I found
>> that I had to add them to my grub.conf to get the install to boot, but
>> all was happy.  After moving to 64bit, I lost one core of my two core
>> processor.  After much discussion with RH, I revisited these parameters
>> and found that by removing the noapic, parm, my macbook would still boot
>> and I got both cores.  The weird thing is, I've tried every combination
>> of these parms before in order to remove them from my boot process in
>> the past, but my macbook would not boot.  There must be something about
>> the latest RHEL 5.5 kernel that resolved that issue.
>>
>> The weird thing is, I did not have this issue on 32bit RHEL 5.4.  That
>> is, I had both cores using all these parms.
>>
> 
> this doesn't seem right..
> you need apic etc... they must be
> doing something in there configs somewhere
> (COFNIG_SMP=y if set gives you both cores
> (but could be wrong)).

No telling, all I know is I have a happy dual core system again with a 
64 bit OS. ;)

> 
> Justin P. Mattock
> 


-- 
Until later, Geoffrey

"I predict future happiness for America if they can prevent
the government from wasting the labors of the people under
the pretense of taking care of them."
- Thomas Jefferson

Re: [Mactel-linux-users] lost one cpu core when upgraded to RHEL 5.5

[Justin P. m. <jus...@gm...>]

On 04/14/2010 06:49 AM, Geoffrey wrote:
> Justin P. mattock wrote:
>> On 04/13/2010 07:57 AM, Geoffrey wrote:
>>> Geoffrey wrote:
>>>> Anyone out there running 64 bit OS on a macbook pro 4,1. I upgraded
>>>> from 32 bit Red Hat EL 5.4 to 64 bit RHEL 5.4, then again to 64 bit
>>>> RHEL
>>>> 5.5, which is actually still in beta. I don't know if I lost the core
>>>> in the 64 bit 5.4 or not. I see the following from dmesg:
>>>>
>>>> SMP: Allowing 2 CPUs, 0 hotplug CPUs
>>>> .
>>>> .
>>>> SMP alternatives: switching to UP code
>>>> .
>>>> .
>>>> SMP motherboard not detected.
>>>> .
>>>> .
>>>> SMP disabled
>>>
>>> Thought I'd update the list with a recent success:
>>>
>>> For whatever reason, I could not get the initial installation RHEL 5.4
>>> disk to even boot until I stumbled across a link that suggested the
>>> following boot parms:
>>>
>>> acpi=force noapic irqpoll

the acpi=force seems harmless, but the noapic scares me(you need this),
In any case you should be able to bootup without any of these boot 
params which makes me wonder if this is a kernel issue and/or userspace

>>>
>>> I don't know why they worked, but they did. Once installed, I found
>>> that I had to add them to my grub.conf to get the install to boot, but
>>> all was happy. After moving to 64bit, I lost one core of my two core
>>> processor. After much discussion with RH, I revisited these parameters
>>> and found that by removing the noapic, parm, my macbook would still boot
>>> and I got both cores. The weird thing is, I've tried every combination
>>> of these parms before in order to remove them from my boot process in
>>> the past, but my macbook would not boot. There must be something about
>>> the latest RHEL 5.5 kernel that resolved that issue.
>>>
>>> The weird thing is, I did not have this issue on 32bit RHEL 5.4. That
>>> is, I had both cores using all these parms.
>>>
>>
>> this doesn't seem right..
>> you need apic etc... they must be
>> doing something in there configs somewhere
>> (COFNIG_SMP=y if set gives you both cores
>> (but could be wrong)).
>
> No telling, all I know is I have a happy dual core system again with a
> 64 bit OS. ;)
>

That's good news.. if you can, maybe try loading the latest kernel from 
git, then if the system can bootup without any of these boot params
then you know there's a regression in the kernel somewhere(then if you 
have the time do a bisect, and report it to lkml, so there aware of the 
commit that causes this).

Justin P. Mattock

Re: [Mactel-linux-users] lost one cpu core when upgraded to RHEL 5.5

[Geoffrey <li...@se...>]

Justin P. mattock wrote:
> On 04/14/2010 06:49 AM, Geoffrey wrote:
>> Justin P. mattock wrote:
>>> On 04/13/2010 07:57 AM, Geoffrey wrote:
>>>> Geoffrey wrote:
>>>>> Anyone out there running 64 bit OS on a macbook pro 4,1. I upgraded
>>>>> from 32 bit Red Hat EL 5.4 to 64 bit RHEL 5.4, then again to 64 bit
>>>>> RHEL
>>>>> 5.5, which is actually still in beta. I don't know if I lost the core
>>>>> in the 64 bit 5.4 or not. I see the following from dmesg:
>>>>>
>>>>> SMP: Allowing 2 CPUs, 0 hotplug CPUs
>>>>> .
>>>>> .
>>>>> SMP alternatives: switching to UP code
>>>>> .
>>>>> .
>>>>> SMP motherboard not detected.
>>>>> .
>>>>> .
>>>>> SMP disabled
>>>>
>>>> Thought I'd update the list with a recent success:
>>>>
>>>> For whatever reason, I could not get the initial installation RHEL 5.4
>>>> disk to even boot until I stumbled across a link that suggested the
>>>> following boot parms:
>>>>
>>>> acpi=force noapic irqpoll
> 
> the acpi=force seems harmless, but the noapic scares me(you need this),
> In any case you should be able to bootup without any of these boot 
> params which makes me wonder if this is a kernel issue and/or userspace

I've played a bit more with this.  Removed the acpi=force too.  Booted 
fine.  Problem if I remove the irqpoll.  System starts to boot, but 
panics on smartd ????  Keyboard is still responsive, ie toggle shift key 
led on/off, but no screen output and can not switch virtual terminals.

Put it back in for now, seems it might have something to do with the 
dvd/cdrom drive.

> 
>>>>
>>>> I don't know why they worked, but they did. Once installed, I found
>>>> that I had to add them to my grub.conf to get the install to boot, but
>>>> all was happy. After moving to 64bit, I lost one core of my two core
>>>> processor. After much discussion with RH, I revisited these parameters
>>>> and found that by removing the noapic, parm, my macbook would still 
>>>> boot
>>>> and I got both cores. The weird thing is, I've tried every combination
>>>> of these parms before in order to remove them from my boot process in
>>>> the past, but my macbook would not boot. There must be something about
>>>> the latest RHEL 5.5 kernel that resolved that issue.
>>>>
>>>> The weird thing is, I did not have this issue on 32bit RHEL 5.4. That
>>>> is, I had both cores using all these parms.
>>>>
>>>
>>> this doesn't seem right..
>>> you need apic etc... they must be
>>> doing something in there configs somewhere
>>> (COFNIG_SMP=y if set gives you both cores
>>> (but could be wrong)).
>>
>> No telling, all I know is I have a happy dual core system again with a
>> 64 bit OS. ;)
>>
> 
> That's good news.. if you can, maybe try loading the latest kernel from 
> git, then if the system can bootup without any of these boot params
> then you know there's a regression in the kernel somewhere(then if you 
> have the time do a bisect, and report it to lkml, so there aware of the 
> commit that causes this).

I do hope to do this in the future, just that I've always had a problem 
getting the kernel to boot once I built it.  Need some time to research 
this issue.

> 
> Justin P. Mattock
> 
> 


-- 
Until later, Geoffrey

"I predict future happiness for America if they can prevent
the government from wasting the labors of the people under
the pretense of taking care of them."
- Thomas Jefferson

Re: [Mactel-linux-users] lost one cpu core when upgraded to RHEL 5.5

[Justin P. m. <jus...@gm...>]

On 04/14/2010 08:06 AM, Geoffrey wrote:
> Justin P. mattock wrote:
>> On 04/14/2010 06:49 AM, Geoffrey wrote:
>>> Justin P. mattock wrote:
>>>> On 04/13/2010 07:57 AM, Geoffrey wrote:
>>>>> Geoffrey wrote:
>>>>>> Anyone out there running 64 bit OS on a macbook pro 4,1. I upgraded
>>>>>> from 32 bit Red Hat EL 5.4 to 64 bit RHEL 5.4, then again to 64 bit
>>>>>> RHEL
>>>>>> 5.5, which is actually still in beta. I don't know if I lost the core
>>>>>> in the 64 bit 5.4 or not. I see the following from dmesg:
>>>>>>
>>>>>> SMP: Allowing 2 CPUs, 0 hotplug CPUs
>>>>>> .
>>>>>> .
>>>>>> SMP alternatives: switching to UP code
>>>>>> .
>>>>>> .
>>>>>> SMP motherboard not detected.
>>>>>> .
>>>>>> .
>>>>>> SMP disabled
>>>>>
>>>>> Thought I'd update the list with a recent success:
>>>>>
>>>>> For whatever reason, I could not get the initial installation RHEL 5.4
>>>>> disk to even boot until I stumbled across a link that suggested the
>>>>> following boot parms:
>>>>>
>>>>> acpi=force noapic irqpoll
>>
>> the acpi=force seems harmless, but the noapic scares me(you need this),
>> In any case you should be able to bootup without any of these boot
>> params which makes me wonder if this is a kernel issue and/or userspace
>
> I've played a bit more with this. Removed the acpi=force too. Booted
> fine. Problem if I remove the irqpoll. System starts to boot, but panics
> on smartd ???? Keyboard is still responsive, ie toggle shift key led
> on/off, but no screen output and can not switch virtual terminals.
>
> Put it back in for now, seems it might have something to do with the
> dvd/cdrom drive.
>
>>
>>>>>
>>>>> I don't know why they worked, but they did. Once installed, I found
>>>>> that I had to add them to my grub.conf to get the install to boot, but
>>>>> all was happy. After moving to 64bit, I lost one core of my two core
>>>>> processor. After much discussion with RH, I revisited these parameters
>>>>> and found that by removing the noapic, parm, my macbook would still
>>>>> boot
>>>>> and I got both cores. The weird thing is, I've tried every combination
>>>>> of these parms before in order to remove them from my boot process in
>>>>> the past, but my macbook would not boot. There must be something about
>>>>> the latest RHEL 5.5 kernel that resolved that issue.
>>>>>
>>>>> The weird thing is, I did not have this issue on 32bit RHEL 5.4. That
>>>>> is, I had both cores using all these parms.
>>>>>
>>>>
>>>> this doesn't seem right..
>>>> you need apic etc... they must be
>>>> doing something in there configs somewhere
>>>> (COFNIG_SMP=y if set gives you both cores
>>>> (but could be wrong)).
>>>
>>> No telling, all I know is I have a happy dual core system again with a
>>> 64 bit OS. ;)
>>>
>>
>> That's good news.. if you can, maybe try loading the latest kernel
>> from git, then if the system can bootup without any of these boot params
>> then you know there's a regression in the kernel somewhere(then if you
>> have the time do a bisect, and report it to lkml, so there aware of
>> the commit that causes this).
>
> I do hope to do this in the future, just that I've always had a problem
> getting the kernel to boot once I built it. Need some time to research
> this issue.
>
>>
>> Justin P. Mattock
>>
>>
>
>


right now the only issue I'm having with the current HEAD
is an Oops during boot:
https://bugzilla.kernel.org/show_bug.cgi?id= 15749
which is fixed with the patch on the bug.

then an SELinux avc issue with nscd. other than that
the system boots fine(need to check other
stuff, but will do later on).

as for the bisect, your situation does look bisectable
keep in mind though this could already have been fixed
especially if redhat is using an older kernel.
(but could be wrong)

Justin P. Mattock

Re: [Mactel-linux-users] lost one cpu core when upgraded to RHEL 5.5

[Geoffrey <li...@se...>]

Justin P. mattock wrote:

>> I do hope to do this in the future, just that I've always had a problem
>> getting the kernel to boot once I built it. Need some time to research
>> this issue.
>>
>>>
>>> Justin P. Mattock
>>
> 
> 
> right now the only issue I'm having with the current HEAD
> is an Oops during boot:
> https://bugzilla.kernel.org/show_bug.cgi?id= 15749
> which is fixed with the patch on the bug.
> 
> then an SELinux avc issue with nscd. other than that
> the system boots fine(need to check other
> stuff, but will do later on).
> 
> as for the bisect, your situation does look bisectable
> keep in mind though this could already have been fixed
> especially if redhat is using an older kernel.
> (but could be wrong)

kernel 2.6.18-194.el5

-- 
Until later, Geoffrey

"I predict future happiness for America if they can prevent
the government from wasting the labors of the people under
the pretense of taking care of them."
- Thomas Jefferson

Re: [Mactel-linux-users] lost one cpu core when upgraded to RHEL 5.5

[Justin P. m. <jus...@gm...>]

On 04/14/2010 08:33 AM, Geoffrey wrote:
> Justin P. mattock wrote:
>
>>> I do hope to do this in the future, just that I've always had a problem
>>> getting the kernel to boot once I built it. Need some time to research
>>> this issue.
>>>
>>>>
>>>> Justin P. Mattock
>>>
>>
>>
>> right now the only issue I'm having with the current HEAD
>> is an Oops during boot:
>> https://bugzilla.kernel.org/show_bug.cgi?id= 15749
>> which is fixed with the patch on the bug.
>>
>> then an SELinux avc issue with nscd. other than that
>> the system boots fine(need to check other
>> stuff, but will do later on).
>>
>> as for the bisect, your situation does look bisectable
>> keep in mind though this could already have been fixed
>> especially if redhat is using an older kernel.
>> (but could be wrong)
>
> kernel 2.6.18-194.el5
>

shit man support for the macbook didn't really come
until 2.6.20(super kernel sunday!!) but keep in mind
they probably patch 2.6.18 so it probably is there.
(if not then this could be why(2.6.18 - 2.6.34
a huge lot of changes)).

Justin P. Mattock