Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 2 Sep 2018 10:21:57 +0200 (CEST)
From:      Ronald Klop <ronald-lists@klop.ws>
To:        Alex McKeever <alex.mckeever@sbcglobal.net>, FreeBSD Stable <freebsd-stable@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org>
Subject:   Re: Failing to retrieve source tarballs for anything.
Message-ID:  <102862689.39555.1535876517540@localhost>
In-Reply-To: <294624069.2289978.1535835996261@mail.yahoo.com>

next in thread | previous in thread | raw e-mail | index | archive | help
First guess... Connect a network cable.


Please copy-paste the error message in your mail. It helps people helping y=
ou.
Any relevant message in /var/log/messages?=20


Regards,=20
Ronald.


Sorry for top posting, my mobile mail app does this.


Van: Alex McKeever <alex.mckeever@sbcglobal.net>
Datum: 01 september 2018 23:06
Aan: Ronald Klop <ronald-lists@klop.ws>, FreeBSD Stable <freebsd-stable@fre=
ebsd.org>, FreeBSD Current <freebsd-current@freebsd.org>
Onderwerp: Re: Failing to retrieve source tarballs for anything.

>=20
>=20
>=20
> I simply changed directory to which thing I want to compile in /ports, ru=
n the command make install, and after a short while it fails to retrieve th=
e source archive (.tar.gz)
>=20
>=20
> Sent from Yahoo Mail for iPhone
>=20
>=20
> On Saturday, September 1, 2018, 4:56 PM, Ronald Klop <ronald-lists@klop.w=
s> wrote:
>>=20
>> It helps a lot of you send the exact command you run with the error mess=
age. Or all the significant output.
>>=20
>>=20
>>=20
>>=20
>> Regards,
>> Ronald
>>=20
>>=20
>> Van: Alex McKeever <alex.mckeever@sbcglobal.net>
>> Datum: 01 september 2018 19:50
>> Aan: FreeBSD Stable <freebsd-stable@freebsd.org>, FreeBSD Current <freeb=
sd-current@freebsd.org>
>> Onderwerp: Failing to retrieve source tarballs for anything.
>>=20
>>>=20
>>> After compiling PKG, when I go to ports to compile anything (my eMac ca=
n run FreeBSD but not modern Linux due to the version of the Radeon GPU) it=
 fails to retrieve any of the source tarballs for any of the software, desk=
top environments etc. I would like help to fix this, as I=E2=80=99d like to=
 run something current.
>>>=20
>>>=20
>>> Sent from Yahoo Mail for iPhone
>>> _______________________________________________
>>> freebsd-stable@freebsd.org mailing list
>>> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
>>> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.or=
g"
>>>=20
>>>=20
>>=20
>=20
>=20
>=20
From owner-freebsd-current@freebsd.org  Sun Sep  2 12:17:42 2018
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id AA8E5FEDFA0
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Sun,  2 Sep 2018 12:17:42 +0000 (UTC)
 (envelope-from Alexander@leidinger.net)
Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org
 [IPv6:2001:1900:2254:206a::50:5])
 by mx1.freebsd.org (Postfix) with ESMTP id 4B9D376B52
 for <freebsd-current@freebsd.org>; Sun,  2 Sep 2018 12:17:42 +0000 (UTC)
 (envelope-from Alexander@leidinger.net)
Received: by mailman.ysv.freebsd.org (Postfix)
 id 0F035FEDF9F; Sun,  2 Sep 2018 12:17:42 +0000 (UTC)
Delivered-To: current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id C7813FEDF9D
 for <current@mailman.ysv.freebsd.org>; Sun,  2 Sep 2018 12:17:41 +0000 (UTC)
 (envelope-from Alexander@leidinger.net)
Received: from mailgate.Leidinger.net (bastille.leidinger.net [89.238.82.207])
 (using TLSv1.2 with cipher DHE-RSA-CAMELLIA128-SHA (128/128 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 5D88076B51
 for <current@freebsd.org>; Sun,  2 Sep 2018 12:17:40 +0000 (UTC)
 (envelope-from Alexander@leidinger.net)
Date: Sun, 02 Sep 2018 14:17:13 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=leidinger.net;
 s=outgoing-alex; t=1535890651;
 bh=0D6Tazn5IHO1iULUbzRh5Z3eeEarRd8M5lMyB++EAPY=;
 h=Date:From:To:Subject;
 b=k/uJpUYIYWen3OEQauIqRjMD7aDIuPmk8RtiweyT/siHukRBcOuOVKrDIewEdZpuX
 lA0YHGs6xUlkOGI6243eB4kD/t3QglobQLV+fWrGSPiuY/4f4DbIT2q4Xly/mcQQeW
 In+SMGbCr4ujHafL27Qv7hFk6GazZQ8N+DWskCnyT6U54vK+BCsdWo1pUAc/qQgMhQ
 ZrTZNg8/chUscgnlTE9LI7WLAvK9xNfJfD/9pXUg7nfAa9SD5eU59qlKkg3InMEGXA
 aPXAO0DpcdJ+Fblc8MMYEBENzMXeymj6ygfJADljg+ypGMHXpWnuNG9mckC4aIZBon
 /oFwUZCjrML6A==
Message-ID: <20180902141713.Horde.K4sEjBr68eHohodvzTmRRp6@webmail.leidinger.net>
From: Alexander Leidinger <Alexander@leidinger.net>
To: current@freebsd.org
Subject: page fault in ip6_output
User-Agent: Horde Application Framework 5
Accept-Language: de,en
Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes
MIME-Version: 1.0
Content-Disposition: inline
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>;
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Sep 2018 12:17:42 -0000

Hi,

-current at r338322 with manually applied r338372 (fix potential data  
corruption in iflib) and r338416 (re-compute arc size).

What worries me a little bit about the validity of this report is the  
gdb 8.1.1 error when loading the dump/kernel:
---snip---
warning: kld_current_sos: Can't read filename: Unknown error: -1

inferior.c:311: internal-error: struct inferior  
*find_inferior_pid(int): Assertion `pid != 0' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) [answered Y; input not from terminal]

This is a bug, please report it.  For instructions, see:
<http://www.gnu.org/software/gdb/bugs/>.

inferior.c:311: internal-error: struct inferior  
*find_inferior_pid(int): Assertion `pid != 0' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) [answered Y; input not from terminal]
Abort trap (core dumped)
---snip---

kernel panic:
---snip---
Unread portion of the kernel message buffer:


Fatal trap 12: page fault while in kernel mode
cpuid = 5; apic id = 13
fault virtual address   = 0x98
fault code              = supervisor read data, page not present
instruction pointer     = 0x20:0xffffffff8068cbf2
stack pointer           = 0x28:0xfffffe0128caa510
frame pointer           = 0x28:0xfffffe0128caa760
code segment            = base 0x0, limit 0xfffff, type 0x1b
                         = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 1658 (isc-worker0003)
trap number             = 12
panic: page fault
cpuid = 5
time = 1535835179
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0128caa1c0
vpanic() at vpanic+0x1a3/frame 0xfffffe0128caa220
panic() at panic+0x43/frame 0xfffffe0128caa280
trap_fatal() at trap_fatal+0x35f/frame 0xfffffe0128caa2d0
trap_pfault() at trap_pfault+0x49/frame 0xfffffe0128caa330
trap() at trap+0x2ba/frame 0xfffffe0128caa440
calltrap() at calltrap+0x8/frame 0xfffffe0128caa440
--- trap 0xc, rip = 0xffffffff8068cbf2, rsp = 0xfffffe0128caa510, rbp  
= 0xfffffe0128caa760 ---
ip6_output() at ip6_output+0xf82/frame 0xfffffe0128caa760
udp6_send() at udp6_send+0x702/frame 0xfffffe0128caa920
sosend_dgram() at sosend_dgram+0x346/frame 0xfffffe0128caa980
kern_sendit() at kern_sendit+0x170/frame 0xfffffe0128caaa10
sendit() at sendit+0x19e/frame 0xfffffe0128caaa60
sys_sendmsg() at sys_sendmsg+0x61/frame 0xfffffe0128caaac0
amd64_syscall() at amd64_syscall+0x254/frame 0xfffffe0128caabf0
fast_syscall_common() at fast_syscall_common+0x101/frame 0xfffffe0128caabf0
--- syscall (28, FreeBSD ELF64, sys_sendmsg), rip = 0x8015adf0a, rsp =  
0x7fffdf9f7218, rbp = 0x7fffdf9f7250 ---
Uptime: 22h37m4s
Dumping 13174 out of 61352  
MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91%
---snip---

I can not reproduce it at will, but it happens often enough (from once  
a day to several times after each reboot).

Can this gdb be trusted? If yes, which frame do you want to see more detailed?

Bye,
Alexander.

-- 
http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.org    netchild@FreeBSD.org  : PGP 0x8F31830F9F2772BF



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?102862689.39555.1535876517540>