On Sun, 1 Apr 2001, Albert D. Cahalan wrote:
> Manfred Spraul writes:
> > [Larry McVoy]
>
> >> There was a lot of discussion about possible tools
> >> that would dig out the /proc/pci info
> > I think the tools should not dig too much information out of the system.
> > I remember some Microsoft (win98 beta?) bugtracking software that
> > insisted on sending a several hundert kB long compressed blob with every
> > bug report.
> > IMHO it must be possible to file bugreports without the complete hw info
> > if I know that the bug isn't hw related.
>
> Yep. The two hardware-related items that usually matter:
>
> Little-endian or broken-endian?
> 32-bit or 64-bit?
Matters to whom? You, or the people actually fixing bugs?
"Broken-endian"? whatever.
/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
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.
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
