[opensuse] boot hang-ups
Hello List , - just wondering - anyone ever met probs like : " Switched to clocksource tsc " and " Random: nonblocking pool is initialized" ??? ........ regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/02/2015 02:20 PM, ellanios82 wrote:
Hello List ,
- just wondering - anyone ever met probs like :
" Switched to clocksource tsc " and
That should not be a impediment. "tsc" is a valid clock source. $ cat /sys/devices/system/clocksource/clocksource0/current_clocksource tsc and $ cat /sys/devices/system/clocksource/clocksource0/available_clocksource tsc hpet acpi_pm I have $ dmesg | grep tsc [ 0.000000] tsc: Fast TSC calibration using PIT [ 0.000000] tsc: Detected 2394.085 MHz processor [ 1.881025] tsc: Refined TSC clocksource calibration: 2393.985 MHz [ 1.881114] clocksource tsc: mask: 0xffffffffffffffff max_cycles: 0x22820552d36, max_idle_ns: 440795305269 ns [ 2.886231] Switched to clocksource tsc
Random: nonblocking pool is initialized"
Again that should not be an impediment. The nonblocking pool is /dev/urandom RTFM I have $ dmesg | grep random [ 2.959736] random: vgchange urandom read with 83 bits of entropy available [ 3.127355] random: nonblocking pool is initialized These are not problems. If you have a problem booting these are not the issues. OBTW: you could google and find the answers I've just given you. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/02/2015 02:20 PM, ellanios82 wrote:
Hello List ,
- just wondering - anyone ever met probs like :
" Switched to clocksource tsc " and " Random: nonblocking pool is initialized"
Should also ask: What system and what kernel are you installing? What hardware do you have and what changes have been made to it since it was last working with Linux, and what version of Linux was that and when? -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/02/2015 09:20 PM, ellanios82 wrote:
Hello List ,
- just wondering - anyone ever met probs like :
" Switched to clocksource tsc " and " Random: nonblocking pool is initialized"
??? ........
- out of the blue , lightening struck , after at least a week of no hardware or software changes : suspicion . . . could this be a snarky DRACUT bug ?? { ok ok feel free to shout : TW belongs to factory } ................ regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
- just wondering - anyone ever met probs like :
" Switched to clocksource tsc " and " Random: nonblocking pool is initialized"
??? ........
- out of the blue , lightening struck , after at least a week of no hardware or software changes : suspicion . . . could this be a snarky DRACUT bug ?? ..................
did have a google search . . . no solution found . . . only mention of these 2 probs that i was able to find was by Roger Oberholtzer of Ramboll Systems , Sweden .......................... regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/02/2015 02:49 PM, ellanios82 wrote:
- out of the blue , lightening struck , after at least a week of no hardware or software changes : suspicion . . . could this be a snarky DRACUT bug ??
I could be but why? if it booted before and nothing changed then why wouldn't it boot now if nothing has changed? Nothing has changed, except the ability to boot. If it was the dracut bug but nothing has changed, or more specifically dracut has not been run to build a new initrd since the last boot then how can it be the dracut bug? Maybe you had a power surge and you CPU is half fried or your RAM is wonky. Maybe its old hardware and your capacitors are dying. I asked what the hardware was. What is it? And I mean ALL the hardware, ... how its plugged in to power source, how its networked, Where your lightening arrestors are. ANYTHING at all that could have effected a change. *A*N*Y*T*H*I*N*G* -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/02/2015 02:03 PM, Anton Aylward wrote:
I asked what the hardware was. What is it? And I mean ALL the hardware, ... how its plugged in to power source, how its networked, Where your lightening arrestors are.
Joining late, so forgive me if I and redundant.... What about a Live boot CD/DVD? Why go to the trouble to document in detail hardware if a simple Live CD works? What is the chance knowing the hardware would lead immediately to a solution without an extensive dive into your Closet of Anxieties for a mad bit of testing? Simple tests first I always say. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/03/2015 12:08 AM, John Andersen wrote:
What about a Live boot CD/DVD? Why go to the trouble to document in detail hardware if a simple Live CD works?
What is the chance knowing the hardware would lead immediately to a solution without an extensive dive into your Closet of Anxieties for a mad bit of testing?
Simple tests first I always say. ...................
- thanks : openSuSE Live USB-stick works a charm :) - next i re-installed from a TW iso : presently all ok [ also saw some Ubuntu users had probs with clocksource tsc but did not see the solution ] ................ regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/02/2015 02:20 PM, ellanios82 wrote:
Hello List ,
- just wondering - anyone ever met probs like :
" Switched to clocksource tsc " and " Random: nonblocking pool is initialized"
In all probability neither of those are the problem. I would think that the kernel did those and reported success. It was what followed that is the problem. On my machine the sequence is <quote> [ 2.886231] Switched to clocksource tsc [ 2.886273] microcode: CPU3 sig=0x6fb, pf=0x10, revision=0xb3 [ 2.890005] microcode: CPU3 updated to revision 0xba, date = 2010-10-03 [ 2.950829] md: linear personality registered for level -1 [ 2.959736] random: vgchange urandom read with 83 bits of entropy available [ 3.059063] usb 3-2.1: new full-speed USB device number 4 using uhci_hcd [ 3.127355] random: nonblocking pool is initialized [ 3.197052] usb 3-2.1: New USB device found, idVendor=04b3, idProduct=301b [ 3.197101] usb 3-2.1: New USB device strings: Mfr=1, Product=3, SerialNumber=0 [ 3.197148] usb 3-2.1: Product: USB Productivity Option Keyboard( has the hub in # 1 ) [ 3.197198] usb 3-2.1: Manufacturer: Lite-On Technology [ 3.207564] input: Lite-On Technology USB Productivity Option Keyboard( has the hub in # 1 ) as /devices/pci0000:00/0000:00 :1a.0/usb3/3-2/3-2.1/3-2.1:1.0/0003:04B3:301B.0002/input/input6 [ 3.258182] hid-generic 0003:04B3:301B.0002: input,hidraw1: USB HID v1.10 Keyboard [Lite-On Technology USB Productivity Opt ion Keyboard( has the hub in # 1 )] on usb-0000:00:1a.0-2.1/input0 [ 3.264139] input: Lite-On Technology USB Productivity Option Keyboard( has the hub in # 1 ) as /devices/pci0000:00/0000:00 :1a.0/usb3/3-2/3-2.1/3-2.1:1.1/0003:04B3:301B.0003/input/input7 [ 3.315151] hid-generic 0003:04B3:301B.0003: input,hidraw2: USB HID v1.10 Device [Lite-On Technology USB Productivity Optio n Keyboard( has the hub in # 1 )] on usb-0000:00:1a.0-2.1/input1 [ 6.448850] xor: measuring software checksum speed [ 6.458003] prefetch64-sse: 9736.000 MB/sec [ 6.468002] generic_sse: 8624.000 MB/sec [ 6.468023] xor: using function: prefetch64-sse (9736.000 MB/sec) [ 6.485004] raid6: sse2x1 gen() 4015 MB/s [ 6.502005] raid6: sse2x1 xor() 3957 MB/s [ 6.519009] raid6: sse2x2 gen() 5812 MB/s [ 6.536005] raid6: sse2x2 xor() 4884 MB/s [ 6.553009] raid6: sse2x4 gen() 7164 MB/s [ 6.570003] raid6: sse2x4 xor() 5445 MB/s [ 6.570024] raid6: using algorithm sse2x4 gen() 7164 MB/s [ 6.570048] raid6: .... xor() 5445 MB/s, rmw enabled [ 6.570070] raid6: using ssse3x2 recovery algorithm [ 6.575274] Btrfs loaded, assert=on [ 6.591780] BTRFS: device label ROOT devid 1 transid 709391 /dev/mapper/vgmain-vROOT </quote> There's the "tsc" followed at 3.127355 by the urandom What comes next? in my case its USB specific stuff 'cos I have a USB keyboard and mouse and the keyboard is also a USB controller in its own right. Skip all that if you don't, like me, have the USB keyboard, and we get into some CPU specific stuff that may not be seen on other architectures since its specific to my CPU and configuration, then we get to the part where the root device is accessed. Now I've had problems here before. Sometimes I've had GRUB or GRUB2 not find the root device. Sometimes I've had LVM not initialise properly. Once a kernel got built without the device mapper module. But again, that's specific to my configuration. There are many other things that might go wrong up to and including a lost file system. BtrFS makes that all the more likely, doesn't it? We've also got a thread going on where the root device is hard-coded as a UUID in the initrd. OUCH! Note that on my system it says "Btrfs loaded, assert=on". That is a past tense. It is AFTER the BtrFS ROOTFS is loaded. If the load did not occur, if the system hung trying to the load, -- I know that from experience! -- then you would not see that message. You would see the "Switched to clocksource tsc" and the "Random: nonblocking pool is initialized" messages though. That's my reasoning for it having nothing to do with either of those. More to the point. It also means that a LiveCD/LiveUSB boot will succeed. How could this have come about? Its back to my assertion that _something_ *DID* change. Probably something rebuilt the initrd in some anomalous manner. We're seeing mention of dracut doing that. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
Anton Aylward -
ellanios82 -
John Andersen