| 1 |
On 27 Sep 2015 at 10:44, "Tóth Attila" wrote: |
| 2 |
|
| 3 |
> I've been seeing radeon related crashes upon boot on my laptop for a while |
| 4 |
> now, but I could just recently capture this Oops, which can be related. If |
| 5 |
> the machine hard-locks on boot, I can capture no messages. It looks, that |
| 6 |
> most of the time it can regenerate from that state somehow and continues |
| 7 |
> on without any problems. There was a kernel version months before, for |
| 8 |
> which boot resulted in a hard-lock each time. It happens once in every |
| 9 |
> couple of startups only. |
| 10 |
> |
| 11 |
> It's a null pointer dereference. Where should I report that? |
| 12 |
|
| 13 |
to upstream kernel maintainers ;). but before you do that, enable |
| 14 |
frame pointers to get a better backtrace and also DEBUG_INFO so |
| 15 |
that addr2line can produce a precise location for the null deref. |
| 16 |
|
| 17 |
> I'm still having early-boot intel-iommu traces on my other machine, but |
| 18 |
> without any symptoms. Might be related to a 3ware card, fully functioning, |
| 19 |
> housing the system - therefore I cannot verify... |
| 20 |
|
| 21 |
twa_interrupt is from the 3ware 9xxx driver and it seems that it wants |
| 22 |
to unmap a page it doesn't own. DEBUG_INFO and addr2line would help to |
| 23 |
identify the bad call in twa_interrupt (ffffffff9f77d78e in the below |
| 24 |
trace) then you can send it upstream ;). |
| 25 |
|
| 26 |
> ------------[ cut here ]------------ |
| 27 |
> WARNING: CPU: 0 PID: 0 at drivers/iommu/intel-iommu.c:3214 |
| 28 |
> intel_unmap+0x146/0x200() |
| 29 |
> Driver unmaps unmatched page at PFN 0 |
| 30 |
> Modules linked in: |
| 31 |
> CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.1.7-hardened-r1 #1 |
| 32 |
> Hardware name: System manufacturer System Product Name/Z8P(N)E-D12(X), |
| 33 |
> BIOS 1302 06/25/2012 |
| 34 |
> 0000000000000000 0bf0f1830deb9167 ffffffffa61a1f87 0000000000000000 |
| 35 |
> ffffffffa61a1f87 ffffffff9fe5d48d ffff880237c03d80 ffffffff9f0a96e7 |
| 36 |
> ffffffffa61a1f87 0000000000000c8e ffffffffa61e1500 ffff880433ceb368 |
| 37 |
> Call Trace: |
| 38 |
> <IRQ> [<ffffffff9fe5d48d>] ? dump_stack+0x40/0x56 |
| 39 |
> [<ffffffff9f0a96e7>] ? warn_slowpath_common+0x77/0xb0 |
| 40 |
> [<ffffffff9f0a978c>] ? warn_slowpath_fmt+0x6c/0x90 |
| 41 |
> [<ffffffff9f6aa8e6>] ? intel_unmap+0x146/0x200 |
| 42 |
> [<ffffffff9f77d78e>] ? twa_interrupt+0x48e/0x780 |
| 43 |
> [<ffffffff9f0f9de3>] ? handle_irq_event_percpu+0x73/0x120 |
| 44 |
> [<ffffffff9f0f9ec0>] ? handle_irq_event+0x30/0x50 |
| 45 |
> [<ffffffff9f0fcfd8>] ? handle_fasteoi_irq+0x88/0x180 |
| 46 |
> [<ffffffff9f005385>] ? handle_irq+0x85/0x160 |
| 47 |
> [<ffffffff9f0ce264>] ? atomic_notifier_call_chain+0x24/0x30 |
| 48 |
> [<ffffffff9f004c01>] ? do_IRQ+0x41/0xf0 |
| 49 |
> [<ffffffff9fe69397>] ? common_interrupt+0x97/0x97 |
Archives