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

Bug#492581: marked as done (linux-image-2.6.25-2-686: Does not halt an EeePC 701)



Your message dated Mon, 1 Mar 2010 23:01:45 +0100
with message-id <20100301220145.GB28081@inutil.org>
and subject line Re: linux-image-2.6.25-2-686: Does not halt an EeePC 701
has caused the Debian Bug report #492581,
regarding linux-image-2.6.25-2-686: Does not halt an EeePC 701
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
492581: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492581
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.25-2-686
Version: 2.6.25-7
Severity: normal

I'm running this kernel on my EeePC 701.  When I tell the system to halt it
shuts down almost everything (the screen goes off) and then hangs.  It leaves
one LED on and produces some heat as the only indications that it's not off.



--- End Message ---
--- Begin Message ---
Version: 2.6.32-1

On Mon, Mar 01, 2010 at 10:38:31AM +1100, Russell Coker wrote:
> On Mon, 1 Mar 2010, Moritz Muehlenhoff <jmm@inutil.org> wrote:
> > The next release of Debian (6.0, code name Squeeze) will be based
> > on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell
> > us whether the problem persists. If so, we should report it upstream
> > to the kernel.org developers.
> >
> > The 2.6.32 kernel is available from packages.debian.org and can
> > be installed in both Debian stable, testing and unstable
> > installations.
> 
> I have been running an Unstable kernel on the EeePC in question for a while 
> and have not noticed the problem.  I think that the problem is fixed in 
> 2.6.32.  Feel free to close this bug, I can open another if the problem 
> occurs again.

Closing, then.

Cheers,
        Moritz


--- End Message ---

Reply to: