Hi Salvatore,
On Mon, Aug 31, 2020 at 11:31:26PM +0200, Salvatore Bonaccorso wrote:
> Thanks for the report. This looks the same as #966846, which we have
> pending fixed in the packaging repository.
>
> If you can expose the fixes for testing, then there are temporary and
> inofficial
Package: src:linux
Version: 4.19.132-1
Severity: normal
Dear Maintainer,
I am experiencing regular kernel crashes with my system. The crashes
seems a bit random and linked to limited activity. Looking at the
backtrace, it seems to be coming from the network stack (bridge
netfilter?). I have
On Sun, Nov 25, 2012 at 12:17:03AM -0800, Jonathan Nieder wrote:
Unfortunately 99f5944b8477 fixes a regression introduced in
v3.5-rc3~1^2~14 (Btrfs: use rcu to protect device-name, 2012-06-04),
so it can't be the fix on its own. How did you track down that patch?
E.g., did you bisect?
No I
tags 687456 patch
thanks
This bug has been fixed by this commit
commit 99f5944b8477914406173b47b4f261356286730b
Btrfs: do not strdup non existent strings
This is available in 3.6.0-rc5.
Can this patch be cherry-picked?
Antoine
--
To UNSUBSCRIBE, email to
severity 687456 normal
thanks
In fact I created the RAID1-like filesystem the wrong way (btrfs wiki
is wrong). I was using a RAID1 strategy only for the metadata and not
the data. With the following command-line to create the fs, I no longer
get the Oops:
# mkfs.btrfs -m raid1 -d raid1 /dev/vdb
Package: src:linux
Version: 3.2.23-1
Severity: grave
On a very fresh wheezy install I was able to crash the kernel by
playing with btrfs. I am reporting it using a kvm image but I first
had the bug on real boxes.
To reproduce the bug, I am creating a raid1 btrfs filesystem,
creating some file
Package: linux-image-2.6.25-2-686
Version: 2.6.25-3
Severity: wishlist
Tags: patch
The iwl3945 wifi driver does only have a limited support of the Monitor
mode: only beacon are captured, no data. In order to have the monitor
mode work properly, a patch must be applied.
I have opened a bug in
Package: linux-image-2.6.22-2-686
Version: 2.6.22-4
--- Please enter the report below this line. ---
I confirm I have the same bug with my samsung Q35 laptop but with an
untaint kernel (my video card is an Intel 945 GM). I'll try the
2.6.23-rc? kernel in order to see if this bug is still
Markus Raab wrote:
Now you know that it is a bug of the kernel, could you please try to reproduce
it on a more recent kernel?
With the actual 2.6.14 kernel, this bug has disappear. I think you can
close the bug.
Thank you, I have re-enabled my hal daemon.
Antoine.
--
To UNSUBSCRIBE,
9 matches
Mail list logo
