From: Boaz Harrosh <bharrosh@panasas.com>
To: Richard Weinberger <richard@nod.at>
Cc: uml-devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] sysreq t back traces stopped working please help
Date: Thu, 27 Feb 2014 21:52:12 +0200 [thread overview]
Message-ID: <530F976C.2090400@panasas.com> (raw)
In-Reply-To: <530F9126.2030206@panasas.com>
On 02/27/2014 09:25 PM, Boaz Harrosh wrote:
> On 02/27/2014 09:16 PM, Richard Weinberger wrote:
>> Hi!
>>
>> Am 27.02.2014 20:05, schrieb Boaz Harrosh:
>>> 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.
>
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
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2014-02-27 19:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 19:05 [uml-devel] sysreq t back traces stopped working please help Boaz Harrosh
2014-02-27 19:16 ` Richard Weinberger
2014-02-27 19:25 ` Boaz Harrosh
2014-02-27 19:52 ` Boaz Harrosh [this message]
2014-02-27 19:22 ` Richard Weinberger
2014-02-27 19:28 ` Boaz Harrosh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=530F976C.2090400@panasas.com \
--to=bharrosh@panasas.com \
--cc=richard@nod.at \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.