From: Greg KH <gregkh@linuxfoundation.org>
To: "Jörg-Volker Peetz" <jvpeetz@web.de>
Cc: 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>,
Alex Deucher <alexander.deucher@amd.com>
Subject: Re: Linux 4.4.4 [regression]
Date: Sat, 5 Mar 2016 09:41:47 -0800 [thread overview]
Message-ID: <20160305174147.GB14401@kroah.com> (raw)
In-Reply-To: <56DAB98D.6050305@web.de>
On Sat, Mar 05, 2016 at 11:48:45AM +0100, Jörg-Volker Peetz wrote:
> On my HP Pavilion dv7 with hybrid graphics (AMD HD 4200 - AMD 5400) X can't be
> started anymore. When trying to start X with "startx" Xorg freezes to an
> un-killable process before switching to a frame buffer. From another console I'm
> able to kill the xinit process which brings the first console back to the shell
> prompt. I can find nothing relevant in the logs.
>
> The last few lines in Xorg.0.log are:
>
> ...
> [ 61.007] (==) ModulePath set to "/usr/lib/xorg/modules"
> [ 61.007] (II) The server relies on udev to provide the list of input devices.
> If no devices become available, reconfigure udev or disable AutoAddDevices.
> [ 61.007] (II) Loader magic: 0x5571980cbdc0
> [ 61.008] (II) Module ABI versions:
> [ 61.008] X.Org ANSI C Emulation: 0.4
> [ 61.008] X.Org Video Driver: 20.0
> [ 61.008] X.Org XInput driver : 22.1
> [ 61.008] X.Org Server Extension : 9.0
> [ 61.009] (++) using VT number 1
>
> [ 61.009] (EE) systemd-logind: failed to get session: The name
> org.freedesktop.login1 was not provided by any .service files
> [ 61.010] (II) xfree86: Adding drm device (/dev/dri/card0)
> [ 61.011] (II) xfree86: Adding drm device (/dev/dri/card1)
>
> which are the same as with 4.4.3. There the log continues with
>
> [ 65.782] (--) PCI:*(0:1:5:0) 1002:9712:103c:1443 rev 0, Mem @
> 0xd0000000/268435456, 0xf0400000/65536, 0xf0300000/1048576, I/O @ 0x00004000/256
> [ 65.782] (--) PCI: (0:2:0:0) 1002:68e0:103c:1443 rev 0, Mem @
> 0xe0000000/268435456, 0xf0200000/131072, I/O @ 0x00003000/256, BIOS @
> 0x????????/131072
> [ 65.782] (II) LoadModule: "glx"
> [ 65.784] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
> [ 65.801] (II) Module glx: vendor="X.Org Foundation"
> ...
>
> I attach the config file.
Can you use 'git bisect' between 4.4.3 and 4.4.4 to track down the
offending patch?
thanks,
greg k-h
next prev parent reply other threads:[~2016-03-05 17:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 23:34 Linux 4.4.4 Greg KH
2016-03-03 23:34 ` Greg KH
2016-03-05 10:48 ` Linux 4.4.4 [regression] Jörg-Volker Peetz
2016-03-05 17:41 ` Greg KH [this message]
2016-03-06 13:18 ` Jörg-Volker Peetz
2016-03-07 1:14 ` Greg KH
2016-03-07 14:20 ` Jörg-Volker Peetz
2016-03-07 16:20 ` Linus Torvalds
2016-03-07 16:44 ` Deucher, Alexander
2016-03-07 17:40 ` Jörg-Volker Peetz
2016-03-07 18:07 ` Deucher, Alexander
2016-03-07 18:20 ` Jörg-Volker Peetz
2016-03-08 8:16 ` Jean Delvare
2016-03-08 8:48 ` Jean Delvare
2016-03-09 4:16 ` Greg KH
2016-03-09 14:40 ` Deucher, Alexander
2016-03-09 16:28 ` 'Greg KH'
2016-03-09 16:31 ` Deucher, Alexander
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=20160305174147.GB14401@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=alexander.deucher@amd.com \
--cc=jslaby@suse.cz \
--cc=jvpeetz@web.de \
--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
Powered by JetHome