From: Andrew Morton <akpm@osdl.org>
To: Marc Koschewski <marc@osknowledge.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: BUG: soft lockup detected on CPU#0!
Date: Thu, 1 Jun 2006 18:54:35 -0700 [thread overview]
Message-ID: <20060601185435.b329b6d1.akpm@osdl.org> (raw)
In-Reply-To: <20060602010223.GA9460@stiffy.osknowledge.org>
On Fri, 2 Jun 2006 03:02:24 +0200
Marc Koschewski <marc@osknowledge.org> wrote:
> here what I got when I connected my mobile phone via gnome-phone-manager and a
> bluetooth PCMCIA adapter. The machine freezes when I connect and attached is
> what dmesg says after I ejected the card. The card had /dev/ttyS3 assigned and I
> used it as my setting in gnome-phone-manager.
>
> [4296372.670000] BUG: soft lockup detected on CPU#0!
> [4296372.670000] [<b0138e29>] softlockup_tick+0x7e/0xbb
> [4296372.670000] [<b0120cdc>] update_process_times+0x2a/0x60
> [4296372.670000] [<b01063ec>] timer_interrupt+0x3a/0xce
> [4296372.670000] [<b0138efd>] handle_IRQ_event+0x2e/0x5a
> [4296372.670000] [<b0138fb2>] __do_IRQ+0x89/0x127
> [4296372.670000] [<b0105099>] do_IRQ+0x6f/0x8b
> [4296372.670000] [<b0103816>] common_interrupt+0x1a/0x20
> [4296372.670000] [<f8e74986>] yenta_interrupt+0x11/0xb7 [yenta_socket]
> [4296372.670000] [<b0138efd>] handle_IRQ_event+0x2e/0x5a
> [4296372.670000] [<b0138fb2>] __do_IRQ+0x89/0x127
> [4296372.670000] [<b010507d>] do_IRQ+0x53/0x8b
> [4296372.670000] =======================
> [4296372.670000] [<f9434c29>] rm_isr_bh+0x61/0x68 [nvidia]
> [4296372.670000] [<b0103816>] common_interrupt+0x1a/0x20
> [4296372.670000] [<b011cfa3>] __do_softirq+0x37/0x92
> [4296372.670000] [<b0105104>] do_softirq+0x4f/0x5b
> [4296372.670000] =======================
> [4296372.670000] [<b011d0e2>] irq_exit+0x38/0x3a
> [4296372.670000] [<b0105084>] do_IRQ+0x5a/0x8b
> [4296372.670000] [<b0103816>] common_interrupt+0x1a/0x20
> [4296372.670000] [<b023ac57>] serial_out+0x29/0x5f
> [4296372.670000] [<b023cd08>] serial8250_startup+0x18e/0x4e8
> [4296372.670000] [<b0238b9e>] uart_startup+0x3c/0x177
> [4296372.670000] [<b0238dad>] uart_open+0xd4/0x4af
> [4296372.670000] [<b0225b42>] check_tty_count+0x45/0xbb
> [4296372.670000] [<b02c28a2>] __mutex_unlock_slowpath+0xd0/0x218
> [4296372.670000] [<b022865d>] tty_open+0x163/0x328
It might be a hang in rm_isr_bh(). Does the same happen if the nvidia
driver is not, and has never been loaded?
next prev parent reply other threads:[~2006-06-02 1:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-02 1:02 Marc Koschewski
2006-06-02 1:04 ` Marc Koschewski
2006-06-02 1:54 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-25 19:41 Christoph Pfister
2007-07-27 19:30 ` Michal Piotrowski
2007-07-27 20:04 ` Christoph Pfister
2007-08-07 8:49 ` Christoph Pfister
2007-07-14 11:19 CIJOML
2007-05-09 12:41 Ralf Hildebrandt
2006-05-11 17:33 Linux 2.6.16.16 Chris Wright
2006-05-11 18:03 ` BUG: soft lockup detected on CPU#0! Winn Johnston
2006-05-12 15:51 ` Winn Johnston
2006-03-05 12:26 Norbert Wegener
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=20060601185435.b329b6d1.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc@osknowledge.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
all inboxes | Powered by JetHome®