Latest firmware update (intel graphics) destabilize ironlake chipset

classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|

Latest firmware update (intel graphics) destabilize ironlake chipset

Stakanov Schufter
Just to let people know (I do not know if this is worth a bug report as older
hardware is considered "older hardware". Unfortunately it is a perfectly
functional "older hardware"...)
With the 4.x versions of the leap kernel the stability of the system was
admittedly not great (max uptime 1d and a few hours) but still you had a day
to work peacefully. With the firware update time to graphics crash under kde
plasma 5 is from some minutes to maximal 2-3 hours. And that without any
suspend to ram or to disc (that was the issue before).
I did revert to the old firmware and blocked it. However, as long as this is
not intentional.... currently there seems really to be a problem.

Crahses are violent and leave you with a yello stripe on the left side on the
screen. Machine shuts down after ca 20 seconds by itself. Data is lost,
especially email and attachment with akonadi if the crash happens during or
after reception.

So if you run an ironlake chipset be warned.

_________________________________________________________________
________________________________________________________
Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de



--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Latest firmware update (intel graphics) destabilize ironlake chipset

Rainer Fiebig
stakanov wrote:
> Just to let people know (I do not know if this is worth a bug report as older
> hardware is considered "older hardware". Unfortunately it is a perfectly
> functional "older hardware"...)
> With the 4.x versions of the leap kernel the stability of the system was
> admittedly not great (max uptime 1d and a few hours) but still you had a day
> to work peacefully. With the firware update time to graphics crash under kde
> plasma 5 is from some minutes to maximal 2-3 hours. And that without any
> suspend to ram or to disc (that was the issue before).

The i915-driver of 4.4.x doesn't work properly for Ironlake-GPUs - at
least not if you use s2disk/s2both (see
https://bugs.freedesktop.org/show_bug.cgi?id=99737)

Switch to the latest 4.9.x.

So long!

Rainer Fiebig


> I did revert to the old firmware and blocked it. However, as long as this is
> not intentional.... currently there seems really to be a problem.
>
> Crahses are violent and leave you with a yello stripe on the left side on the
> screen. Machine shuts down after ca 20 seconds by itself. Data is lost,
> especially email and attachment with akonadi if the crash happens during or
> after reception.
>
> So if you run an ironlake chipset be warned.
>
> _________________________________________________________________
> ________________________________________________________
> Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de
>
>
>


--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Latest firmware update (intel graphics) destabilize ironlake chipset

Carlos E. R.-2
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



On Thursday, 2017-12-21 at 16:22 +0100, Rainer Fiebig wrote:

> stakanov wrote:
>> Just to let people know (I do not know if this is worth a bug report as older
>> hardware is considered "older hardware". Unfortunately it is a perfectly
>> functional "older hardware"...)
>> With the 4.x versions of the leap kernel the stability of the system was
>> admittedly not great (max uptime 1d and a few hours) but still you had a day
>> to work peacefully. With the firware update time to graphics crash under kde
>> plasma 5 is from some minutes to maximal 2-3 hours. And that without any
>> suspend to ram or to disc (that was the issue before).
>
> The i915-driver of 4.4.x doesn't work properly for Ironlake-GPUs - at
> least not if you use s2disk/s2both (see
> https://bugs.freedesktop.org/show_bug.cgi?id=99737)


There is no more s2disk in openSUSE.
It was superseded by systemd.

- --
Cheers,
        Carlos E. R.
        (from openSUSE 42.2 x86_64 "Malachite" at Telcontar)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlo8AjsACgkQtTMYHG2NR9W5HQCdEmVVTT9qr7w3PSN23eMSNPx0
Op4An03fk6tQPVkk078hc6EG58gfWz8j
=Y9oK
-----END PGP SIGNATURE-----

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Latest firmware update (intel graphics) destabilize ironlake chipset

Stakanov Schufter
In data giovedì 21 dicembre 2017 19:49:31 CET, Carlos E. R. ha scritto:

> On Thursday, 2017-12-21 at 16:22 +0100, Rainer Fiebig wrote:
> > stakanov wrote:
> >> Just to let people know (I do not know if this is worth a bug report as
> >> older hardware is considered "older hardware". Unfortunately it is a
> >> perfectly functional "older hardware"...)
> >> With the 4.x versions of the leap kernel the stability of the system was
> >> admittedly not great (max uptime 1d and a few hours) but still you had a
> >> day to work peacefully. With the firware update time to graphics crash
> >> under kde plasma 5 is from some minutes to maximal 2-3 hours. And that
> >> without any suspend to ram or to disc (that was the issue before).
> >
> > The i915-driver of 4.4.x doesn't work properly for Ironlake-GPUs - at
> > least not if you use s2disk/s2both (see
> > https://bugs.freedesktop.org/show_bug.cgi?id=99737)
>
> There is no more s2disk in openSUSE.
> It was superseded by systemd.
>
> --
> Cheers,
>         Carlos E. R.
>         (from openSUSE 42.2 x86_64 "Malachite" at Telcontar)
This is really a problem when updating from 42.2 to 43.3. When that update
came in (and I am already forced to avoid the dkms page, if not sddm does not
work on ironlake) suddenly I had that problem. Uptime to crash went really
down to unusable. Sometimes minutes, sometimes hours.
Then I did out of desperation a complete new install of 42.3 from scratch,
just avoiding dkms package but applying all patches.
Now it seems to work (it still crashes after two times suspending and after
max 2 days uptime, but I can live with that.
So currently, if s.o. is running into this with ironlake after update, my
advice would be a complete reinstall ("solved" it for me to some extend).


_________________________________________________________________
________________________________________________________
Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de



--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Latest firmware update (intel graphics) destabilize ironlake chipset

Rainer Fiebig
stakanov wrote:

> In data giovedì 21 dicembre 2017 19:49:31 CET, Carlos E. R. ha scritto:
>> On Thursday, 2017-12-21 at 16:22 +0100, Rainer Fiebig wrote:
>>> stakanov wrote:
>>>> Just to let people know (I do not know if this is worth a bug report as
>>>> older hardware is considered "older hardware". Unfortunately it is a
>>>> perfectly functional "older hardware"...)
>>>> With the 4.x versions of the leap kernel the stability of the system was
>>>> admittedly not great (max uptime 1d and a few hours) but still you had a
>>>> day to work peacefully. With the firware update time to graphics crash
>>>> under kde plasma 5 is from some minutes to maximal 2-3 hours. And that
>>>> without any suspend to ram or to disc (that was the issue before).
>>>
>>> The i915-driver of 4.4.x doesn't work properly for Ironlake-GPUs - at
>>> least not if you use s2disk/s2both (see
>>> https://bugs.freedesktop.org/show_bug.cgi?id=99737)
>>
>> There is no more s2disk in openSUSE.
>> It was superseded by systemd.
>>
>> --
>> Cheers,
>>         Carlos E. R.
>>         (from openSUSE 42.2 x86_64 "Malachite" at Telcontar)
> This is really a problem when updating from 42.2 to 43.3. When that update
> came in (and I am already forced to avoid the dkms page, if not sddm does not
> work on ironlake) suddenly I had that problem. Uptime to crash went really
> down to unusable. Sometimes minutes, sometimes hours.
> Then I did out of desperation a complete new install of 42.3 from scratch,
> just avoiding dkms package but applying all patches.

> Now it seems to work (it still crashes after two times suspending and after
> max 2 days uptime, but I can live with that.

You seem to have really modest expectations concerning system-stability! ;)

After suspending do a

dmesg

in a terminal. If you see something like

[...]
[drm] stuck on bsd ring
[drm] GPU HANG:
[...]

you know that the instabilities you experience after suspend/hibernation
come from the i915-driver which is an integral part of the kernel. And
as you can read in the thread that I've posted above, it won't get fixed
for kernel 4.4.

> So currently, if s.o. is running into this with ironlake after update, my
> advice would be a complete reinstall ("solved" it for me to some extend).
>
>
> _________________________________________________________________
> ________________________________________________________
> Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de
>
>
>


--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Latest firmware update (intel graphics) destabilize ironlake chipset

Stakanov Schufter
In data giovedì 21 dicembre 2017 22:16:08 CET, Rainer Fiebig ha scritto:

> stakanov wrote:
> > In data giovedì 21 dicembre 2017 19:49:31 CET, Carlos E. R. ha scritto:
> >> On Thursday, 2017-12-21 at 16:22 +0100, Rainer Fiebig wrote:
> >>> stakanov wrote:
> >>>> Just to let people know (I do not know if this is worth a bug report as
> >>>> older hardware is considered "older hardware". Unfortunately it is a
> >>>> perfectly functional "older hardware"...)
> >>>> With the 4.x versions of the leap kernel the stability of the system
> >>>> was
> >>>> admittedly not great (max uptime 1d and a few hours) but still you had
> >>>> a
> >>>> day to work peacefully. With the firware update time to graphics crash
> >>>> under kde plasma 5 is from some minutes to maximal 2-3 hours. And that
> >>>> without any suspend to ram or to disc (that was the issue before).
> >>>
> >>> The i915-driver of 4.4.x doesn't work properly for Ironlake-GPUs - at
> >>> least not if you use s2disk/s2both (see
> >>> https://bugs.freedesktop.org/show_bug.cgi?id=99737)
> >>
> >> There is no more s2disk in openSUSE.
> >> It was superseded by systemd.
> >>
> >> --
> >> Cheers,
> >>
> >>         Carlos E. R.
> >>         (from openSUSE 42.2 x86_64 "Malachite" at Telcontar)
> >
> > This is really a problem when updating from 42.2 to 43.3. When that update
> > came in (and I am already forced to avoid the dkms page, if not sddm does
> > not work on ironlake) suddenly I had that problem. Uptime to crash went
> > really down to unusable. Sometimes minutes, sometimes hours.
> > Then I did out of desperation a complete new install of 42.3 from scratch,
> > just avoiding dkms package but applying all patches.
> >
> > Now it seems to work (it still crashes after two times suspending and
> > after
> > max 2 days uptime, but I can live with that.
>
> You seem to have really modest expectations concerning system-stability! ;)
>
> After suspending do a
>
> dmesg
>
> in a terminal. If you see something like
>
> [...]
> [drm] stuck on bsd ring
> [drm] GPU HANG:
> [...]
>
> you know that the instabilities you experience after suspend/hibernation
> come from the i915-driver which is an integral part of the kernel. And
> as you can read in the thread that I've posted above, it won't get fixed
> for kernel 4.4.
>
> > So currently, if s.o. is running into this with ironlake after update, my
> > advice would be a complete reinstall ("solved" it for me to some extend).
> >
> >
> > _________________________________________________________________
> > ________________________________________________________
> > Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und
> > alte E-Mail-Adresse mitnehmen! https://www.eclipso.de
Mainly I am getting this all the time:

[ 9558.839155] [drm:ironlake_irq_handler [i915]] *ERROR* CPU pipe A FIFO
underrun
[ 9558.839194] [drm:ironlake_irq_handler [i915]] *ERROR* PCH transcoder A FIFO
underrun
[13562.429837] perf interrupt took too long (5001 > 5000), lowering
kernel.perf_event_max_sample_rate to 25000
[14409.905782] [drm:ironlake_irq_handler [i915]] *ERROR* CPU pipe A FIFO
underrun
[14409.905826] [drm:ironlake_irq_handler [i915]] *ERROR* PCH transcoder A FIFO
underrun
[27648.676576] [drm:ironlake_irq_handler [i915]] *ERROR* CPU pipe A FIFO
underrun
[27648.676621] [drm:ironlake_irq_handler [i915]] *ERROR* PCH transcoder A FIFO
underrun
[31898.932931] [drm:ironlake_irq_handler [i915]] *ERROR* CPU pipe A FIFO
underrun
[31898.932969] [drm:ironlake_irq_handler [i915]] *ERROR* PCH transcoder A FIFO
underrun
[34341.181257] [drm:ironlake_irq_handler [i915]] *ERROR* CPU pipe A FIFO
underrun
[34341.181303] [drm:ironlake_irq_handler [i915]] *ERROR* PCH transcoder A FIFO
underrun

Maybe not related? Every session is full of it.

_________________________________________________________________
________________________________________________________
Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de



--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Latest firmware update (intel graphics) destabilize ironlake chipset

Rainer Fiebig
stakanov wrote:

> In data giovedì 21 dicembre 2017 22:16:08 CET, Rainer Fiebig ha scritto:
>> stakanov wrote:
>>> In data giovedì 21 dicembre 2017 19:49:31 CET, Carlos E. R. ha scritto:
>>>> On Thursday, 2017-12-21 at 16:22 +0100, Rainer Fiebig wrote:
>>>>> stakanov wrote:
>>>>>> Just to let people know (I do not know if this is worth a bug report as
>>>>>> older hardware is considered "older hardware". Unfortunately it is a
>>>>>> perfectly functional "older hardware"...)
>>>>>> With the 4.x versions of the leap kernel the stability of the system
>>>>>> was
>>>>>> admittedly not great (max uptime 1d and a few hours) but still you had
>>>>>> a
>>>>>> day to work peacefully. With the firware update time to graphics crash
>>>>>> under kde plasma 5 is from some minutes to maximal 2-3 hours. And that
>>>>>> without any suspend to ram or to disc (that was the issue before).
>>>>>
>>>>> The i915-driver of 4.4.x doesn't work properly for Ironlake-GPUs - at
>>>>> least not if you use s2disk/s2both (see
>>>>> https://bugs.freedesktop.org/show_bug.cgi?id=99737)
>>>>
>>>> There is no more s2disk in openSUSE.
>>>> It was superseded by systemd.
>>>>
>>>> --
>>>> Cheers,
>>>>
>>>>         Carlos E. R.
>>>>         (from openSUSE 42.2 x86_64 "Malachite" at Telcontar)
>>>
>>> This is really a problem when updating from 42.2 to 43.3. When that update
>>> came in (and I am already forced to avoid the dkms page, if not sddm does
>>> not work on ironlake) suddenly I had that problem. Uptime to crash went
>>> really down to unusable. Sometimes minutes, sometimes hours.
>>> Then I did out of desperation a complete new install of 42.3 from scratch,
>>> just avoiding dkms package but applying all patches.
>>>
>>> Now it seems to work (it still crashes after two times suspending and
>>> after
>>> max 2 days uptime, but I can live with that.
>>
>> You seem to have really modest expectations concerning system-stability! ;)
>>
>> After suspending do a
>>
>> dmesg
>>
>> in a terminal. If you see something like
>>
>> [...]
>> [drm] stuck on bsd ring
>> [drm] GPU HANG:
>> [...]
>>
>> you know that the instabilities you experience after suspend/hibernation
>> come from the i915-driver which is an integral part of the kernel. And
>> as you can read in the thread that I've posted above, it won't get fixed
>> for kernel 4.4.
>>
>>> So currently, if s.o. is running into this with ironlake after update, my
>>> advice would be a complete reinstall ("solved" it for me to some extend).
>>>
>>>
>>> _________________________________________________________________
>>> ________________________________________________________
>>> Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und
>>> alte E-Mail-Adresse mitnehmen! https://www.eclipso.de
> Mainly I am getting this all the time:
>
> [ 9558.839155] [drm:ironlake_irq_handler [i915]] *ERROR* CPU pipe A FIFO
> underrun
> [ 9558.839194] [drm:ironlake_irq_handler [i915]] *ERROR* PCH transcoder A FIFO
> underrun
> [13562.429837] perf interrupt took too long (5001 > 5000), lowering
> kernel.perf_event_max_sample_rate to 25000
> [14409.905782] [drm:ironlake_irq_handler [i915]] *ERROR* CPU pipe A FIFO
> underrun
> [14409.905826] [drm:ironlake_irq_handler [i915]] *ERROR* PCH transcoder A FIFO
> underrun
> [27648.676576] [drm:ironlake_irq_handler [i915]] *ERROR* CPU pipe A FIFO
> underrun
> [27648.676621] [drm:ironlake_irq_handler [i915]] *ERROR* PCH transcoder A FIFO
> underrun
> [31898.932931] [drm:ironlake_irq_handler [i915]] *ERROR* CPU pipe A FIFO
> underrun
> [31898.932969] [drm:ironlake_irq_handler [i915]] *ERROR* PCH transcoder A FIFO
> underrun
> [34341.181257] [drm:ironlake_irq_handler [i915]] *ERROR* CPU pipe A FIFO
> underrun
> [34341.181303] [drm:ironlake_irq_handler [i915]] *ERROR* PCH transcoder A FIFO
> underrun
>
> Maybe not related? Every session is full of it.

Absolutely related - it's the driver. There's nothing you can do about
it. Fresh install doesn't help either.

Switching to 4.9 would be the best solution for you. If you don't know
how to compile a kernel (which is not difficult once you know how), file
a bug report with openSuse. They probably won't be able to fix this for
4.4 but perhaps the kernel-guys might provide an alternate kernel for
users with Ironlake-GPUs.

>
> _________________________________________________________________
> ________________________________________________________
> Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de
>
>
>


--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Latest firmware update (intel graphics) destabilize ironlake chipset

Carlos E. R.-2
In reply to this post by Carlos E. R.-2
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



You forgot to post to the list.

> Carlos E. R. wrote:
>> On Thursday, 2017-12-21 at 16:22 +0100, Rainer Fiebig wrote:
>>
>>> stakanov wrote:
>>>> Just to let people know (I do not know if this is worth a bug report
>>>> as older hardware is considered "older hardware". Unfortunately it is
>>>> a perfectly functional "older hardware"...) With the 4.x versions of
>>>> the leap kernel the stability of the system was admittedly not great
>>>> (max uptime 1d and a few hours) but still you had a day to work
>>>> peacefully. With the firware update time to graphics crash under kde
>>>> plasma 5 is from some minutes to maximal 2-3 hours. And that without
>>>> any suspend to ram or to disc (that was the issue before).
>>
>>> The i915-driver of 4.4.x doesn't work properly for Ironlake-GPUs - at
>>> least not if you use s2disk/s2both (see
>>> https://bugs.freedesktop.org/show_bug.cgi?id=99737)
>>
>>
>> There is no more s2disk in openSUSE.
>> It was superseded by systemd.
>
> pm-hibernate then. Doesn't matter here. The Intel-graphics-driver in

There is nothing pm-* either. Again, it is systemd, not pmutils anymore.

The current call is "systemctl hibernate".

> kernels >= 4.3 <= 4.7 doesn't work properly with Ironlake-GPUs. So if he
> wants to use the equivalent of s2disk/s2both with that GPU he can either
> use another kernel or get new hardware. I'd rather switch the kernel.


- --
Saludos
        Carlos E. R.
        (desde openSUSE 42.2 x86_64 "Malachite" en Telcontar)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlo8RcgACgkQtTMYHG2NR9Xx/wCfbo6BaNqY3czVg9+6ojR56iOH
6WAAn3bS3Hl9ZXFx5m9rBMBRjaMuyYDj
=P73z
-----END PGP SIGNATURE-----

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Latest firmware update (intel graphics) destabilize ironlake chipset

Stakanov Schufter
In reply to this post by Rainer Fiebig
In data giovedì 21 dicembre 2017 22:36:48 CET, Rainer Fiebig ha scritto:

> Absolutely related - it's the driver. There's nothing you can do about
> it. Fresh install doesn't help either.
>
> Switching to 4.9 would be the best solution for you. If you don't know
> how to compile a kernel (which is not difficult once you know how), file
> a bug report with openSuse. They probably won't be able to fix this for
> 4.4 but perhaps the kernel-guys might provide an alternate kernel for
> users with Ironlake-GPUs.
>
Well, although in the past I served myself from "kernel-stable" I prefer to
sit it out because of security concerns. I really want to stick as much as
possible to standard leap.
Anyway with a bit of luck I will get rid of it in June or so, if the leap 15
will have a new kernel. But thank you for the heads up. So at least I know it
is not my hardware failing (I actually suspected the driver to be the culprit
but it is good to know).

Seasonale greatings.

_________________________________________________________________
________________________________________________________
Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de



--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Latest firmware update (intel graphics) destabilize ironlake chipset

Rainer Fiebig
stakanov wrote:

> In data giovedì 21 dicembre 2017 22:36:48 CET, Rainer Fiebig ha scritto:
>
>> Absolutely related - it's the driver. There's nothing you can do about
>> it. Fresh install doesn't help either.
>>
>> Switching to 4.9 would be the best solution for you. If you don't know
>> how to compile a kernel (which is not difficult once you know how), file
>> a bug report with openSuse. They probably won't be able to fix this for
>> 4.4 but perhaps the kernel-guys might provide an alternate kernel for
>> users with Ironlake-GPUs.
>>
> Well, although in the past I served myself from "kernel-stable" I prefer to
> sit it out because of security concerns. I really want to stick as much as
> possible to standard leap.
> Anyway with a bit of luck I will get rid of it in June or so, if the leap 15
> will have a new kernel. But thank you for the heads up. So at least I know it
> is not my hardware failing (I actually suspected the driver to be the culprit
> but it is good to know).
>
> Seasonale greatings.
>
> _________________________________________________________________
> ________________________________________________________
> Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de
>
>
>

You should really file a bug report so that the Suse-kernel-guys know
that there's a problem and perhaps provide an alternate kernel. You're
probably not the only "Leaper" with an Ironlake-GPU.

So long!
Rainer Fiebig

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Latest firmware update (intel graphics) destabilize ironlake chipset

Rainer Fiebig
In reply to this post by Carlos E. R.-2
Carlos E. R. wrote:
>
>
> You forgot to post to the list.

Right. Sorry!

>
>> Carlos E. R. wrote:
>>> On Thursday, 2017-12-21 at 16:22 +0100, Rainer Fiebig wrote:
>>>
>>>> stakanov wrote:
>>>>> Just to let people know (I do not know if this is worth a bug
>>>>> report as older hardware is considered "older hardware".
>>>>> Unfortunately it is a perfectly functional "older hardware"...)
>>>>> With the 4.x versions of the leap kernel the stability of the
>>>>> system was admittedly not great (max uptime 1d and a few hours) but
>>>>> still you had a day to work peacefully. With the firware update
>>>>> time to graphics crash under kde plasma 5 is from some minutes to
>>>>> maximal 2-3 hours. And that without any suspend to ram or to disc
>>>>> (that was the issue before).
>>>
>>>> The i915-driver of 4.4.x doesn't work properly for Ironlake-GPUs - at
>>>> least not if you use s2disk/s2both (see
>>>> https://bugs.freedesktop.org/show_bug.cgi?id=99737)
>>>
>>>
>>> There is no more s2disk in openSUSE.
>>> It was superseded by systemd.
>
>> pm-hibernate then. Doesn't matter here. The Intel-graphics-driver in
>
> There is nothing pm-* either. Again, it is systemd, not pmutils anymore.
>
> The current call is "systemctl hibernate".
>
>> kernels >= 4.3 <= 4.7 doesn't work properly with Ironlake-GPUs. So if he
>> wants to use the equivalent of s2disk/s2both with that GPU he can either
>> use another kernel or get new hardware. I'd rather switch the kernel.
>
>
> -- Saludos
>        Carlos E. R.
>        (desde openSUSE 42.2 x86_64 "Malachite" en Telcontar)
>


--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Latest firmware update (intel graphics) destabilize ironlake chipset

Stakanov Schufter
In reply to this post by Rainer Fiebig
In data venerdì 22 dicembre 2017 11:49:08 CET, Rainer Fiebig ha scritto:

> stakanov wrote:
> > In data giovedì 21 dicembre 2017 22:36:48 CET, Rainer Fiebig ha scritto:
> >> Absolutely related - it's the driver. There's nothing you can do about
> >> it. Fresh install doesn't help either.
> >>
> >> Switching to 4.9 would be the best solution for you. If you don't know
> >> how to compile a kernel (which is not difficult once you know how), file
> >> a bug report with openSuse. They probably won't be able to fix this for
> >> 4.4 but perhaps the kernel-guys might provide an alternate kernel for
> >> users with Ironlake-GPUs.
> >
> > Well, although in the past I served myself from "kernel-stable" I prefer
> > to
> > sit it out because of security concerns. I really want to stick as much as
> > possible to standard leap.
> > Anyway with a bit of luck I will get rid of it in June or so, if the leap
> > 15 will have a new kernel. But thank you for the heads up. So at least I
> > know it is not my hardware failing (I actually suspected the driver to be
> > the culprit but it is good to know).
> >
> > Seasonale greatings.
> >
> > _________________________________________________________________
> > ________________________________________________________
> > Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und
> > alte E-Mail-Adresse mitnehmen! https://www.eclipso.de
> You should really file a bug report so that the Suse-kernel-guys know
> that there's a problem and perhaps provide an alternate kernel. You're
> probably not the only "Leaper" with an Ironlake-GPU.
>
> So long!
> Rainer Fiebig

I think I have already. But I will have to wait for the fix upstream I guess.
https://bugzilla.opensuse.org/show_bug.cgi?id=1051115

Thanks and seasonal greetings!


_________________________________________________________________
________________________________________________________
Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de



--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Latest firmware update (intel graphics) destabilize ironlake chipset

Rainer Fiebig
stakanov wrote:

> In data venerdì 22 dicembre 2017 11:49:08 CET, Rainer Fiebig ha scritto:
>> stakanov wrote:
>>> In data giovedì 21 dicembre 2017 22:36:48 CET, Rainer Fiebig ha scritto:
>>>> Absolutely related - it's the driver. There's nothing you can do about
>>>> it. Fresh install doesn't help either.
>>>>
>>>> Switching to 4.9 would be the best solution for you. If you don't know
>>>> how to compile a kernel (which is not difficult once you know how), file
>>>> a bug report with openSuse. They probably won't be able to fix this for
>>>> 4.4 but perhaps the kernel-guys might provide an alternate kernel for
>>>> users with Ironlake-GPUs.
>>>
>>> Well, although in the past I served myself from "kernel-stable" I prefer
>>> to
>>> sit it out because of security concerns. I really want to stick as much as
>>> possible to standard leap.
>>> Anyway with a bit of luck I will get rid of it in June or so, if the leap
>>> 15 will have a new kernel. But thank you for the heads up. So at least I
>>> know it is not my hardware failing (I actually suspected the driver to be
>>> the culprit but it is good to know).
>>>
>>> Seasonale greatings.
>>>
>>> _________________________________________________________________
>>> ________________________________________________________
>>> Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und
>>> alte E-Mail-Adresse mitnehmen! https://www.eclipso.de
>> You should really file a bug report so that the Suse-kernel-guys know
>> that there's a problem and perhaps provide an alternate kernel. You're
>> probably not the only "Leaper" with an Ironlake-GPU.
>>
>> So long!
>> Rainer Fiebig
>
> I think I have already. But I will have to wait for the fix upstream I guess.
> https://bugzilla.opensuse.org/show_bug.cgi?id=1051115
>
> Thanks and seasonal greetings!
>
>
> _________________________________________________________________
> ________________________________________________________
> Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de
>
>
>

OK, so you have done your duty and been waiting almost half a year
already. But even if you wait forever: this won't get fixed in kernel
4.4! Tough luck for everybody with Ironlake-hardware and a distro that
uses that kernel.

Kernels later than 4.7 do work. And in earlier days openSuse offered
alternate kernels for the distro. But I'm not sure whether this is still
the case.

So long!

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]