Hi Peter,
On Mon, Feb 11, 2013 at 09:42:30AM -0500, Peter Hurley wrote:
> Can you reproduce after using the following patch series?
> [PATCH v3 00/23] ldisc fixes
>
I'm constantly seeing this warning on my board (imx6q - ARM Cortex-A9
Quad) with -next kernel, while I believe v3.8-rc kernel works
Hi Peter,
On Mon, Feb 11, 2013 at 09:42:30AM -0500, Peter Hurley wrote:
Can you reproduce after using the following patch series?
[PATCH v3 00/23] ldisc fixes
I'm constantly seeing this warning on my board (imx6q - ARM Cortex-A9
Quad) with -next kernel, while I believe v3.8-rc kernel works
On Tue, 2013-02-12 at 17:41 +1100, Michael Ellerman wrote:
> On Mon, Feb 11, 2013 at 09:53:58PM -0500, Peter Hurley wrote:
> > On Tue, 2013-02-12 at 13:00 +1100, Michael Ellerman wrote:
> > > > Can you reproduce after using the following patch series?
> > > > [PATCH v3 00/23] ldisc fixes
> > >
>
On Tue, 2013-02-12 at 17:41 +1100, Michael Ellerman wrote:
On Mon, Feb 11, 2013 at 09:53:58PM -0500, Peter Hurley wrote:
On Tue, 2013-02-12 at 13:00 +1100, Michael Ellerman wrote:
Can you reproduce after using the following patch series?
[PATCH v3 00/23] ldisc fixes
What are they
On Mon, Feb 11, 2013 at 09:53:58PM -0500, Peter Hurley wrote:
> On Tue, 2013-02-12 at 13:00 +1100, Michael Ellerman wrote:
> > > Can you reproduce after using the following patch series?
> > > [PATCH v3 00/23] ldisc fixes
> >
> > What are they against? I tried Linus' tree and linux-next but they
On Tue, 2013-02-12 at 13:00 +1100, Michael Ellerman wrote:
> Sorry I just mean I'm seeing the warning, I have no idea how.
Ok, no problem. I just got a little excited because that area of code
was hard to test adequately.
> > Can you reproduce after using the following patch series?
> > [PATCH
On Mon, Feb 11, 2013 at 09:42:30AM -0500, Peter Hurley wrote:
> Hi Michael,
>
> On Mon, 2013-02-11 at 13:44 +1100, Michael Ellerman wrote:
> > On Wed, Jan 30, 2013 at 01:33:57PM -0500, Peter Hurley wrote:
> > > On Sat, 2013-01-19 at 22:00 +0100, Jiri Slaby wrote:
> > > > On 01/18/2013 10:07 PM,
Hi Michael,
On Mon, 2013-02-11 at 13:44 +1100, Michael Ellerman wrote:
> On Wed, Jan 30, 2013 at 01:33:57PM -0500, Peter Hurley wrote:
> > On Sat, 2013-01-19 at 22:00 +0100, Jiri Slaby wrote:
> > > On 01/18/2013 10:07 PM, Greg Kroah-Hartman wrote:
> > > > Jiri, was there anything on the mailing
Hi Michael,
On Mon, 2013-02-11 at 13:44 +1100, Michael Ellerman wrote:
On Wed, Jan 30, 2013 at 01:33:57PM -0500, Peter Hurley wrote:
On Sat, 2013-01-19 at 22:00 +0100, Jiri Slaby wrote:
On 01/18/2013 10:07 PM, Greg Kroah-Hartman wrote:
Jiri, was there anything on the mailing list that I
On Mon, Feb 11, 2013 at 09:42:30AM -0500, Peter Hurley wrote:
Hi Michael,
On Mon, 2013-02-11 at 13:44 +1100, Michael Ellerman wrote:
On Wed, Jan 30, 2013 at 01:33:57PM -0500, Peter Hurley wrote:
On Sat, 2013-01-19 at 22:00 +0100, Jiri Slaby wrote:
On 01/18/2013 10:07 PM, Greg
On Tue, 2013-02-12 at 13:00 +1100, Michael Ellerman wrote:
Sorry I just mean I'm seeing the warning, I have no idea how.
Ok, no problem. I just got a little excited because that area of code
was hard to test adequately.
Can you reproduce after using the following patch series?
[PATCH v3
On Mon, Feb 11, 2013 at 09:53:58PM -0500, Peter Hurley wrote:
On Tue, 2013-02-12 at 13:00 +1100, Michael Ellerman wrote:
Can you reproduce after using the following patch series?
[PATCH v3 00/23] ldisc fixes
What are they against? I tried Linus' tree and linux-next but they
didn't
On Wed, Jan 30, 2013 at 01:33:57PM -0500, Peter Hurley wrote:
> On Sat, 2013-01-19 at 22:00 +0100, Jiri Slaby wrote:
> > On 01/18/2013 10:07 PM, Greg Kroah-Hartman wrote:
> > > Jiri, was there anything on the mailing list that I missed that should
> > > have resolved this issue? I thought it was
On Wed, Jan 30, 2013 at 01:33:57PM -0500, Peter Hurley wrote:
On Sat, 2013-01-19 at 22:00 +0100, Jiri Slaby wrote:
On 01/18/2013 10:07 PM, Greg Kroah-Hartman wrote:
Jiri, was there anything on the mailing list that I missed that should
have resolved this issue? I thought it was being
On Sat, 2013-01-19 at 22:00 +0100, Jiri Slaby wrote:
> On 01/18/2013 10:07 PM, Greg Kroah-Hartman wrote:
> > Jiri, was there anything on the mailing list that I missed that should
> > have resolved this issue? I thought it was being worked on, but I can't
> > seem to find any resolution at the
On Sat, 2013-01-19 at 22:00 +0100, Jiri Slaby wrote:
On 01/18/2013 10:07 PM, Greg Kroah-Hartman wrote:
Jiri, was there anything on the mailing list that I missed that should
have resolved this issue? I thought it was being worked on, but I can't
seem to find any resolution at the moment.
On 01/18/2013 10:07 PM, Greg Kroah-Hartman wrote:
> Jiri, was there anything on the mailing list that I missed that should
> have resolved this issue? I thought it was being worked on, but I can't
> seem to find any resolution at the moment.
Somebody had a patchset and promised to repost IIRC. I
On 01/18/2013 10:07 PM, Greg Kroah-Hartman wrote:
Jiri, was there anything on the mailing list that I missed that should
have resolved this issue? I thought it was being worked on, but I can't
seem to find any resolution at the moment.
Somebody had a patchset and promised to repost IIRC. I
On Fri, Jan 18, 2013 at 03:53:58PM -0500, Dave Jones wrote:
> On Wed, Jan 02, 2013 at 10:37:44AM -0500, Dave Jones wrote:
> > This happened a few times to my test boxes I left running over the
> holidays..
> >
> > [ 8419.797533] [ cut here ]
> > [ 8419.798341]
On Wed, Jan 02, 2013 at 10:37:44AM -0500, Dave Jones wrote:
> This happened a few times to my test boxes I left running over the holidays..
>
> [ 8419.797533] [ cut here ]
> [ 8419.798341] WARNING: at drivers/tty/tty_buffer.c:476
> flush_to_ldisc+0x1de/0x1f0()
> [
On Wed, Jan 02, 2013 at 10:37:44AM -0500, Dave Jones wrote:
This happened a few times to my test boxes I left running over the holidays..
[ 8419.797533] [ cut here ]
[ 8419.798341] WARNING: at drivers/tty/tty_buffer.c:476
flush_to_ldisc+0x1de/0x1f0()
[
On Fri, Jan 18, 2013 at 03:53:58PM -0500, Dave Jones wrote:
On Wed, Jan 02, 2013 at 10:37:44AM -0500, Dave Jones wrote:
This happened a few times to my test boxes I left running over the
holidays..
[ 8419.797533] [ cut here ]
[ 8419.798341] WARNING: at
This happened a few times to my test boxes I left running over the holidays..
[ 8419.797533] [ cut here ]
[ 8419.798341] WARNING: at drivers/tty/tty_buffer.c:476
flush_to_ldisc+0x1de/0x1f0()
[ 8419.800313] Hardware name: GA-MA78GM-S2H
[ 8419.800887] tty is NULL
[
This happened a few times to my test boxes I left running over the holidays..
[ 8419.797533] [ cut here ]
[ 8419.798341] WARNING: at drivers/tty/tty_buffer.c:476
flush_to_ldisc+0x1de/0x1f0()
[ 8419.800313] Hardware name: GA-MA78GM-S2H
[ 8419.800887] tty is NULL
[
24 matches
Mail list logo
