Re: [PATCH] Fix BREAK handling in sunsab serial driver

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



From: Christopher Alexander Tobias Schulze <cat.schulze@xxxxxxxxxxxxx>
Date: Sun, 27 Jul 2014 15:19:21 +0200

> However, there seems to be another problem that causes an Oops when
> a register dump is requested by SysRq. This is caused when
> perf_event_print_debug() is called from sysrq_handle_showregs() in
> drivers/tty/sysrq.c.

Did you save the OOPS?  It should be trivial to debug with that
information.

perf_event_print_debug() doesn't do anything fancy, it disables CPU
interrupts and reads the PCR and PIC registers.

UltraSPARC-III should be using direct_pcr_ops for this, therefore:

	__asm__ __volatile__("rd %%pcr, %0" : "=r" (val));

and

	__asm__ __volatile__("rd %%pic, %0" : "=r" (val));

are the two operations it will perform.
--
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Kernel Development]     [DCCP]     [Linux ARM Development]     [Linux]     [Photo]     [Yosemite Help]     [Linux ARM Kernel]     [Linux SCSI]     [Linux x86_64]     [Linux Hams]

  Powered by Linux