linux-kernel - 3.1-rc9: IPMI Bug in 3.x++ [kipmi utilizes 100% CPU until ipmitool sel clear is issued[

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.02.1110142010580.7699@p34.internal.lan>
Date:	Fri, 14 Oct 2011 20:13:52 -0400 (EDT)
From:	Justin Piszcz <jpiszcz@...idpixels.com>
To:	linux-kernel@...r.kernel.org
Subject: 3.1-rc9: IPMI Bug in 3.x++ [kipmi utilizes 100% CPU until ipmitool
 sel clear is issued[

Hi,

Kernel: 3.1-rc9 on x86-64

   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
  1203 root      39  19     0    0    0 R  100  0.0   3693:29 kipmi0

I have a supermicro board in a non-supermico chassis and it keeps alerting
that there is a chassis intrusion, when it fills up this process goes to
100%, when I run ipmitool sel clear, it goes back to 0-1%.

# ipmitool sel clear

Then--

   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
  1203 root      39  19     0    0    0 S    0  0.0   3695:26 kipmi0

Would LKML consider this a kernel bug, shouldn't it just discard future
incoming events/and/or treat/handle it differently rather than using 100%
of the CPU?

Justin.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/