Closed Bug 633892 Opened 9 years ago Closed 9 years ago

Blacklist NVIDIA NVS 3100M on driver 8.17.12.5896

Categories

(Core :: Graphics, defect)

x86
Windows 7
defect
Not set

Tracking

()

RESOLVED FIXED
Tracking Status
blocking2.0 --- final+

People

(Reporter: pavlov, Assigned: joe)

References

Details

(Whiteboard: [softblocker])

I've been getting 2-3 driver resets per day with this driver.  Win7-64
blocking2.0: --- → ?
8.17.12.5896 = 258.96, this should already be blacklisted I thought?

Hmm, just checked, apparently 257.21 is the cutoff.  Ugh.
Can we use this to test the over-network blacklist stuff?
We should test our remote blacklisting capability with this!
Assignee: nobody → joe
blocking2.0: ? → -
Why was this minused? We'd want to prevent these crashes *before* we ship, wouldn't we?
We do want to, but with a weapon to my cranium I would ship without it -> softblocker.
blocking2.0: - → final+
Whiteboard: [softblocker]
(In reply to comment #4)
> Why was this minused? We'd want to prevent these crashes *before* we ship,
> wouldn't we?

I'm not sure, but I believe we can blacklist this remotely, at any time.

One thing is we don't need to hold a code freeze or anything like that over this if our remote blacklisting works.
except we would block the release if the remote blacklisting doesn't work, right? :-)
(In reply to comment #4)
> Why was this minused? We'd want to prevent these crashes *before* we ship,
> wouldn't we?

Fixing these specific driver resets, in my mind, in no way blocks the release, but I've got nothing against it being a softblocker. The downloaded blacklist is of course separate, and testing it is something that we should (are going to!) do.
This is a really terrible experience and we need to have your computer not go black randomly for sometimes 30 seconds while it resets the driver.
Depends on: 635044
Woo!
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Fixed again by bug 635044.
Status: REOPENED → RESOLVED
Closed: 9 years ago9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.