[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#225526: , PCI domains.



severity 225526 important
tag 225526 + moreinfo
thanks

On Thu, Jan 01, 2004 at 04:02:19PM -0800, Mike Mestnik wrote:
> Well it dosen't matter, I discussed this on the xfree86 mailing list
> this is what they had to say.

What doesn't matter?

> http://marc.theaimsgroup.com/?l=xfree86&w=2&r=1&s=pci+domains&q=b
> 
> It dose seam to be a long standing bug in Xfree86 and now the DBTS is
> more complete.  For normalization's sake I don't see any reason to
> have copies of other bugs here, just links too other sources of
> information.

The Debian Bug Tracking System is not a normalized database, especially
with respect to the contents of a user's complaint.

Your bug report needs to contain enough information for the package
maintainer to meaningfully act on it.  That doesn't mean giving the
package maintainer orders and declaring things broken; it means giving
the him or her enough information that he or she can independently reach
a solution.

> BOTTOM LINE, debian can not release xfree86 for sparc64 with this bug.

That doesn't make the bug "grave", that makes it "important".  We do not
hold up an entire release because of hardware-specific bugs.

> An easy way to fix this problem is to build all the kernels with
> pci_domains not set.

That is not my decision to make.  I do not maintain any Debian packages
of the Linux kernel.  You are going to have to direct this suggestion
elsewhere, as I have already told you.  It is not germane to any bug
report against the Debian packages of XFree86.

> This will require a little bit of kernel
> patching as well as making the correct config changes.  It's not the
> best policy for packages to force the kernel to be configured or built
> in a certain way.

As noted above, this is irrelevant to a report against the Debian
packages of XFree86.  "For normalization's sake", if nothing else, you
should not be repeating it.

> I attached my config and logs when I first opened this bug, I will not
> continue to do so.  Please see
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=225526 for this
> information.

My apologies; I overlooked that.

> pciprobe, I apologize for being so vague and inaccurate.  I was just
> trying to refer to the xfree86 code responsible for finding pci
> devices.

This is not a big deal; your failure to reply to Message-ID:
<[🔎] 20040101090426.GI1765@deadbeast.net> is more important, and why this
bug should continue to have the "moreinfo" tag, which you removed.

Please do not interfere with my use of the "moreinfo" tag.  The
"moreinfo" tag is defined as follows in the Debian BTS documentation:

moreinfo
    This bug can't be addressed until more information is provided by
    the submitter. The bug will be closed if the submitter doesn't
    provide more information in a reasonable (few months) timeframe.
    This is for bugs like "It doesn't work". What doesn't work?

This is not a determination for the submitter to make.  It is the
province of a package maintainer or developer working on the bug to set
or clear this flag.  Please do not fool with it any more.

> I have posted a bug against 2.6-test11, giving a pointer to this bug.
> The kernel is actually correct, but for now it is to be reconfigured
> to get around this bug.

I'll have to take your word for it.  As I said before, I do not maintain
any Debian packages of the Linux kernel.

> Divid S. Miller has told me that his work is incomplete.  This may
> mean however that it may be continued by any one with the skill and
> time.  Therefor his CVS commit may be a good place to start.

This bug is not going to be resolvable until someone has done that work.
And that work cannot commence until more information about the problem
is known.  (I could probably write a patch myself if I were given enough
information.)  This is another reason the package should retain the
"moreinfo" tag.

Please do not manipulate this bug any further.  I request that you reply
to the particulars to Message-ID: <[🔎] 20040101090426.GI1765@deadbeast.net>.
If you are able to supply the requisite information for writing a patch
to complete Mr. Miller's work, that would be good as well.

-- 
G. Branden Robinson                |     I suspect Linus wrote that in a
Debian GNU/Linux                   |     complicated way only to be able to
branden@debian.org                 |     have that comment in there.
http://people.debian.org/~branden/ |     -- Lars Wirzenius

Attachment: signature.asc
Description: Digital signature


Reply to: