Re: FC5, And FC6 won't shutdown completely

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

 



On Thu, 2007-01-11 at 13:16 +0000, Anne Wilson wrote:
> On Thursday 11 January 2007 10:07, elk dolk wrote:
> > Rick Stevens <rstevens@xxxxxxxxxxxxxxx> wrote: From: Rick Stevens
> > <rstevens@xxxxxxxxxxxxxxx>
> >
> >  On Wed, 2007-01-10 at 22:13 +0100, Nigel Henry wrote:
> > > Both myself, and Aaron Konstram are having problems with the complete
> > > shutdown of our machines. I am running FC5, and since some updates to
> > > FC5, kernels later than the original kernel installed from the CDROM
> > > refuse to shutdown cmpletely. The shutdown messages reach "power off"
> > > then nothing, and you have to press, and hold the start button on the PC
> > > to switch the machine off. When shutdown reaches the power off stage, I
> > > hear the harddrives spin down, but the machine is still active.
> > >
> > > these ar the kernels on my FC5:
> > > 2.6.15-1.2054_FC5  (this one shutsdown ok)
> > > but all of these refuse to shutdown completely:
> > > 2.6.17-1.2174_FC5
> > > 2.6.17-1.2187_FC5
> > > 2.6.18-1.2200_FC5
> > > 2.6.18-1.2239_FC5
> > > and
> > > 2.6.18-1.2257_FC5
> > >
> > > I have been googling, and found suggestions to use "lapic" . I'm not sure
> > > how to use it. I tried at the grub prompt for the kernel, using "lapic",
> > > or lapic=on" (without the double quotes) , but no success.
> > >
> > > Anyone have any suggestion how to use lapic, or even if this might solve
> > > the problem?
> >
> > All you need to do is append "lapic" to the kernel line in grub:
> >
> >  kernel /boot/vmlinuz-2.6.18-1.2869.fc6 ro root=LABEL=/ rhgb
> >  quiet lapic
> >
> > (all on one line).  That may not solve your issue.  You may need to use
> > "noapic" instead:
> >
> >  kernel /boot/vmlinuz-2.6.18-1.2869.fc6 ro root=LABEL=/ rhgb
> >  quiet noapic
> >
> >
> > My box has the same problem but appending lapic or noapic does not solve
> > the problem !
> >
> I know of one box that required 'noapic nolapic'.  It seems to be trial and 
> error for this sort of problem.
> 
> Anne
I don't mind trial and error but it would be noce if someone would
explain why these additions to the kernel line would be needed. In my
case it is not the machine that has changed but the operating system
that has changed. Why7 only FC6 (in my case) has this problem? 
--
=======================================================================
English literature's performing flea. -- Sean O'Casey on P.G. Wodehouse
=======================================================================
Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam@xxxxxxxxxxxxx

[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora Magazine]     [Fedora News]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux