All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: "Mark O'Donovan" <shiftee@eircom.net>
Cc: meta-ti@yoctoproject.org
Subject: Re: Beaglebone usb issue after first reboot
Date: Fri, 16 May 2014 13:29:42 -0400	[thread overview]
Message-ID: <20140516172942.GA18053@edge> (raw)
In-Reply-To: <CAJv4cO2zWjwBKPVe9Xs4zs4F6ynQ6987CEdjsRnzVDkH=oThdw@mail.gmail.com>

On Wed, May 14, 2014 at 12:38:10PM +0100, Mark O'Donovan wrote:
> Issue:
> Beaglebone black detects usb devices on first boot after flashing sd-card.
> On subsequent boots it does not.
> 
> Setup:
> Yocto Project 1.5.1
> linux-ti-staging 3.12.17
> meta-ti = "dora:990d8f62257029e25fc2b8786155bcf5dc483659"
> 
> Using the diff command found here:
> http://superuser.com/a/470876
> 
> I found the following:
> diff -r CLEAN-IMAGE/etc/udev/cache.data BOOTED-IMAGE/etc/udev/cache.data
> 0a1
> > Linux version 3.12.17 (modonovan@changanu) (gcc version 4.8.1 (GCC) ) #3
> SMP PREEMPT Thu May 1 14:08:42 IST 2014console=ttyO0,115200n8
> root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwaitCharacter devices:1 mem4
> /dev/vc/04 tty4 ttyS5 /dev/tty5 /dev/console5 /dev/ptmx7 vcs10 misc13
> input29 fb81 video4linux89 i2c90 mtd128 ptm136 pts180 usb188 ttyUSB189
> usb_device247 ttySDIO248 usbmon249 ttyO250 watchdog251 ptp252 pps253
> media254 rtcBlock devices:1 ramdisk259 blkext7 loop8 sd31 mtdblock65 sd66
> sd67 sd68 sd69 sd70 sd71 sd128 sd129 sd130 sd131 sd132 sd133 sd134 sd135
> sd179 mmc
> 
> 
> Running the following after booting fixes the issue on the next boot:
> echo "" > /etc/udev/cache.data
> 
> Is this a known issue??

Mark,

Thanks for the report! Yes, I've seen this issue before and had a workaround 
for it, but I didn't trace it to the udev cache. I'll check it again.

-- 
Denys


      reply	other threads:[~2014-05-16 17:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-14 11:38 Beaglebone usb issue after first reboot Mark O'Donovan
2014-05-16 17:29 ` Denys Dmytriyenko [this message]

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=20140516172942.GA18053@edge \
    --to=denys@ti.com \
    --cc=meta-ti@yoctoproject.org \
    --cc=shiftee@eircom.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.