Re: New warnings from WITNESS

2016-11-06 Thread Michael Tuexen 

> On 6 Nov 2016, at 19:41, Scott Long  wrote:
> 
> 
>> On Nov 6, 2016, at 11:01 AM, Michael Tuexen  wrote:
>> 
>>> On 6 Nov 2016, at 15:39, Konstantin Belousov  wrote:
>>> 
>>> On Sun, Nov 06, 2016 at 02:17:45PM +0100, Michael Tuexen wrote:
> On 6 Nov 2016, at 13:28, Konstantin Belousov  wrote:
> 
> On Sun, Nov 06, 2016 at 12:50:12PM +0100, Michael Tuexen wrote:
>> bus_dmamap_create with the following non-sleepable locks held:
>> exclusive sleep mutex mpt (mpt) r = 0 (0xfee2f008) locked @ 
>> dev/mpt/mpt.c:2287
>> stack backtrace:
>> #0 0x80ac0300 at witness_debugger+0x70
>> #1 0x80ac15e7 at witness_warn+0x3d7
>> #2 0x81055fef at bus_dmamap_create+0x2f
>> #3 0x80678a25 at mpt_configure_ioc+0x3a5
>> #4 0x80677476 at mpt_attach+0x226
>> #5 0x80683299 at mpt_pci_attach+0x9c9
>> #6 0x80a9478d at device_attach+0x41d
>> #7 0x80a9595a at bus_generic_attach+0x4a
>> #8 0x806ebe75 at pci_attach+0xd5
>> #9 0x80a9478d at device_attach+0x41d
>> #10 0x80a9595a at bus_generic_attach+0x4a
>> #11 0x803c11a2 at acpi_pcib_acpi_attach+0x402
>> #12 0x80a9478d at device_attach+0x41d
>> #13 0x80a9595a at bus_generic_attach+0x4a
>> #14 0x803b4c8f at acpi_attach+0xdbf
>> #15 0x80a9478d at device_attach+0x41d
>> #16 0x80a9595a at bus_generic_attach+0x4a
>> #17 0x80ee03e3 at nexus_acpi_attach+0x73
>> 
>> ... and so on. Not sure which revision introduced it...
> r308268
> 
> I believe that this is an mpt(4) driver issue, which calls
> bus_dmamap_create(9) with the mpt mutex held.
 OK. Whom to contact? Or are you willing to look into it?
 I haven't worked in that area...
>>> 
>>> I am really not sure.  Looking at the svn history is not very encouraging.
>> Hmm. Time to change my setup, I guess...
>>> 
>>> Might be try freebsd-scsi@ as well.
>> I dropped them an e-mail...
>> 
>> 
> 
> Please see my response on that list.
Will do once it shows up in the archive since I'm not subscribed
to that list...

Best regards
Michael
> 
> Scott
> 
> 

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: New warnings from WITNESS

2016-11-06 Thread Scott Long 

> On Nov 6, 2016, at 11:01 AM, Michael Tuexen  wrote:
> 
>> On 6 Nov 2016, at 15:39, Konstantin Belousov  wrote:
>> 
>> On Sun, Nov 06, 2016 at 02:17:45PM +0100, Michael Tuexen wrote:
 On 6 Nov 2016, at 13:28, Konstantin Belousov  wrote:
 
 On Sun, Nov 06, 2016 at 12:50:12PM +0100, Michael Tuexen wrote:
> bus_dmamap_create with the following non-sleepable locks held:
> exclusive sleep mutex mpt (mpt) r = 0 (0xfee2f008) locked @ 
> dev/mpt/mpt.c:2287
> stack backtrace:
> #0 0x80ac0300 at witness_debugger+0x70
> #1 0x80ac15e7 at witness_warn+0x3d7
> #2 0x81055fef at bus_dmamap_create+0x2f
> #3 0x80678a25 at mpt_configure_ioc+0x3a5
> #4 0x80677476 at mpt_attach+0x226
> #5 0x80683299 at mpt_pci_attach+0x9c9
> #6 0x80a9478d at device_attach+0x41d
> #7 0x80a9595a at bus_generic_attach+0x4a
> #8 0x806ebe75 at pci_attach+0xd5
> #9 0x80a9478d at device_attach+0x41d
> #10 0x80a9595a at bus_generic_attach+0x4a
> #11 0x803c11a2 at acpi_pcib_acpi_attach+0x402
> #12 0x80a9478d at device_attach+0x41d
> #13 0x80a9595a at bus_generic_attach+0x4a
> #14 0x803b4c8f at acpi_attach+0xdbf
> #15 0x80a9478d at device_attach+0x41d
> #16 0x80a9595a at bus_generic_attach+0x4a
> #17 0x80ee03e3 at nexus_acpi_attach+0x73
> 
> ... and so on. Not sure which revision introduced it...
 r308268
 
 I believe that this is an mpt(4) driver issue, which calls
 bus_dmamap_create(9) with the mpt mutex held.
>>> OK. Whom to contact? Or are you willing to look into it?
>>> I haven't worked in that area...
>> 
>> I am really not sure.  Looking at the svn history is not very encouraging.
> Hmm. Time to change my setup, I guess...
>> 
>> Might be try freebsd-scsi@ as well.
> I dropped them an e-mail...
> 
> 

Please see my response on that list.

Scott


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: New warnings from WITNESS

2016-11-06 Thread Michael Tuexen 
> On 6 Nov 2016, at 15:39, Konstantin Belousov  wrote:
> 
> On Sun, Nov 06, 2016 at 02:17:45PM +0100, Michael Tuexen wrote:
>>> On 6 Nov 2016, at 13:28, Konstantin Belousov  wrote:
>>> 
>>> On Sun, Nov 06, 2016 at 12:50:12PM +0100, Michael Tuexen wrote:
 bus_dmamap_create with the following non-sleepable locks held:
 exclusive sleep mutex mpt (mpt) r = 0 (0xfee2f008) locked @ 
 dev/mpt/mpt.c:2287
 stack backtrace:
 #0 0x80ac0300 at witness_debugger+0x70
 #1 0x80ac15e7 at witness_warn+0x3d7
 #2 0x81055fef at bus_dmamap_create+0x2f
 #3 0x80678a25 at mpt_configure_ioc+0x3a5
 #4 0x80677476 at mpt_attach+0x226
 #5 0x80683299 at mpt_pci_attach+0x9c9
 #6 0x80a9478d at device_attach+0x41d
 #7 0x80a9595a at bus_generic_attach+0x4a
 #8 0x806ebe75 at pci_attach+0xd5
 #9 0x80a9478d at device_attach+0x41d
 #10 0x80a9595a at bus_generic_attach+0x4a
 #11 0x803c11a2 at acpi_pcib_acpi_attach+0x402
 #12 0x80a9478d at device_attach+0x41d
 #13 0x80a9595a at bus_generic_attach+0x4a
 #14 0x803b4c8f at acpi_attach+0xdbf
 #15 0x80a9478d at device_attach+0x41d
 #16 0x80a9595a at bus_generic_attach+0x4a
 #17 0x80ee03e3 at nexus_acpi_attach+0x73
 
 ... and so on. Not sure which revision introduced it...
>>> r308268
>>> 
>>> I believe that this is an mpt(4) driver issue, which calls
>>> bus_dmamap_create(9) with the mpt mutex held.
>> OK. Whom to contact? Or are you willing to look into it?
>> I haven't worked in that area...
> 
> I am really not sure.  Looking at the svn history is not very encouraging.
Hmm. Time to change my setup, I guess...
> 
> Might be try freebsd-scsi@ as well.
I dropped them an e-mail...

Best regards
Michael

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: New warnings from WITNESS

2016-11-06 Thread Konstantin Belousov 
On Sun, Nov 06, 2016 at 02:17:45PM +0100, Michael Tuexen wrote:
> > On 6 Nov 2016, at 13:28, Konstantin Belousov  wrote:
> > 
> > On Sun, Nov 06, 2016 at 12:50:12PM +0100, Michael Tuexen wrote:
> >> bus_dmamap_create with the following non-sleepable locks held:
> >> exclusive sleep mutex mpt (mpt) r = 0 (0xfee2f008) locked @ 
> >> dev/mpt/mpt.c:2287
> >> stack backtrace:
> >> #0 0x80ac0300 at witness_debugger+0x70
> >> #1 0x80ac15e7 at witness_warn+0x3d7
> >> #2 0x81055fef at bus_dmamap_create+0x2f
> >> #3 0x80678a25 at mpt_configure_ioc+0x3a5
> >> #4 0x80677476 at mpt_attach+0x226
> >> #5 0x80683299 at mpt_pci_attach+0x9c9
> >> #6 0x80a9478d at device_attach+0x41d
> >> #7 0x80a9595a at bus_generic_attach+0x4a
> >> #8 0x806ebe75 at pci_attach+0xd5
> >> #9 0x80a9478d at device_attach+0x41d
> >> #10 0x80a9595a at bus_generic_attach+0x4a
> >> #11 0x803c11a2 at acpi_pcib_acpi_attach+0x402
> >> #12 0x80a9478d at device_attach+0x41d
> >> #13 0x80a9595a at bus_generic_attach+0x4a
> >> #14 0x803b4c8f at acpi_attach+0xdbf
> >> #15 0x80a9478d at device_attach+0x41d
> >> #16 0x80a9595a at bus_generic_attach+0x4a
> >> #17 0x80ee03e3 at nexus_acpi_attach+0x73
> >> 
> >> ... and so on. Not sure which revision introduced it...
> > r308268
> > 
> > I believe that this is an mpt(4) driver issue, which calls
> > bus_dmamap_create(9) with the mpt mutex held.
> OK. Whom to contact? Or are you willing to look into it?
> I haven't worked in that area...

I am really not sure.  Looking at the svn history is not very encouraging.

Might be try freebsd-scsi@ as well.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: New warnings from WITNESS

2016-11-06 Thread Michael Tuexen 
> On 6 Nov 2016, at 13:28, Konstantin Belousov  wrote:
> 
> On Sun, Nov 06, 2016 at 12:50:12PM +0100, Michael Tuexen wrote:
>> bus_dmamap_create with the following non-sleepable locks held:
>> exclusive sleep mutex mpt (mpt) r = 0 (0xfee2f008) locked @ 
>> dev/mpt/mpt.c:2287
>> stack backtrace:
>> #0 0x80ac0300 at witness_debugger+0x70
>> #1 0x80ac15e7 at witness_warn+0x3d7
>> #2 0x81055fef at bus_dmamap_create+0x2f
>> #3 0x80678a25 at mpt_configure_ioc+0x3a5
>> #4 0x80677476 at mpt_attach+0x226
>> #5 0x80683299 at mpt_pci_attach+0x9c9
>> #6 0x80a9478d at device_attach+0x41d
>> #7 0x80a9595a at bus_generic_attach+0x4a
>> #8 0x806ebe75 at pci_attach+0xd5
>> #9 0x80a9478d at device_attach+0x41d
>> #10 0x80a9595a at bus_generic_attach+0x4a
>> #11 0x803c11a2 at acpi_pcib_acpi_attach+0x402
>> #12 0x80a9478d at device_attach+0x41d
>> #13 0x80a9595a at bus_generic_attach+0x4a
>> #14 0x803b4c8f at acpi_attach+0xdbf
>> #15 0x80a9478d at device_attach+0x41d
>> #16 0x80a9595a at bus_generic_attach+0x4a
>> #17 0x80ee03e3 at nexus_acpi_attach+0x73
>> 
>> ... and so on. Not sure which revision introduced it...
> r308268
> 
> I believe that this is an mpt(4) driver issue, which calls
> bus_dmamap_create(9) with the mpt mutex held.
OK. Whom to contact? Or are you willing to look into it?
I haven't worked in that area...

Best regards
Michael

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: New warnings from WITNESS

2016-11-06 Thread Konstantin Belousov 
On Sun, Nov 06, 2016 at 12:50:12PM +0100, Michael Tuexen wrote:
> bus_dmamap_create with the following non-sleepable locks held:
> exclusive sleep mutex mpt (mpt) r = 0 (0xfee2f008) locked @ 
> dev/mpt/mpt.c:2287
> stack backtrace:
> #0 0x80ac0300 at witness_debugger+0x70
> #1 0x80ac15e7 at witness_warn+0x3d7
> #2 0x81055fef at bus_dmamap_create+0x2f
> #3 0x80678a25 at mpt_configure_ioc+0x3a5
> #4 0x80677476 at mpt_attach+0x226
> #5 0x80683299 at mpt_pci_attach+0x9c9
> #6 0x80a9478d at device_attach+0x41d
> #7 0x80a9595a at bus_generic_attach+0x4a
> #8 0x806ebe75 at pci_attach+0xd5
> #9 0x80a9478d at device_attach+0x41d
> #10 0x80a9595a at bus_generic_attach+0x4a
> #11 0x803c11a2 at acpi_pcib_acpi_attach+0x402
> #12 0x80a9478d at device_attach+0x41d
> #13 0x80a9595a at bus_generic_attach+0x4a
> #14 0x803b4c8f at acpi_attach+0xdbf
> #15 0x80a9478d at device_attach+0x41d
> #16 0x80a9595a at bus_generic_attach+0x4a
> #17 0x80ee03e3 at nexus_acpi_attach+0x73
> 
> ... and so on. Not sure which revision introduced it...
r308268

I believe that this is an mpt(4) driver issue, which calls
bus_dmamap_create(9) with the mpt mutex held.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

New warnings from WITNESS

2016-11-06 Thread Michael Tuexen 
Dear all,

when booting a recent kernel

[freebsd12:~] tuexen% uname -a
FreeBSD freebsd12.testbed 12.0-CURRENT FreeBSD 12.0-CURRENT #702 r308359M: Sun 
Nov  6 11:55:17 CET 2016 
tuexen@freebsd12.testbed:/usr/home/tuexen/head/sys/amd64/compile/SCTP  amd64

on a VMWare Fusion VM, I get a lot of warnings like

bus_dmamap_create with the following non-sleepable locks held:
exclusive sleep mutex mpt (mpt) r = 0 (0xfee2f008) locked @ 
dev/mpt/mpt.c:2287
stack backtrace:
#0 0x80ac0300 at witness_debugger+0x70
#1 0x80ac15e7 at witness_warn+0x3d7
#2 0x81055fef at bus_dmamap_create+0x2f
#3 0x80678a25 at mpt_configure_ioc+0x3a5
#4 0x80677476 at mpt_attach+0x226
#5 0x80683299 at mpt_pci_attach+0x9c9
#6 0x80a9478d at device_attach+0x41d
#7 0x80a9595a at bus_generic_attach+0x4a
#8 0x806ebe75 at pci_attach+0xd5
#9 0x80a9478d at device_attach+0x41d
#10 0x80a9595a at bus_generic_attach+0x4a
#11 0x803c11a2 at acpi_pcib_acpi_attach+0x402
#12 0x80a9478d at device_attach+0x41d
#13 0x80a9595a at bus_generic_attach+0x4a
#14 0x803b4c8f at acpi_attach+0xdbf
#15 0x80a9478d at device_attach+0x41d
#16 0x80a9595a at bus_generic_attach+0x4a
#17 0x80ee03e3 at nexus_acpi_attach+0x73
bus_dmamap_create with the following non-sleepable locks held:
exclusive sleep mutex mpt (mpt) r = 0 (0xfee2f008) locked @ 
dev/mpt/mpt.c:2287
stack backtrace:
#0 0x80ac0300 at witness_debugger+0x70
#1 0x80ac15e7 at witness_warn+0x3d7
#2 0x81055fef at bus_dmamap_create+0x2f
#3 0x80678a25 at mpt_configure_ioc+0x3a5
#4 0x80677476 at mpt_attach+0x226
#5 0x80683299 at mpt_pci_attach+0x9c9
#6 0x80a9478d at device_attach+0x41d
#7 0x80a9595a at bus_generic_attach+0x4a
#8 0x806ebe75 at pci_attach+0xd5
#9 0x80a9478d at device_attach+0x41d
#10 0x80a9595a at bus_generic_attach+0x4a
#11 0x803c11a2 at acpi_pcib_acpi_attach+0x402
#12 0x80a9478d at device_attach+0x41d
#13 0x80a9595a at bus_generic_attach+0x4a
#14 0x803b4c8f at acpi_attach+0xdbf
#15 0x80a9478d at device_attach+0x41d
#16 0x80a9595a at bus_generic_attach+0x4a
#17 0x80ee03e3 at nexus_acpi_attach+0x73
bus_dmamap_create with the following non-sleepable locks held:
exclusive sleep mutex mpt (mpt) r = 0 (0xfee2f008) locked @ 
dev/mpt/mpt.c:2287
stack backtrace:
#0 0x80ac0300 at witness_debugger+0x70
#1 0x80ac15e7 at witness_warn+0x3d7
#2 0x81055fef at bus_dmamap_create+0x2f
#3 0x80678a25 at mpt_configure_ioc+0x3a5
#4 0x80677476 at mpt_attach+0x226
#5 0x80683299 at mpt_pci_attach+0x9c9
#6 0x80a9478d at device_attach+0x41d
#7 0x80a9595a at bus_generic_attach+0x4a
#8 0x806ebe75 at pci_attach+0xd5
#9 0x80a9478d at device_attach+0x41d
#10 0x80a9595a at bus_generic_attach+0x4a
#11 0x803c11a2 at acpi_pcib_acpi_attach+0x402
#12 0x80a9478d at device_attach+0x41d
#13 0x80a9595a at bus_generic_attach+0x4a
#14 0x803b4c8f at acpi_attach+0xdbf
#15 0x80a9478d at device_attach+0x41d
#16 0x80a9595a at bus_generic_attach+0x4a
#17 0x80ee03e3 at nexus_acpi_attach+0x73
bus_dmamap_create with the following non-sleepable locks held:
exclusive sleep mutex mpt (mpt) r = 0 (0xfee2f008) locked @ 
dev/mpt/mpt.c:2287
stack backtrace:
#0 0x80ac0300 at witness_debugger+0x70
#1 0x80ac15e7 at witness_warn+0x3d7
#2 0x81055fef at bus_dmamap_create+0x2f
#3 0x80678a25 at mpt_configure_ioc+0x3a5
#4 0x80677476 at mpt_attach+0x226
#5 0x80683299 at mpt_pci_attach+0x9c9
#6 0x80a9478d at device_attach+0x41d
#7 0x80a9595a at bus_generic_attach+0x4a
#8 0x806ebe75 at pci_attach+0xd5
#9 0x80a9478d at device_attach+0x41d
#10 0x80a9595a at bus_generic_attach+0x4a
#11 0x803c11a2 at acpi_pcib_acpi_attach+0x402
#12 0x80a9478d at device_attach+0x41d
#13 0x80a9595a at bus_generic_attach+0x4a
#14 0x803b4c8f at acpi_attach+0xdbf
#15 0x80a9478d at device_attach+0x41d
#16 0x80a9595a at bus_generic_attach+0x4a
#17 0x80ee03e3 at nexus_acpi_attach+0x73

... and so on. Not sure which revision introduced it...

Best regards
Michael
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"