Bug 1279004
| Summary: | WARNING: CPU: 0 PID: 1 at arch/x86/mm/ioremap.c:198 __ioremap_caller+0x2c5/0x380() | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Edward O'Callaghan <eocallaghan> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 23 | CC: | eocallaghan, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-10-26 16:48:16 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: | |||
|
Description
Edward O'Callaghan
2015-11-07 01:43:40 UTC
Is anything not working here? As far as we know, this is just an unhelpful informational message. Josh, it _is_ helpful if you read it carefully. bisecting I believe it occurs around commit 15c1247953e8a45232ed5a5540f291d2d0a77665 The issue looks to be caused by uncore box initialization, certainly the box init should not be in the IPI context. This patch^[1] moves the box init into the uncore event init which seems like the way to go. $ cat /proc/cpuinfo | grep model model : 61 model name : Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz Kind Regards, Edward. [1] https://lkml.org/lkml/2015/4/28/21 (In reply to Edward O'Callaghan from comment #2) > Josh, it _is_ helpful if you read it carefully. > > bisecting I believe it occurs around commit > 15c1247953e8a45232ed5a5540f291d2d0a77665 > > The issue looks to be caused by uncore box initialization, certainly the box > init should not be in the IPI context. This patch^[1] moves the box init > into the uncore event init which seems like the way to go. The patch you pointed to was never upstreamed, because the commit you bisected to (I think?) was reverted with 15c1247953e8a45232ed5a5540f291d2d0a77665, which is in 4.1-rc8. So the kernel you hit this with already has a fix for that issue. It's certainly possible something else is still needed, but it isn't that patch. You also did not answer my question. Is anything actually not working on your machine? Does the boot continue after the oops? OK so the problem those is that the commit that reverts the previous commit is returning to the original problem. The point of the revert was that the commit that attempted to fix the original problem was confused. Naturally the oops causes erratic system behavior as would ofcourse be expected. The kernel does not oops for giggles, however you are right that a oops isn't a full panic so the machine can obviously boot. I'm not sure I can provide any further information. This is a potential duplicate: bug 1083853 *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 23 kernel bugs. Fedora 23 has now been rebased to 4.7.4-100.fc23. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 24 or 25, and are still experiencing this issue, please change the version to Fedora 24 or 25. If you experience different issues, please open a new bug report for those. *********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |