Re: kern/40674: Ricoh 5C478 PCI-CardBus bridge gets bad Vcc request

[Ignatios Souvatzis <ignatios%cs.uni-bonn.de@localhost>]

The following reply was made to PR kern/40674; it has been noted by GNATS.

From: Ignatios Souvatzis <ignatios%cs.uni-bonn.de@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: kern/40674: Ricoh 5C478 PCI-CardBus bridge gets bad Vcc request
Date: Tue, 17 Feb 2009 16:24:53 +0100

 The above cbb0: bad Vcc request happens after midi2 - like this:
 
 |cbb0 at pci0 dev 12 function 0: vendor 0x1180 product 0x0478 (rev. 0x80)
 |cbb1 at pci0 dev 12 function 1: vendor 0x1180 product 0x0478 (rev. 0x80)
 |isa0 at pcib0
 |com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
 |isapnp0 at isa0 port 0x279: ISA Plug 'n Play device support
 |fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2
 |isapnp0: no ISA Plug 'n Play devices found
 |opl0 at yds0: model OPL3
 |midi1 at opl0: DS-1 integrated Yamaha OPL3 (CPU-intensive output)
 |mpu0 at yds0
 |midi2 at mpu0: Yamaha DS-1 MIDI UART (CPU-intensive output)
 |cbb0: bad Vcc request. sock_ctrl 0xf000ff00, sock_status 0xf000e2c3
 |cbb0: disabling socket
 |new status 0xf000e2c3
 |cbb0: cacheline 0x0 lattimer 0x10
 |...
 
 When I reboot from netbsd4 into netbsd5, I get a NMI instead:
 
 |mpu0 at yds0
 |midi2 at mpu0: Yamaha DS-1 MIDI UART (CPU-intensive output)
 |NMI ... going to debugger
 |Stopped in pid 0.1 (system) at  netbsd:bus_space_write_1+0x15:  ret
 |db{0}> t
 
|bus_space_write_1(8,80006000,10,40000000,10000,0,c0c44b38,cb199624,cae87e58,c0a56d70)
 at netbsd:bus_space_write_1+0x15
 
|pccbb_pci_callback(cb199748,10,c0a68f54,c0a58f78,c09d2a31,0,c0c44b98,c0473423,cae8fc30,cae8fc30)
 at netbsd:pccbb_pci_callback+0xd1
 
|config_process_deferred(cae8fc30,cae8fc30,c0c44bdc,0,c0c44bdc,c0c44ba8,cae8fc30,cacafcd8,1,c0c44c00)
 at netbsd:config_process_deferred+0x44
 
|config_attach_loc(cacafcd8,c0a57538,0,c0c44bdc,c05708a0,0,c0c44c28,c056c291,cacafcd8,c09d2c95)
 at netbsd:config_attach_loc+0x193
 
|config_found_ia(cacafcd8,c09d2c95,c0c44bdc,c05708a0,ca94ef50,c0c44bdc,0,0,0,1) 
at netbsd:config_found_ia+0x32
 
|mainbus_attach(0,cacafcd8,0,c047207e,c09d20fb,c09d20fb,cacafcd8,0,c09d20fb,c4a000)
 at netbsd:mainbus_attach+0x3a1
 |config_attach_loc(0,c0a57520,0,0,0,c4a000,c0c44c98,c0473644,0,c0a57520) at 
netbsd:config_attach_loc+0x163
 |config_attach(0,c0a57520,0,0,c0c41014,c41000,c0c44cb8,c0534268,c09d20fb,0) at 
netbsd:config_attach+0x2c
 
|config_rootfound(c09d20fb,0,0,c0c41014,c41000,c0c41014,c0c44ce8,c04737ed,c0a65720,c4a000)
 at netbsd:config_rootfound+0x44
 
|cpu_configure(c0a65720,c4a000,c0c44ce8,c04236f4,c0b02384,c0c41014,c0c44ce8,c04d4133,c0b1cda0,c0c41014)
 at netbsd:cpu_configure+0x28
 |configure(c0b01400,a,14,f9300,0,0,0,0,0,0) at netbsd:configure+0x3d
 |main(0,c01002cd,0,0,0,0,0,0,0,0) at netbsd:main+0x1aa
 |db{0}>
 
 I've been told that this suggests an uninitialized bus_space_tag in the
 cbb driver.
 
 Regards,
        -is