On Mon, 4 May 2015, Grumbach, Emmanuel wrote:
> Sorry, my bad. I lost context here... So I really don't know what to
> say. I can't see any iwlwifi commit that could be causing this, OTOH,
> bisection didn't bring any results. You can try to unregister the device
> from PCI and then to rescan.
On Mon, 2015-05-04 at 08:55 +0200, Jiri Kosina wrote:
> On Mon, 4 May 2015, Grumbach, Emmanuel wrote:
>
> > > so over a past few days, I tried to perform a bisect, but failed as
> > > expected. The issue is not reliably enough reproducible for me, so I
> > > ended
> > > up with a completely bog
On Mon, 4 May 2015, Grumbach, Emmanuel wrote:
> > so over a past few days, I tried to perform a bisect, but failed as
> > expected. The issue is not reliably enough reproducible for me, so I ended
> > up with a completely bogus commit.
> >
> > *However*, now that I have been following the cause
On Sun, 2015-05-03 at 23:42 +0200, Jiri Kosina wrote:
> Hi,
>
> so over a past few days, I tried to perform a bisect, but failed as
> expected. The issue is not reliably enough reproducible for me, so I ended
> up with a completely bogus commit.
>
> *However*, now that I have been following the
Hi,
so over a past few days, I tried to perform a bisect, but failed as
expected. The issue is not reliably enough reproducible for me, so I ended
up with a completely bogus commit.
*However*, now that I have been following the causes and symptoms more
closely (due to the bisect attempt), I ha
On Thu, 2015-04-23 at 14:48 +0200, Piotr Karbowski wrote:
> Hello,
>
> On Thu, Apr 23, 2015 at 11:15 AM, Jiri Kosina wrote:
> > On Thu, 23 Apr 2015, Grumbach, Emmanuel wrote:
> >
> >> > I will try it, but I expect the result to be bogus because of this,
> >> > unfortunately.
> >>
> >> I can under
Hello,
On Thu, Apr 23, 2015 at 11:15 AM, Jiri Kosina wrote:
> On Thu, 23 Apr 2015, Grumbach, Emmanuel wrote:
>
>> > I will try it, but I expect the result to be bogus because of this,
>> > unfortunately.
>>
>> I can understand. A few users reported that this bug occurred more
>> reliably when mov
On Thu, 23 Apr 2015, Grumbach, Emmanuel wrote:
> > I will try it, but I expect the result to be bogus because of this,
> > unfortunately.
>
> I can understand. A few users reported that this bug occurred more
> reliably when moving their system, although it seems very weird to me.
My "feeling"
On Thu, 2015-04-23 at 10:15 +0200, Jiri Kosina wrote:
> On Thu, 23 Apr 2015, Grumbach, Emmanuel wrote:
>
> > > I've been running current Linus' tree and have been getting system
> > > lockups
> > > frequently. After a few "silent" lockups, I was able to obtain a dmesg
> > > before the machine t
On Thu, 23 Apr 2015, Grumbach, Emmanuel wrote:
> > I've been running current Linus' tree and have been getting system lockups
> > frequently. After a few "silent" lockups, I was able to obtain a dmesg
> > before the machine turned dead again (wifi stopped working shortly before
> > that).
> >
Hi,
On Wed, 2015-04-22 at 22:42 +0200, Jiri Kosina wrote:
> Hi,
>
> I've been running current Linus' tree and have been getting system lockups
> frequently. After a few "silent" lockups, I was able to obtain a dmesg
> before the machine turned dead again (wifi stopped working shortly before
>
Hi,
I've been running current Linus' tree and have been getting system lockups
frequently. After a few "silent" lockups, I was able to obtain a dmesg
before the machine turned dead again (wifi stopped working shortly before
that).
Before starting to debug / bisect (last known good on this mach
12 matches
Mail list logo
