On 2011-04-14 20:36, u20380 wrote:
> Hi all,
>
> I have recently installed Suse 1.4_64 on my system. During the boot
> process I experience two delays of about 30 seconds, every time I boot
> up.
>
> Any suggestions?
splash=verbose
remove “quiet”.
Find out where it waits.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
The first wait occurs at 5 seconds into the boot process, with an error message “ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen”
The second wait at 38 seconds, with a message “device-mapper: ioctl: 4.18.0-ioctl (2010-06-29) initialised: dm-devel@redhat.com”
Then I opened an xterm (konsole also works in KDE) and restarted from the LXDE menu with that separate terminal open.
In the grub option line I entered:
init=/sbin/bootchartd
Then after the reboot was finished I again opened a terminal (or konsole) and that stopped the bootchart data collection process. I then waited a bit for the bootchart.png file to be created.
That produced the charts noted above. … I stumbled a bit on this and had to get help from some of the SuSE-GmbH team (via a bug report which illustrated my ignorance). The first chart shows apparmor was consuming ~26% of CPU during boot, so given it is not essential, I was advised it was a possible candidate to disable. It can be disabled with YaST > System > System Services (run level) > expert mode > boot.apparmor … etc … *.
On 2011-04-15 14:06, u20380 wrote:
>
> The first wait occurs at 5 seconds into the boot process, with an error
> message “ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
> frozen”
> The second wait at 38 seconds, with a message “device-mapper: ioctl:
> 4.18.0-ioctl (2010-06-29) initialised: dm-devel@redhat.com”
Either a hardware problem, or a bug. Try another opensuse version: if it
doesn’t pause, report in bugzilla.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
On 2011-04-17 22:36, u20380 wrote:
>
> Carlos,
>
> I ran the 11.2 LiveCD and it ran like a breeze, no timeouts.
> It does seem to be a bug indeed.
I don’t remember if your system was fully updated; if it isn’t, then do.
Otherwise, do a report in bugzilla. Attacch the boot log (with quiet
removed) and perhaps the output of dmesg. And wait…
I’m not sure if suggesting you should run an older version.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)