Re: BUG: scheduling while atomic

On 8/11/18 6:14 AM, James Courtier-Dutton wrote: > On 6 August 2018 at 07:26, Qu Wenruo wrote: >> >> >>> WARNING: CPU: 3 PID: 803 at >>> /build/linux-hwe-SYRsgd/linux-hwe-4.15.0/fs/btrfs/extent_map.c:77 >>> free_extent_map+0x78/0x90 [btrfs] >> >> Then it makes sense, as it's a WARN_ON() line, sh

Re: BUG: scheduling while atomic

On 6 August 2018 at 07:26, Qu Wenruo wrote: > > >> WARNING: CPU: 3 PID: 803 at >> /build/linux-hwe-SYRsgd/linux-hwe-4.15.0/fs/btrfs/extent_map.c:77 >> free_extent_map+0x78/0x90 [btrfs] > > Then it makes sense, as it's a WARN_ON() line, showing one extent map is > still used. > > If it get freed, i

Re: BUG: scheduling while atomic

On 2018年08月06日 14:07, James Courtier-Dutton wrote: > > > On Mon, 6 Aug 2018, 01:48 Qu Wenruo, > wrote: > > > > On 2018年08月05日 22:09, James Courtier-Dutton wrote: > > I am seeing a server halt and require a manual restart that I think > > might be r

Re: BUG: scheduling while atomic

On 2018年08月05日 22:09, James Courtier-Dutton wrote: > I am seeing a server halt and require a manual restart that I think > might be related to btrfs. > I attach the kernel log from it, in the hope that someone will > understand it better than me. > Any clues? > > https://paste.fedoraproject.org/

BUG: scheduling while atomic

I am seeing a server halt and require a manual restart that I think might be related to btrfs. I attach the kernel log from it, in the hope that someone will understand it better than me. Any clues? https://paste.fedoraproject.org/paste/xSblK1RKANiwhKHQj31Cdw Kind Regards James -- To unsubscrib

Re: BUG: scheduling while atomic: mount/1608/0x00000002

On Tue, Jun 14, 2011 at 01:21:00AM +0200, David Sterba wrote: > The code 1972-1979 was added by cleancache. I've asked the reporter to > try it without cleancache, but we did not figure out how to disable it > on commandline (and there was no followup on compiling without > cleancache). without cl

Re: BUG: scheduling while atomic: mount/1608/0x00000002

620d5899c184 devid 2 transid > 906475 /dev/vdc > [ 320.198357] device fsid 48487393f515c9b8-be3d620d5899c184 devid 3 transid > 906477 /dev/vdb > [ 320.251194] parent transid verify failed on 4517304938496 wanted 906477 > found 852489 > [ 320.252957] BUG: scheduling while

BUG: scheduling while atomic: mount/1608/0x00000002

8496 wanted 906477 found 852489 [ 320.252957] BUG: scheduling while atomic: mount/1608/0x0002 [ 320.254318] Modules linked in: btrfs zlib_deflate lzo_compress crc32c libcrc32c usbhid hid uhci_hcd ehci_hcd usbcore [ 320.256779] Pid: 1608, comm: mount Tainted: GW 3.0.0-rc1 #8 [ 320.2

Re: [BUG] scheduling while atomic: init/1/0x00000002

On Mon, Mar 15, 2010 at 03:20:23PM -0700, Phillip Michael wrote: > >> BUG: scheduling while atomic: init/1/0x0002 > >> Modules linked in: > >> Pid: 1, comm: init Not tainted 2.6.33-zen2-20100307-stable #6 > > > > Can you reproduce this error on stock 2.6

Re: [BUG] scheduling while atomic: init/1/0x00000002

>> BUG: scheduling while atomic: init/1/0x0002 >> Modules linked in: >> Pid: 1, comm: init Not tainted 2.6.33-zen2-20100307-stable #6 > > Can you reproduce this error on stock 2.6.33 without the zen patches? > I get the same bug on a stock archlinux 2.6.

Re: [BUG] scheduling while atomic: init/1/0x00000002

bvolume will no longer boot. It shows this bug: > > VFS: Mounted root (btrfs filesystem) readonly on device 0:13. > Freeing unused kernel memory: 480k freed > BFS CPU scheduler v0.315 by Con Kolivas. > BUG: scheduling while atomic: init/1/0x0002 > Modules linked in: > Pid:

[BUG] scheduling while atomic: init/1/0x00000002

filesystem) readonly on device 0:13. Freeing unused kernel memory: 480k freed BFS CPU scheduler v0.315 by Con Kolivas. BUG: scheduling while atomic: init/1/0x0002 Modules linked in: Pid: 1, comm: init Not tainted 2.6.33-zen2-20100307-stable #6 Call Trace: [] ? schedule+0x768/0xa10 [] ? sync_page