Warning: (1048) Column 'xxxxxxx' cannot be null

Weired behavior occured which lock situation from 10.11.11.
What should be a solution or next further step about below sypmptom.

• Before 10.11.11, no issue. same simple INSERT INTO ON UPDATE query in Stored procedure.
• Within the stored procedure there are
  > insert into _the_temp_table select something from main_real_table
  > insert into main_real_table select from _the_temp_table on key duplicated update ....
  > at this point, if select two or more rows from _the_temp_table, `Warning: (1048) Column 'xxxxxxx' cannot be null` for all columns
  > In the first place, _the_temp_table have fully filled values even 0(zero). Non of null allowed.
  > no tracaction settup, single transaction, split transaction setup shows same result by manual execution from mariadb console/command line, heidlasql, any, same.
  > Single row working perfect. two or more rows make the error under the same queries/SP.

From an internet articles, someone say DRY/SRT matter make the same issue.
But as I explain above you, that is not same table.(to me. Am I something wrong?)
To resolve what should I do? Config check? Optimizer adjust?(then how?)
Any advice needed.