Hi! > > Like this: I applied patch over today's git... > > > > I only see last bits of panic... > > > > Call trace: > > __bfq_bfqq_expire > > bfq_bfqq_expire > > bfq_dispatch_requests > > sci_request_fn > > ... > > EIP: T.1839+0x26
> > Any ideas? > > > > We have tried to think about ways to trigger this failure, but in vain. > Unfortunately, so far no user has reported any failure with this last version > of bfq either. Finally, we have gone through a new static analysis, but also > in this case uselessly. > > So, if you are willing to retry, we have put online a version of the code > filled with many BUG_ONs. I hope they can make it easier to track down the > bug. The archive is here: > http://algogroup.unimore.it/people/paolo/disk_sched/debugging-patches/3.15.0-rc8-v7rc5.tgz > BUG: Unable to handle kernel paging request ad dee22fa0 IP: bfq_del_bfqq_busy+0x4d ... Tainted: GW 3.15.0-rc8+ ... Call trace: __bfq_bfqq_expire bfq_bfqq_expire ? bfq_bfqq_expire ? bfq_bfqq_expire bfq_idle_slice_timer call_timer_fn ... > Should this attempt be useless as well, I will, if you do not mind, try by > asking you more details about your system and reproducing your configuration > as much as I can. > See the preivous email... Best regards, Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
