mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Philipp Matthias Hahn <pmhahn@titan.lahn.de>
To: Holger Kiehl <Holger.Kiehl@dwd.de>
Cc: LKML <linux-kernel@vger.kernel.org>, Corey Minyard <minyard@mvista.com>
Subject: Re: IPMI hangup in 2.6.6-rc3
Date: Tue, 25 May 2004 18:53:36 +0200	[thread overview]
Message-ID: <20040525165335.GA28905@titan.lahn.de> (raw)
In-Reply-To: <Pine.LNX.4.58.R0405040649310.15047@praktifix.dwd.de>

Hi Holger, Corey, LKML!

On Tue, May 04, 2004 at 07:05:12AM +0200, Holger Kiehl wrote:
> When compiling in IPMI (not as modules) my system hangs just after
> it prints out detection of IPMI. 2.6.5 did work fine. Compiling
> it as a module and inserting it with modprobe causes modprobe
> to hang in D state, there is nothing unusual in /var/log/messages:
> 
> May  4 08:46:34 apollo kernel: ipmi message handler version v31
> May  4 08:46:34 apollo kernel: IPMI System Interface driver version v31, KCS version v31, SMIC version v31, BT version v31
> May  4 08:46:34 apollo kernel: ipmi_si: Found SMBIOS-specified state machine at I/O address 0xca2
> May  4 08:54:14 apollo kernel: ipmi device interface version v31

Same for me on one of our single Xeon with 2.6.7-rc1. Using SysRq-T I
was able to track it somehow down to the following situation:

modprobe      D C201AD20     0  3735   2415                     (NOTLB)
f6b51f0c 00000082 00000000 c201ad20 c201a0a0 00008124 00000002 00000000
       f7c03000 f6b51ee4 f8bda434 c04b5dc0 c201ad20 00000000 00000000 8ce9c0c0
       000f431a c03b8d80 f75fccd0 f75fce80 00000246 00000003 f6b50000 f7c03000
Call Trace:
 [<f8bdb46d>] ipmi_register_smi+0x22a/0x386 [ipmi_msghandler]
 [<f8b570a6>] init_one_smi+0x1e6/0x4c2 [ipmi_si]
 [<f8b270c2>] init_ipmi_si+0xc2/0x203 [ipmi_si]
 [<c0137910>] sys_init_module+0x116/0x24d
 [<c0106053>] syscall_call+0x7/0xb

modprobe hangs at linux-2.6.7-rc1/drivers/char/ipmi/ipmi_msghandler.c:1727
	wait_event((*intf)->waitq, ((*intf)->curr_channel>=IPMI_MAX_CHANNELS));

This event should be fired by channel_handler(), but isn't for some
unknown reason. I verified this by adding some printk() there, which
wheren't shown.

When I tried a 2.4 kernel with the patches from openipmi.sf.net, I
was somehow able to use IPMI, but got into problems later.

Any idea, what I can do to track the problem further down?

BYtE
Philipp
-- 
  / /  (_)__  __ ____  __ Philipp Hahn
 / /__/ / _ \/ // /\ \/ /
/____/_/_//_/\_,_/ /_/\_\ pmhahn@titan.lahn.de

       reply	other threads:[~2004-05-25 16:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.58.R0405040649310.15047@praktifix.dwd.de>
2004-05-25 16:53 ` Philipp Matthias Hahn [this message]
2004-06-04 20:59   ` Corey Minyard
2004-06-10 17:12     ` Alex Williamson
2004-06-16 12:32       ` Holger Kiehl
2004-06-16 14:19         ` Corey Minyard
2004-06-16 14:21           ` Corey Minyard
2004-06-16 14:44             ` Alex Williamson
2004-06-16 18:30             ` Holger Kiehl
2004-06-16 18:56               ` Holger Kiehl
2004-06-16 20:42                 ` Corey Minyard
2004-06-16 20:54                   ` Alex Williamson
2004-06-17  7:03                   ` Holger Kiehl
2004-05-04  7:05 Holger Kiehl

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=20040525165335.GA28905@titan.lahn.de \
    --to=pmhahn@titan.lahn.de \
    --cc=Holger.Kiehl@dwd.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minyard@mvista.com \
    /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

all inboxes | Powered by JetHome®