[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] blktap problem: Re: BUG: unable to handle kernel NULL pointer dereference (4.0.1 w/2.6.32.36)


  • To: Pasi Kärkkäinen <pasik@xxxxxx>
  • From: Quartexx <quartex73@xxxxxxxxx>
  • Date: Sat, 11 Jun 2011 13:35:28 +0200
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Daniel Stodden <daniel.stodden@xxxxxxxxxx>
  • Delivery-date: Sat, 11 Jun 2011 04:36:06 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=ao03bUxMMP0Rf9f6u6Iezbu2IchT1XVsKBScantzZKzbtC136WteLdssiaQZW1iX0J Ni1zanRz7quCozvYEvLV/40nmca4KlpyiRNgQjY9m0y6ty+dlmOxpthsjRPy7FOV52YM Nm16IljY12/eufTUyijxjKoLIgO0mP0hsHbKs=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

2011/6/11 Pasi Kärkkäinen <pasik@xxxxxx>:
> Hello,
> I added Daniel as CC, maybe he has some ideas about this one.
> What do you do when this crash happens? How to reproduce it?

It's the third time and all times it happened in the night.  I have
set kernel.panic=20 so when this happen, the box simply reboot.  I
would say it's random.

The output I post was captured with netconsole


Some hardware info:
description: System
   product: S3420GP
   vendor: Intel Corporation
   version: ....................
   serial: ............
   width: 64 bits
   capabilities: smbios-2.5 dmi-2.5 vsyscall64 vsyscall32
   configuration: administrator_password=disabled boot=normal chassis=server fr
ontpanel_password=disabled keyboard_password=disabled power-on_password=disabled
 uuid=0FD8E440-1952-11E0-B578-001E6702C2CA
 *-core
      description: Motherboard
      product: S3420GP
      vendor: Intel Corporation
      physical id: 0
    *-memory
         description: System Memory
         physical id: 2e
         slot: System board or motherboard
         size: 16GiB
    *-cpu:0
         description: CPU
         product: Intel(R) Xeon(R) CPU           X3430  @ 2.40GHz
         vendor: Intel Corp.
         physical id: 3b
         bus info: cpu@0
         version: Intel(R) Xeon(R) CPU           X3430  @ 2.40GHz
         slot: CPU1
         size: 2400MHz
         capacity: 4GHz
         width: 64 bits
         clock: 133MHz
          *-storage
               description: RAID bus controller
               product: 9690SA SAS/SATA-II RAID PCIe
               vendor: 3ware Inc
               physical id: 0
               bus info: pci@0000:01:00.0
               logical name: scsi0
               version: 01
               width: 64 bits
               clock: 33MHz
               capabilities: storage pm msi pciexpress bus_master cap_list rom
emulated
               configuration: driver=3w-9xxx latency=0
               resources: irq:16 memory:b0000000-b1ffffff(prefetchable) memory:
b3a00000-b3a00fff ioport:2000(size=256) memory:b3a20000-b3a3ffff(prefetchable)


In the beginning I experienced controller reset but last lsi firmware
seems to fix that.  Maybe it's related to this bug..






>
> -- Pasi
>
> On Sat, Jun 11, 2011 at 04:17:44AM -0700, quartex wrote:
>> I have updated to 2.6.32.41 but it happened again.
>>
>> [491154.766766] BUG: unable to handle kernel NULL pointer dereference
>> at 0000000000000320
>> [491154.767477] IP: [<ffffffff8128cbc3>] blktap_device_end_request+0x4a/0x71
>> [491154.767844] PGD 3db17067 PUD 3cebe067 PMD 0
>> [491154.768219] Oops: 0000 [#1] SMP
>> [491154.768572] last sysfs file: /sys/devices/vbd-4-51713/statistics/wr_sect
>> [491154.768942] CPU 3
>> [491154.769295] Modules linked in: netconsole [last unloaded:
>> scsi_wait_scan]
>> [491154.769683] Pid: 4392, comm: tapdisk2 Not tainted 2.6.32.36 #4 S3420GP
>> [491154.770056] RIP: e030:[<ffffffff8128cbc3>]   [<ffffffff8128cbc3>]
>> blktap_device_end_request+0x4a/0x71
>> [491154.770767] RSP: e02b:ffff88003cd33ca8  EFLAGS: 00010046
>> [491154.771133] RAX: 0000000000000000 RBX: ffff88003df60d20 RCX:
>> 0000000000000000
>> [491154.771824] RDX: 00000000000000a1 RSI: 0000000000000001 RDI:
>> 0000000000000004
>> [491154.772524] RBP: ffff88003cd33cc8 R08: 0000000000000000 R09:
>> ffff88003cd33b08
>> [491154.773222] R10: 0000000000000001 R11: ffffffff00001000 R12:
>> ffff88003ccadb20
>> [491154.773915] R13: ffff88003d8e3c00 R14: 0000000000000000 R15:
>> 0000000000000002
>> [491154.774622] FS:  00007f152f810740(0000) GS:ffff88002808f000(0000)
>> knlGS:0000000000000000
>> [491154.775325] CS:  e033 DS: 0000 ES: 0000 CR0: 000000008005003b
>> [491154.775683] CR2: 0000000000000320 CR3: 000000003b095000 CR4:
>> 0000000000002660
>> [491154.776380] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
>> 0000000000000000
>> [491154.777079] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7:
>> 0000000000000400
>> [491154.777770] Process tapdisk2 (pid: 4392, threadinfo
>> ffff88003cd32000, task ffff88003d833c80)
>> [491154.778476] Stack:
>> [491154.778821]  ffff88003d8e3c00 0000000000000000 ffff88003ccadb20
>> 0000000000e5386f
>> [491154.779220] <0> ffff88003cd33e58 ffffffff8128beab 000000003cd33ce8
>> ffffffff81aab128
>> [491154.779956] <0> 000000013d743ac0 ffff88003d7439a0 000000019681a000
>> ffff88003fffc800
>> [491154.780987] Call Trace:
>> [491154.781334]  [<ffffffff8128beab>] blktap_ring_ioctl+0x12d/0x23f
>> [491154.781676]  [<ffffffff811d503b>] ? avc_has_perm+0x57/0x69
>> [491154.782017]  [<ffffffff811d6322>] ? inode_has_perm+0x5f/0x61
>> [491154.782368]  [<ffffffff810e13b3>] ? generic_file_aio_write+0x8c/0xa9
>> [491154.782718]  [<ffffffff8111fd46>] vfs_ioctl+0x6a/0x82
>> [491154.783072]  [<ffffffff81120248>] do_vfs_ioctl+0x473/0x4b9
>> [491154.783426]  [<ffffffff811202df>] sys_ioctl+0x51/0x74
>> [491154.783781]  [<ffffffff8103ccc2>] system_call_fastpath+0x16/0x1b
>> [491154.784142] Code: e6 4c 89
>> [491154.795155]  [<ffffffff81120248>] do_vfs_ioctl+0x473/0x4b9
>>
>>
>>
>>
>>
>> --
>> View this message in context: 
>> http://xen.1045712.n5.nabble.com/BUG-unable-to-handle-kernel-NULL-pointer-dereference-4-0-1-w-2-6-32-36-tp4432056p4478572.html
>> Sent from the Xen - Dev mailing list archive at Nabble.com.
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-devel
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.