In closing, Gleb has solved the problem with attached patch.
Many thanks to everyone involved and to Gleb for finding out what's
wrong and fixing it.
p.
fwd_tag.diff
Description: Binary data
___
freebsd-stable@freebsd.org mailing list
Hi list,
After an upgrade from 8.3 to 9.1-STABLE, this machine started
crashing.
It's a GENERIC kernel with following changes:
options DUMMYNET
options IPFIREWALL
options IPFIREWALL_FORWARD
options IPFIREWALL_DEFAULT_TO_ACCEPT
options HZ=1000
Hi,
1. Do you have a full crash dump?
Unfortunately no. This is everything that got logged.
2. Are world and kernel in sync?
I believe so. Is there a fool-proof reliable way to check this?
It's crashing frequently, so I can make changes to get things logged
properly, if given pointers.
p.
Hi,
Hey Pawel, please force fsck of the filesystem (-f), I had that issue
recently and the system was crashing because of that (su-journal did not
show fs corruption). Fsck -f showed and fixed inconsistencies and now its
fine.
This is a ZFS-only machine, including root. There are no
Hi,
If you have swap on a raw disk then adding the following to /etc/rc.conf
is usually sufficent
dumpdev=AUTO
If you don't reboot then run:
/etc/rc.d/dumpon start
Thanks. Dumps will be done to gmirror; I switched balancing to prefer
for the time being. Everything's setup, so hopefully
Here's more info, including backtrace:
Fatal trap 12: page fault while in kernel mode
cpuid = 3; apic id = 03
fault virtual address = 0x0
fault code = supervisor read data, page not present
instruction pointer = 0x20:0x80956c73
stack pointer =
Hi Steven,
Did you get a dump from this one if so /var/crash/core.txt.X
(X = number) would be of help.
Yes, above is from this file. It's quite large and contains sensitive
information, so I'm not comfortable in uploading whole file. Are you
interested in a particular section?
p.
Hi,
The gdb block at the top as that will help identify where in the code
your panic is occurring. The kdb block you posted only lists offsets where
as gdb lists lines.
Steven,
Please see http://pastie.org/5506669
Lawrence,
0x80a7c1af is in tcp_input
Witam,
You can also list the offending IP:
list *0x80956c73
Excuse my ignorance, but how does that list an IP address?
(gdb) list *0x80956c73
0x80956c73 is in m_tag_delete (mbuf.h:1047).
1042 */
1043static __inline void
1044m_tag_unlink(struct mbuf *m,
Hi Matthew,
NO_OPENSSL, no -DHAVE_CRYPTO. No -DHAVE_CRYPTO, no #include
hast_checksum.h.
So was NO_OPENSSL deprecated or something?
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe,
Hi Jeremy,
So was NO_OPENSSL deprecated or something?
I think he's implying that hast indirectly relies upon OpenSSL.
I would classify this as a bug/oversight that should be properly dealt
with via an #error statement or similar -- the current result (what
you've reported) is not
Hi list,
=== sbin/hastctl (all)
cc -O2 -pipe -I/usr/src/sbin/hastctl/../hastd -DINET -DINET6 -DYY_NO_UNPUT
-std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W
-Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith
-Wreturn-type -Wcast-qual
Hi Jeremy,
What tag are you following / FreeBSD version are you using? I ask
because you have a bunch of variables in make.conf that probably need to
go into /etc/src.conf.
It's RELENG_8. 8-STABLE. Yeah, this make.conf kept growing in stuff
since like FBSD4 :)
I just rebuild world and
Hi Doug,
Traditional solution for similar problems is to clean out your /usr/obj/
and try again.
I always do that. If build fails, I delete /usr/obj and try again
without -j.
___
freebsd-stable@freebsd.org mailing list
Daniel Kalchev wrote:
The only real trouble with USB stisks is that some motherboards
behave unpredictable as to boot order, but this is improving.
Why would you care about that?
When running mirrored setups with ZFS on root, I'm using GPT scheme
and every drive has boot partition, swap
Hi,
P.S. -- What's BMC stand for?
Baseband Management Controller. It's the separate NIC (sometimes it's
piggy-backed on a NIC) used for remote management of motherboards.
Usually includes IPMI support. Depending on the motherboard, it may
even include support for keyboard/video/mouse
Hi Luigi,
i recently bought two motherboards with Intel AMT support,
a remote management tool which among other things implements
Serial Over Lan (SOL) -- which seems to be accessible
via TCP port 16994
I have enabled the feature in the bios and built a client
(amtterm, see
Hello list,
I'm observing recurring crashes with dummynet on 8.1-RELEASE.
Abnormal things being done on the system are:
/sbin/ipfw pipe list pipestats-`date +%Y%m%d-%H%M%S` being done
every minute.
There are over 2000 pipes in the system.
Anyway, to the point: is there any resource I could read
Easiest way to create sparse eg 20 GB assuming test.img doesn't exist
already
No no no. Easiest way to do what you want to do:
mdconfig -a -t malloc -s 3t -u 0
mdconfig -a -t malloc -s 3t -u 1
Just make sure to offline and delete mds ASAP, unless you have 6TB of
RAM waiting to be filled ;) -
I do not think I can adjust the existing zpool on the fly. I think I
need to copy everything elsewhere (i.e the 2 empty drives). Then start
the new zpool from scratch.
You can, and you should (for educational purposes if not for fun :),
unless you wish to change raidz1 to raidz2. Replace,
So... the smaller size won't mess things up...
If by smaller size you mean smaller size of existing
drives/partitions, then growing zpools by replacing smaller vdevs
with larger ones is supported and works. What isn't supported is
basically everything else:
- you can't change number of raid
Hi guys,
I second what others have said - crap.
But there could be some hope, not sure.
Can you check what is the actual size used by the pool on the disk?
It should be somewhere in zdb -C output (asize?).
If I remember correctly, that actual size should be a multiple of some rather
large
22 matches
Mail list logo
