[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100709160408.GU30043@gamma.logic.tuwien.ac.at>
Date: Sat, 10 Jul 2010 01:04:08 +0900
From: Norbert Preining <preining@...ic.at>
To: Jesse Barnes <jbarnes@...tuousgeek.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Kernel Testers List <kernel-testers@...r.kernel.org>,
Linux ACPI <linux-acpi@...r.kernel.org>,
Linux PM List <linux-pm@...ts.linux-foundation.org>
Subject: Re: 2.6.35-rc4-git3: Reported regressions from 2.6.34
Hi Jesse,
(stripping some people from Cc, hopefully not too many)
On Fr, 09 Jul 2010, Jesse Barnes wrote:
> > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16179
> > > Subject : 2.6.35-rc2 completely hosed on intel gfx?
> > > Submitter : Norbert Preining <preining@...ic.at>
> > > Date : 2010-06-06 11:55 (33 days old)
> > > Message-ID : <20100606115534.GA9399@...ma.logic.tuwien.ac.at>
> > > References : http://marc.info/?l=linux-kernel&m=127582534931581&w=2
> >
> > Hmm. That one is the vt.c bug coupled with another problem, which in
> > turn got opened as a separate bugzilla entry:
> >
> > http://bugzilla.kernel.org/show_bug.cgi?id=16252
> >
> > which in turn then got closed. I dunno.
>
> Yeah, this is weird. Norbert, do you still see this? Have you tried
> to bisect it?
I wrote in my last comment of this bug that in *most* of the cases
the
echo "mem" > /sys/power/state
works perfectly, and I'm using it permanently now.
The problem seems to be in combination with some pm-utils scripts.
I still haven't been able to pin-point the actual pm-utils script that
causes the problem, since that is something not 100% reproducible.
Futhermore, *once* (only once!) the echo mem > method failed as written in
the bug report with :
[16273.....] PM: resume of devices complete after 2115.046 msecs
[16273.....] Restarting tasks ... done
[16273.....] video LNXVIDEO:00: Restoring backlight state
hanging here, but only once, not any time again.
It is hard to say what the culprit is, some new pm-utils script maybe,
since it happens even when I switch pm-utils to use the kernel method
(echo mem) to suspend, and not uswsusp (s2ram prog).
I would suggest keeping that bug closed until I have found the pm-utils
or a specific culprit, then I can reopen it or open a new bug.
(more disturbing are iwlagn bugs, they are a PITA without any progress)
Best wishes
Norbert
------------------------------------------------------------------------
Norbert Preining preining@...ist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live & Debian Developer
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
------------------------------------------------------------------------
BLEAN
Scientific measure of luminosity : 1 glimmer = 100,000
bleans. Usherettes' torches are designed to produce between 2.5 and 4
bleans, enabling them to assist you in falling downstairs, treading on
people or putting your hand into a Neapolitan tub when reaching for
change.
--- Douglas Adams, The Meaning of Liff
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists