linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Kosina <jikos@jikos.cz>
To: Kristen Carlson Accardi <kristen.c.accardi@intel.com>,
	Len Brown <len.brown@intel.com>, Andrew Morton <akpm@osdl.org>
Cc: linux-acpi@intel.com, linux-kernel@vger.kernel.org
Subject: ACPI bay - 2.6.20-rc3-mm1 hangs on boot
Date: Fri, 5 Jan 2007 14:19:41 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0701051351200.16747@twin.jikos.cz> (raw)

Hi,

2.6.20-rc3-mm1 hangs on boot on my IBM T42p when compiled with ACPI_BAY=y. 
Below is the trace of two BUGs I get.

When compiled with ACPI_BAY=n, it boots fine.

The traces are hand-rewritten (no serial console on that machine), so I 
have omitted the code offsets in the stacktraces.

ACPI: ACPI Dock Station Driver
ACPI: \_SB_PCI0.IDE0.SCND.MSTR: found ejectable bay
ACPI: \_SB_PCI0.IDE0.SCND.MSTR: Adding notify handler
PM: Adding info for platform:bay.0
ACPI: Bay [\_SB_.PCI0.IDE0.SCND.MSTR] Added
BUG: at lib/kref.c:32 kref_get()
	kref_get+0x34/0x3b
	kobject_get+0xf/0x13
	get_bus+0xe/0x1d
	bus_add_driver+0x13/0x165
	init_waitqueue_head+0x12/0x1e
	bay_init+0x57/0x79
	find_bay+0x0/0x2c4
	init+0x88/0x16d
	restore_nocheck+0x12/0x15
	init+0x0/0x16d
	init+0x0/0x16d
	kernel_thread_helper+0x7/0x10
	==========
BUG: at lib/kref.c:32 kref_get()
	kref_get+0x34/0x3b
	kobject_get+0xf/0x13
	kobject_init+0x5d/0x70
	kobject_set_name+0x5c/0x92
	bus_add_driver+0x50/0x79
	bay_init+0x57/0x79
	find_bay+0x0/0x2c4
	init+0x88/0x16d
	init+0x88/0x16d
	kernel_thread_helper+0x7/0x10
	=========

-- 
Jiri Kosina

             reply	other threads:[~2007-01-05 13:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-05 13:19 Jiri Kosina [this message]
2007-01-05 14:33 ` ACPI bay - 2.6.20-rc3-mm1 hangs on boot Henrique de Moraes Holschuh
2007-01-05 15:13   ` Jiri Kosina
2007-01-05 15:51     ` Henrique de Moraes Holschuh
2007-01-05 15:55       ` Jiri Kosina
2007-01-06  7:55 ` Pavel Machek
2007-01-08 21:07 ` Kristen Carlson Accardi

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=Pine.LNX.4.64.0701051351200.16747@twin.jikos.cz \
    --to=jikos@jikos.cz \
    --cc=akpm@osdl.org \
    --cc=kristen.c.accardi@intel.com \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@intel.com \
    --cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).