Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #62644 > unrolled thread

Bug#914495: linux-image-4.18.0-3-amd64: does not boot here

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#914495: linux-image-4.18.0-3-amd64: does not boot here TS <debts@xk2c.de> - 2018-12-03 23:20 +0100
    Bug#914495: linux-image-4.18.0-3-amd64: does not boot here Ben Hutchings <ben@decadent.org.uk> - 2018-12-04 01:20 +0100
    Bug#914495: linux-image-4.18.0-3-amd64: does not boot here Bjørn Mork <bjorn@mork.no> - 2018-12-04 09:50 +0100
      Bug#914495: linux-image-4.18.0-3-amd64: does not boot here TS <debts@xk2c.de> - 2018-12-05 06:10 +0100
        Bug#914495: linux-image-4.18.0-3-amd64: does not boot here TS <debts@xk2c.de> - 2018-12-05 07:00 +0100
          Bug#914495: linux-image-4.18.0-3-amd64: does not boot here Norbert Brondeau <norbert.brondeau@free.fr> - 2018-12-06 18:20 +0100
            Bug#914495: linux-image-4.18.0-3-amd64: does not boot here Norbert Brondeau <norbert.brondeau@free.fr> - 2018-12-08 16:50 +0100
              Bug#914495: linux-image-4.18.0-3-amd64: does not boot here Phil <elektron@halo.nu> - 2018-12-08 20:30 +0100
    Bug#914495: linux-image-4.18.0-3-amd64: does not boot here Bjørn Mork <bjorn@mork.no> - 2018-12-06 19:40 +0100

#62644 — Bug#914495: linux-image-4.18.0-3-amd64: does not boot here

Ben Hutchings schrieb/wrote:

-- <snip> --

>> Since the issue happens very early in boot process debugging is quit difficult.
>> Assistance with further debugging is required if you need additional informations.
> 
> You can use a serial console or netconsole to send the kernel log to
> another computer:
> https://www.kernel.org/doc/html/latest/admin-guide/serial-console.html
> https://www.kernel.org/doc/Documentation/networking/netconsole.txt

Will look into that. My current schedule suggests this will not happen before
weekend though.

Just out of curiosity since linux-image-amd64 4.18+100 has been uploaded to
unstable. This issue here seems not to be wide spread, or reproducible?

This computer here is somewhat lucky in finding special bugs. Last time it was
in Zsh. If i had understand Peter correctly some sort of race condition it was
there.

Could be something like that here, too.


kind regards,

     Thilo

[toc] | [next] | [standalone]

#62645

[Multipart message — attachments visible in raw view] — view raw

On Mon, 2018-12-03 at 23:08 +0100, TS wrote:
> Ben Hutchings schrieb/wrote:
> 
> -- <snip> --
> 
> > > Since the issue happens very early in boot process debugging is quit difficult.
> > > Assistance with further debugging is required if you need additional informations.
> > 
> > You can use a serial console or netconsole to send the kernel log to
> > another computer:
> > https://www.kernel.org/doc/html/latest/admin-guide/serial-console.html
> > https://www.kernel.org/doc/Documentation/networking/netconsole.txt
> 
> Will look into that. My current schedule suggests this will not happen before
> weekend though.
> 
> Just out of curiosity since linux-image-amd64 4.18+100 has been uploaded to
> unstable. This issue here seems not to be wide spread, or reproducible?

Hard to tell.  There are a few people that reported the same *symptom*,
but that doesn't mean they found the same bug.

Ben.

> This computer here is somewhat lucky in finding special bugs. Last time it was
> in Zsh. If i had understand Peter correctly some sort of race condition it was
> there.
> 
> Could be something like that here, too.
> 
> 
> kind regards,
> 
>      Thilo
-- 
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
                                                         - Albert Camus

[toc] | [prev] | [next] | [standalone]

#62646

Ben Hutchings <ben@decadent.org.uk> writes:
> On Mon, 2018-12-03 at 23:08 +0100, TS wrote:
>
>> Just out of curiosity since linux-image-amd64 4.18+100 has been uploaded to
>> unstable. This issue here seems not to be wide spread, or reproducible?
>
> Hard to tell.  There are a few people that reported the same *symptom*,
> but that doesn't mean they found the same bug.

True of course.  But in this case there seems to be a very strong
correlation with Gen4 Intel GPUs. I believe every one of the reports
have had at least a lspci dump showing one of those. And a couple of
the reports had stack traces pointing to gen4_render_ring_flush as well.

Given this, there is an extremely suspicious commit added in v4.18.20: 

 06e562e7f515 ("drm/i915/ringbuffer: Delay after EMIT_INVALIDATE for gen4/gen5")

I do have an old laptop with an affected chipset generation, and
verified that it had the same symptoms.  But never got the time to
actually test any further.  Still, I do think that there is good reason
to simply try a revert of that commit.



Bjørn

[toc] | [prev] | [next] | [standalone]

#62652

Bjørn Mork schrieb/wrote:

-- <snip> --

> Given this, there is an extremely suspicious commit added in v4.18.20: 
> 
>  06e562e7f515 ("drm/i915/ringbuffer: Delay after EMIT_INVALIDATE for gen4/gen5")

-- <snip> --

> Still, I do think that there is good reason to simply try a revert of that commit.

In case such a kernel would be available somewhere i happily would test it.
Making such package myself is sadly beyond the limited scope of personal expertise.

For completeness:
% lspci | grep -i vga
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset
Integrated Graphics Controller (rev 07)


kind regards,

     Thilo

[toc] | [prev] | [next] | [standalone]

#62653

TS schrieb/wrote:


-- <snip> --


> For completeness:
> % lspci | grep -i vga
> 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset
> Integrated Graphics Controller (rev 07)

Two machines with:

# unameALL
Linux desk 4.18.0-3-amd64 #1 SMP Debian 4.18.20-2 (2018-11-23) x86_64 GNU/Linux
# lspci | grepE vga
00:02.0 VGA compatible controller: Intel Corporation 82Q35 Express Integrated
Graphics Controller (rev 02)

and

# unameALL
Linux G5000 4.18.0-3-686-pae #1 SMP Debian 4.18.20-2 (2018-11-23) i686 GNU/Linux
# lspci | grepE vga
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS,
943/940GML Express Integrated Graphics Controller (rev 03)

boot just fine.


kind regards,

     Thilo

[toc] | [prev] | [next] | [standalone]

#62669

On Wed, 5 Dec 2018 06:45:58 +0100 TS <debts@xk2c.de> wrote:
> TS schrieb/wrote:
>
>
> -- <snip> --
>
>
> > For completeness:
> > % lspci | grep -i vga
> > 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset
> > Integrated Graphics Controller (rev 07)
>

lspci | grep -i VGA
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 0c)

Don't work !

[toc] | [prev] | [next] | [standalone]

#62686

On Thu, 6 Dec 2018 18:11:11 +0100 Norbert Brondeau <norbert.brondeau@free.fr> wrote:
> >
>
> lspci | grep -i VGA
> 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 0c)
>
> Don't work !


    drm/i915/ringbuffer: Delay after EMIT_INVALIDATE for gen4/gen5
    _UN_commit fb5bbae9b1333d44023713946fdd28db0cd85751 upstream.

Fix this bug.

[toc] | [prev] | [next] | [standalone]

#62688

sumitted upstream bug: https://bugs.freedesktop.org/show_bug.cgi?id=108984

[toc] | [prev] | [next] | [standalone]

#62670

Bjørn Mork <bjorn@mork.no> writes:
> Given this, there is an extremely suspicious commit added in v4.18.20: 
>
>  06e562e7f515 ("drm/i915/ringbuffer: Delay after EMIT_INVALIDATE for gen4/gen5")
>
> I do have an old laptop with an affected chipset generation, and
> verified that it had the same symptoms.  But never got the time to
> actually test any further.  Still, I do think that there is good reason
> to simply try a revert of that commit.

FWIW, I have now verified that reverting commit 06e562e7f515
("drm/i915/ringbuffer: Delay after EMIT_INVALIDATE for gen4/gen5") fixes
this issue for me.



Bjørn

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web