HI. I'm using Gentoo and my kernel is wget from the kernel.org. When I try to use the kernel (2.6.34-rc2).I found that I can't shutdown my Gentoo,but I can reboot it.The error imformation is "/etc/ini.d/shutdown.sh : line 9". and I try to use the 2.6.33.1,with the same ".config",and it work well. so,I think this is a bug. CPU:AMD althlon 64x2 5000+ P.S. about a weak ago ,I using 2.6.34-git6.It's alsa working very well.... P.S. I'm sorry my english is poor...
(In reply to comment #0) > HI. > > I'm using Gentoo and my kernel is wget from the kernel.org. > > When I try to use the kernel (2.6.34-rc2).I found that I can't shutdown my > Gentoo, what command do you use? >but I can reboot it.The error imformation is "/etc/ini.d/shutdown.sh : > line 9". > please attach the /etc/init.d/shutdown.sh file. so the system is still working after you issue the shutdown commands, right?
e.g. whe I type the "halt" command in the terminal,I receive an error information and I can't do anything.My computer crashed！！！！ The last error information is "/etc/init.d/shutdown.sh line 9: 7532 killed /sbin/halt "${opts}" but when I use the 2.6.33.1 kernel,with the same ".config" file,this issue is solved.
please attach the /etc/init.d/shutdown.sh file.
# Copyright 1999-2006 Gentoo Foundation # Distributed under the terms of the GNU General Public License v2 opts="-d" [ "${INIT_HALT}" != "HALT" ] && opts="${opts}p" [ "${RC_DOWN_INTERFACE}" = "yes" ] && opts="${opts}i" [ "${RC_DOWN_HARDDISK}" = "yes" ] && opts="${opts}h" /sbin/halt "${opts}" # hmm, if the above failed, that's kind of odd ... # so let's force a halt /sbin/halt -f =======================
> /sbin/halt "${opts}" > what if you comment this line?
(In reply to comment #6) > > /sbin/halt "${opts}" > > > what if you comment this line? It doesn't work. http://picasaweb.google.com/blackdream1890/Kernel2634Rc2#5452098710986501506 U can see the pictures.thanks.
as this is a 2.6.34-rc1 regression, it would be great if you can use git bisect to find out which commit introduces this bug.
BTW, this doesn't seem like an ACPI problem.
It was solved with the "2.6.34-rc2-git2".... Everything is OK now. but I don't know why all the same.
(In reply to comment #10) > It was solved with the "2.6.34-rc2-git2".... > > Everything is OK now. > good news, bug closed. > but I don't know why all the same. I have no idea, neither. :(
(In reply to comment #11) > (In reply to comment #10) > > It was solved with the "2.6.34-rc2-git2".... > > > > Everything is OK now. > > > good news, bug closed. > > > but I don't know why all the same. > > I have no idea, neither. :( Anyway,thank U so much.Good luck!