Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1326492
| From | Thomas Gleixner <tglx@linutronix.de> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: crash in 3.12.51 (likely in 3.12.52 as well) in timer code |
| Date | 2016-02-04 10:00 +0100 |
| Message-ID | <qYnVD-6fU-1@gated-at.bofh.it> (permalink) |
| References | <qY3kf-QW-21@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wed, 3 Feb 2016, Nikolay Borisov wrote: > > It seems when the code tries to do prev->next = next in __list_del from detach_timer, > rax has a value of dead000000200200 (LIST_POISON2). > So in this case the prev/next entries do not look like corrupted, whereas > when manipulating the list inside detach_timer they do. This is really > odd, any ideas how to further debug this? Please enable CONFIG_DEBUG_OBJECTS CONFIG_DEBUG_OBJECTS_TIMERS CONFIG_DEBUG_OBJECTS_WORK That should pinpoint the offending code. Thanks, tglx
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
crash in 3.12.51 (likely in 3.12.52 as well) in timer code Nikolay Borisov <kernel@kyup.com> - 2016-02-03 12:00 +0100
Re: crash in 3.12.51 (likely in 3.12.52 as well) in timer code Thomas Gleixner <tglx@linutronix.de> - 2016-02-04 10:00 +0100
Re: crash in 3.12.51 (likely in 3.12.52 as well) in timer code Mike Galbraith <umgwanakikbuti@gmail.com> - 2016-02-04 12:40 +0100
Re: crash in 3.12.51 (likely in 3.12.52 as well) in timer code Nikolay Borisov <kernel@kyup.com> - 2016-02-04 13:00 +0100
Re: crash in 3.12.51 (likely in 3.12.52 as well) in timer code Mike Galbraith <umgwanakikbuti@gmail.com> - 2016-02-04 13:20 +0100
Re: crash in 3.12.51 (likely in 3.12.52 as well) in timer code Mike Galbraith <umgwanakikbuti@gmail.com> - 2016-02-04 13:30 +0100
Re: crash in 3.12.51 (likely in 3.12.52 as well) in timer code Nikolay Borisov <kernel@kyup.com> - 2016-02-04 13:30 +0100
csiph-web