Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #59659 > unrolled thread
| Started by | Salvatore Bonaccorso <carnil@debian.org> |
|---|---|
| First post | 2017-12-14 17:40 +0100 |
| Last post | 2018-01-16 20:40 +0100 |
| Articles | 6 — 4 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#884371: Hangs on boot without messages Salvatore Bonaccorso <carnil@debian.org> - 2017-12-14 17:40 +0100
Bug#884371: Hangs on boot without messages Sven Bartscher <sven.bartscher@weltraumschlangen.de> - 2017-12-14 18:40 +0100
Bug#884371: Hangs on boot without messages Salvatore Bonaccorso <carnil@debian.org> - 2017-12-14 20:50 +0100
Bug#884371: Hangs on boot without messages Sven Bartscher <kritzefitz@debian.org> - 2018-01-16 15:40 +0100
Bug#884371: Hangs on boot without messages Salvatore Bonaccorso <carnil@debian.org> - 2018-01-16 20:40 +0100
Processed: Re: Bug#884371: Hangs on boot without messages "Debian Bug Tracking System" <owner@bugs.debian.org> - 2018-01-16 20:40 +0100
| From | Salvatore Bonaccorso <carnil@debian.org> |
|---|---|
| Date | 2017-12-14 17:40 +0100 |
| Subject | Bug#884371: Hangs on boot without messages |
| Message-ID | <uWEIa-13Z-21@gated-at.bofh.it> |
Hi Sven, On Thu, Dec 14, 2017 at 04:50:02PM +0100, Sven Bartscher wrote: > Package: src:linux > Version: 3.16.51-2 > Severity: important > > Due to the nature of this bug, this report was generated with reportbug running > on 3.16.43-2+deb8u5, so the information gathered by reportbug may only be > partially useful. > > After upgrading the kernel to 3.16.51-2 it doesn't boot anymore. All I can see > is the messages emitted by GRUB “Loading Linux 3.16.0-4-amd64 ...” and “Loading > initial ramdisk ...”. Nothing seems to happen after that (I waited for about 5 > minutes). The kernel does not seem to print any messages, even when booting > without the quiet parameter. > > Unfortunetely the machine in question is a production server and I'm not > allowed to restart it at will. This may make debugging in the future quite hard > and is the reason why I didn't include a photo of the frozen screen. Just to confirm, the output is not logged to any console you are capturing? Is this the same issue as #883938 There are test-kernels available at https://bugs.debian.org/883938#170 which is pending to be scheudled via a jessie-updates upload. Regards, Salvatore
[toc] | [next] | [standalone]
| From | Sven Bartscher <sven.bartscher@weltraumschlangen.de> |
|---|---|
| Date | 2017-12-14 18:40 +0100 |
| Message-ID | <uWFEf-1Hz-15@gated-at.bofh.it> |
| In reply to | #59659 |
[Multipart message — attachments visible in raw view] — view raw
Hi Salvatore, Am 14.12.2017 um 17:33 schrieb Salvatore Bonaccorso: > Just to confirm, the output is not logged to any console you are > capturing? That's a good question. There might actually be another console where the output is going. I will definitely check this the next time it's possible. > Is this the same issue as #883938 Depends on the output I might see on the serial console. > There are test-kernels available at https://bugs.debian.org/883938#170 > which is pending to be scheudled via a jessie-updates upload. I will try if they work as soon as possible. Unfortunately, we can only schedule the next downtime next month. I will post then (or sooner if an unplanned opportunity arrises). Regards Sven
[toc] | [prev] | [next] | [standalone]
| From | Salvatore Bonaccorso <carnil@debian.org> |
|---|---|
| Date | 2017-12-14 20:50 +0100 |
| Message-ID | <uWHG2-2VO-7@gated-at.bofh.it> |
| In reply to | #59660 |
Hi Sven! On Thu, Dec 14, 2017 at 06:20:14PM +0100, Sven Bartscher wrote: > Hi Salvatore, > > Am 14.12.2017 um 17:33 schrieb Salvatore Bonaccorso: > > Just to confirm, the output is not logged to any console you are > > capturing? > > That's a good question. There might actually be another console where > the output is going. I will definitely check this the next time it's > possible. > > > Is this the same issue as #883938 > > Depends on the output I might see on the serial console. > > > There are test-kernels available at https://bugs.debian.org/883938#170 > > which is pending to be scheudled via a jessie-updates upload. > > I will try if they work as soon as possible. Unfortunately, we can only > schedule the next downtime next month. I will post then (or sooner if an > unplanned opportunity arrises). Alright, thanks. I will mark it for now as moreinfo, please let us know as soon you get a chance to confirm either the duplication of #883938 or when more infos with the 3.16.51-3 kernel are avaiable[*]. [*] The update should go out relatively soon now via a stable-updates. Regards, Salvatore
[toc] | [prev] | [next] | [standalone]
| From | Sven Bartscher <kritzefitz@debian.org> |
|---|---|
| Date | 2018-01-16 15:40 +0100 |
| Message-ID | <v8Az8-1Gr-17@gated-at.bofh.it> |
| In reply to | #59662 |
[Multipart message — attachments visible in raw view] — view raw
Hi Salvatore, On Thu, 14 Dec 2017 20:42:48 +0100 Salvatore Bonaccorso <carnil@debian.org> wrote: > Hi Sven! > > On Thu, Dec 14, 2017 at 06:20:14PM +0100, Sven Bartscher wrote: > > Hi Salvatore, > > > > Am 14.12.2017 um 17:33 schrieb Salvatore Bonaccorso: > > > Just to confirm, the output is not logged to any console you are > > > capturing? > > > > That's a good question. There might actually be another console where > > the output is going. I will definitely check this the next time it's > > possible. > > > > > Is this the same issue as #883938 > > > > Depends on the output I might see on the serial console. > > > > > There are test-kernels available at https://bugs.debian.org/883938#170 > > > which is pending to be scheudled via a jessie-updates upload. > > > > I will try if they work as soon as possible. Unfortunately, we can only > > schedule the next downtime next month. I will post then (or sooner if an > > unplanned opportunity arrises). > > Alright, thanks. I will mark it for now as moreinfo, please let us > know as soon you get a chance to confirm either the duplication of > #883938 or when more infos with the 3.16.51-3 kernel are avaiable[*]. We tried 3.16.51-3+deb8u1 today and it booted without problems, so I guess this was actually the same issue as #883938 and the output was missing for some other reason. Regards Sven
[toc] | [prev] | [next] | [standalone]
| From | Salvatore Bonaccorso <carnil@debian.org> |
|---|---|
| Date | 2018-01-16 20:40 +0100 |
| Message-ID | <v8Ffr-4O1-3@gated-at.bofh.it> |
| In reply to | #60008 |
Control: forcemerge 883938 884371 Control: tags 884371 - moreinfo Hi Sven, On Tue, Jan 16, 2018 at 03:29:54PM +0100, Sven Bartscher wrote: > Hi Salvatore, > > On Thu, 14 Dec 2017 20:42:48 +0100 Salvatore Bonaccorso > <carnil@debian.org> wrote: > > Hi Sven! > > > > On Thu, Dec 14, 2017 at 06:20:14PM +0100, Sven Bartscher wrote: > > > Hi Salvatore, > > > > > > Am 14.12.2017 um 17:33 schrieb Salvatore Bonaccorso: > > > > Just to confirm, the output is not logged to any console you are > > > > capturing? > > > > > > That's a good question. There might actually be another console where > > > the output is going. I will definitely check this the next time it's > > > possible. > > > > > > > Is this the same issue as #883938 > > > > > > Depends on the output I might see on the serial console. > > > > > > > There are test-kernels available at https://bugs.debian.org/883938#170 > > > > which is pending to be scheudled via a jessie-updates upload. > > > > > > I will try if they work as soon as possible. Unfortunately, we can only > > > schedule the next downtime next month. I will post then (or sooner if an > > > unplanned opportunity arrises). > > > > Alright, thanks. I will mark it for now as moreinfo, please let us > > know as soon you get a chance to confirm either the duplication of > > #883938 or when more infos with the 3.16.51-3 kernel are avaiable[*]. > > We tried 3.16.51-3+deb8u1 today and it booted without problems, so I > guess this was actually the same issue as #883938 and the output was > missing for some other reason. Alright thanks for reporting back! I'm merging then the two reports, since I'm quite confident it was then the same issue. Regards, Salvatore
[toc] | [prev] | [next] | [standalone]
| From | "Debian Bug Tracking System" <owner@bugs.debian.org> |
|---|---|
| Date | 2018-01-16 20:40 +0100 |
| Subject | Processed: Re: Bug#884371: Hangs on boot without messages |
| Message-ID | <v8Ffs-4O1-13@gated-at.bofh.it> |
| In reply to | #60011 |
Processing control commands:
> forcemerge 883938 884371
Bug #883938 {Done: Ben Hutchings <ben@decadent.org.uk>} [src:linux] linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51
Bug #884069 {Done: Ben Hutchings <ben@decadent.org.uk>} [src:linux] Kernel crash on boot on IBM BladeCenter HS22
Bug #884140 {Done: Ben Hutchings <ben@decadent.org.uk>} [src:linux] Kernel 3.16.51-2 general protection fault in sched_init_smp()
Bug #884183 {Done: Ben Hutchings <ben@decadent.org.uk>} [src:linux] linux-image-3.16.0-4-amd64: Kernel panic at boot
Bug #884183 {Done: Ben Hutchings <ben@decadent.org.uk>} [src:linux] linux-image-3.16.0-4-amd64: Kernel panic at boot
Added tag(s) moreinfo.
Added tag(s) moreinfo.
Added tag(s) moreinfo.
Added tag(s) moreinfo.
Bug #884371 [src:linux] Hangs on boot without messages
Severity set to 'grave' from 'important'
Marked Bug as done
Summary recorded from message bug 884371 message
Added indication that 884371 affects release.debian.org
Marked as fixed in versions linux/3.16.51-3.
Bug #884069 {Done: Ben Hutchings <ben@decadent.org.uk>} [src:linux] Kernel crash on boot on IBM BladeCenter HS22
Bug #884140 {Done: Ben Hutchings <ben@decadent.org.uk>} [src:linux] Kernel 3.16.51-2 general protection fault in sched_init_smp()
Merged 883938 884069 884140 884183 884371
> tags 884371 - moreinfo
Bug #884371 {Done: Ben Hutchings <ben@decadent.org.uk>} [src:linux] Hangs on boot without messages
Bug #883938 {Done: Ben Hutchings <ben@decadent.org.uk>} [src:linux] linux-image-3.16.0-4-amd64: Kernel panic on boot after upgrading to debian 8.10 kernel 3.16.51
Bug #884069 {Done: Ben Hutchings <ben@decadent.org.uk>} [src:linux] Kernel crash on boot on IBM BladeCenter HS22
Bug #884140 {Done: Ben Hutchings <ben@decadent.org.uk>} [src:linux] Kernel 3.16.51-2 general protection fault in sched_init_smp()
Bug #884183 {Done: Ben Hutchings <ben@decadent.org.uk>} [src:linux] linux-image-3.16.0-4-amd64: Kernel panic at boot
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.
--
883938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883938
884069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884069
884140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884140
884183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884183
884371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884371
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web