archive mirror
 help / color / mirror / Atom feed
From: "Müller Keve" <>
To: "'Edward Donovan'" <>,
	"'Jeroen Van den Keybus'" <>
Cc: "'Linus Torvalds'" <>,
	"'Chris Palmer'" <>,
	"'Robert Hancock'" <>,
	"'Andrew Morton'" <>,
	"'Len Brown'" <>, <>,
	<>, <>,
	<>, <>,
	"'Thomas Gleixner'" <>,
	"'Ingo Molnar'" <>
Subject: RE: ASM1083 PCIx-PCI bridge interrupts - widespread problems
Date: Fri, 3 Feb 2012 09:51:49 +0100	[thread overview]
Message-ID: <005701cce251$13ffa090$3bfee1b0$> (raw)
In-Reply-To: <20120203015925.GA14359@Brahman>


Below  is a comment of AsMedia. I will continue now with ASUS, but they are
known to just say "the system is not supporting Linux".

As evidence is growing that the chip might have a severe timing issue, I
believe that all related kernel bug reports should be rooted under 1 major
bug only naming the chipset. Can somebody please advise on how I could
perform this re-routing and whether that makes sense. I would simply take
all PCI related kernel bug reports with a system having a ASM1083 and make
them dependent on a newly created (empty) report.

IMO the bridge should finally get a human readable tag by the kernel (so far
it is numeric only: 1b21:1080) possibly including a note in the tag saying
"buggy". This should raise attention at others running into problems and
channel them to the appropriate place.

Having the hardware and plenty of different PCI cards I am open to test any
suggestion you have and gather data/evidence that sheds light on how to best
treat the issue in the kernel. 

Thank you for your continuing support!

Best regards,


Here is the mail from AsMedia (an ASUS dependency...) .

Dear Keve,
Thanks for your valuable opinion. We are glad to receive the opinion form
the end-user. However, we are sorry to inform you that Asmedia is an IC
design house and so far we only provide direct support to the manufacturer,
OEM/ODM, and brand companies. Because most of software is customerized and
our IC is one of the parts in the system and we even don’t know if that
system supports Linux….Actually we are not authorized to release those
software by ourselves. We are afraid that we are not able to provide the
appropriate solution to you, so we suggest that you contact the service
department of that product and they might provide the appropriate support to
you. We also thank you for purchasing the product on which our IC is used. 

Best Regards,
Asmedia Service

-----Original Message-----
From: Edward Donovan [] On Behalf Of Edward Donovan
Sent: Friday, February 03, 2012 2:59 AM
To: Jeroen Van den Keybus
Cc: Linus Torvalds; Chris Palmer; Robert Hancock; Andrew Morton; Len Brown;;;;;;; Thomas
Gleixner; Ingo Molnar
Subject: Re: ASM1083 PCIx-PCI bridge interrupts - widespread problems

Clemens and Jeroen - um, wow, that is a lot of strong thinking.  I don't
have any code in mind, to match, yet.  Especially given your set of
questions, Jeroen.  I'll try to get time to think and read the code.
Hopefully the group will be ahead of my pace. :)

(I have a more minor patch for spurious.c, that I need to resubmit, too, and
I should probably get that over with, first.  So if you see me post about
"better error messages for spurious IRQs", it won't be directly related to



      reply	other threads:[~2012-02-03  9:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
     [not found] ` <>
2012-01-30 15:04   ` ASM1083 PCIx-PCI bridge interrupts - widespread problems Chris Palmer
2012-01-31  2:12     ` Robert Hancock
2012-01-31 12:08       ` Chris Palmer
2012-02-02 19:20         ` Edward Donovan
2012-02-02 19:28           ` Linus Torvalds
2012-02-02 20:22             ` Edward Donovan
2012-02-02 21:39               ` Clemens Ladisch
2012-02-02 22:41               ` Jeroen Van den Keybus
2012-02-03  1:59                 ` Edward Donovan
2012-02-03  8:51                   ` Müller Keve [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='005701cce251$13ffa090$3bfee1b0$' \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).