[PATCHlet]: removal of redundant line in documentation

[PATCHlet]: removal of redundant line in documentation

[Matthias Juchem]

Hi Linus.

Step [7.3] is redundant because it is
already handled by the ver_linux script

This patch is against 2.4.0

Matthias

--- REPORTING-BUGS.orig	Sat Jan  6 06:49:12 2001
+++ REPORTING-BUGS	Sat Jan  6 06:47:57 2001
@@ -45,11 +45,10 @@
 [7.] Environment
 [7.1.] Software (add the output of the ver_linux script here)
 [7.2.] Processor information (from /proc/cpuinfo):
-[7.3.] Module information (from /proc/modules):
-[7.4.] Loaded driver and hardware information (/proc/ioports, /proc/iomem)
-[7.5.] PCI information ('lspci -vvv' as root)
-[7.6.] SCSI information (from /proc/scsi/scsi)
-[7.7.] Other information that might be relevant to the problem
+[7.3.] Loaded driver and hardware information (/proc/ioports, /proc/iomem)
+[7.4.] PCI information ('lspci -vvv' as root)
+[7.5.] SCSI information (from /proc/scsi/scsi)
+[7.6.] Other information that might be relevant to the problem
        (please look in /proc and include all information that you
        think to be relevant):
 [X.] Other notes, patches, fixes, workarounds:
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Bug reporting script? (was: removal of redundant line in documentation)

[Jeremy M. Dolan]

On Sat, 06 Jan 2001 06:51:58 +0000, Matthias Juchem wrote:
> Step [7.3] is redundant because it is
> already handled by the ver_linux script

If ver_linux can take off one of those steps, why not include a script
which takes care of ALL the leg work? All of the files it asks the
reporter to include are o+r...

I can whip up a bug_report script to walk the user though all of the
steps in REPORTING-BUGS, if the list isn't averse to 'dumbing down'
the process to the point where maybe some people who shouldn't be
submiting bugs (two words: 'user error') end up not being scared off
by the process.

Is perl allowed for kernel scripts intended for users, or am I stuck
with sh? 

-- 
Jeremy M. Dolan <jmd@turbogeek.org>
OpenPGP key = http://turbogeek.org/openpgp-key
OpenPGP fingerprint = 494C 7A6E 19FB 026A 1F52  E0D5 5C5D 6228 DC43 3DEE
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Bug reporting script? (was: removal of redundant line in documentation)

[Matthias Juchem]

On Sat, 6 Jan 2001, Jeremy M. Dolan wrote:

> If ver_linux can take off one of those steps, why not include a script
> which takes care of ALL the leg work? All of the files it asks the
> reporter to include are o+r...

If have started a script that produces the following output. ( some fields
need to be filled, but the structure will be like that). If you have additional
ideas, please tell me. I'll include some more version numbers from system tools
and, maybe, a routine that calls ksymoops.

Regards,
 Matthias

Linux Kernel Problem Report
===============================================================================
1. One line summary of the problem
----------------------------------------------
Error in module foo

2. Full description of the problem
----------------------------------------------
some text
.
.


3. Keywords
----------------------------------------------
modules, foo

4. Kernel version
----------------------------------------------
Linux version 2.4.0 (root@gandalf) (gcc version 2.95.2 19991024 (release)) #6 Sat Jan 6 03:37:57 CET 2001

5. Oops message with symbolic info
----------------------------------------------

6. Example that triggers the problem
----------------------------------------------

7. System information
----------------------------------------------
a) software
 GNU C                 2.95.2
 Modutils              2.4.0
 GNU make              3.79.1
 Binutils              2.9.5.0.24
 Linux C library       2.1.3
 Dynamic linker/loader 2.1.3
 Linux C++ library     2.7.2
 Procps                2.0.6
 Net-tools             1.56
 Kdb                   0.99
 Sh-utils              2.0
 Util-linux            2.10r
 E2fsprogs             1.19

b) loaded modules
aic7xxx scsi_mod ipv6 ne2k-pci 8390 serial isa-pnp unix

c) /proc/cpuinfo
processor	: 0
vendor_id	: AuthenticAMD
cpu family	: 5
model		: 7
model name	: AMD-K6tm w/ multimedia extensions
stepping	: 0
cpu MHz		: 300.689
cache size	: 64 KB
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 1
wp		: yes
flags		: fpu vme de pse tsc msr mce cx8 mmx
bogomips	: 599.65


d) /proc/ioports
0000-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : ide1
01f0-01f7 : ide0
0213-0213 : isapnp read
02f8-02ff : serial(auto)
0376-0376 : ide1
03c0-03df : vga+
03f6-03f6 : ide0
03f8-03ff : serial(auto)
0a79-0a79 : isapnp write
0cf8-0cff : PCI conf1
5f00-5f1f : Intel Corporation 82371AB PIIX4 ACPI
6100-613f : Intel Corporation 82371AB PIIX4 ACPI
6400-64ff : Adaptec AIC-7881U
  6400-64fe : aic7xxx
6800-681f : Intel Corporation 82371AB PIIX4 USB
6900-691f : Realtek Semiconductor Co., Ltd. RTL-8029(AS)
  6900-691f : ne2k-pci
f000-f00f : Intel Corporation 82371AB PIIX4 IDE

e) /proc/iomem
00000000-0009fbff : System RAM
0009fc00-0009ffff : System RAM
000a0000-000bffff : Video RAM area
000c0000-000c7fff : Video ROM
000cc000-000cc7ff : Extension ROM
000f0000-000fffff : System ROM
00100000-03ffffff : System RAM
  00100000-001a130f : Kernel code
  001a1310-001d948f : Kernel data
e0000000-e07fffff : S3 Inc. 86c764/765 [Trio32/64/64V+]
e0800000-e0800fff : Adaptec AIC-7881U
ffff0000-ffffffff : reserved

f) PCI information

g) SCSI information

h) further information (from /proc and other)

8. Other notes, patches, fixes, workarounds...
----------------------------------------------



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Bug reporting script? (was: removal of redundant line in documentation)

[Pavel Machek]

Hi!

> > If ver_linux can take off one of those steps, why not include a script
> > which takes care of ALL the leg work? All of the files it asks the
> > reporter to include are o+r...
> 
> If have started a script that produces the following output. ( some fields
> need to be filled, but the structure will be like that). If you have additional
> ideas, please tell me. I'll include some more version numbers from system tools
> and, maybe, a routine that calls ksymoops.

This is horrible bugreport. Kill "keywords". Putting "modules" into
keywords i not going to help anyone. Having "4. Kernel version" and
minuses before actuall version is not helpfull, either.

								Pavel

> 4. Kernel version
> ----------------------------------------------
> Linux version 2.4.0 (root@gandalf) (gcc version 2.95.2 19991024 (release)) #6 Sat Jan 6 03:37:57 CET 2001

-- 
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Bug reporting script? (was: removal of redundant line in documentation)

[Matthias Juchem]

On Tue, 9 Jan 2001, Pavel Machek wrote:

> Hi!
>
> This is horrible bugreport. Kill "keywords". Putting "modules" into
> keywords i not going to help anyone. Having "4. Kernel version" and
> minuses before actuall version is not helpfull, either.

"modules" as keyword, keywords in general: This is a suggestion from
REPORTING-BUGS.

minuses: I thought it would be nice to see quickly where one point ends
and another begins. Readability. But this can easily be changed, probably
into an empty line, if that doesn't stop you from helping people, either



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Bug reporting script? (was: removal of redundant line in documentation)

[Pavel Machek]

Hi!

> > This is horrible bugreport. Kill "keywords". Putting "modules" into
> > keywords i not going to help anyone. Having "4. Kernel version" and
> > minuses before actuall version is not helpfull, either.
> 
> "modules" as keyword, keywords in general: This is a suggestion from
> REPORTING-BUGS.

Then REPORTING-BUGS should be changed.
								Pavel
-- 
The best software in life is free (not shareware)!		Pavel
GCM d? s-: !g p?:+ au- a--@ w+ v- C++@ UL+++ L++ N++ E++ W--- M- Y- R+
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Bug reporting script? (was: removal of redundant line in documentation)

[Augusto César Radtke]

Jeremy M. Dolan wrote:

> If ver_linux can take off one of those steps, why not include a script
> which takes care of ALL the leg work? All of the files it asks the
> reporter to include are o+r...
> 
> I can whip up a bug_report script to walk the user though all of the
> steps in REPORTING-BUGS, if the list isn't averse to 'dumbing down'
> the process to the point where maybe some people who shouldn't be
> submiting bugs (two words: 'user error') end up not being scared off
> by the process.
> 
	
About bug reports, isn't a good thing introduce the sgi's lkcd (linux kernel crash dump) into the main stream of 2.5? The main problem of lkcd in 2.2 was the lack of kiobufs.

I think it as a good thing, for distributions, the distribution guys have the vmlinuz image of the distro, so when a bug happens the user only needs to send the crash dump to the distribution kernel hacker, and he can discuss the bug on lkml.

This introduce a new kind of bug reporter, if the distribution makes avalaible every new development kernel as a package, a user can download and use, crash and report the bug without any knowledge about kernel. So the marketing guys can say: 'help the development of linux without hacking, report bugs'.

Comments?
	
	Augusto
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Bug reporting script? (was: removal of redundant line in documentation)

[db]

[...]

> About bug reports, isn't a good thing introduce the sgi's lkcd (linux
kernel crash dump) into the main stream of 2.5? The main problem of lkcd in
2.2 was the lack of kiobufs.
>
> I think it as a good thing, for distributions, the distribution guys have
the vmlinuz image of the distro, so when a bug happens the user only needs
to send the crash dump to the distribution kernel hacker, and he can discuss
the bug on lkml.
>
> This introduce a new kind of bug reporter, if the distribution makes
avalaible every new development kernel as a package, a user can download and
use, crash and report the bug without any knowledge about kernel. So the
marketing guys can say: 'help the development of linux without hacking,
report bugs'.



I think this would be a great idea.



Dan Browning, Cyclone Computer Systems, danb@cyclonecomputers.com



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: Bug reporting script?

[Matthias Juchem]

On Sat, 6 Jan 2001, Augusto César Radtke wrote:

> About bug reports, isn't a good thing introduce the sgi's lkcd
> (linux kernel crash dump) into the main stream of 2.5? The main problem
> of lkcd in 2.2 was the lack of kiobufs.

(see http://boudicca.tux.org/hypermail/linux-kernel/2000week48/0700.html).

IDE dumps are finally supported (http://oss.sgi.com/projects/lkcd/news.html)

Matthias

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/