Bug 888388
| Summary: | ARM OMAP kernel produces backtrace for L3 custom error: MASTER:MPU TARGET:DMM1 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | D. Marlin <dmarlin> | ||||
| Component: | kernel | Assignee: | Jon Masters <jcm> | ||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 17 | CC: | gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, pbrobinson | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | arm | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-03-11 19:44:46 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 245418 | ||||||
| Attachments: |
|
||||||
Have you tried to recreate this with the 3.6 kernel from F18? No, I have only tested on F17 with the latest kernel available via yum. Please test kernel-3.7.6-102.fc17 when it lands in updates-testing or updates. |
Created attachment 665573 [details] backtrace snip for L3 custom error: MASTER:MPU TARGET:DMM1 Description of problem: The ARM OMAP kernel produces backtrace when under load (building a kernel): L3 custom error: MASTER:MPU TARGET:DMM1 Version-Release number of selected component (if applicable): kernel-omap-3.5.6-1.fc17.armv7l How reproducible: Consistently Steps to Reproduce: 1. Boot Panda with kernel-omap-3.5.6-1.fc17.armv7l 2. Try to build a kernel: rpmbuild -bb SPECS/kernel.spec 3. Actual results: The kernel starts to build, but after some time (not consistent on how long) backtraces are displayed on the console, and eventually the system locks up (console not responsive and does not respond to pings). Expected results: Kernel builds without issue. Additional info: This is a soft-float (armv5tel) install. The backtrace is attached.