From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Fri, 12 Dec 2003 15:19:26 +0000 (GMT) Received: from smtp.golden.net ([IPv6:::ffff:199.166.210.31]:47111 "EHLO newsmtp.golden.net") by linux-mips.org with ESMTP id ; Fri, 12 Dec 2003 15:19:25 +0000 Received: from as53-01-51.cas-ham.golden.net ([216.208.82.51] helo=unusual.internal.linux-sh.org) by newsmtp.golden.net with esmtp (Exim 4.22) id 1AUp4W-000LrZ-N1; Fri, 12 Dec 2003 10:19:17 -0500 Received: by unusual.internal.linux-sh.org (Postfix, from userid 500) id 4F7B2D7BF; Fri, 12 Dec 2003 10:19:14 -0500 (EST) Date: Fri, 12 Dec 2003 10:19:14 -0500 From: Paul Mundt To: uClinux development list Cc: Alan Cox , "Steven J. Hill" , mips Subject: Re: [uClinux-dev] Re: Network problem in mips Message-ID: <20031212151914.GA21619@linux-sh.org> Mail-Followup-To: Paul Mundt , uClinux development list , Alan Cox , "Steven J. Hill" , mips References: <008f01c3bff7$252e3b40$0a05a8c0@DURAI> <3FD88C4D.6010700@realitydiluted.com> <1071184052.19738.12.camel@dhcp23.swansea.linux.org.uk> <20031211233058.GB20373@linux-mips.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EVF5PPMfhYS0aIcm" Content-Disposition: inline In-Reply-To: <20031211233058.GB20373@linux-mips.org> User-Agent: Mutt/1.4.1i Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 3746 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: lethal@linux-sh.org Precedence: bulk X-list: linux-mips --EVF5PPMfhYS0aIcm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Dec 12, 2003 at 12:30:58AM +0100, Ralf Baechle wrote: > > Seems a little out of order. Not everyone immediately understands you > > need the ksyms to interpret a trace >=20 > Guess that should be mentioned in the FAQ - anybody got a pointer to a > little how to for writing useful bug reports? >=20 What's wrong with the top-level REPORTING-BUGS? This specifically mentions the need for oops tracing with pointers to relevant documentation prior to posting the report. --EVF5PPMfhYS0aIcm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/2dxy1K+teJFxZ9wRAmNeAKCE1gI7UyWpvm/QoXmtUsAfBjawLACdGE01 EWhVkp8vy6JYybmo4czCUXI= =DXkF -----END PGP SIGNATURE----- --EVF5PPMfhYS0aIcm--