NetBSD Problem Report #38698

From gson@gson.org  Mon May 19 12:11:17 2008
Return-Path: <gson@gson.org>
Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11])
	by narn.NetBSD.org (Postfix) with ESMTP id 4F61C63B8BC
	for <gnats-bugs@gnats.NetBSD.org>; Mon, 19 May 2008 12:11:17 +0000 (UTC)
Message-Id: <20080519121112.AE1E47603B@guava.gson.org>
Date: Mon, 19 May 2008 15:11:12 +0300 (EEST)
From: gson@gson.org (Andreas Gustafsson)
Reply-To: gson@gson.org (Andreas Gustafsson)
To: gnats-bugs@gnats.NetBSD.org
Subject: NMI during boot on Fujitsu-Siemens Lifebook S-4546
X-Send-Pr-Version: 3.95

>Number:         38698
>Category:       kern
>Synopsis:       NMI during boot on Fujitsu-Siemens Lifebook S-4546
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    dyoung
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon May 19 12:15:00 +0000 2008
>Closed-Date:    Thu Jun 05 08:14:30 +0000 2008
>Last-Modified:  Thu Jun 05 08:14:31 +0000 2008
>Originator:     Andreas Gustafsson
>Release:        NetBSD 4.99.62 as of 20080513-1503 EET
>Organization:
>Environment:
System: NetBSD 4.99.62
Architecture: i386
Machine: i386
>Description:

When I boot a NetBSD-current installation CD on a Fujitsu-Siemens Lifebook
S-4546 laptop, it drops into DDB with an NMI during autoconfiguration.

The final messages (transcribed by hand) are:

  cbb0 at pci0 dev 19 function 0: vendor 0x1217 product 0x6933 (rev. 0x02)
  cbb1 at pci0 dev 19 function 1: vendor 0x1217 product 0x6933 (rev. 0x02)
  vga1 at pci0 dev 20 function 0: vendor 0x1002 product 0x4c52 (rev. 0x64)
  wsdisplay0 at vga1 kbdmux 1: console (80x25, vt100 emulation)
  drm at vga1 not configured
  NMI ... going to debugger
  Stopped in pid 0.1 (system) at  netbsd:outl+0x9:        ret
  db{0}> 

The first few locations shown in the stack trace are

  outl+0x9
  pccbb_chipinint+0x3b5
  pccbb_pci_callback+0xde
  config_process_deferred+0x44

The instruction at outl+0x8 is "outl %eax,%dx".  According to "show
registers", eax is 0x0, and edx is 0xcf8.  I believe this outl() is
part of the pci_conf_write() to set the CardBus latency timer at line
759 of pccbb.c.

Booting a 4.0 release CD works.

>How-To-Repeat:

>Fix:

The following change may be more of a workaround than a fix, but
it make the machine boot successfully.

Index: pccbb.c
===================================================================
RCS file: /cvsroot/src/sys/dev/pci/pccbb.c,v
retrieving revision 1.167
diff -u -r1.167 pccbb.c
--- pccbb.c	4 Mar 2008 22:15:16 -0000	1.167
+++ pccbb.c	19 May 2008 12:04:56 -0000
@@ -746,7 +746,9 @@
 	/* I believe it is harmless. */
 	csr |= (PCI_COMMAND_IO_ENABLE | PCI_COMMAND_MEM_ENABLE |
 	    PCI_COMMAND_MASTER_ENABLE);
+#if 0
 	csr |= (PCI_COMMAND_PARITY_ENABLE|PCI_COMMAND_SERR_ENABLE);
+#endif
 	pci_conf_write(pc, tag, PCI_COMMAND_STATUS_REG, csr);

 	/*

>Release-Note:

>Audit-Trail:

Responsible-Changed-From-To: kern-bug-people->dyoung
Responsible-Changed-By: dyoung@NetBSD.org
Responsible-Changed-When: Tue, 20 May 2008 04:10:50 +0000
Responsible-Changed-Why:
I'll take this.


From: David Young <dyoung@pobox.com>
To: gnats-bugs@NetBSD.org
Cc: kern-bug-people@NetBSD.org, gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org
Subject: Re: kern/38698: NMI during boot on Fujitsu-Siemens Lifebook S-4546
Date: Mon, 19 May 2008 23:20:44 -0500

 On Mon, May 19, 2008 at 12:15:00PM +0000, Andreas Gustafsson wrote:
 >   NMI ... going to debugger
 >   Stopped in pid 0.1 (system) at  netbsd:outl+0x9:        ret
 >   db{0}> 
 > 
 > The first few locations shown in the stack trace are
 > 
 >   outl+0x9
 >   pccbb_chipinint+0x3b5
 >   pccbb_pci_callback+0xde
 >   config_process_deferred+0x44
 > 
 > The instruction at outl+0x8 is "outl %eax,%dx".  According to "show
 > registers", eax is 0x0, and edx is 0xcf8.  I believe this outl() is
 > part of the pci_conf_write() to set the CardBus latency timer at line
 > 759 of pccbb.c.

 pci_conf_write() is not in the stack trace?  Please capture and send
 the entire stack trace (type 'bt' at the db{0}> prompt) if you can.
 Please send the dmesg you get when you apply your workaround, also.

 Can you examine the netbsd.gdb file with gdb for me?  The gdb command
 'l *(pccbb_chipinit+0x3b5)' will tell you a line number in pccbb_chipinit.
 I would like to know that line number.

 -- 
 David Young             OJC Technologies
 dyoung@ojctech.com      Urbana, IL * (217) 278-3933 ext 24

From: gson@gson.org (Andreas Gustafsson)
To: gnats-bugs@NetBSD.org
Cc: dyoung@NetBSD.org
Subject: Re: kern/38698: NMI during boot on Fujitsu-Siemens Lifebook S-4546
Date: Tue, 20 May 2008 21:28:46 +0300

 David Young wrote:
 >  pci_conf_write() is not in the stack trace?

 That is correct.  I assume this is just ddb having some kind of
 issue with the callers of leaf functions.  I tried building a new
 kernel without optimization, but ddb is still not showing
 pci_conf_write() in the backtrace.

 > Please capture and send
 > the entire stack trace (type 'bt' at the db{0}> prompt) if you can.

 The machine lacks a serial port and it's too much text to to
 transcribe by hand, but here's a pair of screenshots:

 http://www.gson.org/netbsd/bugs/38698/bt1.jpg
 http://www.gson.org/netbsd/bugs/38698/bt2.jpg

 This is from a non-optimized kernel on a live CD, built using
 mklivecd from 20080516-1010 EET kernel sources.

 >  Please send the dmesg you get when you apply your workaround, also.

 http://www.gson.org/netbsd/bugs/38698/dmesg1.jpg
 http://www.gson.org/netbsd/bugs/38698/dmesg2.jpg
 http://www.gson.org/netbsd/bugs/38698/dmesg3.jpg
 http://www.gson.org/netbsd/bugs/38698/dmesg4.jpg
 http://www.gson.org/netbsd/bugs/38698/dmesg5.jpg
 http://www.gson.org/netbsd/bugs/38698/dmesg6.jpg
 http://www.gson.org/netbsd/bugs/38698/dmesg7.jpg

 >  Can you examine the netbsd.gdb file with gdb for me?  The gdb command
 >  'l *(pccbb_chipinit+0x3b5)' will tell you a line number in pccbb_chipinit.
 >  I would like to know that line number.

 Sure.  This is with the new kernel, which shows pccbb_chipinit+0xdd in
 the backtrace:

   (gdb) l *(pccbb_chipinit+0xdd)
   0xc075373f is in pccbb_chipinit (/usr/src/sys/dev/pci/pccbb.c:767).

 I believe the NMI actually occurs in the pci_conf_write call on line
 759, with line 767 being the return address of the function call in
 which the NMI occurs:

    752             /*                                                                           x
    753              * Set CardBus latency timer.                                                x
    754              */                                                                          x
    755             lscp = pci_conf_read(pc, tag, PCI_CB_LSCP_REG);                              x
    756             if (PCI_CB_LATENCY(lscp) < 0x20) {                                           x
    757                     lscp &= ~(PCI_CB_LATENCY_MASK << PCI_CB_LATENCY_SHIFT);              x
    758                     lscp |= (0x20 << PCI_CB_LATENCY_SHIFT);                              x
    759                     pci_conf_write(pc, tag, PCI_CB_LSCP_REG, lscp);                      x
    760             }                                                                            x
    761             DPRINTF(("CardBus latency timer 0x%x (%x)\n",                                x
    762                 PCI_CB_LATENCY(lscp), pci_conf_read(pc, tag, PCI_CB_LSCP_REG)));         x
    763                                                                                          x
    764             /*                                                                           x
    765              * Set PCI latency timer.                                                    x
    766              */                                                                          x
    767             bhlc = pci_conf_read(pc, tag, PCI_BHLC_REG);                                 x

 -- 
 Andreas Gustafsson, gson@gson.org

From: gson@gson.org (Andreas Gustafsson)
To: David Young <dyoung@pobox.com>
Cc: gnats-bugs@NetBSD.org
Subject: Re: kern/38698: NMI during boot on Fujitsu-Siemens Lifebook S-4546
Date: Wed, 21 May 2008 18:10:07 +0300

 David Young wrote:
 > Try commenting out line 759.  Is there an NMI somewhere else, or does
 > it work ok?

 When I do that, I still get an NMI.  The backtrace contains
 pccbb_chipinit+0x118, which corresponds to line 778:

 777             /* Route functional interrupts to PCI. */
 778             bcr = pci_conf_read(pc, tag, PCI_BRIDGE_CONTROL_REG);

 > Do your CardBus slots work?

 Yes, when I turn off PCI_COMMAND_PARITY_ENABLE and PCI_COMMAND_SERR_ENABLE,
 the CardBus slot works (there's only one of them).

 > I'm curious what 'pcictl pci0 dump -d 0' says about the PCI host
 > bridge configuration.

 PCI configuration registers:
   Common header:
     0x00: 0x71948086 0x32000006 0x06000001 0x00804000

     Vendor Name: Intel (0x8086)
     Device Name: 82443MX Host Bridge/Controller (0x7194)
     Command register: 0x0006
       I/O space accesses: off
       Memory space accesses: on
       Bus mastering: on
       Special cycles: off
       MWI transactions: off
       Palette snooping: off
       Parity error checking: off
       Address/data stepping: off
       System error (SERR): off
       Fast back-to-back transactions: off
       Interrupt disable: off
     Status register: 0x3200
       Capability List support: off
       66 MHz capable: off
       User Definable Features (UDF) support: off
       Fast back-to-back capable: off
       Data parity error detected: off
       DEVSEL timing: medium (0x1)
       Slave signaled Target Abort: off
       Master received Target Abort: on
       Master received Master Abort: on
       Asserted System Error (SERR): off
       Parity error detected: off
     Class Name: bridge (0x06)
     Subclass Name: host (0x00)
     Interface: 0x00
     Revision ID: 0x01
     BIST: 0x00
     Header Type: 0x00+multifunction (0x80)
     Latency Timer: 0x40
     Cache Line Size: 0x00

   Type 0 ("normal" device) header:
     0x10: 0x00000000 0x00000000 0x00000000 0x00000000
     0x20: 0x00000000 0x00000000 0x00000000 0x107f10cf
     0x30: 0x00000000 0x00000000 0x00000000 0x00000000

     Base address register at 0x10
       not implemented(?)
     Base address register at 0x14
       not implemented(?)
     Base address register at 0x18
       not implemented(?)
     Base address register at 0x1c
       not implemented(?)
     Base address register at 0x20
       not implemented(?)
     Base address register at 0x24
       not implemented(?)
     Cardbus CIS Pointer: 0x00000000
     Subsystem vendor ID: 0x10cf
     Subsystem ID: 0x107f
     Expansion ROM Base Address: 0x00000000
     Reserved @ 0x34: 0x00000000
     Reserved @ 0x38: 0x00000000
     Maximum Latency: 0x00
     Minimum Grant: 0x00
     Interrupt pin: 0x00 (none)
     Interrupt line: 0x00

   Device-dependent header:
     0x40: 0x00000000 0x00000000 0x00000000 0x00000000
     0x50: 0x0000800c 0x09000000 0x11111000 0x11100000
     0x60: 0x20202010 0x00000000 0x00c00a00 0x00002000
     0x70: 0x380a1f20 0x0107000a 0x00da0326 0x00000000
     0x80: 0x00000000 0x00000000 0x00000000 0x00000000
     0x90: 0x00080000 0x00000104 0x00000000 0x00000000
     0xa0: 0x00000000 0x00000000 0x00000000 0x00000000
     0xb0: 0x00000000 0x00000000 0x00000000 0x00000000
     0xc0: 0x00000000 0x00000000 0xa7e70018 0x00000028
     0xd0: 0x00000000 0x00000000 0x00000000 0x00000000
     0xe0: 0x74afafac 0x80003e87 0x74afaeac 0x00003e87
     0xf0: 0x00000000 0x2028fa00 0x00000f3a 0x00000000

 -- 
 Andreas Gustafsson, gson@gson.org

From: David Young <dyoung@pobox.com>
To: Andreas Gustafsson <gson@gson.org>
Cc: gnats-bugs@NetBSD.org
Subject: Re: kern/38698: NMI during boot on Fujitsu-Siemens Lifebook S-4546
Date: Wed, 21 May 2008 16:52:38 -0500

 On Wed, May 21, 2008 at 06:10:07PM +0300, Andreas Gustafsson wrote:
 > David Young wrote:
 > > Try commenting out line 759.  Is there an NMI somewhere else, or does
 > > it work ok?
 > 
 > When I do that, I still get an NMI.  The backtrace contains
 > pccbb_chipinit+0x118, which corresponds to line 778:
 > 
 > 777             /* Route functional interrupts to PCI. */
 > 778             bcr = pci_conf_read(pc, tag, PCI_BRIDGE_CONTROL_REG);
 > 
 > > Do your CardBus slots work?
 > 
 > Yes, when I turn off PCI_COMMAND_PARITY_ENABLE and PCI_COMMAND_SERR_ENABLE,
 > the CardBus slot works (there's only one of them).

 Oh.  Which one is attached?

 > > I'm curious what 'pcictl pci0 dump -d 0' says about the PCI host
 > > bridge configuration.
 > 
 > PCI configuration registers:

 Thanks.

 What does pcictl say about the CardBus bridge configuration?  Run

 pcictl pci0 dump -d 19 -f 0
 pcictl pci0 dump -d 19 -f 1

 Dave

 -- 
 David Young             OJC Technologies
 dyoung@ojctech.com      Urbana, IL * (217) 278-3933 ext 24

From: gson@gson.org (Andreas Gustafsson)
To: David Young <dyoung@pobox.com>
Cc: gnats-bugs@NetBSD.org
Subject: Re: kern/38698: NMI during boot on Fujitsu-Siemens Lifebook S-4546
Date: Thu, 22 May 2008 08:32:52 +0300

 David Young wrote:
 > > the CardBus slot works (there's only one of them).
 > 
 > Oh.  Which one is attached?

 cardslot0.

 > What does pcictl say about the CardBus bridge configuration?  Run
 > 
 > pcictl pci0 dump -d 19 -f 0

 PCI configuration registers:
   Common header:
     0x00: 0x69331217 0x04100007 0x06070002 0x00821000

     Vendor Name: O2 Micro (0x1217)
     Device Name: OZ6933 PCI-CardBus Bridge (0x6933)
     Command register: 0x0007
       I/O space accesses: on
       Memory space accesses: on
       Bus mastering: on
       Special cycles: off
       MWI transactions: off
       Palette snooping: off
       Parity error checking: off
       Address/data stepping: off
       System error (SERR): off
       Fast back-to-back transactions: off
       Interrupt disable: off
     Status register: 0x0410
       Capability List support: on
       66 MHz capable: off
       User Definable Features (UDF) support: off
       Fast back-to-back capable: off
       Data parity error detected: off
       DEVSEL timing: slow (0x2)
       Slave signaled Target Abort: off
       Master received Target Abort: off
       Master received Master Abort: off
       Asserted System Error (SERR): off
       Parity error detected: off
     Class Name: bridge (0x06)
     Subclass Name: CardBus (0x07)
     Interface: 0x00
     Revision ID: 0x02
     BIST: 0x00
     Header Type: 0x02+multifunction (0x82)
     Latency Timer: 0x10
     Cache Line Size: 0x00

   Type 2 (PCI-CardBus bridge) header:
     0x10: 0x40000000 0x220000a0 0x20010100 0xfffff000
     0x20: 0x00000000 0xfffff000 0x00000000 0x0000fffd
     0x30: 0x00000001 0x0000fffd 0x00000001 0x04230109
     0x40: 0x10e610cf 0x00000001

     Base address register at 0x10 (CardBus socket/ExCA registers)
       type: 32-bit nonprefetchable memory
       base: 0x40000000, not sized
     Capability list pointer: 0xa0
     Secondary status register: 0x2200
       66 MHz capable: off
       User Definable Features (UDF) support: off
       Fast back-to-back capable: off
       Data parity error detection: off
       DEVSEL timing: medium (0x1)
       PCI target aborts terminate CardBus bus master transactions: off
       CardBus target aborts terminate PCI bus master transactions: off
       Bus initiator aborts terminate initiator transactions: on
       System error: off
       Parity error: off
     PCI bus number: 0x00
     CardBus bus number: 0x01
     Subordinate bus number: 0x01
     CardBus latency timer: 0x20
     CardBus memory region 0:
       base register:  0xfffff000
       limit register: 0x00000000
     CardBus memory region 1:
       base register:  0xfffff000
       limit register: 0x00000000
     CardBus I/O region 0:
       base register:  0x0000fffd
       limit register: 0x00000001
     CardBus I/O region 1:
       base register:  0x0000fffd
       limit register: 0x00000001
     Interrupt line: 0x09
     Interrupt pin: 0x01 (pin A)
     Bridge control register: 0x0423
       Parity error response: on
       CardBus SERR forwarding: on
       ISA enable: off
       VGA enable: off
       CardBus master abort reporting: on
       CardBus reset: off
       Functional interrupts routed by ExCA registers: off
       Memory window 0 prefetchable: off
       Memory window 1 prefetchable: off
       Write posting enable: on
     Subsystem vendor ID: 0x10cf
     Subsystem ID: 0x10e6
     Base address register at 0x44 (legacy-mode registers)
       type: i/o
       base: 0x00000000, not sized

   Capability register at 0xa0
     type: 0x01 (Power Management, rev. 1.0)

   Device-dependent header:
     0x48: 0x00000000 0x00000000
     0x50: 0x00000000 0x00000000 0x00000000 0x00000000
     0x60: 0x00000000 0x00000000 0x00000000 0x00000000
     0x70: 0x00000000 0x00000000 0x00000000 0x00000000
     0x80: 0x00000000 0x00000000 0x00000000 0x00000000
     0x90: 0x0c0023bf 0x824203ea 0x10500000 0x00000000
     0xa0: 0xfe020001 0x00c04000 0x00000000 0x00000000
     0xb0: 0x00000000 0x00000000 0x00000000 0x00000000
     0xc0: 0x00000000 0x00000000 0x00000000 0x00000000
     0xd0: 0x00000000 0x00000000 0x00000000 0x00000000
     0xe0: 0x00000000 0x00000000 0x00000000 0x00000000
     0xf0: 0x00000000 0x00000000 0x00000000 0x00000000

 > pcictl pci0 dump -d 19 -f 1

 PCI configuration registers:
   Common header:
     0x00: 0x69331217 0x04100007 0x06070002 0x00821000

     Vendor Name: O2 Micro (0x1217)
     Device Name: OZ6933 PCI-CardBus Bridge (0x6933)
     Command register: 0x0007
       I/O space accesses: on
       Memory space accesses: on
       Bus mastering: on
       Special cycles: off
       MWI transactions: off
       Palette snooping: off
       Parity error checking: off
       Address/data stepping: off
       System error (SERR): off
       Fast back-to-back transactions: off
       Interrupt disable: off
     Status register: 0x0410
       Capability List support: on
       66 MHz capable: off
       User Definable Features (UDF) support: off
       Fast back-to-back capable: off
       Data parity error detected: off
       DEVSEL timing: slow (0x2)
       Slave signaled Target Abort: off
       Master received Target Abort: off
       Master received Master Abort: off
       Asserted System Error (SERR): off
       Parity error detected: off
     Class Name: bridge (0x06)
     Subclass Name: CardBus (0x07)
     Interface: 0x00
     Revision ID: 0x02
     BIST: 0x00
     Header Type: 0x02+multifunction (0x82)
     Latency Timer: 0x10
     Cache Line Size: 0x00

   Type 2 (PCI-CardBus bridge) header:
     0x10: 0x40001000 0x020000a0 0x20020200 0xfffff000
     0x20: 0x00000000 0xfffff000 0x00000000 0x0000fffd
     0x30: 0x00000001 0x0000fffd 0x00000001 0x04e30209
     0x40: 0x10e610cf 0x00000001

     Base address register at 0x10 (CardBus socket/ExCA registers)
       type: 32-bit nonprefetchable memory
       base: 0x40001000, not sized
     Capability list pointer: 0xa0
     Secondary status register: 0x0200
       66 MHz capable: off
       User Definable Features (UDF) support: off
       Fast back-to-back capable: off
       Data parity error detection: off
       DEVSEL timing: medium (0x1)
       PCI target aborts terminate CardBus bus master transactions: off
       CardBus target aborts terminate PCI bus master transactions: off
       Bus initiator aborts terminate initiator transactions: off
       System error: off
       Parity error: off
     PCI bus number: 0x00
     CardBus bus number: 0x02
     Subordinate bus number: 0x02
     CardBus latency timer: 0x20
     CardBus memory region 0:
       base register:  0xfffff000
       limit register: 0x00000000
     CardBus memory region 1:
       base register:  0xfffff000
       limit register: 0x00000000
     CardBus I/O region 0:
       base register:  0x0000fffd
       limit register: 0x00000001
     CardBus I/O region 1:
       base register:  0x0000fffd
       limit register: 0x00000001
     Interrupt line: 0x09
     Interrupt pin: 0x02 (pin B)
     Bridge control register: 0x04e3
       Parity error response: on
       CardBus SERR forwarding: on
       ISA enable: off
       VGA enable: off
       CardBus master abort reporting: on
       CardBus reset: on
       Functional interrupts routed by ExCA registers: on
       Memory window 0 prefetchable: off
       Memory window 1 prefetchable: off
       Write posting enable: on
     Subsystem vendor ID: 0x10cf
     Subsystem ID: 0x10e6
     Base address register at 0x44 (legacy-mode registers)
       type: i/o
       base: 0x00000000, not sized

   Capability register at 0xa0
     type: 0x01 (Power Management, rev. 1.0)

   Device-dependent header:
     0x48: 0x00000000 0x00000000
     0x50: 0x00000000 0x00000000 0x00000000 0x00000000
     0x60: 0x00000000 0x00000000 0x00000000 0x00000000
     0x70: 0x00000000 0x00000000 0x00000000 0x00000000
     0x80: 0x00000000 0x00000000 0x00000000 0x00000000
     0x90: 0x0c0023bf 0x824203ea 0x10500000 0x00000000
     0xa0: 0xfe020001 0x00c04000 0x00000000 0x00000000
     0xb0: 0x00000000 0x00000000 0x00000000 0x00000000
     0xc0: 0x00000000 0x00000000 0x00000000 0x00000000
     0xd0: 0x00000000 0x00000000 0x00000000 0x00000000
     0xe0: 0x00000000 0x00000000 0x00000000 0x00000000
     0xf0: 0x00000000 0x00000000 0x00000000 0x00000000

 -- 
 Andreas Gustafsson, gson@gson.org

From: David Young <dyoung@pobox.com>
To: Andreas Gustafsson <gson@gson.org>
Cc: gnats-bugs@NetBSD.org
Subject: Re: kern/38698: NMI during boot on Fujitsu-Siemens Lifebook S-4546
Date: Thu, 22 May 2008 13:21:43 -0500

 On Wed, May 21, 2008 at 06:10:07PM +0300, Andreas Gustafsson wrote:
 > David Young wrote:
 > > Try commenting out line 759.  Is there an NMI somewhere else, or does
 > > it work ok?
 > 
 > When I do that, I still get an NMI.  The backtrace contains
 > pccbb_chipinit+0x118, which corresponds to line 778:
 > 
 > 777             /* Route functional interrupts to PCI. */
 > 778             bcr = pci_conf_read(pc, tag, PCI_BRIDGE_CONTROL_REG);
 > 
 > > Do your CardBus slots work?
 > 
 > Yes, when I turn off PCI_COMMAND_PARITY_ENABLE and PCI_COMMAND_SERR_ENABLE,
 > the CardBus slot works (there's only one of them).

 Maybe the O2 Micro chips don't wire up the parity line.  What if you turn
 off PCI_COMMAND_PARITY_ENABLE, but you leave PCI_COMMAND_SERR_ENABLE on?

 It really looks to me like a defect in the O2 Micro PCI implementation.

 Dave

 -- 
 David Young             OJC Technologies
 dyoung@ojctech.com      Urbana, IL * (217) 278-3933 ext 24

From: gson@gson.org (Andreas Gustafsson)
To: David Young <dyoung@pobox.com>
Cc: gnats-bugs@NetBSD.org
Subject: Re: kern/38698: NMI during boot on Fujitsu-Siemens Lifebook S-4546
Date: Fri, 23 May 2008 18:10:43 +0300

 David Young wrote:
 > Maybe the O2 Micro chips don't wire up the parity line.  What if you turn
 > off PCI_COMMAND_PARITY_ENABLE, but you leave PCI_COMMAND_SERR_ENABLE on?

 When I do that, the machine boots successfully.
 -- 
 Andreas Gustafsson, gson@gson.org

State-Changed-From-To: open->closed
State-Changed-By: gson@NetBSD.org
State-Changed-When: Thu, 05 Jun 2008 08:14:30 +0000
State-Changed-Why:
Fixed by dyoung in pccbb.c 1.169.


>Unformatted:

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.