Red Hat Bugzilla – Bug 567565
Problem for every booting
Last modified: 2010-02-26 02:33:08 EST
Created attachment 395674 [details]
Description of problem:
Whenever I try to restart a computer after 10 or 15 minutes of time span. I get this error. but on next restart this error vanishes.
Version-Release number of selected component (if applicable):
Just switch of computer more than 15 mintues. and then start the computer.
you will see such error.
Steps to Reproduce:
1. Close computer for 15minute
2. Start the computer.
3. And you will see this error
My Laptop is of Compaq Presario V6000 (2 months before I changed HDD for same reason,thinking that it might be corrupted.) I have removed DVD ROM. but after purchasing I have check HDD its working. even I have checked memory with memtest everything is fine.
Some time udev give lots error. sometime it gives different message. as i have restart machine by force close.
Starting udev: udevd: worker  unexpectedly returned with status 0x000b
udevd: worker  failed while handling '/devices/virtual/tty/tty46'
Hmm, it segfaulted.. looks like a hardware issue, if you say that it gives a different message every time.
Bad memory, I would suspect.
Please Please Please Please answer me. bad memories means HDD or RAM ? because I can't judge it. might be you are much knowledge people might know it.
I would guess RAM... but it's just a guess... time for a "memtest"
"even I have checked memory with memtest everything is fine."
doh.. should have reread the first comment :)
Sorry.. don't know how else to test... maybe fsck the filesystem?
Boot with "forcefsck" on the kernel command line.
Thank you for your honest support. I did the same way you told.
but I have not tested error. as because right now laptop is working on. so tomorrow (in night machine will be poweroff for longer time) I will start computer to check whether that errors are coming or not.
I have attached new boot.log file. looks like they have fixed something. I really wish God that I would not get error again by atleast udev ;).
This is Brand new HDD. (just 2 month old) but that error occurred from the first day of installation. For the same reason I don't move Laptop to anywhere.
Created attachment 395704 [details]
After comment#5 boot.log
dehaviour is same. I don't see any difference forcefsck.
Now lets imagin that I have problem with HDD. then there should not be any problem while running on Flash Drive (Pen Drive). so I created fresh LiveUSB (Purchased 4 months before). and Installed LiveIso on Pen drive. and still I am getting segment fault. now what do you suggest? attached here boot.log.
I still thinks that its really Problem with udev coding. for my specific hardware configuration.
Created attachment 396211 [details]
This boot.log file running from LiveUSB.
One more important thing is that memtest is still 100% Pass.
If you think that their is come kind of problem in machine. Please Please may I still know which hardware causing the issue?
(In reply to comment #9)
> Created an attachment (id=396211) [details]
> This boot.log file running from LiveUSB.
/etc/rc.d/rc.sysinit: line 47: 466 Segmentation fault /sbin/restorecon -R /dev 2> /dev/null
this is not udev!
CPU or memory is my guess.. your hardware is really broken in some way. Is your CPU overclocked?
Harald... I have given one more attempt for memtest84 and found memory RAM is giving me error. Today/tomorrow I will purchase new RAM. I hope this will resolve the issue. Really Thank you for giving me help.
I have not made cpu overcloked. but how to check whether its being overclocked or not. ?
If you did not overclock manually, then it's not overclocked.
Faulty RAM and bad memory lead to such spurious segfaults. Bad disk might also be, but normally it fails with the same error over and over then.
(In reply to comment #12)
> Faulty RAM and bad memory lead to such spurious segfaults.
I meant: "Faulty RAM or overclocked CPUs show such spurious segfaults."
I really appreciate your support for my non software related problem. Thank you, Thank you so much. If in case after changing the RAM if I found still problem. then I would like to open this bug again. :). Hats off for support.
Now I have changed with new samsung ram. Things looks perfect. and no startup errors. I wish now you can close the bug with "no a bug". Thank you for support.
Glad, that it turned out to be a HW problem. Have fun! :-)