[Bug 243422] NVME controller failure: resetting (AMD Radeon R5 NVMe Series)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243422 Bug ID: 243422 Summary: NVME controller failure: resetting (AMD Radeon R5 NVMe Series) Product: Base System Version: 12.1-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: shamaz.ma...@gmail.com Hello. I use a machine running FreeBSD 12.1-RELEASE and equipped with AMD Radeon R5 NVMe 120Gb drive. When I try to write something on this NVMe drive (I have UFS on it), I constantly get these errors in : nvme0: Resetting controller due to a timeout. nvme0: Resetting controller due to a timeout. nvme0: Resetting controller due to a timeout. nvme0: Resetting controller due to a timeout. nvme0: Resetting controller due to a timeout. nvme0: Resetting controller due to a timeout. nvme0: resetting controller nvme0: aborting outstanding i/o nvme0: aborting outstanding i/o nvme0: aborting outstanding i/o nvme0: aborting outstanding i/o nvme0: aborting outstanding i/o nvme0: aborting outstanding i/o nvme0: aborting outstanding i/o This is a message on drive attach: nvme0: mem 0xfe90-0xfe903fff irq 24 at device 0.0 on pci1 The write speed decreases greatly and sometimes written files are corrupt. While reading, on the contrary, all works just fine and read speed is really impressive. There are many bugs reported considering NVMe. Here is what I found and how this differs from my situation: bug #211713 — probably the first bug reported. It is about suspend/resume and I do not use suspend/resume on my PC. bug #232466 — again, this is about suspend/resume bug #243148 — I am not sure, maybe this is the same problem as mine. bug #243063 — This guy has a similar problem in bhyve guest. I've decided to report another bug because this is maybe manufacturer specific bug (some of the bugs I posted above are closed and people have their NVMe drives working). So, I am sorry if it's a duplicate. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 243422] NVME controller failure: resetting (AMD Radeon R5 NVMe Series)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243422 --- Comment #1 from shamaz.ma...@gmail.com --- Also, in the end of discussion of bug #243422, someone said that switching TRIM off helps. I've tried tunefs -t disable, but the problem is still there -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 204521] [new driver] [request] Port rtsx from OpenBSD to FreeBSD
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204521 --- Comment #37 from Gary Jennejohn --- (In reply to hlh from comment #31) You should add sc->rtsx_intr_status = 0; prior to the call to rtsx_wait_intr() in rtsx_xfer()to be consistent. This is the only place where that was not being done. It doesn't change the behavior, but it can prevent false positives in rtsx_wait_intr(). -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 224415] 460.status-mail-rejects and 520.pfdenied appear broken
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224415 --- Comment #13 from Kristof Provost --- (In reply to per from comment #11) Good question without a good answer. Certainly create a bug, with as much relevant information as you can. You may also want to post it to the relevant mailing list. Figuring out who's been touching the affected (or related) code and sending them a ping (one ping only) is fine too. Anything you can do to make it easier to fix the bug (simple reproduction instructions are awesome!) will help too. There are no surefire ways. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 204521] [new driver] [request] Port rtsx from OpenBSD to FreeBSD
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204521 --- Comment #38 from h...@restart.be --- (In reply to Gary Jennejohn from comment #37) Update done. Thanks -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 233431] [bsnmpd] regression on 12-STABLE: crash on start
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233431 --- Comment #3 from commit-h...@freebsd.org --- A commit references this bug: Author: syrinx Date: Sat Jan 18 10:55:38 UTC 2020 New revision: 356865 URL: https://svnweb.freebsd.org/changeset/base/356865 Log: MFC r349265: No need for each bsnmpd(1) module to open connection to syslog bsnmpd(1) main does that early on init and the connection is available to all loaded modules PR: 233431 , 221487 Event:Vienna Hackathon 2019 Changes: _U stable/12/ stable/12/usr.sbin/bsnmpd/modules/snmp_lm75/snmp_lm75.c -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 221487] [bsnmpd] crashes on startup with the enabled module begemotSnmpdModulePath."pf"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221487 --- Comment #6 from commit-h...@freebsd.org --- A commit references this bug: Author: syrinx Date: Sat Jan 18 10:55:38 UTC 2020 New revision: 356865 URL: https://svnweb.freebsd.org/changeset/base/356865 Log: MFC r349265: No need for each bsnmpd(1) module to open connection to syslog bsnmpd(1) main does that early on init and the connection is available to all loaded modules PR: 233431 , 221487 Event:Vienna Hackathon 2019 Changes: _U stable/12/ stable/12/usr.sbin/bsnmpd/modules/snmp_lm75/snmp_lm75.c -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 224415] 460.status-mail-rejects and 520.pfdenied appear broken
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224415 --- Comment #14 from p...@hedeland.org --- (In reply to Kristof Provost from comment #13) OK - thanks again! -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 233400] 12.0-RC1 - FreeBSD 12.x Breaks WINE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233400 --- Comment #26 from verma...@interia.pl --- I finally nailed the source of this problem ... Below line in /boot/loader.conf file: hw.snd.latency=7 Without this line sound in Firefox and WINE works well. The W520 initially worked because I did not yet added my full /boot/loader.conf configuration ... and this option (hw.snd.latency=7) is suggested by almost ALL guides regarding tuning FreeBSD for lower power consumption ... Finally solved. What it (hw.snd.latency=7) does break: Firefox sound (audio in movies from youtube.com for example) WINE sound What it (hw.snd.latency=7) does not break: Chromium sound MPV/VLC sound Hope that helps someone. Regards. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 240943] Missing FreeBSD Logo with boot_mute=YES @ /boot/loader.conf
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240943 verma...@interia.pl changed: What|Removed |Added Status|New |Closed Resolution|--- |FIXED --- Comment #2 from verma...@interia.pl --- Fixed in 12.1-RELEASE. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 240942] FreeBSD loader - failed to read pad2 area or primary vdev
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240942
--- Comment #2 from verma...@interia.pl ---
Its here:
/usr/src/stand/i386/zfsboot/zfsboot.c- *cmd = 0;
/usr/src/stand/i386/zfsboot/zfsboot.c- }
/usr/src/stand/i386/zfsboot/zfsboot.c-} else
/usr/src/stand/i386/zfsboot/zfsboot.c: printf("failed to read pad2 area of
primary vdev\n");
/usr/src/stand/i386/zfsboot/zfsboot.c-
/usr/src/stand/i386/zfsboot/zfsboot.c-/* Mount ZFS only if it's not already
mounted via nextboot parsing. */
/usr/src/stand/i386/zfsboot/zfsboot.c-if (zfsmount.spa == NULL &&
Can we remove that harmless/pointless message?
Its displayed everytime system boots yet it does not provide anything - system
boots properly.
Regards.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
