From: Andreas Mohr <andi@lisas.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Subject: [YASB] Re: Linux 3.7-rc7
Date: Mon, 3 Dec 2012 20:33:10 +0100 [thread overview]
Message-ID: <20121203193310.GA32762@rhlx01.hs-esslingen.de> (raw)
In-Reply-To: <CA+55aFyetqyMa2BQu7kE=cqFdAysUh9gV=O5as5Chgg1EMCW7g@mail.gmail.com>
Hello,
JFYI: Yet Another Suspend Breakage, it seems (hopefully someone
can contribute to and further nail down this issue).
Working:
vmlinuz-3.7.0-rc5-00068-gc5e35d6 (HEAD possibly unknown?)
Failing:
vmlinuz-3.7.0-rc7-00179-g2db18aa (HEAD 3c46f3d6406b1d0c53575774b2d1fd013cd7f76f)
Athlon XP 32bit VIA 8K5A2+.
Florian Fainelli (1):
x86/ce4100: Fix pm_poweroff
sounds like it *might* happen to be a candidate (I could try to add a
revert on top, of certain likely candidates).
I started some initial pm debugging (Documentation/power/basic-pm-debugging.txt), and it started hanging once progressing from "devices" to "platform"
in /sys/power/pm_test .
I could do more invasive debugging (and unloading modules at random, too),
however given that I'm currently spending almost days
debugging my third(!) non-working USB storage device in one year,
I'm somewhat less inclined.
As a side note, support status in (admittedly terribly complex,
and certainly very challenging given Windows' usual dirty non-spec tricks
in this area as well) USB storage areas seems to be nothing short of *terrible*.
At the current rate, there's an almost one-in-three chance to end up
with a dud when shopping for storage devices, it seems.
This situation should DEFINITELY see improvement,
ideally via a concerted effort (and finally get those lazy vendors
involved, too!).
It really cannot be that hard to buy devices at random
and plug into a large selection of random hardware
to verify that everything works in a most compatible way!!
Internet forums are full of stories about device failures on *Linux*,
with some of the usual recommendations being
"oh yeah, you need to disable ehci_hcd" (what a terrible "workaround")
or "use irqpoll" (dito)
[none of which helped in my two remaining cases].
So, all the usual problems (suspend breakage, USB storage) alive and kicking...
</rant>
</asbestos>
Crawling back into my corner,
Andreas Mohr
--
GNU/Linux. It's not the software that's free, it's you.
next prev parent reply other threads:[~2012-12-03 19:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-26 4:21 Linus Torvalds
2012-12-03 19:33 ` Andreas Mohr [this message]
2012-12-03 19:39 ` [YASB] " Linus Torvalds
2012-12-03 19:48 ` Andreas Mohr
2012-12-04 7:26 ` Andreas Mohr
2012-12-05 21:48 ` Andreas Mohr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121203193310.GA32762@rhlx01.hs-esslingen.de \
--to=andi@lisas.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®