udevid segfaulting
Bruce Dubbs
bruce.dubbs at gmail.com
Sat Oct 27 18:23:36 MDT 2007
Bruce Dubbs wrote:
> Matthew Burgess wrote:
>> Hi,
>>
>> I've just built an SVN version of LFS, along with several package updates (everything in Trac besides grep, texinfo and udev). I'm getting the following on bootup:
>>
>> Oct 27 20:58:24 kyoto kernel: usb_id[937]: segfault at 00000000 eip b7e32564 esp bf941360 error 4
>> Oct 27 20:58:24 kyoto kernel: usb_id[938]: segfault at 00000000 eip b7e43564 esp bf97c390 error 4
>> Oct 27 20:58:24 kyoto kernel: usb_id[939]: segfault at 00000000 eip b7e59564 esp bf8a1ac0 error 4
>> Oct 27 20:58:24 kyoto kernel: usb_id[950]: segfault at 00000000 eip b7e2f564 esp bfcf0710 error 4
>> Oct 27 20:58:24 kyoto kernel: usb_id[951]: segfault at 00000000 eip b7ecd564 esp bfe858a0 error 4
>>
>> Has anyone seen anything similar before, or might this be down to GCC-4.2.2 or Glibc-2.7 upgrades? Is there any way of debugging these segfaults earlier (for example, can I check what arguments udev_id was being passed to so I might be able to attach gdb to the problematic process and get a full stacktrace)?
>
> I haven't, but the internet has. Google for: kernel usb_id segfault
>
> It looks like a kernel driver problem.
After a little more looking, the kernel guys think it us a udev problem.
Try backing off on the udev version.
-- Bruce
More information about the lfs-dev
mailing list