Gleb Smirnoff wrote:
> A> This seems to be a fallout of the recent UMA changes and its interaction
> A> with the per-cpu counter(9) system.
> A>
> A> Adding in and handing over to Gleb and Jeff as they touched this area last
.
>
> Ian has reported this panic several days before Jeff's changes :(
On Wed, Jun 19, 2013 at 02:20:14PM +0200, Andre Oppermann wrote:
A> On 19.06.2013 11:34, Ian FREISLICH wrote:
A> > Andre Oppermann wrote:
A> >> On 19.06.2013 11:10, Ian FREISLICH wrote:
A> >>> Hi
A> >>>
A> >>> I'm seeing this panic quite regularly now. Most recent sighting on
r251858.
A> >>
A> >>
On 19.06.2013 11:34, Ian FREISLICH wrote:
Andre Oppermann wrote:
On 19.06.2013 11:10, Ian FREISLICH wrote:
Hi
I'm seeing this panic quite regularly now. Most recent sighting on r251858.
This panic message is not very informative and very hard to extract any
meaningful hints. Do you have a
Andre Oppermann wrote:
> On 19.06.2013 11:10, Ian FREISLICH wrote:
> > Hi
> >
> > I'm seeing this panic quite regularly now. Most recent sighting on r251858.
>
> This panic message is not very informative and very hard to extract any
> meaningful hints. Do you have a core dump and matching debug
On 19.06.2013 11:10, Ian FREISLICH wrote:
Hi
I'm seeing this panic quite regularly now. Most recent sighting on r251858.
This panic message is not very informative and very hard to extract any
meaningful hints. Do you have a core dump and matching debug kernel?
--
Andre
cpuid = 15
KDB: st
Hi
I'm seeing this panic quite regularly now. Most recent sighting on r251858.
cpuid = 15
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xff846b258130
vpanic() at vpanic+0x126/frame 0xff846b258170
panic() at panic+0x43/frame 0xff846b2581d0
__rw_ass
On Thursday, December 29, 2011 3:25:02 pm Pawel Jakub Dawidek wrote:
> On Thu, Dec 29, 2011 at 11:12:59AM -0500, John Baldwin wrote:
> > On Sunday, December 25, 2011 11:01:33 am Коньков Евгений wrote:
> > > Здравствуйте, John.
> > >
> > > Вы писали 20 декабря 2011 г., 16:52:44:
> > >
> > > JB> On
On Thu, Dec 29, 2011 at 11:12:59AM -0500, John Baldwin wrote:
> On Sunday, December 25, 2011 11:01:33 am Коньков Евгений wrote:
> > Здравствуйте, John.
> >
> > Вы писали 20 декабря 2011 г., 16:52:44:
> >
> > JB> On Saturday, December 17, 2011 6:21:27 pm Pawel Jakub Dawidek wrote:
> > >> On Mon, D
On Sunday, December 25, 2011 11:01:33 am Коньков Евгений wrote:
> Здравствуйте, John.
>
> Вы писали 20 декабря 2011 г., 16:52:44:
>
> JB> On Saturday, December 17, 2011 6:21:27 pm Pawel Jakub Dawidek wrote:
> >> On Mon, Dec 12, 2011 at 11:00:23AM -0500, John Baldwin wrote:
> >> > An update. I've
Здравствуйте, John.
Вы писали 20 декабря 2011 г., 16:52:44:
JB> On Saturday, December 17, 2011 6:21:27 pm Pawel Jakub Dawidek wrote:
>> On Mon, Dec 12, 2011 at 11:00:23AM -0500, John Baldwin wrote:
>> > An update. I've sent Pawel a testing patch to see if my hypothesis is
>> > correct
>> > (www
On Saturday, December 17, 2011 6:21:27 pm Pawel Jakub Dawidek wrote:
> On Mon, Dec 12, 2011 at 11:00:23AM -0500, John Baldwin wrote:
> > An update. I've sent Pawel a testing patch to see if my hypothesis is
> > correct
> > (www.freebsd.org/~jhb/patches/tcp_negwin_test.patch). If it is then I
>
On Mon, Dec 12, 2011 at 11:00:23AM -0500, John Baldwin wrote:
> An update. I've sent Pawel a testing patch to see if my hypothesis is correct
> (www.freebsd.org/~jhb/patches/tcp_negwin_test.patch). If it is then I intend
> to commit www.freebsd.org/~jhb/patches/tcp_negwin2.patch as the fix.
Unfo
On Mon, Dec 12, 2011 at 11:00:23AM -0500, John Baldwin wrote:
> An update. I've sent Pawel a testing patch to see if my hypothesis is correct
> (www.freebsd.org/~jhb/patches/tcp_negwin_test.patch). If it is then I intend
> to commit www.freebsd.org/~jhb/patches/tcp_negwin2.patch as the fix.
Sorr
On Monday, October 24, 2011 8:14:22 am John Baldwin wrote:
> On Sunday, October 23, 2011 11:58:28 am Pawel Jakub Dawidek wrote:
> > On Sun, Oct 23, 2011 at 11:44:45AM +0300, Kostik Belousov wrote:
> > > On Sun, Oct 23, 2011 at 08:10:38AM +0200, Pawel Jakub Dawidek wrote:
> > > > My suggestion would
On Friday, October 28, 2011 1:46:07 am Pawel Jakub Dawidek wrote:
> On Fri, Oct 28, 2011 at 11:29:34AM +1100, Lawrence Stewart wrote:
> > On 10/26/11 22:53, John Baldwin wrote:
> > > The assertion would be triggered when the next packet arrives (as I said
> > > above). Try modifying your debugging
On Fri, Oct 28, 2011 at 11:29:34AM +1100, Lawrence Stewart wrote:
> On 10/26/11 22:53, John Baldwin wrote:
> > The assertion would be triggered when the next packet arrives (as I said
> > above). Try modifying your debugging output to also log if the ACK is
> > delayed. I suspect it is not delaye
On 10/26/11 22:53, John Baldwin wrote:
On Wednesday, October 26, 2011 3:54:31 am Pawel Jakub Dawidek wrote:
On Mon, Oct 24, 2011 at 08:14:22AM -0400, John Baldwin wrote:
On Sunday, October 23, 2011 11:58:28 am Pawel Jakub Dawidek wrote:
On Sun, Oct 23, 2011 at 11:44:45AM +0300, Kostik Belousov
On 10/26/11 12:54 AM, Pawel Jakub Dawidek wrote:
On Mon, Oct 24, 2011 at 08:14:22AM -0400, John Baldwin wrote:
On Sunday, October 23, 2011 11:58:28 am Pawel Jakub Dawidek wrote:
On Sun, Oct 23, 2011 at 11:44:45AM +0300, Kostik Belousov wrote:
On Sun, Oct 23, 2011 at 08:10:38AM +0200, Pawel Jak
On Wednesday, October 26, 2011 3:54:31 am Pawel Jakub Dawidek wrote:
> On Mon, Oct 24, 2011 at 08:14:22AM -0400, John Baldwin wrote:
> > On Sunday, October 23, 2011 11:58:28 am Pawel Jakub Dawidek wrote:
> > > On Sun, Oct 23, 2011 at 11:44:45AM +0300, Kostik Belousov wrote:
> > > > On Sun, Oct 23,
On Mon, Oct 24, 2011 at 08:14:22AM -0400, John Baldwin wrote:
> On Sunday, October 23, 2011 11:58:28 am Pawel Jakub Dawidek wrote:
> > On Sun, Oct 23, 2011 at 11:44:45AM +0300, Kostik Belousov wrote:
> > > On Sun, Oct 23, 2011 at 08:10:38AM +0200, Pawel Jakub Dawidek wrote:
> > > > My suggestion wo
On Sunday, October 23, 2011 11:58:28 am Pawel Jakub Dawidek wrote:
> On Sun, Oct 23, 2011 at 11:44:45AM +0300, Kostik Belousov wrote:
> > On Sun, Oct 23, 2011 at 08:10:38AM +0200, Pawel Jakub Dawidek wrote:
> > > My suggestion would be that if we won't be able to fix it before 9.0,
> > > we should
On Sun, Oct 23, 2011 at 11:44:45AM +0300, Kostik Belousov wrote:
> On Sun, Oct 23, 2011 at 08:10:38AM +0200, Pawel Jakub Dawidek wrote:
> > My suggestion would be that if we won't be able to fix it before 9.0,
> > we should turn this assertion off, as the system seems to be able to
> > recover.
>
On Sun, Oct 23, 2011 at 08:10:38AM +0200, Pawel Jakub Dawidek wrote:
> On Sun, Oct 23, 2011 at 12:35:15PM +1100, Lawrence Stewart wrote:
> > On 10/22/11 19:49, Pawel Jakub Dawidek wrote:
> > > The panic message says:
> > >
> > > panic: tcp_input negative window: tp 0xfe007763e000 rcv_nxt
> >
On Sun, Oct 23, 2011 at 12:35:15PM +1100, Lawrence Stewart wrote:
> On 10/22/11 19:49, Pawel Jakub Dawidek wrote:
> > The panic message says:
> >
> > panic: tcp_input negative window: tp 0xfe007763e000 rcv_nxt
> > 3718269252 rcv_adv 3718268291
> >
> > I only have picture of the backtrace:
On Sun, 23 Oct 2011, Lawrence Stewart wrote:
On 10/22/11 19:49, Pawel Jakub Dawidek wrote:
The panic message says:
panic: tcp_input negative window: tp 0xfe007763e000 rcv_nxt
3718269252 rcv_adv 3718268291
I only have picture of the backtrace:
http://people.freebsd.org/~pjd/mis
On 10/22/11 19:49, Pawel Jakub Dawidek wrote:
The panic message says:
panic: tcp_input negative window: tp 0xfe007763e000 rcv_nxt
3718269252 rcv_adv 3718268291
I only have picture of the backtrace:
http://people.freebsd.org/~pjd/misc/panic_negative_window.jpg
ewww that
On Sat, 22 Oct 2011, Pawel Jakub Dawidek wrote:
The panic message says:
panic: tcp_input negative window: tp 0xfe007763e000 rcv_nxt
3718269252 rcv_adv 3718268291
I only have picture of the backtrace:
http://people.freebsd.org/~pjd/misc/panic_negative_window.jpg
I've see
The panic message says:
panic: tcp_input negative window: tp 0xfe007763e000 rcv_nxt
3718269252 rcv_adv 3718268291
I only have picture of the backtrace:
http://people.freebsd.org/~pjd/misc/panic_negative_window.jpg
--
Pawel Jakub Dawidek http://www.whe
28 matches
Mail list logo