Messages in this thread | | | Date | Sun, 20 Jan 2013 00:06:16 +0100 | Subject | Re: [next-20130118] Analyzing a call-trace reproducible with pm_test/freezer [ X86|RCU|TTY|EXT4FS|JBD2|PM related? ] | From | Sedat Dilek <> |
| |
On Sat, Jan 19, 2013 at 11:59 PM, Sedat Dilek <sedat.dilek@gmail.com> wrote: > On Sat, Jan 19, 2013 at 11:56 PM, Ilya Zykov <ilya@ilyx.ru> wrote: >> On 20.01.2013 2:51, Sedat Dilek wrote: >>> On Sat, Jan 19, 2013 at 11:43 PM, Ilya Zykov <ilya@ilyx.ru> wrote: >>>> Hello! >>>> I don't expert, but >>>> maybe it can help. >>>> >>>> I test with: >>>> while echo mem > /sys/power/state; do sleep 2; done >>>> in one X-terminal, in other I trying playing with keyboard. >>>> (Without playing all right I use ext3.) >>> >>> Can you test with the patches listed in [1] (including two TTY patches >>> from you!)? >>> My base is Linux-Next (next-20130118). >>> FYI: My Ubuntu/precise is EXT4FS-formatted. >>> >> Ok. >> but not now I have 3.00 night. >> I already use this in my 3.8.0-rc3-next-20130118-pm+. >> tty: Correct tty buffer flush. >> > > The TTY patches are not enough, you need in addition the JBD2 fix [1]. >
Attached is a testcase script which helped here to hit the issue!
- Sedat -
> - Sedat - > > [1] http://patchwork.ozlabs.org/patch/207237/ > >> [unhandled content-type:application/x-sh] | |