From: Ed Tomlinson <edt@aei.ca>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Ed Tomlinson <edt@aei.ca>, <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
<torvalds@linux-foundation.org>, <stable@vger.kernel.org>,
<lwn@lwn.net>, Jiri Slaby <jslaby@suse.cz>
Subject: Re: Linux 4.9.7
Date: Sat, 04 Feb 2017 19:35:39 -0500 [thread overview]
Message-ID: <fcf096b6-cbbd-4a9f-9273-fad2e59ce0b2@aei.ca> (raw)
In-Reply-To: <20170204075905.GA15045@kroah.com>
On Saturday, February 4, 2017 2:59:05 AM EST, Greg KH wrote:
> On Fri, Feb 03, 2017 at 11:07:08PM -0500, Ed Tomlinson wrote:
>> Hi,
>>
>> Any reports of 4.9.7 breaking X?
>>
>> I run arch and keep it up to date. With todays updates and
>> 4.9.7 built here
>> X will not start kde correctly. Reverting to 4.9.6 fixes
>> things. Config is
>> the same for both builds. I have three btrfs patches and the
>> BFQ 4.9.0-v8r7 ...
>
> There was a report of a PCI issue affecting 4.9.6, and the fix for that
> should be hitting Linus's tree soon (if it's not there already), but I
> haven't heard anything about problems with 4.9.7.
>
> Like the others said, if you could use 'git bisect' to track down the
> offending problem, that would be wonderful.
Greg
Looks like the original 4.9.7 build here must have failed in some wierd
way. I've run the bisect twice and its good till the end.
Sorry for the noise,
Ed
prev parent reply other threads:[~2017-02-05 0:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-02 10:10 Greg KH
2017-02-02 10:10 ` Greg KH
2017-02-04 4:07 ` Ed Tomlinson
2017-02-04 7:13 ` Willy Tarreau
2017-02-04 7:59 ` Greg KH
2017-02-05 0:35 ` Ed Tomlinson [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=fcf096b6-cbbd-4a9f-9273-fad2e59ce0b2@aei.ca \
--to=edt@aei.ca \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®