Thanks for fixing it!
> On 15. Mar 2023, at 13:20, Corey Minyard wrote:
>
> On Wed, Mar 15, 2023 at 01:12:05PM +0100, Christian Theune via
> Openipmi-developer wrote:
>> Ah, fantastic! That explains it of course … :)
>>
>> From my side I guess this works and I don’t have to retry with that,
On Wed, Mar 15, 2023 at 01:12:05PM +0100, Christian Theune via
Openipmi-developer wrote:
> Ah, fantastic! That explains it of course … :)
>
> From my side I guess this works and I don’t have to retry with that, but I’d
> be happy to just wait for 5.10.175 … or would you prefer me explicitly
>
Ah, fantastic! That explains it of course … :)
From my side I guess this works and I don’t have to retry with that, but I’d be
happy to just wait for 5.10.175 … or would you prefer me explicitly testing
your original?
Christian
> On 15. Mar 2023, at 13:07, Corey Minyard wrote:
>
> On Wed,
On Wed, Mar 15, 2023 at 07:32:41AM +0100, Christian Theune via
Openipmi-developer wrote:
> Hi,
>
> that didn’t apply on 5.10. Here’s what I’m currently trying to build after
> manually inspecting the rejected patch:
>
Well, I guess I should have sent the prerequisite patch, too. Her it
is:
FYI:
this patch applied on 5.10.174 and I can see the OEM strings now:
1 | 03/15/2023 | 09:53:50 | Event Logging Disabled SEL | Log area
reset/cleared | Asserted
2 | 03/15/2023 | 09:55:32 | OS Stop/Shutdown #0x73 | Run-time critical stop
| Asserted
3 | Linux kernel panic: sysrq trigg
Hi,
that didn’t apply on 5.10. Here’s what I’m currently trying to build after
manually inspecting the rejected patch:
ipmi-watchdog-set-panic-count-5.10.y.patch
Description: Binary data
> On 14. Mar 2023, at 18:29, Corey Minyard wrote:
>
> Well, dang, I had already fixed this a year and
On Tue, Mar 14, 2023 at 06:42:00PM +0100, Christian Theune via
Openipmi-developer wrote:
> Hi,
>
> ouch, sorry to hear that. I’ll test it with that patch and will ask for a
> backport to 5.10 after that. Is that something you’d do or should I contact
> the maintainers?
I've already requested
Hi,
ouch, sorry to hear that. I’ll test it with that patch and will ask for a
backport to 5.10 after that. Is that something you’d do or should I contact the
maintainers?
Christian
> On 14. Mar 2023, at 18:29, Corey Minyard wrote:
>
> Well, dang, I had already fixed this a year and a half
Well, dang, I had already fixed this a year and a half ago. I wish I
had a better memory.
Anyway, the fix is commit db05ddf7f321634c5659a0cf7ea56594e22365f7
("ipmi:watchdog: Set panic count to proper value on a panic") in
mainstream 5.16. I'm attaching that patch.
-corey
On Tue, Mar 14, 2023
Awesome!
> On 14. Mar 2023, at 15:54, Corey Minyard wrote:
>
> On Tue, Mar 14, 2023 at 03:22:39PM +0100, Christian Theune via
> Openipmi-developer wrote:
>> Hi,
>>
>> sorry, I didn’t expect you to make me a branch. I had already taken your
>> diff over to 5.10 as it applied cleanly … sorry
On Tue, Mar 14, 2023 at 03:22:39PM +0100, Christian Theune via
Openipmi-developer wrote:
> Hi,
>
> sorry, I didn’t expect you to make me a branch. I had already taken your diff
> over to 5.10 as it applied cleanly … sorry for the additional work and thanks
> anyways.
Ok, that's great. It's
Hi,
sorry, I didn’t expect you to make me a branch. I had already taken your diff
over to 5.10 as it applied cleanly … sorry for the additional work and thanks
anyways.
Here’s the output:
[ 6521.905890] sysrq: Trigger a crash
[ 6521.909294] Kernel panic - not syncing: sysrq triggered crash
[
On Mon, Mar 13, 2023 at 02:07:01PM +0100, Christian Theune wrote:
> Hi,
>
> yeah, the IPMI log is fine. This is a 10 minute interval job in our system
> that exports the log and clears it:
>
> The job looks like this:
>
> /nix/store/m7lb36dr93qj27r9vskmjihz8imywy86-ipmitool-1.8.18/bin/ipmitool
Hi,
yeah, the IPMI log is fine. This is a 10 minute interval job in our system that
exports the log and clears it:
The job looks like this:
/nix/store/m7lb36dr93qj27r9vskmjihz8imywy86-ipmitool-1.8.18/bin/ipmitool sel
elist
On Mon, Mar 13, 2023 at 10:27:51AM +0100, Christian Theune wrote:
> Hi,
>
> alright, so here’s the output from the NixOS machine:
>
> root@xxx ~ # echo c >/proc/sysrq-trigger
> client_loop: send disconnect: Broken pipe
> …
>
> root@xxx ~ # journalctl -u ipmi-log.service
> -- Journal begins at
Hi,
alright, so here’s the output from the NixOS machine:
root@xxx ~ # echo c >/proc/sysrq-trigger
client_loop: send disconnect: Broken pipe
…
root@xxx ~ # journalctl -u ipmi-log.service
-- Journal begins at Sun 2023-02-26 14:25:36 CET, ends at Mon 2023-03-13
10:25:27 CET. --
Mar 13 10:12:38
On Wed, Mar 01, 2023 at 06:00:07PM +0100, Christian Theune wrote:
> I’m going to actually attach a serial console to watch the “echo c” panic,
> maybe that gives _some_ indication.
>
> Otherwise: I can quickly run patches on the kernel there to try out things.
> (And the funding offer still
I’m going to actually attach a serial console to watch the “echo c” panic,
maybe that gives _some_ indication.
Otherwise: I can quickly run patches on the kernel there to try out things.
(And the funding offer still stands.)
Christian
> On 1. Mar 2023, at 17:58, Corey Minyard wrote:
>
> On
On Tue, Feb 28, 2023 at 06:36:17PM +0100, Christian Theune wrote:
> Thanks, both machines report:
>
> # cat /sys/module/ipmi_msghandler/parameters/panic_op
> string
At this point, I have no idea. I'd have to start adding printks into
the code and cause crashes to see what is happing.
Maybe
Thanks, both machines report:
# cat /sys/module/ipmi_msghandler/parameters/panic_op
string
> On 28. Feb 2023, at 18:04, Corey Minyard wrote:
>
> Oh, I forgot. You can look at panic_op in
> /sys/module/ipmi_msghandler/parameters/panic_op
>
> -corey
>
> On Tue, Feb 28, 2023 at 05:48:07PM
Oh, I forgot. You can look at panic_op in
/sys/module/ipmi_msghandler/parameters/panic_op
-corey
On Tue, Feb 28, 2023 at 05:48:07PM +0100, Christian Theune via
Openipmi-developer wrote:
> Hi,
>
> > On 28. Feb 2023, at 17:36, Corey Minyard wrote:
> >
> > On Tue, Feb 28, 2023 at 02:53:12PM
Hi,
> On 28. Feb 2023, at 17:36, Corey Minyard wrote:
>
> On Tue, Feb 28, 2023 at 02:53:12PM +0100, Christian Theune via
> Openipmi-developer wrote:
>> Hi,
>>
>> I’ve been trying to debug the PANIC and OEM string handling and am running
>> out of ideas whether this is a bug or whether
On Tue, Feb 28, 2023 at 02:53:12PM +0100, Christian Theune via
Openipmi-developer wrote:
> Hi,
>
> I’ve been trying to debug the PANIC and OEM string handling and am running
> out of ideas whether this is a bug or whether something so subtle has changed
> in my config that I’m just not seeing
23 matches
Mail list logo
