Displaying 7 results from an estimated 7 matches for "whissi".
Did you mean:
whilst
2013 Sep 20
2
touch complain when shorewall start
hello, while starting shorewall4.5.20 on debian7 I get the following
from touch
touch: cannot touch `/var/lock/subsys/shorewall'': No such file or
directory
The needed file can not be created because the directory subsys is
not present!
If I creat the folder manuallly touch does not complain when
shorewall start! Thus it would be nice if durring start shorewall
could check if the
2013 Aug 31
23
ERROR: Log level INFO requires LOG Target in your kernel and iptables
Hi,
I have 2 Debian testing boxes running a very similar setup (both running
the latest aptosid kernel); on one of them, since the
iptables/libxtables10 packages have been upgraded from 1.4.19.1-1 to
1.4.20-2, shorewall-init can''t start shorewall anymore and for this
reason ifupdown also fails triggering firewall up.
Shorewall can be successfully started later on, and ifupdown starts
2015 Oct 01
2
req->nr_phys_segments > queue_max_segments (was Re: kernel BUG at drivers/block/virtio_blk.c:172!)
Hi,
Mike Snitzer wrote:
> This particular dm-crypt on virtio-blk issue is fixed with this commit:
> http://git.kernel.org/linus/586b286b110e94eb31840ac5afc0c24e0881fe34
>
> Linus pulled this into v4.3-rc3.
I have this patch applied to linux-4.1.9. This could be the reason why I
don't see the issue on boot with linux-4.1.9.
So is the freeze I am experiencing with linux-4.1.9
2015 Oct 01
0
req->nr_phys_segments > queue_max_segments (was Re: kernel BUG at drivers/block/virtio_blk.c:172!)
Hi,
seems like we have two problems:
The first (origin) problem seems to be already fixed by Mike's patch.
I applied the patch against linux-4.1.8, rebooted several times without
a problem. But I'll keep testing for sure.
The second problem is a new bug within linux-4.1.9: I experience the
> NMI watchdog: BUG: soft lockup - CPU#3 stuck for 23s!
freeze now on all my systems
2015 Oct 01
2
req->nr_phys_segments > queue_max_segments (was Re: kernel BUG at drivers/block/virtio_blk.c:172!)
Hi,
Mike Snitzer wrote:
> This particular dm-crypt on virtio-blk issue is fixed with this commit:
> http://git.kernel.org/linus/586b286b110e94eb31840ac5afc0c24e0881fe34
>
> Linus pulled this into v4.3-rc3.
I have this patch applied to linux-4.1.9. This could be the reason why I
don't see the issue on boot with linux-4.1.9.
So is the freeze I am experiencing with linux-4.1.9
2015 Oct 01
4
kernel BUG at drivers/block/virtio_blk.c:172!
Hi,
I have a virtual machine which fails to boot linux-4.1.8 while mounting
file systems:
> * Mounting local filesystem ...
> ------------[ cut here ]------------
> kernel BUG at drivers/block/virtio_blk.c:172!
> invalid opcode: 000 [#1] SMP
> Modules linked in: pcspkr psmouse dm_log_userspace virtio_net e1000 fuse nfs lockd grace sunrpc fscache dm_snapshot dm_bufio dm_mirror
2015 Oct 01
4
kernel BUG at drivers/block/virtio_blk.c:172!
Hi,
I have a virtual machine which fails to boot linux-4.1.8 while mounting
file systems:
> * Mounting local filesystem ...
> ------------[ cut here ]------------
> kernel BUG at drivers/block/virtio_blk.c:172!
> invalid opcode: 000 [#1] SMP
> Modules linked in: pcspkr psmouse dm_log_userspace virtio_net e1000 fuse nfs lockd grace sunrpc fscache dm_snapshot dm_bufio dm_mirror