I've been able to resolve this problem. Thanks for those who helped. The problem was simply that after rebuilding the kernel with KGDB, I did not rebuild the driver modules. I guess when the init code tried to call misc_register, well, it didn't. Surprised it didn't crash outright, but it happily loaded itself, just never registered. Rich -----Original Message----- From: Kay Sievers [mailto:kay.sievers@xxxxxxxx] Sent: Wed 1/28/2009 9:20 AM To: Richard Schmitt Cc: linux-hotplug@xxxxxxxxxxxxxxx Subject: Re: Odd behavior with udev and kgdb On Wed, Jan 28, 2009 at 15:12, Richard Schmitt <rschmitt@xxxxxxxxxxx> wrote: > > fpga is our own driver. The driver does call misc_register at the beginning of it's init call. It seems that this routine should create the /sys/class/misc/fpga entry. > > The odd thing is that there is a /sys/module/fpga entry, just not the /sys/class/misc/fpga entry. > > Also a cat of /proc/modules shows the driver as loaded. > > I'll trace through the misc_register function a bit and see if there's something strange going on. > > Keep in mind, that when kgdb is not configured, things work fine. It's only when kgdb is configured that the device node doesn't appear. You have the code of your driver somewhere to look at it? Kay -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
