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
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
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 bpov bin its
name. I suppose bpo stand for backport. See:
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
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 bpov bin its name. I
suppose bpo stand for
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
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 bpov bin its name. I
suppose bpo stand for backport. See:
uname -r
3.2.0-0.bpo.2-amd64
Then I added
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
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)
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
Made some new tests!
When the wlan-hardware is set by the kernel, also Windows-XP will not see the
card.
So it is proven: The kernel is setting my wlancard into some mode, which can
only be reset, when I take completely the power off the notebook.
Reinitialisation through a reboot or by
tags 665881 + moreinfo
quit
Hans-J. Ullrich wrote:
So I am attaching several logfiles to this message. Please apologize, it is
rather big, but I hope it will help.
Thanks. The messages indicate that this is a 2.6.37.y kernel, not from
Debian. Am I misunderstanding?
--
To UNSUBSCRIBE,
reopen 665881
quit
Hans-J. Ullrich wrote:
Today I got the same problem again, and could fix it with the already
mentioned
power-off-trick.
Thanks.
[...]
ehci_hcd :00:02.1: GetStatus port:6 status 001c03 0 ACK POWER sig=? CSC
CONNECT
hub 1-0:1.0: unable to enumerate USB device
Hello all,
it seems now, everything is working again. I cannot really explain, why.
However, it looks like the last update did fix the problem. I checked my logs,
and there were two packages updated, which are kernel related. Package kmod
was added, and package module-init-tools got from
Hi Jonathan,
strange things happen. At the moment it is running, no problems at all. But I
did not change anything. I swear, the last days it did not work. Also the
weired messages in syslog are gone, those
223.597826] ath5k phy0: gain calibration timeout (2412MHz)
[ 224.086320] ath5k
tags 665881 + unreproducible
quit
Hans-J. Ullrich wrote:
strange things happen. At the moment it is running, no problems at all. But I
did not change anything.
Thanks for the update, and no problem. Marking accordingly to save
future investigators some time.
(Maybe the signal strength,
found 665881 linux-2.6/3.2.12-1
quit
Hi Hans,
Hans wrote:
Package: linux-2.6
Severity: important
Thanks. Please specify a version number next time.
[...]
[ 175.461616] ath5k phy0: gain calibration timeout (2462MHz)
[ 175.462671] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Am Montag, 26. März 2012 schrieben Sie:
Hans-J. Ullrich wrote:
It is 3.2.0-2-amd64.
Thanks. Did you mean this to be a private reply?
Oops, no it was a mistake by me. Sent it again, please don't wonder.
To save a round-trip: the above is just a part of the package name
rather than its
Am Montag, 26. März 2012 schrieben Sie:
found 665881 linux-2.6/3.2.12-1
quit
Hi Hans,
Hi Jonathan,
Hans wrote:
Package: linux-2.6
Severity: important
Thanks. Please specify a version number next time.
It is 3.2.0-2-amd64.
[...]
[ 175.461616] ath5k phy0: gain calibration
Hans-J. Ullrich wrote:
Am Montag, 26. März 2012 schrieben Sie:
- can you reproduce this without using wicd? i.e.
install iw and iproute
stop wicd
ip link set wlan0 up
iw dev wlan0 connect -w SSID key d:0:WEP key
dhclient wlan0
with
iw event -t
20 matches
Mail list logo
