LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
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
  Search this Thread
Old 01-07-2011, 12:00 AM   #46
anti_user
Member
 
Registered: May 2008
Location: Russia, Ural
Distribution: Slackware Current
Posts: 69

Rep: Reputation: 4

Quote:
Originally Posted by Old_Fogie View Post
Hello all,

I have two boxen running --current. Over the last two weeks (give or take) they both will randomly just lockup during the boot process.

I'd say this all began around the time I had this issue, which is still randomly occuring:

http://www.linuxquestions.org/questi...-drive-851900/


I don't know how to duplicate it so it happens every boot. But an un-scientific guess is, that I have these lockups 1 out of every five boot ups.

The problem does happen when the pc's are:

1. powered off, and booting up,
2. reboot issued.

But it's not *every* time.

I'm using an initrd for jfs filesystem on both machines.

I have no logs, as the boot process comes to life, I see the message where it's trying to bring up floppy drive, it sits there for about 2 to 3 seconds, and then a bunch of errors are spewed to the screen.

The oops lines are all references sata in one way or another.

Now one pc is indeed using a sata as the "/"

The other pc uses a pata drive for "/" but there is sata ports on that motherboard, but they are not in use at all for that pc.

Since the pc's are locking up prior to the drives being mounted, I don't think anything is able to get logged yet. I don't see anything in my logs, so I don't know what I may be able to post here.

One pc uses:
IDE interface: Intel Corporation 82801FB/FW (ICH6/ICH6W) SATA Controller (rev 03)

And the other uses:
an asus a7n8x-e deluxe nforce 2 motherboard that doesnt even list the sata controllers as there is nothing plugged into them.

Any thoughts greatly appreciated.
Yes, I have the same trouble with my laptop HP 6910p. Hope, this bug will be fix in the future
 
Click here to see the post LQ members have rated as the most helpful post in this thread.
Old 01-07-2011, 09:54 AM   #47
aaazen
Member
 
Registered: Dec 2009
Posts: 357

Rep: Reputation: Disabled
Quote:
Originally Posted by rworkman View Post
comet.berkeley, the /dev/root symlink problem was already fixed.

Kay Sievers (udev maintainer) says that this is definitely a kernel bug, even though the change to ata_id is what triggered it. Any chance someone can try to reproduce this on 2.6.35.10? How about 2.6.36.2?

I personally am on 2.6.36.2 and I've not seen it on any of my systems, even those with old ide devices.

Using the current slackware release and udev-165 I have yet to find a kernel where it does not crash sooner or later.

I have crashed the following kernels with the same error:
2.6.35.7
2.6.35.10
2.6.36.2

Is there another kernel to try?
 
Old 01-07-2011, 12:36 PM   #48
BratPit
Member
 
Registered: Jan 2011
Posts: 237

Rep: Reputation: 85
Quote:
Originally Posted by comet.berkeley View Post
Using the current slackware release and udev-165 I have yet to find a kernel where it does not crash sooner or later.

I have crashed the following kernels with the same error:
2.6.35.7
2.6.35.10
2.6.36.2

Is there another kernel to try?
Hello.

Last but not least.

Better check machine with "mprime" /stress test/.
Sometimes overclocking or undervolting processor causing the same.
 
Old 01-08-2011, 09:20 AM   #49
aaazen
Member
 
Registered: Dec 2009
Posts: 357

Rep: Reputation: Disabled
Quote:
Originally Posted by BratPit View Post
Hello.

Last but not least.

Better check machine with "mprime" /stress test/.
Sometimes overclocking or undervolting processor causing the same.
No the box is fine and runs Slackware stable and other operating systems with no problems.

This crash only happens on Slackware current when the kernel is just starting up.

So for now I will test udev-164 and Slackware current and see if I get the crash.
 
Old 01-08-2011, 04:23 PM   #50
afreitascs
Member
 
Registered: Aug 2004
Distribution: Debian
Posts: 443

Rep: Reputation: 30
Quote:
Originally Posted by comet.berkeley View Post
Using the current slackware release and udev-165 I have yet to find a kernel where it does not crash sooner or later.

I have crashed the following kernels with the same error:
2.6.35.7
2.6.35.10
2.6.36.2

Is there another kernel to try?
I tested now with kernel 2.6.37 and got the same problem ....

Last edited by afreitascs; 01-08-2011 at 04:25 PM. Reason: typing error
 
Old 01-09-2011, 07:24 PM   #51
smoooth103
Member
 
Registered: Aug 2009
Location: NC, USA
Distribution: Slackware (64 bit)
Posts: 242

Rep: Reputation: 62
Is there anywhere on the official mirror that I can grab udev-164 package(or whichever was the previous version) that will fix this problem. I'm generally hesitant to download packages from 3rd parties (unless of course it's AlienBob or Rworkman).
 
Old 01-09-2011, 07:54 PM   #52
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 2,378

Rep: Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936Reputation: 936
You can get udev-164.tar.bz2 from its usual mirrors and build it with the -current build script.
 
Old 01-09-2011, 08:16 PM   #53
smoooth103
Member
 
Registered: Aug 2009
Location: NC, USA
Distribution: Slackware (64 bit)
Posts: 242

Rep: Reputation: 62
Oh! I never really explored the mirrors much and didn't realize the slackbuilds were there in /source for -current. Thanks.
 
Old 01-10-2011, 12:36 AM   #54
Petri Kaukasoina
Member
 
Registered: Mar 2007
Posts: 413

Rep: Reputation: 265Reputation: 265Reputation: 265
Quote:
Originally Posted by smoooth103 View Post
Is there anywhere on the official mirror that I can grab udev-164 package(or whichever was the previous version) that will fix this problem. I'm generally hesitant to download packages from 3rd parties (unless of course it's AlienBob or Rworkman).
If you want the package PV built, I have it here: http://butler.cc.tut.fi/~kaukasoi/slackware/. You should of course check his pgp signature using the .asc file, as always.

(I copied the package from the backups of elektroni.phys.tut.fi, an "official" mirror that I run, but it's no proof the file is the real one, the pgp signature is.)
 
Old 01-10-2011, 03:33 AM   #55
conraid
Member
 
Registered: Feb 2008
Location: Leghorn, Tuscany, Italy
Distribution: Slackware
Posts: 111

Rep: Reputation: 33
I have sometimes the same trouble with -current and various kernel. I haven't tried with udev 164
 
Old 01-11-2011, 11:43 PM   #56
aaazen
Member
 
Registered: Dec 2009
Posts: 357

Rep: Reputation: Disabled
There is a new Slackware current.

udev-165 appears to contain a patch and the kernel is upgraded to 2.6.35.10

I got good results using udev-164 and kernel 2.6.35.7 but I will upgrade to current and keep you posted.
 
Old 01-12-2011, 08:08 AM   #57
hitest
Guru
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware
Posts: 5,874

Rep: Reputation: 2047Reputation: 2047Reputation: 2047Reputation: 2047Reputation: 2047Reputation: 2047Reputation: 2047Reputation: 2047Reputation: 2047Reputation: 2047Reputation: 2047
Quote:
Originally Posted by comet.berkeley View Post
There is a new Slackware current.

udev-165 appears to contain a patch and the kernel is upgraded to 2.6.35.10
The udev patch and new kernel are working well for me; the random crashes have stopped.

Last edited by hitest; 01-12-2011 at 09:18 AM.
 
Old 01-12-2011, 01:44 PM   #58
PainlessRob
LQ Newbie
 
Registered: Jan 2011
Distribution: Arch
Posts: 1

Rep: Reputation: 0
Quote:
Originally Posted by resonance View Post
Additional experimentation:
Another possible cause of this oops could be inappropriate buffer alignment. I built udev-165 with ata_id.c patched to use page-aligned sense and response buffers (rather than simple unsigned char arrays), and so far it looks promising- no panics yet (see attached patch).
I've been using udev 165 patched with resonance's ata-pass-through-memalign patch for a couple of days, seems stable so far ... thanks resonance.
 
Old 01-12-2011, 05:12 PM   #59
smoooth103
Member
 
Registered: Aug 2009
Location: NC, USA
Distribution: Slackware (64 bit)
Posts: 242

Rep: Reputation: 62
issued solved for me with -current upgrade. thanks all.
 
Old 01-13-2011, 01:59 AM   #60
conraid
Member
 
Registered: Feb 2008
Location: Leghorn, Tuscany, Italy
Distribution: Slackware
Posts: 111

Rep: Reputation: 33
In three boot still no crash. Good
 
  


Reply


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



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Slackware-current Kernel OOPS fl0 Slackware 10 05-06-2010 01:17 AM
bad-timed question about current multios Slackware 1 05-21-2009 03:10 AM
X server randomly crashes since update to Current intens Slackware 8 06-16-2007 05:18 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 04:01 AM.

Main Menu
Advertisement
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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration