Re: USB regression (and other failures) in 2.6.2[45]*

[Andrew Buehler]

On 2/16/2008 10:35 PM, Alan Stern wrote:

> On Sat, 16 Feb 2008, Andrew Buehler wrote:
>
> > Messages sent to my address directly are explicitly not filtered
> > into the folders I have set up for various mailing lists, so that
> > if someone does send me a "heads up" reply for a specific topic on
> > a list to which I am subscribed it does not get caught by the list
> > filter and fail to come to my attention. If a message fails to be
> > filtered into any mailing-list folder, then I should be able to
> > conclude that it is specifically intended for me, and not part of
> > normal mailing-list traffic. The practice of sending replies to
> > both addresses renders this an invalid conclusion. I do not think
> > that it is unreasonable to expect that conclusion to be valid.
>
> It's not unreasonable.  Neither is Aristotelian physics.
> Nevertheless, neither one is a good match to reality.
>
> Why not arrange instead that messages sent from a mailing list server
> _do_ get filtered into the corresponding folder, even if they were
> also sent to your address?  This certainly should make your
> assumption (that messages not filtered into any mailing-list folder
> are specifically intended for you) much more valid than it is now.

Two reasons that I can think of off the top of my head.

One of them I mentioned above: because that precludes the possibility of
someone sending me a direct copy to draw my attention to something which
they think needs it, unless they send it separately from the list copy.
(This does not especially apply on the kernel-related mailing lists,
since no one is likely to think I am particularly worth drawing in to
any discussion there anytime soon, but it has come up elsewhere and the
basic principle is the same.)

The other is that this would lead to duplicate copies of the same reply
in the mailing list folder, which is ugly at best, especially with
respect to proper threading.

> > Until this thread, I was not even aware that ACPI was related to
> > USB; I had largely conflated it with a similar acronym which I
> > think is related to power management and which I can suddenly not
> > even find in my kernel config. I will, however, look into
> > linux-acpi.
>
> ACPI isn't directly related to USB; rather it has to do with
> transferring information between the OS and the 
> BIOS/vendor-specific-hardware.  Power management is example where
> such a transfer is needed.  In your case, the relevant information is
> which IRQ is connected to which motherboard device.  If you don't
> have ACPI enabled in your configuration, then perhaps that's the
> problem -- try enabling it.

It is indeed not enabled, and when I check the config for the 2.6.23.1
kernel where USB works, I find that it is enabled there. I will test the
result of enabling it in the current kernel. If I don't have an answer
by the end of the day, I probably won't be able to get one until at
least Tuesday.

> > That will not be helpful for the other two problems, however, since
> > neither of them was ever working as far as I am aware. That also
> > leaves me hesitant to conclude that they are rooted in the same IRQ
> > issue as the USB problem appears to be.
>
> Maybe they aren't.  But when you have multiple bugs, you have to fix
> them one at a time.

Oh, I agree - that is a large part of why I posted a "full" description
of only one problem initially, rather than all three in a single mail.

--
   Andrew Buehler
--
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/