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.
The system: a Panasonic CF-52, see attached lspci for some details reformatted to clean, then installed from F8T3 [2], immediately following install it was fully yum updated to the fedora/linux/development/i386/os/ as of "Nov 6 08:15" [3]. nothing from any non fedora/linux/development/i386/os/ has been installed.
I also tried the system after modifying the bios setting which enables|disables both cores in smp.
grub outputs: kernel /vmlinuz-2.6.23.1-42.fc8 ro root=LABEL=/ nosmp rhgb quiet
---- Console output ----- Uncompressing Linux... Ok, booting the kernel. Red Hat nash version 6.0.19 starting ata1: COMRESET failed (errno=-16) ata1: COMRESET failed (errno=-16) ata1: COMRESET failed (errno=-16) ---- end Console output ----- followed by the nash script output about swap and mounts not working because the disk is not available.
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
Is the above and attached enough information?
[1] or at least track down why it is not, which is a subject for a different thread. [2] No torrent allowed at my location, so I am using what I have. [3] TZ=EST I think, based on when repodata/comps.xml was set at the mirror also the last updated file in development/i386/os/Package was Nov 2 14:01 selinux-policy-3.0.8-44.fc8.noarch.rpm
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
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 wrote, On 11/08/2007 10:26 AM:
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` ???
Still trying to understand this from a personal perspective, I did just a little more research... `nosmp` = `maxcpus=0`[1] and I get the same COMRESET failed for maxcpus=0.
also from [1] `nosmp` ~= `maxcpus=1 noapic` but this gets through the boot process.
looking at [1] and [2] `maxcpus=1 nolapic` also gets through the boot process, just slower, and a lot slower (several minutes) at HAL start.
`maxcpus=1 noapic nolapic` & `noapic nolapic maxcpus=1` also gets through the boot process, just slower, and a lot slower (several minutes) at udev start.
`maxcpus=0 lapic` & `lapic maxcpus=0` gives COMRESET failed.
And just to see if defining them turns something off correctly: `maxcpus=0 noapic nolapic` & `noapic nolapic maxcpus=0` gives COMRESET failed.
So it seems that unlike what is said in [1] [2] and [3] `maxcpus=0` != `maxcpus=1 noapic`
And to me it still seems that nosmp/maxcpus=0 should not have caused a fault with the ata bus.
[1] http://www.linuxhq.com/kernel/v2.6/23/Documentation/kernel-parameters.txt [2] http://www.ussg.iu.edu/hypermail/linux/kernel/0708.2/0321.html [3] http://bugzilla.kernel.org/show_bug.cgi?id=1641
-
Chuck Ebbert -
Todd Denniston