linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: oops on cubox-i (v3.15-rc4)
Date: Fri, 23 May 2014 16:44:53 +0100	[thread overview]
Message-ID: <20140523154453.GY3693@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20140523143845.GD8664@titan.lakedaemon.net>

On Fri, May 23, 2014 at 10:38:45AM -0400, Jason Cooper wrote:
> On Fri, May 23, 2014 at 12:17:51PM +0200, Waldemar Brodkorb wrote:
> > Hi Jason,
> > Jason Cooper wrote,
> > 
> > > Waldemar,
> > > 
> > > + Russell King, linux-arm-kernel ML, Shawn Guo
> > > 
> > > I'm not familiar with the platform, but I almost missed this in the
> > > flood from lkml.  I've added some folks to the Cc who I know work with
> > > this platform and I've also corrected the Subject line so others
> > > familiar with the Cubox-i might catch it.
> > 
> > Thanks. Problem still exist with 3.15-rc6. 
> > It also happens with a NFSv3 exported filesystem.
> > It works nearly stable with 3.10.30 kernel from here:
> > https://github.com/linux4kix/linux-linaro-stable-mx6
> > (a crash after 3 days uptime)
> > 
> > Anything I can do to help debugging?
> > 
> > best regards
> >         Waldemar
> >  
> > > hth,
> > > 
> > > Jason.
> > > 
> > > 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.
> 
> Can you get an oops from when it's on ext4?  It looks like this is going
> through fuse which opens a whole can of unknown worms.

Waldemar mentioned ext4.

I don't think there's anything specific about it to the Cubox-i, and I'd
also suggest that it's got nothing to do with ARM either - the iMX6 are
PIPT data caches so there can't be any issues with D-cache aliasing with
fuse.

It must be a bug in generic code.

> > > > Booting Linux on physical CPU 0x0
> > > > Linux version 3.15.0-rc4 (wbx at kop-brodkorbw) (gcc version 4.8.2 (GCC) ) #1 SMP Fri May 9 12:58:45 CEST 2014
> > > > CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c53c7d
> > > > CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
> > > > Machine model: SolidRun Cubox-i Dual/Quad
> > > > Truncating RAM at 10000000-4fffffff to -3f7fffff (vmalloc region overlap).

Also worth noting that 1/4 of the RAM is not used because highmem is not
enabled.  Also L2 cache is disabled (so it's running slower than it
should...)

-- 
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.

  reply	other threads:[~2014-05-23 15:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20140509144438.GW14063@waldemar-brodkorb.de>
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 [this message]
2014-05-23 16:17         ` Waldemar Brodkorb
2014-06-03  9:42         ` Waldemar Brodkorb

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=20140523154453.GY3693@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).