misc/164472: fsck -B panics on particular data inconsistency

2012-01-25 Thread Eugene M. Zheganin

>Number: 164472
>Category:   misc
>Synopsis:   fsck -B panics on particular data inconsistency
>Confidential:   no
>Severity:   non-critical
>Priority:   low
>Responsible:freebsd-bugs
>State:  open
>Quarter:
>Keywords:   
>Date-Required:
>Class:  sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Jan 25 09:00:29 UTC 2012
>Closed-Date:
>Last-Modified:
>Originator: Eugene M. Zheganin
>Release:8.2-RELEASE
>Organization:
RealService LLC
>Environment:
FreeBSD elf.hq.norma.perm.ru 8.2-RELEASE FreeBSD 8.2-RELEASE #1: Thu May  5 
19:14:23 YEKST 2011 e...@ns.hq.norma.perm.ru:/usr/obj/usr/src/sys/ELF  i386
>Description:
fsck -B panics on particular inconsistencies.
I got one machine that sometimes locks up (probably die to some other bug), and 
after reset when it runs fsck -B it leads to panic.

Since this happens quite often last time I created an image on a partition that 
makes FreeBSD panic.

Unfortunately this machine doesn't run a debug kernel, and, due to a bug when 
FreeBSD reboots immidiately upon a key press from a screen where it says 
'Automatic reboot in 15 seconds, press any key to abort' (which is still 
unreported for some reason, while lots of people confirm its existance) I was 
(and I am) unable to capture a panic screen.

But, since I have an image, everyone can easily reproduce this panic.
This is 100% reproduceable, at least I've done it 5 times on a test machine and 
got a panic each time. Unfortunately, this machine is too old to build debug 
kernel in some reasonable amount of time (I really think anyone will download 
this image faster than I will build a debug kernel).

So... here comes the image in case someone is interested.

Attention, FreeBSD panics only when fsck is run with -B. Ordinary fsck run 
doesn't panic and is able to successfully resolve all the filesystem errors.
>How-To-Repeat:
Get an image from http://tech.norma.perm.ru/files/var.dsk (sorry, this link is 
about a couple of megabits, my really broadband link is served by a server from 
my previous report with a buggy pf route-to/reply-to, so I'm using this old 
server). Mount it read-write (I didn't test it on an unmounted or read-only 
image). Like this:

mdconfig -a -t vnode -f var.dsk
mount /dev/md0 /mnt/panic

Run an fsck (since it's a partition image you need to manually specify the fsck 
of the type needed):

fsck_4.2bsd -B /dev/md0

>Fix:
Run fsck without -B.

>Release-Note:
>Audit-Trail:
>Unformatted:
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


Re: misc/164472: fsck -B panics on particular data inconsistency

2012-01-25 Thread Eugene M. Zheganin
The following reply was made to PR misc/164472; it has been noted by GNATS.

From: "Eugene M. Zheganin" 
To: bug-follo...@freebsd.org, eug...@zhegan.in
Cc:  
Subject: Re: misc/164472: fsck -B panics on particular data inconsistency
Date: Wed, 25 Jan 2012 15:21:48 +0600

 P.S . I forgot to mention that this image size in 2048 megs, so I'm 
 sorry if you cannot afford its downloading.
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


Re: misc/164472: fsck -B panics on particular data inconsistency

2012-01-25 Thread Eugene M. Zheganin
The following reply was made to PR misc/164472; it has been noted by GNATS.

From: "Eugene M. Zheganin" 
To: bug-follo...@freebsd.org, eug...@zhegan.in
Cc:  
Subject: Re: misc/164472: fsck -B panics on particular data inconsistency
Date: Wed, 25 Jan 2012 15:48:16 +0600

 Yeah, my bad, I compressed it with xz and redirected web-server to it. 
 Now it's about 400 megs. Old URL still works.
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


kern/164474: The system couldn't turn on a monitor connected via DisplayPort

2012-01-25 Thread Andrey V. Elsukov

>Number: 164474
>Category:   kern
>Synopsis:   The system couldn't turn on a monitor connected via DisplayPort
>Confidential:   no
>Severity:   non-critical
>Priority:   low
>Responsible:freebsd-bugs
>State:  open
>Quarter:
>Keywords:   
>Date-Required:
>Class:  sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Jan 25 10:10:10 UTC 2012
>Closed-Date:
>Last-Modified:
>Originator: Andrey V. Elsukov
>Release:FreeBSD 10.0-CURRENT amd64
>Organization:
>Environment:
System: FreeBSD 10.0-CURRENT #1 r230475



>Description:
A monitor (HP ZR22w) is connected to the system via displayPort.
When monitor is powered on while system boot, then it works.
Now, if we power off monitor and then turn it on again, it can not find video 
signal
and doesn't turn on.

vgapci0@pci0:0:2:0: class=0x03 card=0x1494103c chip=0x01028086 rev=0x09 
hdr=0x00
vendor = 'Intel Corporation'
device = '2nd Generation Core Processor Family Integrated Graphics 
Controller'
class  = display
subclass   = VGA


>How-To-Repeat:
Connect monitor via DisplayPort.
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


kern/164475: gre misses RUNNING flag after a reboot

2012-01-25 Thread Eugene M. Zheganin

>Number: 164475
>Category:   kern
>Synopsis:   gre misses RUNNING flag after a reboot
>Confidential:   no
>Severity:   non-critical
>Priority:   low
>Responsible:freebsd-bugs
>State:  open
>Quarter:
>Keywords:   
>Date-Required:
>Class:  sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Jan 25 10:20:10 UTC 2012
>Closed-Date:
>Last-Modified:
>Originator: Eugene M. Zheganin
>Release:8.2-RELEASE
>Organization:
RealService LLC
>Environment:
FreeBSD moscow-omega 8.2-RELEASE FreeBSD 8.2-RELEASE #1: Tue Aug 23 16:30:54 
YEKST 2011 emz@moscow-omega:/usr/obj/usr/src/sys/MOSCOW  amd64
>Description:
gre misses RUNNING flag after a reboot and thus cannot function. I have to 'up' 
it manually.

>How-To-Repeat:
Create a gre interface and reboot.
>Fix:
Place this script in /usr/local/etc/rc.d/

#!/bin/sh
#

# PROVIDE: fixgre
# REQUIRE: LOGIN NETWORKING

. /etc/rc.subr  

name="fixgre"
rcvar=`set_rcvar`

start_cmd="start_cmd"

start_cmd () {
for i in `ifconfig | grep gre | awk -F: '{print $1}'`
do
ifconfig $i up
done
}


load_rc_config $name 
run_rc_command "$1"

>Release-Note:
>Audit-Trail:
>Unformatted:
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


Re: misc/164472: fsck -B panics on particular data inconsistency

2012-01-25 Thread Mihail Timofeev
The following reply was made to PR misc/164472; it has been noted by GNATS.

From: Mihail Timofeev <9267...@gmail.com>
To: bug-follo...@freebsd.org, eug...@zhegan.in
Cc:  
Subject: Re: misc/164472: fsck -B panics on particular data inconsistency
Date: Wed, 25 Jan 2012 19:56:57 +0700

 Confirm, bug is reproduced on FreeBSD 9.0-STABLE #2 r230483: Tue Jan
 24 00:48:28 NOVT 2012 r...@bsd.loc:/usr/obj/usr/src/sys/GENERIC
 i386
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


Re: amd64/164425: stat function doesn't 32bit mode on amd64

2012-01-25 Thread John Baldwin
The following reply was made to PR kern/164425; it has been noted by GNATS.

From: John Baldwin 
To: freebsd-am...@freebsd.org
Cc: "C. Jullien" ,
 freebsd-gnats-sub...@freebsd.org
Subject: Re: amd64/164425: stat function doesn't 32bit mode on amd64
Date: Wed, 25 Jan 2012 08:36:37 -0500

 On Monday, January 23, 2012 5:17:11 pm C. Jullien wrote:
 > 
 > >Number: 164425
 > >Category:   amd64
 > >Synopsis:   stat function doesn't 32bit mode on amd64
 > >Confidential:   no
 > >Severity:   critical
 > >Priority:   low
 > >Responsible:freebsd-amd64
 > >State:  open
 > >Quarter:
 > >Keywords:   
 > >Date-Required:
 > >Class:  sw-bug
 > >Submitter-Id:   current-users
 > >Arrival-Date:   Mon Jan 23 22:20:03 UTC 2012
 > >Closed-Date:
 > >Last-Modified:
 > >Originator: C. Jullien
 > >Release:8.1 and 9.0
 > >Organization:
 > Eligis
 > >Environment:
 > FreeBSD freebsd.eligis.com 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan  3 
 07:46:
 > 30 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  
 amd64
 > >Description:
 > A friend of mine also confirmed this issue I discovered at least on 8.1 and 
 is still present on 9.0-RELEASE.
 > 
 > The problem is that, when compiled on amd64 but for i686 target, stat 
 function hangs with a core dump.
 > 
 > $ gcc -m32 -DCOMPAT_32BIT -L/usr/lib32 -B/usr/lib32
 > 
 > I don't see where I'm wrong but can't imagine I'm the only one having this 
 issue.
 
 Yes, -m32 doesn't work currently as it uses the wrong set of headers 
 (/usr/include/machine references amd64 headers, not i386 headers).
 
 -- 
 John Baldwin
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


Re: misc/160818: [patch] boot menu (/boot/menu.rc) clarity and readability improvements

2012-01-25 Thread Devin Teske
The following reply was made to PR misc/160818; it has been noted by GNATS.

From: Devin Teske 
To: , 
Cc:  
Subject: Re: misc/160818: [patch] boot menu (/boot/menu.rc) clarity and 
readability improvements
Date: Wed, 25 Jan 2012 08:10:29 -0800

 Oops! ANSI code "27" is not supported by loader(8).
 
 Go ahead and use the original [now preferred] "0;37".
 -- 
 Devin
 
 _
 The information contained in this message is proprietary and/or confidential. 
If you are not the intended recipient, please: (i) delete the message and all 
copies; (ii) do not disclose, distribute or use the message in any manner; and 
(iii) notify the sender immediately. In addition, please be aware that any 
message addressed to our domain is subject to archiving and review by persons 
other than the intended recipient. Thank you.
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


RE: amd64/164425: stat function doesn't 32bit mode on amd64

2012-01-25 Thread Christian Jullien
The following reply was made to PR kern/164425; it has been noted by GNATS.

From: "Christian Jullien" 
To: "'John Baldwin'" ,

Cc: "'C. Jullien'" ,

Subject: RE: amd64/164425: stat function doesn't 32bit mode on amd64
Date: Wed, 25 Jan 2012 16:40:09 +0100

 Thanks for the reply.
 In that case, you must admit it is strange that gcc on FreeBSD amd64 has
 a-m32 support which does not work!
 
 I see two options that work equally well for me:
 - remove -m32 option on gcc amd64, distro will reduce
 - add /usr/include32 which gcc will use instead of /usr/include in case -m32
 is passed (or something similar)
 
 NetBSD requires a 32bit OS version to compile and use 32bit programs. At
 least it is clear.
 
 Christian 
 
 -Original Message-
 From: John Baldwin [mailto:j...@freebsd.org] 
 Sent: mercredi 25 janvier 2012 14:37
 To: freebsd-am...@freebsd.org
 Cc: C. Jullien; freebsd-gnats-sub...@freebsd.org
 Subject: Re: amd64/164425: stat function doesn't 32bit mode on amd64
 
 On Monday, January 23, 2012 5:17:11 pm C. Jullien wrote:
 > 
 > >Number: 164425
 > >Category:   amd64
 > >Synopsis:   stat function doesn't 32bit mode on amd64
 > >Confidential:   no
 > >Severity:   critical
 > >Priority:   low
 > >Responsible:freebsd-amd64
 > >State:  open
 > >Quarter:
 > >Keywords:   
 > >Date-Required:
 > >Class:  sw-bug
 > >Submitter-Id:   current-users
 > >Arrival-Date:   Mon Jan 23 22:20:03 UTC 2012
 > >Closed-Date:
 > >Last-Modified:
 > >Originator: C. Jullien
 > >Release:8.1 and 9.0
 > >Organization:
 > Eligis
 > >Environment:
 > FreeBSD freebsd.eligis.com 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan  
 > 3
 07:46:
 > 30 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
 
 amd64
 > >Description:
 > A friend of mine also confirmed this issue I discovered at least on 
 > 8.1 and
 is still present on 9.0-RELEASE.
 > 
 > The problem is that, when compiled on amd64 but for i686 target, stat
 function hangs with a core dump.
 > 
 > $ gcc -m32 -DCOMPAT_32BIT -L/usr/lib32 -B/usr/lib32
 > 
 > I don't see where I'm wrong but can't imagine I'm the only one having 
 > this
 issue.
 
 Yes, -m32 doesn't work currently as it uses the wrong set of headers
 (/usr/include/machine references amd64 headers, not i386 headers).
 
 --
 John Baldwin
 
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


Re: misc/160818: [patch] boot menu (/boot/menu.rc) clarity and readability improvements

2012-01-25 Thread Devin Teske
The following reply was made to PR misc/160818; it has been noted by GNATS.

From: Devin Teske 
To: , 
Cc:  
Subject: Re: misc/160818: [patch] boot menu (/boot/menu.rc) clarity and 
readability improvements
Date: Wed, 25 Jan 2012 08:12:19 -0800

 I tried this patch out on 9.0-RELEASE.
 
 I do think it's an improvement of the look-and-feel.
 
 Especially the lining-up of options.
 
 Must admit that at-first I didn't like the inversion, but now I do (after a=
  couple of reboots).
 
 Ship It!
 --=20
 Devin
 
 _
 The information contained in this message is proprietary and/or confidentia=
 l. If you are not the intended recipient, please: (i) delete the message an=
 d all copies; (ii) do not disclose, distribute or use the message in any ma=
 nner; and (iii) notify the sender immediately. In addition, please be aware=
  that any message addressed to our domain is subject to archiving and revie=
 w by persons other than the intended recipient. Thank you.
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


Re: amd64/164425: stat function doesn't 32bit mode on amd64

2012-01-25 Thread John Baldwin
The following reply was made to PR kern/164425; it has been noted by GNATS.

From: John Baldwin 
To: "Christian Jullien" 
Cc: freebsd-am...@freebsd.org,
 "'C. Jullien'" ,
 freebsd-gnats-sub...@freebsd.org
Subject: Re: amd64/164425: stat function doesn't 32bit mode on amd64
Date: Wed, 25 Jan 2012 11:20:10 -0500

 On Wednesday, January 25, 2012 10:40:09 am Christian Jullien wrote:
 > Thanks for the reply.
 > In that case, you must admit it is strange that gcc on FreeBSD amd64 has
 > a-m32 support which does not work!
 > 
 > I see two options that work equally well for me:
 > - remove -m32 option on gcc amd64, distro will reduce
 > - add /usr/include32 which gcc will use instead of /usr/include in case -m32
 > is passed (or something similar)
 > 
 > NetBSD requires a 32bit OS version to compile and use 32bit programs. At
 > least it is clear.
 
 There are several various WIP's to fix -m32 (and probably several existing bug 
 reports, just do a search for 'freebsd "-m32"' and look at the first batch of 
 results).
 
 -- 
 John Baldwin
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


Re: kern/164258: [mfi] mfi does not work with PERC5/i in AMD M350 motherboard

2012-01-25 Thread John Baldwin
The following reply was made to PR kern/164258; it has been noted by GNATS.

From: John Baldwin 
To: bug-follo...@freebsd.org, ja...@mansionfamily.plus.com
Cc:  
Subject: Re: kern/164258: [mfi] mfi does not work with PERC5/i in AMD M350
 motherboard
Date: Wed, 25 Jan 2012 11:53:18 -0500

 Can you capture a full boot -v dmesg (maybe using a serial console?)
 Also, are you booting with ACPI disabled or any other non-standard settings?
 
 -- 
 John Baldwin
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


Re: misc/160818: [patch] boot menu (/boot/menu.rc) clarity and readability improvements

2012-01-25 Thread pluknet
Synopsis: [patch] boot menu (/boot/menu.rc) clarity and readability improvements

State-Changed-From-To: open->patched
State-Changed-By: pluknet
State-Changed-When: Wed Jan 25 18:36:27 UTC 2012
State-Changed-Why: 
Patched in HEAD. MFC to stable/9 will follow in 1 week.

http://www.freebsd.org/cgi/query-pr.cgi?pr=160818
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


Re: misc/160818: [patch] boot menu (/boot/menu.rc) clarity and readability improvements

2012-01-25 Thread pluknet
Synopsis: [patch] boot menu (/boot/menu.rc) clarity and readability improvements

Responsible-Changed-From-To: freebsd-bugs->pluknet
Responsible-Changed-By: pluknet
Responsible-Changed-When: Wed Jan 25 18:38:02 UTC 2012
Responsible-Changed-Why: 
Track.

http://www.freebsd.org/cgi/query-pr.cgi?pr=160818
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


kern/164490: Incorrect IP checksum on pfil pass from ip_output()

2012-01-25 Thread Maxim Ignatenko

>Number: 164490
>Category:   kern
>Synopsis:   Incorrect IP checksum on pfil pass from ip_output()
>Confidential:   no
>Severity:   serious
>Priority:   medium
>Responsible:freebsd-bugs
>State:  open
>Quarter:
>Keywords:   
>Date-Required:
>Class:  sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Jan 25 19:40:01 UTC 2012
>Closed-Date:
>Last-Modified:
>Originator: Maxim Ignatenko
>Release:9-STABLE
>Organization:
>Environment:
FreeBSD imax 9.0-PRERELEASE FreeBSD 9.0-PRERELEASE #8 r228733: Thu Jan 12 
08:15:33 EET 2012 root@imax:/usr/obj/usr/src/sys/IMAX  i386
>Description:
IP checksum in ipfw on "out" appears to be incorrect:

% sudo ipfw show
00100 3899334 2047281422 allow ip from any to any via lo0
00200   0  0 deny ip from 127.0.0.0/8 to any
00300   0  0 deny ip from any to 127.0.0.0/8
00550   8420 ngtee 10 ip from any to 192.168.56.101 out
00600 1822684 1114344681 allow ip from any to any
65535   0  0 deny ip from any to any

% route -n get 192.168.10.10
   route to: 192.168.10.10
destination: 192.168.10.0
   mask: 255.255.255.0
  interface: lagg0
  flags: 
 recvpipe  sendpipe  ssthresh  rtt,msecmtuweightexpire
   0 0 0 0  1500 1 0 

% route -n get 192.168.56.101
   route to: 192.168.56.101
destination: 192.168.56.0
   mask: 255.255.255.0
  interface: vboxnet0
  flags: 
 recvpipe  sendpipe  ssthresh  rtt,msecmtuweightexpire
   0 0 0 0  1500 1 0

Next we run "ping -c1 192.168.10.10" on 192.168.56.101 and get these tcpdumps:

On gateway interface facing to 192.168.10.10:
% sudo tcpdump -i lagg0 -nXvvv -s 0 host 192.168.10.10 and icmp
tcpdump: listening on lagg0, link-type EN10MB (Ethernet), capture size 65535 
bytes
21:10:15.171175 IP (tos 0x0, ttl 63, id 157, offset 0, flags [none], proto ICMP 
(1), length 84)
192.168.56.101 > 192.168.10.10: ICMP echo request, id 19972, seq 0, length 
64
0x:  4500 0054 009d  3f01 b74c c0a8 3865  E..T?..L..8e
0x0010:  c0a8 0a0a 0800 4450 4e04  4f20 5397  ..DPN...O.S.
0x0020:  0001 d7ef 0809 0a0b 0c0d 0e0f 1011 1213  
0x0030:  1415 1617 1819 1a1b 1c1d 1e1f 2021 2223  .!"#
0x0040:  2425 2627 2829 2a2b 2c2d 2e2f 3031 3233  $%&'()*+,-./0123
0x0050:  3435 36374567
21:10:15.173669 IP (tos 0x0, ttl 64, id 1, offset 0, flags [none], proto 
ICMP (1), length 84)
192.168.10.10 > 192.168.56.101: ICMP echo reply, id 19972, seq 0, length 64
0x:  4500 0054 3415  4001 82d4 c0a8 0a0a  E..T4...@...
0x0010:  c0a8 3865  4c50 4e04  4f20 5397  ..8e..LPN...O.S.
0x0020:  0001 d7ef 0809 0a0b 0c0d 0e0f 1011 1213  
0x0030:  1415 1617 1819 1a1b 1c1d 1e1f 2021 2223  .!"#
0x0040:  2425 2627 2829 2a2b 2c2d 2e2f 3031 3233  $%&'()*+,-./0123
0x0050:  3435 36374567

Response checksum is 0x82d4

On 192.168.101.56:
% sudo tcpdump -i em0 -nXvvv -s 0 host 192.168.10.10 and icmp
tcpdump: listening on em0, link-type EN10MB (Ethernet), capture size 65535 bytes
21:10:15.128315 IP (tos 0x0, ttl 64, id 157, offset 0, flags [none], proto ICMP 
(1), length 84)
192.168.56.101 > 192.168.10.10: ICMP echo request, id 19972, seq 0, length 
64
0x:  4500 0054 009d  4001 b64c c0a8 3865  E..T@..L..8e
0x0010:  c0a8 0a0a 0800 4450 4e04  4f20 5397  ..DPN...O.S.
0x0020:  0001 d7ef 0809 0a0b 0c0d 0e0f 1011 1213  
0x0030:  1415 1617 1819 1a1b 1c1d 1e1f 2021 2223  .!"#
0x0040:  2425 2627 2829 2a2b 2c2d 2e2f 3031 3233  $%&'()*+,-./0123
0x0050:  3435 36374567
21:10:15.155980 IP (tos 0x0, ttl 63, id 1, offset 0, flags [none], proto 
ICMP (1), length 84)
192.168.10.10 > 192.168.56.101: ICMP echo reply, id 19972, seq 0, length 64
0x:  4500 0054 3415  3f01 83d4 c0a8 0a0a  E..T4...?...
0x0010:  c0a8 3865  4c50 4e04  4f20 5397  ..8e..LPN...O.S.
0x0020:  0001 d7ef 0809 0a0b 0c0d 0e0f 1011 1213  
0x0030:  1415 1617 1819 1a1b 1c1d 1e1f 2021 2223  .!"#
0x0040:  2425 2627 2829 2a2b 2c2d 2e2f 3031 3233  $%&'()*+,-./0123
0x0050:  3435 36374567

Here TTL decremented and checksum changed to 0x83d4

On gateway's ng_iface attached to ng_ipfw:10:
% sudo tcpdump -i ng0 -n -Xs0 -vvv host 192.168.10.10
tcpdump: WARNING: ng0: no IPv4 address assigned
tcpdump: listening on ng0, link-type NULL (BSD loopback), capture size 65535 
bytes
21:10:15.173749 IP (tos 0x0, ttl 63, id 1, offset 0, flags [none], proto 
ICMP (1), length 84, bad cksum 82d4 (->83d4)!)
192

Re: kern/164490: [pfil] Incorrect IP checksum on pfil pass from ip_output()

2012-01-25 Thread linimon
Old Synopsis: Incorrect IP checksum on pfil pass from ip_output()
New Synopsis: [pfil] Incorrect IP checksum on pfil pass from ip_output()

Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Wed Jan 25 19:58:14 UTC 2012
Responsible-Changed-Why: 
Over to maintainer(s).

http://www.freebsd.org/cgi/query-pr.cgi?pr=164490
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


misc/164495: connect double head igb to switch cause system to halt

2012-01-25 Thread Eugen Konkov

>Number: 164495
>Category:   misc
>Synopsis:   connect double head igb to switch cause system to halt
>Confidential:   no
>Severity:   non-critical
>Priority:   low
>Responsible:freebsd-bugs
>State:  open
>Quarter:
>Keywords:   
>Date-Required:
>Class:  sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Jan 25 21:00:02 UTC 2012
>Closed-Date:
>Last-Modified:
>Originator: Eugen Konkov
>Release:latest 10.0-CURRENT have same behaviour
>Organization:
ISP FreeLine
>Environment:
FreeBSD 9.0-CURRENT FreeBSD 9.0-CURRENT #3: Tue Jan 24 17:18:46 UTC 2012 
:/usr/obj/usr/src/sys/KES_KERN_v9  i386

>Description:
I have igb0 and igb1 connected to switch to port, for example, 3 and 4, each 
port have vlan5, and vlan6 configured,



vlan5,vlan6>>---SWFix:


>Release-Note:
>Audit-Trail:
>Unformatted:
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


Re: misc/164290: FreeBSD 9.0 IS NOT YET PRODUCTION/STABLE

2012-01-25 Thread CeDeROM
On Wed, Jan 18, 2012 at 11:14 PM, Mark Linimon  wrote:
> sysinstall was an absolute bitch to maintain, and people have been
> demanding more modern features for it for years.  Atttempt after
> attempt has been made to rewrite or update it, all of which have been
> abandoned up until now.
> (...)

Hello Mark and thank you for your explanations it gives me a better
overview why things were changed and I accept that.. maybe except new
things does not have old good functionalities which are important from
user perspective :-)

Is there a chance that installation ISO will be updated with new
version of bsdinstall that already can install over existing
filesystem or any new features, or installation ISO are frozen and
cannot change until next release?

Thank you and best regards,
Tomek

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


Re: misc/164290: FreeBSD 9.0 IS NOT YET PRODUCTION/STABLE

2012-01-25 Thread Bruce Cran

On 25/01/2012 22:24, CeDeROM wrote:

Hello Mark and thank you for your explanations it gives me a better
overview why things were changed and I accept that.. maybe except new
things does not have old good functionalities which are important from
user perspective :-)

Is there a chance that installation ISO will be updated with new
version of bsdinstall that already can install over existing
filesystem or any new features, or installation ISO are frozen and
cannot change until next release?


Devin Teske is working on creating an ISO of 9.0 which has support for 
both sysinstall and bsdinstall. I expect it will appear on 
http://druidbsd.sourceforge.net/ when finished.


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


Re: kern/164455: Intel D815E(P)FV FreeBSD 7.2/8.2/9.0 not 6.4 kernel boot errors

2012-01-25 Thread Andriy Gapon
The following reply was made to PR kern/164455; it has been noted by GNATS.

From: Andriy Gapon 
To: bug-follo...@freebsd.org, a...@univ.kiev.ua
Cc:  
Subject: Re: kern/164455: Intel D815E(P)FV FreeBSD 7.2/8.2/9.0 not 6.4 kernel
 boot errors
Date: Thu, 26 Jan 2012 00:37:55 +0200

 Those messages are harmless warnings.
 It's hard to suppress them because  of some architectural problems.  But there
 is no problem with your system.
 
 -- 
 Andriy Gapon
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


kern/164499: if_wi needs fix for big endian architectures.

2012-01-25 Thread Justin Hibbits

>Number: 164499
>Category:   kern
>Synopsis:   if_wi needs fix for big endian architectures.
>Confidential:   no
>Severity:   non-critical
>Priority:   low
>Responsible:freebsd-bugs
>State:  open
>Quarter:
>Keywords:   
>Date-Required:
>Class:  sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Jan 26 02:10:01 UTC 2012
>Closed-Date:
>Last-Modified:
>Originator: Justin Hibbits
>Release:CURRENT
>Organization:
>Environment:
>Description:
if_wi(4) byte-swaps twice on big endian when reading from the device.  The 
attached patch fixes this by calling the streaming read.

Patch discussed with adrian@.
>How-To-Repeat:

>Fix:


Patch attached with submission follows:

Index: sys/dev/wi/if_wi.c
===
--- sys/dev/wi/if_wi.c  (revision 230483)
+++ sys/dev/wi/if_wi.c  (working copy)
@@ -1898,8 +1898,7 @@
 static int
 wi_read_bap(struct wi_softc *sc, int id, int off, void *buf, int buflen)
 {
-   u_int16_t *ptr;
-   int i, error, cnt;
+   int error, cnt;
 
if (buflen == 0)
return 0;
@@ -1908,9 +1907,7 @@
return error;
}
cnt = (buflen + 1) / 2;
-   ptr = (u_int16_t *)buf;
-   for (i = 0; i < cnt; i++)
-   *ptr++ = CSR_READ_2(sc, WI_DATA0);
+   CSR_READ_MULTI_STREAM_2(sc, WI_DATA0, (u_int16_t *)buf, cnt);
sc->sc_bap_off += cnt * 2;
return 0;
 }
@@ -1918,8 +1915,7 @@
 static int
 wi_write_bap(struct wi_softc *sc, int id, int off, void *buf, int buflen)
 {
-   u_int16_t *ptr;
-   int i, error, cnt;
+   int error, cnt;
 
if (buflen == 0)
return 0;
@@ -1929,9 +1925,7 @@
return error;
}
cnt = (buflen + 1) / 2;
-   ptr = (u_int16_t *)buf;
-   for (i = 0; i < cnt; i++)
-   CSR_WRITE_2(sc, WI_DATA0, ptr[i]);
+   CSR_WRITE_MULTI_STREAM_2(sc, WI_DATA0, (u_int16_t *)buf, cnt);
sc->sc_bap_off += cnt * 2;
 
return 0;


>Release-Note:
>Audit-Trail:
>Unformatted:
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


Re: kern/164499: [wi] [patch] if_wi needs fix for big endian architectures.

2012-01-25 Thread linimon
Old Synopsis: if_wi needs fix for big endian architectures.
New Synopsis: [wi] [patch] if_wi needs fix for big endian architectures.

Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless
Responsible-Changed-By: linimon
Responsible-Changed-When: Thu Jan 26 02:22:27 UTC 2012
Responsible-Changed-Why: 
Over to maintainer(s).

http://www.freebsd.org/cgi/query-pr.cgi?pr=164499
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


Re: kern/164495: [igb] connect double head igb to switch cause system to halt

2012-01-25 Thread linimon
Old Synopsis: connect double head igb to switch cause system to halt
New Synopsis: [igb] connect double head igb to switch cause system to halt

Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Thu Jan 26 02:23:09 UTC 2012
Responsible-Changed-Why: 
Over to maintainer(s).

http://www.freebsd.org/cgi/query-pr.cgi?pr=164495
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


Re: kern/164475: [gre] gre misses RUNNING flag after a reboot

2012-01-25 Thread linimon
Old Synopsis: gre misses RUNNING flag after a reboot
New Synopsis: [gre] gre misses RUNNING flag after a reboot

Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Thu Jan 26 02:23:58 UTC 2012
Responsible-Changed-Why: 
Over to maintainer(s).

http://www.freebsd.org/cgi/query-pr.cgi?pr=164475
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


Re: kern/161553: Timestamp missing from msgbuf

2012-01-25 Thread eadler
Synopsis: Timestamp missing from msgbuf

Responsible-Changed-From-To: freebsd-bugs->eadler
Responsible-Changed-By: eadler
Responsible-Changed-When: Thu Jan 26 02:55:28 UTC 2012
Responsible-Changed-Why: 
it will be a bit before I get to this one but I'd like to make sure
someone looks at this PR.

http://www.freebsd.org/cgi/query-pr.cgi?pr=161553
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


Re: kern/144754: gssapi(3): cyradm crashes inside libgssapi.so

2012-01-25 Thread Bob Frazier
The following reply was made to PR kern/144754; it has been noted by GNATS.

From: Bob Frazier 
To: bug-follo...@freebsd.org, m...@aldan.algebra.com
Cc:  
Subject: Re: kern/144754: gssapi(3): cyradm crashes inside libgssapi.so
Date: Wed, 25 Jan 2012 21:34:36 -0800

 still appears to be happening in 8.2 (x86 build).  Is there any other 
 resolution besides removing the libs or building the port without them?
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"