Date: Fri, 23 Apr 2004 15:03:49 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: nate@root.org Cc: jhb@FreeBSD.org Subject: Re: HEADS UP: PCI Chnages Message-ID: <20040423.150349.48498929.imp@bsdimp.com> In-Reply-To: <20040423140023.S53535@root.org> References: <200404231118.11833.jhb@FreeBSD.org> <20040423.144322.115909342.imp@bsdimp.com> <20040423140023.S53535@root.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20040423140023.S53535@root.org>
Nate Lawson <nate@root.org> writes:
: On Fri, 23 Apr 2004, M. Warner Losh wrote:
: > In message: <200404231118.11833.jhb@FreeBSD.org>
: > John Baldwin <jhb@FreeBSD.org> writes:
: > : On Thursday 22 April 2004 12:34 pm, Kevin Oberman wrote:
: > : > Well, things seem to have deteriorated slightly with Warner's r=
ecent PCI
: > : > changes (backing out much of the PCI power stuff).
: > : >
: > : > 1. I have both my hard disks and floppies. Thanks Warner and S=F8=
ren!
: > : >
: > : > 2. USB still works and recovers after a resume!
: > : >
: > : > 3. Sound is again playing too fast after resume. ICH audio is r=
everting
: > : > to its native speed. With the PCI power stuff in there, it w=
orked just
: > : > fine. (It was nice while it lasted.) I suspect this will ret=
urn when
: > : > Warner gets a few rough edges off of the PCI code.
: > : >
: > : > 4. After a resume, the shared PCI interrupt stops being deliver=
ed after
: > : > a LONG time interval. I've had it fail in 10 minutes, but it=
is more
: > : > likely to die after about an hour. It always dies in under 2=
hours.
: > : >
: > : > vmstat -i looks completely normal except that the count for irq=
11 never
: > : > increases. All other interrupts and devices are fine. Is this a=
locking
: > : > problem? Should I put WITNESS back in my kernel? I can't find a=
ny sign
: > : > of any significant resource being exhausted. If you ignore the =
fact that
: > : > all devices on irq 11 are dead, the system continues to run jus=
t fine. X
: > : > is alive and the box seems completely normal. (Of course, USB, =
the
: > : > network cards, and sound are completely gone.) System has neit=
her SMP
: > : > or APIC in the kernel.
: > : >
: > : > I'd love to track this down. I have no idea how common it is,
: > : > either. Since most people running CURRENT are not using suspend=
on their
: > : > laptops because of various problems except to test things, this=
might
: > : > not have shown up for most people. (Or, it might be unique to t=
he IBM
: > : > T30.)
: > : >
: > : > Thanks,
: > :
: > : We probably just need to reprogram the PCI link devices on resume=
. Are you
: > : using ACPI? The non-ACPI case I know doesn't do this yet.
: >
: > We aren't doing that at the moment. I have some changes in my tree=
,
: > but there are issues with ndis not working quite right yet :-(
: =
: I thought that was enabled in the ACPI-PCI bridge driver. At least m=
y
: latest version seems to do it (added by iwasaki@ a while ago). Did y=
ou
: disable that again? Or are your comments just for the !acpi case?
Ah, I was consuing PCI link devices and PCI devices.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040423.150349.48498929.imp>