Does anyone use a FDDI card on 5.0?
Andrew Gallatin
gallatin at cs.duke.edu
Mon Mar 31 12:01:56 PST 2003
Oliver Lehmann writes:
>
> but why i got no crash-dump?
crashdumps are hit or miss in -current. Besides, you've not finished
booting yet, so the dump device might not have gotten set.
> (kgdb) l *0xfffffc000039b51c
> 0xfffffc000039b51c is in pdq_stop (/usr/src/sys/dev/pdq/pdq.c:1327).
> 1322 for (cnt = 0; cnt < 1000; cnt++) {
> 1323 PDQ_OS_CONSUMER_POSTSYNC(pdq);
> 1324 pdq_process_command_responses(pdq);
> 1325 if (pdq->pdq_command_info.ci_response_producer == pdq->pdq_command_info.ci_response_completion)
> 1326 break;
> 1327 PDQ_OS_USEC_DELAY(1000);
> 1328 }
> 1329 state = PDQ_PSTS_ADAPTER_STATE(PDQ_CSR_READ(csrs, csr_port_status));
> 1330 }
> 1331
> (kgdb)
Probably something in pdq_process_command_responses().
Maybe its accessing PCI mem directly w/going through busspace
accessors.
Either that, or the device initiated a bad dma...
Can you try the following patch & see if it helps?
Drew
Index: if_fpa.c
===================================================================
RCS file: /home/ncvs/src/sys/dev/pdq/if_fpa.c,v
retrieving revision 1.17
diff -u -r1.17 if_fpa.c
--- if_fpa.c 2 Jun 2002 20:05:45 -0000 1.17
+++ if_fpa.c 31 Mar 2003 20:00:17 -0000
@@ -144,7 +144,7 @@
sc->mem_rid = PCI_CBMA;
sc->mem_type = SYS_RES_MEMORY;
sc->mem = bus_alloc_resource(dev, sc->mem_type, &sc->mem_rid,
- 0, ~0, 1, RF_ACTIVE);
+ 0, ~0, 1, RF_ACTIVE | PCI_RF_DENSE);
if (!sc->mem) {
device_printf(dev, "Unable to allocate I/O space resource.\n");
error = ENXIO;
More information about the freebsd-alpha
mailing list