On Wed, Dec 30, 2020 at 02:02:48AM +, Rick Macklem wrote:
> Hi,
>
> Post r367671...
> When multiple files are being created by an NFS client in the same
> directory, the VOP_CREATE()/ufs_create() can fail with ERELOOKUP.
> This results in a EIO return to the NFS client.
> --> This causes "nfsv
On Wed, 30 Dec 2020 12:13:44 +0100
Michael Tuexen wrote:
> On 30. Dec 2020, at 08:04, Hartmann, O. wrote:
> >
> > On recent 12-STABLE, 12.1-RELENG and 12.2-RELENG I face a very nasty
> > problem which
> > occured a while ago after it seemed to have vanished for a while: running
> > ssh in a
>
On Wed, Dec 30, 2020 at 08:04:03AM +0100, Hartmann, O. wrote:
> On recent 12-STABLE, 12.1-RELENG and 12.2-RELENG I face a very nasty problem
> which
> occured a while ago after it seemed to have vanished for a while: running ssh
> in a xterm
> on FreeBSD boxes as mentioned at the beginning ends u
On Mon, 2020-12-28 at 17:06:26 -0800, David Wolfskill wrote:
On Mon, Dec 28, 2020 at 04:56:39PM -0800, John-Mark Gurney wrote:
monochrome wrote this message on Mon, Dec 28, 2020 at 19:38 -0500:
> what would be the git command for reverting source to a previous version
> using these numbers? for
On Mon, 2020-12-28 at 19:38:05 -0500, monochrome wrote:
what would be the git command for reverting source to a previous version
using these numbers? for example, with svn and old numbers:
svnlite update -r367627 /usr/src
this is needed often when it blows up for someone tracking current
You n
On Wed, Dec 30, 2020 at 08:04:03AM +0100, Hartmann, O. wrote:
> ...
>
> # Fssh_packet_write_wait: Connection to XXX.XXX.XXX.XXX port 22: Broken pipe
>
> The backend is in most cases a CURRENT, 12.1-RELENG or 12.2-RELENG or
> 12-STABLE server. A
> couple of months ago we moved from 11.3-RELENG to
Kostik wrote:
>On Wed, Dec 30, 2020 at 02:02:48AM +, Rick Macklem wrote:
>> Hi,
>>
>> Post r367671...
>> When multiple files are being created by an NFS client in the same
>> directory, the VOP_CREATE()/ufs_create() can fail with ERELOOKUP.
>> This results in a EIO return to the NFS client.
>>
On Wed, Dec 30, 2020 at 04:48:27PM +, Rick Macklem wrote:
> Kostik wrote:
> >On Wed, Dec 30, 2020 at 02:02:48AM +, Rick Macklem wrote:
> >> Hi,
> >>
> >> Post r367671...
> >> When multiple files are being created by an NFS client in the same
> >> directory, the VOP_CREATE()/ufs_create() can
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" branding and an "Optane"
> SSD wh
On Wed, Dec 30, 2020 at 07:27:08PM +0200, Konstantin Belousov wrote:
> On Wed, Dec 30, 2020 at 04:48:27PM +, Rick Macklem wrote:
> > Kostik wrote:
> > >On Wed, Dec 30, 2020 at 02:02:48AM +, Rick Macklem wrote:
> > >> Hi,
> > >>
> > >> Post r367671...
> > >> When multiple files are being cre
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(&sc->vmd_bus.rman);
In the fail: statement in vmd_attach().
But I
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-12-30 10:04, C
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
I think I found the issue:
This PCIe controller is not detected:
1:e0:1d.0 PCI bridge [0604]: Intel Corporation Tiger Lake-LP PCI
Express Root Port #9 [8086:a0b0] (rev 20) SI
I believe the above PCIe controller is exposed by VMD (as it is on
Linux), but FreeBSD vmd/vmd_bus is unable to a
I also have this breaking builds. Do we have plans to revert this until a
variant that doesn't break builds in some corner cases is completed?
On Tue, Dec 15, 2020 at 12:22 PM Ryan Moeller wrote:
>
> On 12/12/20 2:15 AM, Graham Perrin wrote:
> > On 23/11/2020 12:18, Graham Perrin wrote:
> >
> >>
Hello:
I'm trying to update a system from:
FreeBSD 13.0-CURRENT #0 r365372: Sun Sep 6 10:51:26 EDT 2020
amd64
to the latest version.
buildworld completes successfully.
buildkernel, however, dies with:
struct device dev;
^
/usr/sr
Rick Macklem wrote:
>Kostik wrote:
> >
> >Idea of the change is to restart the syscall at top level. So for NFS
> >server the right approach is to not send a response and also to not
> >free the request mbuf chain, but to restart processing.
> Yes. I took a look and I think restarting the operatio
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
___
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 +
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/
20 matches
Mail list logo
