linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josep Lladonosa <jlladono@gmail.com>
To: Thomas Richter <richter@rus.uni-stuttgart.de>
Cc: Alan Stern <stern@rowland.harvard.edu>, linux-kernel@vger.kernel.org
Subject: Re: [HANG] Trouble with NEC-based USB adapter in PCMCIA slot on E7110
Date: Sat, 10 Aug 2013 21:58:28 +0200	[thread overview]
Message-ID: <CAPBO7TYBWg-vyX3YocGZ94ALbiZC7E-1TWr5zndPob_xyPvqTQ@mail.gmail.com> (raw)
In-Reply-To: <520699F2.7080808@rus.uni-stuttgart.de>

On 10 August 2013 21:52, Thomas Richter <richter@rus.uni-stuttgart.de> wrote:
> Hi Josep,
>
>
>> Have you tried to wait for 5 minutes? It could also be related to it
>> what happens to my kernel 3.11.0-rc4 (and rc3) and USB
>>
>> I plug the drive. Only after 5 minutes of high-speed of USb bus, it
>> mounts.
>
>
> No, currently I don't even depend on gnome mounting it. I don't run a
> desktop. I just mount it manually in the single user mode with "mount"
> (eliminates variables that is). If I mount it, it first looks ok. Then I
> write a file on it. Still looks ok. Then I call "sync". That finally locks
> it up with the 2.6.32 kernel, not on 2.6.31. For the .32, it just sits
> there, after probably twenty seconds, it times out, complains that it can't
> write, then dies away. Works just nicely with the .31 kernel.
>

Perhaps both cases are related, and if you waited after those 5
minutes of resets, your pen would work fine...
Have you checked your /var/log/messages after insertion of pen?

My automount is under XFCE, not Gnome... ;)

Josep


> Thus, at this time, I guess I would need to know more about how a write
> reaches the ehci module, and how the configuration from there works.
>
> Sorry, but this isn't quite as simple as I thought.
>
> Thanks,
>         Thomas



-- 
--
Salutacions...Josep
--

  reply	other threads:[~2013-08-10 19:58 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-09  6:00 [HANG] Trouble with NEC-based USB adapter in PCMCIA slot on E7110 Thomas Richter
2013-08-09 17:46 ` Alan Stern
2013-08-09 19:29   ` Thomas Richter
2013-08-09 19:35     ` Alan Stern
2013-08-09 23:14       ` Thomas Richter
2013-08-10  1:07         ` Alan Stern
2013-08-10  8:36           ` Thomas Richter
2013-08-10 11:26           ` Thomas Richter
2013-08-10 12:04             ` Alan Stern
2013-08-10 19:04               ` Josep Lladonosa
2013-08-10 19:52                 ` Thomas Richter
2013-08-10 19:58                   ` Josep Lladonosa [this message]
2013-08-10 20:03                     ` Josep Lladonosa
2013-08-10 20:05                       ` Thomas Richter
2013-08-10 20:05                     ` Thomas Richter
2013-08-11  1:40                 ` Alan Stern
2013-08-10 19:48               ` Thomas Richter
2013-08-11  1:46                 ` Alan Stern
2013-08-11  8:51                   ` Thomas Richter
2013-08-11 13:27                   ` Thomas Richter
2013-08-11 17:24                   ` [PCMCIA] Solved: No USB 2.0 (ehci) " Thomas Richter
2013-08-12 21:25                     ` Andreas Mohr
2013-08-13  5:57                       ` Tomas Kovacik

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=CAPBO7TYBWg-vyX3YocGZ94ALbiZC7E-1TWr5zndPob_xyPvqTQ@mail.gmail.com \
    --to=jlladono@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richter@rus.uni-stuttgart.de \
    --cc=stern@rowland.harvard.edu \
    /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;
as well as URLs for NNTP newsgroup(s).