Er..As I explained above, this problem just exists with my customized kernel and not with the archlinux official kernel. So I asked 'what kernel options are required'. I didn't mean that it is a bug in systemd.
-- Dark Raven -Waiting for chaos to begin On Wed, Apr 27, 2011 at 11:16 PM, Lennart Poettering <[email protected] > wrote: > On Wed, 27.04.11 22:46, [email protected] ([email protected]) > wrote: > > > I recently started to use systemd. But I experienced a very annoying > > problem. When I try 'systemctl poweroff', everything goes fine first, > > systemd says 'Detaching DM Device' and exits, the kernel stopped my > > hard disk and disabled non-boot cpus, but then my computer just hang > > there. I wait for about 20-30 second, then kernel compliant that > > something tries to read the stopped disk. > > > > (kernel message: > > 'ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 frozen > > ata1.00: cmd 60/00:00:ab:f9:21/00:00:00:0b:00:00/40 tag 0 .....') > > Please report this to the kernel maintainers of your distribution or ask > kernel folks for help on this. This is almost definitely not a bug in > systemd, and needs to be fixed in your kernel. > > Lennart > > -- > Lennart Poettering - Red Hat, Inc. >
_______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
