Re: lockd: cannot unmonitor

[VSJ]

VSJ wrote:

> # CONFIG_APM_REAL_MODE_POWER_OFF is not set

I've set this to 'yes' and now the PC shuts down completely on 'halt', the
problem has been fixed!

Stanley


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: lockd: cannot unmonitor

[VSJ]

Hi Bernd,

it's not a diskless client (only the Home directories and an MP3/Video share
are mounted from the server).

Your suggestion to remove the -i flag seems to work partially: the lockd
errors are gone, but the computer still doesn't power off after printing
the Power Down line to the screen, and the "portmap: server localhost not
responding, timed out" still show up after a long interval.

I'm now going to rebuild the kernel and change some APM/ACPI related
settings. By the way, the computer is an IBM 300 GL  6563-VCG:


(I have included the relevant parts of the current kernel .config below)

Thanks for your help,
Stanley.

Bernd Schubert wrote:

> Hello Stanley,
> 
> yeah we know this problem. Is it a diskless nfs-client?
> Just edit the /etc/init.d/halt script, at the end there should be the line
> 
> halt -d -f -i $poweroff $hddown
> 
> The "-i" option makes all network interfaces to be shutdown, but this
> seems to be too early for diskless clients, just try to remove this
> option, so
> 
> halt -d -f $poweroff $hddown
> 
> 
> If it works we should send a bug report.
> 
> Cheers,
>  Bernd


#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
# CONFIG_SBUS is not set
CONFIG_UID16=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODVERSIONS=y
CONFIG_KMOD=y

#
# Processor type and features
#
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
CONFIG_MPENTIUMIII=y
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MELAN is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_X86_HAS_TSC=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_PGE=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_F00F_WORKS_OK=y
CONFIG_X86_MCE=y
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
# CONFIG_EDD is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_HIGHMEM is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_BIGPHYS_AREA is not set
# CONFIG_SMP is not set
# CONFIG_X86_UP_APIC is not set
# CONFIG_X86_UP_IOAPIC is not set
# CONFIG_X86_TSC_DISABLE is not set
CONFIG_X86_TSC=y

#
# General setup
#
CONFIG_NET=y
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
# CONFIG_ISA is not set
CONFIG_PCI_NAMES=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
# CONFIG_HOTPLUG is not set
# CONFIG_PCMCIA is not set
# CONFIG_HOTPLUG_PCI is not set
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
CONFIG_KCORE_ELF=y
# CONFIG_KCORE_AOUT is not set
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_MISC is not set
# CONFIG_OOM_KILLER is not set
CONFIG_PM=y
CONFIG_APM=y
# CONFIG_APM_IGNORE_USER_SUSPEND is not set
CONFIG_APM_DO_ENABLE=y
CONFIG_APM_CPU_IDLE=y
CONFIG_APM_DISPLAY_BLANK=y
CONFIG_APM_RTC_IS_GMT=y
# CONFIG_APM_ALLOW_INTS is not set
# CONFIG_APM_REAL_MODE_POWER_OFF is not set

#
# ACPI Support
#
CONFIG_ACPI=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_BUS=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_MMCONFIG=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SYSTEM=y
# CONFIG_ACPI_OFF is not set
# CONFIG_ACPI_AC is not set
# CONFIG_ACPI_BATTERY is not set
CONFIG_ACPI_BUTTON=y
# CONFIG_ACPI_FAN is not set
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_TOSHIBA is not set
# CONFIG_ACPI_DEBUG is not set
# CONFIG_OPTIMISE_SIZE is not set


#
# Plug and Play configuration
#
CONFIG_PNP=y
CONFIG_ISAPNP=y

#
# Network File Systems
#
# CONFIG_CODA_FS is not set
# CONFIG_INTERMEZZO_FS is not set
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_NFS_DIRECTIO is not set
# CONFIG_ROOT_NFS is not set
# CONFIG_NFSD is not set
# CONFIG_NFSD_V3 is not set
# CONFIG_NFSD_TCP is not set
CONFIG_SUNRPC=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
# CONFIG_SMB_FS is not set
# CONFIG_NCP_FS is not set
# CONFIG_NCPFS_PACKET_SIGNING is not set
# CONFIG_NCPFS_IOCTL_LOCKING is not set
# CONFIG_NCPFS_STRONG is not set
# CONFIG_NCPFS_NFS_NS is not set
# CONFIG_NCPFS_OS2_NS is not set
# CONFIG_NCPFS_SMALLDOS is not set
# CONFIG_NCPFS_NLS is not set
# CONFIG_NCPFS_EXTRAS is not set
# CONFIG_ZISOFS_FS is not set
CONFIG_FS_MBCACHE=y
# CONFIG_FS_POSIX_ACL is

Re: lockd: cannot unmonitor

[Bernd Schubert]

> 
> 1 lockd_down: lockd failed to exit, clearing pid
> 2 flushing ide devices: hda hdc
> 3 Power down.
> 4 lockd: cannot unmonitor 192.168.1.1
> 5 portmap: server localhost not responding, timed out
> 

[snip]

> Does anyone know how I can fix this problem?
> 
> Thanks in advance,
> Stanley.
> PS: if you need more info, let me know.
> 
> 

Hello Stanley,

yeah we know this problem. Is it a diskless nfs-client? 
Just edit the /etc/init.d/halt script, at the end there should be the line

halt -d -f -i $poweroff $hddown

The "-i" option makes all network interfaces to be shutdown, but this seems
to be too early for diskless clients, just try to remove this option, so

halt -d -f $poweroff $hddown


If it works we should send a bug report.

Cheers,
 Bernd


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

lockd: cannot unmonitor

[VSJ]

Hi,

I've an NFS client running an up-to-date Debian sid, kernel 2.4.27 (not
vanilla, but supplied by Debian).

If someone tries to shut down this machine, the machine doesn't power-off!

These are the last fews messages printed to the console:

1 lockd_down: lockd failed to exit, clearing pid
2 flushing ide devices: hda hdc
3 Power down.
4 lockd: cannot unmonitor 192.168.1.1
5 portmap: server localhost not responding, timed out

I've added line numbers, so I can comment on each line:
at 3, Power down, the harddisk is being turned off (I can hear that), but
the rest of the computer stays on. After a few seconds, message 4 appears.
Than after a (few) minutes, message 5 appears. This message keeps repeating
itself after a certain interval. 
This all happens after the local filesystem is unmounted, so there are no
useful logfile entries.

The host 192.168.1.1 is the NFS server. It is running Debian woody with
kernel 2.4.27.
Log files (messages, user.log, syslog) from the server show the following:
Oct  8 17:17:21 P1 rpc.mountd: authenticated unmount request from P4:682
for /var/share (/var/share)
Oct  8 17:17:21 P1 rpc.mountd: authenticated unmount request from P4:684
for /home (/home)


(the server's name is P1, the client's name is P4)

My own computer is running an up-to-date Debian sid, too, but doesn't suffer
from this shut-down problem. The only difference is that I'm running kernel
2.6.7, not 2.4.27.

Does anyone know how I can fix this problem?

Thanks in advance,
Stanley.
PS: if you need more info, let me know.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]