On Thu, Apr 8, 2021 at 8:46 PM Kurt Jaeger wrote:
> Hi!
>
> I have a new laptop (Lenovo P14s), installed freebsd 13.0-RC5 on it
> with ZFS, geli encryption.
>
> If I cold-start the laptop, the first boot will crash before
> going multi-user and reboot, and the next boo
Hi!
I have a new laptop (Lenovo P14s), installed freebsd 13.0-RC5 on it
with ZFS, geli encryption.
If I cold-start the laptop, the first boot will crash before
going multi-user and reboot, and the next boot will be fine.
I activated /var/log/kern for kern.*, but the crash happens
so early that
Hi!
Long story short: looks like r360843 can lead to kernel panic at disk
initialization in 11.4-STABLE (12-STABLE shall be affected too, however,
this is not tested).
Long story longer: after routine upgrade from 11.2-STABLE to 11.4-STABLE,
host panics during disc initialization. Hardware: De
Hi all,
I was forced to upgrade 11.4 -> 12.2, as QT5 reqires openssl 1.1.1.
I did a full rebuild from source as of this:
12.2-RC2 FreeBSD 12.2-RC2 #11 r366648M#N1055:1078
(local patches applied - some published via sendbug 10 or 12 years ago)
I did a full rebuild of ALL ports from source, a
On 9/30/20 10:35 PM, Jeremy wrote:
So I rebuilt both virtualbox-ose and virtualbox-ose-kmod and the driver
successfully loaded in my system updated to beta 3, but I haven't tested
virtualbox yet to see if it actually works, although I have no reason to
believe it won't.
I suppose the issue reall
So I rebuilt both virtualbox-ose and virtualbox-ose-kmod and the driver
successfully loaded in my system updated to beta 3, but I haven't tested
virtualbox yet to see if it actually works, although I have no reason to
believe it won't.
I suppose the issue really is if you forget to disable loading
I am also experiencing this problem after updating to beta 3. It is a hard
lockup and no keys will respond. It requires the computer to be turned off
via the power button. But it definitely looks like an issue with the
virtualbox driver. Normally I disable the drivers from loading before I do
an up
On 20.09.20 16:29, xto...@hotmail.com wrote:
Volodymyr Kostyrko wrote:
Hello.
I'm currently using 12.2-STABLE r365916. After update the host started
crashing immediately after loading VirtualBox modules. Does anyone
else experience similar behavior?
Tried rebuilding vbox kernel modules?
W
Volodymyr Kostyrko wrote:
Hello.
I'm currently using 12.2-STABLE r365916. After update the host started
crashing immediately after loading VirtualBox modules. Does anyone else
experience similar behavior?
Tried rebuilding vbox kernel modules?
___
f
Hello.
I'm currently using 12.2-STABLE r365916. After update the host started
crashing immediately after loading VirtualBox modules. Does anyone else
experience similar behavior?
Thanks in advance.
--
Sphinx of black quartz judge my vow.
___
freebs
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
On Aug 24, 2020, at 11:30 AM, Mason Loring Bliss wrote:
>
> On Mon, Aug 24, 2020 at 09:46:26AM +0200, Nikos Vassiliadis wrote:
>
>> After updating to 12-STABLE I am getting kernel panics when re-starting
>> the jail service. Here's a backtrace:
>
> This is a known issue. There are a couple rele
On Mon, Aug 24, 2020 at 09:46:26AM +0200, Nikos Vassiliadis wrote:
> After updating to 12-STABLE I am getting kernel panics when re-starting
> the jail service. Here's a backtrace:
This is a known issue. There are a couple relevant bugs:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=2383
Hi,
After updating to 12-STABLE I am getting kernel panics when re-starting the
jail service. Here's a backtrace:
#6 0x8108696f in trap_pfault (frame=0xfe00216682c0,
usermode=, signo=, ucode=)
at /usr/src/sys/amd64/amd64/trap.c:739
#7 0x81085fb6 in trap (frame=0xfe
Hi,
I’m getting the following crash during startup. It seems strongswan is setting
a reqid.
Commit r363430 is on if_bridge. The IPSec interfaces are not bridged at all, so
I’m clueless to why this crash relates to this commit. The only commonality is
that the crash is Epoch related and the
On 6/2/20, Donald Wilde wrote:
> On 6/2/20, Donald Wilde wrote:
>> On 6/2/20, Trond Endrestøl wrote:
>>> On Tue, 2 Jun 2020 05:06-0700, Donald Wilde wrote:
[snipped]
>>> I ran make -C /usr/ports/print/tex-dvipsk all-depends-list on one of
>>> my well-maintained systems, and graphviz didn't show
On 6/2/20, Donald Wilde wrote:
> On 6/2/20, Trond Endrestøl wrote:
>> On Tue, 2 Jun 2020 05:06-0700, Donald Wilde wrote:
>>
> [snipped]
>>> I am willing to live without an updated ports tree, but how can I
>>> resolve the issue with the Synth repo so I can use 'pkg install'? I
>>> only need to in
Interspersed.
On 6/2/20, Trond Endrestøl wrote:
> On Tue, 2 Jun 2020 05:06-0700, Donald Wilde wrote:
>
[snipped]
>> I am willing to live without an updated ports tree, but how can I
>> resolve the issue with the Synth repo so I can use 'pkg install'? I
>> only need to install a few dozen ports fr
On Tue, 2 Jun 2020 05:06-0700, Donald Wilde wrote:
>
> Updating FreeBSD repository catalogue...
> FreeBSD repository is up to date.
> Updating Synth repository catalogue...
> pkg: file:///var/synth/live_packages/meta.txz: No such file or directory
> repository Synth has no meta file, using defaul
sorribouthat! on the lack of a Subject: line in my previous post! My bad.
On 6/1/20, Donald Wilde wrote:
> Hello, my good friends -
>
> I hope all are well!
>
> I did a synth update from my root user on my 12-STABLE system, with
> the following results:
I pulled down the source of the World agai
On 5/24/20, Donald Wilde wrote:
> I will, guys, thanks for the pointer. I didn't look hard enough! >8^O
>
Successful. That (contrib) next to the filter should have been a
bright red flag for me, but I'd forgotten.
Thanks, Beasties!
--
Don Wilde
**
I will, guys, thanks for the pointer. I didn't look hard enough! >8^O
--
Don Wilde
* What is the Internet of Things but a system *
* of systems including humans? *
___
On 24 May 2020, at 12:17, Donald Wilde wrote:
>
> Let's see if I can report this adequately enough. The macro-task I am
> attempting to accomplish is to update my (English) FreeBSD Handbook to
> 12-STABLE from the ports collection asextracted 2020-05-23.
>
> The actual failure in creating libunb
Hello, all -
Let's see if I can report this adequately enough. The macro-task I am
attempting to accomplish is to update my (English) FreeBSD Handbook to
12-STABLE from the ports collection asextracted 2020-05-23.
The actual failure in creating libunbound.so is that the command to
compile iterato
y after a successful boot,
>> the screen goes blank and the system reboots after a while; on reboot
>> a dump is found and written to /var/crash.
>> Kernel config is GENERIC with added options WITNESS and WITNESS_SKIPSPIN
>> CPU is a Celeron 2955U (Haswell class) and the
/var/crash.
Kernel config is GENERIC with added options WITNESS and WITNESS_SKIPSPIN
CPU is a Celeron 2955U (Haswell class) and the graphics controller
identifies as 'Haswell-ULT Integrated Graphics Controller' in pciconf.
Any suggestions how to proceed from here? Any usefull informat
screen
goes blank upon loading the module and does not react any more, powercycle
is required. If I load the the module manually after a successful boot,
the screen goes blank and the system reboots after a while; on reboot
a dump is found and written to /var/crash.
Kernel config is GENERIC with added
Hi all,
I run a following server:
- Supermicro 6047R-E1R36L
- 96 GB RAM
- 1x INTEL CPU E5-2640 v2 @ 2.00GHz
- FreeBSD 10.3-RELEASE-p11
Drive for OS:
- HW RAID1: 2x KINGSTON SV300S37A120G
zpool1:
- 9x WD RED 4TB ; 9x HGST HUS726040ALA610 @ raidz2
- log: mirrored Intel 730 SSD
- cache: single In
I got 2 crashes today after I upgrade eto 12.1-BETA1:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240837
Does someone else have same crashes?
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To
Please try to remove 'WITHOUT_REPRODUCIBLE_BUILD' option and recompile the
kernel to see if it will be stable in your context. The modern FreeBSD
releses (12.0 for example) is with reproducible build enabled now. As quck
check, tell uname -a and you will give the following output:
FreeBSD xxx.yo
> On 24 Sep 2019, at 12:43, Igor V. Ruzanov wrote:
>
> Is your kernel custom and you were compile it? If yes, could you please
> send kernel config to here?
The kernel is from 12.0-STABLE r351639.
I use the GENERIC config to compile the kernel but with custom src.conf:
cat /etc/src.conf
W
Is your kernel custom and you were compile it? If yes, could you please
send kernel config to here?
|Id Refs AddressSize Name
| 1 12 0x8020 2446480 kernel
| 21 0x82648000281e0 geom_mirror.ko
| 31 0x82a21000 88e8 tmpfs.ko
| 41 0xff
Id Refs AddressSize Name
1 12 0x8020 2446480 kernel
21 0x82648000281e0 geom_mirror.ko
31 0x82a21000 88e8 tmpfs.ko
41 0x82a2a000258f8 ipfw.ko
51 0x82a5 acf mac_ntpd.ko
61 0x82a51000
What kernel modules do you load with this kernel? (show the list via
kldstat)
|Randomly every few weeks / months one of the servers I manage gets a panic. It
doesn't happen on the same server every time.
|
|I run FreeBSD stable compiled on 2 September 2019 but it did happen with
previous versi
Randomly every few weeks / months one of the servers I manage gets a panic. It
doesn't happen on the same server every time.
I run FreeBSD stable compiled on 2 September 2019 but it did happen with
previous versions too and if I remember correctly it did happen with FreeBSD 11
too.
I don't hav
I didn't have dumpdev enabled.
I now add it to a test server:
dumpdev="AUTO"
then I reboot it and then I run:
sysctl debug.kdb.panic=1
After it came back online it doesn't have the dump in /var/crash
Do I miss something?
> On 11 Sep 2019, at 11:29, Li-Wen Hsu wro
ow nothing.
>
> Any idea if a commit between these 2 versions can cause it?
Any chance if you can obtain the crash dump?
https://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html#kerneldebug-obtain
___
freebsd-stable@
Few hours ago I upgrade FreeBSD-12.0-STABLE (revision 351639) to
FreeBSD-12.0-STABLE (revision 352091).
After running the new version for few hours 2 of my servers crashed and
auto-reboot.
Logs show nothing.
Any idea if a commit between these 2 versions can cause it?
__
Hi Konstantin,
BINGO! 110 out of 100 possible points :-)
Yes, that fixed the problem:
root@blnn719x - ~
2048 # uname -a
FreeBSD blnn719x.ad001.siemens.net 11.3-PRERELEASE FreeBSD
11.3-PRERELEASE #2 r349719M: Thu Jul 11 09:12:21 CEST 2019
r...@blnn719x.ad001.siemens.net:/usr/obj/usr/src/sys/BL
On Wed, Jul 10, 2019 at 03:02:40PM +0200, Schuendehuette, Matthias (LDA IT PLM)
wrote:
> Sorry, wrong link... :-(
>
> See the verbose boot messages here...
>
> https://www.dropbox.com/sh/buzxekimo2h2r67/AADpUvLndhm2SHa5t9s9Ckksa?dl=0
>
> ...in file "Boot_verbose.jpg"
Can you try the following
and
the kernel which fails to boot.
With best regards and have a nice weekend
Matthias Schuendehuette
-Ursprüngliche Nachricht-
Von: Konstantin Belousov Gesendet: Mittwoch, 3.
Juli 2019 15:55
An: Schuendehuette, Matthias (LDA IT
PLM)
Cc: 'freebsd-stable@freebsd.org';
e boot enabled, for your machine, and
the kernel which fails to boot.
With best regards and have a nice weekend
Matthias Schuendehuette
-Ursprüngliche Nachricht-
Von: Konstantin Belousov
Gesendet: Mittwoch, 3. Juli 2019 15:55
An: Schuendehuette, Matthias (LDA IT PLM)
Cc: '
your machine, and
the kernel which fails to boot.
>
>
>
> With best regards and have a nice weekend
>
> Matthias Schuendehuette
>
>
>
>
> -Ursprüngliche Nachricht-
> Von: Konstantin Belousov
> Gesendet: Mittwoch, 3. Juli 2019 15:55
> An: Schuen
e
-Ursprüngliche Nachricht-
Von: Konstantin Belousov
Gesendet: Mittwoch, 3. Juli 2019 15:55
An: Schuendehuette, Matthias (LDA IT PLM)
Cc: 'freebsd-stable@freebsd.org' ; Osipov, Michael
(LDA IT PLM)
Betreff: Re: GENERIC crash 11.3-PRERELEASE (i386)
On Wed, Jul 03, 2019 at
NULL);"
has been inserted into 'sys/x86/x86/cpu_machdep.c'
That's still the case for 'r349719'.
Did you misunderstand the "+" and "-" signs below?
"+" was the *working* copy, that is 'r348361'
"-" was the
On Wed, Jul 03, 2019 at 08:42:21AM +, Schuendehuette, Matthias wrote:
> Hello Konstantin,
>
> I did some research regarding the kernel crash with the following results>
>
> 1) Last working kernel is:
>
> "FreeBSD 11.3-BETA1 (BLNN719X) #8 r348361: Wed
Hello Konstantin,
I did some research regarding the kernel crash with the following results>
1) Last working kernel is:
"FreeBSD 11.3-BETA1 (BLNN719X) #8 r348361: Wed Jul 3 09:30:17 CEST
2019"
1a) DDB-Backtrace of the crashing kernel r348362 can be seen on "Boot_
Nachricht-
Von: Konstantin Belousov
Gesendet: Donnerstag, 27. Juni 2019 21:00
An: Schuendehuette, Matthias (LDA IT PLM)
Cc: 'freebsd-stable@freebsd.org'
Betreff: Re: GENERIC crash 11.3-PRERELEASE (i386)
On Thu, Jun 27, 2019 at 07:11:40AM +, Schuendehuette, Matthias wrote:
> Hi,
On Thu, Jun 27, 2019 at 07:11:40AM +, Schuendehuette, Matthias wrote:
> Hi,
>
> the missing attachments can be found here now:
>
> https://www.dropbox.com/sh/buzxekimo2h2r67/AADpUvLndhm2SHa5t9s9Ckksa?dl=0
>
So your AP (Application Processor) seems to get fault, most likely in the
trap handle
Hi,
the missing attachments can be found here now:
https://www.dropbox.com/sh/buzxekimo2h2r67/AADpUvLndhm2SHa5t9s9Ckksa?dl=0
with best regards
Matthias Schündehütte
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listi
ap 12 with interrupts disabled".
Since there is no crash dump I attach some screen shots of the boot messages.
I hope this does not violate the mailing list rules...
The GENERIC config-file is:
# $FreeBSD: stable/11/sys/i386/conf/GENERIC 323770 2017-09-19 16:51:51Z
jpaetzel $
The last working kernel
Hello,
for some days now the GENERIC kernel of 11.3-PRERELEASE (i386) crashes on my
ProLiant DL380 G5 server.
Main error message is "kernel trap 12 with interrupts disabled".
Since there is no crash dump I attach some screen shots of the boot messages.
I hope this does not violate t
Hi,
when creating partitions directly adjacent without a safety free space
between them, the kernel may crash.
Does anybody know how big that free space needs to be?
How I found out (and how to reproduce the crash):
https://forums.freebsd.org/threads/create-degraded-raid-5-with-2-disks-on
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227654
Kubilay Kocak changed:
What|Removed |Added
Severity|Affects Only Me |Affects Some People
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227654
--- Comment #5 from Eugene Grosbein ---
I've added additional printf's to sys/net/if_ethersubr.c and found that it
panices within ether_output_frame() function.
I've added this just before PFIL_HOOKED(&V_link_pfil_hook) check:
if (ifp->if
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227654
Eugene Grosbein changed:
What|Removed |Added
Version|11.1-STABLE |CURRENT
--
You are receiving th
It generates nice crashdump and reboots.
I've uploaded kernel.debug (stock one from 12.0-BETA1/i386 installation image,
18M compressed) and vmcore.0.xz (9.2MB compressed) here:
http://www.grosbein.net/freebsd/crash/20181021/
Here comes kgdb script:
Script started on Sun Oct 21 02:31:58
On Fri, Oct 19, 2018 at 01:10:15PM +0200, Sebastian Wojtczak wrote:
> Hi,
>
> I would like to report a kernel crash while dd on ssd drive.
>
> Just found that my PC crashed several times during below command:
> dd if=/dev/ada2 of=file_name bs=10m.
>
> I was trying to m
Am 2018-10-19 13:10, schrieb Sebastian Wojtczak:
Hi,
I would like to report a kernel crash while dd on ssd drive.
Reducing ARC may help:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231296
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231794
See here:
https://bugs.freebsd.org
Hi,
I would like to report a kernel crash while dd on ssd drive.
Just found that my PC crashed several times during below command:
dd if=/dev/ada2 of=file_name bs=10m.
I was trying to make an image from my ssd drive. Once dump file hit size
41G or 52G kernel crashes and reboot the system.
Oct
. Thanks.
On 9/6/2018 12:49 PM, Samuel Chow wrote:
I would like to report a kernel crash while tearing down a
VIMAGE-based jail.This can be reproduced consistently. Thanks.
---
Fatal trap 12: page fault while in kernel mode
cpuid = 4; apic id = 08
fault virtual address = 0xa8
fault code
I would like to report a kernel crash while tearing down a VIMAGE-based
jail.This can be reproduced consistently. Thanks.
---
Fatal trap 12: page fault while in kernel mode
cpuid = 4; apic id = 08
fault virtual address = 0xa8
fault code = supervisor read data, page not present
The problem is that, on crash the kernel drops crash messages on the tty0
console and reboots immediately, making it impossible to read them. (they
are not saved in /var/log/console.log for some reason).
According to
https://lists.freebsd.org/pipermail/freebsd-questions/2009-July/202210.html,
if
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227654
Eugene Grosbein changed:
What|Removed |Added
Summary|[panic] repeatable crash|[panic] repeatable crash
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227654
--- Comment #2 from Eugene Grosbein ---
Created attachment 192690
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=192690&action=edit
debugging patch for single user only
Forgot to note that my kernel has VIMAGE too.
I've reprodu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227654
--- Comment #1 from Eugene Grosbein ---
$ addr2line -e kernel.debug -i -f -C 806fe6ac
ether_output_frame
/data2/src/sys/net/if_ethersubr.c:449
ether_output
/data2/src/sys/net/if_ethersubr.c:435
(kgdb) l /data2/src/sys/net/if_ethe
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227654
Bug ID: 227654
Summary: [panic] repeatable crash with IPv6+lagg+vlan+em
Product: Base System
Version: 11.1-STABLE
Hardware: Any
OS: Any
Status: New
> On 17 Apr 2018, at 9:24 AM, Kyle Evans wrote:
>
> Can you set vm.pmap.pti=0 at the loader prompt and see if
> this affects your situation at all, just to rule that out?
I redid everything from the start, did set vm.pmap.pti=0, and it behaves
exactly the same: kernel panic.
Thanks for your
On Tue, Apr 17, 2018 at 10:18 AM, Dan Allen wrote:
>
>
>> On 17 Apr 2018, at 8:49 AM, Kyle Evans wrote:
>>
>> As "the guy most likely to have broken boot code in stable," may I ask
>> what leads you specifically to amd64 boot code? Mostly curious if
>> there's something beyond "i386 works well" t
> On 17 Apr 2018, at 8:49 AM, Kyle Evans wrote:
>
> As "the guy most likely to have broken boot code in stable," may I ask
> what leads you specifically to amd64 boot code? Mostly curious if
> there's something beyond "i386 works well" that lead you to this
> conclusion.
It is partly just a hu
s/ISO-IMAGES/11.1/FreeBSD-11.1-STABLE-amd64-20180329-r331742-disc1.iso
>
> I can run pkg install and begin adding stuff to the system and life is good.
>
> BUT
>
> This snapshot dated 20180408, after doing a fresh install, will crash when
> running pkg install:
>
>
>
tuff to the system and life is good.
BUT
This snapshot dated 20180408, after doing a fresh install, will crash when
running pkg install:
https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/11.1/FreeBSD-11.1-STABLE-amd64-20180408-r332308-disc1.iso
It crashes about 90% of the way through upda
bin.com/niXrjF0D
Please refer to full output from crash above.
This morning our IMAP server decided to go belly up. I could not remote in, and
the machine would not respond to any pings.
Checking the physical console I had the following worrisome messages on screen:
• g_vfs_done():da1p1[READ(offs
On 2/6/2017 15:01, Shawn Bakhtiar wrote:
> Hi all!
>
> http://pastebin.com/niXrjF0D
>
> Please refer to full output from crash above.
>
> This morning our IMAP server decided to go belly up. I could not remote in,
> and the machine would not respond to any pings.
>
>
Hi all!
http://pastebin.com/niXrjF0D
Please refer to full output from crash above.
This morning our IMAP server decided to go belly up. I could not remote in, and
the machine would not respond to any pings.
Checking the physical console I had the following worrisome messages on screen
d Sandisk SSDs,
so I was told to try to disable TRIM and see what happens (thanks a lot
by the way, that did it). But changing the
vfs.zfs.vdev.bio_delete_disable on the fly can lead to the system crash
with the probability of 50%. Is it just me or is this already known ? If
it's known, why
Hi.
Recently I've encountered the issue with "slow TRIM" and Sandisk SSDs,
so I was told to try to disable TRIM and see what happens (thanks a lot
by the way, that did it). But changing the
vfs.zfs.vdev.bio_delete_disable on the fly can lead to the system crash
with the probabilit
On Sat, 3 Sep 2016 15:56:51 +0100, Steven Hartland wrote:
> That file is not accessible
>
> On 03/09/2016 10:51, Volodymyr Kostyrko wrote:
> > Hi all.
> >
> > Got one host without keyboard so can't dump it.
> >
> > Screenshot: http://limb0.b1t.name/incoming/IMG_20160903_120545.jpg
> >
That file is not accessible
On 03/09/2016 10:51, Volodymyr Kostyrko wrote:
Hi all.
Got one host without keyboard so can't dump it.
Screenshot: http://limb0.b1t.name/incoming/IMG_20160903_120545.jpg
This is MINIMAL kernel with minor additions.
___
Hi,
I've the same issue here with my ZFS server. I've updated from 10.3-STABLE
to 11-PRERELEASE. Then after some time my server just crash.
Then i tried to update again using another svn server. After many tries
(because my server has been crashed all the time) i got RC2. But same i
Hi all.
Got one host without keyboard so can't dump it.
Screenshot: http://limb0.b1t.name/incoming/IMG_20160903_120545.jpg
This is MINIMAL kernel with minor additions.
--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd.org mailing lis
I just upgraded a machine from 10-STABLE to FreeBSD 11, and the machine
seems to crash frequently if flowtable is enabled. Other machines I have
using the identical kernel does not seem to be affected, and the same
hardward on the old 10-STABLE branch was quick stable. Interfaces on this
I have twice had my laptop crash when I inadvertently had a Windows 7 VM
running at the time of the suspend.
I can certainly understand how this could happen, but should it? It's way
too easy to forget to "Save the machine state" before "zzz" and it sure is
annoying.
I a
(00:12)
boot time Fri Feb 5 20:53
[--redacted--] pts/1[--redacted--] Fri Feb 5 04:59 - crash (15:54)
[--redacted--] pts/0[--redacted--] Fri Feb 5 04:59 - 04:59 (00:00)
boot time Fri Feb 5 04:41
boot time
[Sorry for the previous unintended test message I sent to the list].
Hi. I had a bizarre X server crash after updating the packages on my KVM
guest running 10.1-RELEASE-p9 (Debian-8 host). X server with VESA driver
crashes with signal 4 (illegal instruction) when console is set to 'sc
t; replication may be tied to multiple CPUs and/or the allocation of resources
> by an HT CPU core.
>
>
> On Mon, Sep 2, 2013 at 3:53 AM, Zaphod Beeblebrox wrote:
>
>> The first one (kern.geom.transient_map_retries) causes the system to
>> wedge.
>>
>> The secon
t_map_retries) causes the system to wedge.
>
> The second one (default is 180, I doubled to 360) causes the system to
> crash but not dump.
>
> So... neither fixes the problem.
>
>
> On Sat, Aug 31, 2013 at 5:27 AM, Edward Tomasz Napierała <
> tr...@freebsd.org&g
The first one (kern.geom.transient_map_retries) causes the system to wedge.
The second one (default is 180, I doubled to 360) causes the system to
crash but not dump.
So... neither fixes the problem.
On Sat, Aug 31, 2013 at 5:27 AM, Edward Tomasz Napierała
wrote:
> Wiadomość napisana pr
Wiadomość napisana przez Zaphod Beeblebrox w dniu 31 sie
2013, o godz. 00:49:
> Because someone said that there would be no logging of unerlying ATA errors
> without verbose, I rebooted with verbose and tried the same make -j4 again...
> and here is the relatively similar core.txt.5
>
> https:
Because someone said that there would be no logging of unerlying ATA errors
without verbose, I rebooted with verbose and tried the same make -j4
again... and here is the relatively similar core.txt.5
https://uk.eicat.ca/owncloud/public.php?service=files&t=d99648ef5876b91c5957148445e60c87
Looking
My bad. New link for the core.txt.4:
https://uk.eicat.ca/owncloud/public.php?service=files&t=f471e5afae483342cd20dc390e9c2dd7
On Fri, Aug 30, 2013 at 4:51 PM, Ian Lepore wrote:
> On Fri, 2013-08-30 at 21:50 +0200, Edward Tomasz Napierała wrote:
> > Wiadomość napisana przez Zaphod Beeblebrox
On Fri, 2013-08-30 at 21:50 +0200, Edward Tomasz Napierała wrote:
> Wiadomość napisana przez Zaphod Beeblebrox w dniu 29 sie
> 2013, o godz. 23:35:
> > So I have a system running:
> >
> > FreeBSD walk.dclg.ca 9.2-RC3 FreeBSD 9.2-RC3 # r254952: Wed Aug 28 03:02:55
> > EDT 2013 r...@walk.dclg.
Wiadomość napisana przez Zaphod Beeblebrox w dniu 29 sie
2013, o godz. 23:35:
> So I have a system running:
>
> FreeBSD walk.dclg.ca 9.2-RC3 FreeBSD 9.2-RC3 # r254952: Wed Aug 28 03:02:55
> EDT 2013 r...@walk.dclg.ca:/usr/obj/usr/src/sys/STRIKE i386
>
> and it has two 2T SATA disks. To ke
I was going to mention that I ran fsck _twice_, but I forgot. Then when
that didn't fix it, I dumped the filesystem, newfs'd it and restored it.
Then I fsck'd it for good measure.
This particular crash immediately follows that treatment.
I can do this in a loop:
boot -> ma
On Thu, Aug 29, 2013 at 4:35 PM, Zaphod Beeblebrox wrote:
> So I have a system running:
>
> FreeBSD walk.dclg.ca 9.2-RC3 FreeBSD 9.2-RC3 # r254952: Wed Aug 28
> 03:02:55
> EDT 2013 r...@walk.dclg.ca:/usr/obj/usr/src/sys/STRIKE i386
>
> and it has two 2T SATA disks. To keep this post short, t
So I have a system running:
FreeBSD walk.dclg.ca 9.2-RC3 FreeBSD 9.2-RC3 # r254952: Wed Aug 28 03:02:55
EDT 2013 r...@walk.dclg.ca:/usr/obj/usr/src/sys/STRIKE i386
and it has two 2T SATA disks. To keep this post short, the crash.txt is
here.
https://uk.eicat.ca/owncloud/public.php?service=
intermittent crash reports from abrt on the KVM host. Has
anyone else encountered problems using pf under KVM virtualisation?
A typical crash report from the host goes like this:
=
abrt_version: 2.0.8
cmdline:ro root=/dev/mapper/chumby-root rd_LVM_LV=chumby/root
rd_NO_LUKS LANG
14.06.2013 15:51, Dr Josef Karthauser:
On 14 Jun 2013, at 12:00, Volodymyr Kostyrko wrote:
14.06.2013 12:55, Dr Josef Karthauser:
Hi, I'm a bit at the end of my tether.
p.s. the config, btw, is a ZFS mirror on two ad devices. It's got a ZFS root
file system.
If you are fairly sure about
On 14 Jun 2013, at 12:00, Volodymyr Kostyrko wrote:
> 14.06.2013 12:55, Dr Josef Karthauser:
>> Hi, I'm a bit at the end of my tether.
>> p.s. the config, btw, is a ZFS mirror on two ad devices. It's got a ZFS root
>> file system.
>
> If you are fairly sure about your devices you can:
>
> 1.
14.06.2013 12:55, Dr Josef Karthauser:
Hi, I'm a bit at the end of my tether.
We had a ZFS panic last night on a machine that hosts all my mail and web; it
was rebooted and it now panics mounting the ZFS root filesystem.
The call stack info is:
solaris assert: ss == NULL, file:
/usr/
1 - 100 of 755 matches
Mail list logo
