All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13286] New: The system hangs in vmware workstation on the line clocksource switched to clocksource tsc
Date: Tue, 27 Oct 2020 05:56:48 +0000	[thread overview]
Message-ID: <bug-13286-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=13286

            Bug ID: 13286
           Summary: The system hangs in vmware workstation on the line
                    clocksource switched to clocksource tsc
           Product: buildroot
           Version: 2020.02.7
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: batman82 at list.ru
                CC: buildroot at uclibc.org
  Target Milestone: ---

Build a system with default parameters for the platform x86.
Made img and iso images.

If run iso in the vmware workstation 15-16 everything is working.
If rub img in the vmware workstation 15-16 system hangs on the line
"clocksource: switched to clocksource tsc"

In the virtualbox no such problem.

See screenshots here https://yadi.sk/d/vucprOsF5M0tDQ?w=1

How to fix?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2020-10-27  5:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-27  5:56 bugzilla at busybox.net [this message]
2020-10-27  6:09 ` [Buildroot] [Bug 13286] The system hangs in vmware workstation on the line clocksource switched to clocksource tsc bugzilla at busybox.net
2020-10-27  9:40 ` bugzilla at busybox.net

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-13286-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.