linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiang Liu <jiang.liu@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>, Thomas Voegtle <tv@lio96.de>
Cc: Dave Airlie <airlied@gmail.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Lv Zheng <lv.zheng@intel.com>
Subject: Re: regression in 4.0.0-rc1 with r8169 ethernet
Date: Sat, 28 Feb 2015 16:06:45 +0800	[thread overview]
Message-ID: <54F17715.6050506@linux.intel.com> (raw)
In-Reply-To: <1588858.OaSxSRONoY@vostro.rjw.lan>

On 2015/2/28 6:24, Rafael J. Wysocki wrote:
> On Friday, February 27, 2015 03:50:32 PM Thomas Voegtle wrote:
>>
>> Hi,
>>
>> I have the same problem with a Asrock Q1900B-ITX mainboard with 
>> a Intel Celeron J1900 onboard.
>>
>> I did a bisect and ended up with:
>>
>> 593669c2ac0fe18baee04a3cd5539a148aa48574 is the first bad commit
>>
>> commit 593669c2ac0fe18baee04a3cd5539a148aa48574
>> Author: Jiang Liu <jiang.liu@linux.intel.com>
>> Date:   Thu Feb 5 13:44:46 2015 +0800
>>
>>      x86/PCI/ACPI: Use common ACPI resource interfaces to simplify 
>> implementation
>>
>>
>> I can revert this quite big commit on current git head (4f671fe) with no 
>> problems and then everything is fine again.
> 
> Thanks for nailing this one!
> 
> It really wasn't supposed to make any functional difference, though, so there
> must be some subtle mistake that escaped everyone in it.
> 
> I'll have a look at that and hopefully Jiang Liu will be able to help in the
> meantime too.
Hi all,
	Sorry for slow response, just return from Chinese New Holidays:)
Hi Thomas,
	Could you please help to provide the dmesgs before and after the
revert?
Thanks!
Gerry

> 
> 

  reply	other threads:[~2015-02-28  8:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAPM=9tz8HQAZbdfgE15++i++NkArjxqiY3-BjANqDBTo1g-pOw@mail.gmail.com>
2015-02-25  5:46 ` regression in 4.0.0-rc1 with r8169 ethernet Bjorn Helgaas
2015-02-25  7:10 ` Bjorn Helgaas
2015-02-25  8:03   ` Dave Airlie
2015-02-25 22:42     ` Rafael J. Wysocki
2015-02-27 14:50     ` Thomas Voegtle
2015-02-27 22:24       ` Rafael J. Wysocki
2015-02-28  8:06         ` Jiang Liu [this message]
2015-02-28  8:36           ` Marcel Holtmann
2015-02-28  8:45             ` Jiang Liu
2015-02-28 10:03           ` Thomas Voegtle
2015-03-02  4:33             ` [Debug 0/2] Debug PCI root resource parsing failure Jiang Liu
2015-03-02  4:33               ` [Debug 1/2] x86/PCI/ACPI: Ignore resources consumed by host bridge itself Jiang Liu
2015-03-02  4:33               ` [Debug 2/2] x86/PCI/ACPI: Gather debug info Jiang Liu
2015-02-28  8:43   ` regression in 4.0.0-rc1 with r8169 ethernet Jiang Liu

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=54F17715.6050506@linux.intel.com \
    --to=jiang.liu@linux.intel.com \
    --cc=airlied@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lv.zheng@intel.com \
    --cc=rjw@rjwysocki.net \
    --cc=tglx@linutronix.de \
    --cc=tv@lio96.de \
    /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;
as well as URLs for NNTP newsgroup(s).