From: David Baron <d_baron@012.net.il>
To: linux-audio-user@lists.linuxaudio.org
Cc: linux-kernel@vger.kernel.org
Subject: RE: 2.6.21-rt7 Oopses
Date: Wed, 30 May 2007 18:00:29 +0300 [thread overview]
Message-ID: <200705301800.29903.d_baron@012.net.il> (raw)
Verrry eeeenteresting (showing my age):
Kdiff3 if fantastic. Looked at the entire source tree for -rt1 and -rt7. Found
nothing changed touching any of the "oopses" that I have seen. What has been
added, however, seems to be the trace-back code to display them. (Hypervisor
code has been removed but my PIII clunker has no kvm support in any event.)
Am I correct?
These displayed "oopses" are problematic or simply debugging messages?
They seem to not have effected anything outside of my log files :-)
Safe to ignore them and keep using -rt7 or wait on this?
reply other threads:[~2007-05-30 15:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200705301800.29903.d_baron@012.net.il \
--to=d_baron@012.net.il \
--cc=linux-audio-user@lists.linuxaudio.org \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®