On Tue, Mar 12, 2019 at 04:29:25PM -0500, Eric W. Biederman wrote:
> I wonder if there is an easy way to get the scheduler to not schedule
> userspace processes once the reboot system call has started. That
> sounds like the simple way to avoid this kind of confusion.
That sounds like adding
Linus Torvalds writes:
> On Wed, Mar 6, 2019 at 5:29 AM Petr Mladek wrote:
>>
>> I wonder if it is "normal" to get panic() when the system is rebooted
>> using "reboot -f". I looks a bit weird to me.
>
> No, a panic is never normal (except possibly for test modules etc, of course).
>
>> Now,
On Wed, Mar 6, 2019 at 5:29 AM Petr Mladek wrote:
>
> I wonder if it is "normal" to get panic() when the system is rebooted
> using "reboot -f". I looks a bit weird to me.
No, a panic is never normal (except possibly for test modules etc, of course).
> Now, "reboot -f" just calls the reboot()
Hello,
I wonder if it is "normal" to get panic() when the system is rebooted
using "reboot -f". I looks a bit weird to me.
In our case, the panic() was triggered from ext4 filesystem code
that was mounted with "errors=panic"
crash> bt
PID: 3984 TASK: 887db1f6c180 CPU: 32 COMMAND:
4 matches
Mail list logo
