On 2021-08-05 09:42, Hans Petter Selasky wrote:
Hi,
I was lucky to get the hands on a mini-ITX containing a
"AMD Ryzen 5 3400G with Radeon Vega Graphics".
FreeBSD-13 installed just fine and 4K HDMI output works too with
AMDGPU. However I noticed some problems with a webcamd DVB-T receiver,
Hi Warner,
On 2021-07-04 15:17, Warner Losh wrote:
Have you used 'git bisect' yet? It looks like there's only about 244
commits between
last known working and the known broken commit of mine
I was about to do just that. I just posted incase I heard from anyone
else about the commits.
I
Hi freebsd-current@ (CC'd ambrisko@ and imp@),
Right now, with a laptop (HP Spectre x360 13t-aw200) which needs the
vmd(8) driver for NVMe, I am getting kernel panics upon bootup with a
recent kernel.
Here's a screenshot of the panic:
Hi Hans,
Sorry if I have to bother you again.
On 2021-06-20 01:36, Hans Petter Selasky wrote:
sg_dma_address() is zero, because the memory hasn't been loaded.
Makes sense!
You need to handle two cases there:
When r->iobase is -1 and when it is not.
I suspect you should add r->iobase to
On 2021-06-18 20:03, Neel Chauhan wrote:
Apparently, the vm_start values is for some reason coming as 0 when it
is passed into vm_fault_cpu(). That's why it's giving these errors: of
course the address at 0 is mapped, it is (probably) used by the
kernel.
An update: The vm_start 0 seems
On 2021-06-18 12:19, Neel Chauhan wrote:
I'm not sure. I'll just note that the Linux code appears to be trying
to map a set of pages belonging to a scatter-gather list. Taking the
physical address of the first page and assuming that all subsequent
pages are physically contiguous doesn't seem
Hi Mark,
On 2021-06-18 06:57, Mark Johnston wrote:
That seems surprising, since the vm_page_grab() call should return the
page at pidx if one exists.
I believe that's not the case. I did pringfs
Any hints on where the physical address is? Should we have an
FreeBSD-specific "pa" argument for
Hi Mark,
Thank you so much for your response!
On 2021-06-16 14:05, Mark Johnston wrote:
The function in question appears to implement a device page fault
handler. In FreeBSD, such handlers are responsible only for ensuring
that the requested page(s) are present in the VM object backing the
Hi,
On 2021-06-16 00:35, Hans Petter Selasky wrote:
Do you have the full backtrace?
Yes.
I have attached a stack trace in the previous email, but if you didn't
get it, I have uploaded it to GitHub:
https://gist.github.com/neelchauhan/437bd10239f84c563aafb37ab440029a
Doesn't this code
n-based PC and offload my Tor servers
to it (assuming latest Ryzen > Skylake Xeon Scalable in single-thread
performance).
-Neel
On 2021-01-27 11:04, Mark Johnston wrote:
On Sat, Jan 23, 2021 at 03:25:59PM +, Rick Macklem wrote:
Ronald Klop wrote:
>On Wed, 20 Jan 2021 21:21:15 +0100, Nee
Hi freebsd-current@,
I know that In-Kernel TLS was merged into the FreeBSD HEAD tree a while
back.
With 13.0-RELEASE around the corner, I'm thinking about upgrading my
home server, well if I can accelerate any SSL application.
I'm asking because I have a home server on a symmetrical
For reference, I am attaching the `pciconf -lv` and `acpidump -dt`
dumps.
-Neel
On 2020-12-30 21:42, Neel Chauhan wrote:
Hi freebsd-current@,
My apologies for so many emails from me. I sent another copy of this
email to freebsd-hackers@.
I have the following patch:
diff --git a/sys/dev/vmd
Hi freebsd-current@,
My apologies for so many emails from me. I sent another copy of this
email to freebsd-hackers@.
I have the following patch:
diff --git a/sys/dev/vmd/vmd.c b/sys/dev/vmd/vmd.c
index 2cc6f45bed9..7cc0a8a91a7 100644
--- a/sys/dev/vmd/vmd.c
+++ b/sys/dev/vmd/vmd.c
@@ -66,10
On 2020-12-30 21:04, Neel Chauhan wrote:
It is likely because VMD uses PCI domain above 0x1 but we aren't
looking at this.
The 0x1 is purely a Linux construct. It seems the PCI domains are
virtual.
Source: https://lists.x.org/archives/xorg-devel/2016-August/050590.html
-Neel
10:04, Chuck Tuffli wrote:
On Tue, Dec 29, 2020 at 6:30 PM Neel Chauhan wrote:
Hi freebsd-hackers@, CC'd freebsd-current@,
I hope you all had a wonderful holiday season.
I recently got a HP Spectre x360 13t-aw200 which is an Intel
TigerLake-based laptop. It has the Intel "Evo"
I have attached two files:
* pcidump.txt: A dump of `pciconf -lv`
* acpidump.txt: A dump of `acpidump`
Hope this can help.
-Neel
On 2020-12-30 17:21, Neel Chauhan wrote:
To extend, I am getting an issue with `pci_read_device()` where it
returns a `vid` (PCI Vendor ID) of 0x.
This ends
To extend, I am getting an issue with `pci_read_device()` where it
returns a `vid` (PCI Vendor ID) of 0x.
This ends up returning "Cannot allocate dinfo!" from vmd.
Log (via grep): https://imgur.com/a/tAmmY7i
-Neel
On 2020-12-30 16:38, Neel Chauhan wrote:
Hi Chuck,
On 2020-1
Hi Chuck,
On 2020-12-30 10:04, Chuck Tuffli wrote:
What is the output from
# pciconf -rb pci0:0:14:0 0x40:0x48
The output is:
01 00 00 00 01 2e 68 02 00
--chuck
I was also able to stop kernel panics by adding:
rman_fini(>vmd_bus.rman);
In the fail: statement in vmd_attach().
But I
o know about PCI/ACPI subsystems, can you please tell me
what's going wrong?
I'm still debugging in the meanwhile, but am no expert on PCI/ACPI
subsystems. I may know more than most PC builders or CS grads, but not
really enough to do it full-time.
The Spectre's SSD works fine with Windo
On 2020-06-26 21:20, Matthew Macy wrote:
Well - it was from his review.
That's true.
Thanks for committing!
-Neel
===
https://www.neelc.org/
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
ild broke with mmacy@'s commit r362666 which renamed nvpair.c to
bsd_nvpair.c without renaming the Makefile.
Is anyone else having this error?
I have a patch to unbreak the build here:
https://reviews.freebsd.org/D25481
Does the patch work?
Best,
Neel Chau
I don't have a MacBook. I don't own one and my work gives me a ThinkPad
(but runs Windows).
I believe the issue on new Macs is the NVMe queue size or something.
You should read the Linux driver, the FreeBSD equivalents, and then
build your patch on the differences in how the hardware is
Not OP, but would BBR work with VNET, or is that a WIP?
I'm sorry if none of you are familiar with VNET.
-Neel
===
https://www.neelc.org/
BTW: Not neel@ the committer
On 2020-04-24 12:25, Michael Tuexen wrote:
On 24. Apr 2020, at 21:06, Rodney W. Grimes
wrote:
On Fri, Apr 24, 2020 at
Hi freebsd-current@
I have a a HP Spectre x360 13-ap0053dx running 13-CURRENT r360134, I get
this when running acpiconf -i 0:
root@spectre:/home/neel # acpiconf -i 0
Design capacity:0 mWh
Last full capacity: 0 mWh
Technology: primary (non-rechargeable)
Design voltage:
Hi freebsd-current@,
Back in September, I submitted a patch which adds support for the HD
Audio codecs in Intel's Cannon Lake PCH as used by the HP Spectre x360
2018/13-ap0053dx (the "13-p0043dx" is a typo). This was committed as
r352775 and r352776.
However, these two patches are not in
Hi freebsd-current@ mailing list,
When I updated my laptop to r355560, I could boot into GDM, but logging
into GNOME led to a coredump and brought me back to GDM.
I tried KDE, but logging in via SDDM also led to a crash.
I noted a lot of changes to the VM subsystem have happened, are they
Hi freebsd-current@, freebsd-ports@ mailing lists,
When I updated my laptop to r355560, I could boot into GDM, but logging
into GNOME led to a coredump and brought me back to GDM.
I tried KDE, but logging in via SDDM also led to a crash.
I noted a lot of changes to the VM subsystem have
For me, the following code is still necessary for me (HP Spectre x360
2018), which is the remaining parts of the patches not committed if you
are using a recent kernel. I don't know about you all ThinkPad users, it
should still apply as it's Intel in general not just HP or Lenovo.
Without
test drm-v5.0 branch of drm-current-kmod worked just fine with
Intel HD Graphics P630 on Lenovo P51.
On 2019-10-17 18:37, Neel Chauhan wrote:
However, the patch to drm-kmod doesn't work for me. I tried both
drm-devel-kmod and drm-current-kmod.
https://i.imgur.com/81JvaOO.jpg
-Neel
===
https://
However, the patch to drm-kmod doesn't work for me. I tried both
drm-devel-kmod and drm-current-kmod.
https://i.imgur.com/81JvaOO.jpg
-Neel
===
https://www.neelc.org/
On 2019-10-17 17:35, Eirik Øverby wrote:
On 10/17/19 11:29 PM, Eirik Øverby wrote:
On 10/17/19 10:31 PM, Niclas Zeising
While drm-current-kmod worked for a little while, it broke with r353645.
https://i.imgur.com/Q5nYZf2.jpg
I'm using the same HP Spectre that I used earlier (where it worked and
where it panicked).
-Neel
===
https://www.neelc.org/
On 2019-10-13 10:37, Mateusz Guzik wrote:
On 10/13/19,
The patch doesn't work for me on i915kms on a HP Spectre x360
13-p0043dx. I get a panic
Screenshot:
https://user-images.githubusercontent.com/5403564/66688014-d1a16700-ec52-11e9-9c3b-902f49e311de.png
As of now, I'm using an older kernel.
-Neel
===
https://www.neelc.org/
On 2019-10-11
The patch doesn't work for me on i915kms on a HP Spectre x360
13-p0043dx. I get a panic
Screenshot:
https://user-images.githubusercontent.com/5403564/66688014-d1a16700-ec52-11e9-9c3b-902f49e311de.png
As of now, I'm using an older kernel.
-Neel
===
https://www.neelc.org/
On 2019-10-11
Hi freebsd-current@ mailing list,
I have a patch which adds support for the HD Audio Codecs for the Intel
Comet Lake and Ice Lake PCHs. This is similar to my now-committed Cannon
Lake HD Audio patch.
Please find below the Bugzilla and Phabricator links (both have the
patch):
Bugzilla:
Hi,
I recently got a HP Spectre x360 13-ap0043dx as a gift and by default
the clock runs slower on FreeBSD than Windows or Linux. Yes, I know the
ThinkPad is the best laptop for FreeBSD, but getting an X1 Carbon would
increase the price of the gift even more which couldn't be done.
The
On 2013-11-12 03:29, Konstantin Belousov wrote:
On Mon, Nov 11, 2013 at 03:39:06PM -0800, Xin Li wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 11/11/13 14:29, Neel Chauhan wrote:
Sorry if I sent a similar patch before. It didn't get accepted so I
am sending one now. Enjoy.
What
Hello FreeBSD-CURRENT and FreeBSD-X11 mailing list(s),
I have a patch to add support for kernel mode setting on Intel
Haswell/4th generation Core i(3/5/7) chips. The patch is:
diff -u -r -N head/sys/dev/agp/agp_i810.c tree/sys/dev/agp/agp_i810.c
--- head/sys/dev/agp/agp_i810.c 2013-11-11
Dear freebsd-current mailing list,
I created a patch to support kernel mode setting on Intel Haswell. The
patch starts below:
diff -u -r -N freebsd.old/sys/dev/drm2/drm_pciids.h
freebsd/sys/dev/drm2/drm_pciids.h
--- freebsd.old/sys/dev/drm2/drm_pciids.h 2013-09-20 14:58:24.0
-0400
38 matches
Mail list logo
