Hi ,
I have Linux panic when started play music with one of my USB audio device.
first please see this logs:
[ 71.684730] usbcore: registered new interface driver snd-usb-audio
[ 73.835355] BUG: unable to handle kernel NULL pointer dereference
at 0008
[ 73.835412] IP: []
The Linux kernel has had verbal error reporting since the beginning.
Different error conditions trigger different error messages, with
different severity: from a simple warning to the most feared kernel panic.
While this detailed error reporting is much helpful to developers or end
users, there
Use the new aural error reporting framework to signal kernel panic. The
error sound is emitted between the stack dump and the kexec jump.
Signed-off-by: Matteo Croce
---
kernel/panic.c| 25 +
lib/Kconfig.debug | 10 ++
2 files changed, 35 insertions(+)
diff
Use the new aural error reporting framework when reporting an oops. The
sound is emitted at the end of oops_exit(), to avoid interfering with other
oops actions, like stack dump.
Signed-off-by: Matteo Croce
---
kernel/panic.c| 18 ++
lib/Kconfig.debug | 10 ++
2
The Linux kernel has had verbal error reporting since the beginning.
Different error conditions trigger different error messages, with
different severity: from a simple warning to the most feared kernel panic.
While this detailed error reporting is much helpful to developers or end
users, there
Use the new aural error reporting framework to signal kernel bugs. Emit the
sound at the end of the __warn(), so the WARN_* are all covered.
If panic_on_warn is set, panic() will play its sound and never return,
so there is no risk to emit two sounds or the wrong one.
Signed-off-by: Matteo Croce
Add a /proc/crashtest handler which triggers different kernel errors.
Just write a single character (if many are written, only the first one
is read), to trigger different errors:
- p: raise a kernel panic
- w: generate a warning
- o: raise an oops
The handler permissions are set to 0220 to avoid
On Mon, Apr 01, 2019 at 12:24:51PM +0200, Matteo Croce wrote:
> The buzzer driver is simple, requires just a few register writes to work,
> the hardware is extremely cheap and is already present on most machines.
What, no morse-code register dumps?
