This bug was fixed in the package linux - 2.6.35-30.54
---
linux (2.6.35-30.54) maverick-proposed; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #794114
[ Upstream Kernel Changes ]
* Revert "xhci: Fix full speed bInterval encoding."
* Revert "USB: xhci - also
** Tags added: verification-done
** Tags added: verification-done-maverick
** Tags removed: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719446
Title:
systematic freezes on any k
The kernel from maverick-proposed seems to have fixed the problem for
me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719446
Title:
systematic freezes on any kernel version post 2.6.35-22
--
ubu
** Changed in: linux (Ubuntu Maverick)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719446
Title:
systematic freezes on any kernel version post 2.6.35-22
** Tags removed: needs-upstream-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719446
Title:
systematic freezes on any kernel version post 2.6.35-22
--
ubuntu-bugs mailing list
ubuntu-bugs@
Thanks, it seems to fix it :-).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719446
Title:
systematic freezes on any kernel version post 2.6.35-22
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ub
Patch accepted by Andi Kleen, 2.6.35.y stable maintainer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719446
Title:
systematic freezes on any kernel version post 2.6.35-22
--
ubuntu-bugs mailing
Eric - thanks for your response. I'll see about getting this patch into
2.6.35.y stable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719446
Title:
systematic freezes on any kernel version post 2.6
Tim - You presume correctly.
I've had problems with this since the introduction of 2.6.35-23, and
it's been a real pain in the posterior - I've become better acquainted
with Alt-SysReq than I really wanted to be. I'm running on hardware
very similar to that of the original bug report.
I'd run my
Eric - this fix is backported from 2.6.38 (which is Natty).
git describe --contains 88f5acf88ae6a9778f6d25d0d5d7ec2d57764a97
v2.6.38-rc1~216
Since you've had no prior input into this bug, I presume you were able
to first reproduce symptoms similar to those described by Alan and
Pawel?
--
You re
Tim: Your build of 2.6.35-29-generic fixes the problem, at least on my
system. Will we be seeing this fix in Natty?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719446
Title:
systematic freezes on
** Patch added: "Maverick: mm: page allocator: adjust the per-cpu counter
threshold when memory is low"
https://bugs.launchpad.net/ubuntu/maverick/+source/linux/+bug/719446/+attachment/1984371/+files/0001-mm-page-allocator-adjust-the-per-cpu-counter-thresho.patch
--
You received this bug not
OK, try this one (when it gets done building):
echo "deb http://ppa.launchpad.net/timg-tpi/ppa/ubuntu maverick main"|sudo tee
/etc/apt/sources.list.d/timg-tpi.list
sudo apt-get update
sudo apt-get -u dist-upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Pawel and Alan: ignore my previous transmission. Thats a backport to
Lucid, but you guys are interested in Maverick.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719446
Title:
systematic freezes on
Pawel and Alan:
Here is a Lucid test kernel with a backport of upstream commit
88f5acf88ae6a9778f6d25d0d5d7ec2d57764a97. Add my PPA thusly:
echo "deb http://ppa.launchpad.net/timg-tpi/ppa/ubuntu lucid main"|sudo tee
/etc/apt/sources.list.d/timg-tpi.list
sudo apt-get update
sudo apt-get -u dist-u
Pavel: Interesting. With my 2.6Gig of effective memory I dropped back
to 2.6.35-23, loaded firefox, gimp with 9 images between 1x5000 and
5000x5000, celestia, stellarium, sciTE. Best I could get was 67% memory
utilisation, and I couldn't get a freeze on copying data after many
attempts (thou
Pawel - that is the same commit suiggested by upstream to fix this
problem. At first glance, however, it looks like kind of an intrusive
backport. I'll take a more extensive look at it today.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Some short but intensive testing seems to indicate that, for me, Natty
kernel doesn't have this problem, which is good news.
It seems (but I didn't have a chance to test yet) that the fix might be
this patch from upstream:
http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.38.y.git;a=commi
Tim - Ok, I'll do that soon.
Alan - code in the patch that I bisected this to is ran when RAM is
getting full, so to make sure it occurs with more RAM added you'd need
to fill it up (GIMP with a large canvas works for me). My machine is
also single CPU but a Celeron - I'll post the exact infos wit
Ok. Won't be til next week. And I've just thrown more RAM at laptop,
will have to drop back to earlier kernels and make sure problem still
there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719446
Pawel - can you attach a proper stack trace when the problem occurs? Or
at least a better photo?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719446
Title:
systematic freezes on any kernel version
Alan - I should have looked at your boot message. You've got a 32 bit
installation, so use https://launchpad.net/~kernel-ppa/+archive/pre-
proposed/+files/linux-
image-2.6.38-8-generic_2.6.38-8.40~pre201103300902_i386.deb instead.
--
You received this bug notification because you are a member of
dpkg reports
dpkg: error processing
linux-image-2.6.38-8-generic_2.6.38-8.40~pre201103300902_amd64.deb (--install):
package architecture (amd64) does not match system (i386)
Despite me having an AMD Turion 64 cpu
?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
The first step is to figure out if this bug still exists upstream. In
order to do that please install the current Natty kernel from
https://launchpad.net/~kernel-ppa/+archive/pre-
proposed?field.series_filter=natty . I suggest just copying the deb and
installing directly ('cause its easier to remov
Pawel - your bisect results appear to be consistent with the Ubuntu
version of the kernel. There were 3 mm patches added in 2.6.35-23.36
which is when Alan begin to see this issue. I presume that the machine
you are using is also a single CPU ?
--
You received this bug notification because you ar
** Also affects: linux (Ubuntu Maverick)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Maverick)
Status: New => In Progress
** Changed in: linux (Ubuntu Maverick)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux (Ubuntu)
Importance:
Ok, many thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719446
Title:
systematic freezes on any kernel version post 2.6.35-22
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:
Alan - Yes, this page (and emails you should receive if there are any
updates!) should be the best way of knowing when a fix is officially
committed - packages containing it should appear fairly soon afterwards.
If there's any critical patch added to the kernel, you would need to
rebuild it yoursel
More fairly stupid newbie questions:
The custom kernel I made following Pawel's instructions works
flawlessly, so problem clearly solved.
It installed itself as installed as 2.6.35-28.
Now there's an update waiting to come in with the same version number.
Too soon to contain a fix for bug Pawel
YannUbuntu : I suppose you could go through same drill, compile you own
custom kernel sans the patch, following Pawel's instructions in comment
#24. Or you could wait til there's an official kernel build that
addresses the problem and see if tht makes your bug go away.
--
You received this bug
May I just add - as mentioned in one of my posts above, the commit just
preceding the one I bisected this bug to may be related, as on the system where
this bug occurs there are some very short (quarter to half a second?) freezes
in cases when this bug occurs, instead of a hard freeze, which dis
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719446
Title:
systematic freezes on any kerne
Dear all,
I have a very similar bug, but I am not sure it is duplicate or not : see bug
#706532
Please let me know what I can provide to help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719446
Ti
marking Triaged/High -- it seems Pawel and Alan reduced the issue to a
single commit. This may affect all single-core systems.
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification b
Dave,
Any chance the importance of this bug can be increased?
Looking at the code of the offending comment it may affect anyone running stock
kernel on single core processor (the code is ifdeffed-out for non-SMP build
configurations).
--
You received this bug notification because you are a mem
Thanks. Worked a treat. I had tried the other way around (linux-
headers-2.6.35-28-generic_2.6.35-28.49_i386.deb first). All set,
VirtualBox fine. Many thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Alan: you need to install linux-
headers-2.6.35-28-generic_2.6.35-28.49_i386.deb after installing linux-
headers-2.6.35-28_2.6.35-28.49_all.deb to get Virtual Box driver to
compile.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you ar
Sorry, I'm still in a mess with kernel headers.
In custom kernel the usual invocation to bring virtualBox up to speed:
/etc/init.d/vboxdrv setup
gets
Error! Your kernel headers for kernel 2.6.35-28-generic cannot be found at
/lib/modules/2.6.35-28-generic/build or /lib/modules/2.6.35-28-gener
Hi Pawel,
Been running your custom 2.6.35-28 for a few days, no freezes. So in my
opinion he patch you bisected out is probably my culprit as well as
yours.
Headers compiled okay as well. VirtualBox won't install in custom
2.6.35-28, probalby do do with that compile warning when I built kernel.
Ok, I'll try kernel next week. Thanks for all feedback.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719446
Title:
systematic freezes on any kernel version post 2.6.35-22
--
ubuntu-bugs mailing
(sorry for flooding your mailboxes)
Here's a tutorial how to bisect the kernel:
https://wiki.ubuntu.com/Kernel/KernelBisection
should you really want to do it. It is a bit time-consuming.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
linux-image is your kernel, which should now appear when you start your
computer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719446
Title:
systematic freezes on any kernel version post 2.6.35-22
you don't need to install linux-
headers-2.6.35-28-generic_2.6.35-28.49_i386.deb (it's only if you want
to have programs dependend on DKMS working with that particular kernel,
like VirtualBox).
If you DO want to install the headers, start terminal and go to the
folder where your sources sit (if y
I installed
linux-image-2.6.35-28-generic_2.6.35-28.49_i386.deb
by double clicking; it opened in Ubuntu Software Centre
,
Seemed to install successfully.
Then double clicked on
linux-headers-2.6.35-28-generic_2.6.35-28.49_i386.deb
and got "Dependency is not satisfiable: linux-headers-2.6.35-
Kernel compilation produces a lot of warnings and it's ok, as long as it
gives you a 'final product' in the form of .deb packages. Errors (as
opposed to warnings) will stop the compilation and not produce a .deb
package.
To remove packages installed via build dep, you can use this helpful tip:
htt
I'll just do without VirtualBox when testing custom kernel. I really
don't want to mess around with VirtualBox; I've had to rebuild me VMs
several times already, and it VirtualBox uninstall/install goes wrong
I'd be doing it again.
Cant tell whether build-dep linux finished.
==
Oh, and VirtualBox won't be enabled in kernel that you compile - you
would need to create and install kernel headers for your git source for
that; you can do this by running:
fakeroot debian/rules binary-indep
after building the kernel, which would give you linux-headers(...)
package which you ne
Looks like the effects of apt being interrupted while it was doing
something before. It shouldn't matter for kernel compilation, but you
may want to uninstall and reinstall VirtualBox at some point (which
should fix the error). You do need the build-dep linux though, so if the
error occured befor
Before I go any further:
sudo apt-get install fakeroot build-essential crash kexec-tools
makedumpfile kernel-wedge
generated following warnings
update-rc.d: warning: kdump start runlevel arguments (2) do not match
LSB Default-Start values (0 1 2 3 4 5)
update-rc.d: warning: kdump stop runlevel
Yeah, I can do that. Not instantly: sometime next week probably, maybe about
Wednesday or Thursday.
Maybe longer, in that to be completely sure I "can't reproduce the bug with the
kernel" can take time. But happy to have a go.
--
You received this bug notification because you are a member of
Alan - Are you able and willing to build your own kernel? Risks are more
or less the same as for installing a development kernel, but it takes a
bit of time to compile. If you don't want to build a kernel, but are
willing to trust me enough to test one I built, I'll post a generic
build here later
Hi Pawel,
Well I'm not on the kernel team so I'm not going to say for sure; I just know
the normal bug policy for the kernel is to keep them separate. However, if you
have a single patch that fixes it relative to the same starting point for both
of you that does sound pretty conclusive to me.
Dave - if Alan verifies this with the HEAD of maverick kernel repository
with this patch reverted, would that be a good-enough proof, or should
he verify it with the HEAD of mainline kernel with this patch reverted?
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Hi Pawel,
Could you file a separate bug for your problem unless Alan can verify that
the same works for him - it's always difficult to know if two peoples random
crashes have the same underlying cause.
Dave
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I'm impressed. Sounds a time-consuming business.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719446
Title:
systematic freezes on any kernel version post 2.6.35-22
--
ubuntu-bugs mailing list
u
Also, it seems that the main factor in replicability of this bug is a
single-core processor running a SMP kernel (which is stock in Ubuntu) -
any chance someone more knowledgeable in kernel development can have a
look at this ?
N.B. Alan, yes, I could have started with 2.6.35-23 - this would have
Ok, so this commit is related to this bug (after bisection):
58e15f5029c75b45adbcb25cd76a36d26a6c4297 is the first bad commit
commit 58e15f5029c75b45adbcb25cd76a36d26a6c4297
Author: Christoph Lameter
Date: Thu Sep 9 16:38:17 2010 -0700
mm: page allocator: calculate a better estimate of NR_
Know nada about git bisect (except what I just read.
I have problems from 2.6.35-22 onward, so it would be less work to do a
git bisect from 2.6.35-22 to 2.6.35-23?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
I meant, of course, if you did too
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719446
Title:
systematic freezes on any kernel version post 2.6.35-22
--
ubuntu-bugs mailing list
ubuntu-bugs@l
(N.B, it happens for me with 2.6.35.27 as well, so I'm bisecting
2.6.35-22 and 2.6.35-25.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719446
Title:
systematic freezes on any kernel version post 2.
I'm also having this problem and willing to do a git bisect to find the
offending patch. Will get back with any results later.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719446
Title:
systematic
Newbie question: assuming 2.6.38-999-generic may contain fixes that
elimnate most of freezes; when does it become a distributed release.
Will it become 2.6.35.26? O is it not that simple?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Here's right side of f1 terminal screen, 2.6.35.25 locked up
immediately on cp-r running for ten seconds or so.
Left side attached to previous comment
** Attachment added: "Bug719446_kernel2.6.35.25lockupInTerminalRightScreen.JPG"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/719446/
Only way I could get a half-decent picture of f1 terminal
screen was in two halves This is left half, 2.6.35.25 locked up
immediately on cp-r running for ten seconds or so.
** Attachment added: "Bug719446_kernel2.6.35.25lockupInTerminalLeftScreen.JPG"
https://bugs.launchpad.net/ubuntu/+sourc
I installed
2.6.38-999-generic
from
http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/
and got ambiguous results.
I got a freeze when copying sets of files of 600M+ in Nautilus,
but only after a half dozen tries
I wasn't able to get a freeze copying similar amounts using c -r in
Not very comfortable with trying latest development release, if there's
a reasonable change it will screw up my existing installation: I don;t
much fancy redoing everything I've done up til now. I don't yet have
partition backup/mirroring set up, so I've got no way to easily undo any
serious damag
Hi Alan,
Installing development versions in another partition is a good bet - however
being a development version any type of hideous error might occur and destroy
the other installation - that's what you get with development.
http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/ would
> Well, if you could get the exact text of that error it might help;
I think the text I sent was it, barring the code; but I'll try to get
that too using one of methods you suggested.
Log files not available, so I'll try the other methods you suggest next
week.
...
> Please be sure to c
Well, if you could get the exact text of that error it might help; but
probably the best thing is if I give you the standard response asking
you to try the new kernels being developed - if you can give it a go it
would be good to know if they fix it or if they give any
different/better diagnostics
Ok, ta. Let me know if I can gather more data and/or test anything.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719446
Title:
systematic freezes on any kernel version post 2.6.35-22
--
ubunt
Hi Alan,
Thanks for that. Those errors shouldn't happen - so it's pretty likely a
kernel bug.
There are a few ways to get those messages;
1) If you're lucky they'll have been recorded in /var/log/kern.log or
/var/log/kern.log.1 or /var/log/debug
2) A digital camera picture of the message
Neat. I'm linux newebie, never occurred to me to try this.
using 2.6.35.24 (??.. latest kernel)
in console: copied about 700MB from /dev/sda3 to same partition: works ok
same copy via nautilus seized up at about 500 Mb
In console after reboot: froze , then every minute spit out:
at
Hi Alan,
Have you tried doing a copy from a text virtual console (switch to it from
ctrl-alt-f1 - you can switch back using ctrl-alt-f7 or f8)
It's possible you might get a spew of error messages as it hangs on the console.
Dave
** Changed in: linux (Ubuntu)
Status: New => Incomplete
-
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719446
Title:
systematic freezes on any kernel version post 2.6.35-22
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.c
74 matches
Mail list logo
