[Bug 960392] New: leap do not start, resume uuid problem, workaround available - openSUSE Bugs - openSUSE Mailing Lists

newer
[Bug 955142] New:...

[Bug 960392] New: leap do not start, resume uuid problem, workaround available

older
[Bug 960856] New: denyhosts does...

bugzilla_noreply＠novell.com

30 Dec 2015 30 Dec '15

09:08

http://bugzilla.opensuse.org/show_bug.cgi?id=960392 Bug ID: 960392 Summary: leap do not start, resume uuid problem, workaround available Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-maintainers@forge.provo.novell.com Reporter: jdd@dodin.org QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I already had this problem after testing hibernation on my desktop computer. (http://lists.opensuse.org/opensuse/2015-12/msg00550.html) but now it occurs without hibernation (at least no voluntary hibernation), but looks very similar. It seems very similar of the bug 944659. I have a work around. As in bug 944659, the computer do not start. Very soon after loading the kernel, the keyboard activates, the display also, the monitor receives signal but display a black screen. Only way to recover is switching off the computer. The "crash" seems to be related to a bad resume uuid in the kernel option line. Removing this "resume=..." option allow normal boot and subsequent boot is ok. journalctrl do not show any log for the faulty boot (was expected, crash too early). This situation is probably due to the following: I have three disks in the computer, with many Linux/windows installs - mostly openSUSE. I have one swap partition on each disk. The "resume" option of the kernel pointed to a wrong swap partition. All this is proved but the reason not clear in my mind. Wrong in the sense it didn't point to the new ssd swap partition, but to one of the old HDD. This leap install is around a week old. I made it on a new ssd plugged on a e-sata dock, used it full for openSUSE Leap. As I created a swap partition on this disk I though that this one was used and didn't take attention at this part of the yast report (may be I should have done). When I had the bug for the first time, as reported on the mailing list, I found three swap lines in the fstab file. I commented away the two not related to the new ssd and the incorrect one for the ssd and added again the ssd swap partition with YaST. This obviously didn't corrected the resume line in the grub kernel options. That said, I didn't touche the other disks during this period, but there was clearly a conflict between fstab and the kernel options. Right now I removed this grub kernel option with YaST - I do not need hibernation on this desktop computer. I fear I'm not that clear, feel free to ask for infos thanks jdd -- You are receiving this mail because: You are on the CC list for the bug.

Attachments:

attachment.htm (text/html — 4.7 KB)

Reply

Sign in to reply online Use email software

Show replies by date

bugzilla_noreply＠novell.com

31 Dec 31 Dec

06:58

New subject: [Bug 960392] leap do not start, worst than initially said

http://bugzilla.opensuse.org/show_bug.cgi?id=960392 http://bugzilla.opensuse.org/show_bug.cgi?id=960392#c1 Jean-Daniel Dodin changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|leap do not start, resume |leap do not start, worst |uuid problem, workaround |than initially said |available | --- Comment #1 from Jean-Daniel Dodin --- what I said was a fix may not be the real solution, because this morning Leap crashes randomly: do not start (as described: black screen just after grub menu). At least once the keyboard was active and echoed on the screen (full HD screen with small letters), but with no action. Once on a while the computer starts. Changing kernel do not change the result: random start or not start. -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

2 Jan 2 Jan

10:14

New subject: [Bug 960392] leap do not start, worst than initially said

http://bugzilla.opensuse.org/show_bug.cgi?id=960392 http://bugzilla.opensuse.org/show_bug.cgi?id=960392#c2 --- Comment #2 from Jean-Daniel Dodin --- Created attachment 660619 --> http://bugzilla.opensuse.org/attachment.cgi?id=660619&action=edit screen shot I found the computer displaying this after leaving it boot alone (and going to coffee machine :-) -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

10:24

New subject: [Bug 960392] leap do not start, worst than initially said

http://bugzilla.opensuse.org/show_bug.cgi?id=960392 http://bugzilla.opensuse.org/show_bug.cgi?id=960392#c3 --- Comment #3 from Jean-Daniel Dodin --- sorry, the comment #2 is wrong. The image loaded is not the expected one. I have several images I could have removing all the kernel options in grub (but the very ones necessary to boot). I could see boot messages and copy them with a camera with kernel 4.1.13.5-default it ends with: "reached target local file system (pre)" with kernel 4.1.121-default it goes a bit further, until: "Started entropy daemon based on ther Haveged algorythm" the image I speak of in the comment #2 gives ata2 exception the three log images, of course show the part of the boot that worked, but the boot stops always at the same part. No problem at all with 13.2 (but not same disk) -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

10:27

New subject: [Bug 960392] leap do not start, worst than initially said

http://bugzilla.opensuse.org/show_bug.cgi?id=960392 http://bugzilla.opensuse.org/show_bug.cgi?id=960392#c4 --- Comment #4 from Jean-Daniel Dodin --- Created attachment 660620 --> http://bugzilla.opensuse.org/attachment.cgi?id=660620&action=edit camera shot here the real image after long wait (bugzilla load windows do not sort files like dolphin) -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

10:28

New subject: [Bug 960392] leap do not start, worst than initially said

http://bugzilla.opensuse.org/show_bug.cgi?id=960392 http://bugzilla.opensuse.org/show_bug.cgi?id=960392#c5 --- Comment #5 from Jean-Daniel Dodin --- Created attachment 660621 --> http://bugzilla.opensuse.org/attachment.cgi?id=660621&action=edit camera screen shot -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

10:28

New subject: [Bug 960392] leap do not start, worst than initially said

http://bugzilla.opensuse.org/show_bug.cgi?id=960392 http://bugzilla.opensuse.org/show_bug.cgi?id=960392#c6 --- Comment #6 from Jean-Daniel Dodin --- Created attachment 660622 --> http://bugzilla.opensuse.org/attachment.cgi?id=660622&action=edit camera screen shot -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

17:40

New subject: [Bug 960392] leap do not start, worst than initially said

http://bugzilla.opensuse.org/show_bug.cgi?id=960392 http://bugzilla.opensuse.org/show_bug.cgi?id=960392#c7 --- Comment #7 from Jean-Daniel Dodin --- last result... may be it can be related to Nvidia driver. What I did: I wanted to try 3.x kernel (like my working 13.2 install), so found one on the obs. This one installed not only 3.x kernel, but also some "pv" and "xen" 4.1 kernels. The only relevant thing is that those kernels didn't boot either, but displayed nvidia related error messages, that lead me to use the "nomodeset" option. Since them Leap seems to boot. I could reinstall the default 4.1 kernel from openSUSE and boot. Of course I may have been lucky, as it was already some times ago, but I still wanted to share my result. If the problem is really solved, I of course will report here thanks jdd -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

19:59

New subject: [Bug 960392] leap do not start, worst than initially said

http://bugzilla.opensuse.org/show_bug.cgi?id=960392 http://bugzilla.opensuse.org/show_bug.cgi?id=960392#c8 --- Comment #8 from Jean-Daniel Dodin --- alas it was only a good luck. Leap again do not start. I go back to my old 13.2, I have pent my free time :-( sorry -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

3 Jan 3 Jan

15:58

New subject: [Bug 960392] leap do not start, worst than initially said

http://bugzilla.opensuse.org/show_bug.cgi?id=960392 http://bugzilla.opensuse.org/show_bug.cgi?id=960392#c9 --- Comment #9 from Jean-Daniel Dodin --- Created attachment 660629 --> http://bugzilla.opensuse.org/attachment.cgi?id=660629&action=edit journalctl -b 0 Today I could boot Leap (Hey!), so I could have a plain log. I add it to make it easiest to see where the boot may fail -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

4 Jan 4 Jan

09:11

New subject: [Bug 960392] leap do not start, worst than initially said

http://bugzilla.opensuse.org/show_bug.cgi?id=960392 http://bugzilla.opensuse.org/show_bug.cgi?id=960392#c10 --- Comment #10 from Jean-Daniel Dodin --- Created attachment 660708 --> http://bugzilla.opensuse.org/attachment.cgi?id=660708&action=edit buggy start I try starting without nomodeset and the start visibly crash, but at that time I had a log. Notice this nomodeset was added by me recently, Leap started perfectly without it initially. As the bug is random, it may have no relation with nomodeset -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

11:49

New subject: [Bug 960392] leap do not start: gpf in pagecache -- find_get_entry

http://bugzilla.opensuse.org/show_bug.cgi?id=960392 http://bugzilla.opensuse.org/show_bug.cgi?id=960392#c13 --- Comment #13 from Jean-Daniel Dodin --- I just tested a work around, given the problem looks related to nvidia driver. I added "3" on the grub kernel option line, to boot as init 3 Then the computer boots (at least 4 times in a row without stopping)I can log as root, and type "init 5" and get kde. Hope it will continue at least like this :-) thanks jdd -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

5 Jan 5 Jan

11:05

New subject: [Bug 960392] leap do not start: gpf in pagecache -- find_get_entry

http://bugzilla.opensuse.org/show_bug.cgi?id=960392 http://bugzilla.opensuse.org/show_bug.cgi?id=960392#c15 --- Comment #15 from Jean-Daniel Dodin --- I have no idea why, but I didn't experience any crash with "3" on the kernel line, when I remove it sometime it boots fully (rarely) and other I get a gfc -- Logs begin at mer. 2015-12-23 09:15:22 CET, end at mar. 2016-01-05 12:02:03 CET. -- déc. 23 09:15:22 linux-mama systemd-journal[143]: Runtime journal is using 8.0M (max allowed 395.4M, trying to leave 593.1M free of 3.8G available → current limit 39 déc. 23 09:15:22 linux-mama systemd-journal[143]: Runtime journal is using 8.0M (max allowed 395.4M, trying to leave 593.1M free of 3.8G available → current limit 39 déc. 23 09:15:22 linux-mama kernel: microcode: CPU0 microcode updated early to revision 0xe, date = 2013-06-26 déc. 23 09:15:22 linux-mama kernel: Initializing cgroup subsys cpuset déc. 23 09:15:22 linux-mama kernel: Initializing cgroup subsys cpu déc. 23 09:15:22 linux-mama kernel: Initializing cgroup subsys cpuacct déc. 23 09:15:22 linux-mama kernel: Linux version 4.1.12-1-default (geeko@buildhost) (gcc version 4.8.5 (SUSE Linux) ) #1 SMP PREEMPT Thu Oct 29 06:43:42 UTC 2015 (e déc. 23 09:15:22 linux-mama kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.1.12-1-default root=UUID=372ae705-e0e7-4a81-afb8-7d55e276caa8 resume=/dev/disk/by-uuid/4 déc. 23 09:15:22 linux-mama kernel: e820: BIOS-provided physical RAM map: déc. 23 09:15:22 linux-mama kernel: BIOS-e820: [mem 0x0000000000000000-0x00000000000957ff] usable déc. 23 09:15:22 linux-mama kernel: BIOS-e820: [mem 0x0000000000095800-0x000000000009ffff] reserved déc. 23 09:15:22 linux-mama kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved déc. 23 09:15:22 linux-mama kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000cb77ffff] usable déc. 23 09:15:22 linux-mama kernel: BIOS-e820: [mem 0x00000000cb780000-0x00000000cb78dfff] ACPI data déc. 23 09:15:22 linux-mama kernel: BIOS-e820: [mem 0x00000000cb78e000-0x00000000cb7cffff] ACPI NVS déc. 23 09:15:22 linux-mama kernel: BIOS-e820: [mem 0x00000000cb7d0000-0x00000000cb7dffff] reserved déc. 23 09:15:22 linux-mama kernel: BIOS-e820: [mem 0x00000000cb7ed000-0x00000000cbffffff] reserved déc. 23 09:15:22 linux-mama kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved déc. 23 09:15:22 linux-mama kernel: BIOS-e820: [mem 0x00000000ffa00000-0x00000000ffffffff] reserved déc. 23 09:15:22 linux-mama kernel: BIOS-e820: [mem 0x0000000100000000-0x00000001fbffffff] usable déc. 23 09:15:22 linux-mama kernel: BIOS-e820: [mem 0x00000001fc000000-0x00000001ffffffff] reserved déc. 23 09:15:22 linux-mama kernel: BIOS-e820: [mem 0x0000000200000000-0x0000000233ffffff] usable déc. 23 09:15:22 linux-mama kernel: NX (Execute Disable) protection: active déc. 23 09:15:22 linux-mama kernel: SMBIOS 2.6 present. déc. 23 09:15:22 linux-mama kernel: DMI: Hewlett-Packard HPE-311fr/2A9C, BIOS 6.12 07/12/2010 déc. 23 09:15:22 linux-mama kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved déc. 23 09:15:22 linux-mama kernel: e820: remove [mem 0x000a0000-0x000fffff] usable déc. 23 09:15:22 linux-mama kernel: AGP: No AGP bridge found déc. 23 09:15:22 linux-mama kernel: e820: last_pfn = 0x234000 max_arch_pfn = 0x400000000 déc. 23 09:15:22 linux-mama kernel: MTRR default type: uncachable déc. 23 09:15:22 linux-mama kernel: MTRR fixed ranges enabled: déc. 23 09:15:22 linux-mama kernel: 00000-9FFFF write-back déc. 23 09:15:22 linux-mama kernel: A0000-BFFFF uncachable déc. 23 09:15:22 linux-mama kernel: C0000-D7FFF write-protect déc. 23 09:15:22 linux-mama kernel: D8000-DFFFF uncachable déc. 23 09:15:22 linux-mama kernel: E0000-E3FFF write-protect déc. 23 09:15:22 linux-mama kernel: E4000-E7FFF write-through déc. 23 09:15:22 linux-mama kernel: E8000-EBFFF write-protect déc. 23 09:15:22 linux-mama kernel: EC000-EFFFF write-through déc. 23 09:15:22 linux-mama kernel: F0000-FFFFF write-protect déc. 23 09:15:22 linux-mama kernel: MTRR variable ranges enabled: déc. 23 09:15:22 linux-mama kernel: 0 base 000000000 mask E00000000 write-back déc. 23 09:15:22 linux-mama kernel: 1 base 200000000 mask FC0000000 write-back déc. 23 09:15:22 linux-mama kernel: 2 base 240000000 mask FE0000000 write-back déc. 23 09:15:22 linux-mama kernel: 3 base 260000000 mask FF8000000 write-back déc. 23 09:15:22 linux-mama kernel: 4 base 0CC000000 mask FFC000000 uncachable déc. 23 09:15:22 linux-mama kernel: 5 base 0D0000000 mask FF0000000 uncachable déc. 23 09:15:22 linux-mama kernel: 6 base 0E0000000 mask FE0000000 uncachable déc. 23 09:15:22 linux-mama kernel: 7 base 1FC000000 mask FFC000000 uncachable déc. 23 09:15:22 linux-mama kernel: PAT configuration [0-7]: WB WC UC- UC WB WC UC- UC déc. 23 09:15:22 linux-mama kernel: e820: update [mem 0xcc000000-0xffffffff] usable ==> reserved déc. 23 09:15:22 linux-mama kernel: e820: update [mem 0x1fc000000-0x1ffffffff] usable ==> reserved déc. 23 09:15:22 linux-mama kernel: e820: last_pfn = 0xcb780 max_arch_pfn = 0x400000000 déc. 23 09:15:22 linux-mama kernel: found SMP MP-table at [mem 0x000ff780-0x000ff78f] mapped at [ffff8800000ff780] déc. 23 09:15:22 linux-mama kernel: Scanning 1 areas for low memory corruption déc. 23 09:15:22 linux-mama kernel: Base memory trampoline at [ffff88000008f000] 8f000 size 24576 déc. 23 09:15:22 linux-mama kernel: init_memory_mapping: [mem 0x00000000-0x000fffff] déc. 23 09:15:22 linux-mama kernel: [mem 0x00000000-0x000fffff] page 4k déc. 23 09:15:22 linux-mama kernel: BRK [0x0221a000, 0x0221afff] PGTABLE déc. 23 09:15:22 linux-mama kernel: BRK [0x0221b000, 0x0221bfff] PGTABLE déc. 23 09:15:22 linux-mama kernel: BRK [0x0221c000, 0x0221cfff] PGTABLE déc. 23 09:15:22 linux-mama kernel: init_memory_mapping: [mem 0x233e00000-0x233ffffff] déc. 23 09:15:22 linux-mama kernel: [mem 0x233e00000-0x233ffffff] page 2M déc. 23 09:15:22 linux-mama kernel: BRK [0x0221d000, 0x0221dfff] PGTABLE déc. 23 09:15:22 linux-mama kernel: init_memory_mapping: [mem 0x220000000-0x233dfffff] déc. 23 09:15:22 linux-mama kernel: [mem 0x220000000-0x233dfffff] page 2M déc. 23 09:15:22 linux-mama kernel: init_memory_mapping: [mem 0x200000000-0x21fffffff] déc. 23 09:15:22 linux-mama kernel: [mem 0x200000000-0x21fffffff] page 2M déc. 23 09:15:22 linux-mama kernel: init_memory_mapping: [mem 0x00100000-0xcb77ffff] déc. 23 09:15:22 linux-mama kernel: [mem 0x00100000-0x001fffff] page 4k déc. 23 09:15:22 linux-mama kernel: [mem 0x00200000-0xcb5fffff] page 2M déc. 23 09:15:22 linux-mama kernel: [mem 0xcb600000-0xcb77ffff] page 4k déc. 23 09:15:22 linux-mama kernel: init_memory_mapping: [mem 0x100000000-0x1fbffffff] ...skipping... déc. 23 09:30:23 linux-mama kernel: RIP: 0010:[<ffffffff8116daf8>] [<ffffffff8116daf8>] find_get_entry+0x38/0xa0 déc. 23 09:30:23 linux-mama kernel: RSP: 0018:ffff8801c6fc3d38 EFLAGS: 00010246 déc. 23 09:30:23 linux-mama kernel: RAX: ffff8800c4160048 RBX: 005200ff02fedfc0 RCX: 00000000fffffffa déc. 23 09:30:23 linux-mama kernel: RDX: ffff8800c4160048 RSI: 0000000000002643 RDI: 0000000000000007 déc. 23 09:30:23 linux-mama kernel: RBP: ffff8800c40a06e8 R08: ffff8800c4160048 R09: ffff8800c4160008 déc. 23 09:30:23 linux-mama kernel: R10: ffff8801c6fc3d28 R11: 0000000000000246 R12: 0000000000002643 déc. 23 09:30:23 linux-mama kernel: R13: ffff8800c40a06e0 R14: 0000000000002643 R15: ffffea0002fedf80 déc. 23 09:30:23 linux-mama kernel: FS: 00007f551d78d700(0000) GS:ffff880233c40000(0000) knlGS:0000000000000000 déc. 23 09:30:23 linux-mama kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 déc. 23 09:30:23 linux-mama kernel: CR2: 0000000000642000 CR3: 00000001c9f4a000 CR4: 00000000000006e0 déc. 23 09:30:23 linux-mama kernel: Stack: déc. 23 09:30:23 linux-mama kernel: 0000000000000000 0000000000000000 ffff8800a52faa00 ffffffff8116e446 déc. 23 09:30:23 linux-mama kernel: ffff8800bfb7e000 ffff8800c40a06e0 ffff8800c40a06e0 0000000000002643 déc. 23 09:30:23 linux-mama kernel: ffff8800a52faa00 ffff8801c6fc3e90 0000000000000005 ffffffff8116f673 déc. 23 09:30:23 linux-mama kernel: Call Trace: déc. 23 09:30:23 linux-mama kernel: [<ffffffff8116e446>] pagecache_get_page+0x26/0x1c0 déc. 23 09:30:23 linux-mama kernel: [<ffffffff8116f673>] generic_file_read_iter+0x223/0x5e0 déc. 23 09:30:23 linux-mama kernel: [<ffffffff811dd92c>] __vfs_read+0xac/0xf0 déc. 23 09:30:23 linux-mama kernel: [<ffffffff811ddedd>] vfs_read+0x7d/0x130 déc. 23 09:30:23 linux-mama kernel: [<ffffffff811decf2>] SyS_read+0x42/0xb0 déc. 23 09:30:23 linux-mama kernel: [<ffffffff8165f032>] system_call_fastpath+0x16/0x75 déc. 23 09:30:23 linux-mama kernel: [<00007f551d2c3cd0>] 0x7f551d2c3cd0 déc. 23 09:30:23 linux-mama kernel: Code: fd 48 83 c5 08 53 e8 98 9b f5 ff 4c 89 e6 48 89 ef e8 4d fd 1e 00 48 85 c0 49 89 c0 74 3d 48 8b 18 48 85 db 74 25 f6 c3 03 déc. 23 09:30:23 linux-mama kernel: RIP [<ffffffff8116daf8>] find_get_entry+0x38/0xa0 déc. 23 09:30:23 linux-mama kernel: RSP <ffff8801c6fc3d38> déc. 23 09:30:23 linux-mama kernel: ---[ end trace 84239152ad16d66f ]--- déc. 23 09:30:23 linux-mama kernel: BTRFS info (device sdc1): relocating block group 0 flags 2 déc. 23 09:30:23 linux-mama kernel: BTRFS info (device sdc1): relocating block group 6194987008 flags 2 déc. 23 09:30:24 linux-mama kernel: BTRFS info (device sdc1): relocating block group 6228541440 flags 2 déc. 23 09:30:24 linux-mama kernel: BTRFS info (device sdc1): relocating block group 6262095872 flags 2 déc. 23 09:30:24 linux-mama kernel: BTRFS info (device sdc1): relocating block group 5926551552 flags 4 déc. 23 09:30:25 linux-mama kernel: general protection fault: 0000 [#4] PREEMPT SMP déc. 23 09:30:25 linux-mama kernel: Modules linked in: fuse bnep bluetooth nf_log_ipv6 xt_pkttype nf_log_ipv4 nf_log_common xt_LOG xt_limit af_packet iscsi_ibft iscs déc. 23 09:30:25 linux-mama kernel: gpio_ich eeprom_93cx6 ablk_helper cryptd serio_raw i2c_i801 pcspkr snd_timer crc_ccitt r8169 lpc_ich usblp joydev rfkill mfd_cor déc. 23 09:30:25 linux-mama kernel: CPU: 2 PID: 3471 Comm: btrfs Tainted: G D 4.1.12-1-default #1 déc. 23 09:30:25 linux-mama kernel: Hardware name: Hewlett-Packard HPE-311fr/2A9C, BIOS 6.12 07/12/2010 déc. 23 09:30:25 linux-mama kernel: task: ffff88008cccc410 ti: ffff88008ccd0000 task.ti: ffff88008ccd0000 déc. 23 09:30:25 linux-mama kernel: RIP: 0010:[<ffffffff8116daf8>] [<ffffffff8116daf8>] find_get_entry+0x38/0xa0 déc. 23 09:30:25 linux-mama kernel: RSP: 0018:ffff88008ccd37f8 EFLAGS: 00010246 déc. 23 09:30:25 linux-mama kernel: RAX: ffff8800c414e048 RBX: 005200ff00000000 RCX: 00000000fffffffa déc. 23 09:30:25 linux-mama kernel: RDX: ffff8800c414e048 RSI: 000000000000dd43 RDI: 0000000000000007 déc. 23 09:30:25 linux-mama kernel: RBP: ffff880229acde88 R08: ffff8800c414e048 R09: ffff8800c414e008 déc. 23 09:30:25 linux-mama kernel: R10: ffff88008ccd37e8 R11: ffffea00070c9a40 R12: 000000000000dd43 déc. 23 09:30:25 linux-mama kernel: R13: ffff880229acde80 R14: 000000000000dd43 R15: ffff8801ccafd840 déc. 23 09:30:25 linux-mama kernel: FS: 00007fd6ca9c38c0(0000) GS:ffff880233c80000(0000) knlGS:0000000000000000 déc. 23 09:30:25 linux-mama kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b déc. 23 09:30:25 linux-mama kernel: CR2: 00007f6626434f58 CR3: 000000008cc92000 CR4: 00000000000006e0 déc. 23 09:30:25 linux-mama kernel: Stack: déc. 23 09:30:25 linux-mama kernel: 0000000000000007 0000000000000050 ffff880229acde80 ffffffff8116e446 déc. 23 09:30:25 linux-mama kernel: 000000000dd40000 ffffffffa0537527 ffffea00070c9a00 000000000000dd43 déc. 23 09:30:25 linux-mama kernel: ffff880229acde80 ffff8801ccb6c240 ffff880229acdef8 ffffffffa053dc95 déc. 23 09:30:25 linux-mama kernel: Call Trace: déc. 23 09:30:25 linux-mama kernel: [<ffffffff8116e446>] pagecache_get_page+0x26/0x1c0 déc. 23 09:30:25 linux-mama kernel: [<ffffffffa053dc95>] alloc_extent_buffer+0xe5/0x370 [btrfs] déc. 23 09:30:25 linux-mama kernel: [<ffffffffa0504afd>] do_walk_down+0x3ad/0x8d0 [btrfs] déc. 23 09:30:25 linux-mama kernel: [<ffffffffa05050dc>] walk_down_tree+0xbc/0x100 [btrfs] déc. 23 09:30:25 linux-mama kernel: [<ffffffffa0508b01>] btrfs_drop_snapshot+0x401/0x860 [btrfs] déc. 23 09:30:25 linux-mama kernel: [<ffffffffa056f0f1>] merge_reloc_roots+0xd1/0x240 [btrfs] déc. 23 09:30:25 linux-mama kernel: [<ffffffffa056f4c1>] relocate_block_group+0x261/0x670 [btrfs] déc. 23 09:30:25 linux-mama kernel: [<ffffffffa056fa97>] btrfs_relocate_block_group+0x1c7/0x2d0 [btrfs] déc. 23 09:30:25 linux-mama kernel: [<ffffffffa054335e>] btrfs_relocate_chunk.isra.38+0x3e/0xc0 [btrfs] déc. 23 09:30:25 linux-mama kernel: [<ffffffffa05446c1>] __btrfs_balance+0x4c1/0x870 [btrfs] déc. 23 09:30:25 linux-mama kernel: [<ffffffffa0544dd9>] btrfs_balance+0x369/0x630 [btrfs] déc. 23 09:30:25 linux-mama kernel: [<ffffffffa054def1>] btrfs_ioctl_balance+0x401/0x540 [btrfs] déc. 23 09:30:25 linux-mama kernel: [<ffffffffa0552909>] btrfs_ioctl+0x489/0x2860 [btrfs] déc. 23 09:30:25 linux-mama kernel: [<ffffffff811f0f4f>] do_vfs_ioctl+0x2ff/0x510 déc. 23 09:30:25 linux-mama kernel: [<ffffffff811f11e1>] SyS_ioctl+0x81/0xa0 déc. 23 09:30:25 linux-mama kernel: [<ffffffff8165f032>] system_call_fastpath+0x16/0x75 déc. 23 09:30:25 linux-mama kernel: [<00007fd6c9a68be7>] 0x7fd6c9a68be7 déc. 23 09:30:25 linux-mama kernel: Code: fd 48 83 c5 08 53 e8 98 9b f5 ff 4c 89 e6 48 89 ef e8 4d fd 1e 00 48 85 c0 49 89 c0 74 3d 48 8b 18 48 85 db 74 25 f6 c3 03 déc. 23 09:30:25 linux-mama kernel: RIP [<ffffffff8116daf8>] find_get_entry+0x38/0xa0 déc. 23 09:30:25 linux-mama kernel: RSP <ffff88008ccd37f8> déc. 23 09:30:25 linux-mama kernel: ---[ end trace 84239152ad16d670 ]--- déc. 23 09:30:52 linux-mama CRON[3258]: pam_unix(crond:session): session closed for user root -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

11:06

New subject: [Bug 960392] leap do not start: gpf in pagecache -- find_get_entry

http://bugzilla.opensuse.org/show_bug.cgi?id=960392 Jean-Daniel Dodin changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jdd@dodin.org -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

bugzilla_noreply＠novell.com

6 Jan 6 Jan

14:43

New subject: [Bug 960392] leap do not start: gpf in pagecache -- find_get_entry

http://bugzilla.opensuse.org/show_bug.cgi?id=960392 http://bugzilla.opensuse.org/show_bug.cgi?id=960392#c16 Jean-Daniel Dodin changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #16 from Jean-Daniel Dodin --- reinstalling Leap seems to fix the problem. Given the strangeness of the bug I suspect it was some sort of corruption during an update or the initial install. I reinstalled only root (/) and all boot again as expected, so I close the bug as wontfiw -- You are receiving this mail because: You are on the CC list for the bug.

Reply

Sign in to reply online Use email software

3037

Age (days ago)

3044

Last active (days ago)

Download

14 comments

1 participants

tags

participants (1)

bugzilla_noreply＠novell.com