Hi,
I think just some XWayland Nouveau bug:
Nov 23 12:46:26 bigbox kernel: nouveau 0000:01:00.0: gr: TRAP ch 22
[007d08d000 Xwayland[781]]
Nov 23 12:46:26 bigbox kernel: nouveau 0000:01:00.0: gr: GPC0/TPC0/TEX:
80000041
Nov 23 12:46:26 bigbox kernel: nouveau 0000:01:00.0: gr: GPC0/TPC1/TEX:
80000041
Nov 23 12:46:26 bigbox kernel: nouveau 0000:01:00.0: gr: GPC0/TPC2/TEX:
80000041
Nov 23 12:46:26 bigbox kernel: nouveau 0000:01:00.0: gr: GPC0/TPC3/TEX:
80000041
Nov 23 12:46:26 bigbox kernel: nouveau 0000:01:00.0: gr: GPC0/TPC4/TEX:
80000041
Nov 23 12:46:26 bigbox kernel: nouveau 0000:01:00.0: fifo: read fault at
0005860000 engine 00 [GR] client 15 [GPC0/PE_4] reason 02 [PTE] on
channel 22 [007d08d000 Xwayland[781]]
Steffen
Am 23.11.2017 um 13:14 schrieb Qu Wenruo:
On 2017年11月23日 20:02, Steffen Sindzinski wrote:
Hi,
I updated to btrfs-progs v4.14-5-gf09e98a3. Unfortunately after 10h
Gnome desktop / Arch crashed with btrfs check --lowmem unfinished. I
will run it this night again.
Any kernel backtrace about the crash?
IIRC user space program like btrfs check should not trigger a kernel crash.
The result until crash was:
Checking filesystem on /dev/sdd2
UUID: 4fafd0d4-7dd9-4dcc-9a33-5f1ad9555358
ERROR: extent[15923092037632, 73728] referencer count mismatch (root:
260, owner: 3631467, offset: 1019904) wanted: 4, have: 6
ERROR: extent[16078964924416, 69632] referencer count mismatch (root:
260, owner: 4086589, offset: 4296704) wanted: 5, have: 7
This is known bug, please use this branch instead.
https://github.com/adam900710/btrfs-progs/tree/lowmem_fix
Thanks,
Qu
Steffen
Am 22.11.2017 um 17:42 schrieb Chris Murphy:
On Wed, Nov 22, 2017 at 9:38 AM, Steffen Sindzinski
<stes...@gmail.com> wrote:
Hello,
I did btrfs check --readonly on both disk without finding any error. To
reconfirm I did a scrub again which still has found 2 uncorrectable
errors.
Try --mode=lowmem option with btrfs-progs 4.3.3 or better 4.14. This
is a new implementation of btrfs check and sometimes it comes up with
different results. It's strange that there's only this error found by
scrub and not by btrfs check which should be fully checking all
metadata for sanity, and in the process it would surely hit a bad
checksum.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
