[uml-devel] sysreq t back traces stopped working please help

Boaz Harrosh

author

2014-02-27 19:05 UTC #0 lore raw

Hi Richard, uml hackers

Since some time my "echo t > /proc/sysrq-trigger" stopped producing the proper global back-traces for all Kernel threads. All I get is:

Feb 27 12:47:32 fc18-buml18 kernel: [189390.940000]      ksoftirqd/0     3     58344.325336    124146   120               0               0               0.000000               0.000000     
          0.000000 /
Feb 27 12:47:32 fc18-buml18 kernel: [189390.940000]     kworker/0:0H     5      3160.151405         5   100               0               0               0.000000               0.000000     
          0.000000 /
Feb 27 12:47:32 fc18-buml18 kernel: [189390.940000]          khelper     7         8.451419         2   100               0               0               0.000000               0.000000     
          0.000000 /
Feb 27 12:47:32 fc18-buml18 kernel: [189390.940000]        kdevtmpfs     8      5439.251379       169   120               0               0               0.000000               0.000000     
          0.000000 /
Feb 27 12:47:32 fc18-buml18 kernel: [189390.940000]            netns     9        10.451418         2   100               0               0               0.000000               0.000000     
          0.000000 /
Feb 27 12:47:32 fc18-buml18 kernel: [189390.940000]        writeback    37        13.451416         2   100               0               0               0.000000               0.000000     
          0.000000 /
Feb 27 12:47:32 fc18-buml18 kernel: [189390.940000]           bioset    39        12.451417         2   100               0               0               0.000000               0.000000     
          0.000000 /
Feb 27 12:47:32 fc18-buml18 kernel: [189390.940000]          kblockd    41        11.951416         2   100               0               0               0.000000               0.000000     
          0.000000 /
Feb 27 12:47:32 fc18-buml18 kernel: [189390.940000]          kswapd0    66        22.451413         3   120               0               0               0.000000               0.000000     
          0.000000 /
Feb 27 12:47:32 fc18-buml18 kernel: [189390.940000]    fsnotify_mark    67      1686.151405         6   120               0               0               0.000000               0.000000     
          0.000000 /
Feb 27 12:47:32 fc18-buml18 kernel: [189390.940000]          deferwq   219        25.451413         2   100               0               0               0.000000               0.000000     
          0.000000 /
Feb 27 12:47:32 fc18-buml18 kernel: [189390.940000]      jbd2/ubda-8   220     58318.325347       330   120               0               0               0.000000               0.000000     
          0.000000 /
Feb 27 12:47:32 fc18-buml18 kernel: [189390.940000]  ext4-rsv-conver   221        24.951412         2   100               0               0               0.000000               0.000000     
          0.000000 /
Feb 27 12:47:32 fc18-buml18 kernel: [189390.940000]  systemd-journal   233      2254.451426       466   120               0               0               0.000000               0.000000     
          0.000000 /system/systemd-journald.service
Feb 27 12:47:32 fc18-buml18 kernel: [189390.940000]    systemd-udevd   238       426.451404       696   120               0               0               0.000000               0.000000     
          0.000000 /system/systemd-udevd.service
Feb 27 12:47:32 fc18-buml18 kernel: [189390.940000]         rsyslogd   485       447.701421        38   120               0               0               0.000000               0.000000     
          0.000000 /system/rsyslog.service
Feb 27 12:47:32 fc18-buml18 kernel: [189390.940000]      in:imuxsock   549       447.701421       221   120               0               0               0.000000               0.000000     
          0.000000 /system/rsyslog.service
Feb 27 12:47:32 fc18-buml18 kernel: [189390.940000]        in:imklog   550       447.701421        29   120               0               0               0.000000               0.000000     
          0.000000 /system/rsyslog.service
Feb 27 12:47:32 fc18-buml18 kernel: [189390.940000]    rs:main Q:Reg   551       450.701421       255   120               0               0               0.000000               0.000000     
          0.000000 /system/rsyslog.service
Feb 27 12:47:32 fc18-buml18 kernel: [189390.940000]   systemd-logind   486      1540.451422       282   120               0               0               0.000000               0.000000     
          0.000000 /system/systemd-logind.service

	..... etc ...

Single line statistics per thread. I'm based on "make defconfig" plus some additional "YESs". Is there something more (new) I need to set to get this working? If not do you have a theory or I should start bisecting?

(Using Fedora 18 um image, on Fedora 18 host 64bit both)

Thanks lots in advance
Boaz

------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
User-mode-linux-devel mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

Richard Weinberger

maintainer

2014-02-27 19:16 UTC #1 lore raw

Hi!

Am 27.02.2014 20:05, schrieb Boaz Harrosh:

Quoted 4 lines

Hi Richard, uml hackers
Since some time my "echo t > /proc/sysrq-trigger" stopped producing the proper global back-traces for all Kernel threads. All I get is:

"some time" is a bit vague. Do you have more details?

Thanks,
//richard

------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
User-mode-linux-devel mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

Boaz Harrosh

author

2014-02-27 19:25 UTC #2 lore raw

Quoted 10 lines · Richard Weinberger

Hi!
Am 27.02.2014 20:05, schrieb Boaz Harrosh:
Quoted 4 lines
Hi Richard, uml hackers
Since some time my "echo t > /proc/sysrq-trigger" stopped producing the proper global back-traces for all Kernel threads. All I get is:
"some time" is a bit vague. Do you have more details?

OK I've found my problem Da. It all goes to con0 and not at all to /var/log/messages (Fedora) I'll recheck my log levels I see in code KERN_INFO so i do think it should appear but I'll recheck.

Which brings me back to my original problem with my UML setup that Fedora absolutely refuses to use con0= as its main prompt and will only use con1= So I need to now chose what will go to my bash console, the Kernel console output (printk(s)), or Fedora main prompt. Nothing I tried would combine them both. Like it used to be before.

[ Here is what I use:
option 1: vmlinux con0=fd:0,fd:1 con=pts (Will only send printk, invoking console becomes read-only) option 2: vmlinux con1=fd:0,fd:1 con=pts (invoking console becomes UML's main console RW. printk through
log file only, bad for postmortem)

I'll use option 1 for now, so thanks
Boaz

Quoted 3 lines

Thanks,
//richard

------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
User-mode-linux-devel mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

Boaz Harrosh

author

2014-02-27 19:52 UTC #3 lore raw

Quoted 9 lines · Boaz Harrosh

Quoted 8 lines · Richard Weinberger
Hi!
Am 27.02.2014 20:05, schrieb Boaz Harrosh:
Quoted 4 lines
Hi Richard, uml hackers
Since some time my "echo t > /proc/sysrq-trigger" stopped producing the proper global back-traces for all Kernel threads. All I get is:

Quoted 7 lines

Quoted 2 lines
"some time" is a bit vague. Do you have more details?
OK I've found my problem Da. It all goes to con0 and not at all to /var/log/messages (Fedora) I'll recheck my log levels I see in code KERN_INFO so i do think it should appear but I'll recheck.

OK I do not understand. I do see my KERN_DEBUG level at /var/log/messages say from nfs.ko (dprintk) But I do not see these backtrace output at /var/log/messages.

At con0 I see everything.

Thanks
Boaz

------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
User-mode-linux-devel mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

Richard Weinberger

maintainer

2014-02-27 19:23 UTC #4 lore raw

In reply to Boaz Harrosh

Am 27.02.2014 20:05, schrieb Boaz Harrosh:

Quoted 4 lines

Hi Richard, uml hackers
Since some time my "echo t > /proc/sysrq-trigger" stopped producing the proper global back-traces for all Kernel threads. All I get is:

I have an idea, do you see this regression starting with v3.12?

Thanks,
//richard

------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
User-mode-linux-devel mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

Boaz Harrosh

author

2014-02-27 19:28 UTC #5 lore raw

Quoted 5 lines · Richard Weinberger

Am 27.02.2014 20:05, schrieb Boaz Harrosh:
Quoted 2 lines
Hi Richard, uml hackers

Quoted 8 lines

Quoted 2 lines
Since some time my "echo t > /proc/sysrq-trigger" stopped producing the proper global back-traces for all Kernel threads. All I get is:
I have an idea, do you see this regression starting with v3.12?
Thanks,
//richard

Yes. You are right since 3.12 Yes. 3.11 is like before. But please see my other mail it has more info.

Thanks, sir
Boaz

------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
User-mode-linux-devel mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel