date:20180902

Re: page fault in ip6_output

2018-09-02 Thread Alexander Leidinger


Quoting Sean Bruno  (from Sun, 2 Sep 2018 08:52:11 -0600):


I think, you have hit this, no?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230950


Looks like it. I've added me to the CC list of the PR.

Thanks,
Alexander.

--
http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.orgnetch...@freebsd.org  : PGP 0x8F31830F9F2772BF
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Kernel panic: Need help debugging

2018-09-02 Thread lr x

Hi!

I can get the kernel to panic when I try to run virtualbox (selecting the
amd64 ubuntu iso and attaching to virtual machine and starting it up.).

The kernel:
12.0-ALPHA3 FreeBSD 12.0-ALPHA3 #0 r338359: Wed Aug 29 21:49:53 EDT
2018 someone@somebox:/usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64

Virtualbox was installed with pkg install virtualbox-ose

I have access to the crash dump, but running with kgdb does not reveal more
information. I found a reference to the panic string:
https://reviews.freebsd.org/D4197 .  I could find that the panic string is
indeed printed in the malloc_dbg function in the /sys/kern/kern_malloc.c
file. How can I trace this further to understand why the kernel lands in
such a situation?

Thanks!

Here are the contents of the info.last file and kgdb invocation on the
crash dump.

# cat /var/crash/info.last
Dump header from device: /dev/ada0p4
  Architecture: amd64
  Architecture Version: 2
  Dump Length: 937099264
  Blocksize: 512
  Compression: none
  Dumptime: Sat Sep  1 22:50:57 2018
  Hostname: somebox
  Magic: FreeBSD Kernel Dump
  Version String: FreeBSD 12.0-ALPHA3 #0 r338359: Wed Aug 29 21:49:53 EDT
2018
someone@somebox:/usr/obj/usr/src/amd64.amd64/sys/GENERIC
  Panic String: malloc: called with spinlock or critical section held
  Dump Parity: 274387030
  Bounds: 3
  Dump Status: good


root@somebox:/usr/src # kgdb -n 3
<..snip..>
Unread portion of the kernel message buffer:


Fatal trap 12: page fault while in kernel mode
cpuid = 4; apic id = 04
fault virtual address= 0x80a851ab8
fault code= supervisor read data, protection violation
instruction pointer= 0x20:0x8354b2e4
stack pointer= 0x28:0xfe008ced1200
frame pointer= 0x28:0xfe008ced1200
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process= 1792 (VirtualBox)
Uptime: 48m52s
(ada0:ahcich2:0:0:0): spin-down
Dumping 893 out of 16221
MB:..2%..11%..22%..31%..42%..51%..61%..72%..81%..92%



#0  cpustop_handler () at /usr/src/sys/x86/x86/mp_x86.c:1383
1383CPU_SET_ATOMIC(cpu, _cpus);

(kgdb) bt
#0  cpustop_handler () at /usr/src/sys/x86/x86/mp_x86.c:1383
#1  0x811d1484 in ipi_nmi_handler () at
/usr/src/sys/x86/x86/mp_x86.c:1341
#2  0x8105d889 in trap (frame=0x82057db0) at
/usr/src/sys/amd64/amd64/trap.c:206
#3  0x8103baad in nmi_calltrap () at
/usr/src/sys/amd64/amd64/exception.S:776
#4  0x811c1f76 in cpu_idle (busy=) at
/usr/src/sys/x86/x86/cpu_machdep.c:489
Previous frame inner to this frame (corrupt stack?)
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Fatal trap 9 when rebooting after installkernel on VirtualBox VM

2018-09-02 Thread Yasuhiro KIMURA

Hello.

I'm tracking head with VirtualBox VM. Everytime new snapshot is
released I update to same revision. So buildworld, buildkernel and
installkernel always completes sucsessfully. But when rebooting system
always crashes with 'Fatal trap 9: general protection fault while in
kernel mode' message. And I closed VM window and restart VM, new
kernel start up without any problem.

https://www.utahime.org/FreeBSD/VirtualBox_FreeBSD_12.0-ALPHA3.png

This is a screenshot of latest update (ALPHA3 -> ALPHA4).

Does anyone else experienced it?

Conditions about VM and host are following:

VM:
  CPU: x4
  Memory: 8GB
  Disk: 100GB SATA
Host:
  CPU: Intel Core i7 4770S
  Memory: 16GB
  Disk: 2TB SATA
  OS: 64bit Windows 10 Enterprise 1803

Best Regards.

---
Yasuhiro KIMURA
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: page fault in ip6_output

2018-09-02 Thread Sean Bruno



On 9/2/18 6:17 AM, Alexander Leidinger wrote:
> 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:
> .
> 
> 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:0x8068cbf2
> stack pointer   = 0x28:0xfe0128caa510
> frame pointer   = 0x28:0xfe0128caa760
> code segment    = base 0x0, limit 0xf, 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
> 0xfe0128caa1c0
> vpanic() at vpanic+0x1a3/frame 0xfe0128caa220
> panic() at panic+0x43/frame 0xfe0128caa280
> trap_fatal() at trap_fatal+0x35f/frame 0xfe0128caa2d0
> trap_pfault() at trap_pfault+0x49/frame 0xfe0128caa330
> trap() at trap+0x2ba/frame 0xfe0128caa440
> calltrap() at calltrap+0x8/frame 0xfe0128caa440
> --- trap 0xc, rip = 0x8068cbf2, rsp = 0xfe0128caa510, rbp =
> 0xfe0128caa760 ---
> ip6_output() at ip6_output+0xf82/frame 0xfe0128caa760
> udp6_send() at udp6_send+0x702/frame 0xfe0128caa920
> sosend_dgram() at sosend_dgram+0x346/frame 0xfe0128caa980
> kern_sendit() at kern_sendit+0x170/frame 0xfe0128caaa10
> sendit() at sendit+0x19e/frame 0xfe0128caaa60
> sys_sendmsg() at sys_sendmsg+0x61/frame 0xfe0128caaac0
> amd64_syscall() at amd64_syscall+0x254/frame 0xfe0128caabf0
> fast_syscall_common() at fast_syscall_common+0x101/frame 0xfe0128caabf0
> --- 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.
> 


I think, you have hit this, no?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230950



signature.asc
Description: OpenPGP digital signature

page fault in ip6_output

2018-09-02 Thread Alexander Leidinger


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:
.

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:0x8068cbf2
stack pointer   = 0x28:0xfe0128caa510
frame pointer   = 0x28:0xfe0128caa760
code segment= base 0x0, limit 0xf, 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 0xfe0128caa1c0
vpanic() at vpanic+0x1a3/frame 0xfe0128caa220
panic() at panic+0x43/frame 0xfe0128caa280
trap_fatal() at trap_fatal+0x35f/frame 0xfe0128caa2d0
trap_pfault() at trap_pfault+0x49/frame 0xfe0128caa330
trap() at trap+0x2ba/frame 0xfe0128caa440
calltrap() at calltrap+0x8/frame 0xfe0128caa440
--- trap 0xc, rip = 0x8068cbf2, rsp = 0xfe0128caa510, rbp  
= 0xfe0128caa760 ---

ip6_output() at ip6_output+0xf82/frame 0xfe0128caa760
udp6_send() at udp6_send+0x702/frame 0xfe0128caa920
sosend_dgram() at sosend_dgram+0x346/frame 0xfe0128caa980
kern_sendit() at kern_sendit+0x170/frame 0xfe0128caaa10
sendit() at sendit+0x19e/frame 0xfe0128caaa60
sys_sendmsg() at sys_sendmsg+0x61/frame 0xfe0128caaac0
amd64_syscall() at amd64_syscall+0x254/frame 0xfe0128caabf0
fast_syscall_common() at fast_syscall_common+0x101/frame 0xfe0128caabf0
--- 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 alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.orgnetch...@freebsd.org  : PGP 0x8F31830F9F2772BF
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Failing to retrieve source tarballs for anything.

2018-09-02 Thread Ronald Klop


First guess... Connect a network cable.


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



Regards, 
Ronald.



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


Van: Alex McKeever 
Datum: 01 september 2018 23:06
Aan: Ronald Klop , FreeBSD Stable , 
FreeBSD Current 
Onderwerp: Re: Failing to retrieve source tarballs for anything.





I simply changed directory to which thing I want to compile in /ports, run the 
command make install, and after a short while it fails to retrieve the source 
archive (.tar.gz)


Sent from Yahoo Mail for iPhone


On Saturday, September 1, 2018, 4:56 PM, Ronald Klop  
wrote:


It helps a lot of you send the exact command you run with the error message. Or 
all the significant output.




Regards,
Ronald


Van: Alex McKeever 
Datum: 01 september 2018 19:50
Aan: FreeBSD Stable , FreeBSD Current 

Onderwerp: Failing to retrieve source tarballs for anything.



After compiling PKG, when I go to ports to compile anything (my eMac can 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, desktop 
environments etc. I would like help to fix this, as I’d like to run something 
current.


Sent from Yahoo Mail for iPhone
___
freebsd-sta...@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"









___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: page fault in ip6_output

Kernel panic: Need help debugging

Fatal trap 9 when rebooting after installkernel on VirtualBox VM

Re: page fault in ip6_output

page fault in ip6_output

Re: Failing to retrieve source tarballs for anything.

6 matches

Site Navigation

Mail list logo

Footer information