Re: [PATCH] irq: provide debug_poll_all_shared_irqs() method under CONFIG_DEBUG_SHIRQ

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

 



* Ingo Molnar <mingo@xxxxxxx> wrote:

> > So I do think this is worth doing as a "make it easier to _see_ all 
> > the nasty suspend/resume problems", but at the same time it's going to 
> > be really really painful to debug, and it's not an option we can 
> > likely ever enable in some distro kernel - because a regular user 
> > can't even send a bug-report (just a "resume used to work, now it 
> > stopped working" thing).
> 
> Yeah, indeed. Perhaps a sysctl that turns it off by default might help? 
> Under CONFIG_PM_DEBUG or so.

btw., i think the main problem with debugging is whether one can 'see' the 
problem, literally.

Would it be possible to have a s2ram debug/test mode that puts as much 
stuff into low-power mode as possible - except for the console. That would 
still include a fair amount of random drivers that is at issue here. And 
once the crash/hang happens while it can be seen where it hangs/crashes, 
it becomes a lot more debuggable IMO.

Or is this impossible / not feasible / inefficient?

	Ingo
_______________________________________________
linux-pm mailing list
linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linux-foundation.org/mailman/listinfo/linux-pm

[Index of Archives]     [Linux ACPI]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [CPU Freq]     [Kernel Newbies]     [Fedora Kernel]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux