[Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) by an insufficient compiler!
I manage 300+ machines that run openafs that has a dkms built kernel module like the nvidia module that needs to be built. I also manage dozens of nvidia gpu servers where users have sudo access and can install anything they want. Here is a snippet of what I found. Note this is for 16.04 systems but 14.04 systems running the 4.4.0-116 kernel will have similar problems: Short story, if your machine is not using the Ubuntu supplied gcc you will have issues with afs and nvidia built kernel modules or any dkms built kernel modules. Longer story below. NOTE! this problem affects at least, openafs, nvidia, virtual box or any dkms built module. I am going to forward this info to gr...@cs.unc.edu. This started with the latest Ubuntu 4.4.0-116 kernel version. Looking through that bug and testing took me hours. The short story is the machines having issues with openafs.ko module are ones that have the Ubuntu toolchain ppa that has a gcc compiler suite that does not support the "retpoline" feature which was recently put in to fix the Spectre security issue. The nvidia module will also have issues. The machines using the Ubuntu supplied gcc compiler are the ones that are not having issues. But, host olympia was a special case. The compiler that works, using "gcc -v" gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9) The ones that don't work like host bvisionserver8: gcc version 5.4.1 20160904 You can use "apt-cache policy gcc" to show what repo the compiler comes from. WARNING, /usr/bin/gcc is a link to /usr/bin/gcc-5, the gcc package is a meta package and you need to query gcc-5. If you query gcc it shows coming from the standard Ubuntu repo but /usr/bin/gcc-5 is coming from the toolchain repo. A good gcc-5 shows: classroom:55% apt-cache policy gcc-5 gcc-5: Installed: 5.4.0-6ubuntu1~16.04.9 Candidate: 5.4.0-6ubuntu1~16.04.9 Version table: *** 5.4.0-6ubuntu1~16.04.9 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 5.3.1-14ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages The bad compilers show: -- bvisionserver8:/> apt-cache policy gcc-5 gcc-5: Installed: 5.4.1-2ubuntu1~16.04 Candidate: 5.4.1-2ubuntu1~16.04 Version table: *** 5.4.1-2ubuntu1~16.04 500 500 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 5.4.0-6ubuntu1~16.04.9 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 5.3.1-14ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages And you can see /etc/apt/sources.list.d/ubuntu-toolchain-r-ubuntu-test-xenial.list repo is configure on those machines. On a good machine modinfo openafs shows that retpoline is turned on in the vermagic: line: classroom:56% modinfo openafs filename: /lib/modules/4.4.0-116-generic/updates/dkms/openafs.ko license:http://www.openafs.org/dl/license10.html srcversion: 4E1BEB8CE16072EF8E64542 depends: vermagic: 4.4.0-116-generic SMP mod_unload modversions retpoline And not turned on a bad machine: bvisionserver8:/> modinfo openafs filename: /lib/modules/4.4.0-116-generic/updates/dkms/openafs.ko license:http://www.openafs.org/dl/license10.html srcversion: 66044F5DC18AA3288DB22FF depends: vermagic: 4.4.0-116-generic SMP mod_unload modversions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750937 Title: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) by an insufficient compiler! To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/1750937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1550481] Re: hpsa driver causing kernel panics on HP ProLiant DL385p Gen8
We recently inherited several Proliant HP-SL270s Gen 8 with P420 raid controller. Loading 16.04 with kernel 4.4.0-31 I cannot see the logical disk, I disabled Intel Vt-d (same as IOMMU) and this did not fix. There was a similar bug that expired where disabling IOMMU allowed the disks to be seen on a ProLiant BL465c Gen8 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590072 Ubuntu 14.04 can see the logical disk on the installer, would really like to load 16.04. FYI Red Hat 7 can see the disks also. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1550481 Title: hpsa driver causing kernel panics on HP ProLiant DL385p Gen8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577596] Re: ntpd not started when using ntpdate
*** This bug is a duplicate of bug 1575572 *** https://bugs.launchpad.net/bugs/1575572 Another observation, the ntpdate command is really slow on Ubuntu 14.04 and 16.04. On average it takes about 6.1 seconds to run the ntpdate command, I am running ntpdate after boot. Our Red hat 6.8 machines take about 0.1 seconds. We manage 300+ Ubuntu 14.04 and 16.04 systems and I checked ntpdate on several of them. Still can't figure out why most machines work but some consistently fail to start ntpd. Even the ones that do start ntpd ntpdate still takes 6+ seconds to run. And we have our own in house stratum 1 time servers that are on the same internal network. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577596 Title: ntpd not started when using ntpdate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1577596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577596] Re: ntpd not started when using ntpdate
*** This bug is a duplicate of bug 1575572 *** https://bugs.launchpad.net/bugs/1575572 I am seeing this on some but not all systems. I can only manually start after first doing a stop: root@tophat:~# ps -ef | grep ntp root 2380 2365 0 11:51 pts/800:00:00 grep --color=auto ntp root@tophat:~# systemctl start ntp root@tophat:~# ps -ef | grep ntp root 2384 2365 0 11:51 pts/800:00:00 grep --color=auto ntp root@tophat:~# systemctl stop ntp root@tophat:~# systemctl start ntp root@tophat:~# ps -ef | grep ntp ntp 2414 1 0 11:51 ?00:00:00 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 111:116 root 2416 2365 0 11:51 pts/800:00:00 grep --color=auto ntp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577596 Title: ntpd not started when using ntpdate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1577596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1558196] Re: ypbind not able to socket activate rpcbind under systemd, fails at boot unless something else starts rpcbind
Does your /etc/nsswitch.conf have: group: files nis ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1558196 Title: ypbind not able to socket activate rpcbind under systemd, fails at boot unless something else starts rpcbind To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1558196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1558196] Re: ypbind not able to socket activate rpcbind under systemd, fails at boot unless something else starts rpcbind
Doing this forces rpcbind to start on boot and then nis starts correctly: # /bin/systemctl add-wants multi-user.target rpcbind.service Created symlink from /etc/systemd/system/multi-user.target.wants/rpcbind.service to /lib/systemd/system/rpcbind.service -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1558196 Title: ypbind not able to socket activate rpcbind under systemd, fails at boot unless something else starts rpcbind To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1558196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1558196] Re: ypbind not able to socket activate rpcbind under systemd, fails at boot unless something else starts rpcbind
Doing this forces rpcbind to start on boot and then nis starts correctly: # /bin/systemctl add-wants multi-user.target rpcbind.service Created symlink from /etc/systemd/system/multi-user.target.wants/rpcbind.service to /lib/systemd/system/rpcbind.service -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to rpcbind in Ubuntu. https://bugs.launchpad.net/bugs/1558196 Title: ypbind not able to socket activate rpcbind under systemd, fails at boot unless something else starts rpcbind To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1558196/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1558196] Re: rpcbind does not start on boot under systemd
We are on the right track, I have tried so many things I need to reload the system to reset the default config for everything. Our 14.04 systems run rpc.statd but not all the other nfs stuff. So maybe enabling that service will be a work around, that is it will cause rpcbind to start. I will need some time to reload a default system. Thanks for your input. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to rpcbind in Ubuntu. https://bugs.launchpad.net/bugs/1558196 Title: rpcbind does not start on boot under systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1558196/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1558196] Re: rpcbind does not start on boot under systemd
I re-installed the lasted 16.04 beta. Be default the rpc-statd service is not enabled, I enabled and rebooted, same problem rpcbind does not start and neither does the nis service. If I manualy start with systemctl start rpc-statd then rpcbind and rpcbind.statd start. If I systemctl start nis it does not start, I have to first stop withs ystemctl stop nis and then do a start. So still no luck getting nis to start without installing the nfs server. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to rpcbind in Ubuntu. https://bugs.launchpad.net/bugs/1558196 Title: rpcbind does not start on boot under systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1558196/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1558196] Re: ypbind not able to socket activate rpcbind under systemd, fails at boot unless something else starts rpcbind
IMHO if the rpcbind service is enabled it should just start at boot time and not have to be self activated. Found this but no real good solution. "Regression: rpcbind doesn't start at boottime on systemd controlled machines." https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805167 ** Bug watch added: Debian Bug tracker #805167 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805167 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to rpcbind in Ubuntu. https://bugs.launchpad.net/bugs/1558196 Title: ypbind not able to socket activate rpcbind under systemd, fails at boot unless something else starts rpcbind To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1558196/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1558196] Re: rpcbind does not start on boot under systemd
I re-installed the lasted 16.04 beta. Be default the rpc-statd service is not enabled, I enabled and rebooted, same problem rpcbind does not start and neither does the nis service. If I manualy start with systemctl start rpc-statd then rpcbind and rpcbind.statd start. If I systemctl start nis it does not start, I have to first stop withs ystemctl stop nis and then do a start. So still no luck getting nis to start without installing the nfs server. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1558196 Title: rpcbind does not start on boot under systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1558196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1558196] Re: rpcbind does not start on boot under systemd
We use nis ybind which is started out of /etc/init.d/nis which fails because rpcbind is not running. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1558196 Title: rpcbind does not start on boot under systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1558196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1558196] [NEW] rpcbind does not start on boot under systemd
Public bug reported: did apt-get update/upgrade March 16, 2016 Description:Ubuntu Xenial Xerus (development branch) Release:16.04 rpcbind does not start on boot, tried various systemd debugging steps with no clues. After boot systemctl start rpcbind works. There is a /etc/init.d/rpcbind and a /lib/systemd/system/rpcbind.service config files which is confusing. ** Affects: rpcbind (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to rpcbind in Ubuntu. https://bugs.launchpad.net/bugs/1558196 Title: rpcbind does not start on boot under systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1558196/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1558196] [NEW] rpcbind does not start on boot under systemd
Public bug reported: did apt-get update/upgrade March 16, 2016 Description:Ubuntu Xenial Xerus (development branch) Release:16.04 rpcbind does not start on boot, tried various systemd debugging steps with no clues. After boot systemctl start rpcbind works. There is a /etc/init.d/rpcbind and a /lib/systemd/system/rpcbind.service config files which is confusing. ** Affects: rpcbind (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/1558196 Title: rpcbind does not start on boot under systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1558196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1558196] Re: rpcbind does not start on boot under systemd
Meant to type "ypbind", so I installed nfs-kernel-server and now rpcbind and ypbind start. Hate to install nfs-kernel-server on all our desktops and servers that do not need it but they do need ypbind. Thanks for your help. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to rpcbind in Ubuntu. https://bugs.launchpad.net/bugs/1558196 Title: rpcbind does not start on boot under systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1558196/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1558196] Re: rpcbind does not start on boot under systemd
Meant to type "ypbind", so I installed nfs-kernel-server and now rpcbind and ypbind start. Hate to install nfs-kernel-server on all our desktops and servers that do not need it but they do need ypbind. Thanks for your help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1558196 Title: rpcbind does not start on boot under systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1558196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1558196] Re: rpcbind does not start on boot under systemd
We are on the right track, I have tried so many things I need to reload the system to reset the default config for everything. Our 14.04 systems run rpc.statd but not all the other nfs stuff. So maybe enabling that service will be a work around, that is it will cause rpcbind to start. I will need some time to reload a default system. Thanks for your input. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1558196 Title: rpcbind does not start on boot under systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1558196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1558196] Re: ypbind not able to socket activate rpcbind under systemd, fails at boot unless something else starts rpcbind
IMHO if the rpcbind service is enabled it should just start at boot time and not have to be self activated. Found this but no real good solution. "Regression: rpcbind doesn't start at boottime on systemd controlled machines." https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805167 ** Bug watch added: Debian Bug tracker #805167 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805167 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1558196 Title: ypbind not able to socket activate rpcbind under systemd, fails at boot unless something else starts rpcbind To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1558196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1558196] Re: rpcbind does not start on boot under systemd
rpcbind.socket is active, nis fails to start because it cannot contact the rpcbind server so I guess it is not using the socket to communicate. Reading the ypbind and ypbind.conf man pages does not have any info or options on registering with rpcbind. root@tophat:~# systemctl status rpcbind.socket * rpcbind.socket - RPCbind Server Activation Socket Loaded: loaded (/lib/systemd/system/rpcbind.socket; enabled; vendor preset: enabled) Active: active (listening) since Thu 2016-03-17 07:49:58 EDT; 1min 1s ago Listen: /run/rpcbind.sock (Stream) root@tophat:~# systemctl status rpcbind * rpcbind.service - RPC bind portmap service Loaded: loaded (/lib/systemd/system/rpcbind.service; indirect; vendor preset: enabled) Drop-In: /run/systemd/generator/rpcbind.service.d `-50-rpcbind-$portmap.conf Active: inactive (dead) root@tophat:~# systemctl status nis * nis.service - LSB: Start NIS client and server daemons. Loaded: loaded (/etc/init.d/nis; bad; vendor preset: enabled) Active: active (exited) since Thu 2016-03-17 07:50:33 EDT; 48s ago Docs: man:systemd-sysv-generator(8) Process: 1230 ExecStart=/etc/init.d/nis start (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 512) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1558196 Title: rpcbind does not start on boot under systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1558196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1558196] Re: rpcbind does not start on boot under systemd
We use nis ybind which is started out of /etc/init.d/nis which fails because rpcbind is not running. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to rpcbind in Ubuntu. https://bugs.launchpad.net/bugs/1558196 Title: rpcbind does not start on boot under systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1558196/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1558196] Re: rpcbind does not start on boot under systemd
rpcbind.socket is active, nis fails to start because it cannot contact the rpcbind server so I guess it is not using the socket to communicate. Reading the ypbind and ypbind.conf man pages does not have any info or options on registering with rpcbind. root@tophat:~# systemctl status rpcbind.socket * rpcbind.socket - RPCbind Server Activation Socket Loaded: loaded (/lib/systemd/system/rpcbind.socket; enabled; vendor preset: enabled) Active: active (listening) since Thu 2016-03-17 07:49:58 EDT; 1min 1s ago Listen: /run/rpcbind.sock (Stream) root@tophat:~# systemctl status rpcbind * rpcbind.service - RPC bind portmap service Loaded: loaded (/lib/systemd/system/rpcbind.service; indirect; vendor preset: enabled) Drop-In: /run/systemd/generator/rpcbind.service.d `-50-rpcbind-$portmap.conf Active: inactive (dead) root@tophat:~# systemctl status nis * nis.service - LSB: Start NIS client and server daemons. Loaded: loaded (/etc/init.d/nis; bad; vendor preset: enabled) Active: active (exited) since Thu 2016-03-17 07:50:33 EDT; 48s ago Docs: man:systemd-sysv-generator(8) Process: 1230 ExecStart=/etc/init.d/nis start (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 512) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to rpcbind in Ubuntu. https://bugs.launchpad.net/bugs/1558196 Title: rpcbind does not start on boot under systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpcbind/+bug/1558196/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1316035] Re: matrox g200eR2 is unclaimed in 14.04
I did an online chat with Dell to see if they new anything about this and they could not help. Here was there response: Ok. Well, I had them review the article and they see many vendors having the same issue. We don't have any updates / patches for the Matrox graphics card for this kind of issue. Were feeling that this is a desktop OS that is likely a little more graphics intensive than what the server mobo onboard video can do. They had the linux group review this bug. BTW, window 7 and windows 8.1 work fine with this video card and mobo is a short for motherboard. We have put in an inexpensive nvida card in our servers if we need to use the gui to get around this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1316035 Title: matrox g200eR2 is unclaimed in 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1316035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1316035] Re: matrox g200eR2 is unclaimed in 14.04
Still the same issue on 2 new Dell T630 servers Ubuntu 14.04 LTS. % lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04.2 LTS Release:14.04 Codename: trusty % lspci | grep VGA 09:00.0 VGA compatible controller: Matrox Electronics Systems Ltd. G200eR2 (rev 01) % lshw -C display PCI (sysfs) NCL *-display UNCLAIMED description: VGA compatible controller product: G200eR2 vendor: Matrox Electronics Systems Ltd. physical id: 0 bus info: pci@:09:00.0 version: 01 width: 32 bits clock: 33MHz capabilities: pm vga_controller bus_master cap_list configuration: latency=0 maxlatency=32 mingnt=16 resources: memory:9000-90ff memory:9180-91803fff memory:9100-917f % grep '(EE)' /var/log/Xorg.0.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 2742.630] (EE) open /dev/dri/card0: No such file or directory [ 2742.733] (EE) MGA(0): [drm] Direct rendering only supported with G200/G400/G450/G550. [ 2742.742] (EE) AIGLX: reverting to software rendering -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1316035 Title: matrox g200eR2 is unclaimed in 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1316035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 993259] Re: ypbind does not start on boot
This may help if you have this issue with ypbind trying to start and the network not up yet: Use IP addreses in /etc/yp.conf for example: domain your_nis_domain server 10.10.123.123 If the network is not up, ypbind starts and cannot reslove the hostname in yp.conf and dies. If you supply an IP address it will start and bind when the network is up. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/993259 Title: ypbind does not start on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/993259/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 993259] Re: ypbind does not start on boot
This may help if you have this issue with ypbind trying to start and the network not up yet: Use IP addreses in /etc/yp.conf for example: domain your_nis_domain server 10.10.123.123 If the network is not up, ypbind starts and cannot reslove the hostname in yp.conf and dies. If you supply an IP address it will start and bind when the network is up. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/993259 Title: ypbind does not start on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/993259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 993259] Re: ypbind does not start on boot
The problem is with NetworkManager. If the system boots with ifup and DHCP ypbind starts fine. That is uncomment the iface etho line in /etc/network/interfaces and make sure the following entry is in /etc/NetworkManager/NetworkManager.conf so that NetworkManager does not control the interface: [ifupdown] managed=false -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/993259 Title: ypbind does not start on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/993259/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 993259] Re: ypbind does not start on boot
The problem is with NetworkManager. If the system boots with ifup and DHCP ypbind starts fine. That is uncomment the iface etho line in /etc/network/interfaces and make sure the following entry is in /etc/NetworkManager/NetworkManager.conf so that NetworkManager does not control the interface: [ifupdown] managed=false -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/993259 Title: ypbind does not start on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/993259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 867806] Re: df -h permission denied error
I am seeing this in precise 12.04, latest patches, some machines have the issue, others do not: % lsb_release -dcr Description:Ubuntu 12.04 LTS Release:12.04 Codename: precise % df -hl df: `/var/lib/lightdm/.gvfs': Permission denied Filesystem Size Used Avail Use% Mounted on /dev/mapper/sdavg-root 9.3G 3.1G 5.8G 35% / udev 489M 4.0K 489M 1% /dev tmpfs 199M 804K 198M 1% /run none 5.0M 0 5.0M 0% /run/lock none 496M 144K 496M 1% /run/shm /dev/mapper/sdavg-backup20G 416M 18G 3% /backup /dev/sda1 184M 30M 146M 17% /boot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/867806 Title: df -h permission denied error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/867806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 867806] Re: df -h permission denied error
If someone is logged into the desktop, gvfs mounts in there home dir, and df works if you ssh login as another user and do a df. The problem I am seeing is when no one is logged in and /var/lib/lightdm/.gvfs is mounted. For example: No one logged into the desktop: $ df df: `/var/lib/lightdm/.gvfs': Permission denied Filesystem1K-blocksUsed Available Use% Mounted on /dev/mapper/sdavg-root 9733688 3411164 5834284 37% / udev 495080 4495076 1% /dev tmpfs201656 808200848 1% /run none 5120 0 5120 0% /run/lock none 504140 152503988 1% /run/shm /dev/mapper/sdavg-backup 19932248 425728 18506688 3% /backup /dev/sda1188403 30626148049 18% /boot The mount command shows the mount: $ mount | grep gvfs gvfs-fuse-daemon on /var/lib/lightdm/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=lightdm) If another users is logged into the system mount shows: mount | grep gvfs gvfs-fuse-daemon on /home/sopkol/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=sopkol) and df works: $ df Filesystem1K-blocksUsed Available Use% Mounted on /dev/mapper/sdavg-root 9733688 3411196 5834252 37% / udev 495080 4495076 1% /dev tmpfs201656 808200848 1% /run none 5120 0 5120 0% /run/lock none 504140 152503988 1% /run/shm /dev/mapper/sdavg-backup 19932248 425728 18506688 3% /backup /dev/sda1188403 30626148049 18% /boot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/867806 Title: df -h permission denied error To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/867806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 867806] Re: df -h permission denied error
Another observation. When no one is logged in and /var/lib/lightdm is mounted the directory permissions do not allow other access: % ls -ld /var/lib/lightdm drwxr-x--- 9 lightdm lightdm 4096 May 6 09:50 /var/lib/lightdm If someone is logged into the desktop gui the gvfs directory permissions are set to whatever the users home directory is set to: % ls -ld /home/sopkol drwxr-xr-x 23 sopkol sopkol 4096 May 8 15:54 /home/sopkol So if you can read the directory mount df does not complain permission denied. If you chmod on /var/lib/lightdm so you can read the dir the problem goes away. Don't know if that is a security issue: % chmod 755 ld /var/lib/lightdm and df will not complain. I did a reboot and the permissions did not change and it still worked: % mount | grep gvfs gvfs-fuse-daemon on /var/lib/lightdm/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=lightdm) |% ls -ld /var/lib/lightdm drwxr-xr-x 9 lightdm lightdm 4096 May 8 16:01 /var/lib/lightdm/ |% df Filesystem1K-blocksUsed Available Use% Mounted on /dev/mapper/sdavg-root 9733688 3411316 5834132 37% / udev 495080 4495076 1% /dev tmpfs201656 804200852 1% /run none 5120 0 5120 0% /run/lock none 504140 144503996 1% /run/shm /dev/mapper/sdavg-backup 19932248 425728 18506688 3% /backup /dev/sda1188403 30626148049 18% /boot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/867806 Title: df -h permission denied error To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/867806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 993259] Re: ypbind does not start on boot
So the network is taking a really long time to come up using DHCP. I found that the entry in /etc/network/interfaces had the iface eth0 inet dhcp entry commented out as shown below. If I un-comment the iface etho inet dhcp entry things work, the network comes up fast and ypbind starts. It appears NetworkManager is commenting out the line. and it is taking a long time for it to bring up the interface. --- /etc/network/interfaces file # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 #NetworkManager#iface eth0 inet dhcp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/993259 Title: ypbind does not start on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/993259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 993259] Re: ypbind does not start on boot
I confirmed this bug on 4 systems. Here is the output from /var/log/upstart/ypbind.log: Setting NIS domainname to: sunrize No NIS server and no -broadcast option specified. Add a NIS server to the /etc/yp.conf configuration file, or start ypbind with the -broadcast option. Binding to YP server .backgrounded During boot it thinks there is no nis server in yp.conf. If i put a sleep statement at the bottom of the /etc/init/ypbind.conf pre-start script section, its seems to work. I have to crank the sleep to 10 seconds to get it to work. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/993259 Title: ypbind does not start on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/993259/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 993259] Re: ypbind does not start on boot
I confirmed this bug on 4 systems. Here is the output from /var/log/upstart/ypbind.log: Setting NIS domainname to: sunrize No NIS server and no -broadcast option specified. Add a NIS server to the /etc/yp.conf configuration file, or start ypbind with the -broadcast option. Binding to YP server .backgrounded During boot it thinks there is no nis server in yp.conf. If i put a sleep statement at the bottom of the /etc/init/ypbind.conf pre-start script section, its seems to work. I have to crank the sleep to 10 seconds to get it to work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/993259 Title: ypbind does not start on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/993259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 993259] [NEW] ypbind does not start on boot
Public bug reported: root@tophat:/tmp# lsb_release -rd Description:Ubuntu 12.04 LTS Release:12.04 root@tophat:/var/tmp# apt-cache policy nis nis: Installed: 3.17-32ubuntu4 Candidate: 3.17-32ubuntu4 Version table: *** 3.17-32ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages 100 /var/lib/dpkg/status On reboot the ypbind process does not start. After reboot initctl shows it is running but there is no running process. If you stop/start it then it works as shown here: root@tophat:/var/tmp# ypwhich ypwhich: Can't communicate with ypbind root@tophat:/tmp## status ypbind ypbind start/running root@tophat:/tmp# start ypbind start: Job is already running: ypbind root@tophat:/tmp# stop ypbind ypbind stop/waiting root@tophat:/tmp# start ypbind ypbind start/running, process 2400 root@tophat:/var/tmp# ypwhich fafnir.cs.unc.edu Here is the ypbind syslog entries after booting: May 2 09:05:19 tophat kernel: [ 16.320371] init: ypbind main process (819) terminated with status 1 May 2 09:05:19 tophat kernel: [ 16.320441] init: ypbind main process ended, respawning May 2 09:05:24 tophat kernel: [ 21.587347] init: wait-for-state (atdypbind) main process (1074) killed by TERM signal May 2 09:05:24 tophat kernel: [ 21.588998] init: wait-for-state (autofsypbind) main process (1086) killed by TERM signal May 2 09:05:24 tophat kernel: [ 21.590407] init: wait-for-state (lightdmypbind) main process (1148) killed by TERM signal I did a ps -elf in /etc/rc.local and saved to a file, it shows this: rc.local ran Wed May 2 09:05:20 EDT 2012 F S UIDPID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD 4 S root 1 0 6 80 0 - 5679 poll_s 09:05 ?00:00:01 /sbin/init 1 S root 2 0 0 80 0 - 0 kthrea 09:05 ?00:00:00 [kthreadd] 1 S root 3 2 0 80 0 - 0 run_ks 09:05 ?00:00:00 [ksoftirqd/0] 1 S root 4 2 0 80 0 - 0 worker 09:05 ?00:00:00 [kworker/0:0] 5 S root 5 2 2 80 0 - 0 worker 09:05 ?00:00:00 [kworker/u:0] 1 S root 6 2 0 -40 - - 0 cpu_st 09:05 ?00:00:00 [migration/0] 5 S root 7 2 0 -40 - - 0 watchd 09:05 ?00:00:00 [watchdog/0] 1 S root 8 2 0 -40 - - 0 cpu_st 09:05 ?00:00:00 [migration/1] 1 S root 9 2 0 80 0 - 0 worker 09:05 ?00:00:00 [kworker/1:0] 1 S root10 2 0 80 0 - 0 run_ks 09:05 ?00:00:00 [ksoftirqd/1] 1 S root11 2 0 80 0 - 0 worker 09:05 ?00:00:00 [kworker/0:1] 5 S root12 2 0 -40 - - 0 watchd 09:05 ?00:00:00 [watchdog/1] 1 S root13 2 0 60 -20 - 0 rescue 09:05 ?00:00:00 [cpuset] 1 S root14 2 0 60 -20 - 0 rescue 09:05 ?00:00:00 [khelper] 5 S root15 2 0 80 0 - 0 devtmp 09:05 ?00:00:00 [kdevtmpfs] 1 S root16 2 0 60 -20 - 0 rescue 09:05 ?00:00:00 [netns] 1 S root17 2 0 80 0 - 0 worker 09:05 ?00:00:00 [kworker/u:1] 1 S root18 2 0 80 0 - 0 bdi_sy 09:05 ?00:00:00 [sync_supers] 1 S root19 2 0 80 0 - 0 bdi_fo 09:05 ?00:00:00 [bdi-default] 1 S root20 2 0 60 -20 - 0 rescue 09:05 ?00:00:00 [kintegrityd] 1 S root21 2 0 60 -20 - 0 rescue 09:05 ?00:00:00 [kblockd] 1 S root22 2 0 60 -20 - 0 rescue 09:05 ?00:00:00 [ata_sff] 1 S root23 2 0 80 0 - 0 hub_th 09:05 ?00:00:00 [khubd] 1 S root24 2 0 60 -20 - 0 rescue 09:05 ?00:00:00 [md] 1 S root25 2 0 80 0 - 0 worker 09:05 ?00:00:00 [kworker/1:1] 1 S root26 2 0 80 0 - 0 watchd 09:05 ?00:00:00 [khungtaskd] 1 S root27 2 0 80 0 - 0 kswapd 09:05 ?00:00:00 [kswapd0] 1 S root28 2 0 85 5 - 0 ksm_sc 09:05 ?00:00:00 [ksmd] 1 S root29 2 0 99 19 - 0 khugep 09:05 ?00:00:00 [khugepaged] 1 S root30 2 0 80 0 - 0 fsnoti 09:05 ?00:00:00 [fsnotify_mark] 1 S root31 2 0 80 0 - 0 ecrypt 09:05 ?00:00:00 [ecryptfs-kthrea] 1 S root32 2 0 60 -20 - 0 rescue 09:05 ?00:00:00 [crypto] 1 S root40 2 0 60 -20 - 0 rescue 09:05 ?00:00:00 [kthrotld] 1 S root41 2 0 80 0 - 0 scsi_e 09:05 ?00:00:00 [scsi_eh_0] 1 S root42 2 0 80 0 - 0 scsi_e 09:05 ?00:00:00 [scsi_eh_1] 1 S root43 2 0 80 0 - 0 worker 09:05 ?00:00:00 [kworker/u:2] 1 S root
[Bug 993259] Re: ypbind does not start on boot
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/993259 Title: ypbind does not start on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/993259/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 993259] [NEW] ypbind does not start on boot
Public bug reported: root@tophat:/tmp# lsb_release -rd Description:Ubuntu 12.04 LTS Release:12.04 root@tophat:/var/tmp# apt-cache policy nis nis: Installed: 3.17-32ubuntu4 Candidate: 3.17-32ubuntu4 Version table: *** 3.17-32ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages 100 /var/lib/dpkg/status On reboot the ypbind process does not start. After reboot initctl shows it is running but there is no running process. If you stop/start it then it works as shown here: root@tophat:/var/tmp# ypwhich ypwhich: Can't communicate with ypbind root@tophat:/tmp## status ypbind ypbind start/running root@tophat:/tmp# start ypbind start: Job is already running: ypbind root@tophat:/tmp# stop ypbind ypbind stop/waiting root@tophat:/tmp# start ypbind ypbind start/running, process 2400 root@tophat:/var/tmp# ypwhich fafnir.cs.unc.edu Here is the ypbind syslog entries after booting: May 2 09:05:19 tophat kernel: [ 16.320371] init: ypbind main process (819) terminated with status 1 May 2 09:05:19 tophat kernel: [ 16.320441] init: ypbind main process ended, respawning May 2 09:05:24 tophat kernel: [ 21.587347] init: wait-for-state (atdypbind) main process (1074) killed by TERM signal May 2 09:05:24 tophat kernel: [ 21.588998] init: wait-for-state (autofsypbind) main process (1086) killed by TERM signal May 2 09:05:24 tophat kernel: [ 21.590407] init: wait-for-state (lightdmypbind) main process (1148) killed by TERM signal I did a ps -elf in /etc/rc.local and saved to a file, it shows this: rc.local ran Wed May 2 09:05:20 EDT 2012 F S UIDPID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD 4 S root 1 0 6 80 0 - 5679 poll_s 09:05 ?00:00:01 /sbin/init 1 S root 2 0 0 80 0 - 0 kthrea 09:05 ?00:00:00 [kthreadd] 1 S root 3 2 0 80 0 - 0 run_ks 09:05 ?00:00:00 [ksoftirqd/0] 1 S root 4 2 0 80 0 - 0 worker 09:05 ?00:00:00 [kworker/0:0] 5 S root 5 2 2 80 0 - 0 worker 09:05 ?00:00:00 [kworker/u:0] 1 S root 6 2 0 -40 - - 0 cpu_st 09:05 ?00:00:00 [migration/0] 5 S root 7 2 0 -40 - - 0 watchd 09:05 ?00:00:00 [watchdog/0] 1 S root 8 2 0 -40 - - 0 cpu_st 09:05 ?00:00:00 [migration/1] 1 S root 9 2 0 80 0 - 0 worker 09:05 ?00:00:00 [kworker/1:0] 1 S root10 2 0 80 0 - 0 run_ks 09:05 ?00:00:00 [ksoftirqd/1] 1 S root11 2 0 80 0 - 0 worker 09:05 ?00:00:00 [kworker/0:1] 5 S root12 2 0 -40 - - 0 watchd 09:05 ?00:00:00 [watchdog/1] 1 S root13 2 0 60 -20 - 0 rescue 09:05 ?00:00:00 [cpuset] 1 S root14 2 0 60 -20 - 0 rescue 09:05 ?00:00:00 [khelper] 5 S root15 2 0 80 0 - 0 devtmp 09:05 ?00:00:00 [kdevtmpfs] 1 S root16 2 0 60 -20 - 0 rescue 09:05 ?00:00:00 [netns] 1 S root17 2 0 80 0 - 0 worker 09:05 ?00:00:00 [kworker/u:1] 1 S root18 2 0 80 0 - 0 bdi_sy 09:05 ?00:00:00 [sync_supers] 1 S root19 2 0 80 0 - 0 bdi_fo 09:05 ?00:00:00 [bdi-default] 1 S root20 2 0 60 -20 - 0 rescue 09:05 ?00:00:00 [kintegrityd] 1 S root21 2 0 60 -20 - 0 rescue 09:05 ?00:00:00 [kblockd] 1 S root22 2 0 60 -20 - 0 rescue 09:05 ?00:00:00 [ata_sff] 1 S root23 2 0 80 0 - 0 hub_th 09:05 ?00:00:00 [khubd] 1 S root24 2 0 60 -20 - 0 rescue 09:05 ?00:00:00 [md] 1 S root25 2 0 80 0 - 0 worker 09:05 ?00:00:00 [kworker/1:1] 1 S root26 2 0 80 0 - 0 watchd 09:05 ?00:00:00 [khungtaskd] 1 S root27 2 0 80 0 - 0 kswapd 09:05 ?00:00:00 [kswapd0] 1 S root28 2 0 85 5 - 0 ksm_sc 09:05 ?00:00:00 [ksmd] 1 S root29 2 0 99 19 - 0 khugep 09:05 ?00:00:00 [khugepaged] 1 S root30 2 0 80 0 - 0 fsnoti 09:05 ?00:00:00 [fsnotify_mark] 1 S root31 2 0 80 0 - 0 ecrypt 09:05 ?00:00:00 [ecryptfs-kthrea] 1 S root32 2 0 60 -20 - 0 rescue 09:05 ?00:00:00 [crypto] 1 S root40 2 0 60 -20 - 0 rescue 09:05 ?00:00:00 [kthrotld] 1 S root41 2 0 80 0 - 0 scsi_e 09:05 ?00:00:00 [scsi_eh_0] 1 S root42 2 0 80 0 - 0 scsi_e 09:05 ?00:00:00 [scsi_eh_1] 1 S root43 2 0 80 0 - 0 worker 09:05 ?00:00:00 [kworker/u:2] 1 S root
[Bug 993259] Re: ypbind does not start on boot
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/993259 Title: ypbind does not start on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/993259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 760887] Re: Unable to network install on natty
Had the same problem on a Dell 2650 Server and a Dell workstations both with a Broadcom ethernet chip. Very annoying, works with 10.04 but not 11.04. I manually added the IP several times to keep the install going I do not understand the fix mentioned by Sandor. Below are the 2 network cards and the install syslog messages. After the install things seem to work fine. % lshw -C network WARNING: you should run this program as super-user. *-network:0 description: Ethernet interface product: NetXtreme BCM5703X Gigabit Ethernet vendor: Broadcom Corporation physical id: 6 bus info: pci@:03:06.0 logical name: eth0 version: 02 serial: 00:0f:1f:70:02:98 size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 66MHz capabilities: bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=tg3 driverversion=3.116 duplex=full firmware=5703-v2.25a ip=152.2.128.97 latency=64 mingnt=64 multicast=yes port=twisted pair speed=1Gbit/s resources: irq:28 memory:fcd1-fcd1 % lshw -C network WARNING: you should run this program as super-user. *-network:0 description: Ethernet interface product: NetXtreme BCM5705 Gigabit Ethernet vendor: Broadcom Corporation physical id: 0 bus info: pci@:02:00.0 logical name: eth0 version: 01 serial: 00:10:18:0b:00:22 width: 64 bits clock: 66MHz capabilities: bus_master cap_list rom ethernet physical configuration: broadcast=yes driver=tg3 driverversion=3.102 firmware=5705-v3.11 ip=152.2.131.168 latency=64 mingnt=64 multicast=yes Jul 13 13:56:29 net/hw-detect.hotplug: Detected hotpluggable network interface eth0 Jul 13 13:57:15 kernel: [ 487.983861] tg3 :03:06.0: eth0: Tigon3 [partno(BCM95703A30) rev 1002] (PCIX:133MHz:64-bit) MAC address 00:0f:1f:70:02:98 Jul 13 13:57:15 kernel: [ 487.983876] tg3 :03:06.0: eth0: attached PHY is 5703 (10/100/1000Base-T Ethernet) (WireSpeed[1]) Jul 13 13:57:15 kernel: [ 487.983885] tg3 :03:06.0: eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1] Jul 13 13:57:15 kernel: [ 487.983894] tg3 :03:06.0: eth0: dma_rwctrl[769c4000] dma_mask[64-bit] Jul 13 13:57:15 net/hw-detect.hotplug: Detected hotpluggable network interface eth0 Jul 13 13:57:27 kernel: [ 499.357380] tg3 :03:06.0: eth0: Failed to load firmware tigon/tg3_tso.bin Jul 13 13:57:27 kernel: [ 499.357390] tg3 :03:06.0: eth0: TSO capability disabled Jul 13 13:57:27 kernel: [ 499.467335] ADDRCONF(NETDEV_UP): eth0: link is not ready -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/760887 Title: Unable to network install on natty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/760887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
