Ask Your Question
0

Oops!!! We're sorry, it looks like BOOT_IMAGE=.......?

asked 2019-02-22 20:52:10 -0600

yesiamabdul gravatar image

Hi, guys.

Hope you're having a blast.

After the recent update, I'm getting an error message.

Error Message

May I know what it does mean?

Would be happy to know.

Thanks, guys.

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
0

answered 2019-02-25 04:33:42 -0600

updated 2019-02-25 04:35:26 -0600

your kernel detected something odd and oopsed. Check you "dmesg" or "journalctl -xe" for kernel lines :

Examples:

Feb 24 21:06:45 eve kernel: general protection fault: 0000 [#1] SMP NOPTI
Feb 24 21:06:45 eve kernel: CPU: 6 PID: 16717 Comm: Client.exe Tainted: P           OE     4.19.9-201.fc28.x86_64 #1
Feb 24 21:06:45 eve kernel: Hardware name: To be filled by O.E.M. To be filled by O.E.M./M5A97 R2.0, BIOS 2201 12/10/2013
Feb 24 21:06:45 eve kernel: RIP: 0010:__mutex_lock.isra.5+0x74/0x490
Feb 24 21:06:45 eve kernel: Code: 49 01 00 00 48 39 c6 0f 84 c7 03 00 00 65 48 8b 04 25 00 5c 01 00 48 8b 00 a8 08 75 18 49 8b 07 48 83 e0 f8 0f 84 a5 01 00 00 <8b> 40 38 85 c0 0f 85 9a 01 00 00 65 48 8b 04 25 00 5c 01 00 48 8b
Feb 24 21:06:45 eve kernel: RSP: 0018:ffffa01cc91f7d70 EFLAGS: 00010286
Feb 24 21:06:45 eve kernel: RAX: 8020000000000000 RBX: ffff92d489714f00 RCX: 0000000000000001
Feb 24 21:06:45 eve kernel: RDX: 8020000000000000 RSI: ffff92d41db63e00 RDI: ffff92d1e0afd180
Feb 24 21:06:45 eve kernel: RBP: ffffa01cc91f7de8 R08: 0000000000000040 R09: 0000000000000000
Feb 24 21:06:45 eve kernel: R10: ffffa01cc91f7ed0 R11: 0000000000000000 R12: 0000000000000002
Feb 24 21:06:45 eve kernel: R13: ffff92d489714f00 R14: ffff92d1e0afd180 R15: ffff92d1e0afd180
Feb 24 21:06:45 eve kernel: FS:  0000000081fbc000(0063) GS:ffff92d56eb80000(006b) knlGS:000000001c093b40
Feb 24 21:06:45 eve kernel: CS:  0010 DS: 002b ES: 002b CR0: 0000000080050033
Feb 24 21:06:45 eve kernel: CR2: 000000002061d000 CR3: 00000002a069c000 CR4: 00000000000406e0
Feb 24 21:06:45 eve kernel: Call Trace:
Feb 24 21:06:45 eve kernel: pipe_read+0x3f/0x2d0
Feb 24 21:06:45 eve kernel: ? compat_writev+0xd2/0x120
Feb 24 21:06:45 eve kernel: __vfs_read+0x133/0x190
Feb 24 21:06:45 eve kernel: vfs_read+0x8a/0x140
Feb 24 21:06:45 eve kernel: ksys_read+0x4f/0xb0
Feb 24 21:06:45 eve kernel: do_fast_syscall_32+0xa7/0x254
Feb 24 21:06:45 eve kernel: entry_SYSCALL_compat_after_hwframe+0x45/0x4d
As soon as you have these, open a bugreport (http://bugzilla.redhat.com/) against the "kernel" or the programm referenced under "Comm:" (Client.exe in this case means wine ;) ), copy&paste the lines into your bugreport, write as much as you know about the circumstances and hope it gets fixed soon.

edit flag offensive delete link more

Question Tools

1 follower

Stats

Asked: 2019-02-22 20:52:10 -0600

Seen: 715 times

Last updated: Feb 25 '19