2014-06-22 14:25:16

by Martin Kepplinger

[permalink] [raw]
Subject: [BUG] rc1 and rc2: Laptop unusable: on boot,screen black instead of native resolution

Since 3.16-rc1 my laptop's just goes black while booting, instead of
switching to native screen resolution and showing me the starting
system there. It's an Acer TravelMate B113 with i915 driver and
acer_wmi. It stays black and is unusable.

Do you have other people complain about that? Bisecting didn't lead to a
good result. I could be wrong but I somehow suspect the mistake to be
somewhere in commit 99678ed73a50d2df8b5f3c801e29e9b7a3e5aa85

There is nothing unusual in the kernel log.

This is quite unusual for an -rc2. Hence my question. I'm happy to test
changes.

martin
--
Martin Kepplinger
e-mail martink AT posteo DOT at
chat (XMPP) martink AT jabber DOT at


2014-06-23 01:11:12

by Zhang, Rui

[permalink] [raw]
Subject: RE: [BUG] rc1 and rc2: Laptop unusable: on boot,screen black instead of native resolution



> -----Original Message-----
> From: Martin Kepplinger [mailto:[email protected]]
> Sent: Sunday, June 22, 2014 10:25 PM
> To: Zhang, Rui
> Cc: [email protected]; [email protected]; [email protected];
> [email protected]
> Subject: [BUG] rc1 and rc2: Laptop unusable: on boot,screen black
> instead of native resolution
> Importance: High
>
> Since 3.16-rc1 my laptop's just goes black while booting, instead of
> switching to native screen resolution and showing me the starting
> system there. It's an Acer TravelMate B113 with i915 driver and
> acer_wmi. It stays black and is unusable.
>
> Do you have other people complain about that? Bisecting didn't lead to
> a good result. I could be wrong but I somehow suspect the mistake to be
> somewhere in commit 99678ed73a50d2df8b5f3c801e29e9b7a3e5aa85
>
In order to confirm if the problem is introduced by the above commit,
why not checkout the kernel just before and after this commit and see if the problem exists?

Thanks,
rui


> There is nothing unusual in the kernel log.
>
> This is quite unusual for an -rc2. Hence my question. I'm happy to test
> changes.
>
> martin
> --
> Martin Kepplinger
> e-mail martink AT posteo DOT at
> chat (XMPP) martink AT jabber DOT at

2014-06-23 12:22:57

by Martin Kepplinger

[permalink] [raw]
Subject: Re: [BUG] rc1 and rc2: Laptop unusable: on boot,screen black instead of native resolution

Am 2014-06-23 03:10, schrieb Zhang, Rui:
>
>
>> -----Original Message-----
>> From: Martin Kepplinger [mailto:[email protected]]
>> Sent: Sunday, June 22, 2014 10:25 PM
>> To: Zhang, Rui
>> Cc: [email protected]; [email protected]; [email protected];
>> [email protected]
>> Subject: [BUG] rc1 and rc2: Laptop unusable: on boot,screen black
>> instead of native resolution
>> Importance: High
>>
>> Since 3.16-rc1 my laptop's just goes black while booting, instead of
>> switching to native screen resolution and showing me the starting
>> system there. It's an Acer TravelMate B113 with i915 driver and
>> acer_wmi. It stays black and is unusable.
>>
>> Do you have other people complain about that? Bisecting didn't lead to
>> a good result. I could be wrong but I somehow suspect the mistake to be
>> somewhere in commit 99678ed73a50d2df8b5f3c801e29e9b7a3e5aa85
>>
> In order to confirm if the problem is introduced by the above commit,
> why not checkout the kernel just before and after this commit and see if the problem exists?
>
> Thanks,
> rui
>
So maybe I was wrong. d27050641e9bc056446deb0814e7ba1aa7911f5a is still
good and aaeb2554337217dfa4eac2fcc90da7be540b9a73 is the fist bad one.
This is a big v4l merge. I added the linux-media list in cc now.

What could be the problem here?

>
>> There is nothing unusual in the kernel log.
>>
>> This is quite unusual for an -rc2. Hence my question. I'm happy to test
>> changes.
>>
>> martin
>> --
>> Martin Kepplinger
>> e-mail martink AT posteo DOT at
>> chat (XMPP) martink AT jabber DOT at

2014-06-23 13:14:15

by Zhang, Rui

[permalink] [raw]
Subject: Re: [BUG] rc1 and rc2: Laptop unusable: on boot,screen black instead of native resolution

On Mon, 2014-06-23 at 14:22 +0200, Martin Kepplinger wrote:
> Am 2014-06-23 03:10, schrieb Zhang, Rui:
> >
> >
> >> -----Original Message-----
> >> From: Martin Kepplinger [mailto:[email protected]]
> >> Sent: Sunday, June 22, 2014 10:25 PM
> >> To: Zhang, Rui
> >> Cc: [email protected]; [email protected]; [email protected];
> >> [email protected]
> >> Subject: [BUG] rc1 and rc2: Laptop unusable: on boot,screen black
> >> instead of native resolution
> >> Importance: High
> >>
> >> Since 3.16-rc1 my laptop's just goes black while booting, instead of
> >> switching to native screen resolution and showing me the starting
> >> system there. It's an Acer TravelMate B113 with i915 driver and
> >> acer_wmi. It stays black and is unusable.
> >>
This looks like a duplicate of
https://bugzilla.kernel.org/show_bug.cgi?id=78601

thanks,
rui
> >> Do you have other people complain about that? Bisecting didn't lead to
> >> a good result. I could be wrong but I somehow suspect the mistake to be
> >> somewhere in commit 99678ed73a50d2df8b5f3c801e29e9b7a3e5aa85
> >>
> > In order to confirm if the problem is introduced by the above commit,
> > why not checkout the kernel just before and after this commit and see if the problem exists?
> >
> > Thanks,
> > rui
> >
> So maybe I was wrong. d27050641e9bc056446deb0814e7ba1aa7911f5a is still
> good and aaeb2554337217dfa4eac2fcc90da7be540b9a73 is the fist bad one.
> This is a big v4l merge. I added the linux-media list in cc now.
>
> What could be the problem here?
>
> >
> >> There is nothing unusual in the kernel log.
> >>
> >> This is quite unusual for an -rc2. Hence my question. I'm happy to test
> >> changes.
> >>
> >> martin
> >> --
> >> Martin Kepplinger
> >> e-mail martink AT posteo DOT at
> >> chat (XMPP) martink AT jabber DOT at
>

2014-06-23 14:47:15

by Martin Kepplinger

[permalink] [raw]
Subject: Re: [BUG] rc1 and rc2: Laptop unusable: on boot,screen black instead of native resolution

Am 2014-06-23 15:14, schrieb Zhang Rui:
> On Mon, 2014-06-23 at 14:22 +0200, Martin Kepplinger wrote:
>> Am 2014-06-23 03:10, schrieb Zhang, Rui:
>>>
>>>
>>>> -----Original Message-----
>>>> From: Martin Kepplinger [mailto:[email protected]]
>>>> Sent: Sunday, June 22, 2014 10:25 PM
>>>> To: Zhang, Rui
>>>> Cc: [email protected]; [email protected]; [email protected];
>>>> [email protected]
>>>> Subject: [BUG] rc1 and rc2: Laptop unusable: on boot,screen black
>>>> instead of native resolution
>>>> Importance: High
>>>>
>>>> Since 3.16-rc1 my laptop's just goes black while booting, instead of
>>>> switching to native screen resolution and showing me the starting
>>>> system there. It's an Acer TravelMate B113 with i915 driver and
>>>> acer_wmi. It stays black and is unusable.
>>>>
> This looks like a duplicate of
> https://bugzilla.kernel.org/show_bug.cgi?id=78601
>
> thanks,
> rui
I'm not sure about that. I have no problem with v3.15 and the screen
goes black way before a display manager is started. It's right after the
kernel loaded and usually the screen is set to native resolution.

Bisect told me aaeb2554337217dfa4eac2fcc90da7be540b9a73 as the first bad
one. Although, checking that out and running it, works good. not sure if
that makes sense.

>>>> Do you have other people complain about that? Bisecting didn't lead to
>>>> a good result. I could be wrong but I somehow suspect the mistake to be
>>>> somewhere in commit 99678ed73a50d2df8b5f3c801e29e9b7a3e5aa85
>>>>
>>> In order to confirm if the problem is introduced by the above commit,
>>> why not checkout the kernel just before and after this commit and see if the problem exists?
>>>
>>> Thanks,
>>> rui
>>>
>> So maybe I was wrong. d27050641e9bc056446deb0814e7ba1aa7911f5a is still
>> good and aaeb2554337217dfa4eac2fcc90da7be540b9a73 is the fist bad one.
>> This is a big v4l merge. I added the linux-media list in cc now.
>>
>> What could be the problem here?
>>
>>>
>>>> There is nothing unusual in the kernel log.
>>>>
>>>> This is quite unusual for an -rc2. Hence my question. I'm happy to test
>>>> changes.
>>>>
>>>> martin
>>>> --
>>>> Martin Kepplinger
>>>> e-mail martink AT posteo DOT at
>>>> chat (XMPP) martink AT jabber DOT at
>>
>
>

2014-06-23 20:26:44

by Felix Miata

[permalink] [raw]
Subject: Re: [BUG] black screens (was: rc1 and rc2...screen black ...)

>> This looks like a duplicate of
>> https://bugzilla.kernel.org/show_bug.cgi?id=78601

Maybe these are related?

https://bugzilla.redhat.com/show_bug.cgi?id=1104371
https://bugzilla.redhat.com/show_bug.cgi?id=1096487
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata *** http://fm.no-ip.com/

2014-06-27 15:14:47

by Zhang, Rui

[permalink] [raw]
Subject: Re: [BUG] rc1 and rc2: Laptop unusable: on boot,screen black instead of native resolution

On Mon, 2014-06-23 at 16:46 +0200, Martin Kepplinger wrote:
> Am 2014-06-23 15:14, schrieb Zhang Rui:
> > On Mon, 2014-06-23 at 14:22 +0200, Martin Kepplinger wrote:
> >> Am 2014-06-23 03:10, schrieb Zhang, Rui:
> >>>
> >>>
> >>>> -----Original Message-----
> >>>> From: Martin Kepplinger [mailto:[email protected]]
> >>>> Sent: Sunday, June 22, 2014 10:25 PM
> >>>> To: Zhang, Rui
> >>>> Cc: [email protected]; [email protected]; [email protected];
> >>>> [email protected]
> >>>> Subject: [BUG] rc1 and rc2: Laptop unusable: on boot,screen black
> >>>> instead of native resolution
> >>>> Importance: High
> >>>>
> >>>> Since 3.16-rc1 my laptop's just goes black while booting, instead of
> >>>> switching to native screen resolution and showing me the starting
> >>>> system there. It's an Acer TravelMate B113 with i915 driver and
> >>>> acer_wmi. It stays black and is unusable.
> >>>>
> > This looks like a duplicate of
> > https://bugzilla.kernel.org/show_bug.cgi?id=78601
> >
> > thanks,
> > rui
> I'm not sure about that. I have no problem with v3.15 and the screen
> goes black way before a display manager is started. It's right after the
> kernel loaded and usually the screen is set to native resolution.
>
> Bisect told me aaeb2554337217dfa4eac2fcc90da7be540b9a73 as the first bad
> one. Although, checking that out and running it, works good. not sure if
> that makes sense.
>
could you please check if the comment in
https://bugzilla.kernel.org/show_bug.cgi?id=78601#c5 solves your problem
or not?

thanks,
rui
> >>>> Do you have other people complain about that? Bisecting didn't lead to
> >>>> a good result. I could be wrong but I somehow suspect the mistake to be
> >>>> somewhere in commit 99678ed73a50d2df8b5f3c801e29e9b7a3e5aa85
> >>>>
> >>> In order to confirm if the problem is introduced by the above commit,
> >>> why not checkout the kernel just before and after this commit and see if the problem exists?
> >>>
> >>> Thanks,
> >>> rui
> >>>
> >> So maybe I was wrong. d27050641e9bc056446deb0814e7ba1aa7911f5a is still
> >> good and aaeb2554337217dfa4eac2fcc90da7be540b9a73 is the fist bad one.
> >> This is a big v4l merge. I added the linux-media list in cc now.
> >>
> >> What could be the problem here?
> >>
> >>>
> >>>> There is nothing unusual in the kernel log.
> >>>>
> >>>> This is quite unusual for an -rc2. Hence my question. I'm happy to test
> >>>> changes.
> >>>>
> >>>> martin
> >>>> --
> >>>> Martin Kepplinger
> >>>> e-mail martink AT posteo DOT at
> >>>> chat (XMPP) martink AT jabber DOT at
> >>
> >
> >
>

2014-06-27 18:10:11

by Martin Kepplinger

[permalink] [raw]
Subject: Re: [BUG] rc1 and rc2: Laptop unusable: on boot,screen black instead of native resolution

Am 2014-06-27 17:14, schrieb Zhang Rui:
> On Mon, 2014-06-23 at 16:46 +0200, Martin Kepplinger wrote:
>> Am 2014-06-23 15:14, schrieb Zhang Rui:
>>> On Mon, 2014-06-23 at 14:22 +0200, Martin Kepplinger wrote:
>>>> Am 2014-06-23 03:10, schrieb Zhang, Rui:
>>>>>
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Martin Kepplinger [mailto:[email protected]]
>>>>>> Sent: Sunday, June 22, 2014 10:25 PM
>>>>>> To: Zhang, Rui
>>>>>> Cc: [email protected]; [email protected]; [email protected];
>>>>>> [email protected]
>>>>>> Subject: [BUG] rc1 and rc2: Laptop unusable: on boot,screen black
>>>>>> instead of native resolution
>>>>>> Importance: High
>>>>>>
>>>>>> Since 3.16-rc1 my laptop's just goes black while booting, instead of
>>>>>> switching to native screen resolution and showing me the starting
>>>>>> system there. It's an Acer TravelMate B113 with i915 driver and
>>>>>> acer_wmi. It stays black and is unusable.
>>>>>>
>>> This looks like a duplicate of
>>> https://bugzilla.kernel.org/show_bug.cgi?id=78601
>>>
>>> thanks,
>>> rui
>> I'm not sure about that. I have no problem with v3.15 and the screen
>> goes black way before a display manager is started. It's right after the
>> kernel loaded and usually the screen is set to native resolution.
>>
>> Bisect told me aaeb2554337217dfa4eac2fcc90da7be540b9a73 as the first bad
>> one. Although, checking that out and running it, works good. not sure if
>> that makes sense.
>>
> could you please check if the comment in
> https://bugzilla.kernel.org/show_bug.cgi?id=78601#c5 solves your problem
> or not?
>
> thanks,
> rui

thanks for checking. This does not change anything though. I tested the
following on top of v3.16-rc2 and linus's tree as of today, almost -rc3.

---
drivers/gpu/drm/i915/intel_fbdev.c | 1 -
1 file changed, 1 deletion(-)

diff --git a/drivers/gpu/drm/i915/intel_fbdev.c
b/drivers/gpu/drm/i915/intel_fbdev.c
index 088fe93..1e2f9ae 100644
--- a/drivers/gpu/drm/i915/intel_fbdev.c
+++ b/drivers/gpu/drm/i915/intel_fbdev.c
@@ -453,7 +453,6 @@ out:
}

static struct drm_fb_helper_funcs intel_fb_helper_funcs = {
- .initial_config = intel_fb_initial_config,
.gamma_set = intel_crtc_fb_gamma_set,
.gamma_get = intel_crtc_fb_gamma_get,
.fb_probe = intelfb_create,
--
1.7.10.4



>>>>>> Do you have other people complain about that? Bisecting didn't lead to
>>>>>> a good result. I could be wrong but I somehow suspect the mistake to be
>>>>>> somewhere in commit 99678ed73a50d2df8b5f3c801e29e9b7a3e5aa85
>>>>>>
>>>>> In order to confirm if the problem is introduced by the above commit,
>>>>> why not checkout the kernel just before and after this commit and see if the problem exists?
>>>>>
>>>>> Thanks,
>>>>> rui
>>>>>
>>>> So maybe I was wrong. d27050641e9bc056446deb0814e7ba1aa7911f5a is still
>>>> good and aaeb2554337217dfa4eac2fcc90da7be540b9a73 is the fist bad one.
>>>> This is a big v4l merge. I added the linux-media list in cc now.
>>>>
>>>> What could be the problem here?
>>>>
>>>>>
>>>>>> There is nothing unusual in the kernel log.
>>>>>>
>>>>>> This is quite unusual for an -rc2. Hence my question. I'm happy to test
>>>>>> changes.
>>>>>>
>>>>>> martin
>>>>>> --
>>>>>> Martin Kepplinger
>>>>>> e-mail martink AT posteo DOT at
>>>>>> chat (XMPP) martink AT jabber DOT at
>>>>
>>>
>>>
>>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>

2014-06-27 19:51:42

by Martin Kepplinger

[permalink] [raw]
Subject: Re: [BUG] rc1 and rc2: Laptop unusable: on boot,screen black instead of native resolution

Am 2014-06-27 20:09, schrieb Martin Kepplinger:
> Am 2014-06-27 17:14, schrieb Zhang Rui:
>> On Mon, 2014-06-23 at 16:46 +0200, Martin Kepplinger wrote:
>>> Am 2014-06-23 15:14, schrieb Zhang Rui:
>>>> On Mon, 2014-06-23 at 14:22 +0200, Martin Kepplinger wrote:
>>>>> Am 2014-06-23 03:10, schrieb Zhang, Rui:
>>>>>>
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Martin Kepplinger [mailto:[email protected]]
>>>>>>> Sent: Sunday, June 22, 2014 10:25 PM
>>>>>>> To: Zhang, Rui
>>>>>>> Cc: [email protected]; [email protected]; [email protected];
>>>>>>> [email protected]
>>>>>>> Subject: [BUG] rc1 and rc2: Laptop unusable: on boot,screen black
>>>>>>> instead of native resolution
>>>>>>> Importance: High
>>>>>>>
>>>>>>> Since 3.16-rc1 my laptop's just goes black while booting, instead of
>>>>>>> switching to native screen resolution and showing me the starting
>>>>>>> system there. It's an Acer TravelMate B113 with i915 driver and
>>>>>>> acer_wmi. It stays black and is unusable.
>>>>>>>
>>>> This looks like a duplicate of
>>>> https://bugzilla.kernel.org/show_bug.cgi?id=78601
>>>>
>>>> thanks,
>>>> rui
>>> I'm not sure about that. I have no problem with v3.15 and the screen
>>> goes black way before a display manager is started. It's right after the
>>> kernel loaded and usually the screen is set to native resolution.
>>>
>>> Bisect told me aaeb2554337217dfa4eac2fcc90da7be540b9a73 as the first bad
>>> one. Although, checking that out and running it, works good. not sure if
>>> that makes sense.
>>>
>> could you please check if the comment in
>> https://bugzilla.kernel.org/show_bug.cgi?id=78601#c5 solves your problem
>> or not?
>>
>> thanks,
>> rui
>
> thanks for checking. This does not change anything though. I tested the
> following on top of v3.16-rc2 and linus's tree as of today, almost -rc3.
>
> ---
> drivers/gpu/drm/i915/intel_fbdev.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_fbdev.c
> b/drivers/gpu/drm/i915/intel_fbdev.c
> index 088fe93..1e2f9ae 100644
> --- a/drivers/gpu/drm/i915/intel_fbdev.c
> +++ b/drivers/gpu/drm/i915/intel_fbdev.c
> @@ -453,7 +453,6 @@ out:
> }
>
> static struct drm_fb_helper_funcs intel_fb_helper_funcs = {
> - .initial_config = intel_fb_initial_config,
> .gamma_set = intel_crtc_fb_gamma_set,
> .gamma_get = intel_crtc_fb_gamma_get,
> .fb_probe = intelfb_create,
>

I also tested the following patch from
http://lists.freedesktop.org/archives/intel-gfx/2014-June/047981.html
now, with no results. No change in my case :(

diff --git a/drivers/gpu/drm/i915/intel_display.c
b/drivers/gpu/drm/i915/intel_display.c
index efd3cf5..5aee08e 100644
--- a/drivers/gpu/drm/i915/intel_display.c
+++ b/drivers/gpu/drm/i915/intel_display.c
@@ -11087,6 +11087,22 @@ const char *intel_output_name(int output)
return names[output];
}

+static bool intel_crt_present(struct drm_device *dev)
+{
+ struct drm_i915_private *dev_priv = dev->dev_private;
+
+ if (IS_ULT(dev))
+ return false;
+
+ if (IS_CHERRYVIEW(dev))
+ return false;
+
+ if (IS_VALLEYVIEW(dev) && !dev_priv->vbt.int_crt_support)
+ return false;
+
+ return true;
+}
+
static void intel_setup_outputs(struct drm_device *dev)
{
struct drm_i915_private *dev_priv = dev->dev_private;
@@ -11095,7 +11111,7 @@ static void intel_setup_outputs(struct
drm_device *dev)

intel_lvds_init(dev);

- if (!IS_ULT(dev) && !IS_CHERRYVIEW(dev) &&
dev_priv->vbt.int_crt_support)
+ if (intel_crt_present(dev))
intel_crt_init(dev);

if (HAS_DDI(dev)) {
--
1.7.10.4

2014-06-27 22:15:28

by Martin Kepplinger

[permalink] [raw]
Subject: Re: [BUG] rc1 and rc2: Laptop unusable: on boot,screen black instead of native resolution

Am 2014-06-27 21:51, schrieb Martin Kepplinger:
> Am 2014-06-27 20:09, schrieb Martin Kepplinger:
>> Am 2014-06-27 17:14, schrieb Zhang Rui:
>>> On Mon, 2014-06-23 at 16:46 +0200, Martin Kepplinger wrote:
>>>> Am 2014-06-23 15:14, schrieb Zhang Rui:
>>>>> On Mon, 2014-06-23 at 14:22 +0200, Martin Kepplinger wrote:
>>>>>> Am 2014-06-23 03:10, schrieb Zhang, Rui:
>>>>>>>
>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: Martin Kepplinger [mailto:[email protected]]
>>>>>>>> Sent: Sunday, June 22, 2014 10:25 PM
>>>>>>>> To: Zhang, Rui
>>>>>>>> Cc: [email protected]; [email protected]; [email protected];
>>>>>>>> [email protected]
>>>>>>>> Subject: [BUG] rc1 and rc2: Laptop unusable: on boot,screen black
>>>>>>>> instead of native resolution
>>>>>>>> Importance: High
>>>>>>>>
>>>>>>>> Since 3.16-rc1 my laptop's just goes black while booting, instead of
>>>>>>>> switching to native screen resolution and showing me the starting
>>>>>>>> system there. It's an Acer TravelMate B113 with i915 driver and
>>>>>>>> acer_wmi. It stays black and is unusable.
>>>>>>>>
>>>>> This looks like a duplicate of
>>>>> https://bugzilla.kernel.org/show_bug.cgi?id=78601
>>>>>
>>>>> thanks,
>>>>> rui
>>>> I'm not sure about that. I have no problem with v3.15 and the screen
>>>> goes black way before a display manager is started. It's right after the
>>>> kernel loaded and usually the screen is set to native resolution.
>>>>
>>>> Bisect told me aaeb2554337217dfa4eac2fcc90da7be540b9a73 as the first bad
>>>> one. Although, checking that out and running it, works good. not sure if
>>>> that makes sense.
>>>>
>>> could you please check if the comment in
>>> https://bugzilla.kernel.org/show_bug.cgi?id=78601#c5 solves your problem
>>> or not?
>>>
>>> thanks,
>>> rui
>>
>> thanks for checking. This does not change anything though. I tested the
>> following on top of v3.16-rc2 and linus's tree as of today, almost -rc3.
>>
>> ---
>> drivers/gpu/drm/i915/intel_fbdev.c | 1 -
>> 1 file changed, 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_fbdev.c
>> b/drivers/gpu/drm/i915/intel_fbdev.c
>> index 088fe93..1e2f9ae 100644
>> --- a/drivers/gpu/drm/i915/intel_fbdev.c
>> +++ b/drivers/gpu/drm/i915/intel_fbdev.c
>> @@ -453,7 +453,6 @@ out:
>> }
>>
>> static struct drm_fb_helper_funcs intel_fb_helper_funcs = {
>> - .initial_config = intel_fb_initial_config,
>> .gamma_set = intel_crtc_fb_gamma_set,
>> .gamma_get = intel_crtc_fb_gamma_get,
>> .fb_probe = intelfb_create,
>>
>
> I also tested the following patch from
> http://lists.freedesktop.org/archives/intel-gfx/2014-June/047981.html
> now, with no results. No change in my case :(
>
> diff --git a/drivers/gpu/drm/i915/intel_display.c
> b/drivers/gpu/drm/i915/intel_display.c
> index efd3cf5..5aee08e 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -11087,6 +11087,22 @@ const char *intel_output_name(int output)
> return names[output];
> }
>
> +static bool intel_crt_present(struct drm_device *dev)
> +{
> + struct drm_i915_private *dev_priv = dev->dev_private;
> +
> + if (IS_ULT(dev))
> + return false;
> +
> + if (IS_CHERRYVIEW(dev))
> + return false;
> +
> + if (IS_VALLEYVIEW(dev) && !dev_priv->vbt.int_crt_support)
> + return false;
> +
> + return true;
> +}
> +
> static void intel_setup_outputs(struct drm_device *dev)
> {
> struct drm_i915_private *dev_priv = dev->dev_private;
> @@ -11095,7 +11111,7 @@ static void intel_setup_outputs(struct
> drm_device *dev)
>
> intel_lvds_init(dev);
>
> - if (!IS_ULT(dev) && !IS_CHERRYVIEW(dev) &&
> dev_priv->vbt.int_crt_support)
> + if (intel_crt_present(dev))
> intel_crt_init(dev);
>
> if (HAS_DDI(dev)) {
>
I'm on i686 and also the following from
https://bugzilla.redhat.com/show_bug.cgi?id=1110968#c16 does not help :(
this is bad.

---
arch/x86/kernel/signal.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/arch/x86/kernel/signal.c
+++ a/arch/x86/kernel/signal.c
@@ -363,7 +363,7 @@ static int __setup_rt_frame(int sig, struct ksignal
*ksig,

/* Set up to return from userspace. */
restorer = current->mm->context.vdso +
- selected_vdso32->sym___kernel_sigreturn;
+ selected_vdso32->sym___kernel_rt_sigreturn;
if (ksig->ka.sa.sa_flags & SA_RESTORER)
restorer = ksig->ka.sa.sa_restorer;
put_user_ex(restorer, &frame->pretcode);
--

2014-06-30 07:53:37

by Martin Kepplinger

[permalink] [raw]
Subject: Re: [BUG] rc3 Oops: unable to handle kernel NULL pointer dereference at 0000074c

I now booted 3.16-rc3 and suddenly see an oops during boot:

the oops during boot: http://tny.cz/2301e393
also below

lshw if interesting: http://tny.cz/3c9a7609

the full boot log: http://tny.cz/88260b19

does anyone have an idea?
thanks

the oops:

Jun 30 08:35:08 laptop kernel: [ 5.245811] bus: 'platform':
really_probe: probing driver coretemp with device coretemp.0
Jun 30 08:35:08 laptop kernel: [ 5.246134] BUG: unable to handle
kernel NULL pointer dereference at 0000074c
Jun 30 08:35:08 laptop kernel: [ 5.246145] IP: [<c10325d9>]
is_highmem+0x1/0x2b
Jun 30 08:35:08 laptop kernel: [ 5.246158] *pdpt = 0000000033e49001
*pde = 0000000000000000
Jun 30 08:35:08 laptop kernel: [ 5.246167] Oops: 0000 [#1] SMP
Jun 30 08:35:08 laptop kernel: [ 5.246175] Modules linked in:
coretemp(+) kvm_intel kvm snd_hda_codec_hdmi snd_hda_codec_realtek
snd_hda_codec_generic microcode snd_hda_intel i915(+) snd_hda_controller
evdev psmouse snd_hda_codec serio_raw snd_hwdep snd_pcm iwlwifi i2c_i801
lpc_ich mfd_core snd_seq drm_kms_helper snd_timer battery ehci_pci
snd_seq_device drm cfg80211 ehci_hcd snd i2c_algo_bit ac video i2c_core
rfkill soundcore wmi acpi_cpufreq button processor thermal_sys ext4
crc16 jbd2 mbcache sg sd_mod crct10dif_generic crc_t10dif
crct10dif_common ahci libahci crc32c_intel tg3 ptp libata pps_core
sdhci_pci sdhci scsi_mod mmc_core libphy xhci_hcd usbcore usb_common
Jun 30 08:35:08 laptop kernel: [ 5.246320] CPU: 1 PID: 491 Comm:
modprobe Not tainted 3.16.0-rc3 #83
Jun 30 08:35:08 laptop kernel: [ 5.246330] Hardware name: Acer
TravelMate B113/BA10_HX , BIOS V1.09 10/30/2012
Jun 30 08:35:08 laptop kernel: [ 5.246344] task: f3828a90 ti:
f3e88000 task.ti: f3e88000
Jun 30 08:35:08 laptop kernel: [ 5.246355] EIP: 0060:[<c10325d9>]
EFLAGS: 00010206 CPU: 1
Jun 30 08:35:08 laptop kernel: [ 5.246367] EIP is at is_highmem+0x1/0x2b
Jun 30 08:35:08 laptop kernel: [ 5.246376] EAX: 000003c0 EBX:
ffb76000 ECX: 00000001 EDX: 000003c0
Jun 30 08:35:08 laptop kernel: [ 5.246386] ESI: f86cd279 EDI:
00000000 EBP: f3e89c10 ESP: f3e89c04
Jun 30 08:35:08 laptop kernel: [ 5.246396] DS: 007b ES: 007b FS:
00d8 GS: 00e0 SS: 0068
Jun 30 08:35:08 laptop kernel: [ 5.246405] CR0: 80050033 CR2:
0000074c CR3: 2e3fc000 CR4: 000407f0
Jun 30 08:35:08 laptop kernel: [ 5.246414] Stack:
Jun 30 08:35:08 laptop kernel: [ 5.246421] f3e89c10 c1032889
f3cbcc60 f3e89c4c f86b52bf 00000005 00000000 00000448
Jun 30 08:35:08 laptop kernel: [ 5.246442] f3e89c30 00000006
00165000 ffb76000 00000113 f870f010 ee881128 ee881128
Jun 30 08:35:08 laptop kernel: [ 5.246465] 00000001 f418b980
f3e89c74 f86b4e5c 00000000 f3911e00 f3911e00 ee881128
Jun 30 08:35:08 laptop kernel: [ 5.246487] Call Trace:
Jun 30 08:35:08 laptop kernel: [ 5.246500] [<c1032889>] ?
kunmap+0x3b/0x4e
Jun 30 08:35:08 laptop kernel: [ 5.246578] [<f86b52bf>] ?
i915_gem_render_state_init+0x24f/0x28c [i915]
Jun 30 08:35:08 laptop kernel: [ 5.246634] [<f86b4e5c>] ?
i915_switch_context+0x348/0x387 [i915]
Jun 30 08:35:08 laptop kernel: [ 5.246684] [<f86b4f0f>] ?
i915_gem_context_enable+0x74/0x7c [i915]
Jun 30 08:35:08 laptop kernel: [ 5.246742] [<f86bcd38>] ?
i915_gem_init_hw+0x23e/0x285 [i915]
Jun 30 08:35:08 laptop kernel: [ 5.246818] [<f86bce7e>] ?
i915_gem_init+0xff/0x179 [i915]
Jun 30 08:35:08 laptop kernel: [ 5.246924] [<f87047d9>] ?
i915_driver_load+0x989/0xc1d [i915]
Jun 30 08:35:08 laptop kernel: [ 5.246940] [<c1267429>] ?
get_device+0x14/0x1d
Jun 30 08:35:08 laptop kernel: [ 5.246955] [<c1268832>] ?
device_add+0x3b7/0x4a9
Jun 30 08:35:08 laptop kernel: [ 5.246996] [<f8619c80>] ?
drm_minor_register+0x104/0x15c [drm]
Jun 30 08:35:08 laptop kernel: [ 5.247033] [<f8619d44>] ?
drm_dev_register+0x6c/0xce [drm]
Jun 30 08:35:08 laptop kernel: [ 5.247072] [<f861bbb4>] ?
drm_get_pci_dev+0xde/0x174 [drm]
Jun 30 08:35:08 laptop kernel: [ 5.247088] [<c11dcc58>] ?
local_pci_probe+0x33/0x6c
Jun 30 08:35:08 laptop kernel: [ 5.247101] [<c11dcd39>] ?
pci_device_probe+0xa8/0xca
Jun 30 08:35:08 laptop kernel: [ 5.247115] [<c126a75a>] ?
driver_probe_device+0xd3/0x225
Jun 30 08:35:08 laptop kernel: [ 5.247128] [<c126a8f8>] ?
__driver_attach+0x4c/0x68
Jun 30 08:35:08 laptop kernel: [ 5.247141] [<c1269260>] ?
bus_for_each_dev+0x41/0x6b
Jun 30 08:35:08 laptop kernel: [ 5.247155] [<c126a26c>] ?
driver_attach+0x19/0x1b
Jun 30 08:35:08 laptop kernel: [ 5.247166] [<c126a8ac>] ?
driver_probe_device+0x225/0x225
Jun 30 08:35:08 laptop kernel: [ 5.247176] [<c126a027>] ?
bus_add_driver+0xcf/0x192
Jun 30 08:35:08 laptop kernel: [ 5.247184] [<c126ae69>] ?
driver_register+0x73/0xa5
Jun 30 08:35:08 laptop kernel: [ 5.247193] [<f85ee000>] ? 0xf85edfff
Jun 30 08:35:08 laptop kernel: [ 5.247200] [<c100045e>] ?
do_one_initcall+0xe0/0x17a
Jun 30 08:35:08 laptop kernel: [ 5.247209] [<c10fadf8>] ?
__cache_free+0x369/0x371
Jun 30 08:35:08 laptop kernel: [ 5.247216] [<c10fadf8>] ?
__cache_free+0x369/0x371
Jun 30 08:35:08 laptop kernel: [ 5.247223] [<c1088e4d>] ?
load_module+0x11a5/0x14b6
Jun 30 08:35:08 laptop kernel: [ 5.247230] [<c1088e4d>] ?
load_module+0x11a5/0x14b6
Jun 30 08:35:08 laptop kernel: [ 5.247238] [<c1088e90>] ?
load_module+0x11e8/0x14b6
Jun 30 08:35:08 laptop kernel: [ 5.247248] [<c10891e4>] ?
SyS_init_module+0x86/0x9e
Jun 30 08:35:08 laptop kernel: [ 5.247263] [<c135d64f>] ?
sysenter_do_call+0x12/0x16
Jun 30 08:35:08 laptop kernel: [ 5.247269] Code: e4 00 00 00 00 e8 b8
f9 ff ff 83 c4 0c 8d 65 f4 5b 5e 5f 5d c3 55 89 e5 66 66 66 66 90 31 d2
e8 5e fe ff ff 31 c0 5d c3 90 90 55 <2b> 80 8c 03 00 00 89 e5 3d 80 07
00 00 74 14 3d 40 0b 00 00 74
Jun 30 08:35:08 laptop kernel: [ 5.247337] EIP: [<c10325d9>]
is_highmem+0x1/0x2b SS:ESP 0068:f3e89c04
Jun 30 08:35:08 laptop kernel: [ 5.247354] CR2: 000000000000074c
Jun 30 08:35:08 laptop kernel: [ 5.247364] ---[ end trace
f6bf47010230a3ea ]---
Jun 30 08:35:08 laptop kernel: [ 5.249053] device: 'hwmon0': device_add

2014-06-30 08:18:56

by Zhang, Rui

[permalink] [raw]
Subject: Re: [BUG] rc3 Oops: unable to handle kernel NULL pointer dereference at 0000074c

On Mon, 2014-06-30 at 09:52 +0200, Martin Kepplinger wrote:
> I now booted 3.16-rc3 and suddenly see an oops during boot:
>
> the oops during boot: http://tny.cz/2301e393
> also below
>
> lshw if interesting: http://tny.cz/3c9a7609
>
> the full boot log: http://tny.cz/88260b19
>
> does anyone have an idea?

what if you rebuild the kernel with CONFIG_SENSORS_CORETEMP=n?

thanks,
rui
> thanks
>
> the oops:
>
> Jun 30 08:35:08 laptop kernel: [ 5.245811] bus: 'platform':
> really_probe: probing driver coretemp with device coretemp.0
> Jun 30 08:35:08 laptop kernel: [ 5.246134] BUG: unable to handle
> kernel NULL pointer dereference at 0000074c
> Jun 30 08:35:08 laptop kernel: [ 5.246145] IP: [<c10325d9>]
> is_highmem+0x1/0x2b
> Jun 30 08:35:08 laptop kernel: [ 5.246158] *pdpt = 0000000033e49001
> *pde = 0000000000000000
> Jun 30 08:35:08 laptop kernel: [ 5.246167] Oops: 0000 [#1] SMP
> Jun 30 08:35:08 laptop kernel: [ 5.246175] Modules linked in:
> coretemp(+) kvm_intel kvm snd_hda_codec_hdmi snd_hda_codec_realtek
> snd_hda_codec_generic microcode snd_hda_intel i915(+) snd_hda_controller
> evdev psmouse snd_hda_codec serio_raw snd_hwdep snd_pcm iwlwifi i2c_i801
> lpc_ich mfd_core snd_seq drm_kms_helper snd_timer battery ehci_pci
> snd_seq_device drm cfg80211 ehci_hcd snd i2c_algo_bit ac video i2c_core
> rfkill soundcore wmi acpi_cpufreq button processor thermal_sys ext4
> crc16 jbd2 mbcache sg sd_mod crct10dif_generic crc_t10dif
> crct10dif_common ahci libahci crc32c_intel tg3 ptp libata pps_core
> sdhci_pci sdhci scsi_mod mmc_core libphy xhci_hcd usbcore usb_common
> Jun 30 08:35:08 laptop kernel: [ 5.246320] CPU: 1 PID: 491 Comm:
> modprobe Not tainted 3.16.0-rc3 #83
> Jun 30 08:35:08 laptop kernel: [ 5.246330] Hardware name: Acer
> TravelMate B113/BA10_HX , BIOS V1.09 10/30/2012
> Jun 30 08:35:08 laptop kernel: [ 5.246344] task: f3828a90 ti:
> f3e88000 task.ti: f3e88000
> Jun 30 08:35:08 laptop kernel: [ 5.246355] EIP: 0060:[<c10325d9>]
> EFLAGS: 00010206 CPU: 1
> Jun 30 08:35:08 laptop kernel: [ 5.246367] EIP is at is_highmem+0x1/0x2b
> Jun 30 08:35:08 laptop kernel: [ 5.246376] EAX: 000003c0 EBX:
> ffb76000 ECX: 00000001 EDX: 000003c0
> Jun 30 08:35:08 laptop kernel: [ 5.246386] ESI: f86cd279 EDI:
> 00000000 EBP: f3e89c10 ESP: f3e89c04
> Jun 30 08:35:08 laptop kernel: [ 5.246396] DS: 007b ES: 007b FS:
> 00d8 GS: 00e0 SS: 0068
> Jun 30 08:35:08 laptop kernel: [ 5.246405] CR0: 80050033 CR2:
> 0000074c CR3: 2e3fc000 CR4: 000407f0
> Jun 30 08:35:08 laptop kernel: [ 5.246414] Stack:
> Jun 30 08:35:08 laptop kernel: [ 5.246421] f3e89c10 c1032889
> f3cbcc60 f3e89c4c f86b52bf 00000005 00000000 00000448
> Jun 30 08:35:08 laptop kernel: [ 5.246442] f3e89c30 00000006
> 00165000 ffb76000 00000113 f870f010 ee881128 ee881128
> Jun 30 08:35:08 laptop kernel: [ 5.246465] 00000001 f418b980
> f3e89c74 f86b4e5c 00000000 f3911e00 f3911e00 ee881128
> Jun 30 08:35:08 laptop kernel: [ 5.246487] Call Trace:
> Jun 30 08:35:08 laptop kernel: [ 5.246500] [<c1032889>] ?
> kunmap+0x3b/0x4e
> Jun 30 08:35:08 laptop kernel: [ 5.246578] [<f86b52bf>] ?
> i915_gem_render_state_init+0x24f/0x28c [i915]
> Jun 30 08:35:08 laptop kernel: [ 5.246634] [<f86b4e5c>] ?
> i915_switch_context+0x348/0x387 [i915]
> Jun 30 08:35:08 laptop kernel: [ 5.246684] [<f86b4f0f>] ?
> i915_gem_context_enable+0x74/0x7c [i915]
> Jun 30 08:35:08 laptop kernel: [ 5.246742] [<f86bcd38>] ?
> i915_gem_init_hw+0x23e/0x285 [i915]
> Jun 30 08:35:08 laptop kernel: [ 5.246818] [<f86bce7e>] ?
> i915_gem_init+0xff/0x179 [i915]
> Jun 30 08:35:08 laptop kernel: [ 5.246924] [<f87047d9>] ?
> i915_driver_load+0x989/0xc1d [i915]
> Jun 30 08:35:08 laptop kernel: [ 5.246940] [<c1267429>] ?
> get_device+0x14/0x1d
> Jun 30 08:35:08 laptop kernel: [ 5.246955] [<c1268832>] ?
> device_add+0x3b7/0x4a9
> Jun 30 08:35:08 laptop kernel: [ 5.246996] [<f8619c80>] ?
> drm_minor_register+0x104/0x15c [drm]
> Jun 30 08:35:08 laptop kernel: [ 5.247033] [<f8619d44>] ?
> drm_dev_register+0x6c/0xce [drm]
> Jun 30 08:35:08 laptop kernel: [ 5.247072] [<f861bbb4>] ?
> drm_get_pci_dev+0xde/0x174 [drm]
> Jun 30 08:35:08 laptop kernel: [ 5.247088] [<c11dcc58>] ?
> local_pci_probe+0x33/0x6c
> Jun 30 08:35:08 laptop kernel: [ 5.247101] [<c11dcd39>] ?
> pci_device_probe+0xa8/0xca
> Jun 30 08:35:08 laptop kernel: [ 5.247115] [<c126a75a>] ?
> driver_probe_device+0xd3/0x225
> Jun 30 08:35:08 laptop kernel: [ 5.247128] [<c126a8f8>] ?
> __driver_attach+0x4c/0x68
> Jun 30 08:35:08 laptop kernel: [ 5.247141] [<c1269260>] ?
> bus_for_each_dev+0x41/0x6b
> Jun 30 08:35:08 laptop kernel: [ 5.247155] [<c126a26c>] ?
> driver_attach+0x19/0x1b
> Jun 30 08:35:08 laptop kernel: [ 5.247166] [<c126a8ac>] ?
> driver_probe_device+0x225/0x225
> Jun 30 08:35:08 laptop kernel: [ 5.247176] [<c126a027>] ?
> bus_add_driver+0xcf/0x192
> Jun 30 08:35:08 laptop kernel: [ 5.247184] [<c126ae69>] ?
> driver_register+0x73/0xa5
> Jun 30 08:35:08 laptop kernel: [ 5.247193] [<f85ee000>] ? 0xf85edfff
> Jun 30 08:35:08 laptop kernel: [ 5.247200] [<c100045e>] ?
> do_one_initcall+0xe0/0x17a
> Jun 30 08:35:08 laptop kernel: [ 5.247209] [<c10fadf8>] ?
> __cache_free+0x369/0x371
> Jun 30 08:35:08 laptop kernel: [ 5.247216] [<c10fadf8>] ?
> __cache_free+0x369/0x371
> Jun 30 08:35:08 laptop kernel: [ 5.247223] [<c1088e4d>] ?
> load_module+0x11a5/0x14b6
> Jun 30 08:35:08 laptop kernel: [ 5.247230] [<c1088e4d>] ?
> load_module+0x11a5/0x14b6
> Jun 30 08:35:08 laptop kernel: [ 5.247238] [<c1088e90>] ?
> load_module+0x11e8/0x14b6
> Jun 30 08:35:08 laptop kernel: [ 5.247248] [<c10891e4>] ?
> SyS_init_module+0x86/0x9e
> Jun 30 08:35:08 laptop kernel: [ 5.247263] [<c135d64f>] ?
> sysenter_do_call+0x12/0x16
> Jun 30 08:35:08 laptop kernel: [ 5.247269] Code: e4 00 00 00 00 e8 b8
> f9 ff ff 83 c4 0c 8d 65 f4 5b 5e 5f 5d c3 55 89 e5 66 66 66 66 90 31 d2
> e8 5e fe ff ff 31 c0 5d c3 90 90 55 <2b> 80 8c 03 00 00 89 e5 3d 80 07
> 00 00 74 14 3d 40 0b 00 00 74
> Jun 30 08:35:08 laptop kernel: [ 5.247337] EIP: [<c10325d9>]
> is_highmem+0x1/0x2b SS:ESP 0068:f3e89c04
> Jun 30 08:35:08 laptop kernel: [ 5.247354] CR2: 000000000000074c
> Jun 30 08:35:08 laptop kernel: [ 5.247364] ---[ end trace
> f6bf47010230a3ea ]---
> Jun 30 08:35:08 laptop kernel: [ 5.249053] device: 'hwmon0': device_add

2014-06-30 08:20:52

by Zhang, Rui

[permalink] [raw]
Subject: Re: [BUG] rc3 Oops: unable to handle kernel NULL pointer dereference at 0000074c

On Mon, 2014-06-30 at 16:18 +0800, Zhang Rui wrote:
> On Mon, 2014-06-30 at 09:52 +0200, Martin Kepplinger wrote:
> > I now booted 3.16-rc3 and suddenly see an oops during boot:
> >
> > the oops during boot: http://tny.cz/2301e393
> > also below
> >
> > lshw if interesting: http://tny.cz/3c9a7609
> >
> > the full boot log: http://tny.cz/88260b19
> >
> > does anyone have an idea?
>
> what if you rebuild the kernel with CONFIG_SENSORS_CORETEMP=n?
>
BTW, can this be 100% reproduced on a rc3 kernel?

thanks,
rui
> thanks,
> rui
> > thanks
> >
> > the oops:
> >
> > Jun 30 08:35:08 laptop kernel: [ 5.245811] bus: 'platform':
> > really_probe: probing driver coretemp with device coretemp.0
> > Jun 30 08:35:08 laptop kernel: [ 5.246134] BUG: unable to handle
> > kernel NULL pointer dereference at 0000074c
> > Jun 30 08:35:08 laptop kernel: [ 5.246145] IP: [<c10325d9>]
> > is_highmem+0x1/0x2b
> > Jun 30 08:35:08 laptop kernel: [ 5.246158] *pdpt = 0000000033e49001
> > *pde = 0000000000000000
> > Jun 30 08:35:08 laptop kernel: [ 5.246167] Oops: 0000 [#1] SMP
> > Jun 30 08:35:08 laptop kernel: [ 5.246175] Modules linked in:
> > coretemp(+) kvm_intel kvm snd_hda_codec_hdmi snd_hda_codec_realtek
> > snd_hda_codec_generic microcode snd_hda_intel i915(+) snd_hda_controller
> > evdev psmouse snd_hda_codec serio_raw snd_hwdep snd_pcm iwlwifi i2c_i801
> > lpc_ich mfd_core snd_seq drm_kms_helper snd_timer battery ehci_pci
> > snd_seq_device drm cfg80211 ehci_hcd snd i2c_algo_bit ac video i2c_core
> > rfkill soundcore wmi acpi_cpufreq button processor thermal_sys ext4
> > crc16 jbd2 mbcache sg sd_mod crct10dif_generic crc_t10dif
> > crct10dif_common ahci libahci crc32c_intel tg3 ptp libata pps_core
> > sdhci_pci sdhci scsi_mod mmc_core libphy xhci_hcd usbcore usb_common
> > Jun 30 08:35:08 laptop kernel: [ 5.246320] CPU: 1 PID: 491 Comm:
> > modprobe Not tainted 3.16.0-rc3 #83
> > Jun 30 08:35:08 laptop kernel: [ 5.246330] Hardware name: Acer
> > TravelMate B113/BA10_HX , BIOS V1.09 10/30/2012
> > Jun 30 08:35:08 laptop kernel: [ 5.246344] task: f3828a90 ti:
> > f3e88000 task.ti: f3e88000
> > Jun 30 08:35:08 laptop kernel: [ 5.246355] EIP: 0060:[<c10325d9>]
> > EFLAGS: 00010206 CPU: 1
> > Jun 30 08:35:08 laptop kernel: [ 5.246367] EIP is at is_highmem+0x1/0x2b
> > Jun 30 08:35:08 laptop kernel: [ 5.246376] EAX: 000003c0 EBX:
> > ffb76000 ECX: 00000001 EDX: 000003c0
> > Jun 30 08:35:08 laptop kernel: [ 5.246386] ESI: f86cd279 EDI:
> > 00000000 EBP: f3e89c10 ESP: f3e89c04
> > Jun 30 08:35:08 laptop kernel: [ 5.246396] DS: 007b ES: 007b FS:
> > 00d8 GS: 00e0 SS: 0068
> > Jun 30 08:35:08 laptop kernel: [ 5.246405] CR0: 80050033 CR2:
> > 0000074c CR3: 2e3fc000 CR4: 000407f0
> > Jun 30 08:35:08 laptop kernel: [ 5.246414] Stack:
> > Jun 30 08:35:08 laptop kernel: [ 5.246421] f3e89c10 c1032889
> > f3cbcc60 f3e89c4c f86b52bf 00000005 00000000 00000448
> > Jun 30 08:35:08 laptop kernel: [ 5.246442] f3e89c30 00000006
> > 00165000 ffb76000 00000113 f870f010 ee881128 ee881128
> > Jun 30 08:35:08 laptop kernel: [ 5.246465] 00000001 f418b980
> > f3e89c74 f86b4e5c 00000000 f3911e00 f3911e00 ee881128
> > Jun 30 08:35:08 laptop kernel: [ 5.246487] Call Trace:
> > Jun 30 08:35:08 laptop kernel: [ 5.246500] [<c1032889>] ?
> > kunmap+0x3b/0x4e
> > Jun 30 08:35:08 laptop kernel: [ 5.246578] [<f86b52bf>] ?
> > i915_gem_render_state_init+0x24f/0x28c [i915]
> > Jun 30 08:35:08 laptop kernel: [ 5.246634] [<f86b4e5c>] ?
> > i915_switch_context+0x348/0x387 [i915]
> > Jun 30 08:35:08 laptop kernel: [ 5.246684] [<f86b4f0f>] ?
> > i915_gem_context_enable+0x74/0x7c [i915]
> > Jun 30 08:35:08 laptop kernel: [ 5.246742] [<f86bcd38>] ?
> > i915_gem_init_hw+0x23e/0x285 [i915]
> > Jun 30 08:35:08 laptop kernel: [ 5.246818] [<f86bce7e>] ?
> > i915_gem_init+0xff/0x179 [i915]
> > Jun 30 08:35:08 laptop kernel: [ 5.246924] [<f87047d9>] ?
> > i915_driver_load+0x989/0xc1d [i915]
> > Jun 30 08:35:08 laptop kernel: [ 5.246940] [<c1267429>] ?
> > get_device+0x14/0x1d
> > Jun 30 08:35:08 laptop kernel: [ 5.246955] [<c1268832>] ?
> > device_add+0x3b7/0x4a9
> > Jun 30 08:35:08 laptop kernel: [ 5.246996] [<f8619c80>] ?
> > drm_minor_register+0x104/0x15c [drm]
> > Jun 30 08:35:08 laptop kernel: [ 5.247033] [<f8619d44>] ?
> > drm_dev_register+0x6c/0xce [drm]
> > Jun 30 08:35:08 laptop kernel: [ 5.247072] [<f861bbb4>] ?
> > drm_get_pci_dev+0xde/0x174 [drm]
> > Jun 30 08:35:08 laptop kernel: [ 5.247088] [<c11dcc58>] ?
> > local_pci_probe+0x33/0x6c
> > Jun 30 08:35:08 laptop kernel: [ 5.247101] [<c11dcd39>] ?
> > pci_device_probe+0xa8/0xca
> > Jun 30 08:35:08 laptop kernel: [ 5.247115] [<c126a75a>] ?
> > driver_probe_device+0xd3/0x225
> > Jun 30 08:35:08 laptop kernel: [ 5.247128] [<c126a8f8>] ?
> > __driver_attach+0x4c/0x68
> > Jun 30 08:35:08 laptop kernel: [ 5.247141] [<c1269260>] ?
> > bus_for_each_dev+0x41/0x6b
> > Jun 30 08:35:08 laptop kernel: [ 5.247155] [<c126a26c>] ?
> > driver_attach+0x19/0x1b
> > Jun 30 08:35:08 laptop kernel: [ 5.247166] [<c126a8ac>] ?
> > driver_probe_device+0x225/0x225
> > Jun 30 08:35:08 laptop kernel: [ 5.247176] [<c126a027>] ?
> > bus_add_driver+0xcf/0x192
> > Jun 30 08:35:08 laptop kernel: [ 5.247184] [<c126ae69>] ?
> > driver_register+0x73/0xa5
> > Jun 30 08:35:08 laptop kernel: [ 5.247193] [<f85ee000>] ? 0xf85edfff
> > Jun 30 08:35:08 laptop kernel: [ 5.247200] [<c100045e>] ?
> > do_one_initcall+0xe0/0x17a
> > Jun 30 08:35:08 laptop kernel: [ 5.247209] [<c10fadf8>] ?
> > __cache_free+0x369/0x371
> > Jun 30 08:35:08 laptop kernel: [ 5.247216] [<c10fadf8>] ?
> > __cache_free+0x369/0x371
> > Jun 30 08:35:08 laptop kernel: [ 5.247223] [<c1088e4d>] ?
> > load_module+0x11a5/0x14b6
> > Jun 30 08:35:08 laptop kernel: [ 5.247230] [<c1088e4d>] ?
> > load_module+0x11a5/0x14b6
> > Jun 30 08:35:08 laptop kernel: [ 5.247238] [<c1088e90>] ?
> > load_module+0x11e8/0x14b6
> > Jun 30 08:35:08 laptop kernel: [ 5.247248] [<c10891e4>] ?
> > SyS_init_module+0x86/0x9e
> > Jun 30 08:35:08 laptop kernel: [ 5.247263] [<c135d64f>] ?
> > sysenter_do_call+0x12/0x16
> > Jun 30 08:35:08 laptop kernel: [ 5.247269] Code: e4 00 00 00 00 e8 b8
> > f9 ff ff 83 c4 0c 8d 65 f4 5b 5e 5f 5d c3 55 89 e5 66 66 66 66 90 31 d2
> > e8 5e fe ff ff 31 c0 5d c3 90 90 55 <2b> 80 8c 03 00 00 89 e5 3d 80 07
> > 00 00 74 14 3d 40 0b 00 00 74
> > Jun 30 08:35:08 laptop kernel: [ 5.247337] EIP: [<c10325d9>]
> > is_highmem+0x1/0x2b SS:ESP 0068:f3e89c04
> > Jun 30 08:35:08 laptop kernel: [ 5.247354] CR2: 000000000000074c
> > Jun 30 08:35:08 laptop kernel: [ 5.247364] ---[ end trace
> > f6bf47010230a3ea ]---
> > Jun 30 08:35:08 laptop kernel: [ 5.249053] device: 'hwmon0': device_add
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html

2014-06-30 09:01:14

by Martin Kepplinger

[permalink] [raw]
Subject: Re: [BUG] rc3 Oops: unable to handle kernel NULL pointer dereference at 0000074c

Am 2014-06-30 10:20, schrieb Zhang Rui:
> On Mon, 2014-06-30 at 16:18 +0800, Zhang Rui wrote:
>> On Mon, 2014-06-30 at 09:52 +0200, Martin Kepplinger wrote:
>>> I now booted 3.16-rc3 and suddenly see an oops during boot:
>>>
>>> the oops during boot: http://tny.cz/2301e393
>>> also below
>>>
>>> lshw if interesting: http://tny.cz/3c9a7609
>>>
>>> the full boot log: http://tny.cz/88260b19
>>>
>>> does anyone have an idea?
>>
>> what if you rebuild the kernel with CONFIG_SENSORS_CORETEMP=n?
>>
> BTW, can this be 100% reproduced on a rc3 kernel?

no I can't -.- Booted again a few times, no oops now. just the black
screen as 'usual' for 3.16.

>
> thanks,
> rui
>> thanks,
>> rui
>>> thanks
>>>
>>> the oops:
>>>
>>> Jun 30 08:35:08 laptop kernel: [ 5.245811] bus: 'platform':
>>> really_probe: probing driver coretemp with device coretemp.0
>>> Jun 30 08:35:08 laptop kernel: [ 5.246134] BUG: unable to handle
>>> kernel NULL pointer dereference at 0000074c
>>> Jun 30 08:35:08 laptop kernel: [ 5.246145] IP: [<c10325d9>]
>>> is_highmem+0x1/0x2b
>>> Jun 30 08:35:08 laptop kernel: [ 5.246158] *pdpt = 0000000033e49001
>>> *pde = 0000000000000000
>>> Jun 30 08:35:08 laptop kernel: [ 5.246167] Oops: 0000 [#1] SMP
>>> Jun 30 08:35:08 laptop kernel: [ 5.246175] Modules linked in:
>>> coretemp(+) kvm_intel kvm snd_hda_codec_hdmi snd_hda_codec_realtek
>>> snd_hda_codec_generic microcode snd_hda_intel i915(+) snd_hda_controller
>>> evdev psmouse snd_hda_codec serio_raw snd_hwdep snd_pcm iwlwifi i2c_i801
>>> lpc_ich mfd_core snd_seq drm_kms_helper snd_timer battery ehci_pci
>>> snd_seq_device drm cfg80211 ehci_hcd snd i2c_algo_bit ac video i2c_core
>>> rfkill soundcore wmi acpi_cpufreq button processor thermal_sys ext4
>>> crc16 jbd2 mbcache sg sd_mod crct10dif_generic crc_t10dif
>>> crct10dif_common ahci libahci crc32c_intel tg3 ptp libata pps_core
>>> sdhci_pci sdhci scsi_mod mmc_core libphy xhci_hcd usbcore usb_common
>>> Jun 30 08:35:08 laptop kernel: [ 5.246320] CPU: 1 PID: 491 Comm:
>>> modprobe Not tainted 3.16.0-rc3 #83
>>> Jun 30 08:35:08 laptop kernel: [ 5.246330] Hardware name: Acer
>>> TravelMate B113/BA10_HX , BIOS V1.09 10/30/2012
>>> Jun 30 08:35:08 laptop kernel: [ 5.246344] task: f3828a90 ti:
>>> f3e88000 task.ti: f3e88000
>>> Jun 30 08:35:08 laptop kernel: [ 5.246355] EIP: 0060:[<c10325d9>]
>>> EFLAGS: 00010206 CPU: 1
>>> Jun 30 08:35:08 laptop kernel: [ 5.246367] EIP is at is_highmem+0x1/0x2b
>>> Jun 30 08:35:08 laptop kernel: [ 5.246376] EAX: 000003c0 EBX:
>>> ffb76000 ECX: 00000001 EDX: 000003c0
>>> Jun 30 08:35:08 laptop kernel: [ 5.246386] ESI: f86cd279 EDI:
>>> 00000000 EBP: f3e89c10 ESP: f3e89c04
>>> Jun 30 08:35:08 laptop kernel: [ 5.246396] DS: 007b ES: 007b FS:
>>> 00d8 GS: 00e0 SS: 0068
>>> Jun 30 08:35:08 laptop kernel: [ 5.246405] CR0: 80050033 CR2:
>>> 0000074c CR3: 2e3fc000 CR4: 000407f0
>>> Jun 30 08:35:08 laptop kernel: [ 5.246414] Stack:
>>> Jun 30 08:35:08 laptop kernel: [ 5.246421] f3e89c10 c1032889
>>> f3cbcc60 f3e89c4c f86b52bf 00000005 00000000 00000448
>>> Jun 30 08:35:08 laptop kernel: [ 5.246442] f3e89c30 00000006
>>> 00165000 ffb76000 00000113 f870f010 ee881128 ee881128
>>> Jun 30 08:35:08 laptop kernel: [ 5.246465] 00000001 f418b980
>>> f3e89c74 f86b4e5c 00000000 f3911e00 f3911e00 ee881128
>>> Jun 30 08:35:08 laptop kernel: [ 5.246487] Call Trace:
>>> Jun 30 08:35:08 laptop kernel: [ 5.246500] [<c1032889>] ?
>>> kunmap+0x3b/0x4e
>>> Jun 30 08:35:08 laptop kernel: [ 5.246578] [<f86b52bf>] ?
>>> i915_gem_render_state_init+0x24f/0x28c [i915]
>>> Jun 30 08:35:08 laptop kernel: [ 5.246634] [<f86b4e5c>] ?
>>> i915_switch_context+0x348/0x387 [i915]
>>> Jun 30 08:35:08 laptop kernel: [ 5.246684] [<f86b4f0f>] ?
>>> i915_gem_context_enable+0x74/0x7c [i915]
>>> Jun 30 08:35:08 laptop kernel: [ 5.246742] [<f86bcd38>] ?
>>> i915_gem_init_hw+0x23e/0x285 [i915]
>>> Jun 30 08:35:08 laptop kernel: [ 5.246818] [<f86bce7e>] ?
>>> i915_gem_init+0xff/0x179 [i915]
>>> Jun 30 08:35:08 laptop kernel: [ 5.246924] [<f87047d9>] ?
>>> i915_driver_load+0x989/0xc1d [i915]
>>> Jun 30 08:35:08 laptop kernel: [ 5.246940] [<c1267429>] ?
>>> get_device+0x14/0x1d
>>> Jun 30 08:35:08 laptop kernel: [ 5.246955] [<c1268832>] ?
>>> device_add+0x3b7/0x4a9
>>> Jun 30 08:35:08 laptop kernel: [ 5.246996] [<f8619c80>] ?
>>> drm_minor_register+0x104/0x15c [drm]
>>> Jun 30 08:35:08 laptop kernel: [ 5.247033] [<f8619d44>] ?
>>> drm_dev_register+0x6c/0xce [drm]
>>> Jun 30 08:35:08 laptop kernel: [ 5.247072] [<f861bbb4>] ?
>>> drm_get_pci_dev+0xde/0x174 [drm]
>>> Jun 30 08:35:08 laptop kernel: [ 5.247088] [<c11dcc58>] ?
>>> local_pci_probe+0x33/0x6c
>>> Jun 30 08:35:08 laptop kernel: [ 5.247101] [<c11dcd39>] ?
>>> pci_device_probe+0xa8/0xca
>>> Jun 30 08:35:08 laptop kernel: [ 5.247115] [<c126a75a>] ?
>>> driver_probe_device+0xd3/0x225
>>> Jun 30 08:35:08 laptop kernel: [ 5.247128] [<c126a8f8>] ?
>>> __driver_attach+0x4c/0x68
>>> Jun 30 08:35:08 laptop kernel: [ 5.247141] [<c1269260>] ?
>>> bus_for_each_dev+0x41/0x6b
>>> Jun 30 08:35:08 laptop kernel: [ 5.247155] [<c126a26c>] ?
>>> driver_attach+0x19/0x1b
>>> Jun 30 08:35:08 laptop kernel: [ 5.247166] [<c126a8ac>] ?
>>> driver_probe_device+0x225/0x225
>>> Jun 30 08:35:08 laptop kernel: [ 5.247176] [<c126a027>] ?
>>> bus_add_driver+0xcf/0x192
>>> Jun 30 08:35:08 laptop kernel: [ 5.247184] [<c126ae69>] ?
>>> driver_register+0x73/0xa5
>>> Jun 30 08:35:08 laptop kernel: [ 5.247193] [<f85ee000>] ? 0xf85edfff
>>> Jun 30 08:35:08 laptop kernel: [ 5.247200] [<c100045e>] ?
>>> do_one_initcall+0xe0/0x17a
>>> Jun 30 08:35:08 laptop kernel: [ 5.247209] [<c10fadf8>] ?
>>> __cache_free+0x369/0x371
>>> Jun 30 08:35:08 laptop kernel: [ 5.247216] [<c10fadf8>] ?
>>> __cache_free+0x369/0x371
>>> Jun 30 08:35:08 laptop kernel: [ 5.247223] [<c1088e4d>] ?
>>> load_module+0x11a5/0x14b6
>>> Jun 30 08:35:08 laptop kernel: [ 5.247230] [<c1088e4d>] ?
>>> load_module+0x11a5/0x14b6
>>> Jun 30 08:35:08 laptop kernel: [ 5.247238] [<c1088e90>] ?
>>> load_module+0x11e8/0x14b6
>>> Jun 30 08:35:08 laptop kernel: [ 5.247248] [<c10891e4>] ?
>>> SyS_init_module+0x86/0x9e
>>> Jun 30 08:35:08 laptop kernel: [ 5.247263] [<c135d64f>] ?
>>> sysenter_do_call+0x12/0x16
>>> Jun 30 08:35:08 laptop kernel: [ 5.247269] Code: e4 00 00 00 00 e8 b8
>>> f9 ff ff 83 c4 0c 8d 65 f4 5b 5e 5f 5d c3 55 89 e5 66 66 66 66 90 31 d2
>>> e8 5e fe ff ff 31 c0 5d c3 90 90 55 <2b> 80 8c 03 00 00 89 e5 3d 80 07
>>> 00 00 74 14 3d 40 0b 00 00 74
>>> Jun 30 08:35:08 laptop kernel: [ 5.247337] EIP: [<c10325d9>]
>>> is_highmem+0x1/0x2b SS:ESP 0068:f3e89c04
>>> Jun 30 08:35:08 laptop kernel: [ 5.247354] CR2: 000000000000074c
>>> Jun 30 08:35:08 laptop kernel: [ 5.247364] ---[ end trace
>>> f6bf47010230a3ea ]---
>>> Jun 30 08:35:08 laptop kernel: [ 5.249053] device: 'hwmon0': device_add
>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
>> the body of a message to [email protected]
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>

2014-06-30 10:39:51

by Martin Kepplinger

[permalink] [raw]
Subject: Re: [BUG] rc1 rc2 rc3 not bootable - black screen after kernel loading

back to aaeb2554337217dfa4eac2fcc90da7be540b9a73 as the first bad
commit. why is this not revertable exactly? how can I show a complete
list of commits this merge introduces?

2014-07-24 16:19:43

by Martin Kepplinger

[permalink] [raw]
Subject: Re: [BUG] rc1 rc2 rc3 not bootable - black screen after kernel loading

Am 2014-06-30 12:39, schrieb Martin Kepplinger:
> back to aaeb2554337217dfa4eac2fcc90da7be540b9a73 as the first bad
> commit. why is this not revertable exactly? how can I show a complete
> list of commits this merge introduces?
>

It seems that _nobody_ is running a simple 32 bit i915 (acer) laptop.
rc6 is still unusable. Black screen directly after kernel-loading. no
change since rc1.

Seems like I won't be able to use 3.16. I'm happy to test patches and am
happy for any advice what to do, when time permits.

martin

2014-07-24 22:25:29

by Woody Suwalski

[permalink] [raw]
Subject: Re: [BUG] rc1 rc2 rc3 not bootable - black screen after kernel loading

Martin Kepplinger wrote:
> Am 2014-06-30 12:39, schrieb Martin Kepplinger:
>> back to aaeb2554337217dfa4eac2fcc90da7be540b9a73 as the first bad
>> commit. why is this not revertable exactly? how can I show a complete
>> list of commits this merge introduces?
>>
> It seems that _nobody_ is running a simple 32 bit i915 (acer) laptop.
> rc6 is still unusable. Black screen directly after kernel-loading. no
> change since rc1.
>
> Seems like I won't be able to use 3.16. I'm happy to test patches and am
> happy for any advice what to do, when time permits.
>
> martin
>
Martin, I am running happily a 32-bit kernel 3.16-rc*all on i915 (Asus
EeePC)
However: from your postings I still have no idea what Intel video
chipset is in your Acer.
Try to add "nomodeset=y" to your kernel's cmdline to verify that it can
boot. You have many kobject messages which are hiding what is
happening... And please submit at least full dmesg output and "lspci
-nn" ;-)

Woody

2014-07-24 23:22:18

by Hugh Dickins

[permalink] [raw]
Subject: Re: [BUG] rc1 rc2 rc3 not bootable - black screen after kernel loading

On Thu, 24 Jul 2014, Martin Kepplinger wrote:
> Am 2014-06-30 12:39, schrieb Martin Kepplinger:
> > back to aaeb2554337217dfa4eac2fcc90da7be540b9a73 as the first bad
> > commit. why is this not revertable exactly? how can I show a complete
> > list of commits this merge introduces?
> >
>
> It seems that _nobody_ is running a simple 32 bit i915 (acer) laptop.
> rc6 is still unusable. Black screen directly after kernel-loading. no
> change since rc1.
>
> Seems like I won't be able to use 3.16. I'm happy to test patches and am
> happy for any advice what to do, when time permits.

Martin, I know nothing about aaeb25543372 and why it should be relevant,
but if you're having rc1..rc6 32-bit i915 black screens, please try this
patch that Daniel Vetter put in his fixes queue on Monday, which I'm
hoping will reach Linus for -rc7.

Hugh

[PATCH] drm/i915: fix freeze with blank screen booting highmem

x86_64 boots and displays fine, but booting x86_32 with CONFIG_HIGHMEM
has frozen with a blank screen throughout 3.16-rc on this ThinkPad T420s,
with i915 generation 6 graphics.

Fix 9d0a6fa6c5e6 ("drm/i915: add render state initialization"): kunmap()
takes struct page * argument, not virtual address. Which the compiler
kindly points out, if you use the appropriate u32 *batch, instead of
silencing it with a void *.

Why did bisection lead decisively to nearby 229b0489aa75 ("drm/i915:
add null render states for gen6, gen7 and gen8")? Because the u32
deposited at that virtual address by the previous stub failed the
PageHighMem test, and so caused no harm.

Signed-off-by: Hugh Dickins <[email protected]>
---

drivers/gpu/drm/i915/i915_gem_render_state.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

--- 3.16-rc/drivers/gpu/drm/i915/i915_gem_render_state.c 2014-06-16 00:28:52.384076465 -0700
+++ linux/drivers/gpu/drm/i915/i915_gem_render_state.c 2014-07-21 20:10:03.824481521 -0700
@@ -31,7 +31,7 @@
struct i915_render_state {
struct drm_i915_gem_object *obj;
unsigned long ggtt_offset;
- void *batch;
+ u32 *batch;
u32 size;
u32 len;
};
@@ -80,7 +80,7 @@ free:

static void render_state_free(struct i915_render_state *so)
{
- kunmap(so->batch);
+ kunmap(kmap_to_page(so->batch));
i915_gem_object_ggtt_unpin(so->obj);
drm_gem_object_unreference(&so->obj->base);
kfree(so);

2014-07-25 10:16:36

by Martin Kepplinger

[permalink] [raw]
Subject: Re: [BUG] rc1 rc2 rc3 not bootable - black screen after kernel loading

Am 2014-07-25 01:20, schrieb Hugh Dickins:
> On Thu, 24 Jul 2014, Martin Kepplinger wrote:
>> Am 2014-06-30 12:39, schrieb Martin Kepplinger:
>>> back to aaeb2554337217dfa4eac2fcc90da7be540b9a73 as the first bad
>>> commit. why is this not revertable exactly? how can I show a complete
>>> list of commits this merge introduces?
>>>
>>
>> It seems that _nobody_ is running a simple 32 bit i915 (acer) laptop.
>> rc6 is still unusable. Black screen directly after kernel-loading. no
>> change since rc1.
>>
>> Seems like I won't be able to use 3.16. I'm happy to test patches and am
>> happy for any advice what to do, when time permits.
>
> Martin, I know nothing about aaeb25543372 and why it should be relevant,
> but if you're having rc1..rc6 32-bit i915 black screens, please try this
> patch that Daniel Vetter put in his fixes queue on Monday, which I'm
> hoping will reach Linus for -rc7.
>
> Hugh
>
> [PATCH] drm/i915: fix freeze with blank screen booting highmem
>
> x86_64 boots and displays fine, but booting x86_32 with CONFIG_HIGHMEM
> has frozen with a blank screen throughout 3.16-rc on this ThinkPad T420s,
> with i915 generation 6 graphics.
>
> Fix 9d0a6fa6c5e6 ("drm/i915: add render state initialization"): kunmap()
> takes struct page * argument, not virtual address. Which the compiler
> kindly points out, if you use the appropriate u32 *batch, instead of
> silencing it with a void *.
>
> Why did bisection lead decisively to nearby 229b0489aa75 ("drm/i915:
> add null render states for gen6, gen7 and gen8")? Because the u32
> deposited at that virtual address by the previous stub failed the
> PageHighMem test, and so caused no harm.
>
> Signed-off-by: Hugh Dickins <[email protected]>
> ---
>
> drivers/gpu/drm/i915/i915_gem_render_state.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> --- 3.16-rc/drivers/gpu/drm/i915/i915_gem_render_state.c 2014-06-16 00:28:52.384076465 -0700
> +++ linux/drivers/gpu/drm/i915/i915_gem_render_state.c 2014-07-21 20:10:03.824481521 -0700
> @@ -31,7 +31,7 @@
> struct i915_render_state {
> struct drm_i915_gem_object *obj;
> unsigned long ggtt_offset;
> - void *batch;
> + u32 *batch;
> u32 size;
> u32 len;
> };
> @@ -80,7 +80,7 @@ free:
>
> static void render_state_free(struct i915_render_state *so)
> {
> - kunmap(so->batch);
> + kunmap(kmap_to_page(so->batch));
> i915_gem_object_ggtt_unpin(so->obj);
> drm_gem_object_unreference(&so->obj->base);
> kfree(so);
>

yes! thanks Hugh. On top of linus' current tree, that finally fixes my
problem! I hope it'll be included soon!

martin

p.s. linux-media removed from thread

2014-07-26 23:20:44

by Hugh Dickins

[permalink] [raw]
Subject: Re: [BUG] rc1 rc2 rc3 not bootable - black screen after kernel loading

On Fri, 25 Jul 2014, Martin Kepplinger wrote:
> Am 2014-07-25 01:20, schrieb Hugh Dickins:
> >
> > [PATCH] drm/i915: fix freeze with blank screen booting highmem
>
> yes! thanks Hugh. On top of linus' current tree, that finally fixes my
> problem! I hope it'll be included soon!

I'm glad to hear it, Martin, thanks for letting us know. It is now
commit 88b98287356762cc16c9ff6cd48116160a5d4dba in Linus's tree for rc7.

Hugh