linux-kernel - RE: OMAP3 DSP MMU fault + off mode issue

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:	Wed, 15 Sep 2010 10:39:49 -0500
From:	"Ramirez Luna, Omar" <omar.ramirez@...com>
To:	venki kaps <venkiece2005@...il.com>,
	"Kanigeri, Hari" <h-kanigeri2@...com>,
	"ameya.palande@...ia.com" <ameya.palande@...ia.com>,
	"Guzman Lugo, Fernando" <fernando.lugo@...com>,
	"Hebbar, Shivananda" <x0hebbar@...com>,
	"Ramos Falcon, Ernesto" <ernesto@...com>,
	"felipe.contreras@...il.com" <felipe.contreras@...il.com>,
	"Anna, Suman" <s-anna@...com>, "Gupta, Ramesh" <grgupta@...com>,
	"Gomez Castellanos, Ivan" <ivan.gomez@...com>,
	"ext-andriy.shevchenko@...ia.com" <ext-andriy.shevchenko@...ia.com>,
	"Uribe de Leon, Armando" <x0095078@...com>,
	"Chitriki Rudramuni, Deepak" <deepak.chitriki@...com>,
	"Menon, Nishanth" <nm@...com>,
	"ext-phil.2.carmody@...ia.com" <ext-phil.2.carmody@...ia.com>,
	"ohad@...ery.com" <ohad@...ery.com>,
	"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
	"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: OMAP3 DSP MMU fault + off mode issue

venki kaps wrote:
...
> 
> My problem is resolved.GPtimer7 was not reset during the MMU FAULT
> occurrence before the first power cycle. So this pending interrupt is
> preventing the system sleep entry. 
> Now it works fine after resetting Gptimer7 in pm suspend path.
> 

That's doesn't sound right, why the problem is not occurring after the first suspend-resume cycle.

DSP is in charge of clearing the overflow interrupt and if it is doing it after the first transition to Core OFF, why wouldn't be doing it for the first one.

Moreover from the logs sent internally (since it is the same issue and oddly the same resolution), the trace log dump printed is generated in the dsp after clearing the interrupts, so the problem could be the gptimer is configured to autoreload instead of oneshoot or the dsp write is not posted to clear the interrupt (which might be valid issues), but also they could happen after the first transition to OFF.

I'm sorry if I didn't ask you for logs but I was seeing this issue internally (and assumed you'll be in the same team of people :)), and given that more information was posted there than here..., but still, if available send the changes you have made.

Regards,

Omar

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