Is a fix going to get backported to Feisty or do we just have to put up
with much slower boot times ?
--
hal takes about 60 seconds to start up
https://bugs.launchpad.net/bugs/92647
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for hal
Hi Chris,
Chris Samuel [2007-04-17 11:44 -]:
Is a fix going to get backported to Feisty or do we just have to put up
with much slower boot times ?
I am afraid not, hal 0.5.9 has major architectural changes which are
inappropriate for feisty-updates. *However*, if we find some people
who
@Martin: if it helps any, I can test it.
--
hal takes about 60 seconds to start up
https://bugs.launchpad.net/bugs/92647
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for hal in ubuntu.
--
desktop-bugs mailing list
Jason, can you please file a separate bug against linux-source-2.6.20,
please, since it is a completely different problem?
Apparently fixed upstream, so this will get fixed in gutsy when we'll
move to hal 0.5.9.
** Changed in: hal (Ubuntu)
Status: Confirmed = In Progress
--
hal takes
I think Jason is looking at a different problem, the slowdown I see is
purely down to HAL as I'm running on a desktop with no battery or
thermal ACPI modules loaded and the HAL message is quite explicit that
it is HAL itself waiting for 1 second per logical volume and the
upstream bug report shows
yes, I've found that my problem is actually the kernel, 2.6.20 doesn't
play well with ACPI on quite a few systems, it shows it's head when I
modprobe battery,ac and thermal with longer than usual pauses, and then
really shows up with applications like kpowermanager, gkrellm, and hal.
--
hal
This seems to be a kernel problem, it takes a long time just to modprobe
battery and thermal as well.
--
hal takes about 60 seconds to start up
https://bugs.launchpad.net/bugs/92647
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for hal
I see the same thing here with Feisty Kubuntu (up to date), each of my
LVM's results in a 1 second wait:
Waiting 1000ms to wait for device mapper to be ready
So my boot time here has almost doubled from just over 1m to 1m 52s (+/-
3s) - a bit disappointing really as I upgrade thinking I'd see a
Same Problem here, waiting 1 sec for each device manager (evms) device.
** Attachment added: hal.log from feisty: waiting for multiple evms partitions
http://librarian.launchpad.net/7098430/hal.log
--
hal takes about 60 seconds to start up
https://launchpad.net/bugs/92647
--
desktop-bugs
ACPI?
I noticed starting gkrellm today that it took an oddly long time to
startup so I straced it, it was hanging on batt and ac acpi for a long
time.
Then I started hal with --verbose=yes --use-syslog and restarted dbus,
hal also hung for a long time on those same acpi parts.
--
hal takes
Startup w/o acpi modules for batt and ac:
[EMAIL PROTECTED]:~# time /etc/init.d/dbus start
* Starting system message bus dbus
[ OK ]
* Starting Hardware abstraction layer hald
Bootchart from Kubuntu Feisty with current updates showing a boot time
of 1m 57s, over 50 seconds longer than Edgy.
** Attachment added: Feisty bootchart PNG - 20070325
http://librarian.launchpad.net/6930775/feisty-20070325-2.png
--
hal takes about 60 seconds to start up
Bootchart from Kubuntu Edgy immediately prior to upgrade to Feisty
showing a boot time of 1m 4s.
** Attachment added: Edgy bootchart PNG - 20070324
http://librarian.launchpad.net/6930772/edgy-20070324-1.png
--
hal takes about 60 seconds to start up
https://launchpad.net/bugs/92647
--
** Changed in: hal (upstream)
Status: Needs Info = Fix Released
--
hal takes about 60 seconds to start up
https://launchpad.net/bugs/92647
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
** Changed in: hal (upstream)
Status: Confirmed = Needs Info
--
hal takes about 60 seconds to start up
https://launchpad.net/bugs/92647
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
** Changed in: hal (upstream)
Status: Unknown = Confirmed
--
hal takes about 60 seconds to start up
https://launchpad.net/bugs/92647
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
** Changed in: hal (Ubuntu)
Importance: Undecided = Medium
Status: Needs Info = Confirmed
** Bug watch added: Freedesktop Bugzilla #10364
https://bugs.freedesktop.org/show_bug.cgi?id=10364
** Also affects: hal (upstream) via
https://bugs.freedesktop.org/show_bug.cgi?id=10364
Restarted hald in verbose mode. first timestamp is 09:31:43.595, last
timestamp is 09:32:32.162, so about 50 seconds.
There is a forced 1000 ms wait at blockdev (see timestamps 09:32:10.650
onward) for each device found; this piece of init takes about 20 seconds
to complete.
Have not yet looked
Can you please get a hal debug output, as described on the second half
of https://wiki.ubuntu.com/DebuggingRemovableDevices, watch the log
output, and see where it hangs for so long? Since it usually starts in
some-three seconds, I guess it just hangs in a single operation instead
of being
Similar here on a laptop with AMD64, but it is most visible on shutdown,
when I lose usplash when shutting down dbus friends. Takes about a
minute to shutdown dbus.
On startup... I will check next boot.
--
hal takes about 60 seconds to start up
https://launchpad.net/bugs/92647
--
startup hal takes more than 30 seconds. On shutdown, for my surprise, it
was seamless, with absolutely no waits. This is today, yesterday it was
not behaving like this.
--
hal takes about 60 seconds to start up
https://launchpad.net/bugs/92647
--
desktop-bugs mailing list
21 matches
Mail list logo
