NetBSD Problem Report #39725

From kardel@pip.acrys.com  Sat Oct 11 08:02:58 2008
Return-Path: <kardel@pip.acrys.com>
Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11])
	by narn.NetBSD.org (Postfix) with ESMTP id A0ED363B88A
	for <gnats-bugs@gnats.NetBSD.org>; Sat, 11 Oct 2008 08:02:58 +0000 (UTC)
Message-Id: <200810110802.m9B82nI3004577@pip.acrys.com>
Date: Sat, 11 Oct 2008 10:02:49 +0200 (MEST)
From: kardel@netbsg.org
Reply-To: kardel@netbsg.org
To: gnats-bugs@gnats.NetBSD.org
Subject: wdc timeout softintr panic: (l->l_pflag & LP_INTR) == 0
X-Send-Pr-Version: 3.95

>Number:         39725
>Category:       kern
>Synopsis:       panic: diagnostic assertion "(l->l_pflag & LP_INTR) == 0" failed: file "/src/sys/kern/kern_synch.c", line 189
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    bouyer
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Oct 11 08:05:01 +0000 2008
>Closed-Date:    Sun Dec 07 22:46:04 +0000 2008
>Last-Modified:  Sun Dec 07 22:46:04 +0000 2008
>Originator:     Frank Kardel
>Release:        NetBSD 4.99.72
>Organization:

>Environment:
System: NetBSD kardel.name 4.99.72 NetBSD 4.99.72 (PIPADJ) #6: Fri Oct 3 17:31:10 MEST 2008 kardel.name:/fs/raid1a/src/NetBSD/tc-merge/src/obj.i386/sys/arch/i386/compile/PIPADJ i386
Architecture: i386
Machine: i386
>Description:
	during presumably heavy diskio this timeout triggers the assertion. Beats me why I seems to attempt to restart the disk - maybe a probelm with the disk or the ATA emulation mode of the board for
        the actual SATA disks.
	...
	#23 0xc04ef66d in panic (fmt=0xc0afa558 "kernel %sassertion \"%s\" failed: file \"%s\", line %d") at /fs/raid1a/src/NetBSD/tc-merge/src/sys/kern/subr_prf.c:244
	#24 0xc0832019 in __kernassert (t=0xc0a3d5c0 "diagnostic ", f=0xc0a89c34 "/fs/raid1a/src/NetBSD/tc-merge/src/sys/kern/kern_synch.c", l=189, e=0xc0a89baa "(l->l_pflag & LP_INTR) == 0")
	    at /fs/raid1a/src/NetBSD/tc-merge/src/sys/lib/libkern/__assert.c:50
	#25 0xc04d1cb8 in ltsleep (ident=0xce01cc08, priority=16, wmesg=0xc0a6db52 "atapoll", timo=1, interlock=0x0) at /fs/raid1a/src/NetBSD/tc-merge/src/sys/kern/kern_synch.c:189
	#26 0xc034bc14 in wdcwait (chp=0xce73481c, mask=64, bits=64, timeout=10000, flags=0) at /fs/raid1a/src/NetBSD/tc-merge/src/sys/dev/ic/wdc.c:1272
	#27 0xc05d8795 in wdc_ata_bio_start (chp=0xce73481c, xfer=0xc47e7f18) at /fs/raid1a/src/NetBSD/tc-merge/src/sys/dev/ata/ata_wdc.c:225
	#28 0xc05d8e56 in atastart (chp=0xce73481c) at /fs/raid1a/src/NetBSD/tc-merge/src/sys/dev/ata/ata.c:896
	#29 0xc05d7469 in wdc_ata_bio (drvp=0xce73485c, ata_bio=0xd0087090) at /fs/raid1a/src/NetBSD/tc-merge/src/sys/dev/ata/ata_wdc.c:175
	#30 0xc05d51bd in __wdstart (wd=0xd0087004, bp=0xc4a5115c) at /fs/raid1a/src/NetBSD/tc-merge/src/sys/dev/ata/wd.c:758
	#31 0xc05d7305 in wdrestart (v=0xd0087004) at /fs/raid1a/src/NetBSD/tc-merge/src/sys/dev/ata/wd.c:896
	#32 0xc04d9fed in callout_softclock (v=0x0) at /fs/raid1a/src/NetBSD/tc-merge/src/sys/kern/kern_timeout.c:730
	#33 0xc04cdd57 in softint_dispatch (pinned=0xd02968c0, s=2) at /fs/raid1a/src/NetBSD/tc-merge/src/sys/kern/kern_softint.c:502
	#34 0xc0100f4d in Xsoftintr ()
	#35 0x00000000 in ?? ()

	disk related dmesg:

	Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
	    2006, 2007, 2008
	    The NetBSD Foundation, Inc.  All rights reserved.
	Copyright (c) 1982, 1986, 1989, 1991, 1993
	    The Regents of the University of California.  All rights reserved.

	NetBSD 4.99.72 (PIPADJ) #6: Fri Oct  3 17:31:10 MEST 2008
		...:/fs/raid1a/src/NetBSD/tc-merge/src/obj.i386/sys/arch/i386/compile/PIPADJ
	total memory = 3326 MB
	avail memory = 3256 MB
	timecounter: Timecounters tick every 10.000 msec
	timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100
	OEM OEM (OEM)
	mainbus0 (root)
	cpu0 at mainbus0 apid 0: Intel 686-class, 2664MHz, id 0x10677
	cpu1 at mainbus0 apid 2: Intel 686-class, 2664MHz, id 0x10677
	cpu2 at mainbus0 apid 3: Intel 686-class, 2664MHz, id 0x10677
	cpu3 at mainbus0 apid 1: Intel 686-class, 2664MHz, id 0x10677
	ioapic0 at mainbus0 apid 4: pa 0xfec00000, version 20, 24 pins
	acpi0 at mainbus0: Intel ACPICA 20080321
	acpi0: X/RSDT: OemId <IntelR,AWRDACPI,42302e31>, AslId <AWRD,00000000>
	acpi0: SCI interrupting at int 9
	acpi0: fixed-feature power button present
	pci0 at mainbus0 bus 0: configuration mode 1
	pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok
	pchb0 at pci0 dev 0 function 0
	pchb0: Intel product 0x29e0 (rev. 0x01)
	ppb0 at pci0 dev 1 function 0: Intel product 0x29e1 (rev. 0x01)
	ppb0: unsupported PCI Express version
	pci1 at ppb0 bus 1
	pci1: i/o space, memory space enabled, rd/line, wr/inv ok
	azalia1: host: Intel 82801I High Definition Audio Controller (rev. 2), HDA rev. 1.0
	ppb1 at pci0 dev 28 function 0: Intel 82801I PCI Express Port #1 (rev. 0x02)
	pci2 at ppb1 bus 2
	pci2: i/o space, memory space enabled, rd/line, wr/inv ok
	ppb2 at pci0 dev 28 function 3: Intel 82801I PCI Express Port #4 (rev. 0x02)
	pci3 at ppb2 bus 3
	pci3: i/o space, memory space enabled, rd/line, wr/inv ok
	mskc0 at pci3 dev 0 function 0mskc0: interrupt moderation is 0 us
	, Yukon-2 EC rev. A3 (0x2): ioapic0 pin 19
	msk0 at mskc0 port A: Ethernet address...
	makphy0 at msk0 phy 0: Marvell 88E1111 Gigabit PHY, rev. 2
	makphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
	ppb3 at pci0 dev 28 function 4: Intel 82801I PCI Express Port #5 (rev. 0x02)
	pci4 at ppb3 bus 4
	pci4: i/o space, memory space enabled, rd/line, wr/inv ok
	jmide0 at pci4 dev 0 function 0: JMicron Technology JMB363 SATA/PATA controller
	jmide0: 1 PATA port, 2 SATA ports
	jmide0: interrupting at ioapic0 pin 16
	ahcisata0 at jmide0
	ahcisata0: AHCI revision 1.0, 2 ports, 32 command slots, features 0xc722e000
	atabus0 at ahcisata0 channel 0
	atabus1 at ahcisata0 channel 1
	jmide0: PCI IDE interface used
	jmide0: bus-master DMA support present
	jmide0: primary channel wired to native-PCI mode
	jmide0: primary channel is PATA
	atabus2 at jmide0 channel 0
	jmide0: secondary channel wired to native-PCI mode
	jmide0: secondary channel is unused
	ppb4 at pci0 dev 28 function 5: Intel 82801I PCI Express Port #6 (rev. 0x02)
	pci5 at ppb4 bus 5
	pci5: i/o space, memory space enabled, rd/line, wr/inv ok
	ppb5 at pci0 dev 30 function 0: Intel 82801BA Hub-PCI Bridge (rev. 0x92)
	pci6 at ppb5 bus 6
	pci6: i/o space, memory space enabled
	pcib0 at pci0 dev 31 function 0
	pcib0: Intel 82801IR LPC Interface Bridge (rev. 0x02)
	piixide0 at pci0 dev 31 function 2
	piixide0: Intel 82801I Serial ATA Controller (ICH9) (rev. 0x02)
	piixide0: bus-master DMA support present
	piixide0: primary channel configured to native-PCI mode
	piixide0: using ioapic0 pin 19 for native-PCI interrupt
	atabus3 at piixide0 channel 0
	piixide0: secondary channel configured to native-PCI mode
	atabus4 at piixide0 channel 1
	piixide1 at pci0 dev 31 function 5
	piixide1: Intel 82801I Serial ATA Controller (ICH9) (rev. 0x02)
	piixide1: bus-master DMA support present
	piixide1: primary channel wired to native-PCI mode
	piixide1: using ioapic0 pin 19 for native-PCI interrupt
	atabus5 at piixide1 channel 0
	piixide1: secondary channel wired to native-PCI mode
	atabus6 at piixide1 channel 1
	wd0 at atabus2 drive 0: <IC35L180AVV207-1>
	wd0: drive supports 16-sector PIO transfers, LBA48 addressing
	wd0: 172 GB, 359010 cyl, 16 head, 63 sec, 512 bytes/sect x 361882080 sectors
	ehci1: handing over low speed device on port 2 to uhci3
	wd0: 32-bit data port
	wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)
	wd1 at atabus2 drive 1: <IC35L180AVV207-1>
	wd1: drive supports 16-sector PIO transfers, LBA48 addressing
	wd1: 172 GB, 359010 cyl, 16 head, 63 sec, 512 bytes/sect x 361882080 sectors
	wd1: 32-bit data port
	wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)
	wd0(jmide0:0:0): using PIO mode 4, Ultra-DMA mode 5 (Ultra/100) (using DMA)
	wd1(jmide0:0:1): using PIO mode 4, Ultra-DMA mode 5 (Ultra/100) (using DMA)
	atapibus0 at atabus3: 2 targets
	cd0 at atapibus0 drive 1: <ASUS    DRW-2014S1T, , 1.00> cdrom removable
	cd0: 32-bit data port
	cd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 4 (Ultra/66)
	wd2 at atabus3 drive 0: <WDC WD1500ADFD-00NLR5>
	wd2: drive supports 16-sector PIO transfers, LBA48 addressing
	wd2: 139 GB, 290721 cyl, 16 head, 63 sec, 512 bytes/sect x 293046768 sectors
	wd2: 32-bit data port
	wd2: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
	wd2(piixide0:0:0): using PIO mode 4, Ultra-DMA mode 6 (Ultra/133) (using DMA)
	cd0(piixide0:0:1): using PIO mode 4, Ultra-DMA mode 4 (Ultra/66) (using DMA)
	wd3 at atabus4 drive 0: <WDC WD1500ADFD-00NLR1>
	wd3: drive supports 16-sector PIO transfers, LBA48 addressing
	wd3: 139 GB, 290721 cyl, 16 head, 63 sec, 512 bytes/sect x 293046768 sectors
	wd3: 32-bit data port
	wd3: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
	wd3(piixide0:1:0): using PIO mode 4, Ultra-DMA mode 6 (Ultra/133) (using DMA)
	wd4 at atabus5 drive 0: <WDC WD1500ADFD-00NLR1>
	wd4: drive supports 16-sector PIO transfers, LBA48 addressing
	wd4: 139 GB, 290721 cyl, 16 head, 63 sec, 512 bytes/sect x 293046768 sectors
	wd4: 32-bit data port
	wd4: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
	wd4(piixide1:0:0): using PIO mode 4, Ultra-DMA mode 6 (Ultra/133) (using DMA)
	wd5 at atabus6 drive 0: <WDC WD1500ADFD-00NLR5>
	wd5: drive supports 16-sector PIO transfers, LBA48 addressing
	wd5: 139 GB, 290721 cyl, 16 head, 63 sec, 512 bytes/sect x 293046768 sectors
	wd5: 32-bit data port
	wd5: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
	wd5(piixide1:1:0): using PIO mode 4, Ultra-DMA mode 6 (Ultra/133) (using DMA)
	cd1 at scsibus0 target 5 lun 0: <YAMAHA, CRW-F1S, 1.0g> cdrom removable
	cd1: sync (50.00ns offset 15), 8-bit (20.000MB/s) transfers

>How-To-Repeat:
	run bacula backup on Core2 Q9450.
>Fix:
	none

>Release-Note:

>Audit-Trail:
From: Manuel Bouyer <bouyer@antioche.eu.org>
To: gnats-bugs@NetBSD.org
Cc: kern-bug-people@NetBSD.org, gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org
Subject: Re: kern/39725: wdc timeout softintr panic: (l->l_pflag & LP_INTR) == 0
Date: Sat, 11 Oct 2008 16:17:44 +0200

 On Sat, Oct 11, 2008 at 08:05:01AM +0000, kardel@netbsg.org wrote:
 > [...]
 > >Description:
 > 	during presumably heavy diskio this timeout triggers the assertion. Beats me why I seems to attempt to restart the disk - maybe a probelm with the disk or the ATA emulation mode of the board for
 >         the actual SATA disks.
 > 	...
 > 	#23 0xc04ef66d in panic (fmt=0xc0afa558 "kernel %sassertion \"%s\" failed: file \"%s\", line %d") at /fs/raid1a/src/NetBSD/tc-merge/src/sys/kern/subr_prf.c:244
 > 	#24 0xc0832019 in __kernassert (t=0xc0a3d5c0 "diagnostic ", f=0xc0a89c34 "/fs/raid1a/src/NetBSD/tc-merge/src/sys/kern/kern_synch.c", l=189, e=0xc0a89baa "(l->l_pflag & LP_INTR) == 0")
 > 	    at /fs/raid1a/src/NetBSD/tc-merge/src/sys/lib/libkern/__assert.c:50
 > 	#25 0xc04d1cb8 in ltsleep (ident=0xce01cc08, priority=16, wmesg=0xc0a6db52 "atapoll", timo=1, interlock=0x0) at /fs/raid1a/src/NetBSD/tc-merge/src/sys/kern/kern_synch.c:189
 > 	#26 0xc034bc14 in wdcwait (chp=0xce73481c, mask=64, bits=64, timeout=10000, flags=0) at /fs/raid1a/src/NetBSD/tc-merge/src/sys/dev/ic/wdc.c:1272
 > 	#27 0xc05d8795 in wdc_ata_bio_start (chp=0xce73481c, xfer=0xc47e7f18) at /fs/raid1a/src/NetBSD/tc-merge/src/sys/dev/ata/ata_wdc.c:225
 > 	#28 0xc05d8e56 in atastart (chp=0xce73481c) at /fs/raid1a/src/NetBSD/tc-merge/src/sys/dev/ata/ata.c:896
 > 	#29 0xc05d7469 in wdc_ata_bio (drvp=0xce73485c, ata_bio=0xd0087090) at /fs/raid1a/src/NetBSD/tc-merge/src/sys/dev/ata/ata_wdc.c:175
 > 	#30 0xc05d51bd in __wdstart (wd=0xd0087004, bp=0xc4a5115c) at /fs/raid1a/src/NetBSD/tc-merge/src/sys/dev/ata/wd.c:758
 > 	#31 0xc05d7305 in wdrestart (v=0xd0087004) at /fs/raid1a/src/NetBSD/tc-merge/src/sys/dev/ata/wd.c:896
 > 	#32 0xc04d9fed in callout_softclock (v=0x0) at /fs/raid1a/src/NetBSD/tc-merge/src/sys/kern/kern_timeout.c:730

 wdcwait() checks for cpu_intr_p() to know if it can tsleep() or not,
 but this doesn't work for soft interrupts (I though soft interrupt handlers
 could tsleep now). Is there other checks that can be used to know if
 tsleep() is allowed or not (beside checking LP_INTR in curlwp()).

 I'm also concerned by the fact that cpu_intr_p() doesn't catch this case,
 because biodone() can be called from soft interrupt handlers (especially
 callout handlers).

 -- 
 Manuel Bouyer <bouyer@antioche.eu.org>
      NetBSD: 26 ans d'experience feront toujours la difference
 --

From: Manuel Bouyer <bouyer@antioche.eu.org>
To: gnats-bugs@NetBSD.org
Cc: kern-bug-people@NetBSD.org, gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org
Subject: Re: kern/39725: wdc timeout softintr panic: (l->l_pflag & LP_INTR) == 0
Date: Sat, 11 Oct 2008 18:27:55 +0200

 On Sat, Oct 11, 2008 at 04:17:44PM +0200, Manuel Bouyer wrote:
 > On Sat, Oct 11, 2008 at 08:05:01AM +0000, kardel@netbsg.org wrote:
 > > [...]
 > > >Description:
 > > 	during presumably heavy diskio this timeout triggers the assertion. Beats me why I seems to attempt to restart the disk - maybe a probelm with the disk or the ATA emulation mode of the board for
 > >         the actual SATA disks.
 > > 	...
 > > 	#23 0xc04ef66d in panic (fmt=0xc0afa558 "kernel %sassertion \"%s\" failed: file \"%s\", line %d") at /fs/raid1a/src/NetBSD/tc-merge/src/sys/kern/subr_prf.c:244
 > > 	#24 0xc0832019 in __kernassert (t=0xc0a3d5c0 "diagnostic ", f=0xc0a89c34 "/fs/raid1a/src/NetBSD/tc-merge/src/sys/kern/kern_synch.c", l=189, e=0xc0a89baa "(l->l_pflag & LP_INTR) == 0")
 > > 	    at /fs/raid1a/src/NetBSD/tc-merge/src/sys/lib/libkern/__assert.c:50
 > > 	#25 0xc04d1cb8 in ltsleep (ident=0xce01cc08, priority=16, wmesg=0xc0a6db52 "atapoll", timo=1, interlock=0x0) at /fs/raid1a/src/NetBSD/tc-merge/src/sys/kern/kern_synch.c:189
 > > 	#26 0xc034bc14 in wdcwait (chp=0xce73481c, mask=64, bits=64, timeout=10000, flags=0) at /fs/raid1a/src/NetBSD/tc-merge/src/sys/dev/ic/wdc.c:1272
 > > 	#27 0xc05d8795 in wdc_ata_bio_start (chp=0xce73481c, xfer=0xc47e7f18) at /fs/raid1a/src/NetBSD/tc-merge/src/sys/dev/ata/ata_wdc.c:225
 > > 	#28 0xc05d8e56 in atastart (chp=0xce73481c) at /fs/raid1a/src/NetBSD/tc-merge/src/sys/dev/ata/ata.c:896
 > > 	#29 0xc05d7469 in wdc_ata_bio (drvp=0xce73485c, ata_bio=0xd0087090) at /fs/raid1a/src/NetBSD/tc-merge/src/sys/dev/ata/ata_wdc.c:175
 > > 	#30 0xc05d51bd in __wdstart (wd=0xd0087004, bp=0xc4a5115c) at /fs/raid1a/src/NetBSD/tc-merge/src/sys/dev/ata/wd.c:758
 > > 	#31 0xc05d7305 in wdrestart (v=0xd0087004) at /fs/raid1a/src/NetBSD/tc-merge/src/sys/dev/ata/wd.c:896
 > > 	#32 0xc04d9fed in callout_softclock (v=0x0) at /fs/raid1a/src/NetBSD/tc-merge/src/sys/kern/kern_timeout.c:730
 > 
 > wdcwait() checks for cpu_intr_p() to know if it can tsleep() or not,
 > but this doesn't work for soft interrupts (I though soft interrupt handlers
 > could tsleep now). Is there other checks that can be used to know if
 > tsleep() is allowed or not (beside checking LP_INTR in curlwp()).
 > 
 > I'm also concerned by the fact that cpu_intr_p() doesn't catch this case,
 > because biodone() can be called from soft interrupt handlers (especially
 > callout handlers).

 This isn't an issue, as biodone2() is also called from a soft interrupt.
 But the first question about cpu_intr_p() and tsleep() remains.

 -- 
 Manuel Bouyer <bouyer@antioche.eu.org>
      NetBSD: 26 ans d'experience feront toujours la difference
 --

From: Takahiro Kambe <taca@back-street.net>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/39725: wdc timeout softintr panic: (l->l_pflag & LP_INTR)
 == 0
Date: Sun, 19 Oct 2008 10:28:20 +0900 (JST)

 Just additonaly report.

 With my notebook (Panasonic CF-R5), this panic happens after system
 resume.  Stacktrace is the same as original report.

 -- 
 Takahiro Kambe <taca@back-street.net>

Responsible-Changed-From-To: kern-bug-people->bouyer
Responsible-Changed-By: bouyer@NetBSD.org
Responsible-Changed-When: Sun, 16 Nov 2008 20:42:28 +0000
Responsible-Changed-Why:
My bug


State-Changed-From-To: open->feedback
State-Changed-By: bouyer@NetBSD.org
State-Changed-When: Sun, 16 Nov 2008 20:42:28 +0000
State-Changed-Why:
Hi,
I just commited a fix to -current, can you see if you can reproduce it ?


From: Frank Kardel <kardel@netbsd.org>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: kern/39725 (panic: diagnostic assertion "(l->l_pflag & LP_INTR)
 == 0" failed: file "/src/sys/kern/kern_synch.c", line 189)
Date: Sun, 16 Nov 2008 21:55:14 +0100

 Thanks for the fix.

 Reproducing is currently even harder than before - I just exchanged the 
 disks the weekend against SATA drives - for more performance, less errors.

 The problem was caused by an "interface CRC error" (I love those!) that 
 in consequence invoked the reset.
 It appeared when dumping a psql database and the housing was closed.

 If you want I can put the drives back next weekend and see whether I can 
 reproduce the interface CRC errors..

 Frank

 bouyer@NetBSD.org wrote:
 > Synopsis: panic: diagnostic assertion "(l->l_pflag & LP_INTR) == 0" failed: file "/src/sys/kern/kern_synch.c", line 189
 >
 > Responsible-Changed-From-To: kern-bug-people->bouyer
 > Responsible-Changed-By: bouyer@NetBSD.org
 > Responsible-Changed-When: Sun, 16 Nov 2008 20:42:28 +0000
 > Responsible-Changed-Why:
 > My bug
 >
 >
 > State-Changed-From-To: open->feedback
 > State-Changed-By: bouyer@NetBSD.org
 > State-Changed-When: Sun, 16 Nov 2008 20:42:28 +0000
 > State-Changed-Why:
 > Hi,
 > I just commited a fix to -current, can you see if you can reproduce it ?
 >
 >
 >   

From: Manuel Bouyer <bouyer@antioche.eu.org>
To: gnats-bugs@NetBSD.org
Cc: gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org, kardel@netbsg.org
Subject: Re: kern/39725 (panic: diagnostic assertion "(l->l_pflag & LP_INTR) == 0" failed: file "/src/sys/kern/kern_synch.c", line 189)
Date: Tue, 18 Nov 2008 20:18:32 +0100

 On Sun, Nov 16, 2008 at 09:00:06PM +0000, Frank Kardel wrote:
 >  Thanks for the fix.
 >  
 >  Reproducing is currently even harder than before - I just exchanged the 
 >  disks the weekend against SATA drives - for more performance, less errors.
 >  
 >  The problem was caused by an "interface CRC error" (I love those!) that 
 >  in consequence invoked the reset.
 >  It appeared when dumping a psql database and the housing was closed.
 >  
 >  If you want I can put the drives back next weekend and see whether I can 
 >  reproduce the interface CRC errors..

 If it's not too much work for you it would be a good test. I've been able to
 emulate some error, but I'm not sure it's the same as real errors.

 -- 
 Manuel Bouyer <bouyer@antioche.eu.org>
      NetBSD: 26 ans d'experience feront toujours la difference
 --

State-Changed-From-To: feedback->closed
State-Changed-By: bouyer@NetBSD.org
State-Changed-When: Sun, 07 Dec 2008 22:46:04 +0000
State-Changed-Why:
Frank can't reproduce the IDE errors; test I ran on my side show
it's fixed.


>Unformatted:

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD: gnats_config.sh,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2007 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.