Bug#1036773: cloud.debian.org: During vagrant up, mounting NFS fails

2023-05-25 Thread Joshua Kugler 
Package: cloud.debian.org
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
I tried to use the debian/testing64 vagrant box.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I ran `vagrant up`. It mostly runs, but hangs on ==> default: Mounting 
NFS shared folders...
After sitting there 

   * What was the outcome of this action?

It mostly runs, but hangs on ==> default: Mounting NFS shared folders...
After sitting there for a while, it fails with:

The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mount -o vers=4 192.168.121.1:/home/jkugler/vmware/vagrant_debian 
/vagrant

Stdout from the command:


Stderr from the command:

mount.nfs: Connection refused


   * What outcome did you expect instead?

I expected the machine to come up without issue.

I noticed in the default Vagrantfile that comes with the box, there is 
an NFS shared folder.
That should probably be removed and allow the user to configure shared 
folders as they see fit.

Bug#386226: linux-image-2.6.16-2-686-smp: Will not set clock and loses interrupts when rtc is used

2006-09-05 Thread Joshua Kugler 
Package: linux-image-2.6.16-2-686-smp
Version: 2.6.16-18
Severity: important

During boot on my Etch machine (Dell PowerEdge 830 with an Intel Pentium D CPU 
2.80GHz, kernel 2.6.16-2-686-smp), there is a message about select() timing out 
on /dev/rtc.  That message displays twice, a few more messages, then there is a 
message about trying to set the system clock again.  I've looked through the 
syslog and dmesg, and these messages are not in there.  Or else I'd post the 
exact messages. :)

Ah, a google search found the exact message for me:
select to /dev/rtc to wait for clock tick timed out

But no solution.

That leads to this:  When I start up VMWare server, I start getting these 
messages in the syslog:

Sep 2 06:25:13 hostname kernel: rtc: lost some interrupts at 512Hz. 
Sep 2 06:25:44 hostname last message repeated 1521 times 
Sep 2 06:26:45 hostname last message repeated 3050 times 
Sep 2 06:27:46 hostname last message repeated 3050 times 
Sep 2 06:28:47 hostname last message repeated 3049 times 
Sep 2 06:29:48 hostname last message repeated 3050 times 
Sep 2 06:30:49 hostname last message repeated 3050 times 
Sep 2 06:31:50 hostname last message repeated 3050 times 
Sep 2 06:32:51 hostname last message repeated 3050 times 
Sep 2 06:33:52 hostname last message repeated 3050 times 
Sep 2 06:34:53 hostname last message repeated 3050 times 
Sep 2 06:35:54 hostname last message repeated 3049 times 
Sep 2 06:36:55 hostname last message repeated 3050 times 
Sep 2 06:37:56 hostname last message repeated 3049 times 
Sep 2 06:38:57 hostname last message repeated 3049 times 
Sep 2 06:39:58 hostname last message repeated 3050 times 
Sep 2 06:40:59 hostname last message repeated 3050 times 
Sep 2 06:42:00 hostname last message repeated 3050 times 
Sep 2 06:43:01 hostname last message repeated 3050 times 
Sep 2 06:44:02 hostname last message repeated 3050 times 

/proc/interrupts shows:

CPU0 CPU1
 0: 3613286 0 IO-APIC-edge timer
 1: 12 0 IO-APIC-edge i8042
 8: 0 0 IO-APIC-edge rtc
 9: 1 0 IO-APIC-level acpi
 12: 113 0 IO-APIC-edge i8042
 14: 65 0 IO-APIC-edge ide0
 50: 59827 0 IO-APIC-level libata, uhci_hcd:usb1, ehci_hcd:usb4
169: 56297 0 IO-APIC-level eth0
177: 0 0 IO-APIC-level uhci_hcd:usb2
185: 0 0 IO-APIC-level uhci_hcd:usb3
NMI: 0 0
LOC: 3613227 3613226
ERR: 0
MIS: 0

Since VMWare is the only app at the moment that uses the RTC, during its 
execution is the only time I get those error messages.

Someone on the VMWare Forum suggested adding 'nohpet' to the kernel boot 
parameters, but that did not fix anything.

In another bug report (#283524) Laurent Bonnaud suggested trying the genrtc 
module, but putting that in modules conf in place of rtc did not seem to fix 
anything.

I also tried acpi=no on the kernel boot command line.

So far, nothing has helped.

More background here: 
http://www.vmware.com/community/thread.jspa?threadID=53727tstart=50

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-686-smp
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages linux-image-2.6.16-2-686-smp depends on:
ii  initramfs-tools [linux-initra 0.77b  tools for generating an initramfs
ii  module-init-tools 3.2.2-3tools for managing Linux kernel mo

Versions of packages linux-image-2.6.16-2-686-smp recommends:
pn  libc6-i686none (no description available)

-- debconf information:
  linux-image-2.6.16-2-686-smp/preinst/lilo-initrd-2.6.16-2-686-smp: true
  linux-image-2.6.16-2-686-smp/preinst/elilo-initrd-2.6.16-2-686-smp: true
  linux-image-2.6.16-2-686-smp/postinst/bootloader-error-2.6.16-2-686-smp:
  linux-image-2.6.16-2-686-smp/postinst/really-run-bootloader-2.6.16-2-686-smp: 
true
  linux-image-2.6.16-2-686-smp/postinst/old-initrd-link-2.6.16-2-686-smp: true
  linux-image-2.6.16-2-686-smp/preinst/initrd-2.6.16-2-686-smp:
  linux-image-2.6.16-2-686-smp/postinst/kimage-is-a-directory:
  linux-image-2.6.16-2-686-smp/preinst/failed-to-move-modules-2.6.16-2-686-smp:
  linux-image-2.6.16-2-686-smp/preinst/abort-overwrite-2.6.16-2-686-smp:
  linux-image-2.6.16-2-686-smp/postinst/depmod-error-2.6.16-2-686-smp: false
  linux-image-2.6.16-2-686-smp/preinst/overwriting-modules-2.6.16-2-686-smp: 
true
  
linux-image-2.6.16-2-686-smp/prerm/would-invalidate-boot-loader-2.6.16-2-686-smp:
 true
  linux-image-2.6.16-2-686-smp/postinst/old-dir-initrd-link-2.6.16-2-686-smp: 
true
* linux-image-2.6.16-2-686-smp/preinst/already-running-this-2.6.16-2-686-smp:
  linux-image-2.6.16-2-686-smp/prerm/removing-running-kernel-2.6.16-2-686-smp: 
true
  linux-image-2.6.16-2-686-smp/postinst/depmod-error-initrd-2.6.16-2-686-smp: 
false
  linux-image-2.6.16-2-686-smp/postinst/bootloader-test-error-2.6.16-2-686-smp:
  linux-image-2.6.16-2-686-smp/preinst/bootloader-initrd-2.6.16-2-686-smp: true