From: Jon Smirl <jonsmirl@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: sysdev_class use from DRM
Date: Fri, 24 Jun 2005 14:12:19 +0000 [thread overview]
Message-ID: <9e473391050624071263dfbea7@mail.gmail.com> (raw)
DRM has a model where it runs without attaching to the PCI device. It
is doing this because the framebuffer devices are already attached to
the device.
Some developers want to add power manager support to the DRM drivers.
Since the normal pm hooks are occupied they are doing this by creating
a sysdev_class.
static struct sysdev_class drm_sysdev_class = {
set_kset_name("drm"),
.resume = drm_resume,
.suspend = drm_suspend,
};
If I rmmod the modules before reboot I can reboot cleanly. But if the
modules are still loaded at reboot I get the following trap in sysdev.
I suspect this is because the kernel has already wiped out the
loadable drivers when sysdev shut down is happening. Can anyone
explain what is happening?
I could unregister the sysdev device via _exitcall() but the kernel
doesn't call _exitcall() in current builds. Meanwhile it just occurred
to me to mark these routines and structures _exit, I'll try that while
wait for a reply to this.
Don't tell me to merge DRM/fbdev, that fight has been going on for two
years now.
--
Jon Smirl
jonsmirl@gmail.com
EIP: 0060:[<c01fc398>] Not tainted VLI
EFLAGS: 00010246 (2.6.12)
EIP is at sysdev_shutdown+0xbd/0xd2
eax: 6b6b6b47 ebx: f9a904c0 ecx: 00000000 edx: 6b6b6b6b
esi: f9a904c0 edi: 6b6b6b47 ebp: f65e8e8c esp: f65e8e7c
ds: 007b es: 007b ss: 0068
Process reboot (pid: 8899, threadinfoö5e8000 taskÁa7e520)
Stack: f9a904dc c03280fc c03281cc 4f51bff4 f65e8e9c c01ffa64 28121969 01234567
f65e8fb4 c01272ce f7490d84 f7fa5180 00010800 f7fa5180 00000000 f65e8ed4
c0140f08 f1ea4a5c f7f68d80 00030800 f7f68d80 00000000 f65e8f00 c0142321
Call Trace:
[<c0103db8>] show_stack+0x7c/0x92
[<c0103f39>] show_registers+0x152/0x1ca
[<c0104136>] die+0xf4/0x16f
[<c01140cb>] do_page_fault+0x42f/0x654
[<c0103a2b>] error_code+0x4f/0x54
[<c01ffa64>] device_shutdown+0x74/0x78
[<c01272ce>] sys_reboot+0xf8/0x20f
[<c0102e43>] sysenter_past_esp+0x54/0x75
Code: 8d 42 bc 89 c6 eb 86 f0 ff 05 64 82 32 c0 0f 8e 3f 02 00 00 83 c4 04 5b 5e
5f 5d c3 8b 56 08 85 d2 75 17 8b 57 24 8d 42 dc 89 c7 <8b> 40 24 0f 18 00 90 3b
55 f0 e9 77 ff ff ff 89 f8 ff d2 eb e3
INIT: no more processes left in this runlevel
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id\x16492&opÌk
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2005-06-24 14:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-24 14:12 Jon Smirl [this message]
2005-06-24 19:21 ` sysdev_class use from DRM Jon Smirl
2005-06-24 21:08 ` Dmitry Torokhov
2005-06-30 17:40 ` Greg KH
2005-06-30 20:55 ` Jon Smirl
2005-07-01 22:23 ` Greg KH
2005-07-01 23:18 ` Jon Smirl
2005-07-02 5:05 ` Greg KH
2005-07-02 13:34 ` Jon Smirl
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=9e473391050624071263dfbea7@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=linux-hotplug@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).