Opened 12 years ago
Closed 12 years ago
#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 (3)
Change History (9)
by , 12 years ago
| Attachment: | mythbackend-crash_at_boot.txt added |
|---|
comment:1 by , 12 years ago
Looks like might be related to closed (no response) ticket: https://www.virtualbox.org/ticket/10697
follow-up: 3 comment:2 by , 12 years ago
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 by , 12 years ago
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.
by , 12 years ago
| Attachment: | touch.strace added |
|---|
comment:4 by , 12 years ago
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.
comment:5 by , 12 years ago
Just attempted to move from virtualbox version 4.0.16 to 4.2.4 using the same guest host and I can confirm that this causes the problem to occur. In other words, there is something in 4.2.4 (most likely the guest additions) that causes this.
comment:6 by , 12 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Please continue the discussion in #11390.
kern.log showing trace