https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209099
Bug ID: 209099
Summary: ata2: already running! panic: bad link elm
0xfffff80003b7e6a0 prev->next != elm
Product: Base System
Version: 11.0-CURRENT
Hardware: amd64
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: freebsd-b...@freebsd.org
Reporter: furstenwe...@gmail.com
CC: freebsd-amd64@FreeBSD.org
CC: freebsd-amd64@FreeBSD.org
Created attachment 169760
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=169760&action=edit
Image of Screen showing panic.
I have been battling a bug for about 4 months now. This has spanned
10.2-release, 10.3-release, 11-current. If I could get some assistance here in
how to trace this problem I would gladly provide information.
Known Good State: FreeBSD 10.2-11-current, works flawlessly.
Bad State: Install py27-salt, run minions and or master.
Note: tested only on my hardware, but reproducible.
Steps to reproduce, run in ide compatibility mode or hardware that cannot do
AHCI.
Install FreeBSD 10.2-11-Current
Install py27-salt
run 'salt machine test.ping'
Machine will then report.
run 'salt machine state.apply test=True'
Everything reports properly
run 'salt machine state.apply'
Expected behavior is report back of success, observed behavior is kernel panic.
I get a very limited window that I can do any input to the machine. At this
time I cannot boot past starting jails as salt minion loads previously. I
cannot verify who this impacts, I cannot verify the extent of it as I have read
zero data regarding this specific to salt. I can replicate this, I can
reproduce it across multiple machines.
Changing one machine from AHCI to IDE will induce this as well, that machine is
now stable for weeks without issue. Sadly the two machines that are causing the
headache have no allocation for this due to age. I have tried 2 different SSD's
and 2 different spinners. The secondary machine does not have py27-salt
installed, months without panic. Install py27-salt and it starts panicking.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
freebsd-amd64@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-amd64
To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
