From: Jarkko Nikula <jhnikula@gmail.com>
To: tomi.valkeinen@nokia.com
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Latest l-o and usb gadget + NFS root problems
Date: Sat, 28 Mar 2009 16:06:05 +0200 [thread overview]
Message-ID: <20090328160605.cd4e6325.jhnikula@gmail.com> (raw)
In-Reply-To: <1238146821.28118.36.camel@tubuntu>
On Fri, 27 Mar 2009 11:40:21 +0200
Tomi Valkeinen <tomi.valkeinen@nokia.com> wrote:
> Hi,
>
> There seems to be something wrong with latest l-o, usb gadget ethernet
> and nfsroot. I'm not sure when it broke, but 2.6.29-rc3 worked fine.
> This happens to me with beagleboard and a non-public omap3 board:
>
I saw something very similar couple days ago on N810 and ethernet
gadget. What was weird that when connection jammed, then also localhost
stopped working. Unfortunately I didn't debug any further would it
happen e.g. using BT PAN connection.
Jarkko
next prev parent reply other threads:[~2009-03-28 14:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 9:40 Latest l-o and usb gadget + NFS root problems Tomi Valkeinen
2009-03-27 10:38 ` Koen Kooi
2009-03-27 11:07 ` Tomi Valkeinen
2009-03-28 14:06 ` Jarkko Nikula [this message]
2009-03-30 6:47 ` Igor Mazanov
2009-03-30 11:44 ` Jarkko Nikula
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=20090328160605.cd4e6325.jhnikula@gmail.com \
--to=jhnikula@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@nokia.com \
/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