public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rogério Brito" <rbrito@ime.usp.br>
To: bugzilla-daemon@bugzilla.kernel.org
Cc: Denys Rogovchenko <denisius.sion@gmail.com>,
	"Rafael J.Wysocki" <rjw@sisk.pl>,
	"Artem S.Tashkinov" <t.artem@mailcity.com>,
	ykzhao <yakui.zhao@intel.com>,
	len.brown@intel.com, gmaizel@gmail.com,
	linux-kernel@vger.kernel.org
Subject: Re: [Bug 11255] S3: no resume, not even a beep - LG R700
Date: Sat, 24 Oct 2009 22:08:20 -0200	[thread overview]
Message-ID: <20091025000820.GA16225@ime.usp.br> (raw)
In-Reply-To: <8BDFD7B4-ABB5-45BD-BBC9-21C6AC4F48E9@ime.usp.br>

Hi, people.

First of all, to the bug reporters: please, let's get a bit more closer
and try to join our forces.

Triaging the bug report, seeing what still happens with the current
kernels etc. would all be helpful if we want to get our notebooks
working.

OK, now to the problem itself.

After some time without internet connection (humpf), I am back online
and I just did a git pull and a new kernel is being baked, soon to be
served. :-)

I did collect quite a bunch of extra information (including newer blobs
of dsdt, after the firmware upgrade from the firmware from MSI) and I
will upload those in a moment.

I hope that this will help us to better decide what is the culprit and
how we can better address this problem (perhaps asking MSI for some
involvement?).

Anyway, just as an extra piece of information, my notebook is what MSI
calls an MSI Aesthetic PR200 (well, at least after flashing it, that's
what it reports :) and it didn't die with this upgrade).

Some extra pointers (a script, actually) of what I did to create a boot
USB "disk" are outlined here: http://rb.doesntexist.org/diary/2009.xhtml


Hope this helps so far, Rogério Brito.

-- 
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org

  parent reply	other threads:[~2009-10-25  0:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-11255-5003@http.bugzilla.kernel.org/>
     [not found] ` <200909291835.n8TIZigc018246@demeter.kernel.org>
     [not found]   ` <8BDFD7B4-ABB5-45BD-BBC9-21C6AC4F48E9@ime.usp.br>
2009-10-07  5:57     ` [Bug 11255] S3: no resume, not even a beep - LG R700 Rogério Brito
2009-10-07 20:44       ` Rafael J. Wysocki
2009-10-25  0:08     ` Rogério Brito [this message]
2009-10-26 19:55       ` Rafael J. Wysocki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20091025000820.GA16225@ime.usp.br \
    --to=rbrito@ime.usp.br \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=denisius.sion@gmail.com \
    --cc=gmaizel@gmail.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=t.artem@mailcity.com \
    --cc=yakui.zhao@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox