linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Richter <richter@rus.uni-stuttgart.de>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux@brodo.de, linux-kernel@vger.kernel.org
Subject: Re: [HANG] Trouble with NEC-based USB adapter in PCMCIA slot on E7110
Date: Sat, 10 Aug 2013 13:26:11 +0200	[thread overview]
Message-ID: <52062353.9030800@rus.uni-stuttgart.de> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1308092103320.23882-100000@netrider.rowland.org>

Hi Alan,

later... ok, bisected this even more. 2.6.31.14 kernel, old udev works 
fine. Then removed /etc/rcS.d/S02udev to be sure the 2.6.32 kernel would 
not pull the new udev. Rebuild 2.6.32.1 with *identical* kernel 
configuration, booted up, manually started the *old* udev as in 
2.6.31.14, and tried whether it worked.

Did not.

Thus: it is neither the udev configuration, nor the udev userspace 
program, nor the kernel configuration.

Something must be screwed in the kernel space. Which is interesting 
since 2.6.32.1 is actually older than 2.6.31.14 (but the older 2.6.31.6 
works, too, and younger 2.6.32.6 doesn't work either).

As said, configuration of 2.6.32.1 and 2.6.31.14 is the same.

Which modules are relevant for handling the communication with the 
device, and where would you suggest to start looking? I assume 
yenta_socket is one thing for the cartbus adapter, then we have ehci_hcd 
and ehci_pci. Do I assume correctly that we can rule out the ohci_hcd 
module since that is not involved? What about other usb modules? I would 
probably need a short recap on through which modules the user data flows 
before the write is triggered, and which modules are involved in the 
configuration of the NEC ehci host adapter.

Thanks,
	Thomas

  parent reply	other threads:[~2013-08-10 11:26 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 [this message]
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
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=52062353.9030800@rus.uni-stuttgart.de \
    --to=richter@rus.uni-stuttgart.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@brodo.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).