Siduction Forum

Siduction Forum => Upgrade Warnings (DE / EN) => Topic started by: Xaver on 2018/09/27, 19:01:49

Title: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: Xaver on 2018/09/27, 19:01:49

On my system linux-image-4.18.10-towo.2-siduction-amd64 is the first siduction kernel, which causes problems.
[Notebook AsusPro B400VC – CPU: Dual Core Intel Core i5-3317U (-MT MCP-) – speed/min/max: 1489/800/2600 MHz]

Last line of the boot process:
Quote
[  195.590687] NET: Registered Protocol family 5

No problems with kernels 4.18.10-towo.1 and 4.18.9-towo.1
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: absolut on 2018/09/27, 19:43:40
please paste whole boot log, i am not sure one line will help
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: Xaver on 2018/09/27, 21:13:55
@ absolut
Posting the whole boot log does not work
Quote
The following error or errors occurred while posting this message:
The message exceeds the maximum allowed length (20000 characters).

So which part do you need?
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: absolut on 2018/09/27, 22:02:07
please use a pastebin for the whole log and provide the url -> https://paste.debian.net/
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: Xaver on 2018/09/27, 23:12:55
Same problem at paste.debian.net:
Quote
Request Entity Too Large
The requested resource
/
does not allow request data with POST requests, or the amount of data provided in the request exceeds the capacity limit.
Apache/2.4.25 (Debian) Server at paste.debian.net Port 443
P.S.:  I wonder if this is worth the effort. All the other kernels did work. Most likely the next kernel will be fine again.
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: DeepDayze on 2018/09/28, 03:30:56
Why not paste the last several lines into Pastebin? That will show the backtrace and other error messages
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: Xaver on 2018/09/28, 10:26:12
OK: Next try.
I have copied the lines with 'failed' in it (with about 5 lines ahead and past).
At the end the last 100 lines of kernel.log

Code: [Select]
Sep 27 20:53:05 b400vc kernel: [    0.081288] ACPI: 9 ACPI AML tables successfully acquired and loaded
Sep 27 20:53:05 b400vc kernel: [    0.204136] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
Sep 27 20:53:05 b400vc kernel: [    0.204634] ACPI Error: Needed type [Reference], found [Integer] (____ptrval____) (20180531/exresop-69)
Sep 27 20:53:05 b400vc kernel: [    0.204645] ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20180531/dswexec-427)
Sep 27 20:53:05 b400vc kernel: [    0.204653] ACPI Error: Method parse/execution failed \_PR.CPU0._PDC, AE_AML_OPERAND_TYPE (20180531/psparse-516)
Sep 27 20:53:05 b400vc kernel: [    0.205019] ACPI: Dynamic OEM Table Load:
Sep 27 20:53:05 b400vc kernel: [    0.205028] ACPI: SSDT 0xFFFF9B5C1F17F800 000303 (v01 PmRef  ApIst    00003000 INTL 20051117)

Code: [Select]
Sep 27 20:53:05 b400vc kernel: [    1.346543] random: udevd: uninitialized urandom read (16 bytes read)
Sep 27 20:53:05 b400vc kernel: [    1.349085] fjes: module verification failed: signature and/or required key missing - tainting kernel
Sep 27 20:53:05 b400vc kernel: [    1.362920] i801_smbus 0000:00:1f.3: SMBus using PCI interrupt
Sep 27 20:53:05 b400vc kernel: [    1.363366] ACPI: bus type USB registered

Code: [Select]
Sep 27 20:53:05 b400vc kernel: [    3.955237] tpm_tis 00:06: 1.2 TPM (device-id 0xFE, rev-id 71)
Sep 27 20:53:05 b400vc kernel: [    3.963419] tpm tpm0: A TPM error (7) occurred attempting to read a pcr value
Sep 27 20:53:05 b400vc kernel: [    3.963475] tpm tpm0: TPM is disabled/deactivated (0x7)
Sep 27 20:53:05 b400vc kernel: [    3.966704] tpm tpm0: A TPM error (7) occurred attempting get random
Sep 27 20:53:05 b400vc kernel: [    3.978314] EFI Variables Facility v0.08 2004-May-17
Sep 27 20:53:05 b400vc kernel: [    4.009113] pstore: crypto_comp_decompress failed, ret = -22!
Sep 27 20:53:05 b400vc kernel: [    4.009169] pstore: decompression failed: -22
Sep 27 20:53:05 b400vc kernel: [    4.009255] pstore: crypto_comp_decompress failed, ret = -22!
Sep 27 20:53:05 b400vc kernel: [    4.009297] pstore: decompression failed: -22
Sep 27 20:53:05 b400vc kernel: [    4.009373] pstore: crypto_comp_decompress failed, ret = -22!
Sep 27 20:53:05 b400vc kernel: [    4.009411] pstore: decompression failed: -22
Sep 27 20:53:05 b400vc kernel: [    4.009471] pstore: crypto_comp_decompress failed, ret = -22!
Sep 27 20:53:05 b400vc kernel: [    4.009505] pstore: decompression failed: -22
Sep 27 20:53:05 b400vc kernel: [    4.009563] pstore: crypto_comp_decompress failed, ret = -22!
Sep 27 20:53:05 b400vc kernel: [    4.009598] pstore: decompression failed: -22
Sep 27 20:53:05 b400vc kernel: [    4.009655] pstore: crypto_comp_decompress failed, ret = -22!
Sep 27 20:53:05 b400vc kernel: [    4.009690] pstore: decompression failed: -22
Sep 27 20:53:05 b400vc kernel: [    4.009748] pstore: crypto_comp_decompress failed, ret = -22!
Sep 27 20:53:05 b400vc kernel: [    4.009784] pstore: decompression failed: -22
Sep 27 20:53:05 b400vc kernel: [    4.009847] pstore: crypto_comp_decompress failed, ret = -22!
Sep 27 20:53:05 b400vc kernel: [    4.009882] pstore: decompression failed: -22
Sep 27 20:53:05 b400vc kernel: [    4.009944] pstore: crypto_comp_decompress failed, ret = -22!
Sep 27 20:53:05 b400vc kernel: [    4.009978] pstore: decompression failed: -22
Sep 27 20:53:05 b400vc kernel: [    4.010040] pstore: crypto_comp_decompress failed, ret = -22!
Sep 27 20:53:05 b400vc kernel: [    4.010075] pstore: decompression failed: -22
Sep 27 20:53:05 b400vc kernel: [    4.010136] pstore: crypto_comp_decompress failed, ret = -22!
Sep 27 20:53:05 b400vc kernel: [    4.010171] pstore: decompression failed: -22
Sep 27 20:53:05 b400vc kernel: [    4.010232] pstore: crypto_comp_decompress failed, ret = -22!
Sep 27 20:53:05 b400vc kernel: [    4.010267] pstore: decompression failed: -22
Sep 27 20:53:05 b400vc kernel: [    4.010329] pstore: crypto_comp_decompress failed, ret = -22!
Sep 27 20:53:05 b400vc kernel: [    4.010364] pstore: decompression failed: -22
Sep 27 20:53:05 b400vc kernel: [    4.010423] pstore: crypto_comp_decompress failed, ret = -22!
Sep 27 20:53:05 b400vc kernel: [    4.010458] pstore: decompression failed: -22
Sep 27 20:53:05 b400vc kernel: [    4.010520] pstore: crypto_comp_decompress failed, ret = -22!
Sep 27 20:53:05 b400vc kernel: [    4.010556] pstore: decompression failed: -22
Sep 27 20:53:05 b400vc kernel: [    4.010664] pstore: Registered efi as persistent store backend
Sep 27 20:53:05 b400vc kernel: [    4.014693] RAPL PMU: API unit is 2^-32 Joules, 3 fixed counters, 163840 ms ovfl timer
Sep 27 20:53:05 b400vc kernel: [    4.014695] RAPL PMU: hw unit of domain pp0-core 2^-16 Joules

Code: [Select]
Sep 27 20:53:05 b400vc kernel: [    4.072978] ACPI: Battery Slot [BAT0] (battery present)
Sep 27 20:53:05 b400vc kernel: [    4.082401] cryptd: max_cpu_qlen set to 1000
Sep 27 20:53:05 b400vc kernel: [    4.086938] MXM: GUID detected in BIOS
Sep 27 20:53:05 b400vc kernel: [    4.086999] ACPI Error: AE_AML_PACKAGE_LIMIT, Index (0x000000003) is beyond end of object (length 0x0) (20180531/exoparg2-396)
Sep 27 20:53:05 b400vc kernel: [    4.087015] ACPI Error: Method parse/execution failed \_SB.PCI0.GFX0._DSM, AE_AML_PACKAGE_LIMIT (20180531/psparse-516)
Sep 27 20:53:05 b400vc kernel: [    4.087035] ACPI: \_SB_.PCI0.GFX0: failed to evaluate _DSM (0x300b)
Sep 27 20:53:05 b400vc kernel: [    4.087043] ACPI Warning: \_SB.PCI0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20180531/nsarguments-66)
Sep 27 20:53:05 b400vc kernel: [    4.087279] i915 0000:00:02.0: optimus capabilities: enabled, status dynamic power,
Sep 27 20:53:05 b400vc kernel: [    4.087323] ACPI Error: AE_AML_PACKAGE_LIMIT, Index (0x000000003) is beyond end of object (length 0x0) (20180531/exoparg2-396)
Sep 27 20:53:05 b400vc kernel: [    4.087335] ACPI Error: Method parse/execution failed \_SB.PCI0.GFX0._DSM, AE_AML_PACKAGE_LIMIT (20180531/psparse-516)
Sep 27 20:53:05 b400vc kernel: [    4.087347] ACPI Error: Method parse/execution failed \_SB.PCI0.PEG0.PEGP._DSM, AE_AML_PACKAGE_LIMIT (20180531/psparse-516)
Sep 27 20:53:05 b400vc kernel: [    4.087361] ACPI: \_SB_.PCI0.PEG0.PEGP: failed to evaluate _DSM (0x300b)
Sep 27 20:53:05 b400vc kernel: [    4.087365] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20180531/nsarguments-66)
Sep 27 20:53:05 b400vc kernel: [    4.087522] pci 0000:01:00.0: optimus capabilities: enabled, status dynamic power,
Sep 27 20:53:05 b400vc kernel: [    4.087525] VGA switcheroo: detected Optimus DSM method \_SB_.PCI0.PEG0.PEGP handle
Sep 27 20:53:05 b400vc kernel: [    4.087731] nouveau 0000:01:00.0: NVIDIA GF117 (0d7000a2)

last 100 lines
Code: [Select]
Sep 27 20:53:05 b400vc kernel: [   94.374545]  ? __brelse+0x20/0x20
Sep 27 20:53:05 b400vc kernel: [   94.374548]  ? smp_call_function_many+0x200/0x250
Sep 27 20:53:05 b400vc kernel: [   94.374550]  ? __brelse+0x20/0x20
Sep 27 20:53:05 b400vc kernel: [   94.374551]  ? __brelse+0x20/0x20
Sep 27 20:53:05 b400vc kernel: [   94.374553]  on_each_cpu_mask+0x23/0x60
Sep 27 20:53:05 b400vc kernel: [   94.374555]  ? proc_ns_fget+0x40/0x40
Sep 27 20:53:05 b400vc kernel: [   94.374557]  on_each_cpu_cond+0xa9/0xe0
Sep 27 20:53:05 b400vc kernel: [   94.374560]  kill_bdev+0x21/0x30
Sep 27 20:53:05 b400vc kernel: [   94.374562]  __blkdev_put+0x71/0x1d0
Sep 27 20:53:05 b400vc kernel: [   94.374564]  ? disk_flush_events+0x5c/0x60
Sep 27 20:53:05 b400vc kernel: [   94.374567]  blkdev_close+0x21/0x30
Sep 27 20:53:05 b400vc kernel: [   94.374569]  __fput+0xd0/0x1e0
Sep 27 20:53:05 b400vc kernel: [   94.374571]  task_work_run+0x8a/0xb0
Sep 27 20:53:05 b400vc kernel: [   94.374574]  exit_to_usermode_loop+0xe6/0xf0
Sep 27 20:53:05 b400vc kernel: [   94.374576]  do_syscall_64+0xe4/0xf0
Sep 27 20:53:05 b400vc kernel: [   94.374578]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Sep 27 20:53:05 b400vc kernel: [   94.374580] RIP: 0033:0x7f0887fd3a24
Sep 27 20:53:05 b400vc kernel: [   94.374580] Code: eb 89 e8 4f fa 01 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 8d 05 c1 2f 0d 00 8b 00 85 c0 75 13 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 3c f3 c3 66 90 53 89 fb 48 83 ec 10 e8 34 b7
Sep 27 20:53:05 b400vc kernel: [   94.374612] RSP: 002b:00007ffdb2360308 EFLAGS: 00000246 ORIG_RAX: 0000000000000003
Sep 27 20:53:05 b400vc kernel: [   94.374614] RAX: 0000000000000000 RBX: 0000000000000008 RCX: 00007f0887fd3a24
Sep 27 20:53:05 b400vc kernel: [   94.374615] RDX: 00007f08880a1ca0 RSI: 0000000000000000 RDI: 0000000000000008
Sep 27 20:53:05 b400vc kernel: [   94.374616] RBP: 00007f0887c1dd20 R08: 0000000000000007 R09: 0000000000000150
Sep 27 20:53:05 b400vc kernel: [   94.374617] R10: 00007f08880a1ca0 R11: 0000000000000246 R12: 0000000000000000
Sep 27 20:53:05 b400vc kernel: [   94.374618] R13: 0000557cdb3e0a10 R14: 000000000000000c R15: 000000000000000c
Sep 27 20:53:05 b400vc kernel: [   98.220245] RIP: 0010:drm_debugfs_init+0xa2/0x1a0 [drm]
Sep 27 20:53:05 b400vc kernel: [   98.220246] Code: 84 f8 00 00 00 48 89 d9 48 89 c2 be 03 00 00 00 48 c7 c7 20 87 62 c0 e8 5c fb ff ff 85 c0 89 c5 75 68 49 8b 84 24 90 03 00 00 <48> 83 78 28 00 74 10 48 89 df e8 df e4 fe ff 85 c0 0f 85 89 00 00
Sep 27 20:53:05 b400vc kernel: [   98.220276] RSP: 0018:ffffae5f42333a50 EFLAGS: 00010246
Sep 27 20:53:05 b400vc kernel: [   98.220278] RAX: 0000000000000000 RBX: ffff9b5c1b08ad80 RCX: 0000000000000000
Sep 27 20:53:05 b400vc kernel: [   98.220279] RDX: ffff9b5c1f0cba00 RSI: ffff9b5c1b08ada0 RDI: ffff9b5c1b08adb0
Sep 27 20:53:05 b400vc kernel: [   98.220280] RBP: 0000000000000000 R08: ffff9b5c18473b90 R09: 0000000000000000
Sep 27 20:53:05 b400vc kernel: [   98.220281] R10: ffffae5f423339b8 R11: ffffae5f42333a5b R12: ffff9b5c19925000
Sep 27 20:53:05 b400vc kernel: [   98.220282] R13: 0000000000000081 R14: ffffffffc0bed640 R15: ffffae5f42333ea0
Sep 27 20:53:05 b400vc kernel: [   98.220284] FS:  00007f0887c1dec0(0000) GS:ffff9b5c2de00000(0000) knlGS:0000000000000000
Sep 27 20:53:05 b400vc kernel: [   98.220285] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 27 20:53:05 b400vc kernel: [   98.220287] CR2: 0000000000000028 CR3: 0000000319b64004 CR4: 00000000001606f0
Sep 27 20:53:05 b400vc kernel: [   98.221526] alg: No test for pcbc(aes) (pcbc-aes-aesni)
Sep 27 20:53:05 b400vc kernel: [   98.266343] snd_hda_codec_via hdaudioC0D0: autoconfig for VT1802: line_outs=1 (0x24/0x0/0x0/0x0/0x0) type:speaker
Sep 27 20:53:05 b400vc kernel: [   98.266346] snd_hda_codec_via hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Sep 27 20:53:05 b400vc kernel: [   98.266349] snd_hda_codec_via hdaudioC0D0:    hp_outs=1 (0x25/0x0/0x0/0x0/0x0)
Sep 27 20:53:05 b400vc kernel: [   98.266351] snd_hda_codec_via hdaudioC0D0:    mono: mono_out=0x0
Sep 27 20:53:05 b400vc kernel: [   98.266352] snd_hda_codec_via hdaudioC0D0:    inputs:
Sep 27 20:53:05 b400vc kernel: [   98.266355] snd_hda_codec_via hdaudioC0D0:      Mic=0x30
Sep 27 20:53:05 b400vc kernel: [   98.291002] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/sound/card0/input16
Sep 27 20:53:05 b400vc kernel: [   98.291718] input: HDA Intel PCH Front Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input17
Sep 27 20:53:05 b400vc kernel: [   98.291791] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input18
Sep 27 20:53:05 b400vc kernel: [   98.345680] intel_rapl: Found RAPL domain package
Sep 27 20:53:05 b400vc kernel: [   98.345681] intel_rapl: Found RAPL domain core
Sep 27 20:53:05 b400vc kernel: [   98.345683] intel_rapl: Found RAPL domain uncore
Sep 27 20:53:05 b400vc kernel: [   98.415067] media: Linux media interface: v0.10
Sep 27 20:53:05 b400vc kernel: [   98.423634] videodev: Linux video capture interface: v2.00
Sep 27 20:53:05 b400vc kernel: [   98.442486] uvcvideo: Found UVC 1.00 device USB2.0 HD UVC WebCam (04f2:b375)
Sep 27 20:53:05 b400vc kernel: [   98.457902] uvcvideo 1-1.3:1.0: Entity type for entity Extension 4 was not initialized!
Sep 27 20:53:05 b400vc kernel: [   98.457904] uvcvideo 1-1.3:1.0: Entity type for entity Processing 2 was not initialized!
Sep 27 20:53:05 b400vc kernel: [   98.457905] uvcvideo 1-1.3:1.0: Entity type for entity Camera 1 was not initialized!
Sep 27 20:53:05 b400vc kernel: [   98.457975] input: USB2.0 HD UVC WebCam: USB2.0 HD as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input19
Sep 27 20:53:05 b400vc kernel: [   98.458047] usbcore: registered new interface driver uvcvideo
Sep 27 20:53:05 b400vc kernel: [   98.458048] USB Video Class driver (1.1.1)
Sep 27 20:53:05 b400vc kernel: [   98.612184] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 27 20:53:05 b400vc kernel: [   98.630809] asus_wmi: ASUS WMI generic driver loaded
Sep 27 20:53:05 b400vc kernel: [   98.631746] asus_wmi: Initialization: 0x1
Sep 27 20:53:05 b400vc kernel: [   98.631796] asus_wmi: BIOS WMI version: 7.9
Sep 27 20:53:05 b400vc kernel: [   98.631874] asus_wmi: SFUN value: 0x4a2877
Sep 27 20:53:05 b400vc kernel: [   98.633199] input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input20
Sep 27 20:53:05 b400vc kernel: [   99.361444] asus_wmi: Number of fans: 1
Sep 27 20:53:05 b400vc kernel: [   99.509432] Console: switching to colour frame buffer device 170x48
Sep 27 20:53:05 b400vc kernel: [  101.071467] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
Sep 27 20:53:05 b400vc kernel: [  124.280438] Adding 13371388k swap on /dev/sdb7.  Priority:-2 extents:1 across:13371388k SSFS
Sep 27 20:53:05 b400vc kernel: [  124.318781] EXT4-fs (sdb3): re-mounted. Opts: (null)
Sep 27 20:53:05 b400vc kernel: [  124.594429] device-mapper: uevent: version 1.0.3
Sep 27 20:53:05 b400vc kernel: [  124.597604] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: dm-devel@redhat.com
Sep 27 20:53:05 b400vc kernel: [  124.830567] loop: module loaded
Sep 27 20:53:05 b400vc kernel: [  124.845000] lp: driver loaded but no devices found
Sep 27 20:53:05 b400vc kernel: [  124.852622] EXT4-fs (sdb4): mounted filesystem with ordered data mode. Opts: (null)
Sep 27 20:53:05 b400vc kernel: [  124.855579] ppdev: user-space parallel port driver
Sep 27 20:53:05 b400vc kernel: [  124.960814] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
Sep 27 20:53:05 b400vc kernel: [  124.981253] fuse init (API version 7.27)
Sep 27 20:53:05 b400vc kernel: [  125.276241] EXT4-fs (sdb5): mounted filesystem with ordered data mode. Opts: (null)
Sep 27 20:53:05 b400vc kernel: [  198.902003] RPC: Registered named UNIX socket transport module.
Sep 27 20:53:05 b400vc kernel: [  198.903315] RPC: Registered udp transport module.
Sep 27 20:53:05 b400vc kernel: [  198.904552] RPC: Registered tcp transport module.
Sep 27 20:53:05 b400vc kernel: [  198.905744] RPC: Registered tcp NFSv4.1 backchannel transport module.
Sep 27 20:53:05 b400vc kernel: [  198.914963] FS-Cache: Loaded
Sep 27 20:53:05 b400vc kernel: [  198.932287] FS-Cache: Netfs 'nfs' registered for caching
Sep 27 20:53:05 b400vc kernel: [  198.950181] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Sep 27 20:53:05 b400vc kernel: [  199.332622] vboxdrv: loading out-of-tree module taints kernel.
Sep 27 20:53:05 b400vc kernel: [  199.346809] vboxdrv: Found 4 processor cores
Sep 27 20:53:05 b400vc kernel: [  199.368940] vboxdrv: TSC mode is Invariant, tentative frequency 1696142330 Hz
Sep 27 20:53:05 b400vc kernel: [  199.370939] vboxdrv: Successfully loaded version 5.2.18_Debian (interface 0x00290001)
Sep 27 20:53:05 b400vc kernel: [  199.381240] VBoxNetFlt: Successfully started.
Sep 27 20:53:05 b400vc kernel: [  199.392127] VBoxNetAdp: Successfully started.
Sep 27 20:53:05 b400vc kernel: [  199.411098] VBoxPciLinuxInit
Sep 27 20:53:05 b400vc kernel: [  199.418872] vboxpci: IOMMU not found (not registered)
Sep 27 20:53:06 b400vc kernel: [  200.104549] NET: Registered protocol family 3
Sep 27 20:53:06 b400vc kernel: [  200.111553] NET: Registered protocol family 5
Sep 27 20:54:59 b400vc kernel: [  313.554694] sysrq: SysRq : Keyboard mode set to system default
Sep 27 20:55:02 b400vc kernel: [  316.374170] sysrq: SysRq : This sysrq operation is disabled.
Sep 27 20:55:04 b400vc kernel: [  318.556088] sysrq: SysRq : This sysrq operation is disabled.
Sep 27 20:55:07 b400vc kernel: [  320.839267] sysrq: SysRq : Emergency Sync
Sep 27 20:55:07 b400vc kernel: [  320.843058] Emergency Sync complete
Sep 27 20:55:09 b400vc kernel: [  323.520471] sysrq: SysRq : Emergency Remount R/O
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: sunrat on 2018/09/28, 11:46:09
Same problem here.
4.18.7-towo.2-siduction-amd64 boots fine. Strangely the login screen is letterboxed ie. squashed to the centre half of the screen rather than full screen. Desktop is full screen after logging in though.
Code: [Select]
journalctl -b -1 -p 3
-- Logs begin at Tue 2017-10-31 23:28:43 AEDT, end at Fri 2018-09-28 19:42:33 AEST. --
Sep 28 19:17:05 siduction-brain2 kernel: Error: Driver 'pcspkr' is already registered, aborting...
Sep 28 19:17:05 siduction-brain2 kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000028
Sep 28 19:17:05 siduction-brain2 systemd-udevd[277]: worker [304] failed while handling '/devices/pci0000:00/0000:00:01.0/0000:01:00.0'
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: samoht on 2018/09/28, 11:52:02
Confirmed: Kernel linux-image-4.18.10-towo.2-siduction-amd64 does not boot here either.
Kernel linux-image-4.18.10-towo.1-siduction-amd64 works.
I am away from my computer, but can post the boot messages later
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: ReinerS on 2018/09/28, 12:13:55
Here it works with my Big Box, trying it with the lappy now too.
Regards
Reiner
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: tommy2 on 2018/09/28, 12:52:16
Mine stops at ERROR: Driver 'pcspkr' is already registered - aborting, though the hard drive light flickers like it is doing something but that's where it hangs. Need to use the reset button and nothing else works, kernel 10.1 works fine. Looks like I need to set back and wait a while to see if any newer updates fix the problem.
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: dibl on 2018/09/28, 12:59:55
In case it helps with troubleshooting, here is a laptop where the new kernel works with no problem:

Code: [Select]
System:
  Host: n5110 Kernel: 4.18.10-towo.2-siduction-amd64 x86_64 bits: 64
  Desktop: LXQt 0.13.0
  Distro: siduction 17.1.0 Patience - lxqt - (201703051830)
Machine:
  Type: Portable System: Dell product: Inspiron N5110 v: N/A serial: <filter>
  Mobo: Dell model: 034W60 v: A11 serial: <filter> BIOS: Dell v: A11
  date: 08/03/2012
Battery:
  ID-1: BAT0 charge: 82.1 Wh condition: 85.0/81.3 Wh (104%)
CPU:
  Topology: Dual Core model: Intel Core i3-2330M bits: 64 type: MT MCP
  L2 cache: 3072 KiB
  Speed: 799 MHz min/max: 800/2200 MHz Core speeds (MHz): 1: 798 2: 797
  3: 798 4: 798
Graphics:
  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics
  driver: i915 v: kernel
  Display: x11 server: X.Org 1.20.1 driver: modesetting unloaded: fbdev,vesa
  resolution: 1366x768~60Hz
  OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile v: 3.3 Mesa 18.1.8
Audio:
  Device-1: Intel 6 Series/C200 Series Family High Definition Audio
  driver: snd_hda_intel
  Sound Server: ALSA v: k4.18.10-towo.2-siduction-amd64
Network:
  Device-1: Realtek RTL810xE PCI Express Fast Ethernet driver: r8169
  IF: enp5s0 state: down mac: <filter>
  Device-2: Intel Centrino Wireless-N 1030 [Rainbow Peak] driver: iwlwifi
  IF: wlp9s0 state: up mac: <filter>
Drives:
  Local Storage: total: 74.53 GiB used: 10.84 GiB (14.5%)
  ID-1: /dev/sda vendor: Intel model: SSDSA2CW080G3 size: 74.53 GiB
Partition:
  ID-1: / size: 15.62 GiB used: 9.97 GiB (63.8%) fs: ext4 dev: /dev/sda1
  ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2
Sensors:
  System Temperatures: cpu: 43.0 C mobo: N/A
  Fan Speeds (RPM): cpu: 0
Info:
  Processes: 180 Uptime: 12m Memory: 3.77 GiB used: 1.21 GiB (32.2%)
  Shell: bash inxi: 3.0.24
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: AvY on 2018/09/28, 13:05:33
It seems we're all having slightly different problems with this one. Mine also stops on 'Driver pcspkr is already registered', but sometimes hangs on 'Starting Flush Journal to Persistent Storage' instead.
How exciting!
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: dibl on 2018/09/28, 13:13:11
I have been seeing the 'Driver pcspkr is already registered' message for months if not years, on all recent kernels.  I can't believe it has anything to do with failure to boot.
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: tommy2 on 2018/09/28, 13:17:30
That maybe and I just did not notice it before, however that is where my first drive with siduction is hanging. I am in the process of updating my second drive now and will advise how that went.
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: samoht on 2018/09/28, 13:25:56
Quote
I have been seeing the 'Driver pcspkr is already registered' message for months if not years, on all recent kernels.  I can't believe it has anything to do with failure to boot.

Confirm @dibl's statement.

Look at
https://www.linuxquestions.org/questions/linux-newbie-8/error-driver-%27pcspkr%27-is-already-registered-aborting-923450/#post4572887 (https://www.linuxquestions.org/questions/linux-newbie-8/error-driver-%27pcspkr%27-is-already-registered-aborting-923450/#post4572887)
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: samoht on 2018/09/28, 13:46:48
Boot messages here:

Code: [Select]
kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000028
systemd-udevd[324]: worker [333] failed while handling '/devices/pci0000:00/0000:00:01.0/0000:01:00.0'
Like on @sunrat's machine!

Code: [Select]
System:    Host: tuxxy-sid Kernel: 4.18.10-towo.1-siduction-amd64 x86_64 bits: 64 compiler: gcc v: 7.3.0
           Console: tty 0 Distro: siduction 18.3.0 Patience - kde - (201805132121)
           base: Debian GNU/Linux buster/sid
Machine:   Type: Desktop Mobo: Gigabyte model: EP45-UD3LR v: x.x serial: N/A BIOS: Award v: F11
           date: 04/22/2010
CPU:       Topology: Dual Core model: Intel Core2 Duo E7400 bits: 64 type: MCP arch: Penryn rev: A
           L2 cache: 3072 KiB
           flags: lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx bogomips: 11200
           Speed: 1600 MHz min/max: 1600/2800 MHz Core speeds (MHz): 1: 1600 2: 1600
Graphics:  Device-1: NVIDIA GT218 [GeForce 210] driver: nouveau v: kernel bus ID: 01:00.0
           Display: server: X.org 1.20.1 driver: modesetting unloaded: fbdev tty: 236x47
           Message: Advanced graphics data unavailable in console for root.
Audio:     Device-1: Intel 82801JI HD Audio driver: snd_hda_intel v: kernel bus ID: 00:1b.0
           Device-2: NVIDIA High Definition Audio driver: snd_hda_intel v: kernel bus ID: 01:00.1
           Sound Server: ALSA v: k4.18.10-towo.1-siduction-amd64
Info:      Processes: 195 Uptime: 35m Memory: 3.85 GiB used: 1.63 GiB (42.2%) Init: systemd runlevel: 35
           Compilers: gcc: 8.2.0 Shell: bash v: 4.4.23 inxi: 3.0.24
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: Xaver on 2018/09/28, 13:51:35
4.18.10-towo.1 is booting fine,
4.18.10-towo.2 hangs at boot.
So the question simply is: What are the changes? Which of these changes causes the problem?
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: towo on 2018/09/28, 14:57:17
The only change between 4.18.10-towo.1 and 4.18.10-towo.2 is patch-4.18.11-rc1.So propably there is a upstream regression.
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: samoht on 2018/09/28, 15:07:25
Thanks, @towo.
Wait and see!
German: Abwarten und Tee trinken
Our motto: Patience  ;)
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: sunrat on 2018/09/28, 15:11:12
My system is very similar to samoht's. Mobo, CPU and graphics:
Code: [Select]
System:    Host: siduction-brain2 Kernel: 4.18.7-towo.2-siduction-amd64 x86_64 bits: 64
           Desktop: KDE Plasma 5.13.5 Distro: siduction 17.1.0 Patience - kde - (201703051755)
Machine:   Type: Desktop Mobo: Gigabyte model: EP45-UD3R v: x.x serial: <root required> BIOS: Award v: F3
           date: 09/18/2008
CPU:       Topology: Dual Core model: Intel Core2 Duo E8500 bits: 64 type: MCP L2 cache: 6144 KiB
           Speed: 2801 MHz min/max: 2000/3166 MHz Core speeds (MHz): 1: 2801 2: 2800
Graphics:  Device-1: NVIDIA GF114 [GeForce GTX 560 Ti] driver: nouveau v: kernel
           Display: x11 server: X.Org 1.20.1 driver: modesetting unloaded: fbdev,vesa tty: N/A
           OpenGL: renderer: NVCE v: 4.3 Mesa 18.1.8
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: tommy2 on 2018/09/28, 17:43:06
My system is hanging on boot of the .10-towo.2 here:   STARTING udev kernel device manager...[OK] STARTED flush journal to persistent storage. [OK] STARTED udev kernel device manager.
That's where the system locks up and requires a cold "reset" reboot only on this kernel. My .10-towo.1 and .9 kernels boot without any problem, go figure. :(
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: ReinerS on 2018/09/28, 18:10:25
So, started here on the laptop (hp elitebook 8470p) too, also no problems yet here.
Regards
Reiner
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: tommy2 on 2018/09/28, 18:29:03
@ReinerS, just got finished installing it on my second siduction drive and it locked up like I stated earlier on flushing the journal to persistent storage.  The same box with two installations and both lockup with the 10-towo.2 kernels, I even reinstalled the image on the first system to make sure nothing got missed, but it did not make any difference. Maybe a remove and purge of the image and reinstalling again might give me a little better insight as to what might be causing the problem.  :-\
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: ReinerS on 2018/09/28, 19:07:54
Hmm, maybe only some configurations are hit by this.
I have an self-build box with PH II X4 945, 6GB Ram, ASUS Mainboard, two DVBCards, NVidia730 Graphics Card and 4 HDDs with mostly being an LVM Volume.
On the Laptop it is an I-5 3360M, 8 GB Ram, LUKS-encryptet 256GB SSD and 750GB HDD, Intel-Graphics.

Until now, no problems found.
Regards
Reiner
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: samoht on 2018/09/28, 19:37:23
@ReinerS,

Self-build box with ASUS motherboard? That does not help at all.
Laptop: Which motherboard?
Inxi?
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: ReinerS on 2018/09/28, 20:33:44
Ok, here, as follows, the inxi-Screens.
Laptop
Code: [Select]
System:    Host: RS8470p Kernel: 4.18.10-towo.2-siduction-amd64 x86_64 bits: 64 Console: tty 2
           Distro: Frankensid xfce based on siduction 18.3.0 Patience
Machine:   Type: Laptop System: Hewlett-Packard product: HP EliteBook 8470p v: A1029D1102 serial: CNU315BFP3
           Mobo: Hewlett-Packard model: 179B v: KBC Version 42.38 serial: PCWHK001X4JV89 UEFI: Hewlett-Packard
           v: 68ICF Ver. F.72 date: 05/28/2018
Battery:   ID-1: BAT0 charge: 42.5 Wh condition: 44.6/44.6 Wh (100%)
CPU:       Topology: Dual Core model: Intel Core i5-3360M bits: 64 type: MT MCP L2 cache: 3072 KiB
           Speed: 1526 MHz min/max: 1200/3500 MHz Core speeds (MHz): 1: 1205 2: 1197 3: 1197 4: 1283
Graphics:  Device-1: Intel 3rd Gen Core processor Graphics driver: i915 v: kernel
           Display: server: X.org 1.20.1 driver: modesetting unloaded: fbdev,vesa tty: 132x48
           Message: Advanced graphics data unavailable in console for root.
Audio:     Device-1: Intel 7 Series/C216 Family High Definition Audio driver: snd_hda_intel
           Sound Server: ALSA v: k4.18.10-towo.2-siduction-amd64
Network:   Device-1: Intel 82579LM Gigabit Network driver: e1000e
           IF: enp0s25 state: up speed: 1000 Mbps duplex: full mac: 2c:59:e5:04:af:67
           Device-2: Intel Centrino Advanced-N 6205 [Taylor Peak] driver: iwlwifi
           IF: wlo1 state: down mac: d2:aa:da:44:4d:01
           IF-ID-1: wwp0s26u1u5 state: down mac: 7a:30:cb:c4:69:22
Drives:    Local Storage: total: 960.16 GiB used: 269.50 GiB (28.1%)
           ID-1: /dev/sda vendor: Samsung model: SSD 840 EVO 250GB size: 232.89 GiB
           ID-2: /dev/sdb model: WL750GLSA854G size: 698.64 GiB
           ID-3: /dev/sdc type: USB vendor: SanDisk model: Ultra Fit size: 28.64 GiB
Partition: ID-1: / size: 58.81 GiB used: 18.00 GiB (30.6%) fs: ext4 dev: /dev/dm-1
           ID-2: /boot size: 975.9 MiB used: 164.9 MiB (16.9%) fs: ext4 dev: /dev/sda4
           ID-3: /home size: 152.81 GiB used: 71.48 GiB (46.8%) fs: ext4 dev: /dev/dm-3
           ID-4: swap-1 size: 16.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/dm-2
Sensors:   System Temperatures: cpu: 55.0 C mobo: 0.0 C
           Fan Speeds (RPM): N/A
Info:      Processes: 248 Uptime: 2h 39m Memory: 7.66 GiB used: 4.00 GiB (52.2%) Init: systemd runlevel: 5
           Shell: fish inxi: 3.0.24
Self-Build Box:
Code: [Select]
System:    Host: VdrLX Kernel: 4.18.10-towo.2-siduction-amd64 x86_64 bits: 64 Desktop: Xfce 4.12.4
           Distro: Frankensid xfce based on siduction 18.3.0 Patience
Machine:   Type: Desktop Mobo: ASUSTeK model: M4A88TD-V EVO/USB3 v: Rev X.0x serial: MF70B1G04800010
           BIOS: American Megatrends v: 2301 date: 08/09/2012
CPU:       Topology: Quad Core model: AMD Phenom II X4 945 bits: 64 type: MCP L2 cache: 2048 KiB
           Speed: 800 MHz min/max: 800/3000 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800
Graphics:  Device-1: NVIDIA GK208 [GeForce GT 730] driver: nvidia v: 390.87
           Display: server: X.Org 1.20.1 driver: nouveau unloaded: fbdev,modesetting,vesa
           resolution: 1366x768~60Hz
           OpenGL: renderer: N/A v: N/A
Audio:     Device-1: Advanced Micro Devices [AMD/ATI] SBx00 Azalia driver: snd_hda_intel
           Device-2: NVIDIA GK208 HDMI/DP Audio driver: snd_hda_intel
           Sound Server: ALSA v: k4.18.10-towo.2-siduction-amd64
Network:   Device-1: Techsan Co B2C2 FlexCopII DVB chip / Technisat SkyStar2 DVB card driver: b2c2_flexcop_pci
           Device-2: Techsan Co B2C2 FlexCopII DVB chip / Technisat SkyStar2 DVB card driver: b2c2_flexcop_pci
           Device-3: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
           IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: bc:ae:c5:bd:e8:78
           IF-ID-1: docker0 state: down mac: 02:42:4e:d3:ab:bf
Drives:    Local Storage: total: 6.35 TiB used: 6.06 TiB (95.4%)
           ID-1: /dev/sda model: WL2000GSA6454G size: 1.80 TiB
           ID-2: /dev/sdb vendor: Western Digital model: WD20EARX-00PASB0 size: 1.82 TiB
           ID-3: /dev/sdc vendor: Western Digital model: WD20EARS-00J2GB0 size: 1.82 TiB
           ID-4: /dev/sdd vendor: Western Digital model: WD10EARS-00Y5B1 size: 931.51 GiB
Partition: ID-1: / size: 57.55 GiB used: 23.04 GiB (40.0%) fs: ext4 dev: /dev/sda3
           ID-2: /boot size: 476.2 MiB used: 282.9 MiB (59.4%) fs: ext4 dev: /dev/sda1
           ID-3: swap-1 size: 16.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2
Sensors:   System Temperatures: cpu: 0.0 C mobo: N/A
           Fan Speeds (RPM): N/A
Info:      Processes: 181 Uptime: 10h 36m Memory: 5.82 GiB used: 721.1 MiB (12.1%) Shell: fish inxi: 3.0.24

Hope that helps.
regards
Reiner
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: vilde on 2018/09/28, 22:45:41
so far I have tried two machines, the first one does not boot
4.18.10-towo.2-siduction-amd64.
Code: [Select]
System:
  Host: bola-pc Kernel: 4.18.9-towo.1-siduction-amd64 x86_64 bits: 64
  compiler: gcc v: 7.3.0 Desktop: Xfce 4.12.4
  Distro: siduction 18.3.0 Patience - xfce - (201805132203)
  base: Debian GNU/Linux buster/sid
Machine:
  Type: Laptop System: LENOVO product: 25223FG v: ThinkPad T410
  serial: <root required>
  Mobo: LENOVO model: 25223FG serial: <root required> BIOS: LENOVO
  v: 6IET85WW (1.45 ) date: 02/14/2013
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Touch Keyboard K400
  charge: 100% (should be ignored) status: Discharging
CPU:
  Topology: Dual Core model: Intel Core i7 M 620 bits: 64 type: MT MCP
  arch: Nehalem rev: 2 L2 cache: 4096 KiB
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 21280
  Speed: 1463 MHz min/max: 1199/2667 MHz Core speeds (MHz): 1: 1463 2: 1418
  3: 1453 4: 1440
Graphics:
  Device-1: NVIDIA GT218M [NVS 3100M] driver: nouveau v: kernel
  bus ID: 01:00.0
  Display: x11 server: X.Org 1.19.6 driver: nouveau
  unloaded: fbdev,modesetting,vesa resolution: 1920x1080~50Hz
  OpenGL: renderer: NVA8 v: 3.3 Mesa 18.1.8 direct render: Yes
Network:
  Device-1: Intel 82577LM Gigabit Network driver: e1000e v: 3.2.6-k
  port: 1820 bus ID: 00:19.0
  IF: enp0s25 state: up speed: 100 Mbps duplex: full mac: 00:26:2d:f3:8e:a0
  Device-2: Intel Centrino Ultimate-N 6300 driver: iwlwifi v: kernel
  bus ID: 03:00.0
  IF: wlp3s0 state: down mac: 1a:8d:0f:eb:ed:af
Drives:
  Local Storage: total: 2.35 TiB used: 1.24 TiB (52.7%)
Info:
  Processes: 173 Uptime: 3h 21m Memory: 3.72 GiB used: 837.2 MiB (22.0%)
  Init: systemd runlevel: 5 Compilers: gcc: 8.2.0 Shell: bash v: 4.4.23
  inxi: 3.0.24
The second one works.
Code: [Select]
System:
  Host: vilde-T420 Kernel: 4.18.10-towo.2-siduction-amd64 x86_64 bits: 64
  compiler: gcc v: 7.3.0 Desktop: Xfce 4.12.4
  Distro: siduction 18.1.0 Patience - xfce - (201712310104)
  base: Debian GNU/Linux buster/sid
Machine:
  Type: Laptop System: LENOVO product: 4180G73 v: ThinkPad T420
  serial: <root required>
  Mobo: LENOVO model: 4180G73 serial: <root required> UEFI: LENOVO
  v: 83ET78WW (1.48 ) date: 01/21/2016
Battery:
  ID-1: BAT0 charge: 25.6 Wh condition: 26.2/56.2 Wh (47%)
  model: SANYO 45N1001 status: Unknown
  ID-2: BAT1 charge: 65.3 Wh condition: 66.4/93.2 Wh (71%)
  model: SANYO 42T4739 status: Unknown
CPU:
  Topology: Dual Core model: Intel Core i5-2540M bits: 64 type: MT MCP
  arch: Sandy Bridge rev: 7 L2 cache: 3072 KiB
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 20734
  Speed: 797 MHz min/max: 800/3300 MHz Core speeds (MHz): 1: 851 2: 821
  3: 828 4: 832
Graphics:
  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics
  driver: i915 v: kernel bus ID: 00:02.0
  Display: x11 server: X.Org 1.20.1 driver: modesetting unloaded: fbdev,vesa
  resolution: 1600x900~60Hz
  OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile v: 3.3 Mesa 18.1.8
  direct render: Yes
Network:
  Device-1: Intel 82579LM Gigabit Network driver: e1000e v: 3.2.6-k
  port: 5080 bus ID: 00:19.0
  IF: enp0s25 state: up speed: 100 Mbps duplex: full mac: 00:21:cc:ba:0c:ec
  Device-2: Intel Centrino Advanced-N 6205 [Taylor Peak] driver: iwlwifi
  v: kernel bus ID: 03:00.0
  IF: wlp3s0 state: down mac: 86:cb:4d:e1:aa:b4
  IF-ID-1: wwp0s29u1u4i6 state: down mac: 02:80:37:ec:02:00
Drives:
  Local Storage: total: 260.84 GiB used: 104.58 GiB (40.1%)
Info:
  Processes: 172 Uptime: 9h 11m Memory: 7.68 GiB used: 1.36 GiB (17.7%)
  Init: systemd runlevel: 5 Compilers: gcc: 8.2.0 Shell: bash v: 4.4.23
  inxi: 3.0.24
If somebody notice, there is old xorg on the machine that not work with the latest kernel becuaseof the old problem with xorg and old nvidia cards. But I did a new installation on that machine today just to try the newest xorg and that  problem is gone, but the new problemis it will not boot with4.18.10-towo.2-siduction-amd64 .
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: clubex on 2018/09/29, 00:34:43
This machine won't boot to graphic login with 4.18.10-towo.2
Code: [Select]
ystem:
  Host: westfield2 Kernel: 4.18.10-towo.1-siduction-amd64 x86_64 bits: 64
  Desktop: KDE Plasma 5.13.5
  Distro: siduction 14.1.0 Indian Summer - kde - (201411230337)
Machine:
  Type: Desktop Mobo: ASRock model: N68C-GS FX serial: <root required>
  BIOS: American Megatrends v: P1.40 date: 10/31/2012
CPU:
  Topology: Quad Core model: AMD Phenom II X4 945 bits: 64 type: MCP
  L2 cache: 2048 KiB
  Speed: 800 MHz min/max: 800/3000 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800
Graphics:
  Device-1: NVIDIA GM107 [GeForce GTX 750 Ti] driver: nvidia v: 390.87
  Display: x11 server: X.Org 1.20.1 driver: nvidia unloaded: nouveau
  resolution: 1680x1050~60Hz
  OpenGL: renderer: GeForce GTX 750 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 390.87
Audio:
  Device-1: NVIDIA MCP61 High Definition Audio driver: snd_hda_intel
  Device-2: NVIDIA GF116 High Definition Audio driver: snd_hda_intel
  Sound Server: ALSA v: k4.18.10-towo.1-siduction-amd64
Network:
  Device-1: NVIDIA MCP61 Ethernet type: network bridge driver: forcedeth
  IF: enp0s7 state: up speed: 1000 Mbps duplex: full mac: bc:5f:f4:41:1f:d7
Drives:
  Local Storage: total: 465.76 GiB used: 216.39 GiB (46.5%)
  ID-1: /dev/sda vendor: Western Digital model: WD5000AVCS-632DY1 size: 465.76 GiB
Partition:
  ID-1: / size: 18.99 GiB used: 15.08 GiB (79.4%) fs: ext4 dev: /dev/sda1
  ID-2: /home size: 429.48 GiB used: 201.31 GiB (46.9%) fs: ext4 dev: /dev/sda2
  ID-3: swap-1 size: 9.79 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda3
Sensors:
  System Temperatures: cpu: 29.2 C mobo: N/A gpu: nvidia temp: 37 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 40%
Info:
  Processes: 208 Uptime: 5h 35m Memory: 7.79 GiB used: 2.34 GiB (30.1%) Shell: bash
  inxi: 3.0.24
I noticed during boot that the system failed to start loading Kernel Modules although later in the boot process a 'start job' ran loading the modules. Read of that what you may.
I hope when the next kernel arrives the problem will be saved. I not .....
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: seasons on 2018/09/29, 10:10:02
https://github.com/damentz/liquorix-package/issues/10 (https://github.com/damentz/liquorix-package/issues/10)
EDIT: In case it is not clear, the problem is an upstream one that affects system using the nvidia binary/proprietary driver, but it has now been fixed upstream. Continue to boot the previous kernel, and the next kernel that towo uploads should contain the fix.
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: sunrat on 2018/09/29, 10:50:36
https://github.com/damentz/liquorix-package/issues/10 (https://github.com/damentz/liquorix-package/issues/10)
EDIT: In case it is not clear, the problem is an upstream one that affects system using the nvidia binary/proprietary driver, but it has now been fixed upstream. Continue to boot the previous kernel, and the next kernel that towo uploads should contain the fix.
Several of the reports above were for nouveau including mine. It's not just the nvidia proprietary driver.
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: dibl on 2018/09/29, 13:09:26
For the ones who experience a boot failure, how long did you wait before you did the hard reset?

I just updated my main workstation and rebooted with the new kernel, and it stopped after the IPV6 start and it just sat there for a very long pause, then it showed "A start job is running for Load Kernel Modules" and that waited the full 1 minute 30 seconds before it proceeded with the rest of the bootup.  Then it finished and brought up my plasma desktop, and everything seems to be correct.

I have never seen this delay before, so something substantial has changed since the previous kernel.

So if you haven't tried it before, try letting the system sit for a couple of minutes to see if there is some delay in the boot.

Code: [Select]
  Host: dibl-patience Kernel: 4.18.10-towo.2-siduction-amd64 x86_64 bits: 64
  Desktop: KDE Plasma 5.13.5
  Distro: siduction 18.3.0 Patience - kde - (201805132121)
Machine:
  Type: Desktop Mobo: ASUSTeK model: ROG STRIX X299-E GAMING v: Rev 1.xx
  serial: <filter> UEFI: American Megatrends v: 1401 date: 05/21/2018
CPU:
  Topology: Quad Core model: Intel Core i7-7740X bits: 64 type: MT MCP
  L2 cache: 8192 KiB
  Speed: 2699 MHz min/max: 800/4500 MHz Core speeds (MHz): 1: 2699 2: 1873 3: 1654
  4: 2757 5: 3490 6: 3017 7: 2958 8: 2567
Graphics:
  Device-1: NVIDIA GP106 [GeForce GTX 1060 6GB] driver: nvidia v: 390.87
  Display: x11 server: X.Org 1.20.1 driver: nvidia
  resolution: 1920x1200~60Hz, 1920x1080~60Hz
  OpenGL: renderer: llvmpipe (LLVM 6.0 256 bits) v: 3.3 Mesa 18.1.8
Audio:
  Device-1: Intel 200 Series PCH HD Audio driver: snd_hda_intel
  Device-2: NVIDIA GP106 High Definition Audio driver: snd_hda_intel
  Device-3: Logitech HD Pro Webcam C920 type: USB driver: snd-usb-audio,uvcvideo
  Sound Server: ALSA v: k4.18.10-towo.2-siduction-amd64
Network:
  Device-1: Intel Ethernet I219-V driver: e1000e
  IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: br0 state: up speed: N/A duplex: N/A mac: <filter>
Drives:
  Local Storage: total: 2.27 TiB used: 908.96 GiB (39.0%)
  ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB
  ID-2: /dev/sdb vendor: Western Digital model: WD1003FZEX-00K3CA0 size: 931.51 GiB
  ID-3: /dev/sdc vendor: Western Digital model: WD1003FZEX-00K3CA0 size: 931.51 GiB
Partition:
  ID-1: / size: 58.81 GiB used: 9.18 GiB (15.6%) fs: ext4 dev: /dev/sda2
  ID-2: /home size: 393.18 GiB used: 51.10 GiB (13.0%) fs: ext4 dev: /dev/sda4
  ID-3: swap-1 size: 5.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda3
Sensors:
  System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nvidia temp: 34 C
  Fan Speeds (RPM): cpu: 0 gpu: nvidia fan: 0%
Info:
  Processes: 238 Uptime: 8m Memory: 31.33 GiB used: 1.79 GiB (5.7%) Shell: bash
  inxi: 3.0.24

EDIT:  systemd-analyze blame shows at the first line 1 minute 30.057 seconds for the systemd-modules-load service.  All other services are 1.6 seconds or less.
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: id027102 on 2018/09/29, 13:41:01
I was waiting for more than 5 minutes ant then hard reboot.I had to truncate file, so begin of file is deleted ,
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: sunrat on 2018/09/29, 15:35:08
I waited over 5 minutes too with it stalled at 'Starting Flush Journal to Persistent Storage'.Magic SysReq keys worked to reboot it.
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: tommy2 on 2018/09/29, 16:40:30
@dibl, just to be on the safe side over 30 minutes and my system has a radon graphics chip. :-\
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: towo on 2018/09/29, 18:17:53
Don't waste your time with this kernel, it was an updtream regression.
At the moment kernel 4.18.11 is buildingm which has revert the change in 4.18.11-rc1 in drivers/gpu/drm/drm_atomic.c.
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: Xaver on 2018/09/29, 19:28:15
@ towo
Thank you for fixing the issue.


What is an 'upstream regression'?
I have been searching up and down the web and could not find a sufficient answer.
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: clubex on 2018/09/29, 19:40:21
The new kernel 4.18.11-towo.1 works for me so I've purged 4.18.10-towo.2.
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: vilde on 2018/09/29, 19:47:45
The new kernel 4.18.11-towo.1 works for me so I've purged 4.18.10-towo.2.
+1
Thank you towo for the fast work :)
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: samoht on 2018/09/29, 20:38:28
Newest kernel works.
Thanks, @towo!
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: devil on 2018/09/29, 20:43:15
xaver: a regression that happend upstream, so in this case at kernel.org. Regressions can't always be   avoided. You change one thing, which causes a regression some place else, that in some cases only shows later.
Title: Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
Post by: tommy2 on 2018/09/30, 08:40:17
Siduction dev's thanks for all you do for us!  :)