On Fri, 1 Oct 2004, martin f krafft wrote: > also sprach Alan Stern <[EMAIL PROTECTED]> [2004.10.01.2113 +0200]: > > No, you should use usbcore.ko. > > Okay, that worked. > > Now, the function starts at 0x5320, so +0x74 (from the oops) gives > 0x5394... so with +/- 5 lines of context: > > 0x0000537e <hcd_endpoint_disable+94>: movl $0x0,0x44(%edx,%edi,4) > 0x00005386 <hcd_endpoint_disable+102>: mov $0xffffe000,%ecx > 0x0000538b <hcd_endpoint_disable+107>: and %esp,%ecx > 0x0000538d <hcd_endpoint_disable+109>: incl 0x14(%ecx) > 0x00005390 <hcd_endpoint_disable+112>: mov 0x18(%esp),%eax > 0x00005394 <hcd_endpoint_disable+116>: mov 0x8(%eax),%edx > 0x00005397 <hcd_endpoint_disable+119>: lea 0xfffffff4(%edx),%ebx > 0x0000539a <hcd_endpoint_disable+122>: mov 0xc(%ebx),%eax > 0x0000539d <hcd_endpoint_disable+125>: lea 0x0(%eax),%eax > 0x000053a1 <hcd_endpoint_disable+129>: cmp %ebp,%edx > 0x000053a3 <hcd_endpoint_disable+131>: je 0x53d2 <hcd_endpoint_disable+178> > > The full dump is at > > ftp://ftp.madduck.net/scratch/hcd_endpoint_disable.disass.bz2 > > This is completely beyond me at this point. :(
Don't worry, your disassembly gave the answer we needed. For whatever reason (I don't have time to go searching for it now), in hcd_endpoint_disable the udev->hcpriv value stored in dev is a NULL pointer. Of course that's not supposed to happen. Is this reproducible? What happens if you do "rmmod uhci-hcd" yourself by hand, without involving the hotplug programs? Alan Stern ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
