public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Jason Cooper <jason@lakedaemon.net>,
	Shawn Guo <shawn.guo@linaro.org>,
	Rabeeh Khoury <rabeeh@solid-run.com>,
	linux-kernel@vger.kernel.org,
	Linux ARM Kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: oops on cubox-i (v3.15-rc4)
Date: Tue, 3 Jun 2014 11:42:32 +0200	[thread overview]
Message-ID: <20140603094231.GH4197@waldemar-brodkorb.de> (raw)
In-Reply-To: <20140523154453.GY3693@n2100.arm.linux.org.uk>

Hi Again,
> > > > 
> > > > On Fri, May 09, 2014 at 04:44:38PM +0200, Waldemar Brodkorb wrote:
> > > > > Dear Kernel Hackers,
> > > > > 
> > > > > I am getting kernel oopses on my cubox-i (i2ultra) running
> > > > > Linux 3.15-rc4, when using the box as a samba server with 
> > > > > a local attached 8 GB usb stick. (it also happen with a smaller
> > > > > video on the micro-sd card)
> > > > > The oops happens while playing a movie (4 GB file) on a samba client 
> > > > > (macos x maverick macbook) via vlc (after 5-15 minutes). 
> > > > > 
> > > > > Both systems are connected to a gigabit ethernet switch.
> > > > > 
> > > > > The oops happens with ntfs-3g, ntfs, vfat and ext4 filesystem.

The problem is gone with rc7.
It seems just like a cold, after seven rc'ays it's gone.

Sorry for the noise.
        best regards
                Waldemar 

      parent reply	other threads:[~2014-06-03  9:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-09 14:44 oops on cubix-i Waldemar Brodkorb
2014-05-11  0:25 ` oops on cubox-i (v3.15-rc4) Jason Cooper
2014-05-23 10:17   ` Waldemar Brodkorb
2014-05-23 14:38     ` Jason Cooper
2014-05-23 15:44       ` Russell King - ARM Linux
2014-05-23 16:17         ` Waldemar Brodkorb
2014-06-03  9:42         ` Waldemar Brodkorb [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=20140603094231.GH4197@waldemar-brodkorb.de \
    --to=wbx@openadk.org \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=rabeeh@solid-run.com \
    --cc=shawn.guo@linaro.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