search for: 0x38b

...0 000000000033bef7 0000000000008560 0000000000000000 00000000000007bf ffff880bf0984870 00000000000009d9 0000000000000000 ffff880bf560b1b0 ffff8805c29a5e88 000000000033bef7 Call Trace: [<ffffffffa03210e5>] ? __btrfs_unlink_inode+0x172/0x25e [btrfs] [<ffffffffa032158c>] ? btrfs_rename+0x38b/0x55b [btrfs] [<ffffffff81124e8c>] ? vfs_rename+0x202/0x382 [<ffffffff81127312>] ? sys_renameat+0x169/0x1e5 [<ffffffff81051164>] ? do_page_fault+0x39b/0x3af [<ffffffff8112c35e>] ? dput+0x3f/0x126 [<ffffffff8111ee28>] ? vfs_fstatat+0x57/0x60 [<ffffffff81057176&...

...27 23:41:41 jupiter2 kernel: [ 351.170003] [<ffffffff8115c705>] ? page_getlink+0x25/0x80 Jul 27 23:41:41 jupiter2 kernel: [ 351.170003] [<ffffffff8115c77b>] ? page_follow_link_light+0x1b/0x30 Jul 27 23:41:41 jupiter2 kernel: [ 351.170003] [<ffffffff8116099b>] ? path_lookupat+0x38b/0x720 Jul 27 23:41:41 jupiter2 kernel: [ 351.170003] [<ffffffff81160d5c>] ? do_path_lookup+0x2c/0xd0 Jul 27 23:41:41 jupiter2 kernel: [ 351.170003] [<ffffffff81346f31>] ? ocfs2_inode_revalidate+0x71/0x160 Jul 27 23:41:41 jupiter2 kernel: [ 351.170003] [<ffffffff81161c0c>] ?...

...9.323] (EE) 3: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f40f87bd000+0xd74f) [0x7f40f87ca74f] [ 9.323] (EE) 4: /usr/bin/X (PixmapShareToSlave+0x8e) [0x5616575cc94e] [ 9.323] (EE) 5: /usr/bin/X (RRCrtcSet+0x670) [0x561657671870] [ 9.323] (EE) 6: /usr/bin/X (ProcRRSetCrtcConfig+0x38b) [0x56165767289b] [ 9.323] (EE) 7: /usr/bin/X (0x561657558000+0x5818f) [0x5616575b018f] [ 9.323] (EE) 8: /usr/bin/X (0x561657558000+0x5c34b) [0x5616575b434b] [ 9.323] (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7f40fc85ea40] [ 9.323] (EE) 10: /usr/bin/X (_sta...

Next version of https://patchwork.freedesktop.org/series/48596/ . Made some important changes to the refactoring patch, but everything else is the same. Lyude Paul (5): drm/nouveau: Check backlight IDs are >= 0, not > 0 drm/nouveau: Move backlight device into nouveau_connector drm/nouveau: s/nouveau_backlight_exit/nouveau_backlight_fini/ drm/nouveau: Cleanup indenting in

This series fixes some issues with nouveau's backlight support that were causing kernel panics on module reloads, specifically on systems with nouveau handling the backlight of one of the displays. While we're at it, let's cleanup nouveau_backlight.c as well Lyude Paul (5): drm/nouveau: Check backlight IDs are >= 0, not > 0 drm/nouveau: Move backlight device into

Next version of https://patchwork.freedesktop.org/series/48596/ . Added NV_INFO_ONCE and made "Move backlight device into nouveau_connector" use that instead so we don't print the GMUX warning more then once. Lyude Paul (5): drm/nouveau: Add NV_PRINTK_ONCE and variants drm/nouveau: Move backlight device into nouveau_connector drm/nouveau:

Forgot to send 6 patches instead of five since there's one new one now, whoops! No actual changes, next version of https://patchwork.freedesktop.org/series/48596/ Lyude Paul (6): drm/nouveau: Check backlight IDs are >= 0, not > 0 drm/nouveau: Add NV_PRINTK_ONCE and variants drm/nouveau: Move backlight device into nouveau_connector drm/nouveau:

Refactor for Ben, hopefully this time this should apply to his tree. Next version of https://patchwork.freedesktop.org/series/48596/ No changes otherwise. Lyude Paul (6): drm/nouveau: Check backlight IDs are >= 0, not > 0 drm/nouveau: Add NV_PRINTK_ONCE and variants drm/nouveau: Move backlight device into nouveau_connector drm/nouveau:

I noticed a huge problem with the free space cache that was presenting as an early ENOSPC. Turns out when writing the free space cache out I forgot to take into account pinned extents and more importantly clusters. This would result in us leaking free space everytime we unmounted the filesystem and remounted it. I fix this by making sure to check and see if the current block group has a cluster

Hi Jan, After commit 2ca9fbd739b8a72b16dd790d0fff7b75f5488fb8 AMD IOMMU: allocate IRTE entries instead of using a static mapping, booting dom0 stalls several times. Sometimes this results in RCU stall warnings from the dom0 kernel, hitting the "any" key, on normal or serial console, makes the boot continue for a while but it stalls several times. (It also stalls on shutdown BTW) I have