Re: FC5, And FC6 won't shutdown completely

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 11 Jan 2007 19:08:48 +0100
Nigel Henry <cave.dnb@xxxxxxxxxx> wrote:

> On Thursday 11 January 2007 14:53, pds wrote:
> >
> > My experience is that SuSe doesn't have a problem shutting down.
> > At least FC5 & FC6 have a problem shutting down once I log in KDE or
> > GNOME.  If I don't log in or only use a console then power off
> > works. I had seen somewhere on the list and a bug that dbus is a
> > culprit.
> >
> > -pete
> 
> Hi Pete. Tried that after your post. First booted up as far as GDM,
> then shutdown, but machine still refused to shutdown completely. Next
> booted up to init3, logged in as user, then used "halt" to shut down,
> but still no joy.

halt should only halt the machine, try it with 'poweroff'.  I expect
that you will still have problems....
-pete

> 
> During the last 2-3 hours I've been scouring logs. Dmesg, acpid, and
> messages.
> 
> Ok here goes.  I booted up FC5 with kernel 2.6.15-1.2054_FC5 (the
> original one). After all the stuff that ends up in dmesg various
> daemons services are started. The first one to start with this kernel
> is "Acpi" as below. Starting Acpi Daemon           OK
> 
> This is verified by one entry in /var/log/acpid for today, even
> though I've booted other kernels today, but obviously because the
> acpid wasn't started for these other kernels, no entries are there.
> See below.
> 
> /var/log/acpid:
> [Thu Jan 11 16:45:57 2007] starting up
> [Thu Jan 11 16:45:57 2007] 1 rule loaded
> [Thu Jan 11 16:46:21 2007] client connected from 2171[68:68]
> [Thu Jan 11 16:46:21 2007] 1 client rule loaded
> 
> There was one entry also for yesterday, and the day before when I
> booted with this kernel, but I have rebooted using different kernels
> many times over the last couple of days, but with no entries in this
> log. 
> 
> Moving on to /var/log/messages. the first bit below is when booting
> with the 2.6.15 kernel (the one that shutsdown ok), the one I'm
> booted into at the mo.
> 
> Jan 11 16:45:29 localhost syslogd 1.4.1: restart.
> Jan 11 16:45:30 localhost kernel: klogd 1.4.1, log source
> = /proc/kmsg started.
> Jan 11 16:45:30 localhost kernel: Linux version 2.6.15-1.2054_FC5 
> (bhcompile@xxxxxxxxxxxxxxxxxxxxxxxxxxx) (gcc version 4.1.0 20060304
> (Red Hat 4.1.0-3)) #1 Tue Mar 14 15:48:33 EST 2006
> <snip>
> Jan 11 16:45:37 localhost kernel: ACPI: PM-Timer IO Port: 0x4008
> Jan 11 16:45:38 localhost kernel: Allocating PCI resources starting
> at 50000000 (gap: 40000000:bfff0000)
> Jan 11 16:45:38 localhost kernel: Built 1 zonelists
> Jan 11 16:45:38 localhost kernel: Kernel command line: ro
> root=LABEL=/1 Jan 11 16:45:38 localhost kernel: Local APIC disabled
> by BIOS -- you can enable it with "lapic"
> 
> The first line after the <snip> is the relevant one. Compare this
> with the output booting with a later kernel, as below.
> 
> Jan 11 15:49:45 localhost syslogd 1.4.1: restart.
> Jan 11 15:49:46 localhost kernel: klogd 1.4.1, log source
> = /proc/kmsg started.
> Jan 11 15:49:46 localhost kernel: Linux version 2.6.17-1.2174_FC5 
> (brewbuilder@xxxxxxxxxxxxxxxxxxxxxxxxxxx) (gcc version 4.1.1 20060525
> (Red Hat 4.1.1-1)) #1 Tue Aug 8 15:30:55 EDT 2006
> <snip>
> Jan 11 15:49:52 localhost kernel: ACPI: Disabling ACPI support
> Jan 11 15:49:53 localhost kernel: Allocating PCI resources starting
> at 50000000 (gap: 40000000:bfff0000)
> Jan 11 15:49:54 localhost kernel: Built 1 zonelists
> Jan 11 15:49:54 localhost kernel: Kernel command line: ro
> root=LABEL=/1 3 Jan 11 15:49:54 localhost kernel: Local APIC disabled
> by BIOS -- you can enable it with "lapic"
> 
> The first line after the <snip> here shows "ACPI: Disabling ACPI
> support", and this ( and I'm convinced after some updates to FC5) is
> the same for all kernels later than the 2.6.15 one.
> 
> Any Guru's out there that know whats going on here?
> 
> I'm personally convinced that this problem started after some updates
> to FC5, which are only affecting kernels later than my 2.6.15 one.
> Which update is anybodies guess.
> 
> Aaron has the same problem with FC6, but I presume the kernel that
> was installed, when he installed FC6 was a lot later version than my
> 2.6.15 one which shutsdown ok on FC5.
> 
> The menu item "Services" shows "Acpid" as running, in the status box
> for the 2.6.15 kernel, but for any later kernel the status box is
> empty, although "Acpid" is on "Services" list, and shows a
> description of it. Trying to start it for the later kernels, I get a
> confirmation box saying that it's started, but still nothing in the
> status box, so obviously it's lying.
> 
> This is a frustrating problem, especially as I have no idea as to
> which update has changed the behaviour of later kernels than the
> 2.6.15 one. Alright it's no big deal to have to press, and hold the
> start button on the machine to switch it off, but I shouldn't have to.
> 
> Nigel.
> 
> 
> 
> 
> 


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux