Discussion:
i810 segfault starting server
(too old to reply)
Felix Miata
2014-08-30 09:13:13 UTC
Permalink
Raw Message
Factory with kernel 3.16.0, server 1.16.0 and driver 2.99.914 segfaults.
Factory with kernel 3.16.0, server 1.16.0 and driver 3.0.0git-199 (BS:sumski)
is OK.

The 3git driver was known on the intel-gfx mailing list to have fixed the
problem more than 3 months ago. Why is such an old and known broken intel
driver still in Factory? I don't see any open bug about getting Factory past
2.99. Is a new bug needed here?
--
"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/
Takashi Iwai
2014-09-01 08:52:54 UTC
Permalink
Raw Message
At Sat, 30 Aug 2014 05:13:13 -0400,
Post by Felix Miata
Factory with kernel 3.16.0, server 1.16.0 and driver 2.99.914 segfaults.
Factory with kernel 3.16.0, server 1.16.0 and driver 3.0.0git-199 (BS:sumski)
is OK.
The 3git driver was known on the intel-gfx mailing list to have fixed the
problem more than 3 months ago. Why is such an old and known broken intel
driver still in Factory?
I don't see any open bug about getting Factory past
2.99. Is a new bug needed here?
What's relevant with opensuse-kernel ML...?

In anyway, the reason 2.99.914 is used is that it's the latest
released tarball version. 2.99.914 was released in July 23, so the
fix for your issue should have been already included in it had been
fixed in 3 or more months ago.


Takashi
Felix Miata
2014-09-01 11:22:08 UTC
Permalink
Raw Message
Post by Takashi Iwai
Post by Felix Miata
Factory with kernel 3.16.0, server 1.16.0 and driver 2.99.914 segfaults.
Factory with kernel 3.16.0, server 1.16.0 and driver 3.0.0git-199 (BS:sumski)
is OK.
The 3git driver was known on the intel-gfx mailing list to have fixed the
problem more than 3 months ago. Why is such an old and known broken intel
driver still in Factory?
I don't see any open bug about getting Factory past
2.99. Is a new bug needed here?
In anyway, the reason 2.99.914 is used is that it's the latest
released tarball version. 2.99.914 was released in July 23, so the
fix for your issue should have been already included in it had been
fixed in 3 or more months ago.
Turns out it wasn't fixed until just over a month ago, and then only in git:
https://bugs.freedesktop.org/show_bug.cgi?id=83287
--
"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/
Takashi Iwai
2014-09-01 11:41:43 UTC
Permalink
Raw Message
At Mon, 01 Sep 2014 07:22:08 -0400,
Post by Felix Miata
Post by Takashi Iwai
Post by Felix Miata
Factory with kernel 3.16.0, server 1.16.0 and driver 2.99.914 segfaults.
Factory with kernel 3.16.0, server 1.16.0 and driver 3.0.0git-199 (BS:sumski)
is OK.
The 3git driver was known on the intel-gfx mailing list to have fixed the
problem more than 3 months ago. Why is such an old and known broken intel
driver still in Factory?
I don't see any open bug about getting Factory past
2.99. Is a new bug needed here?
In anyway, the reason 2.99.914 is used is that it's the latest
released tarball version. 2.99.914 was released in July 23, so the
fix for your issue should have been already included in it had been
fixed in 3 or more months ago.
https://bugs.freedesktop.org/show_bug.cgi?id=83287
Then please open a bug entry and point the commit id to cherry-pick
there. Thanks.


Takashi

Loading...