Subj : gentoo profile 17 :=)
To   : Maurice Kinal
From : Benny Pedersen
Date : Sun Dec 24 2017 14:25:34

Hello Maurice!

21 Dec 2017 00:55, Maurice Kinal wrote to Benny Pedersen:

 BP>> i did see prink msgs with 4.14, maybe just fp warnings, dont
 BP>> know, but if this does not happen on 4.15 i am  happy its not
 BP>> fail of my own .config

 MK> I can relate.  On this system I have issues with the ast drm graphics 
 MK> which were working fine with 4.13 kernels.  However I decided to 
 MK> disable that and go back with vesafb and a standard resolution monitor 
 MK> on 4.14 kernels.

today tested with 4.14.8 get this:

   ----- kernel begins -----
Dec 24 13:28:20 themultixpoint kernel: INFO: rcu_sched detected stalls on
CPUs/tasks:
Dec 24 13:28:20 themultixpoint kernel: \x090-...: (1 GPs behind) idle=8a6/1/0
softirq=205303/205304 fqs=0 
Dec 24 13:28:20 themultixpoint kernel: \x09(detected by 1, t=4005 jiffies,
g=45017, c=45016, q=6)
Dec 24 13:28:20 themultixpoint kernel: Sending NMI from CPU 1 to CPUs 0:
Dec 24 13:28:20 themultixpoint kernel: NMI backtrace for cpu 0
Dec 24 13:28:20 themultixpoint kernel: CPU: 0 PID: 0 Comm: swapper/0 Not
tainted 4.14.8-gentoo-r1 #1
Dec 24 13:28:20 themultixpoint kernel: Hardware name: Dell Computer Corporation
 Dimension 8300               /0M2035, BIOS A05 02/23/2004
Dec 24 13:28:20 themultixpoint kernel: task: c1700600 task.stack: c16fa000
Dec 24 13:28:20 themultixpoint kernel: EIP: _raw_spin_lock_irq+0xe/0x30
Dec 24 13:28:20 themultixpoint kernel: EFLAGS: 00000046 CPU: 0
Dec 24 13:28:20 themultixpoint kernel: EAX: 00000000 EBX: 00000000 ECX:
00000001 EDX: f69b0f80
Dec 24 13:28:20 themultixpoint kernel: ESI: f6413fa0 EDI: f69b0f80 EBP:
f6413fcc ESP: f6413f8c
Dec 24 13:28:20 themultixpoint kernel:  DS: 007b ES: 007b FS: 00d8 GS: 0000 SS:
 0068
Dec 24 13:28:20 themultixpoint kernel: CR0: 80050033 CR2: 0055e300 CR3:
3507e000 CR4: 000006d0
Dec 24 13:28:20 themultixpoint kernel: Call Trace:
Dec 24 13:28:20 themultixpoint kernel:  <SOFTIRQ>
Dec 24 13:28:20 themultixpoint kernel:  ? run_timer_softirq+0x150/0x300
Dec 24 13:28:20 themultixpoint kernel:  ? run_rebalance_domains+0x15f/0x170
Dec 24 13:28:20 themultixpoint kernel:  ? blk_done_softirq+0x53/0x70
Dec 24 13:28:20 themultixpoint kernel:  __do_softirq+0xc2/0x1a2
Dec 24 13:28:20 themultixpoint kernel:  ?
smp_irq_move_cleanup_interrupt+0x150/0x150
Dec 24 13:28:20 themultixpoint kernel:  do_softirq_own_stack+0x1d/0x30
Dec 24 13:28:20 themultixpoint kernel:  </SOFTIRQ>
Dec 24 13:28:20 themultixpoint kernel:  irq_exit+0xa5/0xb0
Dec 24 13:28:20 themultixpoint kernel:  smp_apic_timer_interrupt+0x4c/0x80
Dec 24 13:28:20 themultixpoint kernel:  apic_timer_interrupt+0x35/0x3c
Dec 24 13:28:20 themultixpoint kernel: EIP: default_idle+0x5/0x10
Dec 24 13:28:20 themultixpoint kernel: EFLAGS: 00000246 CPU: 0
Dec 24 13:28:20 themultixpoint kernel: EAX: 80000000 EBX: 00000000 ECX:
00000001 EDX: 00000000
Dec 24 13:28:20 themultixpoint kernel: ESI: 00000000 EDI: c1700600 EBP:
c16fbf50 ESP: c16fbf50
Dec 24 13:28:20 themultixpoint kernel:  DS: 007b ES: 007b FS: 00d8 GS: 0000 SS:
 0068
Dec 24 13:28:20 themultixpoint kernel:  arch_cpu_idle+0x9/0x10
Dec 24 13:28:20 themultixpoint kernel:  default_idle_call+0x19/0x30
Dec 24 13:28:20 themultixpoint kernel:  do_idle+0x14d/0x170
Dec 24 13:28:20 themultixpoint kernel:  cpu_startup_entry+0x1d/0x20
Dec 24 13:28:20 themultixpoint kernel:  rest_init+0x8c/0x90
Dec 24 13:28:20 themultixpoint kernel:  start_kernel+0x2f9/0x2fe
Dec 24 13:28:20 themultixpoint kernel:  i386_start_kernel+0x95/0x99
Dec 24 13:28:20 themultixpoint kernel:  startup_32_smp+0x164/0x166
Dec 24 13:28:20 themultixpoint kernel: Code: 0a 85 c0 74 08 31 c0 5d c3 8d 74
26 00 b8 01 00 00 00 5d c3 89 f6 8d bc 27 00 00 00 00 89 c2 fa 31 c0 b9 01 00
00 00 f0 0f b1 0a <85> c0 75 06 c3 90 8d 74 26 00 55 89 d1 89 c2 89 c8 89 e5 e8
 9a
Dec 24 13:28:20 themultixpoint kernel: rcu_sched kthread starved for 4005
jiffies! g45017 c45016 f0x0 RCU_GP_WAIT_FQS(3) ->state=0x402 ->cpu=1
Dec 24 13:28:20 themultixpoint kernel: rcu_sched       I    0     8      2
0x80000000
Dec 24 13:28:20 themultixpoint kernel: Call Trace:
Dec 24 13:28:20 themultixpoint kernel:  __schedule+0x16d/0x590
Dec 24 13:28:20 themultixpoint kernel:  schedule+0x29/0x70
Dec 24 13:28:20 themultixpoint kernel:  schedule_timeout+0x105/0x240
Dec 24 13:28:20 themultixpoint kernel:  ? __next_timer_interrupt+0xc0/0xc0
Dec 24 13:28:20 themultixpoint kernel:  rcu_gp_kthread+0x440/0x760
Dec 24 13:28:20 themultixpoint kernel:  kthread+0xd1/0x100
Dec 24 13:28:20 themultixpoint kernel:  ? call_rcu_sched+0x20/0x20
Dec 24 13:28:20 themultixpoint kernel:  ? kthread_create_on_node+0x20/0x20
Dec 24 13:28:20 themultixpoint kernel:  ret_from_fork+0x19/0x24
   ----- kernel ends -----

4.15 fix this

 MK> To be honest I prefer standard resolution monitors so I got to use 
 MK> this as an excuse.  :-)

i like to get rid of vga framebuffers in initial boot, have forgot how to make
this into the boot line so it takes radeonfb always

 BP>> you loosed, i am not bigfoot (small memory footprint is my goal)

 MK> Understood.  However I don't plan to follow your lead as I like my 8 
 MK> penguins and 100M out of the available 32G is a very small price to 
 MK> pay to see those 8 penguins on bootup.

 MK> How many penguins do you get with your small footprint 22M's?

many as more then one :=)


 Regards Benny

.... there can only be one way of life, and it works :)

--- Msged/LNX 6.2.0 (Linux/4.14.8-gentoo-r1 (i686))
 * Origin: I will always keep a PC running CPM 3.0 (2:230/0)

.