* RE: disk thread problem when using RT-kernel
@ 2011-02-03 20:50 Victor henri
2011-02-03 21:02 ` Nathan Grennan
0 siblings, 1 reply; 5+ messages in thread
From: Victor henri @ 2011-02-03 20:50 UTC (permalink / raw
To: linux-rt-users
Hello
I'm back after some testing.... and it is a complete mess; actually there is more than that just problems with linuxsampler.... with every RT kernel greater than 2.6.31.12 (i started seeing it on gentoo), i have total system freeze... after a few minutes.... to the point that i have to force shut down the system without proper shutdown (i hate doing that); i have installed "das-watchdog" and see the pop-up window saying that das watchdog has disabled real-time for 8 seconds... and this pop-up appears every 8 sec... (forever)... everything happen before i have time to play a single note....
This old problem is coming again... and i've open a new subject to solve this first
Vic
> Date: Mon, 31 Jan 2011 13:17:49 -0200
> From: lclaudio@uudg.org
> To: nadaeck@hotmail.com
> CC: linux-rt-users@vger.kernel.org
> Subject: Re: disk thread problem when using RT-kernel
>
> On Mon, Jan 31, 2011 at 03:16:37PM +0100, Victor henri wrote:
> |
> | Hello Daniel and Luis
> |
> | - Yes i'm using the rtirq script;
> |
> | - I'm using the latest version of linuxsampler 1.0.0 (in Gentoo : from
> | pro-audio overlay; in Ubuntu : not in the repositories so I compile it
> | myself, after taking it on the linuxsampler website); same for libgig
> | (dependency of linuxsampler);
>
> Have you tried running linuxsample at a higher priority? I would try
> running it as sched_fifo, priority 60 or 70. You can use 'chrt' to achieve
> that.
>
> | - I'll have a look at hwlat_detector; it seems not to be in the
> | repositories in Ubuntu; i'll be searching;
>
> hwlat_detector is a kernel module. You just have to load the module and
> tweak the values (though IIRC the defaults are sane) and let it run for a
> while (at least 2h).
>
> | - regarding the logs of the USB, how can I do it please? I'm using an
> | external USB sound card (a M-Audio Fast Track Pro); the keybord is
> | connected to the card via midi.
>
> Have a look at /var/log/messages and dmesg and see if anything suspect
> catches your eyes :)
>
> Regards,
> Luis
> --
> [ Luis Claudio R. Goncalves Bass - Gospel - RT ]
> [ Fingerprint: 4FDD B8C4 3C59 34BD 8BE9 2696 7203 D980 A448 C8F8 ]
>
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: disk thread problem when using RT-kernel
2011-02-03 20:50 disk thread problem when using RT-kernel Victor henri
@ 2011-02-03 21:02 ` Nathan Grennan
2011-02-03 21:34 ` disk thread problem when using RT kernel Victor henri
0 siblings, 1 reply; 5+ messages in thread
From: Nathan Grennan @ 2011-02-03 21:02 UTC (permalink / raw
To: linux-rt-users
On 02/03/2011 12:50 PM, Victor henri wrote:
> Hello
>
> I'm back after some testing.... and it is a complete mess; actually there is more than that just problems with linuxsampler.... with every RT kernel greater than 2.6.31.12 (i started seeing it on gentoo), i have total system freeze... after a few minutes.... to the point that i have to force shut down the system without proper shutdown (i hate doing that); i have installed "das-watchdog" and see the pop-up window saying that das watchdog has disabled real-time for 8 seconds... and this pop-up appears every 8 sec... (forever)... everything happen before i have time to play a single note....
> This old problem is coming again... and i've open a new subject to solve this first
It sounds like you are running into the same problem I did a while
back. I never got to the bottom of it. I am waiting for the 2.6.37-rt
kernel. See my thread below.
http://www.spinics.net/lists/linux-rt-users/msg06248.html
^ permalink raw reply [flat|nested] 5+ messages in thread
* RE: disk thread problem when using RT kernel
2011-02-03 21:02 ` Nathan Grennan
@ 2011-02-03 21:34 ` Victor henri
0 siblings, 0 replies; 5+ messages in thread
From: Victor henri @ 2011-02-03 21:34 UTC (permalink / raw
To: linux-rt-users
Hello
So if i understand well 'soft lock' is what i have described in my post, and what you were experiencing.
The only solution is to wait then?
Thank you for your answer
Victor
----------------------------------------
> Date: Thu, 3 Feb 2011 13:02:38 -0800
> From: linux-rt-users@cygnusx-1.org
> To: linux-rt-users@vger.kernel.org
> Subject: Re: disk thread problem when using RT-kernel
>
> On 02/03/2011 12:50 PM, Victor henri wrote:
> > Hello
> >
> > I'm back after some testing.... and it is a complete mess; actually there is more than that just problems with linuxsampler.... with every RT kernel greater than 2.6.31.12 (i started seeing it on gentoo), i have total system freeze... after a few minutes.... to the point that i have to force shut down the system without proper shutdown (i hate doing that); i have installed "das-watchdog" and see the pop-up window saying that das watchdog has disabled real-time for 8 seconds... and this pop-up appears every 8 sec... (forever)... everything happen before i have time to play a single note....
> > This old problem is coming again... and i've open a new subject to solve this first
> It sounds like you are running into the same problem I did a while
> back. I never got to the bottom of it. I am waiting for the 2.6.37-rt
> kernel. See my thread below.
>
> http://www.spinics.net/lists/linux-rt-users/msg06248.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 5+ messages in thread
* RE: disk thread problem when using RT kernel
@ 2011-02-04 1:13 Victor henri
0 siblings, 0 replies; 5+ messages in thread
From: Victor henri @ 2011-02-04 1:13 UTC (permalink / raw
To: linux-rt-users
Hello Carsten
> Date: Thu, 3 Feb 2011 23:26:51 +0100
> From: C.Emde@osadl.org
> To: nadaeck@hotmail.com
> Subject: Re: disk thread problem when using RT kernel
>
> Victor,
>
>> So if i understand well 'soft lock' is what i have described in my
>> post, and what you were experiencing.
>>
>> The only solution is to wait then?
> No, there is much more you can do. If you are willing to help in a
> constructive way and provide traces and other debug material, we will be
> glad to assist you to locate and fix your problem. Up to now, we are not
> aware of any problem in the 2.6.33.7.2-rt30 "Latest Stable" real-time
> kernel version (osadl.org/Latest-Stable), since it underwent more than
> three months of heavy testing in our QA farm (osadl.org/QA). In general,
> it is a good idea to follow Alan Cox's recommendations on how to post to
> a mailing list ->
> https://www.osadl.org/Eric-Raymond-How-to-ask-questions-the-s.questions-the-smart-way.0.html
Sure I'm willing to help; thank you for your help;
>
> 1. Do not top-post; if you do, you will get much less help than you
> would otherwise -> http://www.catb.org/~esr/jargon/html/T/top-post.html.
Understood; i won't
>
> 2. Enable System Request (SysRq)
> Edit /etc/sysctl.conf and change
> kernel.sysrq = 0
> to
> kernel.sysrq = 1
kernel.sysrq = 0 was not in /etcsysctl.conf, so I added manually kernel.sysrq = 1 in the file
> This will enable SysRq at next reboot. To enable it while the computer
> is running, type
> echo 1>/proc/sys/kernel/sysrq
> When SysRq is activated, the key combination Right-Alt/SysRq/ becomes
> available. The SysRq key is the leftmost key of the group of three keys
> to the right of F12. It is normally labeled "PrntScr" above and "SysRq"
> below. You need to type the three keys altogether. The command
> Right-Alt/SysRq/H, for example, displays help information, i.e. a list
> of the various available commands. To try it out, type Right-Alt, then
> type SysRq while you hold Right-Alt, then type H while you continue to
> hold Right-Alt and SysRq. Hint: this may not work under a window
> manager, since the key combination is filtered out. Use a virtual
> console (Control/Left-Alt/F1). After you typed Right-Alt/SysRq/H, the
> help info will be appended to the system log file such as:
>
> # tail -1 /var/log/messages
> kernel: SysRq : HELP : loglevel(0-9) reBoot Crash terminate-all-tasks(E)
> memory-full-oom-kill(F) kill-all-tasks(I) thaw-filesystems(J) saK
> show-backtrace-all-active-cpus(L) show-memory-usage(M)
> nice-all-RT-tasks(N) powerOff show-registers(P) show-all-timers(Q) unRaw
> Sync show-task-states(T) Unmount show-blocked-tasks(W)
> dump-ftrace-buffer(Z)
It worked
>
> The Key combination S-U-B (Right-Alt/SysRq/S - Right-Alt/SysRq/U -
> Right-Alt/SysRq/B) is worth to remember - in many cases, it will reboot
> a crashed system gracefully, since it flushes the disk cache, unmounts
> the disk and then reboots the system. You will no longer hate to do a
> forced shutdown of the system.
>
> When the system "hangs", the commands Right-Alt/SysRq/L,
> Right-Alt/SysRq/M, Right-Alt/SysRq/T etc. may be helpful to check out
> what the system is doing when the system has crashed and there is hope
> it still has some life in it.
>
> 3. Enable a serial console
> To print system and kernel messages, add
> ignore_log_level earlyprintk=ttyS0,115200
> and
> console=ttyS0,115200 console=tty0
> to the kernel boot parameters. Connect the system under test to another
> computer (use a null-modem cable) and minicom to it. If the system does
> not have a serial interface, but has an empty PCI slot, consider to
> purchase a PCI serial adapter. They are available for less than $25
> (US). When the system hangs, the serial console may contain useful
> information such as kernel crash dumps.
>
> 4. Next time you post a bug report, please provide the debug and trace
> information that you were able to generate from the output of the serial
> console or from SysRq.
>
>
> Hope this helps,
>
> Carsten.
Thanks i'll try do all that;
PS Please one more thing : before i understand that Right-Alt had to be
replaced (in my case) by AltGr, I've been trying different combination
of keys (right, arrow, Left-Alt, and others); right away i was off
connection and i have bit networking problems on the whole pc : wireless
is disabled, and eth0 is gone; fortunately, i can connect on eth1; this
happens **on the whole laptop** (even my other ubuntu on another disk
partition, or the ubuntu from the live usb stick have the same problem;
it's like the previous network interface has been "burned"...); this
happened just after the combination key test... I'll post it somewhere
else where it is more appropriate, but i just wanted to ask if it
sounded familiar...
Thanks again
Victor
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 5+ messages in thread
* RE: disk thread problem when using RT kernel
[not found] ` <4D4C47FC.2080100@osadl.org>
@ 2011-02-04 19:18 ` Victor henri
0 siblings, 0 replies; 5+ messages in thread
From: Victor henri @ 2011-02-04 19:18 UTC (permalink / raw
To: linux-rt-users
Hello Carsten
> Date: Fri, 4 Feb 2011 19:39:56 +0100
> From: C.Emde@osadl.org
> To: nadaeck@hotmail.com
> Subject: Re: disk thread problem when using RT kernel
>
> Victor,
>
> > [..] When I got soft lock (it happen very quickly), I typed
> > AltGr/PrintScr/L, */M and */T, but only */L gave me something on the
> > screen; so i got a file called /var/log/messages; i'll allow myself
> > to send it to your mail directly
> Yes, this would have been ok.
>
> I had a quick look at your kernel messages. Are you sure that you are
> using a real-time kernel?
Yew I've I have booted on on the rt kernel; when I type : uname -r, i get : 2.6.33.7.2-rt30 (on the tested laptop)
>
> I did a
> # grep "Linux version" messages.txt
> and all I could see was the SMP flag but no PREEMPT and no RT flag. So
> your problem is likely not RT-related.
>
> In addition, I found
> # grep Tainted messages.txt
> which gave a lot of "Tainted: P".
>
> Please refer to Documentation/oops-tracing.txt in the kernel tree
> (towards the end of the file). As you can see, "P" means that a
> proprietary module was loaded. Please understand that the community
> cannot assist you. You may try to contact the vendor for support or use
> a community driver and check whether the problem persists.
I've checked : indeed only the 2.6.35-generic appears, whichis the kernel of the pc that i'm using to watch the laptop under testing (and yes i have proprietary driver on it); in other terms, i didn't manage to have a working connection with the pc under testing; i'll search to have it working and then post it the log message , after i have verified that the right kernel appears in the file, if you agree of course; i'm sorry for the trouble; all of this is brand new to me.
>
> -Carsten.
thank you for your kind help
Victor
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2011-02-04 19:18 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-02-03 20:50 disk thread problem when using RT-kernel Victor henri
2011-02-03 21:02 ` Nathan Grennan
2011-02-03 21:34 ` disk thread problem when using RT kernel Victor henri
-- strict thread matches above, loose matches on Subject: below --
2011-02-04 1:13 Victor henri
[not found] <SNT110-W34A9D54FBCD3910233EA5A8E60@phx.gbl>
[not found] ` <4D4C47FC.2080100@osadl.org>
2011-02-04 19:18 ` Victor henri
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.