WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: call trace on shutdown /reboot  (Read 216 times)

Offline billium

  • WikiUser
  • *
  • Posts: 6
call trace on shutdown /reboot
« on: June 29, 2017, 12:12:22 PM »
I updated tinycore on a Pixie boot and now I get a call trace on shutdown. 
(copied core.gz and vmlinuz from the ISO boot and the optional files from ISO/cde/optional)

It works great during use :)

The orange text displayed:
Killing -o 1411 - o 1410 - o1413
block nbd0: Receive control failed (result -512)
block nbd0: shutting down socket
WARNING: CPU: 2 PID 1411 at kernel/softirq.c:150 0xc0141199
then a list of modules
CPU: 2 PID: 1411 Comm: nbd-client Not tainted 4.8.17-tinycore #2017
then some numbers follower by a call trace.
udevd[168]: worker [455] did not accept message -1 (Connection refused), kill it
udevd[168]: worker [456] did not accept message -1 (Connection refused), kill it

Terminating - o 1411 -o 1410 -o 1413 all processes.
block nbd0: Receive control failed (result -512)
block nbd0: shutting down socket
Unmounting all filesystems
Then in white
Kernel BUG at C0206618 [verbose debug info unavailable]
invalid opcode: 0000 [#1] SMP
list of modules again then registers, stack and call trace.

It then just does not shut down.

I does this on all hardware that boots from PXE.

Have I upgraded wrong?

Thanks

Offline Rich

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 5337
Re: call trace on shutdown /reboot
« Reply #1 on: June 29, 2017, 12:40:42 PM »
Hi billium
Maybe you have some extensions that are not compatible and also need updating?

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 9518
Re: call trace on shutdown /reboot
« Reply #2 on: June 30, 2017, 12:17:39 AM »
You've hit a kernel bug, so probably nothing you did. You could try more recent kernels if it bothers you, or trying to find if someone has a patch for it by searching the trace contents.
The only barriers that can stop you are the ones you create yourself.

Offline billium

  • WikiUser
  • *
  • Posts: 6
Re: call trace on shutdown /reboot
« Reply #3 on: June 30, 2017, 01:07:23 AM »
Thanks for the answers, it is all up to date, and there is not much loaded,  It doesn't bother me that much as the plug is pulled straight after ... just doesn't look as good!
I think the kernel bug is something to do with NBD.
I will check it out when I can, and see if the kernel can be replaced.

NBD now uses export name instead of port number, but I haven't found a way of doing that yet in the kernel command line, so I am still using:

Code: [Select]
APPEND initrd=tinycore/core.gz keymap=qwerty/uk superuser host=tcPixie1 nbd=192.168.3.200:12345  tce=nbd0

Thanks again for TinyCore.