Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #63433 > unrolled thread
| Started by | Michael Niewöhner <linux@mniewoehner.de> |
|---|---|
| First post | 2019-02-24 17:40 +0100 |
| Last post | 2019-07-28 03:00 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.debian.kernel
Bug#923165: initramfs: reboot in panic function does not work Michael Niewöhner <linux@mniewoehner.de> - 2019-02-24 17:40 +0100
Bug#923165: marked as done (initramfs: reboot in panic function does not work) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2019-07-28 03:00 +0200
| From | Michael Niewöhner <linux@mniewoehner.de> |
|---|---|
| Date | 2019-02-24 17:40 +0100 |
| Subject | Bug#923165: initramfs: reboot in panic function does not work |
| Message-ID | <xv4YP-71a-47@gated-at.bofh.it> |
Package: initramfs-tools
Version: 0.133
Severity: normal
Tags: patch
The panic()-function in /scripts/function tries to reboot the system.
When this fails, a kernel panic is generated by exiting PID 1.
At least for me, the reboot always fails. AFAIK "reboot" would not work at all
because there is no reboot handler at this stage...
Patch:
--- a/scripts/functions
+++ b/scripts/functions
@@ -47,3 +47,3 @@ panic()
sleep "${panic}"
- reboot
+ reboot -f
exit # in case reboot fails, force kernel panic
[toc] | [next] | [standalone]
| From | "Debian Bug Tracking System" <owner@bugs.debian.org> |
|---|---|
| Date | 2019-07-28 03:00 +0200 |
| Subject | Bug#923165: marked as done (initramfs: reboot in panic function does not work) |
| Message-ID | <yoFHA-1TM-11@gated-at.bofh.it> |
| In reply to | #63433 |
[Multipart message — attachments visible in raw view] — view raw
Your message dated Sun, 28 Jul 2019 00:50:51 +0000 with message-id <E1hrXOl-0009Al-H8@fasolo.debian.org> and subject line Bug#923165: fixed in initramfs-tools 0.134 has caused the Debian Bug report #923165, regarding initramfs: reboot in panic function does not work to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 923165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923165 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web