Re: 7.1RC2 - Sendmail : Segmentation fault (core dumped)

2008-12-30 Thread Garrett Cooper
On Dec 30, 2008, at 20:16, Peter Sprokkelenburg wrote: I had 7.0 installed and did a binary upgrade to 7.1RC2 everything seems okay until I went to check my mailq and got : Segmentation fault (core dumped) I am running Postfix as my mail server and it does not seem to be affected. I ca

Lock enabling onboard lan (Attansic L1 GbE) on 7.1-PRERELEASE

2008-12-30 Thread Barbara
Hello, one of my motherboards has an onboard Attansic network interface, I think an AR8121. # pciconf -lcv no...@pci0:4:0:0: class=0x02 card=0x82261043 chip=0x10481969 rev=0xb0 hdr=0x00 vendor = 'Attansic (Now owned by Atheros)' device = 'L1 Gigabit Ethernet 10/100/100

7.1RC2 - Sendmail : Segmentation fault (core dumped)

2008-12-30 Thread Peter Sprokkelenburg
I had 7.0 installed and did a binary upgrade to 7.1RC2 everything seems okay until I went to check my mailq and got : Segmentation fault (core dumped) I am running Postfix as my mail server and it does not seem to be affected. I can't even run sendmail as I get the same error. ---

Re: rdump stuck in sbwait state (RELENG_7)

2008-12-30 Thread Terry Kennedy
> I'm pretty sure it's caused by FreeBSD. It can very well be related to > PR 117603, a real nasty dump(8) bug that was introduced in 7.0 on SMP > systems. But it should have been patched back in March by this: [...] > So I'm real surprised it shows up again. We got a pretty large backup > enviro

7.1-RC2 : ACPI warning and errors ACPI Error (psparse-0626)

2008-12-30 Thread Bernard Dugas
Hello, With 7.1-RC2 : Dec 30 18:10:38 client1 kernel: FreeBSD 7.1-RC2 #0: Tue Dec 23 11:42:13 UTC 2008 Dec 30 18:10:38 client1 kernel: r...@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC Dec 30 18:10:38 client1 kernel: Timecounter "i8254" frequency 1193182 Hz quality 0 Dec 30 18:10:38

TCP packet out-of-order problem

2008-12-30 Thread Lin Jui-Nan Eric
Dear listers, We recently found our new FreeBSD server (located in some foreign region) has poor network performance. After doing some tcpdump and iperf testing, we found that out-of-order TCP packets are not inserted into queue. This is an 100Mbps line, and TSO is disabled. % uname -a FreeBSD b

Re: SATA hotplug and AHCI

2008-12-30 Thread David Ehrmann
Bruce M. Simpson wrote: Andrey V. Elsukov wrote: ... Linux's libata driver has a quirk for VIA AHCI: /* vt8251 doesn't clear BSY on signature FIS reception, * request follow-up softreset. */ If i right understand it issues softreset for VIA controllers just after hardreset. And after softres

Re: SATA hotplug and AHCI

2008-12-30 Thread Bruce M. Simpson
Andrey V. Elsukov wrote: ... Linux's libata driver has a quirk for VIA AHCI: /* vt8251 doesn't clear BSY on signature FIS reception, * request follow-up softreset. */ If i right understand it issues softreset for VIA controllers just after hardreset. And after softreset it is trying to read d

Re: rdump stuck in sbwait state (RELENG_7)

2008-12-30 Thread Andy Kosela
I'm pretty sure it's caused by FreeBSD. It can very well be related to PR 117603, a real nasty dump(8) bug that was introduced in 7.0 on SMP systems. But it should have been patched back in March by this: jeff 2008-03-13 00:46:12 UTC FreeBSD src repository Modified files: sys/kern subr_sleepqu

Re: rdump stuck in sbwait state (RELENG_7)

2008-12-30 Thread Peter Jeremy
On 2008-Dec-30 05:48:26 -0500, Terry Kennedy wrote: >> Unfortunately, you need the last packets that were exchanged in order >> to identify which end has the problem (and hopefully provide some >> pointers as to why). If possible, can you repeat the dump whilst you >> run a tcpdump on the rdump f

Re: rdump stuck in sbwait state (RELENG_7)

2008-12-30 Thread Terry Kennedy
> Unfortunately, you need the last packets that were exchanged in order > to identify which end has the problem (and hopefully provide some > pointers as to why). If possible, can you repeat the dump whilst you > run a tcpdump on the rdump flow and then post the last dozen or so > packets in each

Re: panic: lock (ng_worklist) sleep mutex does not match earlier (spin mutex) lock

2008-12-30 Thread Alexander Motin
pluknet wrote: > While debugging I noticed that sys/netgraph/ng_base.c#rev1.131 > was MFCed to RELENG_6 inbeetwen 6.3 and 6.4 by mav as 1.102.2.15. > > But this depends on sys/kern/subr_witness.c#rev1.227 which was > not MFCed, and that is triggering panic (in subj) if kernel is built > with WITNE

Re: panic: lock (ng_worklist) sleep mutex does not match earlier (spin mutex) lock

2008-12-30 Thread pluknet
2008/12/30 Alexander Motin : > pluknet wrote: >> While debugging I noticed that sys/netgraph/ng_base.c#rev1.131 >> was MFCed to RELENG_6 inbeetwen 6.3 and 6.4 by mav as 1.102.2.15. >> >> But this depends on sys/kern/subr_witness.c#rev1.227 which was >> not MFCed, and that is triggering panic (in su

panic: lock (ng_worklist) sleep mutex does not match earlier (spin mutex) lock

2008-12-30 Thread pluknet
While debugging I noticed that sys/netgraph/ng_base.c#rev1.131 was MFCed to RELENG_6 inbeetwen 6.3 and 6.4 by mav as 1.102.2.15. But this depends on sys/kern/subr_witness.c#rev1.227 which was not MFCed, and that is triggering panic (in subj) if kernel is built with WITNESS. -- wbr, pluknet _

Re: rdump stuck in sbwait state (RELENG_7)

2008-12-30 Thread Peter Jeremy
On 2008-Dec-29 20:28:41 -0500, Terry Kennedy wrote: > I upgraded a box (Dell Poweredge 1550, dual PIII processors) from a kernel + >world of December 8th to one from today (December 29th) and I am experiencing >a new problem with rdump. ... > A tcpdump on both the sending and receiving systems s