Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 26 Feb 2013 13:17:56 -0500
From:      Sean Cavanaugh <millenia2000@hotmail.com>
To:        "'Brett Wynkoop'" <wynkoop@wynn.com>, <freebsd-arm@freebsd.org>
Subject:   RE: Raspberry Pi Network Data
Message-ID:  <BAY165-ds1973AAF7E1EBE7F0B444D6CAFC0@phx.gbl>
In-Reply-To: <20130226120335.6928b473@ivory.wynn.com>
References:  <20130226120335.6928b473@ivory.wynn.com>

next in thread | previous in thread | raw e-mail | index | archive | help


> -----Original Message-----
> From: owner-freebsd-arm@freebsd.org [mailto:owner-freebsd-
> arm@freebsd.org] On Behalf Of Brett Wynkoop
> Sent: Tuesday, February 26, 2013 12:04 PM
> To: freebsd-arm@freebsd.org
> Subject: Raspberry Pi Network Data
> 
> Greeting-
> 
> For a couple of days I have been building software from ports.  Mostly
these
> builds are for things I just want to try on the Pi, or Bone, but the
secondary
> reason is to put some pre-compiled packages up for those that do not have
> the patience to build them.
> 
> While my Pi has been stable for a couple of weeks I have noted that
> sometimes it stops talking on the network.  At those times if I get on the
> console and ifconfig down and back up the interface it starts talking on
the
> net just fine again.
> 
> Last night I believe I found a link between disk i/o and network non-
> responsiveness.  During a period of high disk i/o to the USB connected
flash
> drive I lost network.  The console had messages about retrys to the disk
and
> the console was slow to respond.  It took me for ever to get logged in
> because the console kept dropping characters while I typed.  I am using
usb-
> keyboard and composite video for the console.
> 
> When I got logged in I still had trouble typing ifconfig ue0 down ;
ifconfig ue0
> up, but once I did everything went back to normal.
> Keyboard response was fine, disk i/o no longer seemed to be reporting
> errors and of course the network came back on line.
> 
> I went to sleep with zoneminder building.  Now 6 hours later I find the
> machine in the same state. Since the disk, keyboard, and ethernet are all
usb
> devices could we have a bug in the usb sub-system?
> 
> As soon as the ifconfig ue0 down happens the console keyboard becomes
> properly responsive again.  Could we have some sort of interrupt problem
> going on here?
> 
> This is food for thought for you kernel hackers.  If there is anything you
want
> me to specifically try or do the next time I have this problem, probably
in the
> next 24 hours, please let me know.
> 
> Your fellow ARM hacker,
> 
> -Brett
> 

Keep in mind that the network port, the SD card slot,  and obviously the USB
ports themselves are all on the same USB bus. That may be part of the issue.
Definitely agree that it should be able to swap between them easier than
manually shunting it.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BAY165-ds1973AAF7E1EBE7F0B444D6CAFC0>