[Bug 567591] Re: statd does not start when /usr is mounted on a separate volume
I think the bug may be related to a recent change in portmap: indeed until recently portmap did start on "local-filesystems", so /usr (and /var, etc.) was mounted before portmap starts, and statd starts after portmap, so statd could start properly. portmap (6.0.0-1ubuntu2) lucid; urgency=low * portmap should start on virtual-filesystems, not local-filesystems, since it only ever writes to /var/run; this should break the circular dependency between portmap and mountall when the root filesystem is on NFS. LP: #537133 -- Steve LangasekSat, 17 Apr 2010 01:43:55 + In my bug description I said this was linked to /usr mounted on a separate volume, but this could also happen when /var is mounted on a separate volume, see LP #525154. -- statd does not start when /usr is mounted on a separate volume https://bugs.launchpad.net/bugs/567591 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 567591] Re: statd does not start when /usr is mounted on a separate volume
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/44927866/Dependencies.txt ** Description changed: On my desktop computer, (which has separate volumes for /, /usr, /var, /tmp,etc.) statd fail to start, and then autofs later fails to mount NFS volumes. - This problem does not appear on my laptop computer that only has one volume for the whole filesystem, so I think that is a race condition between statd starting and /usr mounting. Indeed, reading /etc/init/statd.conf I can see that statd is ran after portmap. Portmap can start only with / mounted, because it is located in /sbin, however statd is located in /usr and so we have to wait for /usr to be mounted. + This problem does not appear on my laptop computer that only has one volume for the whole filesystem, so I think that is a race condition between statd starting and /usr mounting. Indeed, reading /etc/init/statd.conf I can see that statd is ran after portmap. Portmap can start with only / mounted, because it is located in /sbin, however statd is located in /usr and so we have to wait for /usr to be mounted. I suggest the following fix: in /etc/init/statd.conf, replace "start on" clause (line 6) with: start on ((started portmap and local-filesystems) or mounting TYPE=nfs) (was: start on (started portmap or mounting TYPE=nfs) On my computer this fixes the issue, nevertheless I am not sure whether this will suit all cases. + Please tell me if you need more details or logs. + ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: nfs-common 1:1.2.0-4ubuntu4 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 Date: Wed Apr 21 00:52:06 2010 ProcEnviron: - LANG=fr_FR.UTF-8 - SHELL=/bin/bash + LANG=fr_FR.UTF-8 + SHELL=/bin/bash SourcePackage: nfs-utils ** Description changed: - On my desktop computer, (which has separate volumes for /, /usr, /var, /tmp,etc.) statd fail to start, and then autofs later fails to mount NFS volumes. - This problem does not appear on my laptop computer that only has one volume for the whole filesystem, so I think that is a race condition between statd starting and /usr mounting. Indeed, reading /etc/init/statd.conf I can see that statd is ran after portmap. Portmap can start with only / mounted, because it is located in /sbin, however statd is located in /usr and so we have to wait for /usr to be mounted. + On my desktop computer, (which has separate volumes for /, /usr, /var, /tmp,etc.) statd fail to start, and then autofs later fails to mount NFS v3 volumes. + This problem does not appear on my laptop computer that only has one volume for the whole filesystem, so I think that is a race condition between statd starting and /usr mounting. Indeed, reading /etc/init/statd.conf I can see that statd is ran after portmap. Portmap can start only with / mounted, because it is located in /sbin, however statd is located in /usr and so we have to wait for /usr to be mounted. I suggest the following fix: in /etc/init/statd.conf, replace "start on" clause (line 6) with: start on ((started portmap and local-filesystems) or mounting TYPE=nfs) (was: start on (started portmap or mounting TYPE=nfs) On my computer this fixes the issue, nevertheless I am not sure whether this will suit all cases. - - Please tell me if you need more details or logs. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: nfs-common 1:1.2.0-4ubuntu4 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 Date: Wed Apr 21 00:52:06 2010 ProcEnviron: LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: nfs-utils -- statd does not start when /usr is mounted on a separate volume https://bugs.launchpad.net/bugs/567591 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 567591] [NEW] statd does not start when /usr is mounted on a separate volume
Public bug reported: On my desktop computer, (which has separate volumes for /, /usr, /var, /tmp,etc.) statd fail to start, and then autofs later fails to mount NFS v3 volumes. This problem does not appear on my laptop computer that only has one volume for the whole filesystem, so I think that is a race condition between statd starting and /usr mounting. Indeed, reading /etc/init/statd.conf I can see that statd is ran after portmap. Portmap can start only with / mounted, because it is located in /sbin, however statd is located in /usr and so we have to wait for /usr to be mounted. I suggest the following fix: in /etc/init/statd.conf, replace "start on" clause (line 6) with: start on ((started portmap and local-filesystems) or mounting TYPE=nfs) (was: start on (started portmap or mounting TYPE=nfs) On my computer this fixes the issue, nevertheless I am not sure whether this will suit all cases. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: nfs-common 1:1.2.0-4ubuntu4 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 Date: Wed Apr 21 00:52:06 2010 ProcEnviron: LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: nfs-utils ** Affects: nfs-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- statd does not start when /usr is mounted on a separate volume https://bugs.launchpad.net/bugs/567591 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 543045] Re: [RV530] screen flickers in lucid lynx [Needs pll quirk]
Linux kernel version 2.6.32-20-generic fixes the problem on my computer. -- [RV530] screen flickers in lucid lynx [Needs pll quirk] https://bugs.launchpad.net/bugs/543045 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 544662] Re: [RV530] screen flickering, lucid lynx beta 1 [Needs pll quirk]
Linux kernel version 2.6.32-20-generic fixes the problem on my computer. Thanks! -- [RV530] screen flickering, lucid lynx beta 1 [Needs pll quirk] https://bugs.launchpad.net/bugs/544662 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 549709] Re: [RV515] screen flickers in lucid lynx beta1 [Needs pll quirk]
Steve, I eventually set up a new Ubuntu system using i386 architecture, and then set up http://people.canonical.com/~sconklin/test-i915/linux-image-2.6.32-18-generic_2.6.32-18.28~spcintelfixes01_i386.deb package. However the bug is still there... -- [RV515] screen flickers in lucid lynx beta1 [Needs pll quirk] https://bugs.launchpad.net/bugs/549709 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 549709] Re: [RV515] screen flickers in lucid lynx beta1 [Needs pll quirk]
Thanks Steve, nevertheless I am using amd64 architecture, so may I get either an amd64 kernel, or the source code so that I can compile it myself? (I can of course set up a new i386 system, but I think this will take more time.) -- [RV515] screen flickers in lucid lynx beta1 [Needs pll quirk] https://bugs.launchpad.net/bugs/549709 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 544662] Re: [RV530] screen flickering, lucid lynx beta 1 [Needs pll quirk]
Robert Hooker: As requested, I file a new bug. See bug report #549709 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/549709 -- [RV530] screen flickering, lucid lynx beta 1 [Needs pll quirk] https://bugs.launchpad.net/bugs/544662 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 549709] Re: [RV515] screen flickers in lucid lynx beta1 [Needs pll quirk]
** Attachment added: "AlsaDevices.txt" http://launchpadlibrarian.net/42182928/AlsaDevices.txt ** Attachment added: "AplayDevices.txt" http://launchpadlibrarian.net/42182929/AplayDevices.txt ** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/42182930/BootDmesg.txt ** Attachment added: "CRDA.txt" http://launchpadlibrarian.net/42182931/CRDA.txt ** Attachment added: "Card0.Amixer.values.txt" http://launchpadlibrarian.net/42182932/Card0.Amixer.values.txt ** Attachment added: "Card0.Codecs.codec.0.txt" http://launchpadlibrarian.net/42182933/Card0.Codecs.codec.0.txt ** Attachment added: "Card0.Codecs.codec.1.txt" http://launchpadlibrarian.net/42182934/Card0.Codecs.codec.1.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/42182935/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/42182936/Dependencies.txt ** Attachment added: "IwConfig.txt" http://launchpadlibrarian.net/42182937/IwConfig.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/42182938/Lspci.txt ** Attachment added: "Lsusb.txt" http://launchpadlibrarian.net/42182939/Lsusb.txt ** Attachment added: "PciMultimedia.txt" http://launchpadlibrarian.net/42182940/PciMultimedia.txt ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/42182941/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/42182942/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/42182943/ProcModules.txt ** Attachment added: "RfKill.txt" http://launchpadlibrarian.net/42182944/RfKill.txt ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/42182945/UdevDb.txt ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/42182946/UdevLog.txt ** Attachment added: "WifiSyslog.txt" http://launchpadlibrarian.net/42182947/WifiSyslog.txt ** Attachment added: "XsessionErrors.txt" http://launchpadlibrarian.net/42182948/XsessionErrors.txt ** Description changed: As already reported by other users in bug reports #544662 or #543045, my - laptop screen flickers. This can happen from boot time of after a few - minutes, but when it begins it stays until shutdown or reboot. + laptop screen flickers in Ubuntu Lucid Lynx beta1. This can happen at + boot time of after a few minutes, but when it begins it stays until + shutdown or reboot. As for other users, this issue is solved by passing "radeon.new_dll=0" parameter to the kernel at boot time, or by passing "new_dll=0" parameter to "radeon" kernel module. My laptop is a Dell Inspiron 6400 (aka E1505), an ATI Radeon Mobility X1400 video adapter and a 15.4" 1680x1050 panel. (See attached files for details) ProblemType: Bug Architecture: amd64 ArecordDevices: - List of CAPTURE Hardware Devices - card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] -Subdevices: 1/1 -Subdevice #0: subdevice #0 + List of CAPTURE Hardware Devices + card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] + Subdevices: 1/1 + Subdevice #0: subdevice #0 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: chips 2600 F pulseaudio - /dev/snd/pcmC0D0p: chips 2600 F...m pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: chips 2600 F pulseaudio + /dev/snd/pcmC0D0p: chips 2600 F...m pulseaudio Card0.Amixer.info: - Card hw:0 'Intel'/'HDA Intel at 0xefffc000 irq 21' -Mixer name : 'SigmaTel STAC9200' -Components : 'HDA:83847690,102801bd,00102201 HDA:14f12bfa,14f100c3,0009' -Controls : 12 -Simple ctrls : 7 + Card hw:0 'Intel'/'HDA Intel at 0xefffc000 irq 21' + Mixer name : 'SigmaTel STAC9200' + Components : 'HDA:83847690,102801bd,00102201 HDA:14f12bfa,14f100c3,0009' + Controls : 12 + Simple ctrls : 7 Date: Sat Mar 27 18:06:44 2010 DistroRelease: Ubuntu 9.10 HibernationDevice: RESUME=UUID=52820742-c7bd-44f1-b01e-188b0519db8d MachineType: Dell Inc. MM061 Package: linux-image-2.6.32-17-generic 2.6.32-17.26 ProcCmdLine: root=UUID=5ddd3dbc-62a3-40df-8de4-9f2d4e5296d1 ro quiet splash locale=fr_FR ProcEnviron: - LANGUAGE=fr_FR.UTF-8 - LANG=fr_FR.UTF-8 - SHELL=/bin/bash + LANGUAGE=fr_FR.UTF-8 + LANG=fr_FR.UTF-8 + SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 RelatedPackageVersions: linux-firmware 1.26 SourcePackage: linux Uname: Linux 2.6.32-17-generic x86_64 WpaSupplicantLog: - + dmi.bios.date: 06/13/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XD720 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: MM061 dmi.sys.vendor
[Bug 549709] [NEW] [RV515] screen flickers in lucid lynx beta1 [Needs pll quirk]
Public bug reported: As already reported by other users in bug reports #544662 or #543045, my laptop screen flickers in Ubuntu Lucid Lynx beta1. This can happen at boot time of after a few minutes, but when it begins it stays until shutdown or reboot. As for other users, this issue is solved by passing "radeon.new_dll=0" parameter to the kernel at boot time, or by passing "new_dll=0" parameter to "radeon" kernel module. My laptop is a Dell Inspiron 6400 (aka E1505), an ATI Radeon Mobility X1400 video adapter and a 15.4" 1680x1050 panel. (See attached files for details) ProblemType: Bug Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chips 2600 F pulseaudio /dev/snd/pcmC0D0p: chips 2600 F...m pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xefffc000 irq 21' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:83847690,102801bd,00102201 HDA:14f12bfa,14f100c3,0009' Controls : 12 Simple ctrls : 7 Date: Sat Mar 27 18:06:44 2010 DistroRelease: Ubuntu 9.10 HibernationDevice: RESUME=UUID=52820742-c7bd-44f1-b01e-188b0519db8d MachineType: Dell Inc. MM061 Package: linux-image-2.6.32-17-generic 2.6.32-17.26 ProcCmdLine: root=UUID=5ddd3dbc-62a3-40df-8de4-9f2d4e5296d1 ro quiet splash locale=fr_FR ProcEnviron: LANGUAGE=fr_FR.UTF-8 LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 RelatedPackageVersions: linux-firmware 1.26 SourcePackage: linux Uname: Linux 2.6.32-17-generic x86_64 WpaSupplicantLog: dmi.bios.date: 06/13/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XD720 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: MM061 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid needs-pll-quirk -- [RV515] screen flickers in lucid lynx beta1 [Needs pll quirk] https://bugs.launchpad.net/bugs/549709 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 544662] Re: [RV530] screen flickering, lucid lynx beta 1 [Needs pll quirk]
I am affected by this problem too, but with an ATI Radeon Mobility X1400 (RV515). Adding radeon.new_pll=0 to the kernel command line solves the issue (or passing new_pll=0 to the "radeon" kernel module). Please tell me if you need more details, or if I need to make a separate bug report. See attached lspci.txt ** Attachment added: "lspci -vvnn" http://launchpadlibrarian.net/42180630/lspci.txt -- [RV530] screen flickering, lucid lynx beta 1 [Needs pll quirk] https://bugs.launchpad.net/bugs/544662 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
