From: Jorge Almeida <jalmeida@math.ist.utl.pt>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] confused udev?
Date: Thu, 17 Nov 2005 18:23:19 +0000 (WET) [thread overview]
Message-ID: <Pine.LNX.4.63.0511171821590.7664@weber.math.ist.utl.pt> (raw)
In-Reply-To: <7573e9640511171014p1b5dd90ay29e841abd7310bbe@mail.gmail.com>
On Thu, 17 Nov 2005, Richard Fish wrote:
> Hmm, looks ok. Could you set udev_log=7 in /etc/udev/udev.conf, and
> post the entries that are added to /var/log/messages when you turn on
> the hard drive.
>
$ tail -F /var/log/kernel/current
Nov 17 17:41:51 [kernel] usb-storage: -- transfer complete
Nov 17 17:41:51 [kernel] usb-storage: Bulk command transfer result=0
Nov 17 17:41:51 [kernel] usb-storage: Attempting to get CSW...
Nov 17 17:41:51 [kernel] usb-storage: usb_stor_bulk_transfer_buf: xfer
13 bytes
Nov 17 17:41:51 [kernel] usb-storage: Status code 0; transferred 13/13
Nov 17 17:41:51 [kernel] usb-storage: -- transfer complete
Nov 17 17:41:51 [kernel] usb-storage: Bulk status result = 0
Nov 17 17:41:51 [kernel] usb-storage: Bulk Status S 0x53425355 T 0x78 R
0 Stat 0x0
Nov 17 17:41:51 [kernel] usb-storage: scsi cmd done, result=0x0
Nov 17 17:41:51 [kernel] usb-storage: *** thread sleeping.
Nov 17 18:21:25 [kernel] usb 1-3: new high speed USB device using
ehci_hcd and address 20
Nov 17 18:21:25 [kernel] usb 1-3: device descriptor read/all, error -71
Nov 17 18:21:25 [kernel] usb 1-3: new high speed USB device using
ehci_hcd and address 21
Nov 17 18:21:25 [kernel] usb 1-3: string descriptor 0 read error: -71
- Last output repeated 2 times -
Nov 17 18:21:25 [kernel] usb 1-3: new high speed USB
device using ehci_hcd and address 22
Nov 17 18:21:25 [kernel] usb 1-3: string descriptor 0
read error: -71
- Last output repeated 2 times -
Nov 17 18:21:25 [kernel] usb 1-3: new
high speed USB device using ehci_hcd and
address 23
Nov 17 18:21:25 [kernel] usb 1-3: string
descriptor 0 read error: -71
(Using metalog...)
Jorge
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-11-17 18:28 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-17 9:26 [gentoo-user] confused udev? Jorge Almeida
2005-11-17 9:49 ` Dirk Heinrichs
2005-11-17 12:43 ` Jorge Almeida
2005-11-17 13:54 ` Dirk Heinrichs
2005-11-17 14:14 ` Jorge Almeida
2005-11-18 10:21 ` Dirk Heinrichs
2005-11-18 10:29 ` Neil Bothwick
2005-11-18 10:40 ` Dirk Heinrichs
2005-11-18 10:31 ` Jorge Almeida
2005-11-20 2:21 ` Richard Fish
2005-11-20 11:21 ` Jorge Almeida
2005-11-21 15:18 ` Richard Fish
2005-11-22 11:46 ` Jorge Almeida
2005-11-23 4:10 ` Richard Fish
2005-11-23 9:32 ` Jorge Almeida
2005-11-23 15:07 ` Richard Fish
2005-11-23 21:13 ` Jorge Almeida
2005-11-17 14:14 ` Richard Fish
2005-11-17 16:19 ` Jorge Almeida
2005-11-17 17:11 ` Richard Fish
2005-11-17 17:47 ` Jorge Almeida
2005-11-17 18:14 ` Richard Fish
2005-11-17 18:23 ` Jorge Almeida [this message]
2005-11-17 20:15 ` Richard Fish
2005-11-17 20:49 ` Jorge Almeida
2005-11-17 21:11 ` Richard Fish
2005-11-17 22:04 ` Jorge Almeida
2005-11-17 23:57 ` Richard Fish
2005-11-18 8:33 ` Jorge Almeida
2005-11-18 7:03 ` Dirk Heinrichs
2005-11-18 6:56 ` Dirk Heinrichs
2005-11-18 8:36 ` Jorge Almeida
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=Pine.LNX.4.63.0511171821590.7664@weber.math.ist.utl.pt \
--to=jalmeida@math.ist.utl.pt \
--cc=gentoo-user@lists.gentoo.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