seduction
 Language:
Welcome, Guest. Please login or register.
Did you miss your activation email?
2019/11/19, 06:15:09


Help

Author [EN] [PL] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] Topic: linux-image-4.18.10-towo.2-siduction-amd64 does not boot  (Read 2256 times)

0 Members and 1 Guest are viewing this topic.

Offline Xaver

  • User
  • Posts: 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

Offline absolut

  • User
  • Posts: 421
Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
« Reply #1 on: 2018/09/27, 19:43:40 »
please paste whole boot log, i am not sure one line will help

Offline Xaver

  • User
  • Posts: 49
Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
« Reply #2 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?
« Last Edit: 2018/09/27, 21:17:16 by Xaver »

Offline absolut

  • User
  • Posts: 421
Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
« Reply #3 on: 2018/09/27, 22:02:07 »
please use a pastebin for the whole log and provide the url -> https://paste.debian.net/

Offline Xaver

  • User
  • Posts: 49
Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
« Reply #4 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.

Offline DeepDayze

  • User
  • Posts: 409
Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
« Reply #5 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

Offline Xaver

  • User
  • Posts: 49
Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
« Reply #6 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
« Last Edit: 2018/09/28, 10:32:20 by Xaver »

Offline sunrat

  • User
  • Posts: 309
Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
« Reply #7 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'
« Last Edit: 2018/09/28, 11:53:20 by sunrat »

Offline samoht

  • User
  • Posts: 321
Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
« Reply #8 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
« Last Edit: 2018/09/28, 11:57:56 by samoht »

Offline ReinerS

  • User
  • Posts: 943
Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
« Reply #9 on: 2018/09/28, 12:13:55 »
Here it works with my Big Box, trying it with the lappy now too.
Regards
Reiner
slackware => SuSE => kanotix => sidux => aptosid  => siduction

Offline tommy2

  • User
  • Posts: 120
Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
« Reply #10 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.

Offline dibl

  • siduction community member
  • Global Moderator
  • User
  • *****
  • Posts: 1.927
    • Land of the Buckeye
Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
« Reply #11 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
Asus ROG STRIX X299-E, Core i7-7740X, Nvidia GTX-1060, dual monitors, SSD 860 EVO, 2@WD1003FZEX in BTRFS

Offline AvY

  • Newbie
  • Posts: 3
    • AvY Enterprises
Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
« Reply #12 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!

Offline dibl

  • siduction community member
  • Global Moderator
  • User
  • *****
  • Posts: 1.927
    • Land of the Buckeye
Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
« Reply #13 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.
Asus ROG STRIX X299-E, Core i7-7740X, Nvidia GTX-1060, dual monitors, SSD 860 EVO, 2@WD1003FZEX in BTRFS

Offline tommy2

  • User
  • Posts: 120
Re: linux-image-4.18.10-towo.2-siduction-amd64 does not boot
« Reply #14 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.