LKML Archive on
help / color / mirror / Atom feed
From: Auke Kok <>
To: "Eric W. Biederman" <>
Cc: Auke Kok <>,
	linux-pci maillist <>,
	Linux Kernel Mailing List <>,
	Andrew Morton <>, Linus Torvalds <>,
	Jesse Brandeburg <>
Subject: Re: Possible regression: MSI vector leakage since 2.6.18-rc5ish (Unable to repeatedly allocate/free MSI interrupt)
Date: Sat, 27 Jan 2007 11:39:32 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Eric W. Biederman wrote:
> Auke Kok <> writes:
>> I highly doubt it - I've seen the problem even on this weeks git on
>> x86_64. Moreover, I'm at home for the weekend and testing resources are limited
>> :). I'll see what I can do
> Thanks.  There may be more to it than what I suspect, but I could not
> reproduce it on x86_64.
> Now I may have missed something as I optimized my tested based on the fact
> that close and open are triggered when you up and down a network interface.
> so I didn't do a complete rmmod, (since my network driver wasn't modular).
> Since you have seen this on x86_64 I will look deeper.  

gah, strike that.

my only x86_64 system here survived the test with latest git tree.

my 386 system here has no msi devices and I can't reinstall my x86_64 system 
since it's headless, so I can't test anything until monday. I'll give it a full 
test again and see which 2.6.20rc kernels did fail, most likely a much older 
tree (I suspect).


  reply	other threads:[~2007-01-27 19:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-26 22:38 Auke Kok
2007-01-26 22:50 ` Auke Kok
2007-01-27  9:28 ` Eric W. Biederman
2007-01-27 19:07   ` Auke Kok
2007-01-27 19:28     ` Eric W. Biederman
2007-01-27 19:39       ` Auke Kok [this message]
2007-01-29 19:00   ` Auke Kok
2007-01-29 19:36     ` Linus Torvalds
2007-01-29 19:42       ` Eric W. Biederman
2007-01-29 20:19       ` [PATCH] i386: In assign_irq_vector look at all vectors before giving up Eric W. Biederman

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 \ \ \ \ \ \ \ \ \
    --subject='Re: Possible regression: MSI vector leakage since 2.6.18-rc5ish (Unable to repeatedly allocate/free MSI interrupt)' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).