I have the same problem and I think the crash only happens if gnome is
started with multiple windows (--window parameter) and tabs, and if one
closes a tab (or the most-right tab?) in another than the first window.
--
ERROR:terminal-tabs-menu.c:133:free_tab_id: assertion failed: (id >= 0 && id <
Just for the record:
I confirm that upgrading to the latest intrepid packages (as of today) solved
the problem for me, too.
Thanks for the fast upstream upgrade.
--
ERROR:terminal-tabs-menu.c:133:free_tab_id: assertion failed: (id >= 0 && id <
tabs_id_array->len * 8)
https://bugs.launchpad.net/
Abel Cheung wrote:
>For those who need command line access, change your habit is the way to go.
This ignorance against command line users is annoying, at best!
Matt Zimmerman wrote in that link mailing list message:
>Today, at least, it doesn't seem to be used, and more featureful indexed
>searchi
When you say "suspend works perfectly now", does that include both, suspend to
ram (Fn+F4) and suspend to disk (Fn+F12)?
What is your BIOS revision please?
--
Suspend-to-ram broken on IBM/Lenovo Thinkpad T61p [FIXED]
https://bugs.launchpad.net/bugs/235284
You received this bug notification becau
Public bug reported:
If installing 6.06 (dapper) on a system with an already satisfying partition
situation (e.g. when replacing another linux), (i.e. one does "manual
partitioning" and only assigns mount points) the installer won't continue
beyond the partitioning step.
This problem seems to a
Public bug reported:
On a fresh Dapper, with universe+multiverse sources activated, an
aptitude update and aptitude upgrade leads to the highly unexpected
effect that lilo gets installed (but not configured!!!) and grub gets
uninstalled.
I don't know if this problem applies
- to aptitude, or
- t
Btw., I used the text installer from the alternative CDs, because the
graphic installer sucks anyway due to it's graphics and RAM
requirements.
--
dapper installer insists on partition table change
https://launchpad.net/bugs/50865
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://
As it took me half an hour's research to follow the TEXMFLOCAL hint
above, I decided to create a Mini-HowTo and took the liberty of making
the two .sty files available:
These steps make fancyheadings.sty (from Ubuntu feisty's tetex-extra
package) available in Ubuntu gutsy and took the liberty of m
Such a "redirect" style could have been integrated to tex-live ;-))
But I can see that a new tex distribution won't care for all addons of all
other tex distributions.
For me and the other people with document bases uses fancyheadings.sty,
the TEXMFLOCAL approach is far more convenient, even if w
Public bug reported:
Binary package hint: linux-image-generic
For some months now developer machines (desktop and laptop) are
available and bought with more than 2 GB of RAM, say 4 GB.
Unfortunately, the -generic kernel of Ubuntu x86 only uses up to 3 GB
(at least that's /proc/meminfo tells), wh
I failed to reproduce the problem in a 32-bit environment (early Athlon 1.33
GHz).
I suppose the problem is restricted to 64-bit installations.
--
vmware-server : guest can't access server and vis-versa
https://bugs.launchpad.net/bugs/112702
You received this bug notification because you are a m
Confirmed for Quadro 750 M: nvidia + acpi_sleep=s3_mode allows suspend to ram.
Thanks for the hint.
thinkpad_acpi is currently working on the backlight brightness, where the T61
introduced more levels.
But as hibernation is very ACPI specific, I tried anyway.
I'm gonna try combining s3_mode with
No I just said they are working in the area of brightness control in the
current T61 generation.
I am not sure this concerns the GPU driver at all, but brightness control seems
not to be working yet on some T61 models.
Details can be found in the mailing lists of linux-thinkpad.org.
--
Gutsy Gi
After those many upgrades today, I did more research testing - and have
partial success!
Calling the script attached (based on the one from ThinkWiki) as root
now safely suspends to ram and I even have reasonable 2D and 3D
performance after resuming.
Suspend to disk or any suspend using Fn+F4 or
For know everyone is working on getting gutsy ready (especially for this damn
hardware thrown on the market the last few months).
Hardy development will start at an open kickoff meeting at the end of October
(in the campus hotel of a certain US university I believe), we won't see even
an alpha f
Found some more hints and a new thinkpad-acpi 0.17, so here are more
test results:
1. with kernel parameter maxcpus=1 (hint in nvidia forum), nvidia 100.11.19
(.deb)
suspend 2 ram works fine.
hibernation does not work, but dies much later.
2. with new thinkpad-acpi 0.17-20071002 patched into ubu
fancyheadings.sty is present in feisty's tetex-extra package, but is
missing from gutsy's TeX Live package.
I googled some comment that said that fancyheadings.sty was removed from
debian's TeX packages because it has been marked obsolete for some time.
This is very ruthless youngster thinking an
The fact that fancyheadings.sty is missing in gutsy is obiously true and
I therefore confirm it.
** Changed in: texlive-base (Ubuntu)
Status: New => Confirmed
--
fancyheadings.sty disappeared
https://bugs.launchpad.net/bugs/132399
You received this bug notification because you are a membe
First, s/fancyheadings/fancyhdr/ does not help, the headings does not
look correct then.
Maybe it's not that much to change, but I still see no reason to kill
fancyheadings.sty.
We and at least on other firm I know use fancyheadings in script-
generated documents for automatic invoice prodution.
First let me apologize for my sour note above.
In the first place I just wanted to know if anyone besides me is missing this
fancyheadings style, too.
Then I just wanted to confirm the simple fact, but sometimes my fresh angry
thoughts fall in a feedback loop ;-((
Secondly, MANY THANKS for the t
Because of the release of gutsy beta, I re-did most of my tests today.
Still no change though:
gutsy beta with nvidia driver (gutsy package nvida-glx-new 100.14.19)
kills the machine during resume (although I sometimes was able to ping
or even ssh it).
gutsy beta with nv driver (the open source d
>Is this fixed in Gutsy beta?
Yes, more or less.
At least libwfb.so is in the current nvidia-glx-new 100.14.19 package.
Unfortunately there are many other unsolved problem with recent cards
from all manufacturers.
--
[nvidia-glx-new] Driver is missing libwfb breaking X on 8000 series cards
https
I solved my performance problem with tex stuff run as non-root, using
top and Google:
In this article ...
http://www.esm.psu.edu/mac-tex/MacOSX-TeX-Digests/2001/MacOSX-TeX_Digest_11-26-01.html
... from 2001 (!) I found:
--- SNIP ---
- Added '$HOME contains //' check to TeXGSInstaller installation
>1. Has anyone ssen this happen on the SERVER build of kernels, or is
this just happening on the GENERIC build?
I have seen this kind of crash with feisty's server kernel on my IBM x335
servers on a regular basis.
I would not be surprised if the initial cause(s) are in since 2.6.20 (which
seem t
>non-PAE supporting hardware will fail booting with the kernel
Ouch, I admit that hurts.
Especially for non-x64-hardware where you have no "workaround" in
switching to the amd64 distro.
I guest PAE cannot be "loaded" lateron or switched active with a kernel line
parameter?
So what's left is eit
>>How about a PAE-enable kernel as option after installation?
>>The bug sure isn't invalid.
>It exists already. It is the server kernel.
At the time we came up with this issue (feisty), several module packages
had not been available for the -server kernel, therefore some things
(especially GPUs a
"Better" way (still not recommended):
sudo dpkg --force-all --remove scrollkeeper --purge
--
Can't Remove Scrollkeeper without trashing Gnome
https://bugs.launchpad.net/bugs/164819
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
I strongly support this issue.
This damn thing just eats resources, energy, ... and the only "nice" way to
disable it is either hacking or removing it's binaries and/or cronjob.
--
Can't Remove Scrollkeeper without trashing Gnome
https://bugs.launchpad.net/bugs/164819
You received this bug notif
Btw., how do you define LTS?
--
dapper installer insists on partition table change
https://bugs.launchpad.net/bugs/50865
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
http
Finally, the new 2.6.22-11 kernel packages and other update from the
last 3 day breaks down restricted stuff completely.
There are no loadable nvidia kernel modules!!??
The restricted manages tells us we would'nt need restricted drivers!!!???
The damn self-repair-function of gdm (or is it X) simpl
Two days ago the state (on the Austrian mirror) was a pain, but with current
updates ...
I confirm it works now with gutsy-amd64 on a Thinkpad T61p with Nvidia Quadro
FX 570M.
However, I had to explicitly uninstall the manual installation of NVidia's
driver, I reinstalled nvidia-glx-new and res
Confirming solution by package updates, and how-to undo workarounds ...
With updates from today this problem does not exist any more.
If a machine has traces of workaround described above, one needs to:
+ --uninstall any manual NVIDIA*run installation
+ remove nv* from DISABLED_MODULES (in
/etc/
Wether or not this bug was "real" (or only the siblings were), I set it
to "Fix Released" so other people can find the knowledge collected here.
** Changed in: linux-restricted-modules-2.6.22 (Ubuntu)
Status: Invalid => Fix Released
--
wrong nvidia kernel module (7185 instead of 100.11.14
With 2.6.22-10-generic suspend to ram sometimes "worked" (after setting
POST_VIDEO=false in /etc/default/acpi-support).
Unfortunatley, X was incredibly and unusable after resume, which seems to be an
NVidia problem promised to be solved with the next driver after nvidia-glx-new
100.14.11.
With
Don't worry.
1. ThinkPads have always been a popular device for Linux users, including many
professional developers.
2. The Centrino Pro chipset used in the most recent models are absolutely
mainstream and also used by other manufacturers including HP and especially
Dell who has chosen to sell a
Bad thing is, the patch did'nt work for me :-((
Do you have any special kernel parameters?
What is the value of POST_VIDEO in your /etc/default/acpi-support?
Which X driver are you using?
--
Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p
https://bugs.launchpad.net/bugs/139
thinkpad_acpi 0.16 from
http://sourceforge.net/project/showfiles.php?group_id=117042&package_id=230205
can easily applied to Ubuntu's 2.6.22 kernel source.
I am not sure what it does solve (e.g. for my T61p), I am still fighting
for suspend/resume ;-))
Also, I still have two /proc/acpi/video/VID
Thanks for the fast reply.
So this seems to leave the nvidia driver as bad guy.
Let's all hope they finish their next release really soon.
--
Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p
https://bugs.launchpad.net/bugs/139089
You received this bug notification because you
With kernel 2.6.22-10 I could suspend from tty1-6 using the script from
http://thinkwiki.org/wiki/Installing_Ubuntu_7.04_%28Feisty_Fawn%29_on_a_ThinkPad_T61#Suspend
However I am not sure if this is the same suspend operation that occurs
when pressing Fn-F4 while in X.
With my former ThinkPads, A3
With vesa driver, suspend to ram works for me.
However, I can't get the full 1920x1200 for now, fighting on it right now.
Of course the only real solutions is a better nvidia driver, but suspend/resume
is more important for me than the performance advantage of the nvidia driver.
With AMD/ATI openi
I just got vesa working with full res. 1920x1200. (I'll BLog how some
day soon)
Only remaing problem so far:
GoogleEarth does not even run slow but crashes X ;-((
I think because xorg's software GLX, unlike the nvidia driver, does not provide
32bit compatibility on 64bit installations.
Well, I ca
I do not think my (mini) BLog is that interesting, but there are some
Ubuntu hints ;-))
I'd have published the VESA hints earlier this day, but due to a
Tapestry 4.1 incompatibility in my website I had not been able to log in
at all ;->>>
Here's the deep Link to the VESA Mini-HowTo:
https://secur
There is of course a non-secure BLog access also:
http://www.ibcl.at/ibclweb/ibclweb?component=%24DirectLink&page=ShowBLogOverview&service=direct&session=T&sp=l148
--
Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p
https://bugs.launchpad.net/bugs/139089
You received this bug
As of decision making in Ubuntu development, I think there is plenty of room
for improvement.
This is one of the topics where SuSE is better and probably one reason for why
SuSE's market share has grown again, despite Ubuntu's popularity.
If gutsy really is published with thinkpad_acpi <0.15, I
Sitsofe Wheeler, it seems you work too hard ;-))
As I read it, the new thinkpad_acpi 0.16 solved suspend/resume for Robbob.
He uses VESA driver anyway because he did'nt know how to build an according
linux-restricted-modules package (I wonder if this would be needed to rebuild
at all?).
I can c
Somehow the recent acpi* updates killed my resume capabilities ;-((
At the moment I don't have the time to track down details ...
--
Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p
https://bugs.launchpad.net/bugs/139089
You received this bug notification because you are a me
I just resumed successfully again.
It seems the kernel parameter acpi_sleep=s3_bios is crucial after all.
I should not touch /boot/grub/menu.lst that often and use shift-D in vi that
ofen ;-))
Sorry if I really bothered you because of my incautiousness, I am gonna add
more experience reports as g
Just FYI some anti-nvidia-confirmations:
As suspected, no resume with manually installed brand new nvidia driver
100.14.19 (with neither 2.6.22-11-generic kernel nor "our" thinkpad_acpi
upgraded 2.6.22.6)
Nvidia*run --uninstall, apt-get install --reinstall libgl1-mesa-glx, back to
VESA, resume o
First a small success report:
During the past 30 hours, I suspended to RAM 4+ times, and either the power
manager or the BIOS induced one suspend to disk due to poor battery state (best
CPU, 4 Gig RAM, best GPU, all so power consuming ...).
I had no problem resuming, even with such evil circumsta
** Attachment added: "xorg.conf for T61p NVidia Q570M in VESA mode"
http://launchpadlibrarian.net/9370024/xorg.conf
--
Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p
https://bugs.launchpad.net/bugs/139089
You received this bug notification because you are a member of Ub
This package solved the problem for me (1 week old Lenovo T61p).
Many many thanks!
--
no sound with 82801H (ICH8 Family) HD Audio Controller
https://bugs.launchpad.net/bugs/122560
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I don't think the Tribe 5 CD can contain Tim's new packages which seems to work
for most of us. (Yet one has to unmute the channels manually)
Have you installed the updates form the net archives?
--
no sound with 82801H (ICH8 Family) HD Audio Controller
https://bugs.launchpad.net/bugs/122560
You
I had the same glx-crahses described above even without compiz.
My solution (for i386 and for amd64 architecture) was to supress AIGLX (from
Xorg 7.1 I think) and allow the Nvidia driver to use it's own NV-GLX:
$ grep -i glx /var/log/Xorg.0.log
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/mo
It seems I do not have this problem on my T61p.
However, when I turned it on for the very first time last week, I changed the
BIOS settings (for PCI->IRQ assignment) from "IRQ 11" (for every single one of
the ~8 listed devices or channels) to "Auto", just on an old Geek's instinct.
If the BIOS is
The only USB device I use regular is an external mouse.
It might even be that my kernel also disables the IRQ but lacks negative
effects.
I am gonna take a look to my logs when I am back in office some time tomorrow.
--
kernel disables irq after 10 minutes
https://bugs.launchpad.net/bugs/126369
Public bug reported:
Binary package hint: linux-restricted-modules-2.6.22-10-generic
I have a Lenovo Thinkpad T61p with a nVidia Quadro FX 570M card (PCI-Id:
10de:040c) that needs up-to-date driver 100.11.14 to work at all.
(It still has the problem of slowing down after suspend/resume, but X wo
After hours of googling, I found the according OpenSuSE 10.3 bug:
https://bugzilla.novell.com/show_bug.cgi?id=290385
--
wrong nvidia kernel module (7185 instead of 100.11.14) loads at boot time
https://bugs.launchpad.net/bugs/136838
You received this bug notification because you are a member of U
While searching for a solution to the X-slow-after-resume problem, I
found, say another workaround:
In NVidia's Forum, on
http://www.nvnews.net/vbulletin/showthread.php?t=72490
gives some hints.
As it is impossible to remove linux-restricted-modules-* without lateral damage,
the crucial step seem
Voila:
# ls -al /lib/linux-restricted-modules
total 24
drwxr-xr-x 4 root root 4096 2007-09-02 22:27 .
drwxr-xr-x 18 root root 12288 2007-09-01 19:52 ..
drwxr-xr-x 17 root root 4096 2007-08-23 20:39 2.6.22-10-generic
drwxr-xr-x 17 root root 4096 2007-08-23 20:29 2.6.22-9-generic
I don't think
Sorry for the SuSE link, that one concerns the X-slow-after-resume
problem, not this module related one.
--
wrong nvidia kernel module (7185 instead of 100.11.14) loads at boot time
https://bugs.launchpad.net/bugs/136838
You received this bug notification because you are a member of Ubuntu
Bugs,
Purging all 2.6.22-9-generic stuff did not prevent the loading of the
7185 driver.
--
wrong nvidia kernel module (7185 instead of 100.11.14) loads at boot time
https://bugs.launchpad.net/bugs/136838
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug conta
One addition:
I am currently with gutsy i386 usually, but the 100 Gig drive allows me to have
installations of gutsy amd64, feisty i386 and feisty amd64 on the same machine.
Due to the far-too-new hardware I don't start feisty often, I usually switch
betwenn gutsy i386 (provides Opera, Skype, rea
Initially I used the binary package nvidia-glx-new with NVIDIA*.run run over it
(due to a .so file missing in the binary .deb).
Now I am using _only_ a manual installed NVidia driver.
All of these variants share the same problem, only adding nvidia to
DISABLED_MODULES in /etc/default/linux-restri
I did'nt go with both ways at the same time.
But I could not go the .deb only way, because the nvidia-glx-new 100.11.14
package is still incomplete (#98641) and I can see this one kind of depends on
#98641 and perhaps other nvidia-glx-* bugs.
And there is of course the possibility that the final
s bug to invalid and assign it to me.
Whenever untill nvidia-glx-new is fixed, I will retest the situation with a
pure Ubuntu configuration and then decide either to close or to re-open this
bug.
** Changed in: linux-restricted-modules-2.6.22 (Ubuntu)
Assignee: (unassigned) => Ch
Most restricted drivers are available es extra package, in versions
sepcifically compiled against specific kernels.
(nvida-glx-legacy, nvidia-glx, nvidia-glx-new)
Putting restricted nvidia modules in the kernel will not happen and for good
reasons:
+ the kernel should be kept small, It's awful b
Ah, that you meant.
The server kernel will never get X11 support ;->>
I used the server kernel (and nvidia's own installer) for some time
myself, but that's really not the way it should be.
I agree with your solution list and that #1 is the favourite.
However I'd generally love to see more com
Has anybody tried the new 169.07 driver?
--
Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p
https://bugs.launchpad.net/bugs/139089
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
u
On the other hand, suspend to ram worked with nvidia 100.11.14 and
kernel 2.6.22-10-generic, so it could be a two edged sword after all!?
X have been unusable slow after resume with that combination, but
according to the NVidia forum
http://www.nvnews.net/vbulletin/showthread.php?t=94258 this seem
With today's update (or yesterday's, many traffic these days) I seem not to
need the thinkpad_acpi update any more, as long as I use the VESA driver.
I just did one suspend 2 ram, one hibernate, resume was ok both times.
I use amd64 only, so if Robbob tests with i386 this issue could
eventually
*** This bug is a duplicate of bug 112937 ***
https://bugs.launchpad.net/bugs/112937
I can confirm the problem, however I cannot confirm the solutions.
I still get this:
Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM (vmware-authd) illegal module
type: @include
Dec 24 15:38:44 vz02 vmware-aut
I just had the same expirience with gutsy.
I absolutely support that the chunksize should be configurable in
base-installer's partitioning section, and that the mke2fs call should be
checked for optimization.
--
Initial install, RAID; use --assume-clean with mdadm, and prompt for chunk size
htt
Public bug reported:
The software RAID section of the text based installer from gutsy's
alternate amd64 CD fails to delete existing software RAID devices,
because it uses the wrong device path, i.e. /dev/md/0 instead of
/dev/md0, /dev/md/1 instead of /dev/md1.
Creating according softlinks via con
Eventually good news.
After investing in a docking station and a 24" TFT, I had to try the
nvidia driver again (the VESA driver does not support or not understand
the up to 3 available monitors when using all external video
connectors), and I have suspend to RAM perfectly working now on my T61p
wi
*** This bug is a duplicate of bug 116842 ***
https://bugs.launchpad.net/bugs/116842
For the record:
After all one 3rd party software company learns 64 bit compilation:
In the developer snapshot area ...
http://my.opera.com/desktopteam/blog/
... Opera provides a 64 binary package for several
...OK, we've set up another test system, where the bug occurred exactly
as reported.
The output of your shell script is:
[EMAIL PROTECTED]:~# sh /home/lech/Desktop/test.sh eth0
Examining interface: eth0
udi for eth0 is /org/freedesktop/Hal/devices/net_00_16_cb_a6_f3_16
sysfs_path for eth0 is
/s
>It's a known fact that 32-bit Linux only supports around 3.2 GB of RAM.
???
With PAE and HIGHMEM_4G/HIGHMEM_64G enabled and compiled for i686 or higher, a
32-bit Linux can see 4 GB resp. 64 GB without problems.
(One could of course argue that these kernels are not "pure" 32-bit)
In some PAE art
Unfortunately there are cards that seem to work only with the nvidia-
glx-new driver.
I have a brand new 7600 GS, lspci says:
VGA compatible controller: nVidia Corporation G70 [GeForce 7600 GS] (rev a1)
>From manual playing with feisty beta (apt-get dist-upgraded from edgy) I
knew that only the -
Sorry for my delayed response, somehow I must have overlooked the mail about
your question.
As far as my virtual machine test shows, this problem also seems to have been
solved in the meantime.
--
aptitude update + aptitude upgrade on fresh dapper replaces grub with
unconfigured lilo
https://l
Sorry for my delayed response, somehow I must have overlooked the mail about
your question.
As all my edgy installations are dapper installations updated live, so I just
made a quick test with a VMWare virtual machine (installed edgy, shutdown,
pretended install again), and it seems the problem
I seem to suffer from the same problem in up-to-date lucid x86_64 with Ubuntu
kernel 2.6.32-21-generic.
I assume the problem only occurs when the target server is considerable slower
than the local machine, like an ultra slow NAS serving for a SSD boosted
developer machine.
--
Writing big file
The bug still is here, I suffer from it on my "failback terminal", a MacMini.
I'll test some mainline kernels and then report back.
--
sky2 rx length error: status 0x2630100 length
https://bugs.launchpad.net/bugs/354717
You received this bug notification because you are a member of Ubuntu
Bugs,
The problem still is there in 2.6.32-0206321203 (2.6.32.12.3-lucid) and
2.6.33-02063303 (2.6.33.3-lucid).
But I noticed why it probably does not concern too many people:
The errors only occur if at least one VLAN interface is stacked upon the ethX
interface handled by the sky2 module, like eth0.1
Architecture: i386
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1)
Package: linux (not installed)
ProcEnviron:
LANGUAGE=de_AT:de
PATH=(custom, user)
LANG=de_AT.utf8
SHELL=/bin/bash
Tags: lucid
Uname: Linux 2.6.33-02063303-generic i686
Unr
In other quite old sky/sky2 problem reports I found reports that it'd
help to reduce the MTU to 1492 (default is 1500), so I tried MTUs of
1492 and 1400, that did'nt help though.
--
sky2 rx length error: status 0x2630100 length
https://bugs.launchpad.net/bugs/354717
You received this bug notific
The problems occurs without VLAN too, if VirtualBox is running and using the
ethX.
It seems any "logical" interface stacked upon sky2's ethX provokes the problem.
--
sky2 rx length error: status 0x2630100 length
https://bugs.launchpad.net/bugs/354717
You received this bug notification because y
Today I tried copying very large files to a NFS share mounted with
rsize=64,wsize=64 and I could reproduce freezes of about 30 secs, but no
120-sec-freezes and nothing in dmesg' output.
I am on lucid's amd64 kernel 2.6.32-22.
--
Writing big files to NFS target causes system lock up
https://bugs
I only had the problem with an extremely slow NAS as target, I have given the
damn thing away a wee ago.
So I have no easy way of reproducing it now, sorry.
--
Writing big files to NFS target causes system lock up
https://bugs.launchpad.net/bugs/561210
You received this bug notification because
My Desktop also did freeze for those 120 seconds.
I use a Gnome but there are KDE based widgets running, namely klipper.
Ac. buffer size: Larger write buffers (backed by enough RAM) defer or
eventually avoid the point at which the buffer runs full.
I think we agree that's when the freeze occurs.
If my assumption of the freeze trigger is correct, it should be possible to
provoke the problem even against fast NFS servers by setting the buffer size
extremly low, i.e. to the minimum allowed by the NFS driver.
I 'll try this out, but due to a business trip I won't happen before the end of
th
I am not so sure if OpenVZ as a project is going to "survive" the fact
that Ubuntu 10.04 LTS and RHEL6 both are switching to LXC, I am afraid
it might starve to death.
However it should become (a lot) easier to get a current distro (like
lucid) running (and up to date) as guest under any kernel
vi
Is there a specific patch that addresses our problem?
--
Writing big files to NFS target causes system lock up
https://bugs.launchpad.net/bugs/561210
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
>by the way I also tried 64 bit ubuntu, but it also saw only ~3GB
I see no way a 64-bit distro falls short of using every RAM there is.
(Well maybe there are kernel params to restrict the RAM but I assume you have
not done that)
IMO you either have only 3 GB, or your mainboard and/or BIOS lack
s
Excuse me!?
How does a workaround for the next non-LTS release solve this for the current
LTS release!?
Besides, telling a few services not to start has nothing to do with a
stable setup in the long term, because any update in the area of udev or
upstarted will undo part of that and thereby make
This is another proof of Ubuntu's way of operation:
Don't work on an issue, wait, close.
There's nothing incomplete here except Ubuntu's manpower for following
kernel problems.
--
sky2 rx length error: status 0x2630100 length
https://bugs.launchpad.net/bugs/354717
You received this bug notifica
ly would do an apache restart for
"graceful" by mistake.
So PLEASE, if you insinst on rerouting apache2ctl graceful to systemd make it
reload and not restart Apache.
Thanks, regards, Christoph Lechleitner
--
You received this bug notification because you are a member of Ubuntu
First, sorry if I'm in the slightly wrong issue here. The most recent
comment before mine fits our situation perfectly and wasn't old, so I
think it's an acceptable place for this discussion.
> So we have a regression when `apache2ctl graceful` is called directly,
which I think it's still a common
97 matches
Mail list logo
