Re: More info on port 80 symptoms on MCP51 machine.

On Wed, 12 Dec 2007 21:58:25 +0100
Rene Herman <[email protected]> wrote:

> On 12-12-07 21:26, Rene Herman wrote:
> 
> > On 12-12-07 21:07, David P. Reed wrote:
> 
> >> Someone might have an in to nVidia to clarify this, since I don't.  In 
> >> any case, the udelay(2) approach seems to be a safe fix for this machine.
> 
> By the way, _does_ anyone have a contact at nVidia who could clarify? Alan 
> maybe? I'm quite curious what they did...

I don't. Nvidia are not the most open bunch of people on the planet. This
doesn't appear to be a chipset bug anyway but a firmware one (other
systems with the same chipset work just fine).

The laptop maker might therefore be a better starting point.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: More info on port 80 symptoms on MCP51 machine.
    • From: "H. Peter Anvin" <[email protected]>

• References:
  • Re: RFC: outb 0x80 in inb_p, outb_p harmful on some modern AMD64 with MCP51 laptops
    • From: "H. Peter Anvin" <[email protected]>
  • Re: RFC: outb 0x80 in inb_p, outb_p harmful on some modern AMD64 with MCP51 laptops
    • From: David Newall <[email protected]>
  • Re: RFC: outb 0x80 in inb_p, outb_p harmful on some modern AMD64 with MCP51 laptops
    • From: Paul Rolland <[email protected]>
  • Re: RFC: outb 0x80 in inb_p, outb_p harmful on some modern AMD64 with MCP51 laptops
    • From: Rene Herman <[email protected]>
  • Re: RFC: outb 0x80 in inb_p, outb_p harmful on some modern AMD64 with MCP51 laptops
    • From: David Newall <[email protected]>
  • Re: RFC: outb 0x80 in inb_p, outb_p harmful on some modern AMD64 with MCP51 laptops
    • From: Rene Herman <[email protected]>
  • Re: RFC: outb 0x80 in inb_p, outb_p harmful on some modern AMD64 with MCP51 laptops
    • From: David Newall <[email protected]>
  • Re: RFC: outb 0x80 in inb_p, outb_p harmful on some modern AMD64 with MCP51 laptops
    • From: "linux-os (Dick Johnson)" <[email protected]>
  • Re: RFC: outb 0x80 in inb_p, outb_p harmful on some modern AMD64 with MCP51 laptops
    • From: Andi Kleen <[email protected]>
  • Re: RFC: outb 0x80 in inb_p, outb_p harmful on some modern AMD64 with MCP51 laptops
    • From: Rene Herman <[email protected]>
  • Re: RFC: outb 0x80 in inb_p, outb_p harmful on some modern AMD64 with MCP51 laptops
    • From: Pavel Machek <[email protected]>
  • Re: RFC: outb 0x80 in inb_p, outb_p harmful on some modern AMD64 with MCP51 laptops
    • From: Rene Herman <[email protected]>
  • More info on port 80 symptoms on MCP51 machine.
    • From: "David P. Reed" <[email protected]>
  • Re: More info on port 80 symptoms on MCP51 machine.
    • From: Rene Herman <[email protected]>
  • Re: More info on port 80 symptoms on MCP51 machine.
    • From: Rene Herman <[email protected]>

• Prev by Date: [RFC] [PATCH -mm] reiser4: replace uid==0 check with capability
• Next by Date: Re: More info on port 80 symptoms on MCP51 machine.
• Previous by thread: Re: More info on port 80 symptoms on MCP51 machine.
• Next by thread: Re: More info on port 80 symptoms on MCP51 machine.
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]