[opensuse-factory] laptop with core 2 duo shows only one core
The hardware lister says I have two cores: lshw -C cpu *-cpu description: CPU product: Intel(R) Core(TM)2 Duo CPU T9500 @ 2.60GHz vendor: Intel Corp. physical id: 400 bus info: cpu@0 slot: Microprocessor size: 2600MHz capacity: 2600MHz width: 64 bits clock: 200MHz capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 lahf_lm ida dtherm tpr_shadow vnmi flexpriority configuration: cores=2 enabledcores=2 threads=2 inxi shows me I'm running in uniprocessor mode: inxi -c 0 -F System: Host: <hostname> Kernel: 3.8.9-5-desktop x86_64 (64 bit) Console tty 1 Distro: openSUSE 12.3 (x86_64) VERSION = 12.3 CODENAME = Dartmouth Machine: System: Dell (portable) product: MXG071 serial: XXXXXXXXX Mobo: Dell model: 0KX412 serial: .YYYYYYYYYY. Bios: Dell version: A11 date: 04/23/2010 CPU: Single core Intel Core2 Duo CPU T9500 (-UP-) cache: 6144 KB flags: (lm nx sse sse2 sse3 sse4_1 ssse3 vmx) clocked at 2592.643 MHz Graphics: Card: NVIDIA G84 [GeForce 8700M GT] X.org: 1.13.2 driver: nvidia tty size: 190x54 Advanced Data: N/A for root out of X Audio: Card: Intel 82801H (ICH8 Family) HD Audio Controller driver: snd_hda_intel Sound: ALSA ver: k3.8.9-5-desktop Network: Card-1: Broadcom NetXtreme BCM5754M Gigabit Ethernet PCI Express driver: tg3 IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 00:23:ae:2d:3e:ff Card-2: Intel PRO/Wireless 4965 AG or AGN [Kedron] Network Connection driver: iwl4965 IF: wlan0 state: down mac: 00:21:5c:59:b1:bf Drives: HDD Total Size: 1320.3GB (36.4% used) 1: /dev/sdb WDC_WD10JPVT 1000.2GB 2: /dev/sda ST9320421ASG 320.1GB Partition: ID: / size: 60G used: 32G (54%) fs: ext3 ID: /home size: 226G used: 167G (78%) fs: ext3 ID: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap Sensors: System Temperatures: cpu: 62.5C mobo: N/A Fan Speeds (in rpm): cpu: N/A Info: Processes: 197 Uptime: 1:12 Memory: 1535.6/7985.0MB Runlevel: 5 Client: Shell inxi: 1.7.24 my grub boot options are: noapic nolapic apm=off noresume edd=off nohz=off hires=off processor.max_cstate=1 nomodeset resume=/dev/disk/by-id/ata-ST9320421ASG_5TJ0Q4HY-part2 splash=silent quiet showopts Can anyone tell me what I need to change to get my system to boot smp again? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sunday 2013-05-05 04:08, Bruce Ferrell wrote:
my grub boot options are: noapic nolapic apm=off noresume edd=off nohz=off hires=off processor.max_cstate=1 nomodeset resume=/dev/disk/by-id/ata-ST9320421ASG_5TJ0Q4HY-part2 splash=silent quiet showopts
Deactivating all the features conflicts with (modern) SMP. Do not run "Failsafe" from the boot menu. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2013-05-04 19:08 (GMT-0700) Bruce Ferrell composed:
my grub boot options are: noapic nolapic apm=off noresume edd=off nohz=off hires=off processor.max_cstate=1 nomodeset resume=/dev/disk/by-id/ata-ST9320421ASG_5TJ0Q4HY-part2 splash=silent quiet showopts
Is that the content of /proc/cmdline, or your perusal of some latter portion your Grub menu file? If the former, why are you using it??? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 05/05/2013 02:37 AM, Felix Miata wrote:
On 2013-05-04 19:08 (GMT-0700) Bruce Ferrell composed:
my grub boot options are: noapic nolapic apm=off noresume edd=off nohz=off hires=off processor.max_cstate=1 nomodeset resume=/dev/disk/by-id/ata-ST9320421ASG_5TJ0Q4HY-part2 splash=silent quiet showopts
Is that the content of /proc/cmdline, or your perusal of some latter portion your Grub menu file? If the former, why are you using it???
Felix, it is in fact the contents of the /boot/grub.d/grub.cfg. to give you what you requested, rather than asking why you requested it: more /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-3.8.9-5-desktop root=UUID=a3b45d4e-a3dc-4e0f-9b24-2d0d4f65c221 noapic nolapic apm=off noresume edd=off powersaved=off nohz=off hires=off processor.max_cstate=1 nomodeset resume=/dev/disk/by-id/ata-ST9320421ASG_5TJ0Q4HY-part2 splash=silent quiet showopts And now, to answer the question "WHY are the Failsafe options on?" (see catbird... not a "smart" question). This is an issue I've requested assistance with a number of times. It's a slowly being modified back to "normal", because the installer, when booted on THIS system and NOT in failsafe, puts the display into selftest mode (never installs either). I had to install in failsafe (resulting in grub2 being set that way). Now I'm trying to turn the "stuff" off that kills my performance. And Jan, yes, I understand this configuration turns off SMP. Now, tell me what turns it back ON. Just for the record, the live CD/DVDs do this too using OpenSUSE. Ubuntu live doesn't, Fedora live doesn't. This "error" seems to be unique to y'all and now I'm asking to help me fix it so I can properly report it to the bug tracker so maybe it can be fixed going forward. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sun, 5 May 2013 17:36, Bruce Ferrell
On 05/05/2013 02:37 AM, Felix Miata wrote:
On 2013-05-04 19:08 (GMT-0700) Bruce Ferrell composed:
my grub boot options are: noapic nolapic apm=off noresume edd=off nohz=off hires=off processor.max_cstate=1 nomodeset resume=/dev/disk/by-id/ata-ST9320421ASG_5TJ0Q4HY-part2 splash=silent quiet showopts
Is that the content of /proc/cmdline, or your perusal of some latter portion your Grub menu file? If the former, why are you using it???
Felix, it is in fact the contents of the /boot/grub.d/grub.cfg. to give you what you requested, rather than asking why you requested it:
more /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-3.8.9-5-desktop root=UUID=a3b45d4e-a3dc-4e0f-9b24-2d0d4f65c221 noapic nolapic apm=off noresume edd=off powersaved=off nohz=off hires=off processor.max_cstate=1 nomodeset resume=/dev/disk/by-id/ata-ST9320421ASG_5TJ0Q4HY-part2 splash=silent quiet showopts [snip]
Hmm, when I compare that to my /proc/cmdline, the short answer would be to remove the following options: noapic nolapic apm=off noresume edd=off nohz=off hires=off processor.max_cstate=1 nomodeset Now, if you are unsure wether or not you NEED one of these options, start the remove action with: edd=off (Monitor modi detection stuff, uncritical on most systems) hires=off (hires timer, uncritical on most systems) noapic, nolapic (every modern (past 2003/2004) needs apic to controll interrupt handling, no apic = nosmp) apm=off (system power management, only need for shitty BIOS) nohz=off (AFAIK Intel speedstep / AMD Cool'n'Quiet need that removed) processor.max_cstate=1 (removal of this should be uncritical in nearly all situations) nomodeset (when you remove this, the kernel tries to use kms during startup) Addenum: For a first blind try I would remove: "apm=off edd=off nohz=off hires=off processor.max_cstate=1" That still does not give you SMP, but gives you a measure off security. If the system still works fine (other than no smp), you have a first win on your side. For the second try remove additionally: "noapic nolapic" This should give you SMP. At last you can remove: "nomodeset noresume" To get a near standard install. I hope this give you a hint where to start. - Yamaban. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2013-05-05 08:36 (GMT-0700) Bruce Ferrell composed:
And now, to answer the question "WHY are the Failsafe options on?" (see catbird... not a "smart" question). This is an issue I've requested assistance with a number of times.
When? I just looked in the opensuse-factory and opensuse-kernel mailing list archives for your name back to 2013 Jan 01 and found no subjects that look like this, finding only NIC and Grub subject lines.
It's a slowly being modified back to "normal", because the installer, when booted on THIS system and NOT in failsafe, puts the display into selftest mode (never installs either). I had to install in failsafe (resulting in grub2 being set that way). Now I'm trying to turn the "stuff" off that kills my performance.
And Jan, yes, I understand this configuration turns off SMP. Now, tell me what turns it back ON.
Just for the record, the live CD/DVDs do this too using OpenSUSE. Ubuntu live doesn't, Fedora live doesn't. This "error" seems to be unique to y'all and now I'm asking to help me fix it so I can properly report it to the bug tracker so maybe it can be fixed going forward.
I have no multicore laptops. I tried reproducing on a C2D desktop in 12.3 and 13.1 (with 3.8.2 & 3.9.0 kernels) but could not: 12.3-3.7.10# cat /proc/cmdline root=/dev/disk/by-label/h50os123 ipv4only=1 apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe vga=794 3 12.3-3.7.10# inxi -C CPU: Dual core Intel Core2 Duo CPU E7600 (-MCP-) cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 ssse3 vmx) Clock Speeds: 1: 1603.00 MHz 2: 1603.00 MHz 13.1-3.8.2# cat /proc/cmdline root=/dev/disk/by-label/h50os131 ipv4only=1 apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe vga=794 3 13.1-3.8.2# inxi -C CPU: Dual core Intel Core2 Duo CPU E7600 (-MCP-) cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 ssse3 vmx) Clock Speeds: 1: 1603.00 MHz 2: 1603.00 MHz 13.1-3.9.0# cat /proc/cmdline root=/dev/disk/by-label/h50os131 ipv4only=1 apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe vga=794 3 CPUFREQ=0 13.1-3.9.0# inxi -C CPU: Dual core Intel Core2 Duo CPU E7600 (-MCP-) cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 ssse3 vmx) Clock Speeds: 1: 3059.100 MHz 2: 3059.100 MHz Maybe your problem needs asking on the opensuse-kernel list? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 05/05/2013 11:25 AM, Yamaban wrote:
[snip]
Hmm, when I compare that to my /proc/cmdline, the short answer would be to remove the following options:
noapic nolapic apm=off noresume edd=off nohz=off hires=off processor.max_cstate=1 nomodeset
Now, if you are unsure wether or not you NEED one of these options, start the remove action with:
edd=off (Monitor modi detection stuff, uncritical on most systems)
hires=off (hires timer, uncritical on most systems)
noapic, nolapic (every modern (past 2003/2004) needs apic to controll interrupt handling, no apic = nosmp)
apm=off (system power management, only need for shitty BIOS)
nohz=off (AFAIK Intel speedstep / AMD Cool'n'Quiet need that removed)
processor.max_cstate=1 (removal of this should be uncritical in nearly all situations)
nomodeset (when you remove this, the kernel tries to use kms during startup)
Addenum: For a first blind try I would remove: "apm=off edd=off nohz=off hires=off processor.max_cstate=1"
That still does not give you SMP, but gives you a measure off security. If the system still works fine (other than no smp), you have a first win on your side.
For the second try remove additionally: "noapic nolapic"
This should give you SMP.
At last you can remove: "nomodeset noresume"
To get a near standard install.
I hope this give you a hint where to start.
- Yamaban.
Yamaban That was VERY helpful and informative! Thank you very, very much. I now have SMP again Felix, The reason you didn't find it under kernel or factory is this issue first showed up under a stock install and I asked in the main support lists... Once again proving too narrow a scope of search will yield too little information. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2013-05-05 12:04 (GMT-0700) Bruce Ferrell composed:
I now have SMP again
What was the culprit? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 05/05/2013 03:04 PM, Bruce Ferrell wrote:
On 05/05/2013 11:25 AM, Yamaban wrote:
[snip]
Hmm, when I compare that to my /proc/cmdline, the short answer would be to remove the following options:
noapic nolapic apm=off noresume edd=off nohz=off hires=off processor.max_cstate=1 nomodeset
Now, if you are unsure wether or not you NEED one of these options, start the remove action with:
edd=off (Monitor modi detection stuff, uncritical on most systems)
hires=off (hires timer, uncritical on most systems)
noapic, nolapic (every modern (past 2003/2004) needs apic to controll interrupt handling, no apic = nosmp)
apm=off (system power management, only need for shitty BIOS)
nohz=off (AFAIK Intel speedstep / AMD Cool'n'Quiet need that removed)
processor.max_cstate=1 (removal of this should be uncritical in nearly all situations)
nomodeset (when you remove this, the kernel tries to use kms during startup)
Addenum: For a first blind try I would remove: "apm=off edd=off nohz=off hires=off processor.max_cstate=1"
That still does not give you SMP, but gives you a measure off security. If the system still works fine (other than no smp), you have a first win on your side.
For the second try remove additionally: "noapic nolapic"
This should give you SMP.
At last you can remove: "nomodeset noresume"
To get a near standard install.
I hope this give you a hint where to start.
- Yamaban.
Yamaban
That was VERY helpful and informative! Thank you very, very much.
I now have SMP again
Felix,
The reason you didn't find it under kernel or factory is this issue first showed up under a stock install and I asked in the main support lists... Once again proving too narrow a scope of search will yield too little information.
This should be added to a wiki. Very informative. -- Cheers! Roman ------------------------------------------------------- openSUSE -- Get it! Discover it! Share it! ------------------------------------------------------- http://linuxcounter.net/ #179293 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sun, 5 May 2013 21:17, Felix Miata
On 2013-05-05 12:04 (GMT-0700) Bruce Ferrell composed:
I now have SMP again
What was the culprit?
From past experience, I'd like to think "noapic nolapic", some systems also need apm to use smp.
- Yamaban. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 05/05/2013 12:17 PM, Felix Miata wrote:
On 2013-05-05 12:04 (GMT-0700) Bruce Ferrell composed:
I now have SMP again
What was the culprit?
The apic settings, noapic and nolapic have been removed as has nomodeset. I also removed processor.max_cstate=1 I suspect the edd setting is what causes the LCD to go into self test mode... Not important right now Can someone point me to a document with a complete list of all the possibilities? I like to be complete Thanks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2013-05-05 12:04 (GMT-0700) Bruce Ferrell composed:
The reason you didn't find it under kernel or factory is this issue first showed up under a stock install and I asked in the main support lists... Once again proving too narrow a scope of search will yield too little information.
A problem too often induced by too little information, and sometimes by too much information, in a plea for help. The opensuse list has a lot of noise to wade through, so I search there as little as I can get away with, as WRT issues I first see raised here. :-p -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2013-05-05 12:24 (GMT-0700) Bruce Ferrell composed:
Felix Miata wrote:
On 2013-05-05 12:04 (GMT-0700) Bruce Ferrell composed:
I now have SMP again
What was the culprit?
The apic settings, noapic and nolapic have been removed as has nomodeset. I also removed processor.max_cstate=1
IOW, you don't know? Consequently, we, and Google, still don't know. It's hard to imagine every one of those had to be removed to solve one single problem.
I suspect the edd setting is what causes the LCD to go into self test mode... Not important right now
Can someone point me to a document with a complete list of all the possibilities?
Like these? https://www.kernel.org/doc/Documentation/kernel-parameters.txt
I like to be complete -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 05.05.2013 21:24, schrieb Bruce Ferrell:
I suspect the edd setting is what causes the LCD to go into self test mode... Not important right now
No. edd is the enhanced disk detection (or similar), that allows the kernel to know what the BIOS is thinking about which disk is which. It has absolutely nothing to do with anything display related. -- Stefan Seyfried "If your lighter runs out of fluid or flint and stops making fire, and you can't be bothered to figure out about lighter fluid or flint, that is not Zippo's fault." -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sun, 5 May 2013 21:24, Bruce Ferrell
On 05/05/2013 12:17 PM, Felix Miata wrote:
On 2013-05-05 12:04 (GMT-0700) Bruce Ferrell composed:
I now have SMP again
What was the culprit?
The apic settings, noapic and nolapic have been removed as has nomodeset. I also removed processor.max_cstate=1
I suspect the edd setting is what causes the LCD to go into self test mode... Not important right now
Can someone point me to a document with a complete list of all the possibilities?
I like to be complete
As a starting point, use the documenation of the kernel source, (e.g. from kernel-source-3.7.10-1.1.1.noarch.rpm) the files the directory /usr/src/linux/Documentation/ and deeper, esp: .../Documentation/kernel-parameters.txt .../Documentation/x86/boot.txt and .../Documentation/x86/x86_64/boot-options.txt or for a web-search: linux kernel boot-options see: "THE SOURCE" https://www.kernel.org/doc/Documentation/kernel-parameters.txt https://www.kernel.org/doc/Documentation/x86/boot.txt https://www.kernel.org/doc/Documentation/x86/x86_64/boot-options.txt (Be aware the the links on kernel.org point to the lastest stable release.) Others: http://tldp.org/HOWTO/BootPrompt-HOWTO.html (old 2003-03-21) https://help.ubuntu.com/community/BootOptions (Ubuntu 10.4, near pageend) https://www.centos.org/docs/4/html/rhel-ig-x8664-multi-en-4/ap-bootopts.html (old) https://fedoraproject.org/wiki/Common_kernel_problems (modif.2012, most common uses) And yes, there is a great 'empty' on opensuse.org on this matter. - Yamaban. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sun, 5 May 2013 22:19, Stefan Seyfried
Am 05.05.2013 21:24, schrieb Bruce Ferrell:
I suspect the edd setting is what causes the LCD to go into self test mode... Not important right now
No. edd is the enhanced disk detection (or similar), that allows the kernel to know what the BIOS is thinking about which disk is which. It has absolutely nothing to do with anything display related.
Ups, my bad, thanks for the info. Yes, that display stuff is named "edid" - Yamaban. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Bruce Ferrell
[snip]
Hmm, when I compare that to my /proc/cmdline, the short answer would be to remove the following options:
noapic nolapic apm=off noresume edd=off nohz=off hires=off
On 05/05/2013 11:25 AM, Yamaban wrote: processor.max_cstate=1 nomodeset
Now, if you are unsure wether or not you NEED one of these options, start the remove action with:
edd=off (Monitor modi detection stuff, uncritical on most systems)
hires=off (hires timer, uncritical on most systems)
noapic, nolapic (every modern (past 2003/2004) needs apic to
controll interrupt handling, no apic = nosmp)
apm=off (system power management, only need for shitty BIOS)
nohz=off (AFAIK Intel speedstep / AMD Cool'n'Quiet need that removed)
processor.max_cstate=1 (removal of this should be uncritical in
nearly all situations)
nomodeset (when you remove this, the kernel tries to use kms during
startup)
Addenum: For a first blind try I would remove: "apm=off edd=off nohz=off hires=off processor.max_cstate=1"
That still does not give you SMP, but gives you a measure off
security.
If the system still works fine (other than no smp), you have a first win on your side.
For the second try remove additionally: "noapic nolapic"
This should give you SMP.
At last you can remove: "nomodeset noresume"
To get a near standard install.
I hope this give you a hint where to start.
- Yamaban.
Yamaban
That was VERY helpful and informative! Thank you very, very much.
I now have SMP again
Felix,
The reason you didn't find it under kernel or factory is this issue first showed up under a stock install and I asked in the main support lists... Once again proving too narrow a scope of search will yield too little information.
Thinking of search, have you guys seen the new http://opensuse.markmail.org It only goes back to Jan, but even 4 months of messages is pretty cool. I love their weui. Greg -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 05/05/2013 12:44 PM, Felix Miata wrote:
On 2013-05-05 12:24 (GMT-0700) Bruce Ferrell composed:
Felix Miata wrote:
On 2013-05-05 12:04 (GMT-0700) Bruce Ferrell composed:
I now have SMP again
What was the culprit?
The apic settings, noapic and nolapic have been removed as has nomodeset. I also removed processor.max_cstate=1
IOW, you don't know? Consequently, we, and Google, still don't know. It's hard to imagine every one of those had to be removed to solve one single problem.
I suspect the edd setting is what causes the LCD to go into self test mode... Not important right now
Can someone point me to a document with a complete list of all the possibilities?
Like these? https://www.kernel.org/doc/Documentation/kernel-parameters.txt
I like to be complete
Felix, Do you have anything to contribute beyond jibes? Please sit down and shut up. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2013-05-06 07:10 (GMT-0700) Bruce Ferrell composed:
Felix Miata wrote:
On 2013-05-05 12:24 (GMT-0700) Bruce Ferrell composed:
Felix Miata wrote:
On 2013-05-05 12:04 (GMT-0700) Bruce Ferrell composed:
I now have SMP again
What was the culprit?
The apic settings, noapic and nolapic have been removed as has nomodeset. I also removed processor.max_cstate=1
IOW, you don't know? Consequently, we, and Google, still don't know. It's hard to imagine every one of those had to be removed to solve one single problem.
I suspect the edd setting is what causes the LCD to go into self test mode... Not important right now
Can someone point me to a document with a complete list of all the possibilities?
Like these? https://www.kernel.org/doc/Documentation/kernel-parameters.txt
I like to be complete
Felix,
Do you have anything to contribute beyond jibes? Please sit down and shut up.
You didn't answer the question which cmdline parameter fixed your problem. Don't you think those who tried to help, and the archives, deserve to know that fixed it so that maybe next time someone can find the answer via search instead of thread? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Bruce Ferrell
Felix,
Do you have anything to contribute beyond jibes? Please sit down and shut up.
Ah, perhaps a little thought on your part would allay your frustration and lack of tact. It is normal and expected that one post specifics when a solution is reached and the manner is not *obvious*. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 05/06/2013 07:55 AM, Felix Miata wrote:
On 2013-05-06 07:10 (GMT-0700) Bruce Ferrell composed:
Felix Miata wrote:
On 2013-05-05 12:24 (GMT-0700) Bruce Ferrell composed:
Felix Miata wrote:
On 2013-05-05 12:04 (GMT-0700) Bruce Ferrell composed:
I now have SMP again
What was the culprit?
The apic settings, noapic and nolapic have been removed as has nomodeset. I also removed processor.max_cstate=1
IOW, you don't know? Consequently, we, and Google, still don't know. It's hard to imagine every one of those had to be removed to solve one single problem.
I suspect the edd setting is what causes the LCD to go into self test mode... Not important right now
Can someone point me to a document with a complete list of all the possibilities?
Like these? https://www.kernel.org/doc/Documentation/kernel-parameters.txt
I like to be complete
Felix,
Do you have anything to contribute beyond jibes? Please sit down and shut up.
You didn't answer the question which cmdline parameter fixed your problem. Don't you think those who tried to help, and the archives, deserve to know that fixed it so that maybe next time someone can find the answer via search instead of thread?
I think Felix, I've taken a bit of time to pull YOU on google and I see this is all you do on ALL the lists you're active on. You're a useless troll. Were it not against my personal policy to place filters on lists I subscribe to, you'd be in my mail kill file. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 05/06/2013 08:13 AM, Patrick Shanahan wrote:
* Bruce Ferrell
[05-06-13 10:12]: [...] Felix,
Do you have anything to contribute beyond jibes? Please sit down and shut up.
Ah, perhaps a little thought on your part would allay your frustration and lack of tact. It is normal and expected that one post specifics when a solution is reached and the manner is not *obvious*.
No Pat (may I call you Pat), the signal to noise ratio of this list has gotten way too high from trolls who contribute little nothing.... And "can't we all just get along" is also not contributory nor is it terribly useful except to the self righteous. The information provided by Yamaban WAS a real and useful contribution and was acknowledged; as were the thoughts expressed by other that wiki is lacking in the information provided. You may call it a lack of tact. I say I'm simply direct and sugar coat nothing. And this too, is not contributory or terribly useful so this is the last I'll say to you, Felix or anyone else on the topic of "manners" on this technical list. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2013-05-06 08:24 (GMT-0700) Bruce Ferrell composed:
You didn't answer the question which cmdline parameter fixed your problem. Don't you think those who tried to help, and the archives, deserve to know that fixed it so that maybe next time someone can find the answer via search instead of thread?
I think Felix, I've taken a bit of time to pull YOU on google and I see this is all you do on ALL the lists you're active on. You're a useless troll. Were it not against my personal policy to place filters on lists I subscribe to, you'd be in my mail kill file.
I really don't get your complaint. If it's about my questions, they're typically designed to get people to think about what was written[1], typically to get a writer to think about an apparent lack of completeness, usefulness and/or validity to what he wrote. In this thread, you were asked a question that help list etiquette dictated you give, and you responded without giving an apparent answer. Do you really think solving your problem required that you remove all of 4 or 5 parameters from cmdline? I doubt I'm the only thread reader to think that implausible. [1] http://en.wikipedia.org/wiki/Socratic_method -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 5/5/2013 at 02:25 PM, Yamaban
wrote: On Sun, 5 May 2013 17:36, Bruce Ferrell wrote: On 05/05/2013 02:37 AM, Felix Miata wrote: On 2013-05-04 19:08 (GMT-0700) Bruce Ferrell composed: my grub boot options are: noapic nolapic apm=off noresume edd=off nohz=off hires=off processor.max_cstate=1 nomodeset resume=/dev/disk/by-id/ata-ST9320421ASG_5TJ0Q4HY-part2 splash=silent quiet showopts
Is that the content of /proc/cmdline, or your perusal of some latter portion your Grub menu file? If the former, why are you using it???
Felix, it is in fact the contents of the /boot/grub.d/grub.cfg. to give you
what you requested, rather than asking why you requested it:
more /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-3.8.9-5-desktop root=UUID=a3b45d4e-a3dc-4e0f-9b24-2d0d4f65c221 noapic nolapic apm=off noresume edd=off powersaved=off nohz=off hires=off processor.max_cstate=1 nomodeset resume=/dev/disk/by-id/ata-ST9320421ASG_5TJ0Q4HY-part2 splash=silent quiet showopts [snip]
Hmm, when I compare that to my /proc/cmdline, the short answer would be to remove the following options:
noapic nolapic apm=off noresume edd=off nohz=off hires=off processor.max_cstate=1 nomodeset
Now, if you are unsure wether or not you NEED one of these options, start the remove action with:
edd=off (Monitor modi detection stuff, uncritical on most systems)
hires=off (hires timer, uncritical on most systems)
noapic, nolapic (every modern (past 2003/2004) needs apic to controll interrupt handling, no apic = nosmp)
apm=off (system power management, only need for shitty BIOS)
nohz=off (AFAIK Intel speedstep / AMD Cool'n'Quiet need that removed)
nohz is for enable/disable dynamic timer ticks. It helps with power savings, but has little to do with Intel SpeedStep / AMD Cool'n'Quiet, other than allowing the CPU to go truly idle by the system not triggering timer interrupts CONFIG_HZ times a second when it's unnecessary. See http://kerneltrap.org/node/6750 HTH, --Tom -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (9)
-
Bruce Ferrell
-
Felix Miata
-
Greg Freemyer
-
Jan Engelhardt
-
Patrick Shanahan
-
Roman Bysh
-
Stefan Seyfried
-
Tom Abraham
-
Yamaban