Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #901804
| From | Luke Kenneth Casson Leighton <lkcl@lkcl.net> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.kernel |
| Subject | Bug#901006: closed by Ben Hutchings <ben@decadent.org.uk> (Re: Bug#901006: linux-image-4.16.0-2-amd64: "core has locked up" kernel messagee) |
| Date | 2018-06-08 04:10 +0200 |
| Message-ID | <vYf0J-73O-3@gated-at.bofh.it> (permalink) |
| References | <vYeo1-6Cf-3@gated-at.bofh.it> <vYcFz-5B1-1@gated-at.bofh.it> <vYf0J-73O-5@gated-at.bofh.it> <vYcFz-5B1-1@gated-at.bofh.it> <vYf0J-73O-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
On Fri, Jun 8, 2018 at 2:27 AM, Debian Bug Tracking System <owner@bugs.debian.org> wrote: > ---------- Forwarded message ---------- > From: Ben Hutchings <ben@decadent.org.uk> > To: 901006-done@bugs.debian.org > Cc: > Bcc: > Date: Fri, 08 Jun 2018 02:24:57 +0100 > Subject: Re: Bug#901006: linux-image-4.16.0-2-amd64: "core has locked up" kernel messagee > Sorry, we can't do anything with this. that's ok, ben: the report was more fyi, as it's so unusual (never seen anything like it before, didn't even know it was *possible* for one single core on an SMP system to end up "frozen"), however it's pretty highly indicative that whatever changes have gone into 4.16 are clearly *completely* unsuited to being propagated for advancement to debian/stable status. l.
Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Find similar | Unroll thread
Bug#901006: linux-image-4.16.0-2-amd64: "core has locked up" kernel messagee lkcl <lkcl@lkcl.net> - 2018-06-08 01:40 +0200 Bug#901006: closed by Ben Hutchings <ben@decadent.org.uk> (Re: Bug#901006: linux-image-4.16.0-2-amd64: "core has locked up" kernel messagee) Luke Kenneth Casson Leighton <lkcl@lkcl.net> - 2018-06-08 04:10 +0200
csiph-web