From: Robert Reif <reif@earthlink.net>
To: sparclinux@vger.kernel.org
Subject: sparc-next RTC BUG: sleeping function called from invalid context
Date: Thu, 25 Sep 2008 01:27:40 +0000 [thread overview]
Message-ID: <48DAE90C.7010608@earthlink.net> (raw)
I'm getting this repeatable BUG from sparc-next with almost all
kernel debugging options turned on shortly after booting:
Sep 24 21:19:45 ss20-1 kernel: BUG: sleeping function called from
invalid context at kernel/mutex.c:88
Sep 24 21:19:45 ss20-1 kernel: in_atomic():1, irqs_disabled():1
Sep 24 21:19:45 ss20-1 kernel: [f015c2bc : rtc_class_open+0x1c/0x7c ]
[f001b034 : timer_interrupt+0xc0/0x138 ] [f0017340 :
handler_irq+0xdc/0x148 ] [f0014774 : patch_handler_irq+0x0/0x24 ]
[f0018bb0 : cpu_idle+0x2c/0x38 ] [f001ddd8 : smp_do_cpu_idle+0x0/0x10 ]
[00000000 : 0x0 ]
Sep 24 21:19:45 ss20-1 kernel: ------------[ cut here ]------------
Sep 24 21:19:45 ss20-1 kernel: WARNING: at kernel/mutex.c:135
__mutex_lock_slowpath+0x44/0x238()
Sep 24 21:19:45 ss20-1 kernel: Modules linked in: ipv6 lp parport
sunlance sunhme loop sermouse evdev ext3 jbd sg sr_mod sd_mod cdrom
sun_esp esp_scsi scsi_transport_spi scsi_mod
Sep 24 21:19:45 ss20-1 kernel: [f0146710 : class_find_device+0x48/0xe8 ]
[f015c2bc : rtc_class_open+0x1c/0x7c ] [f001b034 :
timer_interrupt+0xc0/0x138 ] [f0017340 : handler_irq+0xdc/0x148 ]
[f0014774 : patch_handler_irq+0x0/0x24 ] [f0018bb0 : cpu_idle+0x2c/0x38
] [f001ddd8 : smp_do_cpu_idle+0x0/0x10 ] [00000000 : 0x0 ]
Sep 24 21:19:45 ss20-1 kernel: ---[ end trace 46346a150b775121 ]---
Let me know if you need more info.
next reply other threads:[~2008-09-25 1:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-25 1:27 Robert Reif [this message]
2008-09-25 1:48 ` sparc-next RTC BUG: sleeping function called from invalid David Miller
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=48DAE90C.7010608@earthlink.net \
--to=reif@earthlink.net \
--cc=sparclinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.