Bug 1062832 - ioremap error for 0xbae23000-0xbae24000, requested 0x10, got 0x0
Summary: ioremap error for 0xbae23000-0xbae24000, requested 0x10, got 0x0
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-08 06:10 UTC by Mohammed Arafa
Modified: 2014-06-18 14:18 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-06-18 14:18:22 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
requested dmesg after fresh boot (68.80 KB, text/plain)
2014-03-23 03:01 UTC, Mohammed Arafa
no flags Details

Description Mohammed Arafa 2014-02-08 06:10:04 UTC
Description of problem:
this error message is filling my messages log. since feb4 it has occurred 27000+ times.
this is a lenovo t420 laptop.

Feb  4 16:03:13 notebook kernel: [   59.695536] ioremap error for 0xbae23000-0xbae24000, requested 0x10, got 0x0
.
.
.
Feb  8 01:03:45 notebook kernel: [  668.096353] ioremap error for 0xbae23000-0xbae24000, requested 0x10, got 0x0

pls advise

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Josh Boyer 2014-02-12 17:39:14 UTC
Please attach the dmesg output from a fresh boot.  We probably only need it up to the point where the first error message pops out.  You might also look in the journal to see if there is something corresponding to that error message.

Comment 2 Mohammed Arafa 2014-02-13 02:46:29 UTC
on Feb 11 17:42:19 Installed: kernel-3.12.10-300.fc20.x86_64

i mention this because i did a fresh reboot and saved the dmesg log. i cant find any ioremap errors now

journalctl -xn shows no errors either.

Comment 3 Josh Boyer 2014-02-13 13:49:10 UTC
OK.  We'll close this out for now then.  If you see them return, please reopen and provide the input asked for in comment #1.

Comment 4 Mohammed Arafa 2014-03-23 03:01:56 UTC
Created attachment 877710 [details]
requested dmesg after fresh boot

requested dmesg after fresh boot
lots of ioremap errors immediately after boot

Comment 5 Justin M. Forbes 2014-05-21 19:37:55 UTC
*********** 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 20 kernel bugs.

Fedora 20 has now been rebased to 3.14.4-200.fc20.  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 experience different issues, please open a new bug report for those.

Comment 6 Josh Boyer 2014-06-18 14:18:22 UTC
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 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.


Note You need to log in before you can comment on or make changes to this bug.