>>
>>
>>
>> Commands line options:
> rd.debug rd.udev.debug systems.log_level=debug
>
> That willl be incredibly verbose, and slows things down a lot, so in the
> off chance there's a race, you might get different results. But if not,
> the
> log should contain something useful.
>
> I like the
>
>
>
> Commands line options:
rd.debug rd.udev.debug systems.log_level=debug
That willl be incredibly verbose, and slows things down a lot, so in the
off chance there's a race, you might get different results. But if not, the
log should contain something useful.
I like the hypothesis about
On 12/4/18 11:03 PM, Nicolas Kovacs wrote:
I could manage to switch to another virtual console, and I have the
following kernel log messages:
WARNING: kernel:perf: interrupt took too long
Can you run "dmesg" and find out if there's any more info? Often there
will be a kernel stack trace
On Wed, 5 Dec 2018 at 02:02, Nicolas Kovacs wrote:
>
> Hi,
>
> I just updated my installation media for CentOS. I have a few sandbox
> PCs in my office, and I'm testing CentOS 7.6 1810 on them. There seem to
> be a few issues with the CentOS 7.6 1810 DVD.
>
> Checked DVD integrity on startup :
Hi,
I just updated my installation media for CentOS. I have a few sandbox
PCs in my office, and I'm testing CentOS 7.6 1810 on them. There seem to
be a few issues with the CentOS 7.6 1810 DVD.
Checked DVD integrity on startup : OK.
First attempt : installer froze on root password dialog.
5 matches
Mail list logo
