Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1734520
| From | Randy Dunlap <rdunlap@infradead.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: Kernel Panic sysrq questions |
| Date | 2017-09-19 00:40 +0200 |
| Message-ID | <urcRQ-47U-7@gated-at.bofh.it> (permalink) |
| References | <ufRH3-5H5-15@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 08/18/17 08:40, Sriram V wrote: > Hi, > > 1. I am testing my watchdog driver. The driver uses the internal > watchdog (Internal to SOC). > 2. I use a single core SOC. > 3. I have a workqueue which pets the watchdog every 60 seconds. > 4. I trigger a kernel crash by doing a echo c > /proc/sysrq-trigger to > trigger a kernel crash > 5. Even after the crash, I observe that the workqueue gets > periodically executed. (I have a printk > inside the workqueue before the pet as a result the watchdog does > not reset the board. > > My Understanding is When a fatal panic happens, The Kernel is in > frozen state (no workques > or tasks get executed). > > Is my understanding correct or am i missing something here. Hi, What kernel version? I don't see anything in the wq docs about that specific point. Tejun? -- ~Randy
Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
Re: Kernel Panic sysrq questions Randy Dunlap <rdunlap@infradead.org> - 2017-09-19 00:40 +0200 Re: Kernel Panic sysrq questions Tejun Heo <tj@kernel.org> - 2017-09-19 02:30 +0200
csiph-web