Re: BUG: unable to handle kernel NULL pointer deref, bisected to 746650160

2015-04-27 Thread Torsten Luettgert
On Wed, 22 Apr 2015 10:45:19 +0200 Torsten Luettgert wrote: > I'll keep this running, and if - when - it has been going for a week > (3 times the max uptime without the patch) - I'll give a final notice. So here it is, the final notice: 17:16:36 up 7 days, 4:07, 2 users, lo

Re: BUG: unable to handle kernel NULL pointer deref, bisected to 746650160

2015-04-13 Thread Torsten Luettgert
On Mon, 13 Apr 2015 19:41:05 +0200 Christoph Hellwig wrote: > Can you run gdb on your vmlinux file and send the output of the > following command in gdb > > l *(scsi_dma_unmap+0x54) Thanks for looking into it! Here is what gdb says: Reading symbols from /opt/kvm/bisect/vmlinux-3.16.0-746650160

Re: BUG: unable to handle kernel NULL pointer deref, bisected to 746650160

2015-04-17 Thread Torsten Luettgert
On Fri, 17 Apr 2015 15:31:16 +0200 Torsten Luettgert wrote: > On Mon, 13 Apr 2015 20:28:29 +0200 > Torsten Luettgert wrote: > > Right now, I'm trying the problematic release, compiled with a newer > gcc (4.9.2-6 from Fedora, while using 4.4.7-11 from rhel6 > before). It

Re: BUG: unable to handle kernel NULL pointer deref, bisected to 746650160

2015-04-17 Thread Torsten Luettgert
On Mon, 13 Apr 2015 20:28:29 +0200 Torsten Luettgert wrote: > On Mon, 13 Apr 2015 19:41:05 +0200 > Christoph Hellwig wrote: > > > Can you run gdb on your vmlinux file and send the output of the > > following command in gdb > > > > l *(scsi_dma_unmap+0x54) >

Re: BUG: unable to handle kernel NULL pointer deref, bisected to 746650160

2015-04-20 Thread Torsten Luettgert
On Sun, 19 Apr 2015 18:58:41 +0200 Christoph Hellwig wrote: > This looks like a long standing bug in all three 3ware drivers to > me, that the taking the host lock around the host_busy manipulation > was hiding. > > Can you test the patch below? I'm running it right now and keeping my fingers c

Re: BUG: unable to handle kernel NULL pointer deref, bisected to 746650160

2015-04-22 Thread Torsten Luettgert
On Mon, 20 Apr 2015 13:24:24 +0200 Torsten Luettgert wrote: > > Can you test the patch below? > > I'm running it right now and keeping my fingers crossed. Just under two days uptime now, and no crashes. I'm pretty sure you nailed it. I'll keep this running, and if