Re: can we move USB_DEVICEFS to non-embedded?

[Dave Airlie]

On Wed, Jun 24, 2009 at 1:39 AM, Greg KH<gregkh@xxxxxxx> wrote:
> On Tue, Jun 23, 2009 at 11:29:50PM +0800, Jeff Chua wrote:
>> On Tue, Jun 23, 2009 at 10:42 PM, Greg KH<gregkh@xxxxxxx> wrote:
>> > On Tue, Jun 23, 2009 at 01:11:51PM +0800, Jeff Chua wrote:
>> >> commit cc71329b3b89b4a5be849b617f2c4f151f0b9213 moved USB_DEVICEFS to
>> >> be embedded and marked it as depreciated. Can this be reverted? This
>> >> breaks vmware and those systems not using udev.
>>
>> > vmware now works properly with this fix, and has for over a year or so.
>>
>> vmware is working, but can't detect USB devices.
>
> Odd, what version of vmware are you using?
>
>> > What distro does not use udev or mdev or something like it already and
>> > also does not use an updated libusb?
>> > We need some specifics here please.
>>
>> I'm not using it and have been fine without it all these while, so
>> don't see any gain moving to udev or perhaps it's time to consider ...
>
> If you are running your own custom distro/install, then you should be
> able to select CONFIG_EMBEDDED and then USB_DEVICEFS just fine on your
> own.  But note, that you don't sound like the "normal" user at all :)
>

Okay can we revert this for a better reason? it seems to have unhidden a race
condition on booting some of my machines. I've booted some other machines
with the same USB disk and the same kernel fine. The two machines it so far
has turned up issues on are an AMD 1Ghz Athlon with SIS chipset, the other is
an Intel Celeron CPU with a AMD rc410 chipset.

If I take a stock F11 distro, and build 2.6.31-rc2 on a USB HDD root,
I can't boot
I'm not quite sure if something in the F11 initrd needs usbfs for
something (cc'ed Peter)

The same hang happens if I boot a 2.6.30 kernel with an F11 initrd and
with usbfs turned off.

Also for reference all rawhide kernels fail to boot on the same F11 system.

I haven't tried using a rawhide initrd due to rawhide being a bit
unusable at the moment.

Dave.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/