[Bug 222691] Thinkpad t440p - lid sysctl gets confused
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222691 --- Comment #1 from Thomas Merkel --- I've the same issue, steps to reproduce: 1. LID open 'sysctl -n dev.acpi_lid.0.state = 1' 2. LID closed 'sysctl -n dev.acpi_lid.0.state = 0' 3. Sending device to suspend 4. LID open (device resume from suspend automatically) 'sysctl -n dev.acpi_lid.0.state = 0' Expected: On LID open after resume the value should be 1. -- 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 240530] Patch to allow ng_source to inject into any netgraph network
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240530 Bug ID: 240530 Summary: Patch to allow ng_source to inject into any netgraph network Product: Base System Version: 12.0-STABLE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: l...@donnerhacke.de Created attachment 207415 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=207415&action=edit patch to ng_source in 12-STABLE train ng_source is a module for debugging and performance measurement within netgraph. The current implementation is designed to emit packets to an physical ethernet interface and tries to maximize the hardware throughput. There is already code to limit the packet rate injected (maxpps) further. The whole code is able to inject any netgraph messages into any netgraph network, despite the dependency to a physical interface prohibits this at the moment. This patch allows to use the ng_source module to be used in arbitary netgraph network. In order to limit the rate of packets injected, the maxpps part needs to be enforced if there is no assigned ethernet interface available. I personally use this patch to profile somewhat complex netgraph networks, which terminate in i.e. in eiface nodes. -- 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 240532] pf stops purging IPv6 FIN_WAIT_2 states?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240532 Bug ID: 240532 Summary: pf stops purging IPv6 FIN_WAIT_2 states? Product: Base System Version: 11.2-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: p...@lysator.liu.se Created attachment 207418 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=207418&action=edit pf.conf I just noticed that our production servers seems to be accumulating FIN_WAIT_2 state entries in PF (atleast IPv6 ones). # pfctl -ss | egrep FIN_WAIT_2 | egrep -v 2001 | wc -l 386 # pfctl -ss | egrep FIN_WAIT_2 | egrep 2001 | wc -l 23141 Using workaround from bug 222126 seems to wake up the "pf purge" kernel thread again (atleast for a while): # echo "set timeout interval 5" | pfctl -mf - FreeBSD 11.2-RELEASE-p10 Dell PowerEdge R730xd 256GB RAM (NFS & SMB fileservers) -- 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 240533] pf stops purging IPv6 FIN_WAIT_2 states?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240533 Bug ID: 240533 Summary: pf stops purging IPv6 FIN_WAIT_2 states? Product: Base System Version: 11.2-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: p...@lysator.liu.se I just noticed that our production servers seems to be accumulating FIN_WAIT_2 state entries in PF (atleast IPv6 ones). # pfctl -ss | egrep FIN_WAIT_2 | egrep -v 2001 | wc -l 386 # pfctl -ss | egrep FIN_WAIT_2 | egrep 2001 | wc -l 23141 Using workaround from bug 222126 seems to wake up the "pf purge" kernel thread again (atleast for a while): # echo "set timeout interval 5" | pfctl -mf - FreeBSD 11.2-RELEASE-p10 Dell PowerEdge R730xd 256GB RAM (NFS & SMB fileservers) -- 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 240339] [ig4] I2C2 (touchpad bus) broken on the Google Pixelbook (Sunrise Point PCH)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240339 --- Comment #17 from Vladimir Kondratyev --- (In reply to Greg V from comment #16) > Interesting how the other buses are fine with this, only the touchpad one was > broken. That is related to buses and gates capacitance and resistance. Here you can find what happens if SDA HOLD is set too low: https://www.cypress.com/file/364871/download -- 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 240533] pf stops purging IPv6 FIN_WAIT_2 states?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240533 Peter Eriksson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|New |Closed --- Comment #1 from Peter Eriksson --- *** This bug has been marked as a duplicate of bug 240532 *** -- 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 240532] pf stops purging IPv6 FIN_WAIT_2 states?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240532 --- Comment #1 from Peter Eriksson --- *** Bug 240533 has been marked as a duplicate of this bug. *** -- 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 240339] [ig4] I2C2 (touchpad bus) broken on the Google Pixelbook (Sunrise Point PCH)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240339 --- Comment #18 from commit-h...@freebsd.org --- A commit references this bug: Author: wulf Date: Thu Sep 12 12:33:09 UTC 2019 New revision: 352243 URL: https://svnweb.freebsd.org/changeset/base/352243 Log: ig4(4): Fix SDA HOLD time set too low on Skylake controllers Execution of "Soft reset" command (IG4_REG_RESETS_SKL) at controller init stage sets SDA_HOLD register value to 0x0001 which is often too low for normal operation. Set SDA_HOLD back to 28 after reset to restore controller functionality. PR: 240339 Reported by: imp, GregV, et al. MFC after:3 days Changes: head/sys/dev/ichiic/ig4_iic.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 240539] tuntap: Getting "ifconfig: ioctl SIOCSIFNAME (set name): File exists" from `ifconfig tap create name tap0`
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240539 Bug ID: 240539 Summary: tuntap: Getting "ifconfig: ioctl SIOCSIFNAME (set name): File exists" from `ifconfig tap create name tap0` Product: Base System Version: CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: 0...@freebsd.org Here's a sample shell session: > # ifconfig | grep tap0 > # ifconfig tap create name tap0 > ifconfig: ioctl SIOCSIFNAME (set name): File exists > tap0 > # ifconfig | grep tap0 > tap0: flags=8802 metric 0 mtu 1500 FWIW, I am getting unexpected system hangs requiring hard reset when I'm destroying tap devices. I am running FreeBSD 13.0-CURRENT r351819 GENERIC amd64. -- 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 240539] tuntap: Getting "ifconfig: ioctl SIOCSIFNAME (set name): File exists" from `ifconfig tap create name tap0`
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240539 --- Comment #1 from Yuri Pankov --- It makes some sense, actually. If you don't have any tap devices, `ifconfig tap create name tap0` would first create 'tap0', and then try to rename it to 'tap0' (which, of course, already exists at that time). There could be a check if original and new name are the same, I guess. Also, you could just create it as `ifconfig tap0 create`. -- 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 240539] tuntap: Getting "ifconfig: ioctl SIOCSIFNAME (set name): File exists" from `ifconfig tap create name tap0`
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240539 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|n...@freebsd.org -- 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 240532] pf stops purging IPv6 FIN_WAIT_2 states?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240532 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|p...@freebsd.org -- 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 240530] Patch to allow ng_source to inject into any netgraph network
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240530 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|n...@freebsd.org Keywords||patch -- 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 240506] picobsd build script not producing usable output
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240506 Glen Barber changed: What|Removed |Added CC|r...@freebsd.org |i...@freebsd.org --- Comment #3 from Glen Barber --- This is not re@'s territory. CC'd imp@, who I believe is the picobsd maintainer. -- You are receiving this mail because: You are on the CC list 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 240475] [PATCH]: Add support for CPUID 0x16 in tsc_freq_cpuid() (TSC clock)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240475 Konstantin Belousov changed: What|Removed |Added CC||k...@freebsd.org --- Comment #2 from Konstantin Belousov --- (In reply to Neel Chauhan from comment #1) It is wrong to use cpuid leaf 0x16 for frequency base, this is explicitly stated in Intel SDM. Also, I am even more curious about your machine config. Please post verbose dmesg, as requested. -- 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 189095] big5 manual page is inaccurate.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=189095 Li-Wen Hsu changed: What|Removed |Added Assignee|b...@freebsd.org|lw...@freebsd.org -- 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 240475] [PATCH]: Add support for CPUID 0x16 in tsc_freq_cpuid() (TSC clock)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240475 --- Comment #3 from Neel Chauhan --- This patch is based upon an existing Linux commit: https://github.com/torvalds/linux/commit/604dc9170f2435d27da5039a3efd757dceadc684 In the commit message: Skylake, Kabylake and all variants of those two chipsets report a crystal frequency of zero, however we can calculate the crystal clock speed by condidering data from CPUID.0x16. This method correctly distinguishes between the two crystal clock frequencies present on different Skylake X variants that caused headaches before. As the calculations do not quite match the previously-hardcoded values in some cases (e.g. 23913043Hz instead of 24MHz), TSC refinement is enabled on all platforms where we had to calculate the crystal frequency in this way. This is also true on my system. I will post two verbose dmesgs: one without any patches, and one with this patch (which also has drm-kmod and Vladimir Kondratyev's iichid loaded). -- 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 240475] [PATCH]: Add support for CPUID 0x16 in tsc_freq_cpuid() (TSC clock)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240475 --- Comment #5 from Neel Chauhan --- Created attachment 207427 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=207427&action=edit dmesg log on the Spectre x360 with the Bug 240475 patch (Main System) -- 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 240475] [PATCH]: Add support for CPUID 0x16 in tsc_freq_cpuid() (TSC clock)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240475 --- Comment #4 from Neel Chauhan --- Created attachment 207426 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=207426&action=edit dmesg log on the Spectre x360 without any patches (LiveUSB) -- 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 240543] Realtek ALC265 - Asus Vivobook e203n
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240543 Bug ID: 240543 Summary: Realtek ALC265 - Asus Vivobook e203n Product: Base System Version: 12.0-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: misc Assignee: b...@freebsd.org Reporter: signals...@icloud.com I am having an issue getting my audio device to work. Forum post: https://forums.freebsd.org/threads/asus-e203n-no-audio.72255/ I can't get audio out of speakers or headphones. I think someone may have been having a similar issue here but I am unsure if they are related. https://lists.freebsd.org/pipermail/freebsd-questions/2012-October/246013.html -- 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 240543] Realtek ALC265 - Asus Vivobook e203n
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240543 signalsout changed: What|Removed |Added Keywords||needs-patch URL||https://forums.freebsd.org/ ||threads/asus-e203n-no-audio ||.72255/ CC||signals...@icloud.com -- 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 240475] [PATCH]: Add support for CPUID 0x16 in tsc_freq_cpuid() (TSC clock)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240475 --- Comment #6 from Konstantin Belousov --- Your patch is still not equivalent to what Linux did. Note that they still apply the nom/denom coefficient reported from leaf 0x15, but take adjusted mhz from 0x16, instead of zero hz from 0x15. In other words, they do not hardcode 10. -- 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 240545] patch to remove unneeded M_WAITOK return value checks
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240545 Bug ID: 240545 Summary: patch to remove unneeded M_WAITOK return value checks Product: Base System Version: 12.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: a...@watson.org Created attachment 207432 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=207432&action=edit remove NULL check and handling of it for M_WAITOK cases Attached is a patch that removes the check of malloc(9)'s return value against NULL when M_WAITOK flag is used. This does not cover all cases, but a number of them that I found with an LLVM pass and partial compilation of kernel. That pass also checks mallocarray(), realloc(), and reallocf(), but in the areas analyzed did not see the extra code. I am not sure I like the idea of removing NULL checks, but it is already handled. Are there any cases to be aware of for why the check would be necessary with M_WAITOK? If no, I will try to go through and look for others. The patch is for 12.0-RELEASE, but can adjust that as well. -- 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 240545] patch to remove unneeded M_WAITOK return value checks
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240545 --- Comment #1 from Conrad Meyer --- It is definitely ok for malloc, mallocarray, and realloc. (We have a kernel reallocf? Huh.) Honestly, reallocf with M_WAITOK seems like a mistake — those could instead/additionally be replaced with just realloc(M_WAITOK). > Are there any cases to be aware of for why the check would be necessary with > M_WAITOK? Yes, contigmalloc() can fail with M_WAITOK; some of the busdma allocation stuff can fail with M_WAITOK. Normal malloc / UMA allocations with M_WAITOK can't return NULL (just sleep indefinitely). -- 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 240545] patch to remove unneeded M_WAITOK return value checks
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240545 Conrad Meyer changed: What|Removed |Added CC||c...@freebsd.org --- Comment #2 from Conrad Meyer --- By the way, have you considered writing this as a coccinelle script? It seems like something that could be done with that tool. -- 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 240545] patch to remove unneeded M_WAITOK return value checks
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240545 --- Comment #3 from Andrew Reiter --- (In reply to Conrad Meyer from comment #2) No I have not used that tool before, but it looks handy. Is there any history of it being used in any FreeBSD processes before? Thanks for the pointer! -- 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 240545] patch to remove unneeded M_WAITOK return value checks
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240545 --- Comment #4 from Conrad Meyer --- Yes, I've used it, pfg@ has used it some, and I believe mjg@ has as well (https://reviews.freebsd.org/D21427). -- 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 240475] [PATCH]: Add support for CPUID 0x16 in tsc_freq_cpuid() (TSC clock)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240475 --- Comment #7 from Neel Chauhan --- It's true that Linux does this (lines 660-661): crystal_khz = eax_base_mhz * 1000 * eax_denominator / ebx_numerator; But in the same function, Linux returns this (line 674): return crystal_khz * ebx_numerator / eax_denominator; So the numerator and denominator in crystal_khz effectively cancels out on CPUID 0x16. >From what I understand, Linux expects the value in kilohertz, so a multiplier of 1000 works on Linux. I believe FreeBSD expects hertz, so a multiplier of 100 is needed. For unit conversion of megahertz to hertz, 1000 Hz = 1 KHz and 1000 KHz = 1 MHz, so 1 MHz = 1000 KHz * 1000 Hz. Also, using the numerator and denominator wouldn't work (I've tried that, I got a kernel panic). -- 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 240545] patch to remove unneeded M_WAITOK return value checks
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240545 Mark Linimon changed: What|Removed |Added Keywords||patch -- 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 240543] Realtek ALC265 - Asus Vivobook e203n audio device does not work
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240543 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|multime...@freebsd.org Summary|Realtek ALC265 - Asus |Realtek ALC265 - Asus |Vivobook e203n |Vivobook e203n audio device ||does not work -- 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"
