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

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. Inany 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? Alanmaybe? I'm quite curious what they did...


Summary:

Unless after booting with "acpi=off", outputs to port 0x80 (the legacy wayto delay I/O) reliably, but not immediately, hang MCP51 machines. Outputs toport 0xed do not indicating it's a not a generic bus abort problem.


Rene.
--
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]>
- Re: More info on port 80 symptoms on MCP51 machine.
  - From: Alan Cox <[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]>

Prev by Date: Re: [PATCH 05/30] blk_end_request: changing um (take 4)
Next by Date: [RFC] [PATCH -mm] reiser4: replace uid==0 check with capability
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]