[Bug 361478] Re: acroread 9 in hardy overrides application settings in firefox
I'm also seeing this, but on intrepid. And, argh! I looked in Edit->Preferences->Applications, and when the behaviour for PDF states "always ask" and the damn thing didn't obey that I gave up my first efforts... Btw, the main reason I want to disable it is that my firefox always crashes when left unattended after having displayed a pdf using the plugin... It seems about as unstable as some 10 years ago, that's what I call development ;) -- acroread 9 in hardy overrides application settings in firefox https://bugs.launchpad.net/bugs/361478 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 135075] Re: Dapper cciss driver doesn't handle over 2TB devices.
That's funny, since the bug is that the cciss-driver on _dapper_ doesn't support large devices. The main issue here is what kind of support we really can expect for the LTS releases, you should keep in mind that the LTS-releases are the ones mainly deployed in larger environments where you don't want diverging installations all over the place. Support for newer hardware is essential to be able to use an LTS release for a longer period where new hardware acquisitions are likely to be made. -- Dapper cciss driver doesn't handle over 2TB devices. https://bugs.launchpad.net/bugs/135075 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 57972] mdrun fails if large disk present, thus boot fails.
Public bug reported: Ubuntu Dapper on AMD64. mdrun fails if a large disk is present in the system, causing boot to fail if you have your root partition on MD. Our setup: Dual 3ware 9550-SX cards, each with two units which maps to: sda - single disk (250GB) sdb - raid5 (1.2TB) sdc - single disk (250GB) sdd - raid5 (1.2TB) The single disks (sda and sdc) are used in an MD mirror for the system. ---8<--- # grep sd /proc/partitions 8 0 244129792 sda 8 1 393561 sda1 8 2 787185 sda2 8 33935925 sda3 8 4 239007037 sda4 816 1220648960 sdb 817 1220642766 sdb1 832 244129792 sdc 833 393561 sdc1 834 787185 sdc2 8353935925 sdc3 836 239007037 sdc4 848 1220648960 sdd 849 1220642766 sdd1 ---8<--- Perhaps not obvious with a proportional font, but there's only one space between the 2nd and 3rd column on the large devices. mdadm assumes two spaces. Doing sh -x /sbin/mdrun in the initramfs shows that it generates the following code snippet: ---8<--- if [ ! -b sda4 ]; then mknod sda4 b 8 4; fi ; 816 1220648960 sdb if [ ! -b sdc ]; then mknod sdc b 8 32; fi ; ---8<--- This causes a syntax error, the entire block fails, meaning no device nodes whatsoever gets created and the system is dead in the water. Note that it's sufficient to have a large device present in the system, so if you have your root device on MD and add a large device to the system you won't be able to boot. Doing a normal boot, all you see is the following (mostly included as a reference for others bitten by this issue): ---8<--- Begin: Running /scripts/local-top ... eval: 1: 8: not found mknod: sdc: File exists eval: 1: Syntax error: ";" unexpected mdadm: error opening /dev/md?: No such file or directory mdadm: error opening /dev/md?: No such file or directory mdadm: error opening /dev/md?: No such file or directory mdadm: error opening /dev/md?: No such file or directory mdadm: error opening /dev/md?: No such file or directory mdadm: error opening /dev/md?: No such file or directory mdadm: error opening /dev/md?: No such file or directory mdadm: error opening /dev/md?: No such file or directory Done. Begin: Waiting for root file system... ... Done. ALERT! /dev/md1 does not exist. Dropping to a shell! ---8<--- It would be nice if this was fixed in Dapper. I'll attach a patch that fixes the problem in mdrun. ** Affects: mdadm (Ubuntu) Importance: Untriaged Status: Unconfirmed -- mdrun fails if large disk present, thus boot fails. https://launchpad.net/bugs/57972 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 57972] Re: mdrun fails if large disk present, thus boot fails.
Patch that fixes /proc/partinfo parsing in mdrun so system with large devices present can boot when having root on MD. -- mdrun fails if large disk present, thus boot fails. https://launchpad.net/bugs/57972 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 57972] Re: mdrun fails if large disk present, thus boot fails.
Ehm. That would be /proc/partitions and nothing else. -- mdrun fails if large disk present, thus boot fails. https://launchpad.net/bugs/57972 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 67532] Re: udev-rule for PTP class detection broken
Indeed, editing /etc/udev/rules.d/45-libgphoto2.rules and replacing BUS with SUBSYSTEM makes it work. Incidentally, this coincides with the output style from /usr/lib/libgphoto2/print-camera-list udev-rules-0.98 which is supposed to output a file usable by udev 0.98+... Could it be so simple as libgphoto2-2.postinst being buggy? If I look at /etc/udev/rules.d/45-libgphoto2.rules it says it's for (udev < 0.98) but the installed udev is obviously newer than that... If that's the case, fix should be trivial. And developers should be embarassed ;) This is on Ubuntu Feisty x86, libgphoto2-2 2.3.0-0ubuntu4, using a Panasonic DMC-FZ5 camera (recognized as FZ20 I think). -- udev-rule for PTP class detection broken https://bugs.launchpad.net/bugs/67532 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 67532] Re: udev-rule for PTP class detection broken
This is a machine upgraded from edgy, and doing dpkg-reconfigure libgphoto2-2 indeed gives me a correct 45-libgphoto2.rules that has the comment about being for a new udev version. I suspect that when doing an upgrade it's still running the old udev- version, and thus generates the file for the old version. When the machine finally gets around to running the new udev version (it might even take a reboot, I don't really know) it obviously will not work. The kludge for the moment is of course doing dpkg-reconfigure on libgphoto2-2, I was too tired and frustrated to even think of that. In the long run this should really be fixed in some sane way, you really shouldn't be expected to do dpkg-reconfigure on various packages in order for stuff to work after an upgrade. -- udev-rule for PTP class detection broken https://bugs.launchpad.net/bugs/67532 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 135075] Re: Dapper cciss driver doesn't handle over 2TB devices.
Debian packaging of the cciss 2.6.18-5 driver. This is the driver above, I have only added some packaging to produce a source package that can be used by module-assistant. The module- assistant target also produces a meta package which depends on the latest (ie. newly built) module package. The module package diverts cciss.ko and replaces it with the updated version, and updates module dependencies and initramfs. It seems to work for us, hopefully someone else finds it useful. ** Attachment added: "cciss-2.6.18-5_dapper-debianized.tar.gz" http://launchpadlibrarian.net/9233690/cciss-2.6.18-5_dapper-debianized.tar.gz -- Dapper cciss driver doesn't handle over 2TB devices. https://bugs.launchpad.net/bugs/135075 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 135075] Dapper cciss driver doesn't handle over 2TB devices.
Public bug reported: Binary package hint: linux-image-2.6.15-28-amd64-server The Dapper cciss driver doesn't handle devices larger than 2TB in size. This is becoming a real problem in environments like ours where we prefer having all our servers on the Ubuntu LTS track. For example, the HP DL320s with 12 large SATA drives is a rather cheap box that's hits this limit really hard. Given that people on the LTS track prefers stable environments I understand if you don't want to upgrade the cciss driver in Dapper, but for those who needs it a newer version that provides this functionality should be available. I have hacked the cciss 2.6.18-5 driver (available from http://cciss.sourceforge.net/) so it compiles cleanly and seems to work with Dapper, no warranties but it at least seems to work. I'll try to attach the tarball to the bug if it's possible. One solution might be to package this and having it divert the cciss.ko available in the kernel package. I'm sure there are lots of other options too. In any case, people really want to be able to install a package that solves the problem and not having to track stray modules. In any case, Ubuntu LTS needs to have some way to handle this class of problems in order to be considered a viable long-term server distribution. ** Affects: linux-source-2.6.15 (Ubuntu) Importance: Undecided Status: New -- Dapper cciss driver doesn't handle over 2TB devices. https://bugs.launchpad.net/bugs/135075 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 135075] Re: Dapper cciss driver doesn't handle over 2TB devices.
cciss 2.6.18-5 driver (available from http://cciss.sourceforge.net/) hacked so it compiles cleanly on Ubuntu Dapper AMD64. Only tested on Dapper AMD64 in a HP DL320s with SmartArray P400 controller and a raid6 set consisting of 11x750GB SATA drives. To build: apt-get install module-assistant m-a prepare mkdir /tmp/dir cd /tmp/dir tar -xzf /path/to/cciss-2.6.18-5_dapper.tar.gz make NOTE! IF SOMETHING GOES WRONG YOUR SYSTEM MIGHT NOT BOOT. YOU HAVE BEEN WARNED. To install: cp /lib/modules/`uname -r`/kernel/drivers/block/cciss.ko /lib/modules/`uname -r`/kernel/drivers/block/cciss.ko.bak cp cciss.ko /lib/modules/`uname -r`/kernel/drivers/block/cciss.ko depmod -a update-initramfs -u ** Attachment added: "Dapper cciss 2.6.18-5 driver" http://launchpadlibrarian.net/9012448/cciss-2.6.18-5_dapper.tar.gz -- Dapper cciss driver doesn't handle over 2TB devices. https://bugs.launchpad.net/bugs/135075 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 164386] Re: open_basedir restriction causes bogus warnings
Testing on hardy it works, naturally, because it's 5.2.4-2ubuntu4 and since the bug is fixed upstreams in 5.2.4 ... -- open_basedir restriction causes bogus warnings https://bugs.launchpad.net/bugs/164386 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 185654] [NEW] hardy: fglrx needs amdpcsdb.default - doesn't start
Public bug reported: Binary package hint: xorg-driver-fglrx Package: xorg-driver-fglrx Source: linux-restricted-modules-2.6.24 (2.6.24.6-4.13) Version: 1:7.1.0-8-01+2.6.24.6-4.13 Ubuntu hardy amd64 on HP8510p (mobility HD2600). X using fglrx worked until doing an aptitude update and rebooting today. /var/log/Xorg.0.log.old contains: (EE) fglrx(0): Unable to initialize PCS database (EE) fglrx(0): Missing PCS defaults file /etc/ati/amdpcsdb.default Googling suggests that amdpcsdb.default is mandatory, but it doesn't seem to be included in any package. As an additional headache xorg is started in "failsafe" mode using the vesa driver, this doesn't work which results in a hung console. ** Affects: linux-restricted-modules-2.6.24 (Ubuntu) Importance: Undecided Status: New -- hardy: fglrx needs amdpcsdb.default - doesn't start https://bugs.launchpad.net/bugs/185654 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 164386] open_basedir restriction causes bogus warnings
Public bug reported:
Binary package hint: php5-cgi
Enabling an open_basedir restriction causes bogus warnings to be
emitted.
Testcase (using php-cli):
# /usr/bin/php5 -d open_basedir=/tmp/ -r 'var_dump(file_exists("/tmp/nosuch"));'
Warning: file_exists(): open_basedir restriction in effect. File(/tmp/nosuch)
is not within the allowed path(s): (/tmp/) in Command line code on line 1
bool(false)
The warning vanishes if you remove the trailing slash of the
open_basedir restriction, but this allows matches like /tmpathon since
it's a simple substring match.
See upstreams http://bugs.php.net/bug.php?id=41518 for more information
and examples.
It's fixed in PHP 5.2.4 according to
http://www.php.net/ChangeLog-5.php#5.2.4 but I haven't been able to find
the patch that fixes it.
** Affects: php5 (Ubuntu)
Importance: Undecided
Status: New
--
open_basedir restriction causes bogus warnings
https://bugs.launchpad.net/bugs/164386
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 106700] Re: /etc/cron.d/drupal-5.1 contains nonexistant path
To add insult to injury, /etc/cron.d/drupal-5.1 isn't even a filename that's valid since it contains a dot. Verify by running: run-parts --list /etc/cron.d and notice how drupal-5.1 isn't listed. Renaming it to drupal-51 makes it show up. -- /etc/cron.d/drupal-5.1 contains nonexistant path https://bugs.launchpad.net/bugs/106700 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 121867] Bug in gameplay/campaign
Public bug reported: Binary package hint: wesnoth Wesnoth 1.2.3 has gameplay bugs; the character supposed to go to a specific place to finish the chapter (South Guard: Vengeance) does not show up at all. Neither does the other veterans from the previous chapter. See http://wesnoth.org/forum/viewtopic.php?t=15616 for more details. The bug is supposedly fixed in 1.2.4, I suggest that wesnoth-1.2.4 is backported to Ubuntu Feisty. ** Affects: wesnoth (Ubuntu) Importance: Undecided Status: New -- Bug in gameplay/campaign https://bugs.launchpad.net/bugs/121867 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 67532] Re: udev-rule for PTP class detection broken
The issue might be that the machine in question had edgy-backports (to get working gphoto2 stuff), and edgy-backports and feisty has the same libgphoto2-2 version. -- udev-rule for PTP class detection broken https://bugs.launchpad.net/bugs/67532 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 106540] Recommends postgresql-server-8.2 doesn't exist
Public bug reported: drupal-5.1 on feisty recommends postgresql-server-8.2 which doesn't exist. Since I have postgresql-8.2 installed I'm not interested in the mysql-server that aptitude tries to install to satisfy the recommends. ** Affects: drupal (Ubuntu) Importance: Undecided Status: Unconfirmed -- Recommends postgresql-server-8.2 doesn't exist https://bugs.launchpad.net/bugs/106540 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 106689] post-installation fails when already configured
Public bug reported: Binary package hint: drupal When installing drupal-5.1 on feisty I get this: -8<- dpkg: error processing drupal-5.1 (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: drupal-5.1 -8<- Poking a -x in drupal-5.1.postinst I see that it's the following that fails: -8<- curl http://localhost/drupal/install.php?profile=default 2> /dev/null | grep "Drupal installation complete" > /dev/null || exit 1 -8<- This can fail because: - That page says "Drupal already installed" when already configured and installed - If you don't want help from the dbconfig-thingie, you won't have a complete install until you have configured the DB. - There's no guarantee thats the location of the VHost using drupal. I suggest that this test is refined, and that the only effect of failing it is popping up a warning saying that manual configuration is needed. Failing hard without an explanation like now is definately wrong in any case. ** Affects: drupal (Ubuntu) Importance: Undecided Status: Unconfirmed -- post-installation fails when already configured https://bugs.launchpad.net/bugs/106689 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 106693] Default configuration inconsistent and inflexible
Public bug reported: Binary package hint: drupal I find the following default configuration items of drupal-5.1 in Feisty needing improvement: - In /etc/drupal/5.1/htaccess the directive "RewriteBase /drupal" is commented, this makes "Clean URLs" not work in the default configuration since the default location is http://whatever/drupal ... - /etc/drupal/5.1/apache.conf is symlinked into /etc/apache2/conf.d/ . Since conf.d applies to the base server configuration this has the effect of having drupal Alias:ed into all your VHosts, which you might not want. I suggest that the Alias-part is placed in an appropriate VHost configuration in /etc/apache2/sites-available/ instead. - Since the htaccess isn't dynamically updated by drupal there's no reason for it not to be included in the server configuration directly. There are obvious gains in performance by not having to check and parse the htaccess for every access. I suggest that the htaccess stuff is moved into the apache2 config since that's the only webserver the package supports anyway. Also having a single htaccess will cause problems if you want to have different drupal sites in different locations since the RewriteBase directive is common to all VHosts. - And then there's the usual "can't configure database access without password" issue. Postgresql has supported reliable identification by using a Unix Domain Socket for quite some time now, this is the default access method when the database server is on the local host. The dbconfig-thingie seems to generate a database with a password and it looked like it was using localhost instead of the default access method, which might be explained by drupal being stupid and not allowing you to specify an empty host/password. I poked the drupal developers regarding it on http://drupal.org/node/125105 (probably the wrong place, but I was rather annoyed at that point). I'm not expecting this last item to be solved, but I want to raise the issue in the hopes of having all stupid web applications that gets this wrong fixed eventually. ** Affects: drupal (Ubuntu) Importance: Undecided Status: Unconfirmed -- Default configuration inconsistent and inflexible https://bugs.launchpad.net/bugs/106693 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 106700] /etc/cron.d/drupal-5.1 contains nonexistant path
Public bug reported: Binary package hint: drupal In drupal-5.1 on Feisty /etc/cron.d/drupal-5.1 contains references to /usr/share/drupal which doesn't exist. This should probably be /usr/share/drupal-5.1 instead. ** Affects: drupal (Ubuntu) Importance: Undecided Status: Unconfirmed -- /etc/cron.d/drupal-5.1 contains nonexistant path https://bugs.launchpad.net/bugs/106700 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 57972] Re: mdrun fails if large disk present, thus boot fails.
On Sun, 28 Mar 2010, ceg wrote:
> Is this still an issue with recent releases? mdrun isn't around
anymore
Haven't verified, but I suspect it is.
/Nikke
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Niklas Edmundsson, Admin @ {acc,hpc2n}.umu.se |ni...@hpc2n.umu.se
---
Experience is the name everyone gives to his mistakes
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
--
mdrun fails if large disk present, thus boot fails.
https://bugs.launchpad.net/bugs/57972
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 1923733] [NEW] unbound.service needs network online
Public bug reported: unbound.service in Ubuntu 20.04LTS Focal has insufficient dependencies for the ExecStartPre package-helper root_trust_anchor_update command to reliably succeed, while it depends on network.target that is no guarantee that network is available. While unbound startup succeeds, the following error can typically be seen on boot on physical hosts with NICs that have long setup/startup times (approx 10 seconds on this host): package-helper[899]: fail: the anchor is NOT ok and could not be fixed Our workaround is to add an appropriate dependency on network-online.target in /etc/systemd/system/unbound.service.d/network-online.conf like so: --8< [Unit] # Needs network online to be able to verify/update dnssec root key on startup After=network-online.target --8< With this workaround in place, after reboot we see success: package-helper[1025]: success: the anchor is ok ** Affects: unbound (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923733 Title: unbound.service needs network online To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1923733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894045] Re: modpython support missing from Ganglia
This indeed has to be a packaging bug. The last changelog entry says "Build using python2" but there is no dependency of anything python in the ganglia-monitor package: Depends: libapr1 (>= 1.2.7), libc6 (>= 2.14), libconfuse2 (>= 3.2.1~), libganglia1 (= 3.6.0-7ubuntu4), libpcre3, zlib1g (>= 1:1.1.4), adduser So, this package needs to be rebuilt correctly on focal to really build with python2 so modpython.so gets built. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894045 Title: modpython support missing from Ganglia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ganglia/+bug/1894045/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918141] [NEW] nfs-server.service needs name resolution and network online
Public bug reported: nfs-server.service has insufficient dependencies to start correctly in a setting where the nfs exports list contains DNS host names (not in local hosts file) or netgroups served via network (for example sssd). Typical failures listed by systemctl status nfs-server.service are: Mar 08 14:16:52 server.example.com exportfs[844]: exportfs: Failed to resolve client1.example.com Mar 08 14:16:52 server.example.com exportfs[844]: exportfs: Failed to resolve client2.example.com Our workaround is to add the appropriate dependecies in /etc/systemd/system/nfs-server.service.d/dependencies.conf like so: --8< [Unit] # nfs-server.service runs exportfs on startup, thus we need to be able to # do host and netgroup lookups which requires network to be online. After=network-online.target nss-lookup.target nss-user-lookup.target --8< While nfs-server.service do depend on network.target, that only means that the network has been configured. On physical hardware it can take significantly longer for the network to come online (8+ seconds for our 10G NICs). Also note that we configure static IP:s via systemd-networkd, things might behave differently when using DHCP, network-manager etc. In any case, depending on network.target is almost always wrong, and network-online.target is usually the right one. nss-lookup.target is needed to ensure that DNS resolution works, and nss-user-lookup.target is the best approximation to ensure that netgroup resolution via sssd or equivalent works. Usually things "just works" even without these dependencies, but to ensure correct startup they should be present. It should be noted that this seems to once have been fixed in Ubuntu, but has been lost along the way for quite some time. When googling I find for example https://code.launchpad.net/~ubuntu-branches/ubuntu/wily /nfs-utils/wily-201507271018/+merge/265946 that fixes the network.target vs network-online.target dependency, but it has since been lost in the wind it seems. ** Affects: nfs-utils (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918141 Title: nfs-server.service needs name resolution and network online To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1918141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918141] Re: nfs-server.service needs name resolution and network online
I should note that we have observed this on both 18.04LTS (bionic) and 20.04LTS (focal). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918141 Title: nfs-server.service needs name resolution and network online To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1918141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918141] Re: nfs-server.service needs name resolution and network online
First off, nfs-server starts but doesn't export the unresolvable hosts. The failures do show in systemctl status nfs-server. To reproduce in a VM you'll likely need something that causes network.target to be fulfilled but actual network traffic to not be forwarded until a few seconds later when network-online.target is fulfilled. Exactly how to do this varies between setups, but adding a unit that fulfills network.target shouldn't be too hard, delaying the network startup in a meaningful way is the tricky one. In any case, I recommend systemd-analyze plot > boot.svg to get an overview of the boot timings. If I find time today I can take a stab at figuring something out that emulates the behavior we see on physical hardware, for these machines we see between 8 to 10 seconds for systemd-networkd-wait-online.service to complete, with the corresponding delay in network-online.target fulfillment. I think the record I've seen on physical hardware was 30+ seconds on first boot when doing a major OS upgrade trigging a more involved firmware download and NIC restart... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918141 Title: nfs-server.service needs name resolution and network online To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1918141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918141] Re: nfs-server.service needs name resolution and network online
OK, getting the network delay got a little bit convoluted as you can't clear dependencies with overrides but instead have to copy the unit file and edit it. I'm no systemd expert so this can probably be improved, but on a focal VM host of ours (KVM/Ganeti) that uses systemd-networkd I needed to do this, if you're using some other network setup scheme you'll need to adapt accordingly: * cp /lib/systemd/system/systemd-networkd.service /etc/systemd/system/systemd-networkd.service ** Edit /etc/systemd/system/systemd-networkd.service: *** Comment out Before= and Wants= *** Add in [Unit] section, Before= without network.target and After=/Wants= fakenet.service: Before=multi-user.target shutdown.target After=fakenet.service Wants=fakenet.service *** Add in [Service] section: ExecStartPre=/bin/sleep 10 * Create /etc/systemd/system/fakenet.service with content as [1] (bottom of comment) * systemctl daemon-reload * systemctl enable fakenet * It turned out that systemd-resolved also messed with network.target, so I just disabled it ** Edit /etc/resolv.conf to contain usable DNS resolver ** systemctl stop systemd-resolved ** systemctl mask systemd-resolved ** Check /etc/resolv.conf again and verify that you can do DNS lookups reboot, and then verify with systemd-analyze plot > boot.svg that timings are right, you should have network.target and then 10s or so later network-online.target (I just load boot.svg into a browser and use find to search in the file). If not you have to find the culprit that has a Before=network.target and edit or disable. You should also find that nfs-server starts a few seconds before the network is available, and systemctl status nfs-server should show exportfs: Failed to resolve errors. Hope this helps to QA/reproduce. [1] fakenet.service: [Unit] Description=Fake network.target DefaultDependencies=no After=systemd-udevd.service network-pre.target systemd-sysusers.service systemd-sysctl.service Before=network.target multi-user.target shutdown.target Conflicts=shutdown.target Wants=network.target [Service] Type=oneshot ExecStart=/bin/true [Install] WantedBy=multi-user.target -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918141 Title: nfs-server.service needs name resolution and network online To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1918141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918141] Re: nfs-server.service needs name resolution and network online
For this I honestly see no risks of regressions for nfs-server. Also, be aware that on systems using DHCP depending on network.target or network-online.target has the same effect simply due to the inherent ordering of DHCP packets not passing through until the interface is able to pass traffic. When using static addressing it's essential that things that require networking to be able to handle traffic do depend on the correct thing, and that's network-online.target Regarding the "my system hangs on boot" comment: 1) nfs-server is a server service, it's not something you run on a laptop or somesuch and expect things to work without networking. 2) Network startup has a timeout, so the system will boot eventually. Do remember that one of the appealing things about Ubuntu/Debian is the main goal of services to "just work", and the most basic thing here must be to get at least the dependencies right for things to work in the common usecase for which the service is intended. As a final note on nfs-server.service: It currently does two things: Start the nfs-server and do exportfs. It's the latter that depends on network-online, so the startup could be split into two services with tailored dependencies. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918141 Title: nfs-server.service needs name resolution and network online To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1918141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918141] Re: nfs-server.service needs name resolution and network online
For nfs-server and the risk of applying the fix to stable releases, this is my take: It won't break anything unless you've done something truly esoteric, and then you're on your own anyway IMHO. It will enable nfs-server to consistently start in configurations using static addressing, which is NOT esoteric or strange IMHO, regardless of the startup time of your NIC/switchport/etc. It will make startup consistent, which is currently not the case if your NIC is just slow enough to start to sometime trigger name resolve failures depending on how lucky you were when rebooting the machine. The current behavior is unwanted, and while the fix was present in Ubuntu once upon a time (pre-systemd releases and wily I think), it has since gone missing so this is really a regression that's lingered longer than necessary. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918141 Title: nfs-server.service needs name resolution and network online To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1918141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570950] Re: remote x applications crash on xubuntu 16.04 beta
*** This bug is a duplicate of bug 1574886 *** https://bugs.launchpad.net/bugs/1574886 ** This bug has been marked a duplicate of bug 1574886 All gtk applications Segfault if no GLX context is active -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570950 Title: remote x applications crash on xubuntu 16.04 beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1570950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1610519] Re: apport-gtk crashes with segmentation fault
*** This bug is a duplicate of bug 1574886 *** https://bugs.launchpad.net/bugs/1574886 ** This bug has been marked a duplicate of bug 1574886 All gtk applications Segfault if no GLX context is active -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610519 Title: apport-gtk crashes with segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1610519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1610518] Re: synaptic crashed with segfault
*** This bug is a duplicate of bug 1574886 *** https://bugs.launchpad.net/bugs/1574886 ** This bug has been marked a duplicate of bug 1574886 All gtk applications Segfault if no GLX context is active -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610518 Title: synaptic crashed with segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/1610518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574886] Re: All gtk applications Segfault if no GLX context is active
Upstream bug/discussion: https://github.com/anholt/libepoxy/issues/72 Main issue seems to be libepoxy having been unmaintained for some time, but this issue is showing up in other distros as well so will have to be fixed sooner or later. Patch is trivial, bug/crash is due to passing on a pointer without checking for NULL return value. ** Bug watch added: github.com/anholt/libepoxy/issues #72 https://github.com/anholt/libepoxy/issues/72 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574886 Title: All gtk applications Segfault if no GLX context is active To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libepoxy/+bug/1574886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668557] [NEW] Write performance regression severely affecting hpsa controllers
Public bug reported: Upgrading our HP(E) servers to xenial we have discovered a severe performance regression affecting write performance on Smart Array RAID logical drives. Firmware is up to date with latest HPE SPP release at the time of testing. This performance regression has been verified on multiple sites with different HPE systems and OS:s, downgrading kernel brings back the expected performance. We are NOT seeing this on Dell hardware with H730P (LSI based) controllers, using the same OS installs. Our test system setup: Ubuntu 16.04.2 LTS Server: HP(E) DL380e, 36 G RAM, 1x E5-2420 CPU RAID Controller: Smart Array P420 2GB FBWC RAID setup: 24x 500G SAS HDDs in RAID50 with 2 parity groups. File system: xfs We are also seeing this issue on setups using DL380e with P430 controller and 14 HDDs in RAID6, but those systems are not available for testing. Fast/normal (previous) bulk IO performance is approx 1600-1800 MB/s sustained read and write using a simple dd bs=256k based test. Slow/performance regression reduces the write performance to approx 500-600 MB/s sustained using the same tests and filesystem. We have tested using the following OS installs and kernels: Precise: All tested Ubuntu kernels are fast. Trusty: trusty 3.13.0.110.118 fast utopic 3.16.0.77.68 fast vivid 3.19.0.80.62 slow xenial 4.4.0.64.50 slow Xenial: xenial 4.4.0.64.68 slow hwe 4.8.0.39.10 slow mainline 3.12.64-031264.201610030943 fast mainline 3.16.41-031641.201702270232 fast mainline 3.17.8-031708.201501081837 fast mainline 3.18.0-031800.201412071935 fast mainline 3.18.12-031812.201504221338 fast mainline 3.18.18-031818.201507101433 fast mainline 3.18.21-031821.201509020527 fast mainline 3.18.22-031822.201510031227 slow mainline 3.18.23-031823.201510291931 slow mainline 3.18.24-031824.201511031331 slow mainline 3.18.47-031847.201701181631 slow mainline 4.10.1-041001.201702260735 slow ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "version.log" https://bugs.launchpad.net/bugs/1668557/+attachment/4828073/+files/version.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668557 Title: Write performance regression severely affecting hpsa controllers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668557] Re: Write performance regression severely affecting hpsa controllers
** Attachment added: "hpssacli-show-config-detail.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668557/+attachment/4828075/+files/hpssacli-show-config-detail.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668557 Title: Write performance regression severely affecting hpsa controllers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668557] Re: Write performance regression severely affecting hpsa controllers
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668557/+attachment/4828074/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668557 Title: Write performance regression severely affecting hpsa controllers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668557] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1668557/+attachment/4828117/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668557 Title: Write performance regression severely affecting hpsa controllers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668557] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1668557/+attachment/4828116/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668557 Title: Write performance regression severely affecting hpsa controllers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668557] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1668557/+attachment/4828118/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668557 Title: Write performance regression severely affecting hpsa controllers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668557] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1668557/+attachment/4828119/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668557 Title: Write performance regression severely affecting hpsa controllers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668557] Re: Write performance regression severely affecting hpsa controllers
apport information ** Tags added: apport-collected xenial ** Description changed: Upgrading our HP(E) servers to xenial we have discovered a severe performance regression affecting write performance on Smart Array RAID logical drives. Firmware is up to date with latest HPE SPP release at the time of testing. This performance regression has been verified on multiple sites with different HPE systems and OS:s, downgrading kernel brings back the expected performance. We are NOT seeing this on Dell hardware with H730P (LSI based) controllers, using the same OS installs. Our test system setup: Ubuntu 16.04.2 LTS Server: HP(E) DL380e, 36 G RAM, 1x E5-2420 CPU RAID Controller: Smart Array P420 2GB FBWC RAID setup: 24x 500G SAS HDDs in RAID50 with 2 parity groups. File system: xfs We are also seeing this issue on setups using DL380e with P430 controller and 14 HDDs in RAID6, but those systems are not available for testing. Fast/normal (previous) bulk IO performance is approx 1600-1800 MB/s sustained read and write using a simple dd bs=256k based test. Slow/performance regression reduces the write performance to approx 500-600 MB/s sustained using the same tests and filesystem. We have tested using the following OS installs and kernels: Precise: All tested Ubuntu kernels are fast. Trusty: trusty 3.13.0.110.118 fast utopic 3.16.0.77.68 fast vivid 3.19.0.80.62 slow xenial 4.4.0.64.50 slow Xenial: xenial 4.4.0.64.68 slow hwe 4.8.0.39.10 slow mainline 3.12.64-031264.201610030943 fast mainline 3.16.41-031641.201702270232 fast mainline 3.17.8-031708.201501081837 fast mainline 3.18.0-031800.201412071935 fast mainline 3.18.12-031812.201504221338 fast mainline 3.18.18-031818.201507101433 fast mainline 3.18.21-031821.201509020527 fast mainline 3.18.22-031822.201510031227 slow mainline 3.18.23-031823.201510291931 slow mainline 3.18.24-031824.201511031331 slow mainline 3.18.47-031847.201701181631 slow mainline 4.10.1-041001.201702260735 slow + --- + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Feb 28 10:29 seq + crw-rw 1 root audio 116, 33 Feb 28 10:29 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.20.1-0ubuntu2.5 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 16.04 + IwConfig: Error: [Errno 2] No such file or directory + MachineType: HP ProLiant DL380e Gen8 + Package: linux (not installed) + PciMultimedia: + + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic root=/dev/mapper/rootvg-rootlv ro console=ttyS0,115200n8 noquiet nosplash nomodeset + ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 + RelatedPackageVersions: + linux-restricted-modules-4.4.0-64-generic N/A + linux-backports-modules-4.4.0-64-generic N/A + linux-firmware1.157.8 + RfKill: Error: [Errno 2] No such file or directory + Tags: xenial xenial + Uname: Linux 4.4.0-64-generic x86_64 + UnreportableReason: The report belongs to a package that is not installed. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: False + dmi.bios.date: 08/02/2014 + dmi.bios.vendor: HP + dmi.bios.version: P73 + dmi.chassis.type: 23 + dmi.chassis.vendor: HP + dmi.modalias: dmi:bvnHP:bvrP73:bd08/02/2014:svnHP:pnProLiantDL380eGen8:pvr:cvnHP:ct23:cvr: + dmi.product.name: ProLiant DL380e Gen8 + dmi.sys.vendor: HP ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1668557/+attachment/4828115/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668557 Title: Write performance regression severely affecting hpsa controllers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668557] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1668557/+attachment/4828120/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668557 Title: Write performance regression severely affecting hpsa controllers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668557] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1668557/+attachment/4828121/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668557 Title: Write performance regression severely affecting hpsa controllers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668557] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1668557/+attachment/4828124/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668557 Title: Write performance regression severely affecting hpsa controllers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668557] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1668557/+attachment/4828125/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668557 Title: Write performance regression severely affecting hpsa controllers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668557] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1668557/+attachment/4828123/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668557 Title: Write performance regression severely affecting hpsa controllers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668557] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1668557/+attachment/4828122/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668557 Title: Write performance regression severely affecting hpsa controllers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668557] Re: Write performance regression severely affecting hpsa controllers
Last time I checked the hpsa driver is part of the kernel shipped with Ubuntu... Regardless of whether the core kernel is doing it right or not, the hpsa driver should not advertise a larger max_sectors_kb than it can handle with good performance. FYI, the hpsa driver in the xenial default kernel advertise the stripe size so this breaks performance for any setup with a stripe size more than approx 1 MiB. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668557 Title: Write performance regression severely affecting hpsa controllers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668557] Re: Write performance regression severely affecting hpsa controllers
As a workaround this udev rule can be used. Caveat: It works as intended for us, but I'm not an udev expert. ** Attachment added: "90-hpsa-limitiosize.rules" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668557/+attachment/4828213/+files/90-hpsa-limitiosize.rules -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668557 Title: Write performance regression severely affecting hpsa controllers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668557] Re: Write performance regression severely affecting hpsa controllers
We realized that this likely affects older controllers using the cciss driver as well, updated udev rule for completeness. ** Attachment added: "90-smartarray-limitiosize.rules" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668557/+attachment/4828905/+files/90-smartarray-limitiosize.rules -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668557 Title: Write performance regression severely affecting hpsa controllers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668557] Re: Write performance regression severely affecting hpsa controllers
Johan Guldmyr pointed out that my udev rule attempted to apply the attribute changes to partitions as well, which causes errors in system log files. Uploading a fixed version. ** Attachment added: "90-smartarray-limitiosize.rules" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668557/+attachment/4838063/+files/90-smartarray-limitiosize.rules -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668557 Title: Write performance regression severely affecting hpsa controllers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1668557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1434508] [NEW] PDL::Stats::Basic needs to be recompiled against the newly installed PDL
Public bug reported: [Impact] Ubuntu trusty/14.04 (LTS). Although package can be installed, it's not usable due to pdl, which it depends on, has been upgraded but this package has not been rebuilt against it. This affects all LTS installations (mostly enterprise environments, compute clusters, etc) that wishes to do statistics using the Perl Data Language, PDL. [Test Case] A minimum test script which uses the perl module provided by this package should execute without errors: $ cat pdlstatstest.pl #!/usr/bin/perl use PDL::LiteF;# loads less modules use PDL::NiceSlice;# preprocessor for easier pdl indexing syntax use PDL::Stats; $ ./pdlstatstest.pl [PDL->Version: 10 PDL_CORE_VERSION: 8 XS_VERSION: ] PDL::Stats::Basic needs to be recompiled against the newly installed PDL at /usr/lib/perl/5.18/DynaLoader.pm line 207. Compilation failed in require at (eval 27) line 4. BEGIN failed--compilation aborted at (eval 27) line 4. BEGIN failed--compilation aborted at ./pdlstatstest.pl line 4. [Regression Potential] None, package is not usable as is. Future regressions might happen if the cause for this package not being rebuilt properly when pdl was upgraded isn't fixed. [Other Info] Effort to fix is low, as package only needs to be rebuilt. $ lsb_release -rd Description:Ubuntu 14.04.2 LTS Release:14.04 $ apt-cache policy libpdl-stats-perl libpdl-stats-perl: Installed: 0.6.2-1build1 Candidate: 0.6.2-1build1 Version table: *** 0.6.2-1build1 0 500 http://se.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: pdl (Ubuntu) Importance: Undecided Status: New ** Tags: bitesize packaging testcase -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1434508 Title: PDL::Stats::Basic needs to be recompiled against the newly installed PDL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pdl/+bug/1434508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1434508] Re: PDL::Stats::Basic needs to be recompiled against the newly installed PDL
It wasn't as easy as just rebuilding the package, build fails due to a test failing: https://rt.cpan.org/Public/Bug/Display.html?id=89976 Getting a newer source package from http://packages.ubuntu.com/vivid /libpdl-stats-perl and just doing dpkg-buildpackage on it gives me a .deb, and with it installed I have a usable PDL::Stats. So I don't really know if this falls into the category of an SRU or backport. As the package currently available in trusty doesn't work at all, and the backports page at https://wiki.ubuntu.com/UbuntuBackports hints that bugfixes are more appropriately handled as SRU:s, I guess an SRU makes more sense?? ** Bug watch added: CPAN RT #89976 http://rt.cpan.org/Ticket/Display.html?id=89976 ** Tags added: ftbfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1434508 Title: PDL::Stats::Basic needs to be recompiled against the newly installed PDL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pdl/+bug/1434508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1434508] Re: PDL::Stats::Basic needs to be recompiled against the newly installed PDL
** Package changed: pdl (Ubuntu) => libpdl-stats-perl (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1434508 Title: PDL::Stats::Basic needs to be recompiled against the newly installed PDL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpdl-stats-perl/+bug/1434508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1434508] Re: PDL::Stats::Basic needs to be recompiled against the newly installed PDL
** Also affects: hundredpapercuts Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1434508 Title: PDL::Stats::Basic needs to be recompiled against the newly installed PDL To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1434508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1111416] Re: CONFIG_NFS_V4_1=y in Precise kernel update, please
We have now tested the NFS 4.1 functionality of both the Precise and Quantal kernels and they both work as expected. No regressions have been found when testing on machines not using NFS 4.1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/416 Title: CONFIG_NFS_V4_1=y in Precise kernel update, please To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1111416] Re: CONFIG_NFS_V4_1=y in Precise kernel update, please
For starters, no regressions noticed on machines not using the new features: amd64 laptop doing laptoppy things, also reading/writing nfs3. amd64 server, doing mostly local IO. Pending results from NFS 4.1 tests this is looking promising. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/416 Title: CONFIG_NFS_V4_1=y in Precise kernel update, please To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1065536] Re: rsyslog imrelp module doesn't do DNS resolve to hostname
** Tags added: precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1065536 Title: rsyslog imrelp module doesn't do DNS resolve to hostname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1065536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 789174] Re: rsyslog fails to create tcp socket.
** Tags added: precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/789174 Title: rsyslog fails to create tcp socket. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/789174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997123] Re: iwl4965 works imposible slow because it tries to use 11n on non compatible rooter
iwl4965 is a kernel module ** Package changed: module-init-tools (Ubuntu) => linux-meta (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997123 Title: iwl4965 works imposible slow because it tries to use 11n on non compatible rooter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/997123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997123] Re: iwl4965 works imposible slow because it tries to use 11n on non compatible rooter
I have stability/connectivity issues on University campuses, most of them using high-end Cisco wireless equipment, when I have 11n enabled on Ubuntu 12.04LTS. This was not a problem with 10.04LTS, so this is a regression. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997123 Title: iwl4965 works imposible slow because it tries to use 11n on non compatible rooter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/997123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997123] Re: iwl4965 works imposible slow because it tries to use 11n on non compatible rooter
Is this perhaps a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/836250 ?? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997123 Title: iwl4965 works imposible slow because it tries to use 11n on non compatible rooter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/997123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 910678] Re: gmond crashes when an NFS mount is active
This should be fixed ASAP, Ganglia is an important component in many server environments which is the target of LTS releases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/910678 Title: gmond crashes when an NFS mount is active To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ganglia/+bug/910678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1111416] Re: CONFIG_NFS_V4_1=y in Precise kernel update, please
** Tags removed: verification-needed-precise verification-needed-quantal ** Tags added: verification-done verification-done-precise verification-done-quantal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/416 Title: CONFIG_NFS_V4_1=y in Precise kernel update, please To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 946899] Re: [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
As suggested earlier, this issue seems to be tracked in bug 1140716. That bug recently logs "Fix Released". In hindsight, I'm guessing that the original issue of this bug was something completely different given its age. But since this was what popped up when searching... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/946899 Title: [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/946899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 946899] Re: [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
Same here on precise amd64. Booting with 3.2.0-39 X hangs shortly after login with the earlier mentioned hangcheck messages in the kernel log (machine is remotely login:able). Reverting to 3.2.0-38 yields a stable machine. This is on a machine with an Intel i5 CPU on an ASUS P8H67-V motherboard, with the latest&greatest BIOS (upgrading the BIOS made no difference). ** Tags added: regression-update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/946899 Title: [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/946899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1006212] Re: cciss: hpacucli "ctrl slot=0 create type=ld drives=2:4" hangs, spews call trace in dmesg
Out if curiosity, which version of hpacucli are you guys using? Version? 32bit or 64bit? Running Precise, I see this problem on controllers using the old cciss driver (P400 for example), but not on controllers using the hpsa driver (P810 for example). This is with hpacucli 9.10 64bit. This all worked on lucid, albeit with an earlier hpacucli release which was 32bit, but it indeed smells like a regression. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1006212 Title: cciss: hpacucli "ctrl slot=0 create type=ld drives=2:4" hangs, spews call trace in dmesg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1006212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1006212] Re: cciss: hpacucli "ctrl slot=0 create type=ld drives=2:4" hangs, spews call trace in dmesg
hpacucli 8.x is only available as 32bit binaries. 9.x is available as both 32bit and 64bit binaries. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1006212 Title: cciss: hpacucli "ctrl slot=0 create type=ld drives=2:4" hangs, spews call trace in dmesg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1006212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 660974] [NEW] net-device-up emitted for bonding members
Public bug reported: Binary package hint: ifupdown net-device-up is emitted when bonding link members are configured, which is rather misleading as the machine won't get connectivity until the master device is configured. This leads to problems if you for example wants to use a post-up hook in /etc/network/interfaces to wait for your less cooperative switch that takes 60 seconds to establish a LACP trunk. The attached patch fixes the issue. # lsb_release -rd Description:Ubuntu 10.04.1 LTS Release:10.04 # apt-cache policy ifupdown ifupdown: Installed: 0.6.8ubuntu29.1 Candidate: 0.6.8ubuntu29.1 ** Affects: ifupdown (Ubuntu) Importance: Undecided Status: New -- net-device-up emitted for bonding members https://bugs.launchpad.net/bugs/660974 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 660974] Re: net-device-up emitted for bonding members
** Patch added: "Proposed fix to not emit events for bonding member devices." https://bugs.launchpad.net/bugs/660974/+attachment/1693852/+files/upstart.patch -- net-device-up emitted for bonding members https://bugs.launchpad.net/bugs/660974 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 110992] Re: ipmi modules need to manually inserted and device created
On my lucid install ipmi_si seems to autoload, but ipmi_devintf doesn't. Loading ipmi_devintf is enough to have /dev/ipmi0 created and ipmitool then works. -- ipmi modules need to manually inserted and device created https://bugs.launchpad.net/bugs/110992 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 603170] [NEW] Include backport of driver for mantis/hopper DVB cards
Public bug reported: Please include the backport of the driver for mantis/hopper based DVB cards in the Ubuntu Lucid kernel. There are lots of DVB cards that uses this driver. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=577264 for an excellent summary including the patches accepted in Debian, I strongly suspect that those patches will apply nicely to the Lucid kernel too. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- Include backport of driver for mantis/hopper DVB cards https://bugs.launchpad.net/bugs/603170 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 603170] Re: Include backport of driver for mantis/hopper DVB cards
The driver is included in 2.6.33, so it works with the latest upstream kernel. This backport inclusion request is specific to the Lucid (LTS) kernel. ** Tags removed: needs-kernel-logs needs-upstream-testing -- Include backport of driver for mantis/hopper DVB cards https://bugs.launchpad.net/bugs/603170 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 525154] Re: mountall for /var races with rpc.statd
A lame workaround is to simply add this to /etc/rc.local (before the "exit 0"): /sbin/initctl start statd -- mountall for /var races with rpc.statd https://bugs.launchpad.net/bugs/525154 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 1867949] [NEW] It's time to increase the default pid_max from 32768 to avoid PID wraparounds/collossions
Public bug reported: The kernel.pid_max sysctl defaults to 32768. This is a very historic limit to provide compatibility with ancient binaries. Moving on to the year 2020 multicore CPU:s for desktops, laptops and servers is the standard, and together with PID randomization wraparound happens rather quickly on many-core machines with lots of activity. Wraparounds in itself is not a big issue, but there are corner cases like scripts that checks if a PID is alive etc that run into trouble if another process has started using the PID it expects, scripts (erroneously) using PIDs for work/temporary files, etc. To avoid problems within the lifetime of Ubuntu Focal, it's time to increase kernel.pid_max by default in the distribution by including tuning in a file in /etc/sysctl.d/ Our suggestion is to ship the following tuning by default: # Make PID-rollover not happen as often. # Default is 32768 kernel.pid_max = 99 with the following motivation: 1) It achieves a 30-fold increase in the available number-space, reducing the likelihood of PID wraparound/collisions. 2) It only adds one digit to the PID, so it's still possible to remember a PID 3) Output in top, ps, etc is still nicely readable 3) We have used it for years on Ubuntu 14.04 and onwards, on 1000+ machines and with a wide array of commercial and scientific software without any issues. 4) One could argue that it is a preventive security measure, there are a lot of weirdly written scripts and software out there that behaves badly upon PID reuse/collissions. ** Affects: procps (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867949 Title: It's time to increase the default pid_max from 32768 to avoid PID wraparounds/collossions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1867949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1660587] Re: Dracut cannot be used to generate kernel initramfs image
This seems to be fixed in Ubuntu 24.04 LTS (noble). At least I'm able to create an Ubuntu noble nfsroot, with these caveats: - Must run fai-make-nfsroot on a host with a new-enough debootstrap, I ran it on an Ubuntu noble host. - Must use a newer FAI, the one shipped with Noble isn't new enough. I simply used the FAI Ubuntu jammy PPA (there isn't one for noble yet), both on the host running fai-make-nfsroot and in the nfsroot. - You must have a dhclient binary installed in the nfsroot for the dracut network-legacy module to work, I used isc-dhcp-client (added it to the right place in NFSROOT). Getting this to work was actually a showstopper for us, due to NIC (un)stable naming issues. The Debian nfsroot gave us slightly different NIC names compared to the installed Ubuntu noble, this only affected NICs in PCIe slots... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1660587 Title: Dracut cannot be used to generate kernel initramfs image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1660587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
