FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian User

 
 
LinkBack Thread Tools
 
Old 06-19-2011, 07:13 AM
yuanwei xu
 
Default Debian wheezy:machine auto booted after poweroff

Hi,
After upgrade from Squeeze to Wheezy, my notebook always auto booted
after I shutdowned it using #poweroff in gnome terminal.
Sometimes, it auto booted in 1 minutes, sometimes in 3 minutes after poweroff.
I have to use #poweroff to shutdown it once more, and it wouldn't
auto boot anymore.
I tried to go back to kernel 2.6.32-5-686, it didn't have such problem.
and I compiled kernel 2.6.39.1 using oldconfig of 2.6.38-2-686, the
auto boot still happened.
It made me crazy, any advice is appreciated.

Below is one section of syslog when the auto boot happened,nothing
seemed unusual:

Jun 14 23:47:56 Lemmon shutdown[4506]: shutting down for system halt
Jun 14 23:47:57 Lemmon init: Switching to runlevel: 0
Jun 14 23:47:57 Lemmon x-session-manager[2328]: WARNING: Detected that
screensaver has left the bus
Jun 14 23:48:14 Lemmon exiting on signal 15
Jun 14 23:50:53 Lemmon syslogd 1.5.0#6.1: restart.
Jun 14 23:50:54 Lemmon acpid: starting up with netlink and the input layer
Jun 14 23:50:54 Lemmon acpid: 42 rules loaded
Jun 14 23:50:54 Lemmon acpid: waiting for events: event logging is off
Jun 14 23:50:54 Lemmon anacron[1547]: Anacron 2.3 started on 2011-06-14
Jun 14 23:50:54 Lemmon anacron[1547]: Normal exit (0 jobs run)
Jun 14 23:50:55 Lemmon avahi-daemon[1573]: Found user 'avahi' (UID
110) and group 'avahi' (GID 114).
Jun 14 23:50:55 Lemmon avahi-daemon[1573]: Successfully dropped root privileges.
Jun 14 23:50:55 Lemmon avahi-daemon[1573]: avahi-daemon 0.6.30 starting up.
Jun 14 23:50:55 Lemmon avahi-daemon[1573]: Successfully called chroot().
Jun 14 23:50:55 Lemmon avahi-daemon[1573]: Successfully dropped
remaining capabilities.
Jun 14 23:50:55 Lemmon avahi-daemon[1573]: Loading service file
/services/udisks.service.
Jun 14 23:50:55 Lemmon avahi-daemon[1573]: Network interface
enumeration completed.
Jun 14 23:50:55 Lemmon avahi-daemon[1573]: Registering HINFO record
with values 'I686'/'LINUX'.
Jun 14 23:50:55 Lemmon avahi-daemon[1573]: Server startup complete.
Host name is Lemmon.local. Local service cookie is 3966028872.
Jun 14 23:50:55 Lemmon avahi-daemon[1573]: Service "Lemmon"
(/services/udisks.service) successfully established.
Jun 14 23:50:55 Lemmon /usr/sbin/cron[1600]: (CRON) INFO (pidfile fd = 3)
Jun 14 23:50:55 Lemmon /usr/sbin/cron[1601]: (CRON) STARTUP (fork ok)
Jun 14 23:50:55 Lemmon /usr/sbin/cron[1601]: (CRON) INFO (Running @reboot jobs)
Jun 14 23:50:57 Lemmon kernel: Inspecting /boot/System.map-2.6.38-2-686
Jun 14 23:50:57 Lemmon kernel: Cannot find map file.
Jun 14 23:50:57 Lemmon kernel: Loaded 25540 symbols from 152 modules.
Jun 14 23:50:57 Lemmon kernel: [ * *0.000000] Initializing cgroup subsys cpuset
----

This problem occured several times, and blow is the result of $grep
"exiting on signal" -A 1 of all syslog files
(the line marked * is the auto boot happened)
*Jun 14 23:48:14 Lemmon exiting on signal 15 *// last log of poweroff
*Jun 14 23:50:53 Lemmon syslogd 1.5.0#6.1: restart. //first log of boot
--
Jun 15 00:14:42 Lemmon exiting on signal 15
Jun 15 20:38:21 Lemmon syslogd 1.5.0#6.1: restart.
--
Jun 15 21:00:10 Lemmon exiting on signal 15
Jun 15 22:43:01 Lemmon syslogd 1.5.0#6.1: restart.
--
*Jun 13 23:47:41 Lemmon exiting on signal 15
*Jun 13 23:48:41 Lemmon syslogd 1.5.0#6.1: restart.
--
Jun 14 00:02:32 Lemmon exiting on signal 15
Jun 14 21:29:10 Lemmon syslogd 1.5.0#6.1: restart.
--
*Jun 13 00:25:14 Lemmon exiting on signal 15
*Jun 13 00:28:24 Lemmon syslogd 1.5.0#6.1: restart.
--
Jun 13 00:28:45 Lemmon exiting on signal 15
Jun 13 20:51:24 Lemmon syslogd 1.5.0#6.1: restart.
--
*Jun 10 22:30:26 Lemmon exiting on signal 15
*Jun 10 22:31:26 Lemmon syslogd 1.5.0#6.1: restart.
--
Jun 11 00:19:48 Lemmon exiting on signal 15
Jun 12 15:50:09 Lemmon syslogd 1.5.0#6.1: restart.
--
Jun *9 22:37:47 Lemmon exiting on signal 15
Jun 10 20:38:53 Lemmon syslogd 1.5.0#6.1: restart.
--
*Jun *8 23:43:13 Lemmon exiting on signal 15
*Jun *8 23:44:17 Lemmon syslogd 1.5.0#6.1: restart.
--
Jun *8 23:45:55 Lemmon exiting on signal 15
Jun *9 21:08:10 Lemmon syslogd 1.5.0#6.1: restart.
--
Jun *7 23:36:44 Lemmon exiting on signal 15
Jun *8 21:26:27 Lemmon syslogd 1.5.0#6.1: restart.
--
Jun *6 16:21:59 Lemmon exiting on signal 15
Jun *6 18:00:22 Lemmon syslogd 1.5.0#6.1: restart.
--
*Jun *6 21:37:16 Lemmon exiting on signal 15
*Jun *6 21:38:35 Lemmon syslogd 1.5.0#6.1: restart.
--
*Jun *6 21:38:54 Lemmon exiting on signal 15
*Jun *7 21:42:29 Lemmon syslogd 1.5.0#6.1: restart.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: BANLkTikkCg1kZ2Np45MFubL1b5jgTG3dMQ@mail.gmail.com ">http://lists.debian.org/BANLkTikkCg1kZ2Np45MFubL1b5jgTG3dMQ@mail.gmail.com
 
Old 06-22-2011, 02:43 PM
yuanwei xu
 
Default Debian wheezy:machine auto booted after poweroff

2011/6/19 Camaleón <noelamac@gmail.com>:
> On Sun, 19 Jun 2011 15:13:37 +0800, yuanwei xu wrote:
>
>> After upgrade from Squeeze to Wheezy, my notebook always auto booted
>> after I shutdowned it using #poweroff in gnome terminal. Sometimes, it
>> auto booted in 1 minutes, sometimes in 3 minutes after poweroff. I have
>> to *use #poweroff to shutdown it once more, and it wouldn't auto boot
>> anymore.
>> I tried to go back to kernel 2.6.32-5-686, it didn't have such problem.
>
> So it could be a kernel related issue... There are others reporting a
> similar problem:
>
> Computer is not turned off at shutdown
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/762203
>
> unexpected reboot after rebooting or shutting down from Ubuntu 11.04
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/791089
>
>> and I compiled kernel 2.6.39.1 using oldconfig of 2.6.38-2-686, the auto
>> boot still happened.
>> It made me crazy, any advice is appreciated.
>
> (...)
>
> Make a quick test: go to "init 1" and try to shutdown from there
> (shutdown -h now).

Yes, it works, thanks for your reply. Hope there will be a final solution soon.
>
> Greetings,
>
> --
> Camaleón
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> Archive: http://lists.debian.org/pan.2011.06.19.14.22.18@gmail.com
>
>


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: BANLkTimL_gv0yXVafWbT39iJQmEDZAyH=w@mail.gmail.com ">http://lists.debian.org/BANLkTimL_gv0yXVafWbT39iJQmEDZAyH=w@mail.gmail.com
 
Old 06-22-2011, 02:43 PM
yuanwei xu
 
Default Debian wheezy:machine auto booted after poweroff

2011/6/19 Camaleón <noelamac@gmail.com>:
> On Sun, 19 Jun 2011 15:13:37 +0800, yuanwei xu wrote:
>
>> After upgrade from Squeeze to Wheezy, my notebook always auto booted
>> after I shutdowned it using #poweroff in gnome terminal. Sometimes, it
>> auto booted in 1 minutes, sometimes in 3 minutes after poweroff. I have
>> to *use #poweroff to shutdown it once more, and it wouldn't auto boot
>> anymore.
>> I tried to go back to kernel 2.6.32-5-686, it didn't have such problem.
>
> So it could be a kernel related issue... There are others reporting a
> similar problem:
>
> Computer is not turned off at shutdown
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/762203
>
> unexpected reboot after rebooting or shutting down from Ubuntu 11.04
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/791089
>
>> and I compiled kernel 2.6.39.1 using oldconfig of 2.6.38-2-686, the auto
>> boot still happened.
>> It made me crazy, any advice is appreciated.
>
> (...)
>
> Make a quick test: go to "init 1" and try to shutdown from there
> (shutdown -h now).

Yes, it works, thanks for your reply. Hope there will be a final solution soon.
>
> Greetings,
>
> --
> Camaleón
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> Archive: http://lists.debian.org/pan.2011.06.19.14.22.18@gmail.com
>
>


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: BANLkTimL_gv0yXVafWbT39iJQmEDZAyH=w@mail.gmail.com ">http://lists.debian.org/BANLkTimL_gv0yXVafWbT39iJQmEDZAyH=w@mail.gmail.com
 
Old 06-23-2011, 02:07 PM
yuanwei xu
 
Default Debian wheezy:machine auto booted after poweroff

2011/6/22 Camaleón <noelamac@gmail.com>:
> On Wed, 22 Jun 2011 22:43:06 +0800, yuanwei xu wrote:
>
>> 2011/6/19 Camaleón <noelamac@gmail.com>:
>>> On Sun, 19 Jun 2011 15:13:37 +0800, yuanwei xu wrote:
>>>
>>>> After upgrade from Squeeze to Wheezy, my notebook always auto booted
>>>> after I shutdowned it using #poweroff in gnome terminal. Sometimes, it
>>>> auto booted in 1 minutes, sometimes in 3 minutes after poweroff. I
>>>> have to *use #poweroff to shutdown it once more, and it wouldn't auto
>>>> boot anymore.
>>>> I tried to go back to kernel 2.6.32-5-686, it didn't have such
>>>> problem.
>>>
>>> So it could be a kernel related issue... There are others reporting a
>>> similar problem:
>>>
>>> Computer is not turned off at shutdown
>>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/762203
>>>
>>> unexpected reboot after rebooting or shutting down from Ubuntu 11.04
>>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/791089
>>>
>>>> and I compiled kernel 2.6.39.1 using oldconfig of 2.6.38-2-686, the
>>>> auto boot still happened.
>>>> It made me crazy, any advice is appreciated.
>>>
>>> (...)
>>>
>>> Make a quick test: go to "init 1" and try to shutdown from there
>>> (shutdown -h now).
>>
>> Yes, it works, thanks for your reply. Hope there will be a final
>> solution soon.
>
> It worked?? Hum... I didn't expect it did.

At least, it had not auto booted in one night after "#init 1" and "#poweroff".
>
> This could be something to investigate further. At a first glance I can
> think in acpi being the culprit... is the "acpid" service loaded in
> single-user mode?

In /etc/rc2.d, $ls | grep acpi, there are files:

S18acpi-fakekey
S19acpid
S19acpi-support
In /etc/rc1.d,$ls | grep acpi, there is file:
K01acpi-support

>
> Greetings,
>
> --
> Camaleón
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> Archive: http://lists.debian.org/pan.2011.06.22.15.00.35@gmail.com
>
>


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: BANLkTinG6GjCY-T4Mq4zD31gXBXdOPWdHg@mail.gmail.com">http://lists.debian.org/BANLkTinG6GjCY-T4Mq4zD31gXBXdOPWdHg@mail.gmail.com
 
Old 06-23-2011, 02:07 PM
yuanwei xu
 
Default Debian wheezy:machine auto booted after poweroff

2011/6/22 Camaleón <noelamac@gmail.com>:
> On Wed, 22 Jun 2011 22:43:06 +0800, yuanwei xu wrote:
>
>> 2011/6/19 Camaleón <noelamac@gmail.com>:
>>> On Sun, 19 Jun 2011 15:13:37 +0800, yuanwei xu wrote:
>>>
>>>> After upgrade from Squeeze to Wheezy, my notebook always auto booted
>>>> after I shutdowned it using #poweroff in gnome terminal. Sometimes, it
>>>> auto booted in 1 minutes, sometimes in 3 minutes after poweroff. I
>>>> have to *use #poweroff to shutdown it once more, and it wouldn't auto
>>>> boot anymore.
>>>> I tried to go back to kernel 2.6.32-5-686, it didn't have such
>>>> problem.
>>>
>>> So it could be a kernel related issue... There are others reporting a
>>> similar problem:
>>>
>>> Computer is not turned off at shutdown
>>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/762203
>>>
>>> unexpected reboot after rebooting or shutting down from Ubuntu 11.04
>>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/791089
>>>
>>>> and I compiled kernel 2.6.39.1 using oldconfig of 2.6.38-2-686, the
>>>> auto boot still happened.
>>>> It made me crazy, any advice is appreciated.
>>>
>>> (...)
>>>
>>> Make a quick test: go to "init 1" and try to shutdown from there
>>> (shutdown -h now).
>>
>> Yes, it works, thanks for your reply. Hope there will be a final
>> solution soon.
>
> It worked?? Hum... I didn't expect it did.

At least, it had not auto booted in one night after "#init 1" and "#poweroff".
>
> This could be something to investigate further. At a first glance I can
> think in acpi being the culprit... is the "acpid" service loaded in
> single-user mode?

In /etc/rc2.d, $ls | grep acpi, there are files:

S18acpi-fakekey
S19acpid
S19acpi-support
In /etc/rc1.d,$ls | grep acpi, there is file:
K01acpi-support

>
> Greetings,
>
> --
> Camaleón
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> Archive: http://lists.debian.org/pan.2011.06.22.15.00.35@gmail.com
>
>


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: BANLkTinG6GjCY-T4Mq4zD31gXBXdOPWdHg@mail.gmail.com">http://lists.debian.org/BANLkTinG6GjCY-T4Mq4zD31gXBXdOPWdHg@mail.gmail.com
 
Old 06-23-2011, 03:12 PM
yuanwei xu
 
Default Debian wheezy:machine auto booted after poweroff

2011/6/23 Camaleón <noelamac@gmail.com>:
> On Thu, 23 Jun 2011 22:07:29 +0800, yuanwei xu wrote:
>
>> 2011/6/22 Camaleón <noelamac@gmail.com>:
>
>>>> Yes, it works, thanks for your reply. Hope there will be a final
>>>> solution soon.
>>>
>>> It worked?? Hum... I didn't expect it did.
>>
>> At least, it had not auto booted in one night after "#init 1" and
>> "#poweroff".
>
> Good.
>
>>> This could be something to investigate further. At a first glance I can
>>> think in acpi being the culprit... is the "acpid" service loaded in
>>> single-user mode?
>>
>> In /etc/rc2.d, $ls | grep acpi, there are files:
>>
>> * * * * S18acpi-fakekey
>> * * * * S19acpid
>> * * * * S19acpi-support
>> In /etc/rc1.d,$ls | grep acpi, there is file:
>> * * * * K01acpi-support
Oh, the "acpid" service also started in runlevel 1, it existed in the
process list,I thought it shouldn't started because there is no
Sxxacpid file.

>
> Hum... so at init 1 there is no "acpid" service running on background.
> This can be relevant for your issue when powering off the machine... How
> about stopping "acpid" service on a normal session and then try to
> shutdown the machine? Just to test with other variant...
>
> Greetings,
>
> --
> Camaleón
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> Archive: http://lists.debian.org/pan.2011.06.23.15.07.06@gmail.com
>
>


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: BANLkTikp=kfwi6neV_97XQHYtVkKroJNPQ@mail.gmail.com ">http://lists.debian.org/BANLkTikp=kfwi6neV_97XQHYtVkKroJNPQ@mail.gmail.com
 
Old 06-23-2011, 04:02 PM
yuanwei xu
 
Default Debian wheezy:machine auto booted after poweroff

2011/6/23 yuanwei xu <xuyuanwei@gmail.com>:
> 2011/6/23 Camaleón <noelamac@gmail.com>:
>> On Thu, 23 Jun 2011 22:07:29 +0800, yuanwei xu wrote:
>>
>>> 2011/6/22 Camaleón <noelamac@gmail.com>:
>>
>>>>> Yes, it works, thanks for your reply. Hope there will be a final
>>>>> solution soon.
>>>>
>>>> It worked?? Hum... I didn't expect it did.
>>>
>>> At least, it had not auto booted in one night after "#init 1" and
>>> "#poweroff".
>>
>> Good.
>>
>>>> This could be something to investigate further. At a first glance I can
>>>> think in acpi being the culprit... is the "acpid" service loaded in
>>>> single-user mode?
>>>
>>> In /etc/rc2.d, $ls | grep acpi, there are files:
>>>
>>> * * * * S18acpi-fakekey
>>> * * * * S19acpid
>>> * * * * S19acpi-support
>>> In /etc/rc1.d,$ls | grep acpi, there is file:
>>> * * * * K01acpi-support
> Oh, the "acpid" service also started in runlevel 1, it existed in the
> process list,I thought it shouldn't started because there is no
> Sxxacpid file.

Sorry, I am a little confused. I run "#init 1" under gnome-terminal,
then the system quit gnome to console, the screen shows:
INIT: Goging single user
INIT: Sending processes the TERM signal
Give root password for maintenance
(or type Control-D to continue):
I press Control-D, then some Stopping and some Starting(include
acpi_fakekey daemon and ACPI service).
Then I login as root,run #runlevel, it outputs "N 2". here why is not
runlevel 1?

So where i said i found the acpid process in runlevel 1, it in fact
was in runlevel 2.

I edit the /etc/inittab to change default runlevel to be 1,and reboot,
run #ps -e | grep acpi, there were:
kacpid
kacpi_notify
kacpi_hotplug
but no acpid and acpi_fakekeyd

>
>>
>> Hum... so at init 1 there is no "acpid" service running on background.
>> This can be relevant for your issue when powering off the machine... How
>> about stopping "acpid" service on a normal session and then try to
>> shutdown the machine? Just to test with other variant...

I will try it.Thanks.

>>
>> Greetings,
>>
>> --
>> Camaleón
>>
>>
>> --
>> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
>> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>> Archive: http://lists.debian.org/pan.2011.06.23.15.07.06@gmail.com
>>
>>
>


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: BANLkTim=MxuLm0SnUJh=rPd+dGVLE82y_g@mail.gmail.com ">http://lists.debian.org/BANLkTim=MxuLm0SnUJh=rPd+dGVLE82y_g@mail.gmail.com
 
Old 06-24-2011, 09:36 AM
Darac Marjal
 
Default Debian wheezy:machine auto booted after poweroff

On Fri, Jun 24, 2011 at 12:02:54AM +0800, yuanwei xu wrote:
> 2011/6/23 yuanwei xu <xuyuanwei@gmail.com>:
> > 2011/6/23 Camaleón <noelamac@gmail.com>:
> >> On Thu, 23 Jun 2011 22:07:29 +0800, yuanwei xu wrote:
> >>
> >>>> This could be something to investigate further. At a first glance I can
> >>>> think in acpi being the culprit... is the "acpid" service loaded in
> >>>> single-user mode?
> >>>
> >>> In /etc/rc2.d, $ls | grep acpi, there are files:
> >>>
> >>> * * * * S18acpi-fakekey
> >>> * * * * S19acpid
> >>> * * * * S19acpi-support
> >>> In /etc/rc1.d,$ls | grep acpi, there is file:
> >>> * * * * K01acpi-support
> > Oh, the "acpid" service also started in runlevel 1, it existed in the
> > process list,I thought it shouldn't started because there is no
> > Sxxacpid file.
>
> Sorry, I am a little confused. I run "#init 1" under gnome-terminal,
> then the system quit gnome to console, the screen shows:
> INIT: Goging single user
> INIT: Sending processes the TERM signal
> Give root password for maintenance
> (or type Control-D to continue):
> I press Control-D, then some Stopping and some Starting(include
> acpi_fakekey daemon and ACPI service).
> Then I login as root,run #runlevel, it outputs "N 2". here why is not
> runlevel 1?

Runlevel 1 is single-user mode. That single user is root. The "Give root
password for maintenance" prompt is your indication that you are at
runlevel 1. You should log in as root at that point and proceed as
above. When you press Ctrl+D, you are leaving runlevel 2 and going back
to multi-user mode which is why you're able to log in as any user.

--
Paul Saunders
 
Old 06-26-2011, 08:37 AM
xuyuanwei
 
Default Debian wheezy:machine auto booted after poweroff

在 2011-06-24五的 00:02 +0800,yuanwei xu写道:
> 2011/6/23 yuanwei xu <xuyuanwei@gmail.com>:
> > 2011/6/23 Camaleón <noelamac@gmail.com>:
> >> On Thu, 23 Jun 2011 22:07:29 +0800, yuanwei xu wrote:
> >>
> >>> 2011/6/22 Camaleón <noelamac@gmail.com>:
> >>
> >>>>> Yes, it works, thanks for your reply. Hope there will be a final
> >>>>> solution soon.
> >>>>
> >>>> It worked?? Hum... I didn't expect it did.
> >>>
> >>> At least, it had not auto booted in one night after "#init 1" and
> >>> "#poweroff".
> >>
> >> Good.
> >>
> >>>> This could be something to investigate further. At a first glance I can
> >>>> think in acpi being the culprit... is the "acpid" service loaded in
> >>>> single-user mode?
> >>>
> >>> In /etc/rc2.d, $ls | grep acpi, there are files:
> >>>
> >>> S18acpi-fakekey
> >>> S19acpid
> >>> S19acpi-support
> >>> In /etc/rc1.d,$ls | grep acpi, there is file:
> >>> K01acpi-support
> > Oh, the "acpid" service also started in runlevel 1, it existed in the
> > process list,I thought it shouldn't started because there is no
> > Sxxacpid file.
>

> >
> >>
> >> Hum... so at init 1 there is no "acpid" service running on background.
> >> This can be relevant for your issue when powering off the machine... How
> >> about stopping "acpid" service on a normal session and then try to
> >> shutdown the machine? Just to test with other variant...


In /etc/rc2.d, i disabled "acpi-fakekey","acpid" and "acpi-support",the
auto start problem still happened,both 2.6.38-2-686 and 2.6.39-2-686-pae
kernel.

It seems the problem has something to do with the uptime, but more
observation is needed.
>
> >>
> >> Greetings,
> >>
> >> --
> >> Camaleón
> >>
> >>
> >> --
> >> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> >> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> >> Archive: http://lists.debian.org/pan.2011.06.23.15.07.06@gmail.com
> >>
> >>
> >



--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 1309077439.2636.16.camel@localhost">http://lists.debian.org/1309077439.2636.16.camel@localhost
 

Thread Tools




All times are GMT. The time now is 05:15 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org