|
Bugzilla – Full Text Bug Listing |
| Summary: | Powersave problem with nfs-client | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | t. f. <corax2.05> |
| Component: | Basesystem | Assignee: | Holger Macht <hmacht> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | coolo, postadal |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | SuSE Linux 10.0 | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
last 300 lines of /var/log/messages (i686)
/var/log/yast2 (i686) /etc/fstab (i686) |
||
|
Description
t. f.
2006-02-08 18:35:42 UTC
Is the second issue a result from the failure of powersaved? If not, please open a seperate report about this. Give more information about the configuration (aka the steps you have done to provoke this). Furthermore, add 300 lines of your syslog in /var/log/messages. Created attachment 67408 [details]
last 300 lines of /var/log/messages (i686)
yes it is a result of the powersaved failur. the systems are standard installations. i didn't any special to get this result. the nfs-client was created with yast. here nothing special too, the options are "defaults". In that case, please attach the Yast logfiles (/var/log/YaST2) and /etc/fstab. Are you sure the problem is due to the creation of the nfs-mount? I cannot really see a connection here. What makes you so sure the failure of powerd is caused by shutting down your local NFS server (which would also have no influence on your local mounts) - are you mounting a local NFS share? ok, i try to explain this... there are 3 pc's, connected with a hardwarerouter. 1. i686 (suse10) 2. x86_64 (suse10) 3. i586 (linVDR) linVDR and x86_64 run a nfs-server. x86_64 run a nfs-client connected to linVDR. i686 run a nfs-client connected to x86_64. if i boot the x86_64 without a running linVDR, i get the powersaved message. same if i boot the i686 without a running x86_64. with running servers there are absolutly no problems. and without running nfs-clients there are no problems too. this is, what make me sure, it has something to do with nfs. maybe it is only a symptom for another issue, i don't know. btw: the issue with the USB-stick is not the only one. this means, if i plug an USB-stick in, i got no messagewindow "USB-stick found". the same (i asserted yesterday) with cd's. if i put a disc in the drive, there's no messagewindow. Created attachment 68177 [details]
/var/log/yast2 (i686)
Created attachment 68178 [details]
/etc/fstab (i686)
Reassigning to Thomas... Hmmm, I expect it is this requirement in /etc/init.d/powersave: # Required-Start: $remote_fs dbus haldaemon This was already discussed some time ago on research, I really would like to get rid of the remote_fs stuff... What I expect is going on: nfsclient starts and tries to import fs shares, these cannot be imported and it hangs until timeout... During that time X and KDE already came up (shouldn't they also wait for nfs?!?) Kpowersave reports: no running powersave daemon... NFS client times out then dbus and powersave daemon are going to be started ... Maybe we should add an KDE/X guy and ask him why those services are started before..., Coolo? *** This bug has been marked as a duplicate of 121965 *** |