nosmp causes 'ata1: COMRESET failed' on vmlinuz-2.6.23.1-42.fc8

Todd Denniston Todd.Denniston at ssa.crane.navy.mil
Thu Nov 8 15:26:55 UTC 2007


Chuck Ebbert wrote, On 11/07/2007 03:32 PM:
> On 11/07/2007 10:13 AM, Todd Denniston wrote:
>> Folks,
>> While attempting to get xorg working[1] in vesa and fbdev mode with the
>> CF52 I have, I tried using the nosmp boot option and received an
>> unexpected result on boot.  Fortunately I don't require nosmp to get the
>> system working, but I definitely was not expecting the nosmp option to
>> cause a failure of the ata subsystem.
>>
> 
> Try maxcpus=1
> 
normal boot (no nosmp or maxcpus=1)
grub outputs:
kernel /vmlinuz-2.6.23.1-42.fc8 ro root=LABEL=/ rhgb quiet

grub outputs:
kernel /vmlinuz-2.6.23.1-42.fc8 ro root=LABEL=/ maxcpus=1 rhgb quiet
maxcpus=1 bios    result
--------- ----    ------
!use      smp     Boots and works normally, modulo X problems.
!use      !smp    Boots and works normally, modulo X problems.
use       !smp    Boots and works normally, modulo X problems.
use       smp     Boots and works normally, modulo X problems.

grub outputs:
kernel /vmlinuz-2.6.23.1-42.fc8 ro root=LABEL=/ nosmp rhgb quiet
nosmp    bios    result
-----    ----    ------
!use     smp     Boots and works normally, modulo X problems.
!use     !smp    Boots and works normally, modulo X problems.
use      smp     Fails with ata1: COMRESET failed
use      !smp    Fails with ata1: COMRESET failed

Interesting...
`nosmp` !(exactly)= `maxcpus=1` ???

-- 
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter




More information about the fedora-test-list mailing list