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 nev
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 t
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.
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
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
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 referr
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 hardw
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
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
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
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 packag
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 re
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
Exp
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=62e2c102cc1d2600381410c089ca9
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=62e2c102cc1d2600381410c089ca9a373595
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 depe
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
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-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: htt
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 depe
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
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,
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
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
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
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/linu
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-kernel-requ...@lists.debian.org
with a
> 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.
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
> 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, powe
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
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 o
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
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/lin
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 UNS
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
> experim
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...@vge
36 matches
Mail list logo
