John Baldwin wrote:
quoted text
> On Sunday 07 October 2007 07:06:21 pm Michael Butler wrote:
>> For whatever reason I seem to be able to reliably reproduce a panic on
>> -current by running gkrellmd on one of my machines yet another (this
>> one) has no problems at all :-(

[ .. snip .. ]

Sorry - have been traveling this week. The patch you offered solves the
problem. Thanks!

	Michael

quoted text
> Can you make sure you have DDB in your kernel and get the full console 
> messages when it panics?  It will include the stack trace for the offending 
> thread.  But actually, try this patch:
> 
> Index: intpm.c
> ===================================================================
> RCS file: /usr/cvs/src/sys/pci/intpm.c,v
> retrieving revision 1.39
> diff -u -r1.39 intpm.c
> --- intpm.c     19 Apr 2007 17:14:06 -0000      1.39
> +++ intpm.c     11 Oct 2007 20:25:52 -0000
> @@ -436,7 +436,7 @@
>                 /* So that it can use device during device probe on SMBus. */
>                 return (intsmb_stop_poll(sc));
> 
> -       error = tsleep(sc, PWAIT | PCATCH, "SMBWAI", hz / 8);
> +       error = msleep(sc, &sc->lock, PWAIT | PCATCH, "SMBWAI", hz / 8);
>         if (error == 0) {
>                 status = bus_read_1(sc->io_res, PIIX4_SMBHSTSTS);
>                 if (!(status & PIIX4_SMBHSTSTAT_BUSY)) {
> 
> 

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