Re: HEADS UP: PCI Chnages

From: John Baldwin (jhb_at_FreeBSD.org)
Date: 04/23/04

  • Next message: John Baldwin: "Re: HEADS UP: PCI Chnages" 
    To: freebsd-current@freebsd.org
Date: Fri, 23 Apr 2004 11:18:11 -0400

    On Thursday 22 April 2004 12:34 pm, Kevin Oberman wrote:
    > Well, things seem to have deteriorated slightly with Warner's recent PCI
    > changes (backing out much of the PCI power stuff).
    >
    > 1. I have both my hard disks and floppies. Thanks Warner and Søren!
    >
    > 2. USB still works and recovers after a resume!
    >
    > 3. Sound is again playing too fast after resume. ICH audio is reverting
    > to its native speed. With the PCI power stuff in there, it worked just
    > fine. (It was nice while it lasted.) I suspect this will return when
    > Warner gets a few rough edges off of the PCI code.
    >
    > 4. After a resume, the shared PCI interrupt stops being delivered 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 any 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 just fine. X
    > is alive and the box seems completely normal. (Of course, USB, the
    > network cards, and sound are completely gone.) System has neither 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 the 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. 

    -- 
John Baldwin <jhb@FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve"  =  http://www.FreeBSD.org
_______________________________________________
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"
  • Next message: John Baldwin: "Re: HEADS UP: PCI Chnages"

    Relevant Pages

    • Re: HEADS UP: PCI Chnages
      ... things seem to have deteriorated slightly with Warner's recent PCI ... the shared PCI interrupt stops being delivered after ... > likely to die after about an hour. ... Should I put WITNESS back in my kernel? ...
      (freebsd-current)
    • Re: some 5.1 audio card for mac g5
      ... I got logitech X-530 5.1 speakers and I intend to use them in "full power";-)). ... If you go PCI you will be sad, ... Get any decent Firewire or USB device that provides the output device. ... Being a patriot is not to die for your country, but to make other one die for his ...
      (comp.sys.mac.hardware.misc)
    • Re: 2.6.25 crash: EIP: [] xfrm_output_resume+0x64/0x100 ss:esp 0068:c03a1e5c
      ... Allocating PCI resources starting at 10000000 ... 158944k/163840k available (2005k kernel code, 4464k reserved, ... Found PM-Timer Bug on the chipset. ... XFS mounting filesystem hda1 ...
      (Linux-Kernel)
    • Problem with IRQ routing in 2.6 kernel on HP LH3 server
      ... Kernel 2.4.X works fine on the system but any mandrake 2.6 or compiled ... I narrow the problem to IRQ ... CPU: L2 cache: 512K ... PCI: PCI BIOS revision 2.10 entry at 0xfdaa7, ...
      (Linux-Kernel)
    • FW: Problem with IRQ routing in 2.6 kernel on HP LH3 server
      ... Kernel 2.4.X works fine on the system but any mandrake 2.6 or compiled ... I narrow the problem to IRQ ... CPU: L2 cache: 512K ... PCI: PCI BIOS revision 2.10 entry at 0xfdaa7, ...
      (Linux-Kernel)