Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #61344 > unrolled thread
| Started by | Ryan Tandy <ryan@nardis.ca> |
|---|---|
| First post | 2018-07-04 04:00 +0200 |
| Last post | 2019-04-13 11:30 +0200 |
| Articles | 3 — 3 participants |
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.
Bug#866122: slapd-mtread crash on ppc64{,el} in stretch/sid Ryan Tandy <ryan@nardis.ca> - 2018-07-04 04:00 +0200
Bug#866122: slapd-mtread crash on ppc64{,el} in stretch/sid Ben Hutchings <ben@decadent.org.uk> - 2019-02-10 18:10 +0100
Bug#866122: slapd-mtread crash on ppc64{,el} in stretch/sid Ivo De Decker <ivodd@debian.org> - 2019-04-13 11:30 +0200
| From | Ryan Tandy <ryan@nardis.ca> |
|---|---|
| Date | 2018-07-04 04:00 +0200 |
| Subject | Bug#866122: slapd-mtread crash on ppc64{,el} in stretch/sid |
| Message-ID | <w7Ffj-2x3-3@gated-at.bofh.it> |
Control: found -1 4.17.3-1 Hi, On Mon, Jul 02, 2018 at 08:42:45PM -0700, Ryan Tandy wrote: >However it looks like it might be resolved with the kernel in >unstable. I will run some more iterations and let you know. The issue still reproduces with stretch userland and the current unstable kernel. It cannot be reproduced with buster's glibc because lock elision was disabled in #878071, citing this issue. Thanks Ryan
[toc] | [next] | [standalone]
| From | Ben Hutchings <ben@decadent.org.uk> |
|---|---|
| Date | 2019-02-10 18:10 +0100 |
| Message-ID | <xq0M9-3QV-1@gated-at.bofh.it> |
| In reply to | #61344 |
[Multipart message — attachments visible in raw view] — view raw
On Tue, 3 Jul 2018 18:51:49 -0700 Ryan Tandy <ryan@nardis.ca> wrote: > Control: found -1 4.17.3-1 > > Hi, > > On Mon, Jul 02, 2018 at 08:42:45PM -0700, Ryan Tandy wrote: > >However it looks like it might be resolved with the kernel in > >unstable. I will run some more iterations and let you know. > > The issue still reproduces with stretch userland and the current > unstable kernel. > > It cannot be reproduced with buster's glibc because lock elision was > disabled in #878071, citing this issue. This bug has been open for over 18 months with no sign of a solution, which is really not acceptable for a release architecture. I propose to disable CONFIG_PPC_TRANSACTIONAL_MEMORY in both stretch and unstable, until a fix is available for TM. Ben. -- Ben Hutchings The world is coming to an end. Please log off.
[toc] | [prev] | [next] | [standalone]
| From | Ivo De Decker <ivodd@debian.org> |
|---|---|
| Date | 2019-04-13 11:30 +0200 |
| Message-ID | <xMn8Z-7SO-13@gated-at.bofh.it> |
| In reply to | #63305 |
Hi Ben, On Sun, Feb 10, 2019 at 05:07:07PM +0000, Ben Hutchings wrote: > On Tue, 3 Jul 2018 18:51:49 -0700 Ryan Tandy <ryan@nardis.ca> wrote: > > Control: found -1 4.17.3-1 > > > > Hi, > > > > On Mon, Jul 02, 2018 at 08:42:45PM -0700, Ryan Tandy wrote: > > >However it looks like it might be resolved with the kernel in > > >unstable. I will run some more iterations and let you know. > > > > The issue still reproduces with stretch userland and the current > > unstable kernel. > > > > It cannot be reproduced with buster's glibc because lock elision was > > disabled in #878071, citing this issue. > > This bug has been open for over 18 months with no sign of a solution, > which is really not acceptable for a release architecture. I propose > to disable CONFIG_PPC_TRANSACTIONAL_MEMORY in both stretch and > unstable, until a fix is available for TM. We're getting pretty close to the release. Are you planning to disable CONFIG_PPC_TRANSACTIONAL_MEMORY for buster? Thanks, Ivo
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web