You are not logged in.
Pages: 1
http://88.113.120.141/bootchart.png [outofdate]
Hello. I just installed bootchart becouse my boot process is so slow. Now, when looking on it I can see that there is init process sleeping 20 seconds and then the action begins. So what's wrong? My specs are: 2.6ghz P4, 512mb ram, ati radeon 9600. I don't know what configs should I post. Also, I don't know if this is right place for questions like this. Thanks.
Excuse my poor ensligh.
Last edited by igglybuff (2007-10-24 15:14:44)
Offline
Does your computer do anything for the 20 seconds? Any hard drive activity? Anything on the screen?
EDIT: Try init=/bin/bash. Does this take long to start too?
Karol Swietlicki
Last edited by magotari (2007-09-27 17:38:47)
Offline
Eh.. how I can add /bin/bash to init if there is already /sbin/bootchartd?
E: Kernel panic when trying /bin/bash :>
Btw, there is some "Waiting for devices to settle..." and "sd 1:0:0:0: [sda] Attached SCSI disk" -things what takes couple of seconds.
Last edited by igglybuff (2007-09-27 18:12:48)
Offline
No, just one init at a time...
Couple of seconds does not account for 20.
I am at a loss here. Anyone else?
Offline
bump...
Offline
Is it waiting for devices to come ready? I have seen that message seen scrolling by fairly often, although my boot is quite swift . Brand new box here though...
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
I think so, but it stays there for 20 seconds and it's way too much i think. Does it matter, becouse it comes before "Archlinux (Don't panic)" and "> Loading modules".
Brand new box, sarcasm?
Offline
Are your "/" partition on your sda disk? If not, you could tweak your initcpio setup, so it wont load the scsi modules, which might solve the issue.
Offline
Eh.. how i can know are they? I've only one harddisk?
>: df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda3 8.7G 2.3G 6.0G 28% /
none 252M 0 252M 0% /dev/shm
/dev/sda1 69M 10M 55M 16% /boot
/dev/sda4 67G 4.9G 58G 8% /home
what can i do now
Last edited by igglybuff (2007-09-29 16:08:53)
Offline
What part in that bootchart is those 20 seconds we're talking about here? The very beginning, or that "sleep" under "bootchartd"?
Does turning off dhcp solve it? Turn it off in your /etc/rc.conf (set it to some a static address), reboot, see if it is better.
Could you post your rc.conf? And I doubt that this has anything to do with it, but why do you want to set your locale by passing it as an option to your kernel (as opposed to setting it in rc.conf)
Well actually, when exactly does it happen? I'm not sure, but you mean you start your computer, choose "Arch Linux" in your boot manager, then the screen "flips", you see the Archlogo and the Kernelstuff scroll by, then it hangs for those 20 seconds and then it continues normally printing "Arch Linux (Don't panic)" on your screen and it starts processing rc.conf (loading modules, setting hostname, and so on and so forth), right? That's how it happens or did I mistake you?
If so, then it happens even before rc.sysinit is called. And the only things that are happen prior to that are: your kernel is getting extracted into the memory and it initializes itself (gathers information about your hardware from your mainboards BIOS, defines it's internal structures) and then the kernel calles init.
So unless someone tampered with your /etc/inittab (what does 'grep sysinit /etc/inittab' say?) it can actually only be something with the kernel, or init.
Has it always been like that or did this start recently?
edit: Since it apparently can't be due to something set in your rc.conf, I guess I don't need to see it, but your /boot/grub/menu.1st respectively your lilo-config could be interesting to see. Same goes for /var/log/kernel.log and /var/log/messages.log
Last edited by hybrid (2007-09-29 16:58:06)
Offline
What part in that bootchart is those 20 seconds we're talking about here? The very beginning, or that "sleep" under "bootchartd"?
Does turning off dhcp solve it? Turn it off in your /etc/rc.conf (set it to some a static address), reboot, see if it is better.
No, turning off didn't solve it.
Could you post your rc.conf? And I doubt that this has anything to do with it, but why do you want to set your locale by passing it as an option to your kernel (as opposed to setting it in rc.conf)
Here: http://pastebin.archlinux.org/15328 I just tried that locale thing, it doesn't relate here.
Well actually, when exactly does it happen? I'm not sure, but you mean you start your computer, choose "Arch Linux" in your boot manager, then the screen "flips", you see the Archlogo and the Kernelstuff scroll by, then it hangs for those 20 seconds and then it continues normally printing "Arch Linux (Don't panic)" on your screen and it starts processing rc.conf (loading modules, setting hostname, and so on and so forth), right? That's how it happens or did I mistake you?
Just like that (thought i don't know what you mean by Archlogo).
If so, then it happens even before rc.sysinit is called. And the only things that are happen prior to that are: your kernel is getting extracted into the memory and it initializes itself (gathers information about your hardware from your mainboards BIOS, defines it's internal structures) and then the kernel calles init.
So unless someone tampered with your /etc/inittab (what does 'grep sysinit /etc/inittab' say?) it can actually only be something with the kernel, or init.
>: grep sysinit /etc/inittab
rc::sysinit:/etc/rc.sysinit
Has it always been like that or did this start recently?
Yes, it has always been like that in this installation. In previous installation which I installed in May there wasn't problem like this.
edit: Since it apparently can't be due to something set in your rc.conf, I guess I don't need to see it, but your /boot/grub/menu.1st respectively your lilo-config could be interesting to see. Same goes for /var/log/kernel.log and /var/log/messages.log
menu.lst http://pastebin.archlinux.org/15330
/var/log/kernel.log's last 677 lines.. http://pastebin.archlinux.org/15331
/var/log/message's last 632 lines http://pastebin.archlinux.org/15332
That was tedious
Offline
Hmmmm, unfortunately I can't see anything weird in those logs, everything else looks fine to me too... I dunno, I'm kind of running out of ideas now too.
Offline
I have a small idea.
Remember the kernel panic at init=/bin/bash ?
Did it take long to panic too, or did it do it right away? Was there a 20 second wait?
If it took a while, we are dealing with a kernel problem. Not much to be done, unless you feel like compiling your own kernel.
Otherwise it is a userspace problem, and we could try to figure out where it lies by putting printf/echo into init scripts.
Karol Swietlicki
Offline
Yeah, kernel panic came after waiting 20 seconds. Isn't it harder to compile my own kernel on arch than debian or something?
Offline
Does it matter becouse i've these hooks on my mkinitcpio.conf
HOOKS="base udev autodetect pata scsi sata usb usbinput keymap filesystems"
E: I reinstalled..
Last edited by igglybuff (2007-09-30 18:09:48)
Offline
Pages: 1