| Summary: | [abrt] WARNING: CPU: 0 PID: 0 at arch/x86/mm/ioremap.c:83 __ioremap_caller+0x337/0x360() | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Piraeus <piraeus> | ||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 19 | CC: | gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, nimchung, piraeus | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/ad6899972a967db82db330b9681d5cc3c1fc75e7 | ||||||
| Whiteboard: | abrt_hash:e09756ce724d1b0a3d614cdf7bbea2c4bb7fc345 | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-03-10 14:39:22 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Piraeus
2013-11-20 16:42:24 UTC
Created attachment 826742 [details]
File: dmesg
The stacktrace reported here doesn't make any sense for the problem you reported. It happened before the rootfs was even mounted and there error cases is already handled. You might want to look for a firmware update to fix that issue, as the BGRT tables come directly from firmware. For the actual hang issue, is the machine still responsive on the keyboard or via ssh? Can you install kernel-debug and see if you can get some further debug output? (In reply to Josh Boyer from comment #2) > The stacktrace reported here doesn't make any sense for the problem you > reported. It happened before the rootfs was even mounted and there error > cases is already handled. You might want to look for a firmware update to > fix that issue, as the BGRT tables come directly from firmware. > > For the actual hang issue, is the machine still responsive on the keyboard > or via ssh? Can you install kernel-debug and see if you can get some > further debug output? It happens every time I try to move cells in libreoffice-calc. Fedora freezes, no response at all (Keyboard, Mouse, not even Ctrl+Alt+Back) and I have to manually shut down the Computer by pressing the power button. It only happens after the upgrade to Fedora 19 though. Never had any problems before. Can you install kernel-debug and see if you can get some further debug output? Description of problem: When simply booting the computer with a new install, after updating the whole system, i get this error at each reboot. (PC= HP elite 8300). Version-Release number of selected component: kernel Additional info: reporter: libreport-2.1.9 cmdline: BOOT_IMAGE=/vmlinuz-3.11.9-200.fc19.x86_64.debug root=UUID=e05324e1-7ca3-487f-acc0-e6af0e4f28c8 ro rd.md=0 rd.lvm=0 rd.dm=0 vconsole.keymap=us rd.luks=0 vconsole.font=latarcyrheb-sun16 rhgb quiet LANG=en_US.UTF-8 kernel: 3.11.9-200.fc19.x86_64.debug runlevel: unknown type: Kerneloops Truncated backtrace: WARNING: CPU: 0 PID: 0 at arch/x86/mm/ioremap.c:83 __ioremap_caller+0x357/0x380() Modules linked in: CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.11.9-200.fc19.x86_64.debug #1 Hardware name: Hewlett-Packard HP Compaq Elite 8300 CMT/3396, BIOS K01 v02.05 05/07/2012 0000000000000009 ffffffff81c01e58 ffffffff817283fc 0000000000000000 ffffffff81c01e90 ffffffff8107458d 0000000000000000 1376e01800000006 0000000000000000 ffff88041df27680 0000000000000006 ffffffff81c01ea0 Call Trace: [<ffffffff817283fc>] dump_stack+0x54/0x74 [<ffffffff8107458d>] warn_slowpath_common+0x7d/0xa0 [<ffffffff8107466a>] warn_slowpath_null+0x1a/0x20 [<ffffffff8105ac17>] __ioremap_caller+0x357/0x380 [<ffffffff81415b99>] ? acpi_ut_status_exit+0x5/0xa2 [<ffffffff81f108c9>] ? efi_bgrt_init+0x8b/0x12b [<ffffffff8105ac57>] ioremap_nocache+0x17/0x20 [<ffffffff81f108c9>] efi_bgrt_init+0x8b/0x12b [<ffffffff81f101f7>] efi_late_init+0x9/0xb [<ffffffff81ef5f1e>] start_kernel+0x432/0x44e [<ffffffff81ef58f4>] ? repair_env_string+0x5c/0x5c [<ffffffff81ef5120>] ? early_idt_handlers+0x120/0x120 [<ffffffff81ef55dc>] x86_64_start_reservations+0x2a/0x2c [<ffffffff81ef56e6>] x86_64_start_kernel+0x108/0x117 *********** MASS BUG UPDATE ************** This bug has been in a needinfo state for more than 1 month and is being closed with insufficient data due to inactivity. If this is still an issue with Fedora 19, please feel free to reopen the bug and provide the additional information requested. |