linux-kernel - Re: oops on cubox-i (v3.15-rc4)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 23 May 2014 18:17:57 +0200
From:	Waldemar Brodkorb <wbx@...nadk.org>
To:	Russell King - ARM Linux <linux@....linux.org.uk>
Cc:	Jason Cooper <jason@...edaemon.net>,
	Shawn Guo <shawn.guo@...aro.org>,
	Rabeeh Khoury <rabeeh@...id-run.com>,
	linux-kernel@...r.kernel.org,
	Linux ARM Kernel <linux-arm-kernel@...ts.infradead.org>
Subject: Re: oops on cubox-i (v3.15-rc4)

Hi Russell,
Russell King - ARM Linux wrote,

> > 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.

I think this, too. I observed a crash in a similar configuration
with my Mikrotik RB532 (mips32). I just couldn't get a kernel Oops yet,
because I fighted against some PCI and serial output problems on
this device.
http://www.linux-mips.org/archives/linux-mips/2014-05/msg00124.html
http://www.linux-mips.org/archives/linux-mips/2014-05/msg00074.html
May be I can get an oops on Monday.
 
> > > > > Booting Linux on physical CPU 0x0
> > > > > Linux version 3.15.0-rc4 (wbx@...-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...)

Thanks for the hint. I thought I only need HIGHMEM for cubox-i4pro
with 2 GB. Will enable it for my cubox-i2ultra.
 
best regards
 Waldemar
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/