From: Miles Lane <miles@megapathdsl.net>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: "Albert D. Cahalan" <acahalan@cs.uml.edu>,
Manfred Spraul <manfred@colorfullife.com>,
lm@bitmover.com, linux-kernel@vger.kernel.org
Subject: Re: bug database braindump from the kernel summit
Date: Sun, 01 Apr 2001 18:49:04 -0700 [thread overview]
Message-ID: <3AC7DA90.BA522CF2@megapathdsl.net> (raw)
In-Reply-To: <Pine.LNX.3.96.1010401160430.28121K-100000@mandrakesoft.mandrakesoft.com>
Jeff Garzik wrote:
<snip>
> /proc/pci data alone with every bug report is usually invaluable. It
> gives you a really good idea of the general layout of the system, and
> you can often catch or become aware of related hardware characteristics
> which
I often see requests for the output of "lspci -vvxxx" when developers
are looking into problems with handling pci bus bridging and quirks
in specific hardware. For example, this info has been requested of
me for debugging a problem handling my Neomagic 2160, at least one
bug in early Yenta code and so on. Does /proc/pci get you all the
information that would be obtained with "lspci -vvxxx"?
> linux/REPORTINGS-BUGS was created to give users a hint that we need
> -more- information, and tells exactly what general information is useful
> to provide. We do not need less information.
Agreed.
Miles
next prev parent reply other threads:[~2001-04-02 2:48 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-01 19:32 bug database braindump from the kernel summit Manfred Spraul
2001-04-01 20:17 ` Albert D. Cahalan
2001-04-01 21:07 ` Jeff Garzik
2001-04-01 21:48 ` Manfred Spraul
2001-04-01 22:48 ` Jeff Garzik
2001-04-01 23:01 ` David Lang
2001-04-01 23:21 ` Jeff Garzik
2001-04-01 23:25 ` David Lang
2001-04-01 23:34 ` Jeff Garzik
2001-04-01 23:32 ` David Lang
2001-04-01 23:44 ` Jeff Garzik
2001-04-01 23:43 ` David Lang
2001-04-02 0:26 ` Ben Ford
2001-04-02 18:57 ` Kai Henningsen
2001-04-05 12:55 ` Petr Baudis
2001-04-02 5:26 ` Richard Russon
2001-04-02 21:35 ` Steven Walter
2001-04-02 19:39 ` Oliver Xymoron
2001-04-02 21:40 ` J . A . Magallon
2001-04-02 22:09 ` Jeff Garzik
2001-04-02 22:24 ` David Lang
2001-04-02 22:38 ` J . A . Magallon
2001-04-02 23:04 ` Tom Leete
2001-04-02 23:12 ` Oliver Xymoron
2001-04-02 23:24 ` Jeff Garzik
2001-04-02 23:31 ` Oliver Xymoron
2001-04-03 16:05 ` Miles Lane
2001-04-02 1:49 ` Miles Lane [this message]
2001-04-01 20:59 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2001-04-01 22:34 Stephen Satchell
2001-04-02 8:00 ` Olaf Titz
2001-04-01 17:54 Larry McVoy
2001-04-01 19:43 ` Albert D. Cahalan
2001-04-01 20:21 ` Gregory Maxwell
2001-04-01 20:38 ` Albert D. Cahalan
2001-04-01 21:16 ` David Lang
2001-04-01 21:18 ` David Lang
2001-04-02 1:57 ` Miles Lane
2001-04-02 5:07 ` David Lang
2001-04-01 23:14 ` Jeff Garzik
2001-04-02 13:31 ` Rogier Wolff
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=3AC7DA90.BA522CF2@megapathdsl.net \
--to=miles@megapathdsl.net \
--cc=acahalan@cs.uml.edu \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=manfred@colorfullife.com \
/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 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.