From: Russell King <rmk@arm.linux.org.uk>
To: Thomas Molina <tmolina@cox.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5 Problem Report Status for 10 Nov
Date: Sun, 10 Nov 2002 17:02:19 +0000 [thread overview]
Message-ID: <20021110170219.A15424@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0211100834110.16968-100000@dad.molina>; from tmolina@cox.net on Sun, Nov 10, 2002 at 10:31:56AM -0600
On Sun, Nov 10, 2002 at 10:31:56AM -0600, Thomas Molina wrote:
> ------------------------------------------------------------------------
> open 23 Oct 2002 2.5.x and 8250 UART problems
> 18. http://marc.theaimsgroup.com/?l=linux-kernel&m=103383019409525&w=2
No movement, and I don't particular see there's going to be any movement
on this one. There are too many variables that changed around the time
that the serial code went in to allow the cause to be isolated.
> ------------------------------------------------------------------------
> open 15 Oct 2002 oops stopping serial
> 36. http://marc.theaimsgroup.com/?l=linux-kernel&m=103470900729987&w=2
Fixed.
> ------------------------------------------------------------------------
> open 24 Oct 2002 serial driver bug with asus motherboard
> 67. http://marc.theaimsgroup.com/?l=linux-kernel&m=103548912126308&w=2
Awaiting feedback from Andrew Walrond; the code as of 2.5.46 allows
better remote debugging of wrong/mis-detections.
> ------------------------------------------------------------------------
> open 07 Nov 2002 odd deref in serial_in
> 84. http://marc.theaimsgroup.com/?l=linux-kernel&m=103647077515688&w=2
Not my problem - it looks like something else is trampling on %ebx,
although Zwane/myself are at a loss to locate the cause of that.
(%ebx = "up" pointer, which must have been valid a few instructions
previous to even get to this point in the code. Could it be a compiler
bug?)
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2002-11-10 16:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-10 16:31 2.5 Problem Report Status for 10 Nov Thomas Molina
2002-11-10 17:02 ` Russell King [this message]
2002-11-10 17:22 ` Roman Zippel
2002-11-10 17:32 ` Robert Love
2002-11-10 21:31 ` James Simmons
2002-11-11 13:33 ` Greg Boyce
2002-11-11 19:11 ` Gcc k6 testing account
2002-11-12 20:47 ` Mikael Pettersson
2002-11-12 23:47 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2002-11-10 17:12 Andries.Brouwer
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=20021110170219.A15424@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=tmolina@cox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox