search for: block

...cs because I couldn''t do much but hit the reset button after a couple of minutes.) On restart, dmesg said: [ 10.018204] Btrfs detected SSD devices, enabling SSD mode [ 10.049623] btrfs: free space inode generation (0) did not match free space cache generation (776515) [ 10.293808] block group 29020389376 has an wrong amount of free space [ 10.293810] btrfs: failed to load free space cache for block group 29020389376 [ 10.302647] block group 30094131200 has an wrong amount of free space [ 10.302649] btrfs: failed to load free space cache for block group 30094131200 [ 10.364...

Hello everybody. I got some strange problem when running wine with ALSA as sound driver. For example: when I run mdk2 (I compiled wine myself version 0.9.22 - newest for now) sound is very noisy and crack'y and I get tons of this errors: err:dsound:DSOUND_MixInBuffer length not a multiple of block size, len = 3122, block size = 4 err:dsound:DSOUND_MixInBuffer length not a multiple of block size, len = 3122, block size = 4 err:dsound:DSOUND_MixInBuffer length not a multiple of block size, len = 1258, block size = 4 err:dsound:DSOUND_MixInBuffer length not a multiple of block size, len = 2085,...

...ne,I meet a problem: I used reahat9.0(kernel 2.4.20-8smp,I installed a SCSI RAID Card),and there are always some problems and them the system is dead. is anyone can help me about it? Thanks Crist Below is the error log: Jun 11 22:19:03 mail1 kernel: EXT3-fs error (device sd(8,18)): ext3_free_blocks: Freeing blocks not in datazone - block = 1382828372, count = 1 Jun 11 22:19:03 mail1 kernel: EXT3-fs error (device sd(8,18)): ext3_free_blocks: Freeing blocks not in datazone - block = 1481734211, count = 1 Jun 11 22:19:03 mail1 kernel: EXT3-fs error (device sd(8,18)): ext3_free_blocks: Freei...

...0000.0103 power enable connect Port 2: 0000.0100 power Device Status: 0x0003 Self Powered Remote Wakeup Enabled Let me give you some more diag. Here is what I did: Having read that too large max_sectors sometimes gives problems, I did: root at tarnica:~# echo "64" > /sys/block/sda/device/max_sectors But before I tried without reducing max_sectors from the default - no difference. root at tarnica:~# mkfs.ext3 /dev/sda1 mke2fs 1.40-WIP (07-Apr-2007) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 523264 inodes, 1046521 blocks 52326 blo...

...e this capability to myself before fully committing to this system as the primary data storage. I'm having some problems resizing an ext3 filesystem after I've resized the underlying logical volume. Following the ext3 resize, fsck spits out lots of errors like: Pass 1: Checking inodes, blocks, and sizes Group 49's inode table at 1605636 conflicts with some other fs block. Relocate<y>? no I believe that I'm following the correct procedure for resizing the filesystem. Any pointers greatly appreciated. Thanks. A complete transcript demonstrating this problem follows: SEV...

Hi Everyone, I have pfSense running which supplies Asterisk with DHCP. I had some testing ports opened for a web server which I have totally closed now but when I chose option 10 (filter log) on pfSense I get all of this type of traffic (note that it was only 1 single IP and once I blocked that one it was like opening a can full of bees with all different IPs): tcpdump: WARNING: pflog0: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on pflog0, link-type PFLOG (OpenBSD pflog file), capture size 96 bytes 000000 rule 70...

...an search-engine of the archive of this list. Somehow the ext3 filesystem on one of my machines died an after a reboot grub wouldn't come up again. What I did so far: fsck -y /dev/hda4 fsck 1.35 (28-Feb-2004) e2fsck 1.35 (28-Feb-2004) Group descriptors look bad... trying backup blocks... Block bitmap for group 0 is not in group. (block 2553887680) Relocate? yes Inode bitmap for group 0 is not in group. (block 16777216) Relocate? yes Inode table for group 0 is not in group. (block 2238581760) WARNING: SEVERE DATA LOSS POSSIBLE. Relocate? yes...

Done with coccinelle: @@ expression e1, e2, e3; identifier rc; @@ ( rc = device_add_disk(e1, e2, e3); | + /* FIXME: handle error. */ device_add_disk(e1, e2, e3); ) Signed-off-by: Fam Zheng <famz at redhat.com> --- arch/m68k/emu/nfblock.c | 1 + arch/um/drivers/ubd_kern.c | 1 + arch/xtensa/platforms/iss/simdisk.c | 1 + drivers/block/DAC960.c | 1 + drivers/block/amiflop.c | 1 + drivers/block/aoe/aoeblk.c | 1 + drivers/block/ataflop.c | 1 + drivers/block/brd.c...

flight 12357 qemu-upstream-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/12357/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-oldkern 2 host-install(2) broken REGR. vs. 11890 build-i386 2 host-install(2) broken REGR. vs. 11890 build-amd64 2 host-install(2) broken REGR. vs. 11890 build-i386-old...

Hi all, This is about https://reviews.llvm.org/D26100 That change moves the block info block state from BitstreamReader to BitstreamCursor in order to accommodate multiple block info blocks (the idea is that the cursor would store the block info block state for whichever block info block is active for that cursor). Duncan objected to it on the grounds that we should aim for a d...

flight 12445 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/12445/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i386-oldkern 4 xen-build fail REGR. vs. 12437 build-i386 4 xen-build fail REGR. vs. 12437 build-amd64 4 xen-build fail REGR. vs. 12437 build-amd64-ol...

flight 13557 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/13557/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i386-pvops 2 host-install(2) broken REGR. vs. 13536 build-i386-oldkern 2 host-install(2) broken REGR. vs. 13536 build-amd64-oldkern 2 host-install(2) broken REGR. vs. 13536 build-amd64...

...roblem). I'll attach a dump of the console/verbose output and my .config in case it's of any use. Interestingly if I run the example launcher before applying patch 05 (in other words with the old bzImage loader code) it just stops early with an "unhandled trap 14": $./lguest --block=disk.img 256 /boot/vmlinuz-2.6.23-rc9 --initrd=/boot/initrd.img-2.6.23-rc9 --tunnet=192.168.150.1 --verbose root=/dev/vda1 single Guest base is at 0xa7cba000 device 0: console Unpacked size 3506404 addr 0xa7dba000 mapped initrd /boot/initrd.img-2.6.23-rc9 size=14139392 @ 0xf284000 Linear mapp...

...roblem). I'll attach a dump of the console/verbose output and my .config in case it's of any use. Interestingly if I run the example launcher before applying patch 05 (in other words with the old bzImage loader code) it just stops early with an "unhandled trap 14": $./lguest --block=disk.img 256 /boot/vmlinuz-2.6.23-rc9 --initrd=/boot/initrd.img-2.6.23-rc9 --tunnet=192.168.150.1 --verbose root=/dev/vda1 single Guest base is at 0xa7cba000 device 0: console Unpacked size 3506404 addr 0xa7dba000 mapped initrd /boot/initrd.img-2.6.23-rc9 size=14139392 @ 0xf284000 Linear mapp...

> On Oct 28, 2016, at 6:00 PM, Peter Collingbourne <peter at pcc.me.uk> wrote: > > Hi all, > > This is about https://reviews.llvm.org/D26100 <https://reviews.llvm.org/D26100> > > That change moves the block info block state from BitstreamReader to BitstreamCursor in order to accommodate multiple block info blocks (the idea is that the cursor would store the block info block state for whichever block info block is active for that cursor). > > Duncan objected to it on the grounds that we should a...

...vif = [ ''mac=mac=00:16:3e:00:00:12'' ] # # Behaviour # on_poweroff = ''destroy'' on_reboot = ''restart'' on_crash = ''restart'' domU console: vif vif-0: 2 parsing device/vif/0/mac xen-vbd: registered block device major 8 blkfront: sda1: barriers enabled blkfront: sda2: barriers enabled XENBUS: Timeout connecting to device: device/vif/0 (state 6) XENBUS: Device with no driver: device/console/0 Freeing unused kernel memory: 196k freed softcursor: no version for "struct_module" found: ke...

..., so it can be added before KOBJ_ADD. Also add basic error handling around device_add_disk code, (or add FIXME comment where work is left). Fam Zheng (15): disk: Drop add_disk in favor of device_add_disk genhd: Return error from register_disk() genhd: Return error from blk_register_region block: Return error from blk_integrity_add genhd: Return error from disk_{add,alloc}_events genhd: Add return code to device_add_disk genhd: Add attribute group parameter to device_add_disk nvme: Pass attribute group to device_add_disk virtio-blk: Pass attribute group to device_add_disk mtd:...

..., so it can be added before KOBJ_ADD. Also add basic error handling around device_add_disk code, (or add FIXME comment where work is left). Fam Zheng (15): disk: Drop add_disk in favor of device_add_disk genhd: Return error from register_disk() genhd: Return error from blk_register_region block: Return error from blk_integrity_add genhd: Return error from disk_{add,alloc}_events genhd: Add return code to device_add_disk genhd: Add attribute group parameter to device_add_disk nvme: Pass attribute group to device_add_disk virtio-blk: Pass attribute group to device_add_disk mtd:...

It would go something like like the code below. The goal would be to turn the basic blocks which the graph looks like "...->x->y->..." where the instructions of x and y could live in the same basic block without a jump or fall through in between. bool runOnMachineFunction(MachineFunction &mf) { BitVector seen( mf.size() ); for( unsigned i = 0, e =...

On 11/20/2017 08:42 PM, Jens Axboe wrote: > On 11/20/2017 12:29 PM, Christian Borntraeger wrote: >> >> >> On 11/20/2017 08:20 PM, Bart Van Assche wrote: >>> On Fri, 2017-11-17 at 15:42 +0100, Christian Borntraeger wrote: >>>> This is >>>> >>>> b7a71e66d (Jens Axboe 2017-08-01 09:28:24 -0600 1141) * are mapped to