On Tue, Mar 15, 2016 at 11:28:36AM -0700, Jeremiah Rothschild wrote:
On Tue, Mar 15, 2016 at 11:27:13AM -0700, Jeremiah Rothschild wrote:
I can't find the command in my `history' anymore but, IIRC, the command was something like:
modprobe ipmi_si trydefaults=0
Err, sorry. trydefaults=1. That then kicked off the kernel errors to syslogd.
While the effects are similar, it does look like a different bug.
The kernel stack trace for this is:
[13964.588032] [<fffffdfffc4300a0>] port_inb+0x3c/0x50 [ipmi_si] [13964.593756] [<fffffdfffc434bdc>] kcs_detect+0x28/0x40 [ipmi_si] [13964.599654] [<fffffdfffc43231c>] try_smi_init+0x184/0x938 [ipmi_si] [13964.605897] [<fffffdfffc434870>] init_ipmi_si+0x788/0xa48 [ipmi_si] [13964.612133] [<fffffe000008430c>] do_one_initcall+0xcc/0x1c0 [13964.617678] [<fffffe00001b0db8>] do_init_module+0x68/0x1c8 [13964.623137] [<fffffe0000134548>] load_module+0xf3c/0x11b8 [13964.628507] [<fffffe00001349f4>] SyS_finit_module+0xa0/0xc8 [13964.634050] [<fffffe0000083a8c>] __sys_trace_return+0x0/0x4
As it is different, and I can reproduce it, I reported another bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1318057
Rich.