https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235944
--- Comment #14 from Andriy Gapon ---
(In reply to Ravi Pokala from comment #13)
Oh, I recall this now. Thank you for refreshing my memory. And I could have
checked the code more thoroughly myself. So, sorry for the noise.
In one part-s
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235944
--- Comment #15 from Andriy Gapon ---
Ravi,
also, I think that it is wrong to fail the attach on a failure to access TSOD.
Many DDR3 DIMMs simply do not have it (not sure about DDR4).
I think that all "server" RDIMMS/LRDIMMs and consumer EC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=158387
Sergey Kandaurov changed:
What|Removed |Added
Resolution|--- |FIXED
Status|Open
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236021
Bug ID: 236021
Summary: UFS w/ SU] [hang] Hang seen when using a FS with the
block size of 65536
Product: Base System
Version: CURRENT
Hardware: Any
O
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236021
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|f...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234094
--- Comment #2 from o...@oz42.eu ---
This bus still exists in 12.0-RELEASE-p3
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
h
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235944
--- Comment #16 from Ravi Pokala ---
(In reply to Andriy Gapon from comment #14)
> In one part-specific datasheet I noticed this curious bit:
> https://www.onsemi.com/pub/Collateral/N34C04-D.PDF
>> 17. The N34C04MU3ETG will respond with No
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235944
--- Comment #17 from Ravi Pokala ---
(In reply to Andriy Gapon from comment #15)
> also, I think that it is wrong to fail the attach on a failure to access TSOD.
> Many DDR3 DIMMs simply do not have it (not sure about DDR4).
> I think that
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235944
--- Comment #18 from Ravi Pokala ---
(In reply to Ravi Pokala from comment #16)
> That could very well be the Greg is seeing.
That could very well be the *problem* Greg is seeing.
--
You are receiving this mail because:
You are the assig
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235944
--- Comment #19 from Andriy Gapon ---
(In reply to Ravi Pokala from comment #17)
In my svn checkout the first ellipses expand to:
if (rc != 0) {
device_printf(dev, "failed to read TSOD-present byte: %d\n",
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224270
Ed Maste changed:
What|Removed |Added
Status|Open|In Progress
--
You are receiving this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236030
Bug ID: 236030
Summary: [patch] ipfw(8) man page: fix typos & caps
Product: Documentation
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235944
--- Comment #20 from Ravi Pokala ---
The TSOD-present byte is just another byte in the SPD; it should be readable if
the SPD in general is readable. If that specific byte is not readable, that
suggests a real problem reading the SPD.
--
Y
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235798
David Bright changed:
What|Removed |Added
Assignee|b...@freebsd.org|d...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235944
--- Comment #21 from Andriy Gapon ---
Sorry, I've been inattentive again.
What if that bit lies, e.g., because of a vendor's mistake...
Then, we would fail here:
if (byte & 0x80) {
tsod_present = true;
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236035
Bug ID: 236035
Summary: ptrace: SIGTRAP and EXIT race
Product: Base System
Version: 12.0-RELEASE
Hardware: amd64
OS: Any
Status: New
Severity: Affec
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236030
Mark Linimon changed:
What|Removed |Added
Keywords||patch
--
You are receiving this ma
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235944
--- Comment #22 from Greg V ---
(In reply to Andriy Gapon from comment #14)
> what specific EEPROM part the DIMM in question uses
I don't really want to take the heatsink off, but the high resolution photos
helpfully provided by KFA2 on t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235944
--- Comment #23 from Greg V ---
Ignoring the page errors makes it read the second page successfully (contents
match the ones seen in Windows)!
And yeah, the TSOD presence bit seems to lie on these DIMMs…
So pretty much the only thing I ca
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235944
--- Comment #24 from Ravi Pokala ---
Awesome! Can you attach a patch with your changes?
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mai
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235944
--- Comment #25 from Greg V ---
Created attachment 202365
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=202365&action=edit
dimm-hack.patch
(In reply to Ravi Pokala from comment #24)
It's not a good patch, but this is what I did
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235944
--- Comment #26 from Ravi Pokala ---
Thanks Greg! I'll massage it as needed and commit it for you sometime in the
next few days.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235944
--- Comment #27 from Andriy Gapon ---
(In reply to Greg V from comment #23)
I once got some Kingston modules, they all had the same serial number.
Turned out to be counterfeit. Hope that that is not the case with the memory
you got.
Also,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236042
Bug ID: 236042
Summary: Windows Server 2016 Hyper-V snapshot triggers SCSI
errors
Product: Base System
Version: 12.0-RELEASE
Hardware: amd64
OS: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236042
--- Comment #1 from Alex G ---
I tried to email the authors of the hyerv integration drivers but I got a
bounce back from Microsoft email server.
The response from the remote server was:
550 5.4.1 [bs...@microsoft.com]: Recipient address r
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236043
Bug ID: 236043
Summary: bectl can't destroy origin snapshot
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
Severity: Affect
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236006
Rob changed:
What|Removed |Added
CC||rob.fx...@gmail.com
--- Comment #1 from Rob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236043
Rob changed:
What|Removed |Added
Summary|bectl can't destroy origin |[patch] bectl can't destroy
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236043
Mark Linimon changed:
What|Removed |Added
Keywords||patch
Summary|[patch] be
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236042
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|virtualizat...@freebsd.org
--
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236043
Rob changed:
What|Removed |Added
Summary|bectl can't destroy origin |[patch] bectl can't destroy
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205036
joke...@mail-share.com changed:
What|Removed |Added
CC||joke...@mail-share.com
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236006
--- Comment #2 from Sergey ---
(In reply to Rob from comment #1)
Thanx Rob, then I'm closing this ticket.
BR,
Sergey.
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236006
Sergey changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236043
Sergey changed:
What|Removed |Added
CC||kp...@protonmail.com
--- Comment #1 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236014
nis...@snickers.org changed:
What|Removed |Added
Severity|Affects Only Me |Affects Many People
--
You a
36 matches
Mail list logo
