public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Huang Ying <ying.huang@intel.com>
To: Drunkard Zhang <gongfan193@gmail.com>
Cc: Borislav Petkov <bp@amd64.org>, Greg KH <gregkh@suse.de>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Jin Dongming <jin.dongming@np.css.fujitsu.com>,
	"Brown, Len" <len.brown@intel.com>
Subject: Re: 2.6.39.2: duplicate filename '/devices/platform/GHES.9' on Asus DSBV-D
Date: Tue, 12 Jul 2011 09:13:06 +0800	[thread overview]
Message-ID: <4E1B9FA2.7090602@intel.com> (raw)
In-Reply-To: <20110708142453.GA15256@gere.osrc.amd.com>

Hi, Drunkard,

On 07/08/2011 10:24 PM, Borislav Petkov wrote:
> On Fri, Jul 08, 2011 at 06:40:03AM -0700, Greg KH wrote:
>> On Fri, Jul 08, 2011 at 04:02:27PM +0800, Drunkard Zhang wrote:
>>> On newly updated kernel I found this. I'm not sure it's a BIOS bug or
>>> kernel bug. More infomation attached. I can gather more infomation if
>>> you want :)
>>
>> It's an acpi issue, care to send it to that mailing list?
> 
> We had this issue already: http://lkml.org/lkml/2010/9/17/116 - I
> guess the fix wasn't complete. And yes, it is a BIOS bug but the
> kernel shouldn't OOPS just because BIOS programmers fell asleep on the
> keyboard.
> 
> Adding some more people to Cc.
> 

This bug has been reported and resolved in following bugzilla entry already.

https://bugzilla.kernel.org/show_bug.cgi?id=37412

We have the bugfix patch, just have not made it into upstream yet.

Best Regards,
Huang Ying

      parent reply	other threads:[~2011-07-12  1:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-08  8:02 2.6.39.2: duplicate filename '/devices/platform/GHES.9' on Asus DSBV-D Drunkard Zhang
2011-07-08 13:40 ` Greg KH
2011-07-08 14:24   ` Borislav Petkov
2011-07-08 14:35     ` Greg KH
2011-07-12  1:13     ` Huang Ying [this message]

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=4E1B9FA2.7090602@intel.com \
    --to=ying.huang@intel.com \
    --cc=bp@amd64.org \
    --cc=gongfan193@gmail.com \
    --cc=gregkh@suse.de \
    --cc=jin.dongming@np.css.fujitsu.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    /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