Tried to reproduce this with: 1. NTP time sync set to false 2. Change the time to 23:57:00 3. Run the ubuntu_cts_kernel test and wait for the logrotate to kick in
I can't reproduce this issue in this way. However I got another i386 node running with B-hwe that failed with another systemd related task, after the ubuntu_cts_kernel test: Jan 25 04:17:35 pepe kernel: [ 304.413908] audit: type=1400 audit(1548389855.757:26): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/home/ubuntu/autotest/client/results/default/ubuntu_cts_kernel.lp1026116/sleep1" pid=4158 comm="apparmor_parser" Jan 25 04:17:36 pepe systemd-networkd[706]: gre_sys: Gained IPv6LL Jan 25 04:17:36 pepe systemd-timesyncd[568]: Network configuration changed, trying to establish connection. Jan 25 04:17:36 pepe systemd-timesyncd[568]: Synchronized to time server 10.246.72.3:123 (10.246.72.3). Jan 25 04:19:04 pepe kernel: [ 393.227539] BUG: unable to handle kernel paging request at 1cab2fe3 Jan 25 04:19:04 pepe kernel: [ 393.233797] *pdpt = 0000000025377001 *pde = 0000000000000000 Jan 25 04:19:04 pepe kernel: [ 393.239571] Oops: 0000 [#1] SMP Jan 25 04:19:04 pepe kernel: [ 393.242821] CPU: 3 PID: 7541 Comm: dpkg Not tainted 4.18.0-14-generic #15~18.04.1-Ubuntu Jan 25 04:19:04 pepe kernel: [ 393.250983] Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.8.2 08/17/2011 Jan 25 04:19:04 pepe kernel: [ 393.258544] EIP: __kmalloc+0xc7/0x240 Jan 25 04:19:04 pepe kernel: [ 393.262234] Code: 00 89 cb 89 4d e0 8d 4a 01 89 45 dc 31 c3 8b 45 f0 64 0f c7 0e 0f 94 c0 84 c0 74 bb 8b 45 dc 39 45 e0 8b 75 e4 74 0e 03 5f 14 <33> 1b 33 9f b4 00 00 00 0f 18 03 f7 45 ec 00 80 00 00 0f 85 41 01 Jan 25 04:19:04 pepe kernel: [ 393.281135] EAX: ee5c5263 EBX: 1cab2fe3 ECX: 00002502 EDX: 00002501 Jan 25 04:19:04 pepe kernel: [ 393.287401] ESI: eac03a00 EDI: eac03a00 EBP: e4c59d9c ESP: e4c59d74 Jan 25 04:19:04 pepe kernel: [ 393.293666] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00010202 Jan 25 04:19:04 pepe kernel: [ 393.300531] CR0: 80050033 CR2: 1cab2fe3 CR3: 2a362f80 CR4: 000006f0 Jan 25 04:19:04 pepe kernel: [ 393.306900] Call Trace: Jan 25 04:19:04 pepe kernel: [ 393.309346] ? ext4_htree_store_dirent+0x31/0x120 Jan 25 04:19:04 pepe kernel: [ 393.314105] ext4_htree_store_dirent+0x31/0x120 Jan 25 04:19:04 pepe kernel: [ 393.318680] htree_dirblock_to_tree+0xd2/0x240 Jan 25 04:19:04 pepe kernel: [ 393.323162] ? terminate_walk+0x95/0x100 Jan 25 04:19:04 pepe kernel: [ 393.327102] ext4_htree_fill_tree+0x93/0x2b0 Jan 25 04:19:04 pepe kernel: [ 393.331412] ? kmem_cache_alloc_trace+0x167/0x1e0 Jan 25 04:19:04 pepe kernel: [ 393.336149] ? ext4_readdir+0x9bd/0xb00 Jan 25 04:19:04 pepe kernel: [ 393.340033] ext4_readdir+0x718/0xb00 Jan 25 04:19:04 pepe kernel: [ 393.343711] ? security_file_permission+0x93/0xb0 Jan 25 04:19:04 pepe kernel: [ 393.348458] iterate_dir+0x8d/0x190 Jan 25 04:19:04 pepe kernel: [ 393.351977] ksys_getdents64+0x6f/0x100 Jan 25 04:19:04 pepe kernel: [ 393.355858] ? iterate_dir+0x190/0x190 Jan 25 04:19:04 pepe kernel: [ 393.359629] sys_getdents64+0x16/0x20 Jan 25 04:19:04 pepe kernel: [ 393.363330] do_fast_syscall_32+0x7f/0x1e0 Jan 25 04:19:04 pepe kernel: [ 393.367448] entry_SYSENTER_32+0x4e/0x7c Jan 25 04:19:04 pepe kernel: [ 393.371423] EIP: 0xb7f7ed09 Jan 25 04:19:04 pepe kernel: [ 393.374239] Code: 08 8b 80 5c cd ff ff 85 d2 74 02 89 02 5d c3 8b 04 24 c3 8b 0c 24 c3 8b 1c 24 c3 8b 3c 24 c3 90 90 51 52 55 89 e5 0f 34 cd 80 <5d> 5a 59 c3 90 90 90 90 8d 76 00 58 b8 77 00 00 00 cd 80 90 8d 76 Jan 25 04:19:04 pepe kernel: [ 393.393185] EAX: ffffffda EBX: 00000008 ECX: 00cc774c EDX: 00008000 Jan 25 04:19:04 pepe kernel: [ 393.399537] ESI: ffffff3c EDI: b7cce780 EBP: 00cc7730 ESP: bfaf4048 Jan 25 04:19:04 pepe kernel: [ 393.405881] DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 007b EFLAGS: 00000296 Jan 25 04:19:04 pepe kernel: [ 393.412711] Modules linked in: iptable_nat ip_gre gre ip_tunnel dummy iptable_filter xt_recent bpfilter openvswitch nsh nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_conncount nf_nat nf_conntrack intel_powerclamp coretemp kvm_intel ipmi_ssif kvm irqbypass acpi_power_meter gpio_ich intel_cstate ipmi_si ipmi_devintf dcdbas ipmi_msghandler mac_hid lpc_ich i7core_edac sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mgag200 i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops mpt3sas drm raid_class pata_acpi Jan 25 04:19:04 pepe kernel: [ 393.483766] bnx2 scsi_transport_sas Jan 25 04:19:04 pepe kernel: [ 393.487357] CR2: 000000001cab2fe3 Jan 25 04:19:04 pepe kernel: [ 393.490793] ---[ end trace 22a42d3ce8b6aea9 ]--- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813244 Title: systemd logrotate cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
