On Mon, 7 Jun 2021 16:54:11 -0400
Mark Johnston wrote:
> On Mon, Jun 07, 2021 at 11:01:09AM +0200, Gary Jennejohn wrote:
> > I've seen this panic three times in the last two days:
> >
> > [first panic]
> > Unread portion of the kernel message buffer:
> >
> >
> > Fatal trap 12: page fault while
Given how easy it is to reproduce perhaps you can spend a little bit
of time narrowing it down to a specific commit. You can do it with
git-bisect.
On 6/8/21, Gary Jennejohn wrote:
> On Mon, 7 Jun 2021 16:54:11 -0400
> Mark Johnston wrote:
>
>> On Mon, Jun 07, 2021 at 11:01:09AM +0200, Gary Jenn
On 6/8/21 11:04 AM, Mateusz Guzik wrote:
Apparently caused by recent changes to CAM.
Let me know if you want more information.
Maybe you can print the *ccb being freed and figure out which device it
belongs to.
--HPS
On Mon, Jun 07, 2021 at 01:58:01PM -0600, Ian Lepore wrote:
> Sometimes it's a real interesting exercise to figure out where a
> file on your runtime system comes from in the source world.
A tangential problem I trip over is "what is on this SD card?"
It generally takes me 5-10 minutes to remembe
On Mon, 7 Jun 2021 22:35:20 +0200
Baptiste Daroussin wrote:
> On Mon, Jun 07, 2021 at 12:30:46AM -0700, Mark Millard wrote:
> > On 2021-Jun-6, at 13:25, Mark Millard wrote:
> >
> > > Baptiste Daroussin wrote on
> > > Date: Sun, 6 Jun 2021 10:53:49 +0200 :
> > >
> > >> What has happende
8 juin 2021 13:15:50 Michael Gmelin :
>
>
> On Mon, 7 Jun 2021 22:35:20 +0200
> Baptiste Daroussin wrote:
>
>> On Mon, Jun 07, 2021 at 12:30:46AM -0700, Mark Millard wrote:
>>> On 2021-Jun-6, at 13:25, Mark Millard wrote:
>>>
Baptiste Daroussin wrote on
Date: Sun, 6 Jun 2021 10:53
On Tue, 8 Jun 2021 11:20:37 +0200
Hans Petter Selasky wrote:
> On 6/8/21 11:04 AM, Mateusz Guzik wrote:
> > Apparently caused by recent changes to CAM.
> >
> > Let me know if you want more information.
>
> Maybe you can print the *ccb being freed and figure out which device
> it belongs to.
>
On 6/8/21 1:34 PM, Gary Jennejohn wrote:
Fields in the ccb like periph_name, unit_number and dev_name are filled
with zeroes.
Smells like a double free, like the panic message indicates, but would
be nice to know exactly which driver is doing this, if it is "ATA" or
"UMASS", so to speak.
Ma
On Tue, 8 Jun 2021 11:04:33 +0200
Mateusz Guzik wrote:
> Given how easy it is to reproduce perhaps you can spend a little bit
> of time narrowing it down to a specific commit. You can do it with
> git-bisect.
>
Ok, I'll give it a try.
--
Gary Jennejohn
Hello,
As mentioned in the "OpenZFS imports, status update":
https://lists.freebsd.org/archives/freebsd-git/2021-June/13.html
We're going to rename the current openzfs vendor branch,
vendor/openzfs, to vendor/openzfs/legacy
and import directly the master and zfs-2.1-release branches from
On Tue, 8 Jun 2021 09:41:34 +
Mark Linimon wrote:
> On Mon, Jun 07, 2021 at 01:58:01PM -0600, Ian Lepore wrote:
> > Sometimes it's a real interesting exercise to figure out where a
> > file on your runtime system comes from in the source world.
>
> A tangential problem I trip over is "what
On Tue, Jun 8, 2021 at 2:47 AM Gary Jennejohn wrote:
> On Mon, 7 Jun 2021 16:54:11 -0400
> Mark Johnston wrote:
>
> > On Mon, Jun 07, 2021 at 11:01:09AM +0200, Gary Jennejohn wrote:
> > > I've seen this panic three times in the last two days:
> > >
> > > [first panic]
> > > Unread portion of the
Sorry to reply to myself... had a thought as my brain rested while making
tea...
I think we may need to consider reverting (or at least not yet enabling)
the uma stuff.
On Tue, Jun 8, 2021 at 6:27 AM Warner Losh wrote:
>
>
> On Tue, Jun 8, 2021 at 2:47 AM Gary Jennejohn
> wrote:
>
>> On Mon, 7
On Tue, Jun 8, 2021 at 7:45 PM Li-Wen Hsu wrote:
>
> Hello,
>
> As mentioned in the "OpenZFS imports, status update":
>
> https://lists.freebsd.org/archives/freebsd-git/2021-June/13.html
>
> We're going to rename the current openzfs vendor branch,
> vendor/openzfs, to vendor/openzfs/legacy
On Tue, 8 Jun 2021 06:48:19 -0600
Warner Losh wrote:
> Sorry to reply to myself... had a thought as my brain rested while making
> tea...
>
> I think we may need to consider reverting (or at least not yet enabling)
> the uma stuff.
>
I tested and enabled the UMA CCB stuff immediately after tra
On Tue, 2021-06-08 at 13:47 +0200, Gary Jennejohn wrote:
> On Tue, 8 Jun 2021 09:41:34 +
> Mark Linimon wrote:
>
> > On Mon, Jun 07, 2021 at 01:58:01PM -0600, Ian Lepore wrote:
> > > Sometimes it's a real interesting exercise to figure out where a
> > > file on your runtime system comes from
On Tue, Jun 8, 2021 at 8:42 AM Gary Jennejohn wrote:
> On Tue, 8 Jun 2021 06:48:19 -0600
> Warner Losh wrote:
>
> > Sorry to reply to myself... had a thought as my brain rested while making
> > tea...
> >
> > I think we may need to consider reverting (or at least not yet enabling)
> > the uma st
On Tue, 8 Jun 2021 06:27:04 -0600
Warner Losh wrote:
> On Tue, Jun 8, 2021 at 2:47 AM Gary Jennejohn wrote:
>
[snip old stuff]
> > Here the kgdb backtrace:
> >
> > Unread portion of the kernel message buffer:
> > panic: Duplicate free of 0xf800356b9000 from zone
> > 0xfe00dcbdd800(da_cc
On 6/7/21 12:58 PM, Ian Lepore wrote:
On Mon, 2021-06-07 at 13:53 -0600, Warner Losh wrote:
On Mon, Jun 7, 2021 at 12:26 PM John Baldwin wrote:
On 5/20/21 9:37 AM, Michael Gmelin wrote:
Hi,
After a binary update using freebsd-update, all files in /etc
contain
"empty" VCS Id headers, e.g.,
Hi,
I’m having problem to build recent 14-CURRENT/aarch64 as of
6d2648bcaba9b14e2f5c76680f3e7608e1f125f4:
--- cddl/lib/libuutil__L ---
make[4]: make[4]: don't know how to make uu_dprintf.c. Stop
make[4]: make[4]: don't know how to make uu_open.c. Stop
`uu_alloc.c' is up to date.
`uu_avl.c' is up
On Tue, Jun 08, 2021 at 09:15:37PM +0200, Juraj Lutter wrote:
> Hi,
>
> I???m having problem to build recent 14-CURRENT/aarch64 as of
> 6d2648bcaba9b14e2f5c76680f3e7608e1f125f4:
>
> --- cddl/lib/libuutil__L ---
> make[4]: make[4]: don't know how to make uu_dprintf.c. Stop
> make[4]: make[4]: don
> On 8 Jun 2021, at 21:38, bob prohaska wrote:
>
> FWIW, same problem seen here. In an added twist, git pull (hoping for
> a fix) fails also:
>
> root@www:/usr/src # git pull
> error: cannot lock ref 'refs/remotes/freebsd/vendor/openzfs/legacy':
> 'refs/remotes/freebsd/vendor/openzfs' exists
On 6/8/21 3:42 PM, Juraj Lutter wrote:
On 8 Jun 2021, at 21:38, bob prohaska wrote:
FWIW, same problem seen here. In an added twist, git pull (hoping for
a fix) fails also:
root@www:/usr/src # git pull
error: cannot lock ref 'refs/remotes/freebsd/vendor/openzfs/legacy':
'refs/remotes/freeb
On Thu, 3 Jun 2021 15:09:06 +0200
Michael Gmelin wrote:
> On Tue, 1 Jun 2021 13:47:47 +0200
> Michael Gmelin wrote:
>
> > Hi,
> >
> > Since upgrading servers from 12.2 to 13.0, I get
> >
> > Fssh_packet_write_wait: Connection to 1.2.3.4 port 22: Broken pipe
> >
> > consistently, usually
Li-Wen Hsu wrote (in part) on
Date: Tue, 8 Jun 2021 06:29:51 +0800 :
> The people have local branch tracking the original vendor/openzfs will
> encounter issues like this whey doing `git pull`:
>
> error: cannot lock ref
> 'refs/remotes/freebsd/vendor/openzfs/legacy':
> 'refs/remotes/freebsd
> On Tue, 8 Jun 2021 09:41:34 +
> Mark Linimon wrote:
>
> > On Mon, Jun 07, 2021 at 01:58:01PM -0600, Ian Lepore wrote:
> > > Sometimes it's a real interesting exercise to figure out where a
> > > file on your runtime system comes from in the source world.
There is a command for that which
>
> On Thu, 3 Jun 2021 15:09:06 +0200
> Michael Gmelin wrote:
>
> > On Tue, 1 Jun 2021 13:47:47 +0200
> > Michael Gmelin wrote:
> >
> > > Hi,
> > >
> > > Since upgrading servers from 12.2 to 13.0, I get
> > >
> > > Fssh_packet_write_wait: Connection to 1.2.3.4 port 22: Broken pipe
> > >
>
> On 9. Jun 2021, at 00:20, Rodney W. Grimes
> wrote:
>
>>
>> On Thu, 3 Jun 2021 15:09:06 +0200
>> Michael Gmelin wrote:
>>
>>> On Tue, 1 Jun 2021 13:47:47 +0200
>>> Michael Gmelin wrote:
>>>
Hi,
Since upgrading servers from 12.2 to 13.0, I get
Fssh_packet_write_w
Top posting...
You can do a 'git remote purge freebsd' to reset the branch names, then
you'll be able to do a normal pull.
Thanks for the feedback
Warner
On Tue, Jun 8, 2021 at 4:10 PM Mark Millard via freebsd-git <
freebsd-...@freebsd.org> wrote:
> Li-Wen Hsu wrote (in part) on
> Date: Tue,
On Tue, Jun 8, 2021 at 4:58 PM Michael Tuexen <
michael.tue...@macmic.franken.de> wrote:
> > On 9. Jun 2021, at 00:52, Warner Losh wrote:
> >
> > Top posting...
> >
> > You can do a 'git remote purge freebsd' to reset the branch names, then
> > you'll be able to do a normal pull.
> Do you mean 'g
On Tue, 2021-06-08 at 15:11 -0700, Rodney W. Grimes wrote:
> > On Tue, 8 Jun 2021 09:41:34 +
> > Mark Linimon wrote:
> >
> > > On Mon, Jun 07, 2021 at 01:58:01PM -0600, Ian Lepore wrote:
> > > > Sometimes it's a real interesting exercise to figure out where
> > > > a
> > > > file on your runt
Hi,
On Tue, Jun 08, 2021 at 04:52:43PM -0600, Warner Losh wrote:
Top posting...
You can do a 'git remote purge freebsd' to reset the branch names, then
you'll be able to do a normal pull.
This doesn't work for me. I use the anonssh method of updating the tree
% git remote -v
origin ssh://an
> On 9. Jun 2021, at 03:07, tech-lists wrote:
>
> Hi,
>
> On Tue, Jun 08, 2021 at 04:52:43PM -0600, Warner Losh wrote:
>> Top posting...
>>
>> You can do a 'git remote purge freebsd' to reset the branch names, then
>> you'll be able to do a normal pull.
>
> This doesn't work for me. I use the
On Tue, Jun 08, 2021 at 05:02:15PM -0600, Warner Losh wrote:
On Tue, Jun 8, 2021 at 4:58 PM Michael Tuexen <
michael.tue...@macmic.franken.de> wrote:
> On 9. Jun 2021, at 00:52, Warner Losh wrote:
>
> Top posting...
>
> You can do a 'git remote purge freebsd' to reset the branch names, then
>
On Wed, Jun 09, 2021 at 03:14:01AM +0200, tue...@freebsd.org wrote:
Try: git remote prune freebsd
unfortunately that didn't work either. In the end I rm -rf'd src and
just cloned the repo again
--
J.
signature.asc
Description: PGP signature
On Tue, Jun 8, 2021, 7:31 PM tech-lists wrote:
> On Wed, Jun 09, 2021 at 03:14:01AM +0200, tue...@freebsd.org wrote:
> >Try: git remote prune freebsd
>
> unfortunately that didn't work either. In the end I rm -rf'd src and
> just cloned the repo again
>
You likely don't have freebsd as the remot
On 4/17/20, Ryan Moeller wrote:
>
>> On Apr 17, 2020, at 4:56 PM, Pete Wright wrote:
>>
>> On 4/17/20 11:35 AM, Ryan Moeller wrote:
>>> OpenZFS brings many exciting features to FreeBSD, including:
>>> * native encryption
>> Is there a good doc reference on available for using this? I believe th
On 4/17/20, Ryan Moeller wrote:
>
>> On Apr 17, 2020, at 4:56 PM, Pete Wright wrote:
>>
>> On 4/17/20 11:35 AM, Ryan Moeller wrote:
>>> OpenZFS brings many exciting features to FreeBSD, including:
>>> * native encryption
>> Is there a good doc reference on available for using this? I believe th
tech-lists wrote on
Date: Wed, 9 Jun 2021 02:13:07 +0100 :
> root_at_desktop:/usr/src# git remote prune freebsd
> fatal: 'freebsd' does not appear to be a git repository
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository e
On 8 Jun, Michael Gmelin wrote:
>
>
> On Thu, 3 Jun 2021 15:09:06 +0200
> Michael Gmelin wrote:
>
>> On Tue, 1 Jun 2021 13:47:47 +0200
>> Michael Gmelin wrote:
>>
>> > Hi,
>> >
>> > Since upgrading servers from 12.2 to 13.0, I get
>> >
>> > Fssh_packet_write_wait: Connection to 1.2.3.4 p
40 matches
Mail list logo
