Hey dear maintainers!

Did you change something related to this bug? Yesterday I updated linux-image
from version 3.2.12-1 -> 3.2.14-1, and since then the bug didn't appear right
now.

However, I suggest, to let the report a few days open, so I can see, if the
bug appears during the following week. I will inform you, as soon as I know
more.

Best regards

Hans




--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201204151857.56170.hans.ullrich@loop.de">http://lists.debian.org/201204151857.56170.hans.ullrich@loop.de

Hi Hans,

Hans-J. Ullrich wrote:

> Did you change something related to this bug? Yesterday I updated linux-image
> from version 3.2.12-1 -> 3.2.14-1, and since then the bug didn't appear right
> now.

This change, maybe:

- PCI: ASPM: Fix pcie devices with non-pcie children (Closes: #665420)

If you boot the old kernel with pcie_aspm added to the kernel command
line, does it work?



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120415223146.GC5813@burratino">http://lists.debian.org/20120415223146.GC5813@burratino

Jonathan Nieder wrote:

> If you boot the old kernel with pcie_aspm added to the kernel command
> line, does it work?

Sloppy of me. Make that:

If you boot the old kernel with pcie_aspm=force added to the kernel command
line, does it work? (I left out "=force" before.)



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120415223558.GD5813@burratino">http://lists.debian.org/20120415223558.GD5813@burratino

Jonathan Nieder wrote:

>> If you boot the old kernel with pcie_aspm added to the kernel command
>> line, does it work?

>Sloppy of me. Make that:

> If you boot the old kernel with pcie_aspm=force added to the kernel command
> line, does it work? (I left out "=force" before.)

Hi Jonathan,

I did as you adviced. First I installed the kernel version before. which is
3.2.12-1-amd64, and the package is something with "bpo"v bin its name. I
suppose bpo stand for backport. See:

uname -r
3.2.0-0.bpo.2-amd64

Then I added pcie_aspm=force to the commandline. With this added, I rebooted
several times, but I could not manage to reproduce this bug again. Did you
expect the bug with or without the added "pcie_asm=" switch?

It makes me not happy, when the reason cannot be found, although IMO your idea
might be correct. In the changelog it was the only bugfix, which might be
related to this bug.

On the other hand some other packages have been changed, too (i.e. libs), so
they might also be responsible for this or partly responsible.

Best regards

Hans







--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201204162117.56357.hans.ullrich@loop.de">http://lists.debian.org/201204162117.56357.hans.ullrich@loop.de

tags 665881 = upstream patch fixed-upstream
tags 665420 - pending
forcemerge 665420 665881
quit

Hans-J. Ullrich wrote:

> I did as you adviced. First I installed the kernel version before. which is
> 3.2.12-1-amd64, and the package is something with "bpo"v bin its name. I
> suppose bpo stand for backport. See:
>
> uname -r
> 3.2.0-0.bpo.2-amd64
>
> Then I added pcie_aspm=force to the commandline. With this added, I rebooted
> several times, but I could not manage to reproduce this bug again.

Perfect, thanks.

This is the same bug as #665420 and the bugs merged with it. Closing.

Ciao,
Jonathan



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120416193056.GZ5813@burratino">http://lists.debian.org/20120416193056.GZ5813@burratino

Am Montag, 16. April 2012 schrieb Jonathan Nieder:
> tags 665881 = upstream patch fixed-upstream
> tags 665420 - pending
> forcemerge 665420 665881
> quit
>
> Hans-J. Ullrich wrote:
> > I did as you adviced. First I installed the kernel version before. which
> > is 3.2.12-1-amd64, and the package is something with "bpo"v bin its
> > name. I suppose bpo stand for backport. See:
> >
> > uname -r
> > 3.2.0-0.bpo.2-amd64
> >
> > Then I added pcie_aspm=force to the commandline. With this added, I
> > rebooted several times, but I could not manage to reproduce this bug
> > again.
>
> Perfect, thanks.
>
> This is the same bug as #665420 and the bugs merged with it. Closing.
>
> Ciao,
> Jonathan

Hi Jonathan!
Yeah, great! I am very happy I could help you.

So I will uninstall the old kernel and run the latest kernel again. You made
my day!

Thank you very much for all the help and all the care you did!

Best regards

Hans




--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201204162135.42587.hans.ullrich@loop.de">http://lists.debian.org/201204162135.42587.hans.ullrich@loop.de

Jonathan Nieder wrote:
> Hans-J. Ullrich wrote:

>> I did as you adviced. First I installed the kernel version before. which is
>> 3.2.12-1-amd64, and the package is something with "bpo"v bin its name. I
>> suppose bpo stand for backport. See:
>>
>> uname -r
>> 3.2.0-0.bpo.2-amd64
>>
>> Then I added pcie_aspm=force to the commandline. With this added, I rebooted
>> several times, but I could not manage to reproduce this bug again.
>
> Perfect, thanks.

On second thought, if you get a chance to reproduce the bug using 3.2.12-1
without the pcie_aspm=force parameter, that would be a comfort. If I
understood correctly before, when it was happening this was pretty
repeatable, right?

If you don't have time for it, that's fine with me still.



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120416234221.GY12613@burratino">http://lists.debian.org/20120416234221.GY12613@burratino

Am Dienstag, 17. April 2012 schrieb Jonathan Nieder:
> Jonathan Nieder wrote:
> > Hans-J. Ullrich wrote:
> >> I did as you adviced. First I installed the kernel version before. which
> >> is 3.2.12-1-amd64, and the package is something with "bpo"v bin its
> >> name. I suppose bpo stand for backport. See:
> >>
> >> uname -r
> >> 3.2.0-0.bpo.2-amd64
> >>
> >> Then I added pcie_aspm=force to the commandline. With this added, I
> >> rebooted several times, but I could not manage to reproduce this bug
> >> again.
> >
> > Perfect, thanks.
>
> On second thought, if you get a chance to reproduce the bug using 3.2.12-1
> without the pcie_aspm=force parameter, that would be a comfort. If I
> understood correctly before, when it was happening this was pretty
> repeatable, right?
>
> If you don't have time for it, that's fine with me still.

Yes, the error was very good reproducable, If it is not in a hurry, I will be
able, to test it on next weekend. At the moment, my notebook is not available
for me. It is at my work, doing some longer job.

I have not always time for doing such tests. Mostly in the evening or at
weekends is a good time for me, as I am at the other time at work. I am
working in a little shop as a Computer guy, and so I have not much time do
private things. That was better, when I was in my sysadmin job before. )

So, I will test and report, as soon as I know more.

Best regards

Hans





--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201204182003.52379.hans.ullrich@loop.de">http://lists.debian.org/201204182003.52379.hans.ullrich@loop.de

Hi Jonathan,

today I tested with the old bpo-kernel, but sadly I could not manage to get
this bug shown again, neither with pcie= nor without pcie= addition.

But what i can say: This bug is gone! I have now rebooted almost 20 times and
it never appeared a single time. IMO that bugreport can safely be closed (I
think, it is already). It is a pity, I can give no other answer, but all my
tests to reproduce the bug with the older kernel failed.

However, I have already updated some software around it, for example some
libs. My system (debian-amd/testing) is beeig updated nearly daily, so I can
see bugs very fast.

This is in one way good, on the other way it might be bad (like this time).

Thank you for your help anyway. I hope, I can help next time better.

Best regards

Hans




--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201204192122.21656.hans.ullrich@loop.de">http://lists.debian.org/201204192122.21656.hans.ullrich@loop.de

unmerge 665881
notforwarded 665881
notfixed 665881 linux-2.6/3.2.14-1 , linux-2.6/3.3.2-1~experimental.1
tags 665881 = upstream unreproducible
quit

Hans-J. Ullrich wrote:

> Hi Jonathan,
>
> today I tested with the old bpo-kernel, but sadly I could not manage to get
> this bug shown again

Thanks again. So we are back where we were. Sorry for my
sloppiness.

I'm keeping the bug closed and marked unreproducible, so we can pick
up where we left off when it happens again.



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120419195147.GA2429@burratino">http://lists.debian.org/20120419195147.GA2429@burratino