Ticket #11148 (closed defect: duplicate)
Warning: dcache.c d_set_d_op at boot
| Reported by: | socalbob | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 4.2.4 |
| Keywords: | dcache d_set_d_op | Cc: | |
| Guest type: | Linux | Host type: | Windows |
Description
Whenever I boot my ubuntu-12.10 guest VM on my Win7-64bit host I get this error message in the kern.log file:
WARNING: at /build/buildd/linux-3.5.0/fs/dcache.c:1375 d_set_d_op+0x7c/0xb0()
There are some stability issues (hangs seg faults, etc) and I think it might be related to this problem.
Attachments
-
mythbackend-crash_at_boot.txt
(11.7 KB) -
added by socalbob 10 years ago.
- kern.log showing trace
-
VBox.log
(65.8 KB) -
added by socalbob 10 years ago.
- vbox.log
-
touch.strace
(4.5 KB) -
added by gipsy 10 years ago.
Change History
Changed 10 years ago by socalbob
-
attachment
mythbackend-crash_at_boot.txt
added
comment:1 Changed 10 years ago by socalbob
Looks like might be related to closed (no response) ticket: https://www.virtualbox.org/ticket/10697
comment:2 follow-up: ↓ 3 Changed 10 years ago by gipsy
I can confirm this bug with the following equipment.
Host: Thinkpad T61
Host OS: Ubuntu 11.10 (64Bit)
VirtualBox Version 4.2.4 (64Bit)
Guest: Xubuntu 12.10 (64Bit)
Guest Extensions installed: yes
The error entry in the dmesg of the guest does not show up immediately after booting and logging in but after a while (between 5 and 25 minutes working within the guest).
comment:3 in reply to: ↑ 2 Changed 10 years ago by gipsy
Replying to gipsy:
I can confirm this bug with the following equipment.
Host: Thinkpad T61
Host OS: Ubuntu 11.10 (64Bit)
VirtualBox Version 4.2.4 (64Bit)
Guest: Xubuntu 12.10 (64Bit)
Guest Extensions installed: yesThe error entry in the dmesg of the guest does not show up immediately after booting and logging in but after a while (between 5 and 25 minutes working within the guest).
I my case I can further narrow it down to that it happens in the moment there's a write access to a new (!) file on a shared folder (A simple touch was sufficent to trigger the crash). An strace is shown below
However the file was successfully created but once the error has been triggered the VM slows down significantly.
comment:4 Changed 10 years ago by socalbob
FYI, I downgraded virtualbox to version 4.0.16 and installed the 32-bit version of ubuntu-12.04.1 and the problem went away - i.e. I no longer get the warning and my system is much more stable. Not sure if it is an issue with the 64-bit guest or the version of virtualbox.
kern.log showing trace