Prompt bug reporters to run the kernel version they're reporting on or otherwise record boot messages
svn path=/dists/trunk/linux-2.6/; revision=14322
This commit is contained in:
parent
9d4910d240
commit
02eed2eef7
|
@ -91,6 +91,8 @@ linux-2.6 (2.6.31-1~experimental.1) experimental; urgency=low
|
|||
corruption and GPU lock-ups (Closes: #541307)
|
||||
* Generate architecture-qualified package relations as needed for
|
||||
flavours that exist for multiple architectures (Closes: #278729)
|
||||
* Prompt bug reporters to run the kernel version they're reporting on
|
||||
or otherwise record boot messages
|
||||
|
||||
[ Martin Michlmayr ]
|
||||
* [armel/orion5x, armel/kirkwood] Set GPIO_SYSFS=y since these
|
||||
|
|
|
@ -5,5 +5,8 @@ add_dmesg() {
|
|||
}
|
||||
|
||||
ask_dmesg() {
|
||||
true
|
||||
# Remind the user to attach the kernel log. This should also trigger
|
||||
# a reminder in some MUAs if the user tries to send without it.
|
||||
echo '** Kernel log: boot messages should be attached' >&3
|
||||
echo >&3
|
||||
}
|
||||
|
|
|
@ -0,0 +1,7 @@
|
|||
Please ensure that you are currently running the kernel version that you
|
||||
are reporting on. This will allow your bug report to include useful
|
||||
diagnostic information about the running kernel.
|
||||
|
||||
If you are reporting that the kernel fails to boot, please use a digital
|
||||
camera, serial console or netconsole to record the boot messages and
|
||||
attach these to your report.
|
Loading…
Reference in New Issue