Stefan Ott wrote:
> Do you have a particular commit in mind that might be responsible?
Here's a series[1] that's more likely to work as a full fix than the
single patch I sent (though I'm interested in both). Applies to a
3.2.y-based tree with "git am -3sc $(ls -1 /path/to/patches/0*)".
[1] htt
fixed 689096 linux/3.5.2-1~experimental.1
tags 689096 = upstream patch moreinfo
quit
Stefan Ott wrote:
> I've been using the 3.5-trunk-686-pae kernel for about a week now and
> so far there haven't been any further incidents
Drat. ;-)
[...]
> Do you have a particular commit in mind that might b
Hey
On Sun, Sep 30, 2012 at 10:57 AM, Jonathan Nieder wrote:
> Hi Stefan,
>
> Stefan Ott wrote:
>
>> Is there anything I can do to help debug this, other than building &
>> trying dozens of kernel versions to try and find the "bad" commit?
>
> I haven't looked closely into this report, but here a
Hi Stefan,
Stefan Ott wrote:
> Is there anything I can do to help debug this, other than building &
> trying dozens of kernel versions to try and find the "bad" commit?
I haven't looked closely into this report, but here are two quick
ideas:
A. Have you tried the 3.5.y kernel from experimental
4 matches
Mail list logo
