LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
LinkBack Search this Thread
Old 10-18-2013, 01:59 PM   #1
FeyFre
Member
 
Registered: Jun 2010
Location: Ukraine, Vinnitsa
Distribution: Slackware
Posts: 305

Rep: Reputation: 22
Workaround to work w/ overclocked CPUs?


Hi. This is my story:
My desktop system:
CPU AMD A4-3400 (2.7GHz)
MB: ASrock A75M-HVS
(output lspci attached)
HDD: Hitachi HDS721050CLA362 500GB (SATA)
Slakcware-current, tried versions of 14.1-rc1(3.10.16-smp) and a bit older one(3.8.8-smp kernel).

LILO loads kernel/initrd image successfully, but, when kernel wants to mount root partition it reports absence of root disk. The same problem on Slax-7.0.8 on USB (HDD not detected). Other devices work perfectly.

Found temporary workaround of this problem: a bit earlier I have overclocked CPU from 2.7GHz to 3.2GHz. When I reset overclocking kernel can detect HDD, and boots successfully.

So question: is there any boot-time kernel parameters or build-time configurations which can help kernel to detect my HDD? This is not hardware problem in any case, because WindowsXP does detects HDD in overclocked mode anyway. And I not going to reset overclock every time I boot linux, because I want system work overclocked.

Regards
Attached Files
File Type: txt lspci-t-vv-M-nn-Q-k.txt (24.5 KB, 4 views)

Last edited by FeyFre; 10-18-2013 at 06:28 PM. Reason: opps, original freq was 2.7GHz, not 3GHz
 
Old 10-18-2013, 02:59 PM   #2
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 836

Rep: Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620Reputation: 1620
My computer runs at 3.3GHz (not overclocked), and the kernel has no issues with that (so it's not like the kernel can't handle 3.2GHz if the hardware is stable). I'd say that more than likely the situation with your machine is, in fact, a hardware problem due to overclocking, even if XP isn't showing any immediate symptoms.
 
1 members found this post helpful.
Old 10-18-2013, 03:16 PM   #3
ReaperX7
Senior Member
 
Registered: Jul 2011
Distribution: LFS-SVN, Slackware-14.1, PCBSD-10.0
Posts: 2,427
Blog Entries: 14

Rep: Reputation: 590Reputation: 590Reputation: 590Reputation: 590Reputation: 590Reputation: 590
What partitioning method did you use?
 
Old 10-18-2013, 04:58 PM   #4
chemfire
Member
 
Registered: Sep 2012
Posts: 67

Rep: Reputation: Disabled
The kernel used to have a parameter rootdelay=N where N was the number of seconds for it to sleep before trying to mount the root filesystem.

It is/was for dealing with root devices that were on external storage and might require some spin up time. You can add it to the append= line in /etc/lilo. It may or may not help, worth a try I supposed.

I am inclined toward volkerdi's opinion however, sounds like stability problems related to the over clock. Even if you can make it work, I would not be real excited about running a machine that exhibits quirkiness related to disk I/O.
 
Old 10-18-2013, 06:05 PM   #5
FeyFre
Member
 
Registered: Jun 2010
Location: Ukraine, Vinnitsa
Distribution: Slackware
Posts: 305

Original Poster
Rep: Reputation: 22
> What partitioning method did you use?
Old good MBR created by cfdisk long time ago(since 13.0 I think). I don't think it influences problem.

> The kernel used to have a parameter rootdelay=N where N was the number of seconds for it to sleep before trying to mount the root filesystem.

As I said earlier, I tried boot slax(doesn't requires hdd to boot) on this machine, and long after full boot no HDD-related /dev/sd* devices was detected.
But I tried to boot using this additional parameter(rootdelay=10) on both 3.8.8 and 3.10.16 ... not changes detected except notification of waiting in boot log. During boot of windows I do not hear any special spin-up sounds(all spin-ups done during POST of 1st cold boot).
Can anybody describe what mean 4 lines at time 2.228-2.244? I don't like them. (I shall try reset overclock and see if they disappeared).


> a hardware problem due to overclocking,
Looks like for me too, but logic votes for opposite side: same conditions, only software differs, logically problem in software. So I hope there is some soft- solution.
Attached Images
File Type: jpg IMG_0115.JPG (237.8 KB, 30 views)
 
Old 10-18-2013, 06:43 PM   #6
FeyFre
Member
 
Registered: Jun 2010
Location: Ukraine, Vinnitsa
Distribution: Slackware
Posts: 305

Original Poster
Rep: Reputation: 22
So, I have reset overclocking back to native 2.7GHz and examined log. Now I can see, there is only 3 lines(SATA link down) left(time 2.324), one disappeared(of ata1, my hdd connected to 1st of 6 sata sockets).

And I noticed weird:
"SATA link down" notifications in overclocked mode printed relatively late then in not-overclocked mode, for instance relatively to message "Using IPI No-Shortcut mode" and to messages of net subsystem initialization. I shall search for sources of this message, probably there are some specific parameter that influence behavior.
Attached Images
File Type: jpg IMG_0116.jpg (187.1 KB, 8 views)
 
Old 10-19-2013, 03:44 PM   #7
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Slackware
Posts: 14,880
Blog Entries: 2

Rep: Reputation: 3806Reputation: 3806Reputation: 3806Reputation: 3806Reputation: 3806Reputation: 3806Reputation: 3806Reputation: 3806Reputation: 3806Reputation: 3806Reputation: 3806
Quote:
Originally Posted by FeyFre View Post
a bit earlier I have overclocked CPU from 2.7GHz to 3.2GHz. When I reset overclocking kernel can detect HDD, and boots successfully.
To follow your own logic: Same condition, only hardware differs, so a hardware problem. How have you actually determined that your system is stable at 3.2GHz?
 
Old 10-19-2013, 06:09 PM   #8
FeyFre
Member
 
Registered: Jun 2010
Location: Ukraine, Vinnitsa
Distribution: Slackware
Posts: 305

Original Poster
Rep: Reputation: 22
Well, at least 2-3 month(or even more, cant remember precisely) I work on this PC in overclocked mode on Windows XP, and no malfunction was detected. Well, I consider this stable.
 
Old 10-19-2013, 09:32 PM   #9
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Slackware
Posts: 14,880
Blog Entries: 2

Rep: Reputation: 3806Reputation: 3806Reputation: 3806Reputation: 3806Reputation: 3806Reputation: 3806Reputation: 3806Reputation: 3806Reputation: 3806Reputation: 3806Reputation: 3806
Quote:
Originally Posted by FeyFre View Post
Well, at least 2-3 month(or even more, cant remember precisely) I work on this PC in overclocked mode on Windows XP, and no malfunction was detected. Well, I consider this stable.
In other words, no stress tests were used to confirm stability and you have malfunctions in Linux when running the system overclocked. I wouldn't consider that stable, but to each his own. Reduce your overclock and see when you get a functioning Linux system, use stress tests to confirm stability.
 
Old 10-20-2013, 05:57 AM   #10
55020
Member
 
Registered: Sep 2009
Location: Yorks. W.R. 167397
Distribution: Slackware
Posts: 272
Blog Entries: 4

Rep: Reputation: 256Reputation: 256Reputation: 256
Quote:
Originally Posted by FeyFre View Post
I work on this PC in overclocked mode on Windows XP, and no malfunction was detected
It's quite possible that it's specific machine instructions which fail consistently because of the overclock, and if XP never executes those instructions (different embedded assembler code, or different compiler with different optimisations, or different strategy for accessing PCI memory, or 32/64 bit) then XP never fails.

Last edited by 55020; 10-20-2013 at 06:00 AM. Reason: red herring about bitness
 
Old 10-20-2013, 05:59 AM   #11
Raveriux
Member
 
Registered: Jul 2013
Location: Lithuania
Distribution: Slackware64 14, Slackware64 -current, Maemo
Posts: 74

Rep: Reputation: Disabled
As I ran into a big problems to start firewire controller yesterday I can say that the biggest problem is here:

Quote:
Originally Posted by FeyFre View Post
MB: ASrock A75M-HVS
 
  


Reply

Tags
kernel, overclock, parameters


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Getting Flash plug-in to work with older CPUs DavidMcCann LinuxQuestions.org Member Success Stories 7 Yesterday 07:52 PM
ZendGuardLoader.so requires httpd_execmem to work, workaround found but... mysteron Linux - Security 1 10-18-2012 01:00 PM
[SOLVED] Overclocked CPU using P-States: is Linux running it at the overclocked frequency? vik Linux - General 5 08-29-2012 08:40 PM
how does TOP work with 2 CPUs ipanema Linux - Server 6 10-23-2007 01:01 AM
Bad /proc/cpuinfo or processor overclocked!!! pulsez Linux - Laptop and Netbook 1 11-10-2005 05:19 AM


All times are GMT -5. The time now is 02:27 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration