Re: Kernel-Crash when working with ubt0, (Lizbeth Mutterhunt, Ph.D.)

From: Miranda van den Breukelingen <mms.vanbreukelingen_at_gmail.com>
Date: Mon, 14 Oct 2019 15:38:21 +0200
So there are two sides now: I'm still having existential problems with X
-configure on my new machine and the bug on the other (see below), that
can't be updated to recent kernel, even with the patch enabled.

There's no need to write it just for my old grandmothers-laptop and one
is always on linux, so there's YT music available without mobile usage.


Concerning Miranda van Breukelingen's (Lizbeth is just "my second
desktop" or the shadow package), problems,  this is still the problem:

FreeBSD freeBSD13 13.0-CURRENT FreeBSD 13.0-CURRENT #10 r353366: Wed
Oct  9 23:18:59 CEST 2019    
miranda_at_freeBSD13:/usr/obj/usr/home/src/head/amd64.amd64/sys/MIRANDA  amd64

panic: Assertion in_epoch(net_epoch_preempt) failed at
/usr/home/src/head/sys/netinet6/in6.c:1554

GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "amd64-marcel-freebsd"...

Unread portion of the kernel message buffer:
<118>Starting sshd.
<118>Starting git_daemon.
<6>bridge0: Ethernet address: 02:81:54:81:3d:00
<6>bridge0: changing name to 'virbr0'
<6>tap0: Ethernet address: 58:9c:fc:10:ff:8d
<6>tap0: link state changed to UP
<6>tap0: changing name to 'virbr0-nic'
panic: Assertion in_epoch(net_epoch_preempt) failed at
/usr/home/src/head/sys/netinet6/in6.c:1554
cpuid = 3
time = 1570660566
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x47/frame
0xfffffe003b94b680
vpanic() at vpanic+0x1e0/frame 0xfffffe003b94b6e0
panic() at panic+0x43/frame 0xfffffe003b94b740
in6ifa_llaonifp() at in6ifa_llaonifp+0x167/frame 0xfffffe003b94b770
bridge_ioctl_add() at bridge_ioctl_add+0x179/frame 0xfffffe003b94b7d0
bridge_ioctl() at bridge_ioctl+0x4ea/frame 0xfffffe003b94b870
ifioctl() at ifioctl+0xdb1/frame 0xfffffe003b94b940
kern_ioctl() at kern_ioctl+0x465/frame 0xfffffe003b94b9b0
sys_ioctl() at sys_ioctl+0x267/frame 0xfffffe003b94ba80
amd64_syscall() at amd64_syscall+0x44f/frame 0xfffffe003b94bbb0
fast_syscall_common() at fast_syscall_common+0x101/frame 0xfffffe003b94bbb0
--- syscall (54, FreeBSD ELF64, sys_ioctl), rip = 0x801bf52ea, rsp =
0x7fffde1eea18, rbp = 0x7fffde1eeb00 ---
KDB: enter: panic
Uptime: 56s
Dumping 338 out of 3949 MB:..5%..15%..24%..34%..43%..53%..62%..71%..81%..95%


If just someone had an idea how to get this s* radeon 240 to grafics mode:

hdac1: <ATI (0xaab0) HDA Controller> mem 0xfe660000-0xfe663fff at device
0.1 on pci6
hdac1: hdac_get_capabilities: Invalid corb size (0)
device_attach: hdac1 attach returned 6

or mixing new and old hardware with kmod-legacy.  skeleton fault of
sources on 'svn up' used to be a big problem even in a VM.

Looking forward for trying to solve at least one of the three problems.
Most important wouuld be the graphics for X -configure to work:

ubt0 on uhub0
ubt0: <Broadcom Corp BCM20702A0, rev 2.00/1.12, addr 8> on usbus0
WARNING: attempt to domain_add(bluetooth) after domainfinalize()
WARNING: attempt to domain_add(netgraph) after domainfinalize()

this would be your case I guess, but just if there's time and you are
bored.

thx,
m.








On 2019-10-14 14:00, freebsd-current-request_at_freebsd.org wrote:


> Send freebsd-current mailing list submissions to
> 	freebsd-current_at_freebsd.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://lists.freebsd.org/mailman/listinfo/freebsd-current
> or, via email, send a message with subject or body 'help' to
> 	freebsd-current-request_at_freebsd.org
>
> You can reach the person managing the list at
> 	freebsd-current-owner_at_freebsd.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of freebsd-current digest..."
>
> Today's Topics:
>
>    1. Re: HELP: UEFI/ZFS Boot failure: Ignoring Boot000A: Only one
>       DP found (O. Hartmann)
>    2. Re: Kernel-Crash when working with ubt0
>       (Lizbeth Mutterhunt, Ph.D.)
>    3. Re: Lockdown adaX numbers to allow booting ? (Nenhum_de_Nos)
>    4. New driver for Asus Xonar DG/DGX soundcards now available
>       (Alexei Palyutin)
>    5. assertion error in ZFS (Piotr Kubaj)
>    6. Re: Lockdown adaX numbers to allow booting ? (Kurt Jaeger)
>    7. Re: Lockdown adaX numbers to allow booting ? (Kurt Jaeger)
>    8. SVN r353480 now mandates kernel option VIMAGE (Michael Butler)
>    9. Re: SVN r353480 now mandates kernel option VIMAGE (Michael Tuexen)
>   10. Re: SVN r353480 now mandates kernel option VIMAGE (Michael Tuexen)
>   11. Re: Lockdown adaX numbers to allow booting ? (O'Connor, Daniel)
>   12. Re: Lockdown adaX numbers to allow booting ? (O'Connor, Daniel)
>   13. [2 WEEKS LEFT REMINDER] Call for 2019Q3 quarterly status
>       reports (salvadore_at_FreeBSD.org)
>   14. Re: Lockdown adaX numbers to allow booting ? (Kurt Jaeger)
>   15. Re: Lockdown adaX numbers to allow booting ? (O'Connor, Daniel)
>
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
Received on Mon Oct 14 2019 - 11:44:47 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:22 UTC