Date: Thu, 22 May 2014 16:30:01 GMT From: Radim Kolar <hsn@sendmail.cz> To: freebsd-fs@FreeBSD.org Subject: RE: kern/189355: [zfs] zfs panic on root mount 10-stable Message-ID: <201405221630.s4MGU1Ci058652@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/189355; it has been noted by GNATS. From: Radim Kolar <hsn@sendmail.cz> To: Steven Hartland <smh@freebsd.org>, "bug-followup@freebsd.org" <bug-followup@freebsd.org> Cc: Subject: RE: kern/189355: [zfs] zfs panic on root mount 10-stable Date: Thu, 22 May 2014 16:24:48 +0000 --_0f2b99c2-5ea7-4f3d-ba3f-f126c437da89_ Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable after recompiling kernel and zfs with -O0=2C i am have very different stack= trace. I cant get dump with your patch in this case. Can you identify which= kernel component failed? its MPT driver? panic dblfault_handler cpu_search cpu_search_lowest sched_lowest sched_pickcpu sched_add intr_event_schedule_thread intr_event_handle intr_execute_handlers lapic_handle_intr Xapis_isr1 bus_space_write_4 mpt_write mpt_send_cmd mpt_execute_req bus_dmamap_load_ccb mpt_start mpt_action xpt_run_devq xpt_action_default scsi_action xpt_action dastart xpt_run_allocq xpt_schedule dareprobe g_disk_access g_access g_part_access g_access vdev_geom_attach_taster m_attach_taster vdev_geom_read_pool_label spa_generate_rootconf spa_import_rootpool zfs_mount vfs_domount_first vfs_domount vfs_donmount kernel_mount parse_mount vfs_mountroot_parse = --_0f2b99c2-5ea7-4f3d-ba3f-f126c437da89_ Content-Type: text/html; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable <html> <head> <style><!-- .hmmessage P { margin:0px=3B padding:0px } body.hmmessage { font-size: 12pt=3B font-family:Calibri } --></style></head> <body class=3D'hmmessage'><div dir=3D'ltr'>after recompiling kernel and zfs= with -O0=2C i am have very different stacktrace. I cant get dump with your= patch in this case. Can you identify which kernel component failed? its MP= T driver?<br><br>panic<br>dblfault_handler<br>cpu_search<br>cpu_search_lowe= st<br>sched_lowest<br>sched_pickcpu<br>sched_add<br>intr_event_schedule_thr= ead<br>intr_event_handle<br>intr_execute_handlers<br>lapic_handle_intr<br>X= apis_isr1<br>bus_space_write_4<br>mpt_write<br>mpt_send_cmd<br>mpt_execute_= req<br>bus_dmamap_load_ccb<br>mpt_start<br>mpt_action<br>xpt_run_devq<br>xp= t_action_default<br>scsi_action<br>xpt_action<br>dastart<br>xpt_run_allocq<= br>xpt_schedule<br>dareprobe<br>g_disk_access<br>g_access<br>g_part_access<= br>g_access<br>vdev_geom_attach_taster<br>m_attach_taster<br>vdev_geom_read= _pool_label<br>spa_generate_rootconf<br>spa_import_rootpool<br>zfs_mount<br= >vfs_domount_first<br>vfs_domount<br>vfs_donmount<br>kernel_mount<br>parse_= mount<br>vfs_mountroot_parse<br> </div></body> </html>= --_0f2b99c2-5ea7-4f3d-ba3f-f126c437da89_--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201405221630.s4MGU1Ci058652>