Bug#665881: [wheezy] module ath5k is blocking wlan-card
fixed 665881 linux-2.6/3.3~rc6-1~experimental.1 found 665881 linux/3.2.35-2 # not fixed in 3.2.y yet tags 665881 - fixed-upstream quit Hans-J. Ullrich wrote: > I installed linux-image-3.3.0-rc6-amd64_3.3~rc6-1~experimental.1_amd64.deb > from snapshots.debian.org, and its headers, but the bug never appeared. > > I did almos 10 - 15 rebootsx with no appearence of the bug. > > Then I started 3.2 kernel and the bug appeared again. Thanks, Hans. Marking accordingly so we don't forget. Am I correct in assuming the 3.2 kernel in question is 3.2.35-2? The next step is for us to ferret out another upstream patch to test. If you're bored before then, here are instructions for performing a "reverse bisect" to find when the fix seems to have been introduced. These instructions will probably be confusing: remember that a "good" kernel is one that successfully reproduces the bug, while a "bad" one is one that does not reproduce it. 0. get the kernel history, if you don't already have it: git clone \ https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux.git 1. initialize the bisection, configure, build, test: cd linux git bisect start git checkout v3.2 cp /boot/config-$(uname -r) .config; # current configuration make localmodconfig; # optional: minimize configuration make deb-pkg; # optionally with -j for parallel build dpkg -i ../; # as root reboot ...test test test ... Hopefully it reproduces the bug, so: git bisect good; # it reproduced the bug! 2. confirm upper bound: cd linux git checkout v3.3-rc6 make deb-pkg; # maybe with -j4 dpkg -i ../; # as root reboot ... test test test ... Hopefully it does not reproduce the bug, so: cd linux git bisect bad 3. A version half-way between is automatically checked out for testing. Test: make deb-pkg; # maybe with -j4 dpkg -i ../; # as root reboot ...test test test ... Record the result: cd linux git bisect good; # if it reproduces the bug git bisect bad; # if rebooting a few times does not reproduce it git bisect skip; # if some other bug makes it hard to test Repeat. Eventually git tells you the "first bad commit", which is the patch that alleviated symptoms. If the "gitk" package is installed, you can see the range of candidates at any step by running "git bisect visualize". To stop early, run "git bisect log", which produces a log that others can use to see your results so far or pick up where you left off. Even a few rounds can narrow down the search by quite a bit. You can read more about the "git bisect" tool at http://www.kernel.org/pub/software/scm/git/docs/git-bisect-lk2009.html but remember, for us a "bad" commit is a commit _not_ exhibiting the bug and a "good" commit is one that successfully reproduces the bug. Thanks again for your patience. Hopefully we will have a better idea of what's going on soon. Regards, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#665881: [wheezy] module ath5k is blocking wlan-card
Hi Jonathan and Ben. Some special news. I tested again. I installed linux-image-3.3.0-rc6-amd64_3.3~rc6-1~experimental.1_amd64.deb from snapshots.debian.org, and its headers, but the bug never appeared. I did almos 10 - 15 rebootsx with no appearence of the bug. Then I started 3.2 kernel and the bug appeared again. Maybe this information might be important for you. However, I guess I already tested this in the past, but this time all packagesd are up-to-date (state from today, of course). Hope this helps! Greets Hans -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#665881: [wheezy] module ath5k is blocking wlan-card
On Tue, 2013-01-01 at 14:54 +0100, Hans-J. Ullrich wrote: > Hi jonatahan, > > happy new year! > > > > >> Hadn't you tested 3.3-rc6 and found it to work ok? > > > > > > No, I never did. Maybe I should. > > > > Hmm, I could not find it in the repositories and neither in > backports.debian.org. I remember, there is another source, where packages go, > but I forgot, where it was. > > Can you point me to, where I find a 3.3-rc6-kernel-package? I guess, I will > find > the headers there, too. http://snapshot.debian.org/package/linux-2.6/ (also http://snapshot.debian.org/package/linux/ for later versions) Ben. -- Ben Hutchings It is easier to change the specification to fit the program than vice versa. signature.asc Description: This is a digitally signed message part
Bug#665881: [wheezy] module ath5k is blocking wlan-card
Hi Jonathan, I already tested 3.3-rc6. Just look into the history of this bugreport. Shall I test it new? Due to my tests in the past, it might be rather possible, to find out, in which kernel version and where a change was made, to inhibit the described behaviour. IMO it never appeared in 3.4 and higher. Hans -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#665881: [wheezy] module ath5k is blocking wlan-card
Hi jonatahan, happy new year! > > >> Hadn't you tested 3.3-rc6 and found it to work ok? > > > > No, I never did. Maybe I should. > Hmm, I could not find it in the repositories and neither in backports.debian.org. I remember, there is another source, where packages go, but I forgot, where it was. Can you point me to, where I find a 3.3-rc6-kernel-package? I guess, I will find the headers there, too. Cheers Hans -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#665881: [wheezy] module ath5k is blocking wlan-card
tags 665881 - moreinfo quit Hans-J. Ullrich wrote: > It patched fine, it loaded fine, but the bug did not disappear. Excellent. I assume you applied all four patches. Thanks for checking. >> Hadn't you tested 3.3-rc6 and found it to work ok? > > No, I never did. Maybe I should. I was referring to [1]. Given how hard this is to reproduce, I guess it couldn't hurt to try it and 3.2.y again. Thanks again for ruling out the calibration patches as the fix. I don't have any great ideas for what to try next, unfortunately. I'll be thinking about it more. Sincerely, Jonathan [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=271;bug=665881 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#665881: [wheezy] module ath5k is blocking wlan-card
Hi Jonathan! > Gah, that's way more work than should be required. Did the module > eventually load and just not work well, or were the instructions in my > message or in the kernel handbook broken? (The latter would be a very > serious bug, more serious than any particular instance of missing hardware > support.) > It patched fine, it loaded fine, but the bug did not disappear. > Hadn't you tested 3.3-rc6 and found it to work ok? > No, I never did. Maybe I should. > [...] > > > It sounds like debuginfo is not disabled like it should be. Did you forget > to run scripts/config --disable DEBUG_INFO? Ahm I forgot. I just build the whole kernel with make-kpkg -j4 --initrd kernel-image > > Sorry for the trouble and hope that helps. Next time, I will try better. > > Sincerely, > Jonathan Greets Hans -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#665881: [wheezy] module ath5k is blocking wlan-card
Hans-J. Ullrich wrote: > After several tries and 5 hours of compiling, I am sad, to tell you, the > patch, Ben sent me, is not working. Gah, that's way more work than should be required. Did the module eventually load and just not work well, or were the instructions in my message or in the kernel handbook broken? (The latter would be a very serious bug, more serious than any particular instance of missing hardware support.) > Just before you take work into a new patch, let me first try kernel-3.4, which > might be also possible to be released into next debian stable. Ben told so. I think you misunderstood, unfortunately. The wheezy kernel will be 3.2.y, but individual drivers can be backported when the new version is well tested. > I tested 3.1, 3.2, 3,5 and 3.6, but NOT 3.4! So maybe 3.4 might work as > wished, then no other action has to be done - just release debian with 3.4! Hadn't you tested 3.3-rc6 and found it to work ok? [...] > It has > only 20G, so kernel building breaks, with "no space left on device". It sounds like debuginfo is not disabled like it should be. Did you forget to run scripts/config --disable DEBUG_INFO? Sorry for the trouble and hope that helps. Sincerely, Jonathan
Bug#665881: [wheezy] module ath5k is blocking wlan-card
Hi Ben, hi Jonathan! After several tries and 5 hours of compiling, I am sad, to tell you, the patch, Ben sent me, is not working. Just before you take work into a new patch, let me first try kernel-3.4, which might be also possible to be released into next debian stable. Ben told so. I tested 3.1, 3.2, 3,5 and 3.6, but NOT 3.4! So maybe 3.4 might work as wished, then no other action has to be done - just release debian with 3.4! However, if kernel-3.2 shall be in next release, I am willing to test it for you. Maybe it will be easier, if you send me a precompiled module, which I then will test here. Please let me explain: I am not too lazy to compile, but my system is not good prepared for it. The main problem is, my /usr partition is too small. It has only 20G, so kernel building breaks, with "no space left on device". I built the kernel now on my older 64-bit-machine, which has only 512 MB RAM and is rather slow. It is not possible for me, to increase /usr (i.e. with gparted) without data loss, for it is ecrypted with luks. This just a little bit of information, why I am not so fast with the kernel building. All machines I am using (my 64-bit notebook, the 64-bit desktop-pc, my netbook and so on) are mostly permanently needed for my work, so they should not be killed somehow. I am happy, when they are working as wished! However, as I said, I am happy, when I can help, but results may be last a little longer as expected due to my "weired" environment. Thanks for your patience and best regards Hans -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#665881: [wheezy] module ath5k is blocking wlan-card
Hans-J. Ullrich wrote: > Sure! I did the following: Installed all needed packages, unpacked the source > package and made a symlink /usr/src/linux to /usr/src/linux-source-3.2 > > Patched: patch -p1 < /mypath/blah/0001ath5kxx.patch > So I did with all patches. > > Then copied /boot/config-3.2.0-4-amd64 to /usr/src/linux/.config (so I got > also > the version, worked before in the past this way). > > After that make menuconfig to check. > > Building then: make modules, because I just wanted to build only the ath5k > module. > > At last I copied the newly build module ath5k.ko and replaced it with the new > built one. > > depmod -a finished all. Thanks. The ABI of the module you built doesn't match the ABI of the installed kernel. Here's how I'd finish from there: scripts/config --disable DEBUG_INFO; # makes the build a lot smaller make deb-pkg; # optionally with -j for parallel build dpkg -i ../; # as root http://kernel-handbook.alioth.debian.org/ch-common-tasks.html has more details. FWIW all ideas for making that document more useful would be welcome --- making it easy for users to build a custom kernel is very important since it is what makes communication with upstream possible. :) [...] > But my time is limited, > as I cannot run compilatiuon at work and in the evening the time is often too > short, to run a compilation. Yes, no problem. When time is short, we can wait --- as long as it is clear how long to expect for a reply, waiting doesn't interfere much with other work. Regards, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#665881: [wheezy] module ath5k is blocking wlan-card
Hi Jonathan, > > Could you send the command you used? Generally you need to install > the new Debian package you built and reboot to test, but there are > other possibilities, too. The above doesn't tell me enough to know > what went wrong. Sure! I did the following: Installed all needed packages, unpacked the source package and made a symlink /usr/src/linux to /usr/src/linux-source-3.2 Patched: patch -p1 < /mypath/blah/0001ath5kxx.patch So I did with all patches. Then copied /boot/config-3.2.0-4-amd64 to /usr/src/linux/.config (so I got also the version, worked before in the past this way). After that make menuconfig to check. Building then: make modules, because I just wanted to build only the ath5k module. At last I copied the newly build module ath5k.ko and replaced it with the new built one. depmod -a finished all. > > You've made this same argument before. The sad situation we're in is > that only a small fraction of Debian users report bugs. You're a > representative of quiet masses of Debian users, potential Debian > users, and other Linux users with similar hardware. Meanwhile > stubborn people like me want to see all easily-fixable hardware > support bugs fixed, even if they only affect one person. > Well, if there are other people with the same problem, leave it open. Very ok for me! I just did not want to waste your time for a single person (=me), who cannot give much help back. > Sorry for the burden, but it really does help. > > Of course if you're sick of it, that's also fine --- we can mark the > bug as unreproducible, stop bothering you, and probably close it in a > couple of weeks. No, I am not sick and I will try it in the next time. But my time is limited, as I cannot run compilatiuon at work and in the evening the time is often too short, to run a compilation. > > Hoping that clarifies, > Jonathan Best regards Hans -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#665881: [wheezy] module ath5k is blocking wlan-card
Hi Hans, Hans-J. Ullrich wrote: > so, now after hours and hours of compiling, I could not manage to get the > patched module loaded. The system is telling something of "version mismatch". Could you send the command you used? Generally you need to install the new Debian package you built and reboot to test, but there are other possibilities, too. The above doesn't tell me enough to know what went wrong. > Whatever, I think, just close the bug and do no more efforts in fixing the > bug, > it is itz not worth for the following reasons: > > 1. This bug is now since kernel 3.1 and no one cared of it - except of me. You've made this same argument before. The sad situation we're in is that only a small fraction of Debian users report bugs. You're a representative of quiet masses of Debian users, potential Debian users, and other Linux users with similar hardware. Meanwhile stubborn people like me want to see all easily-fixable hardware support bugs fixed, even if they only affect one person. Sorry for the burden, but it really does help. Of course if you're sick of it, that's also fine --- we can mark the bug as unreproducible, stop bothering you, and probably close it in a couple of weeks. Hoping that clarifies, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#665881: [wheezy] module ath5k is blocking wlan-card
On Sat, 2012-09-15 at 14:39 +0200, elrond wrote: > According to this thread [1], these two patches [2][3] should fix the > issue. Can you backport to Wheezy kernel? [...] These are not obviously applicable to 3.2; in fact I think they may be fixing a different problem. Ben. -- Ben Hutchings Experience is what causes a person to make new mistakes instead of old ones. signature.asc Description: This is a digitally signed message part
Bug#665881: [wheezy] module ath5k is blocking wlan-card
tags 681232 - moreinfo quit elrond wrote: > According to this thread [1], these two patches [2][3] should fix the > issue. Don't those depend on the calibration rework from 3.3? Thanks, Jonathan > [1] https://bbs.archlinux.org/viewtopic.php?id=139270 > [2] [...];h=62e2c102cc1d2600381410c089ca9a37359577d2 > [3] [...];h=5c17ddc4a047c59638c7eb8537aa887a1ddb9b0b -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#665881: [wheezy] module ath5k is blocking wlan-card
According to this thread [1], these two patches [2][3] should fix the issue. Can you backport to Wheezy kernel? Cheers [1] https://bbs.archlinux.org/viewtopic.php?id=139270 [2] http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=commitdiff;h=62e2c102cc1d2600381410c089ca9a37359577d2 [3] http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=commitdiff;h=5c17ddc4a047c59638c7eb8537aa887a1ddb9b0b -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#665881: [wheezy] module ath5k is blocking wlan-card
Hans-J. Ullrich wrote: [...] > Error: Module powernow_k8 is in use > > modinfo powernow-k8 | grep depends > depends:processor,mperf > > rmmod mperf > Error: Module mperf is in use by: powernow_k8 > > rmmod processor > Error: Module processor is in use by: powernow_k8 Heh. A circular dependency. Does "modprobe -r powernow_k8" work? If not, how about "for module in powernow_k8 processor mperf; do rmmod -w $module; done"? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#665881: [wheezy] module ath5k is blocking wlan-card
Hi Jonathan, sorry for my late answer. I was tired and early in bed yesterday. Well, this is what the system is telling me (please do not matter, that this example was made with 3.5. But there is no difference to 3.2): rmmod powernow-k8 Error: Module powernow_k8 is in use modinfo powernow-k8 | grep depends depends:processor,mperf rmmod mperf Error: Module mperf is in use by: powernow_k8 rmmod processor Error: Module processor is in use by: powernow_k8 lsmod | grep freq cpufreq_conservative13147 0 cpufreq_stats 12866 0 cpufreq_userspace 12576 0 cpufreq_powersave 12454 0 The last four I could unload, but powernow-k8 still not. Hans -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#665881: [wheezy] module ath5k is blocking wlan-card
Hans-J. Ullrich wrote: >powernow-k8 can not be unloaded. What is the message in the kernel log when you try? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#665881: [wheezy] module ath5k is blocking wlan-card
Am Mittwoch, 12. September 2012 schrieb Jonathan Nieder: > notfound 665881 linux-2.6/3.3-1~experimental.1 > Does the problem go away if you unload the cpufreq driver > (powernow_k8)? Jonathan, I apologize, but powernow-k8 can not be unloaded. The kernel inhibits it. Of course I unloaded all dependent modules of powernow-k8 and all cpufreq-*. But no success. Sorry I can not tell better things. Hans -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#665881: [wheezy] module ath5k is blocking wlan-card
notfound 665881 linux-2.6/3.3-1~experimental.1 # Hans can reproduce it now --- nice! tags 665881 - unreproducible quit Hans-J. Ullrich wrote: > Am Mittwoch, 12. September 2012 schrieb Jonathan Nieder: >> Have you tested 3.2.23-1 again? [...] > I did, and the bug reappeared. Oh, excellent! Does the problem go away if you unload the cpufreq driver (powernow_k8)? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#665881: [wheezy] module ath5k is blocking wlan-card
Am Mittwoch, 12. September 2012 schrieb Jonathan Nieder: > Hans-J. Ullrich wrote: > > With 3.3-rc6 not a single problem during my tests. > > Thanks. > > >However, it might be a > > > > coincidence, but with 3.223, it happend almost every time, and with 3.3 > > not a single one. > > Have you tested 3.2.23-1 again? If not, please do. > > Jonathan I did, and the bug reappeared. Hans -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#665881: [wheezy] module ath5k is blocking wlan-card
Hans-J. Ullrich wrote: > With 3.3-rc6 not a single problem during my tests. Thanks. >However, it might be a > coincidence, but with 3.223, it happend almost every time, and with 3.3 not a > single one. Have you tested 3.2.23-1 again? If not, please do. Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#665881: [wheezy] module ath5k is blocking wlan-card
Am Mittwoch, 12. September 2012 schrieb Jonathan Nieder: Well, tested again. 10 times each. > It means my guess was wrong. Could you try the following two? > > - 3.3-rc6 > - 3.2.23-1 again > With 3.3-rc6 not a single problem during my tests. However, it might be a coincidence, but with 3.223, it happend almost every time, and with 3.3 not a single one. So maybe there is a fix since 3.3. :)) > Sorry for the fuss, > Jonathan Cheers, Hans -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#665881: [wheezy] module ath5k is blocking wlan-card
Hans-J. Ullrich wrote: > However, I tested now 3.3 and 3.4. None of them showed any problems (rebooted > both each 10 times, Windows - Linux - Windows - Linux and so on.) It means my guess was wrong. Could you try the following two? - 3.3-rc6 - 3.2.23-1 again Sorry for the fuss, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#665881: [wheezy] module ath5k is blocking wlan-card
Am Mittwoch, 12. September 2012 schrieb Jonathan Nieder: Hi Jonathan, > Hi again, > > Hans-J. Ullrich wrote: > > I would like to help. Can you tell me, where I find the packages of > > 3.3 and 3.4 images? I did not find them in the debian repositories. > > http://snapshot.debian.org/package/linux-2.6/ Thank you for pointing me to this. I lookes at backports.debian.org, so I didn't find. However, I tested now 3.3 and 3.4. None of them showed any problems (rebooted both each 10 times, Windows - Linux - Windows - Linux and so on.) I do not know, if this is good or evil. However, i am still running 3.5 from experimental, as I guess, 3.3 and 3.4 will not make it into testing. Still no problems, yet. I will test it now for a while, if no problems will occur in the next time, I will send you feedback. Thumbs up! Hans -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#665881: [wheezy] module ath5k is blocking wlan-card
Hi again, Hans-J. Ullrich wrote: > I would like to help. Can you tell me, where I find the packages of > 3.3 and 3.4 images? I did not find them in the debian repositories. http://snapshot.debian.org/package/linux-2.6/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#665881: [wheezy] module ath5k is blocking wlan-card
> I have my guesses about causes, but I am keeping them to myself until > we have the additional information I asked about, namely how 3.3.6 and > 3.4.1 do. > I would like to help. Can you tell me, where I find the packages of 3.3 and 3.4 images? I did not find them in the debian repositories. > Thanks for your patience, and sorry for the lack of clarity. No problem. > Jonathan Hans -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#665881: [wheezy] module ath5k is blocking wlan-card
Hans-J. Ullrich wrote: > Yes, it happened at once. Right after I booted Win7 and then booted into Linux > again. Ok, very good. [...] >> If it did, and assuming you rebooted out of Windows 7 to try it, >> there is no need to test 3.5.y any more. We already know it doesn't >> reproduce the bug under the same circumstances as 3.2.y did. > > So you know the reasons. No. We know the above because of the information you provided! * 3.2.y triggers the bug reproducibly * 3.5.y does not trigger the bug reproducibly I have my guesses about causes, but I am keeping them to myself until we have the additional information I asked about, namely how 3.3.6 and 3.4.1 do. Thanks for your patience, and sorry for the lack of clarity. Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#665881: [wheezy] module ath5k is blocking wlan-card
> Ok, that is how I understood it the first time. > > My question still stands: when it happened every time, did it happen > right away? > Yes, it happened at once. Right after I booted Win7 and then booted into Linux again. It happened also, when I booted Win 7, shut down the computer, powered off (power supply and power cell), and then started Linux. Did I describe it now better? > If it did, and assuming you rebooted out of Windows 7 to try it, > there is no need to test 3.5.y any more. We already know it doesn't > reproduce the bug under the same circumstances as 3.2.y did. > So you know the reasons. That is really good news! I read about, that 3.5 changed several things in bus strategies. > Hoping that clarifies, > Jonathan Thank you very much! Hans -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#665881: [wheezy] module ath5k is blocking wlan-card
Hans-J. Ullrich wrote: > Am Dienstag, 11. September 2012 schrieb Jonathan Nieder: >> Ah, I think I see where I misunderstood. When you said "The described >> behavior appears EVERY TIME", did you mean that it appears after a >> while (how long?), and not necessarily the first time you try to use >> wireless after rebooting out of Windows 7 into Linux? > > No, I meant it this way: I started Windows 7, then rebooted and started again > choosing "Linux", then the bahviour appeared every time (hmm, maybe "each > time" might be the better English expression). Ok, that is how I understood it the first time. My question still stands: when it happened every time, did it happen right away? If it did, and assuming you rebooted out of Windows 7 to try it, there is no need to test 3.5.y any more. We already know it doesn't reproduce the bug under the same circumstances as 3.2.y did. Hoping that clarifies, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#665881: [wheezy] module ath5k is blocking wlan-card
Am Dienstag, 11. September 2012 schrieb Jonathan Nieder: > Ah, I think I see where I misunderstood. When you said "The described > behavior appears EVERY TIME", did you mean that it appears after a > while (how long?), and not necessarily the first time you try to use > wireless after rebooting out of Windows 7 into Linux? No, I meant it this way: I started Windows 7, then rebooted and started again choosing "Linux", then the bahviour appeared every time (hmm, maybe "each time" might be the better English expression). So I guessed, that Windows switched something in the wirelesscard or the bus. > > Jonathan Hans -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#665881: [wheezy] module ath5k is blocking wlan-card
Hans-J. Ullrich wrote: > Am Dienstag, 11. September 2012 schrieb Jonathan Nieder: >> Drat. Am I correct in guessing that the prebuilt 3.3.6 package from >> http://snapshot.debian.org/package/linux-2.6/ reproduces it, while >> 3.4.1 does not? > > Huh, I did not test those versions. I just tested 3.2-xx (stock debian > testing) and now at your advice version 3.5. (experimental) > > If 3.5 will work, I can test 3.3 and 3.4, too, if needed. Ah, I think I see where I misunderstood. When you said "The described behavior appears EVERY TIME", did you mean that it appears after a while (how long?), and not necessarily the first time you try to use wireless after rebooting out of Windows 7 into Linux? Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#665881: [wheezy] module ath5k is blocking wlan-card
Am Dienstag, 11. September 2012 schrieb Jonathan Nieder: > Hans-J. Ullrich wrote: > > Well, I installed now 3.5-trunk-amd64 from experimental. First tests are > > showing good results. > > Drat. Am I correct in guessing that the prebuilt 3.3.6 package from > http://snapshot.debian.org/package/linux-2.6/ reproduces it, while > 3.4.1 does not? > Huh, I did not test those versions. I just tested 3.2-xx (stock debian testing) and now at your advice version 3.5. (experimental) If 3.5 will work, I can test 3.3 and 3.4, too, if needed. > Jonathan Hans -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#665881: [wheezy] module ath5k is blocking wlan-card
Hans-J. Ullrich wrote: > Well, I installed now 3.5-trunk-amd64 from experimental. First tests are > showing good results. Drat. Am I correct in guessing that the prebuilt 3.3.6 package from http://snapshot.debian.org/package/linux-2.6/ reproduces it, while 3.4.1 does not? Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#665881: [wheezy] module ath5k is blocking wlan-card
Am Montag, 10. September 2012 schrieb Jonathan Nieder: > Hans-J. Ullrich wrote: Hi Jonathan, > > 1. The described behaviour appears EVERY TIME, when I started Windows 7 > > on this system, and rebooted to linux again. > > That's very good to hear. Can you reproduce this with 3.5.y from > experimental? > Well, I installed now 3.5-trunk-amd64 from experimental. First tests are showing good results. I still could not reproduce the behaviour with this kernel. But it is too early, to make a final conclusion. So I will test it now for a few days and will then send a report. > If so, please send a description of the symptoms to > linux-wirel...@vger.kernel.org, cc-ing ath5k-de...@lists.ath5k.org, > Nick Kossifidis , and either me or this bug log > so we can track it. Be sure to mention > > - steps to reproduce, expected result, actual result, and how the >difference indicates a bug (should be simple enough) > > - which kernel versions you have tested and what happened with >each > > - full "dmesg" output from booting and trying to use wireless in the >affected state, as an attachment > > - any other weird symptoms or observations > Yes, if any strange behaviours occure, I will send them to the list. My current system is debian-testing, which I am running on several computers (mostly daily updated). These are 2 x amd64-cpus (a notebook Acer Aspire 7520G and a Desktop PC) and my Asus EEEPC 1005 HGO (i386). > Hopefully the symptoms will ring a bell for someone, who can provide > instructions or a patch to track down the cause further. Yeah, that might be great! > > Hope that helps, > Jonathan Thanky for the help. Best regards Hans -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#665881: [wheezy] module ath5k is blocking wlan-card
Hans-J. Ullrich wrote: > 1. The described behaviour appears EVERY TIME, when I started Windows 7 on > this system, and rebooted to linux again. That's very good to hear. Can you reproduce this with 3.5.y from experimental? If so, please send a description of the symptoms to linux-wirel...@vger.kernel.org, cc-ing ath5k-de...@lists.ath5k.org, Nick Kossifidis , and either me or this bug log so we can track it. Be sure to mention - steps to reproduce, expected result, actual result, and how the difference indicates a bug (should be simple enough) - which kernel versions you have tested and what happened with each - full "dmesg" output from booting and trying to use wireless in the affected state, as an attachment - any other weird symptoms or observations Hopefully the symptoms will ring a bell for someone, who can provide instructions or a patch to track down the cause further. Hope that helps, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
