public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Udo van den Heuvel <udovdh@xs4all.nl>
To: linux-usb@vger.kernel.org
Cc: Alan Stern <stern@rowland.harvard.edu>,
	Jan Ceuleers <jan.ceuleers@computer.org>,
	Clemens Ladisch <clemens@ladisch.de>,
	Simon Jones <sijones2010@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: 3.4.4: disabling irq
Date: Sun, 15 Jul 2012 17:55:40 +0200	[thread overview]
Message-ID: <5002E7FC.5070307@xs4all.nl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1207151122050.25880-100000@netrider.rowland.org>

On 2012-07-15 17:35, Alan Stern wrote:
> echo 0000:00:13.1 >/sys/bus/pci/drivers/ohci_hcd/unbind

Afterwards I did:

> echo 0000:00:13.1 >/sys/bus/pci/drivers/ohci_hcd/bind

And I saw:

Jul 15 17:50:30 surfplank2 kernel: ohci_hcd 0000:00:13.1: remove, state 1
Jul 15 17:50:30 surfplank2 kernel: usb usb4: USB disconnect, device number 1
Jul 15 17:50:30 surfplank2 kernel: usb 4-3: USB disconnect, device number 2
Jul 15 17:50:30 surfplank2 kernel: ohci_hcd 0000:00:13.1: USB bus 4
deregistered
Jul 15 17:50:37 surfplank2 kernel: ohci_hcd 0000:00:13.1: OHCI Host
Controller
Jul 15 17:50:37 surfplank2 kernel: ohci_hcd 0000:00:13.1: new USB bus
registered, assigned bus number 4
Jul 15 17:50:37 surfplank2 kernel: ohci_hcd 0000:00:13.1: irq 18, io mem
0xfe02a000
Jul 15 17:50:37 surfplank2 kernel: usb usb4: New USB device found,
idVendor=1d6b, idProduct=0001
Jul 15 17:50:37 surfplank2 kernel: usb usb4: New USB device strings:
Mfr=3, Product=2, SerialNumber=1
Jul 15 17:50:37 surfplank2 kernel: usb usb4: Product: OHCI Host Controller
Jul 15 17:50:37 surfplank2 kernel: usb usb4: Manufacturer: Linux 3.4.4
ohci_hcd
Jul 15 17:50:37 surfplank2 kernel: usb usb4: SerialNumber: 0000:00:13.1
Jul 15 17:50:37 surfplank2 kernel: hub 4-0:1.0: USB hub found
Jul 15 17:50:37 surfplank2 kernel: hub 4-0:1.0: 3 ports detected
Jul 15 17:50:37 surfplank2 kernel: usb 4-3: new full-speed USB device
number 2 using ohci_hcd
Jul 15 17:50:38 surfplank2 kernel: usb 4-3: New USB device found,
idVendor=0471, idProduct=0311
Jul 15 17:50:38 surfplank2 kernel: usb 4-3: New USB device strings:
Mfr=0, Product=0, SerialNumber=1
Jul 15 17:50:38 surfplank2 kernel: usb 4-3: SerialNumber: 01690000A5000000
Jul 15 17:50:38 surfplank2 mtp-probe: checking bus 4, device 2:
"/sys/devices/pci0000:00/0000:00:13.1/usb4/4-3"
Jul 15 17:50:38 surfplank2 mtp-probe: bus: 4, device: 2 was not an MTP
device
Jul 15 17:50:38 surfplank2 kernel: pwc: Philips PCVC740K (ToUCam
Pro)/PCVC840 (ToUCam II) USB webcam detected.
Jul 15 17:50:39 surfplank2 kernel: pwc: Registered as video0.
Jul 15 17:50:39 surfplank2 kernel: input: PWC snapshot button as
/devices/pci0000:00/0000:00:13.0/usb3/3-2/input/input8
Jul 15 17:50:39 surfplank2 kernel: pwc: Philips PCVC740K (ToUCam
Pro)/PCVC840 (ToUCam II) USB webcam detected.
Jul 15 17:50:39 surfplank2 kernel: pwc: Registered as video1.
Jul 15 17:50:39 surfplank2 kernel: input: PWC snapshot button as
/devices/pci0000:00/0000:00:13.1/usb4/4-3/input/input9
Jul 15 17:50:39 surfplank2 kernel: usbcore: registered new interface
driver Philips webcam
Jul 15 17:50:39 surfplank2 colord[3375]: (colord:3375): Cd-WARNING **:
CdMain: failed to emit DeviceAdded: failed to register object: An object
is already exported for the interface
org.freedesktop.ColorManager.Device at
/org/freedesktop/ColorManager/devices/sysfs_0471_0311

So I have two webcams on this controller, each on a different port.
The final line is an issue that cam with Fedora 17, nobody could foresee
that one could need a colord *and* have two identical webcams too. (I do
not need colord but have two webcams to be clear)

After doing this I could modprobe pwc and start mrtg without problem.

So now I can wait for the next occurrence.

Kind regards,
Udo




  reply	other threads:[~2012-07-15 15:55 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-08  7:53 3.4.4: disabling irq Udo van den Heuvel
2012-07-09 13:54 ` Clemens Ladisch
2012-07-09 16:05   ` Udo van den Heuvel
2012-07-09 18:58   ` Alan Stern
2012-07-11 14:50   ` Udo van den Heuvel
2012-07-11 15:15     ` Alan Stern
2012-07-12 13:23       ` Udo van den Heuvel
2012-07-12 13:43         ` Jan Ceuleers
2012-07-12 14:02           ` Udo van den Heuvel
2012-07-12 14:54             ` Alan Stern
2012-07-15 14:28               ` Udo van den Heuvel
2012-07-15 14:36                 ` Udo van den Heuvel
2012-07-15 15:35                 ` Alan Stern
2012-07-15 15:55                   ` Udo van den Heuvel [this message]
2012-07-15 15:57                     ` Udo van den Heuvel
2012-07-15 18:28                     ` Alan Stern
2012-11-04 10:31                       ` Udo van den Heuvel
2012-11-17 12:35                       ` Udo van den Heuvel
2012-11-19 16:41                         ` Alan Stern
2012-11-19 16:47                           ` Udo van den Heuvel
2012-11-20 14:41                           ` Udo van den Heuvel
2012-11-20 16:14                             ` Alan Stern
2012-12-01  8:52                           ` Udo van den Heuvel
2012-12-01 16:54                             ` Alan Stern

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=5002E7FC.5070307@xs4all.nl \
    --to=udovdh@xs4all.nl \
    --cc=clemens@ladisch.de \
    --cc=jan.ceuleers@computer.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=sijones2010@gmail.com \
    --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