Re: [Bug 741930] Re: [natty] nvidia binary packages for older cards - dependencies not met
I'd say a simpler but still useful thing would be to make sure that if some hardware isn't compatible at the time of release because a proprietary driver is required (and that's the situation here - Unity doesn't work on Nouveau), then a big, red note of that should be made in the "release notes" prompt encouraging for upgrade, so that people can wait until Nvidia or any other vendor provides updated driver. Alternatively, the upgrading script should warn user about such incompatibilities at the start of the process, allowing them to easily cancel. On Tue, May 10, 2011 at 8:09 AM, Andrea Mazzilli <741...@bugs.launchpad.net> wrote: > for the next Ubuntu release, if the nvidia-96 driver are not compatible > with xorg again, it's possible add a "legacy xorg" to the repository? > > something like: > xserver-xorg-core (new version, for the driver compatible) > xserver-xorg-core-1.9 (legacy, for the driver that not support new xorg) > > then the nvidia-96 package require the legacy xorg instead of the new > one > > -- > You received this bug notification because you are a direct subscriber > of the bug. > https://bugs.launchpad.net/bugs/741930 > > Title: > [natty] nvidia binary packages for older cards - dependencies not met > > Status in NVIDIA Drivers Ubuntu: > Confirmed > Status in “nvidia-graphics-drivers” package in Ubuntu: > Invalid > Status in “nvidia-graphics-drivers-173” package in Ubuntu: > Fix Released > Status in “nvidia-graphics-drivers-96” package in Ubuntu: > Confirmed > > Bug description: > Package has broken dependencies that cannot be met. > xorg-video-abi-8.0 > xserver-xorg-core (>= 2:1.8.99.905-1ubuntu3) > > Steps to reproduce: > 1. Install Natty beta & do sudo apt-get upgrade and dist-upgrade > 2. Try sudo apt-get install nvidia-96 to get the error. > > (confirmed to still occur in beta 1). > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/741930/+subscribe > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/741930 Title: [natty] nvidia binary packages for older cards - dependencies not met -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 301958] Re: [needs-packaging] no working driver for sis 671/771 video cards
Timo - would it not be possible to put this driver in universe, as a service for users who still have this chip? I think it will become less relevant with time as I've not seen any newer laptops/netbooks having using SiS 671, so it might just happen that when it is finally merged with the FD.o, next to no-one might acutally need it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/301958 Title: [needs-packaging] no working driver for sis 671/771 video cards -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 741930] Re: [natty] nvidia binary packages for older cards - dependencies not met
Algo, ubuntu is not really at fault here, it's more to do with the relationship between nvidia and xorg developers. On 28/04/2011, Algo <741...@bugs.launchpad.net> wrote: > Very very trouble! > > Last time upgrade to Ubuntu 10.10, I got deep trouble with nvidia-96. > This time upgrade to Ubuntu 11.04, I got deep trouble with nvidia-96 again!! > > -- > You received this bug notification because you are a direct subscriber > of the bug. > https://bugs.launchpad.net/bugs/741930 > > Title: > [natty] nvidia binary packages for older cards - dependencies not met > > Status in NVIDIA Drivers Ubuntu: > Confirmed > Status in “nvidia-graphics-drivers” package in Ubuntu: > Invalid > Status in “nvidia-graphics-drivers-173” package in Ubuntu: > Fix Released > Status in “nvidia-graphics-drivers-96” package in Ubuntu: > Confirmed > > Bug description: > Package has broken dependencies that cannot be met. > xorg-video-abi-8.0 > xserver-xorg-core (>= 2:1.8.99.905-1ubuntu3) > > Steps to reproduce: > 1. Install Natty beta & do sudo apt-get upgrade and dist-upgrade > 2. Try sudo apt-get install nvidia-96 to get the error. > > (confirmed to still occur in beta 1). > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/741930/+subscribe > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/741930 Title: [natty] nvidia binary packages for older cards - dependencies not met -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 719446] Re: systematic freezes on any kernel version post 2.6.35-22
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.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 741930] Re: [natty] nvidia binary packages for older cards - dependencies not met
** Description changed: Package has broken dependencies that cannot be met. xorg-video-abi-8.0 xserver-xorg-core (>= 2:1.8.99.905-1ubuntu3) Steps to reproduce: - 1. Install Natty alpha 3 & do sudo apt-get upgrade and dist-upgrade + 1. Install Natty beta & do sudo apt-get upgrade and dist-upgrade 2. Try sudo apt-get install nvidia-96 to get the error. + + (confirmed to still occur in beta 1). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/741930 Title: [natty] nvidia binary packages for older cards - dependencies not met -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 741930] Re: [natty] nvidia binary packages for older cards - dependencies not met
** Also affects: nvidia-graphics-drivers-96 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-96 (Ubuntu) Status: New => Confirmed ** Also affects: nvidia-graphics-drivers-173 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-173 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/741930 Title: [natty] nvidia binary packages for older cards - dependencies not met -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 741930] Re: [natty] nvidia binary packages for older cards - dependencies not met
Sorry for setting this to nvidia-graphics-drivers - I wasn't sure how to set the bug as affecting multiple packages? ** Summary changed: - [natty] nvidia-96 dependencies not met + [natty] nvidia binary packages for older cards - dependencies not met ** Changed in: nvidia-graphics-drivers-96 (Ubuntu) Status: New => Confirmed ** Package changed: nvidia-graphics-drivers-96 (Ubuntu) => nvidia- graphics-drivers (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/741930 Title: [natty] nvidia binary packages for older cards - dependencies not met -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 719446] Re: systematic freezes on any kernel version post 2.6.35-22
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=commit;h=88f5acf88ae6a9778f6d25d0d5d7ec2d57764a97 I'll test this kernel more and perhaps try to apply this patch to Maverick kernel and see if it solves the problem as I suspect. -- 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.com/mailman/listinfo/ubuntu-bugs
[Bug 719446] Re: systematic freezes on any kernel version post 2.6.35-22
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 with the stack trace. -- 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.com/mailman/listinfo/ubuntu-bugs
[Bug 719446] Re: systematic freezes on any kernel version post 2.6.35-22
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 yourself to get it (rembering to revert the commit) until a patch for this bug is officially incorporated into Ubuntu kernel. -- 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.com/mailman/listinfo/ubuntu-bugs
[Bug 706532] Re: [Regression] Freezes since kernel 2.6.35-23
Yann, I'm going to mark this bug as invalid, as it's next to impossible to find a culprit of a software problem if hardware is unreliable. If you're suffering from https://bugs.launchpad.net/bugs/719446 , then it is already triaged with high priority so it will be fixed. If you're suffering from a different bug, any diagnosing efforts are going to be hampered by hardware problems. If you manage to find and fix a cause for your computer crashing during memtest (most likely culprit is RAM), feel free to re-open this bug by marking it as 'New' again. ** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/706532 Title: [Regression] Freezes since kernel 2.6.35-23 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 706532] Re: [Regression] Freezes since kernel 2.6.35-23
Some other hardware problems are also possible, but less likely. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/706532 Title: [Regression] Freezes since kernel 2.6.35-23 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 706532] Re: [Regression] Freezes since kernel 2.6.35-23
Most likely reason is that your RAM is damaged and you need to replace it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/706532 Title: [Regression] Freezes since kernel 2.6.35-23 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 741930] [NEW] [natty] nvidia-96 dependencies not met
Public bug reported: Package has broken dependencies that cannot be met. xorg-video-abi-8.0 xserver-xorg-core (>= 2:1.8.99.905-1ubuntu3) Steps to reproduce: 1. Install Natty alpha 3 & do sudo apt-get upgrade and dist-upgrade 2. Try sudo apt-get install nvidia-96 to get the error. ** Affects: nvidia-graphics-drivers-96 (Ubuntu) Importance: Undecided Status: New ** Tags: natty nvidia restriced -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/741930 Title: [natty] nvidia-96 dependencies not met -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 706532] Re: [Regression] Freezes since kernel 2.6.35-23
Yann, first of all can you test your RAM for defects? Hold left shift key while powering on your computer to see GRUB boot menu and select memory test from there. You should run it for a few hours (probably best overnight) and see if there are any errors reported at the bottom of the screen (in which case you would need to replace your RAM as it is damaged). I'm asking you to do this as you said you experienced freezes even on 2.6.35-22. Also, looking at ProcCpuinfo.txt which you attached to this bug report, your processor is indeed single core. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/706532 Title: [Regression] Freezes since kernel 2.6.35-23 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 719446] Re: systematic freezes on any kernel version post 2.6.35-22
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 disappear when that commit is removed. Both of those commits modify page allocator (I can find that commit's sha-1 if needed, but it directly precedes this one). I can also report another bug for it if needed, but it may be wiser to simply have a look at both of the commits. I don't have any experience in kernel development so I may of course be mistaken as to the role of preceding commit. Also, my way of reproducing this bug, which seemed to work every time: 1. On an affected system, run Open Office, GIMP, Inkscape or any other memory-hogging application. 2. Use scp to copy a large file over the local network (I used a 2 Gb DVD image). -- 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.com/mailman/listinfo/ubuntu-bugs
[Bug 719446] Re: systematic freezes on any kernel version post 2.6.35-22
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 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.com/mailman/listinfo/ubuntu-bugs
[Bug 719446] Re: systematic freezes on any kernel version post 2.6.35-22
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 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.com/mailman/listinfo/ubuntu-bugs
[Bug 719446] Re: systematic freezes on any kernel version post 2.6.35-22
(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. 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.com/mailman/listinfo/ubuntu-bugs
[Bug 719446] Re: systematic freezes on any kernel version post 2.6.35-22
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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 719446] Re: 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 you followed my tutorial exactly: cd kernel-custom cd ubuntu-maverick fakeroot debian/rules binary-indep which would generate, among other files, linux-headers-2.6.35-28 . -- 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.com/mailman/listinfo/ubuntu-bugs
[Bug 719446] Re: systematic freezes on any kernel version post 2.6.35-22
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: http://www.webupd8.org/2010/10/undo-apt-get-build-dep-remove-build.html -- 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.com/mailman/listinfo/ubuntu-bugs
[Bug 719446] Re: systematic freezes on any kernel version post 2.6.35-22
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 need to install so DKMS is able to auto-compile VirtualBox kernel module. -- 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.com/mailman/listinfo/ubuntu-bugs
[Bug 719446] Re: systematic freezes on any kernel version post 2.6.35-22
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 before the installation finished, then there's a (very small) chance that you can get some really weird errors when you attempt to compile the kernel if you don't fix it. The first two warnings from update-rc.d don't really mean anything bad, it apparently is a configuration bug in Ubuntu ( https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/569980 ) - kdump is used to create kernel crashdumps and all this is saying is that they will only be created during 'normal operation' (runlevel 2) rather than also during startup, shutdown, etc (which have different runlevels). -- 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.com/mailman/listinfo/ubuntu-bugs
[Bug 719446] Re: systematic freezes on any kernel version post 2.6.35-22
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. If you can't reproduce the bug with the kernel made with these steps, it means we suffer from the same thing. Maverick git repository: If so, can you please follow the instructions here for installing the tools: https://help.ubuntu.com/community/Kernel/Compile#Tools you'll need (steps are the same as for Lucid). then, in the terminal, make a directory and download repository from git (warning: it's few hundred megabytes), e.g. mkdir kernel-custom cd kernel-custom git clone git://kernel.ubuntu.com/ubuntu/ubuntu-maverick.git cd ubuntu-maverick git checkout -b bug-testing master git revert 58e15f5029c75b45adbcb25cd76a36d26a6c4297 <> fakeroot debian/rules clean AUTOBUILD=1 NOEXTRAS=1 fakeroot debian/rules binary-generic This should build for you two .deb packages for linux-image (which you need to install) and linux-headers (which isn't necessary for this testing) with version number of 2.6.35-28.49 and place them in your kernel-custom directory. After installation, you need to reboot and select the new kernel. You can uninstall it in a standard way (synaptic, dpkg - choose your favourite) after you've done 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@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 719446] Re: systematic freezes on any kernel version post 2.6.35-22
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, 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.com/mailman/listinfo/ubuntu-bugs
[Bug 719446] Re: systematic freezes on any kernel version post 2.6.35-22
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 saved me ~1 compilation and reboot, probably. -- 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.com/mailman/listinfo/ubuntu-bugs
[Bug 719446] Re: systematic freezes on any kernel version post 2.6.35-22
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_FREE_PAGES when memory is low and kswapd is awake commit aa45484031ddee09b06350ab8528bfe5b2c76d1c upstream. Ordinarily watermark checks are based on the vmstat NR_FREE_PAGES as it is cheaper than scanning a number of lists. To avoid synchronization overhead, counter deltas are maintained on a per-cpu basis and drained both periodically and when the delta is above a threshold. On large CPU systems, the difference between the estimated and real value of NR_FREE_PAGES can be very high. If NR_FREE_PAGES is much higher than number of real free page in buddy, the VM can allocate pages below min watermark, at worst reducing the real number of pages to zero. Even if the OOM killer kills some victim for freeing memory, it may not free memory if the exit path requires a new page resulting in livelock. This patch introduces a zone_page_state_snapshot() function (courtesy of Christoph) that takes a slightly more accurate view of an arbitrary vmstat counter. It is used to read NR_FREE_PAGES while kswapd is awake to avoid the watermark being accidentally broken. The estimate is not perfect and may result in cache line bounces but is expected to be lighter than the IPI calls necessary to continually drain the per-cpu counters while kswapd is awake. Signed-off-by: Christoph Lameter Signed-off-by: Mel Gorman Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds Signed-off-by: Greg Kroah-Hartman (cherry picked from commit 87f1cbdee91c60af6dd255226e792a6410d77fbb 2.6.35.6) Signed-off-by: Leann Ogasawara :04 04 56b962edbe8815533041d28a1b4c744bf810c302 b93faeb21bff790a5e90f1370509a4903bb4fd9a M include :04 04 a3d6ce0e31b4552a22ef291e0a66441b78744ac2 4664c82b2f1aa2452751144455f9f133cbf71270 M mm It *MIGHT* be also connected to the previous commit (7dd373d47c6e0dc124924348265be61990ba0fb6) as I observed some short (0.5 second) freezes while testing it, but no errors. I'll see if I can revert it in HEAD and whether it helps - will post soon. -- 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.com/mailman/listinfo/ubuntu-bugs
[Bug 719446] Re: systematic freezes on any kernel version post 2.6.35-22
(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.6.35-22 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 719446] Re: systematic freezes on any kernel version post 2.6.35-22
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 freezes on any kernel version post 2.6.35-22 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 301958] Re: no working driver for sis 671/771 video cards
I've written to maintainer of the satux driver, and he said that their driver is based on code from here : http://www.linuxconsulting.ro/xorg- drivers/ with some patches. He promised to publish them on his blog - but haven't done this yet, apparently. -- no working driver for sis 671/771 video cards https://bugs.launchpad.net/bugs/301958 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 207409] Re: [HARDY] xserver-xorg does not auto-configure correctly
hmmm... Stupid question - you are running it from GUI, not console?? You may also try to run dexconf first, just to reset xorg.conf to whatever it thinks is default and then try again. (it looks like displayconfig-gtk couldn't get screen size - I'd report this as a separate bug. It's still a package in Hardy (and works fine for me), so it can be reported :-). -- [HARDY] xserver-xorg does not auto-configure correctly https://bugs.launchpad.net/bugs/207409 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 207409] Re: [HARDY] xserver-xorg does not auto-configure correctly
Emm why not just try: sudo apt-get install displayconfig-gtk sudo displayconfig-gtk -- [HARDY] xserver-xorg does not auto-configure correctly https://bugs.launchpad.net/bugs/207409 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 192599] Re: GDM support for domain choice
Also, to see the domain selection box, likewise open should probably be patched to add/remove ShowDomain=true to/from the config file -- GDM support for domain choice https://bugs.launchpad.net/bugs/192599 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 192599] Re: GDM support for domain choice
This patch is used by the current version of OpenSuse (gdm 2.20, at least), so please ignore version in file-name. -- GDM support for domain choice https://bugs.launchpad.net/bugs/192599 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 192599] Re: GDM support for domain choice
A patch which OpenSuse uses, extracted from RPMS. ** Attachment added: "gdm-2.8.0.7-domain-entry.patch" http://launchpadlibrarian.net/15414920/gdm-2.8.0.7-domain-entry.patch -- GDM support for domain choice https://bugs.launchpad.net/bugs/192599 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 65664] Re: Cannot subscribe to exchange shared folders / calender in edgy
hmmm, what I did now is just setting the machine domain (there is an option in the administration menu in Ubuntu to do this) to be the same as the full domain name of windows - and now I have removed the /etc/hosts entries and for me it's still working. lilbudda - I never tried using Evo with external access exchange, but I think it wouldn't work (as it tries to talk to the domain controller to get GAL) --> I need to check it in evolution sources to verify that, but if that's the case, then it is imho a different bug than this. weierj - try to use nslookup on windows to see what domain windows *thinks* exchange is in (e.g. nslookup exchangefrontend) and use it as your ubuntu domain (I rarely see windows domains that use domain.org domain - more often It's domain.local). or try running ipconfig /all and see what is the domain name that windows uses. Hope this helps -- Cannot subscribe to exchange shared folders / calender in edgy https://bugs.launchpad.net/bugs/65664 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 207409] Re: [HARDY] xserver-xorg does not auto-configure correctly
Am I wrong in thinking that dexconf should generate xorg.conf which would use vesa and 800x600 resolution, which should always work, and be a good starting point? -- [HARDY] xserver-xorg does not auto-configure correctly https://bugs.launchpad.net/bugs/207409 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 65664] Re: Cannot subscribe to exchange shared folders / calender in edgy
Ok, I found a solution - this may be silly, but works. I have added ip addresses and host names of: - exchange OWA server - primary DC - secondary DC (last two for compatibility with GAL). to /etc/hosts . I've done two entries for each of them ( one with the sole host name, the other one as a fully qualified windows domain name, eg. hostname.domainname.local ) and now it works flawlessly. I think this proves that this is not bug in Exchange handling, but rather dns server requests. I've started using hostname in stead of ipaddress for OWA server. After all this, it miraculously started to work :-). -- Cannot subscribe to exchange shared folders / calender in edgy https://bugs.launchpad.net/bugs/65664 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 65664] Re: Cannot subscribe to exchange shared folders / calender in edgy
Hi, I observe exactly the same symptoms - when I try subscribing to another person folder, I cannot access it because of "generic error". I have "full mailbox rights" to that other mailbox, so I don't have problems accessing it as http://exchange_server/exchange/other-mailbox using my own login credentials. I would be very happy to provide more info on this, only if you point me to what you may need :-) P. -- Cannot subscribe to exchange shared folders / calender in edgy https://bugs.launchpad.net/bugs/65664 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
