Re: very stupid mistake: a part of /usr is deleted

[c0re]

But if Zara Kanaeva use freebsd-update that method wont fit her needs.

2010/9/15 Bartosz Stec :
>
> This is a solution I would recommend (if time isn't the problem), first csup
> fresh 8.X sources, rebuild, upgrade, and as a result you will get more than
> missing files, but 8.1-RELASE + STABLE patches :).
> --
> Bartosz Stec
> ___
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: freebsd-update with non-GENERIC kerrnel

[c0re]

freebsd-update made for only GENERIC kerndel due to binary diff patches.
After you rebuild world and kernel you'll be not able to apply binary
patches.

2010/6/1 Olaf Seibert 

> I find the way freebsd-update handles a system that runs a non-GENERIC
> kernel less than helpful.
>
> It is doing this:
>
> | fourquid.3:~$ sudo freebsd-update upgrade -r 8.1-BETA1
> | Password:
> | Looking up update.FreeBSD.org mirrors... 3 mirrors found.
> | Fetching metadata signature for 8.0-RELEASE from update5.FreeBSD.org...
> done.
> | Fetching metadata index... done.
> | Fetching 2 metadata patches.. done.
> | Applying metadata patches... done.
> | Inspecting system... done.
> |
> | WARNING: This system is running a "fourquid" kernel, which is not a
> | kernel configuration distributed as part of FreeBSD 8.0-RELEASE.
> | This kernel will not be updated: you MUST update the kernel manually
> | before running "/usr/sbin/freebsd-update install".
> |
> | The following components of FreeBSD seem to be installed:
> | src/base src/bin src/cddl src/contrib src/crypto src/etc src/games
> | src/gnu src/include src/krb5 src/lib src/libexec src/release src/rescue
> | src/sbin src/secure src/share src/sys src/tools src/ubin src/usbin
> | world/base world/catpages world/dict world/doc world/games world/info
> | world/lib32 world/manpages world/proflibs
> |
> | The following components of FreeBSD do not seem to be installed:
> | kernel/generic
> |
> | Does this look reasonable (y/n)? n
>
> I do have the kernel sources installed, so I would like to have them
> updated. I don't even mind to have a GENERIC kernel temporarily
> installed, until I compile my own (fortunately, they are not that
> different).
>
> It is nice that it tells me that I "MUST update the kernel manually",
> but it gives me no help in getting the sources and doing that. (Can the
> new kernel even be built in all cases with old tools? NetBSD offers a
> nice cross-building system for that.)
>
> For my previous update to 8.0-RELEASE-p2 I patched freebsd-update simply
> to think that my kernel *is* GENERIC,
>
> --- /usr/sbin/freebsd-update2009-12-22 17:16:01.0 +0100
> +++ /tmp/freebsd-update 2010-05-11 10:35:05.0 +0200
> @@ -631,6 +631,7 @@
># we're running an SMP kernel.  This mis-identification is a bug
># which was fixed in 6.2-STABLE.
>KERNCONF=`uname -i`
> +   KERNCONF=GENERIC
>if [ ${KERNCONF} = "SMP-GENERIC" ]; then
>KERNCONF=SMP
>fi
>
> but that seems riskier as updates get a bit bigger.
>
> The official way seems to be to reboot using GENERIC, upgrade (with a
> reboot with new GENERIC), rebuild new CUSTOM kernel, reboot again. At
> least the first reboot ought to be avoided...
>
> -Olaf.
> --
> ___
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: FreeBSD 7.3, reboot after panic: double fault

[c0re]

And some more workaround:

On 7.2

ifconfig mtu
em0: flags=8843 metric 0 mtu 1500
gif0: flags=8051 metric 0 mtu 1280

Apache running on em0 alias address.

>From remote machine trying to download 10Kb file and looking into tcpdump.
No kernel panic. But 7.2 dows not respond to GET request, but in apache
access log I see that it responds with OK, and there no tcp push packets
from 7.2. So file not downloading. But at least no kernel panic :)
Then I setup 1200 mtu on em0 and everything is okay, file download
successful.

On 7.3 same mtu 1500 adn 1280 - kernel panic when trying to download file.
When I configure on em0 mtu 1200 - no kernel panic and file download
successful.

So it looks like mtu discovery related kernel panic.

Hope this will help to resolve problem.

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

Re: FreeBSD 7.3, reboot after panic: double fault

[c0re]

I also tryed to use GIF interface istead of GRE - same result and same
backtrace in kgdb - kernel panic.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: FreeBSD 7.3, reboot after panic: double fault

[c0re]

8
#46 0xc09bd5a8 in tcp_mtudisc (inp=0xc4c5d44c, errno=0) at tcp_offload.h:282
#47 0xc09bac9b in tcp_output (tp=0xc4c5f768) at
/usr/src/sys/netinet/tcp_output.c:1248
#48 0xc09bd5a8 in tcp_mtudisc (inp=0xc4c5d44c, errno=0) at tcp_offload.h:282
#49 0xc09bac9b in tcp_output (tp=0xc4c5f768) at
/usr/src/sys/netinet/tcp_output.c:1248
---Type  to continue, or q  to quit---
#50 0xc09bd5a8 in tcp_mtudisc (inp=0xc4c5d44c, errno=0) at tcp_offload.h:282
#51 0xc09bac9b in tcp_output (tp=0xc4c5f768) at
/usr/src/sys/netinet/tcp_output.c:1248
#52 0xc09bd5a8 in tcp_mtudisc (inp=0xc4c5d44c, errno=0) at tcp_offload.h:282
#53 0xc09bac9b in tcp_output (tp=0xc4c5f768) at
/usr/src/sys/netinet/tcp_output.c:1248
#54 0xc09bd5a8 in tcp_mtudisc (inp=0xc4c5d44c, errno=0) at tcp_offload.h:282
#55 0xc09bac9b in tcp_output (tp=0xc4c5f768) at
/usr/src/sys/netinet/tcp_output.c:1248
#56 0xc09b78e5 in tcp_do_segment (m=0xc4a83800, th=0xc4aa4024,
so=0xc4a2480c, tp=0xc4c5f768, drop_hdrlen=52, tlen=0, iptos=0 '\0',
ti_locked=3)
at /usr/src/sys/netinet/tcp_input.c:2684
#57 0xc09b8b7d in tcp_input (m=0xc4a83800, off0=20) at
/usr/src/sys/netinet/tcp_input.c:1020
#58 0xc09af671 in ip_input (m=0xc4a83800) at
/usr/src/sys/netinet/ip_input.c:804
#59 0xc0946a09 in netisr_dispatch_src (proto=1, source=0, m=0xc4a83800) at
/usr/src/sys/net/netisr.c:917
#60 0xc0946ca0 in netisr_dispatch (proto=1, m=0xc4a83800) at
/usr/src/sys/net/netisr.c:1004
#61 0xc093d2aa in ether_demux (ifp=0xc42d7000, m=0xc4a83800) at
/usr/src/sys/net/if_ethersubr.c:901
#62 0xc093d82f in ether_input (ifp=0xc42d7000, m=0xc4a83800) at
/usr/src/sys/net/if_ethersubr.c:760
#63 0xc0623c4a in lem_handle_rxtx (context=0xc42ea000, pending=1) at
/usr/src/sys/dev/e1000/if_lem.c:3616
#64 0xc08cb282 in taskqueue_run (queue=0xc42c9c80) at
/usr/src/sys/kern/subr_taskqueue.c:239
#65 0xc08cb48d in taskqueue_thread_loop (arg=0xc42ee5a8) at
/usr/src/sys/kern/subr_taskqueue.c:360
#66 0xc0868831 in fork_exit (callout=0xc08cb3d0 ,
arg=0xc42ee5a8, frame=0xe460dd38) at /usr/src/sys/kern/kern_fork.c:843
#67 0xc0b28c10 in fork_trampoline () at
/usr/src/sys/i386/i386/exception.s:270
(kgdb)


2010/4/21 Bjoern A. Zeeb 

> On Tue, 20 Apr 2010, pluknet wrote:
>
>  On 20 April 2010 15:48, John Baldwin  wrote:
>>
>>> On Tuesday 20 April 2010 2:53:16 am c0re wrote:
>>>
>>>> Hello All!
>>>> I've upgraded freebsd from 7.0 to 7.3 and all was good until I tryed to
>>>> configure gre interface and use ipfw fwd.
>>>> I'm actually does not know what was the point of failure in my
>>>> configuration.
>>>>
>>>> [ some details snipped ]
>>>>
>>>> It worked about one week and then I made some configuration changes:
>>>> added gre interface and 2 aliases:
>>>>
>>>> # cat /etc/rc.conf |grep
>>>> ifconfig_xl0="inet 192.168.0.10  netmask 255.255.255.0"
>>>> ifconfig_xl0_alias0="192.168.0.11 netmask 255.255.255.255"
>>>> ifconfig_xl0_alias1="192.168.0.12 netmask 255.255.255.255"
>>>> cloned_interfaces="gre0"
>>>> ifconfig_gre0="inet 192.168.250.6 192.168.250.5 tunnel 192.168.0.12
>>>> 192.168.200.15 netmask 255.255.255.252 link1 up"
>>>>
>>>> and
>>>>
>>>> # cat /etc/rc.local
>>>> #!/bin/sh
>>>> ipfw add fwd 192.168.250.5 icmp from 192.168.0.11 to any out via xl0
>>>> ipfw add fwd 192.168.250.5 tcp from 192.168.0.11 443 to any out via xl0
>>>> ipfw add allow ip from any to any
>>>>
>>>> # ifconfig gre0
>>>> gre0: flags=b050 metric 0 mtu
>>>> 1476
>>>> tunnel inet 192.168.0.12 --> 192.168.200.15
>>>> inet 192.168.250.6 --> 192.168.250.5 netmask 0xfffc
>>>>
>>>> I shutted down gre interface to prevent requests via gre to buggy IP.
>>>>
>>>> The main idea of such configurations was: fwd all connections to https
>>>> to
>>>> 192.168.0.1 via gre interface.
>>>> And also I made apache configurations to make it listen on 192.168.0.11
>>>> too.
>>>>
>>>> And make some tests: ping 192.168.0.11 - was fine, goes via gre. Telnet
>>>> to
>>>> 192.168.0.11  443 was fine too. Then I tryed to make browser https
>>>> connection to 192.168.0.11. Apache showed me certificate warning and I
>>>> accepted, then in browser nothing happened, it was trying to open page.
>>>> But
>>>> server got kernel panic at that moment.
>>>>
>>>> At first time I thought that it was some power failure, I tryed 2 more
>>>> times
>>>> and

Re: FreeBSD 7.3, reboot after panic: double fault

[c0re]

Bjoern A. Zeeb, I send you e-mail with link to download kernel and dump.

And I remade kernel panic situation on virtual machines.

You need 2 freebsd machines for gre tunnel.
First need just to make gre tunnel like:

ifconfig em0 inet 10.0.0.1  netmask 255.255.255.0
ifconfig gre0 create
ifconfig gre0 inet 192.168.0.1 192.168.0.2 tunnel 10.10.0.1 10.10.0.2
netmask 255.255.255.252 link1 up
route add 10.10.0.3/32 10.10.0.2

Also this machine will be as a client to connect to remote. So we need to
install some browser like lynx.

Second machine:
Default installation of freebsd 7.3 with "src" checked in distributions.
After install - recompile kernel for IPFIREWALL_FORWARD support (mainly):

# Local additions
options IPFIREWALL  #firewall
options IPFIREWALL_VERBOSE  #enable logging to syslogd(8)
options IPFIREWALL_VERBOSE_LIMIT=1000   #limit verbosity
options IPFIREWALL_FORWARD  #packet destination changes
options IPDIVERT#divert sockets
options IPSTEALTH   #support for stealth forwarding
options DUMMYNET
device  carp

And make kernel KERNCONF=MYKERNEL

reboot and configure network and firewall:

ifconfig em0 inet 10.10.0.2  netmask 255.255.255.0
ifconfig em0 alias inet 10.0.0.3 netmask 255.255.255.255
ifconfig gre0 create
ifconfig gre0 inet 192.168.0.2 192.168.0.1 tunnel 10.0.0.2 10.0.0.1 netmask
255.255.255.252 link1 up

ipfw add 00100 fwd 192.168.0.1 icmp from 10.0.0.3 to any out via em0
ipfw add 00200 fwd 192.168.0.1 tcp from 10.0.0.3 80 to any out via em0
ipfw add 00300 fwd 192.168.0.1 tcp from 10.0.0.3 443 to any out via em0
ipfw add 00400 allow ip from any to any

At that moment you can check icmp ping from 10.0.0.1 10.0.0.3 and ipfw show
to view that ipfw fwd counters are working.

Next we need to have some tcp service. I used apache2.
So in port /usr/ports/www/apache20 make install clean.
apache20_enable="YES" in rc.conf
In /usr/local/etc/apache2/httpd.conf:
edit "Listen 80" to "Listen 10.0.0.3:80 "
and add virtual host with 10kb index.html

NameVirtualHost 10.0.0.3:80 
http://10.0.0.3/>>
   DocumentRoot /usr/local/www/test


mkdir /usr/local/www/test
dd if=/dev/random of=/usr/local/www/test/index.html bc=10k count=1

/usr/local/etc/rc.d/apache2 start

At that moment everything ready to panic :)
>From first machine i'm trying lynx http://10.0.0.3/

On second machine I see kernel panic.

When I was testing - I got no panic at first time. So I generated apache ssl
certs and adited ssl.conf. But next time I made same configuration - not
only 443, but 80 port connection made kernel panic too.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"