From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Jeroen Roovers <jer@gentoo.org>
Cc: linux-parisc@vger.kernel.org, Rolf Eike Beer <eike@sf-mail.de>
Subject: Re: Short notice: ipmi_si kills C8000
Date: Tue, 29 Oct 2013 10:37:06 +0100 [thread overview]
Message-ID: <20131029093706.GA6255@alpha.franken.de> (raw)
In-Reply-To: <20131028105612.GB19852@alpha.franken.de>
On Mon, Oct 28, 2013 at 11:56:12AM +0100, Thomas Bogendoerfer wrote:
> On Sat, Oct 26, 2013 at 07:17:20PM +0200, Jeroen Roovers wrote:
> > > I did "modprobe ipmi_si" on my C8000 (kernel 3.11.6), which
> > > immediately broke the machine. I have no backtrace yet, but I'll try
> > > to get one next week. In case someone has such a machine and the mood
> > > to debug this already??? ;)
> >
> > [ 730.964000] ipmi message handler version 39.2
> > [ 731.092000] IPMI System Interface driver.
> > [ 731.148000] ipmi_si: Adding default-specified kcs state
> > machine[ 731.224000] ipmi_si: Trying default-specified kcs state
> > machine at i/o address 0xca2, slave address 0x0, irq 0 <Cpu0>
>
> looks like stupid ISA auto probing is turned on, when ipmi is loaded
> as a module :-( I'll have a look.
my patch went into 3.12-rc1 so it's expected that 3.11.6 crashes without it.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2013-10-29 9:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-26 14:26 Short notice: ipmi_si kills C8000 Rolf Eike Beer
2013-10-26 17:17 ` Jeroen Roovers
2013-10-28 10:56 ` Thomas Bogendoerfer
2013-10-29 9:37 ` Thomas Bogendoerfer [this message]
2013-10-29 10:41 ` Rolf Eike Beer
2013-10-29 16:41 ` Thomas Bogendoerfer
2013-10-29 17:14 ` Jeroen Roovers
2013-10-29 19:50 ` Helge Deller
2013-10-31 12:06 ` Thomas Bogendoerfer
2013-10-31 12:22 ` Helge Deller
2013-11-02 16:18 ` John David Anglin
2013-10-31 21:40 ` Rolf Eike Beer
2013-11-05 12:23 ` Rolf Eike Beer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131029093706.GA6255@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=eike@sf-mail.de \
--cc=jer@gentoo.org \
--cc=linux-parisc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox