reopen 506419
found 506419 linux-2.6/2.6.26-10
found 506419 linux-2.6/2.6.26-11
found 506419 linux-2.6/2.6.27
tags 506419 + upstream
owner 506419 !
quit

Ben Hutchings wrote:

> I'm closing this because I think a year is more than enough time to test
> a new version.

I'll take ownership then. I used to have a forcedeth and while I
don't anymore, I'm interested in the driver being reliable.

Martin, ping? Of course if you've lost interest (e.g., if you've lost
the hardware) then closing the bug again is probably the right thing
to do.

Thanks, both.
Jonathan



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110324062817.GA27426@elie">http://lists.debian.org/20110324062817.GA27426@elie

also sprach Jonathan Nieder <jrnieder@gmail.com> [2011.03.24.0728 +0100]:
> > I'm closing this because I think a year is more than enough time to test
> > a new version.
>
> I'll take ownership then. I used to have a forcedeth and while I
> don't anymore, I'm interested in the driver being reliable.
>
> Martin, ping? Of course if you've lost interest (e.g., if you've lost
> the hardware) then closing the bug again is probably the right thing
> to do.

I still have the hardware, but it's on a production machine. It is
onboard and I added a separate NIC, so it's unused, but I cannot
really run kernel-level experiments.

However, the machine has KVM, and as soon as KVM supports PCI
passthrough, that might be useful. There are two cards connected to
each other (I expected debugging), and with two KVM instances, this
could be interesting.

--
.'`. martin f. krafft <madduck@d.o> Related projects:
: :' : proud Debian developer http://debiansystem.info
`. `'` http://people.debian.org/~madduck http://vcs-pkg.org
`- Debian - when you have better things to do than fixing systems

"never try to explain computers to a layman.
it's easier to explain sex to a virgin."
-- robert heinlein

(note, however, that virgins tend to know a lot about computers.)

martin f krafft wrote:

> I still have the hardware, but it's on a production machine. It is
> onboard and I added a separate NIC, so it's unused, but I cannot
> really run kernel-level experiments.
>
> However, the machine has KVM, and as soon as KVM supports PCI
> passthrough, that might be useful. There are two cards connected to
> each other (I expected debugging), and with two KVM instances, this
> could be interesting.

Thanks for the update; I'm happy to wait. I'm leaving the bug tagged
moreinfo for now, as in "wouldn't it be nice if someone with similar
hardware could try to reproduce this".

Regards,
Jonathan



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110324065903.GA27507@elie">http://lists.debian.org/20110324065903.GA27507@elie

On Thu, 2011-03-24 at 01:28 -0500, Jonathan Nieder wrote:
> reopen 506419
> found 506419 linux-2.6/2.6.26-10
> found 506419 linux-2.6/2.6.26-11
> found 506419 linux-2.6/2.6.27
> tags 506419 + upstream
> owner 506419 !
> quit
>
> Ben Hutchings wrote:
>
> > I'm closing this because I think a year is more than enough time to test
> > a new version.
>
> I'll take ownership then. I used to have a forcedeth and while I
> don't anymore, I'm interested in the driver being reliable.
[...]

If you can't test it, what good does it to reopen the bug?

Ben.

--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

Ben Hutchings wrote:

> If you can't test it, what good does it to reopen the bug?

It is a real bug and I have no reason to believe it was fixed.
Meanwhile the submitter has said that as soon as circumstances allow,
he'll test it. Is the bug doing harm by sitting open? Perhaps
someone should lower the severity to wishlist to keep it off your
radar? I just want the bug to be fixed and believe the bug tracking
system is a useful way to track work towards bringing that about.

Jonathan



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110324211841.GA3151@elie">http://lists.debian.org/20110324211841.GA3151@elie

On Thu, Mar 24, 2011 at 04:18:41PM -0500, Jonathan Nieder wrote:
> Ben Hutchings wrote:
>
> > If you can't test it, what good does it to reopen the bug?
>
> It is a real bug and I have no reason to believe it was fixed.

It *was* a real bug and you have no reason to believe it is not fixed.

> Meanwhile the submitter has said that as soon as circumstances allow,
> he'll test it. Is the bug doing harm by sitting open?

New submitters are expected to look through existing bug reports. The
BTS can take over a minute to generate a summary of all reports in
linux-2.6. Yes, stale bug reports do harm.

> Perhaps
> someone should lower the severity to wishlist to keep it off your
> radar?

If it is a real, live bug then it is important. If not, it should be
closed. Changing the severity is just silly.

Ben.

> I just want the bug to be fixed and believe the bug tracking
> system is a useful way to track work towards bringing that about.

--
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
- Albert Camus



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110324224510.GO2356@decadent.org.uk">http://lists.debian.org/20110324224510.GO2356@decadent.org.uk

Ben Hutchings wrote:

> It *was* a real bug and you have no reason to believe it is not fixed.

Sure, it is possible that 6c2da9c or eb10a781 fixes this. But I
really do suspect that it's not fixed. I'd take at least 1:1 odds.

> New submitters are expected to look through existing bug reports. The
> BTS can take over a minute to generate a summary of all reports in
> linux-2.6.

Yes, that is a problem. Maybe linux-2.6 bugs could be split using
usertags (for networking, dri, etc) to lessen it? Or maybe it's
possible to serve snapshots of the bug list as static HTML somewhere,
or to add some caching to debbugs to alleviate the underlying problem?

> If it is a real, live bug then it is important. If not, it should be
> closed. Changing the severity is just silly.

Ok, that makes sense to me. Unfortunately, hardware-dependent bugs
are hard to debug. I trust this particular bug submitter a great
deal, which is part of why I don't consider it a lost cause.

Anyway, you've done enough work on linux-2.6 that you should feel free
to do whatever you want. Hopefully the above explanations make my
actions clearer, but if you want to close the bug again, I won't stop
you.

Regards,
Jonathan



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110324230634.GD3151@elie">http://lists.debian.org/20110324230634.GD3151@elie