<div>Er..As I explained above, this problem just exists with my customized kernel and</div><div> not with the archlinux official kernel. So I asked 'what kernel options are required'.</div><div>I didn't mean that it is a bug in systemd.</div> <div><br></div>--<br><div>Dark Raven</div><div>-Waiting for chaos to begin</div><br> <br><br><div class="gmail_quote">On Wed, Apr 27, 2011 at 11:16 PM, Lennart Poettering <span dir="ltr"><<a href="mailto:lennart@poettering.net">lennart@poettering.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> <div class="im">On Wed, 27.04.11 22:46, <a href="mailto:drdarkraven@gmail.com">drdarkraven@gmail.com</a> (<a href="mailto:drdarkraven@gmail.com">drdarkraven@gmail.com</a>) wrote:<br> <br> > I recently started to use systemd. But I experienced a very annoying<br> > problem. When I try 'systemctl poweroff', everything goes fine first,<br> > systemd says 'Detaching DM Device' and exits, the kernel stopped my<br> > hard disk and disabled non-boot cpus, but then my computer just hang<br> > there. I wait for about 20-30 second, then kernel compliant that<br> > something tries to read the stopped disk.<br> ><br> > (kernel message:<br> > 'ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 frozen<br> > ata1.00: cmd 60/00:00:ab:f9:21/00:00:00:0b:00:00/40 tag 0 .....')<br> <br> </div>Please report this to the kernel maintainers of your distribution or ask<br> kernel folks for help on this. This is almost definitely not a bug in<br> systemd, and needs to be fixed in your kernel.<br> <br> Lennart<br> <font color="#888888"><br> --<br> Lennart Poettering - Red Hat, Inc.<br> </font></blockquote></div><br>