Hello, I wrote:
This thread came up on kgdb-bugreport mailing list. Could you please
suggest us what's the correct way of fixing this problem?
1. When running a kgdb on RTL8139 ethernet interface: 8139too driver
prints too many "Out-of-sync dirty pointer" messages on console and
gdb can't co
Hello, I wrote:
This thread came up on kgdb-bugreport mailing list. Could you please
suggest us what's the correct way of fixing this problem?
1. When running a kgdb on RTL8139 ethernet interface: 8139too driver
prints too many "Out-of-sync dirty pointer" messages on console and
gdb can't co
Hello.
Amit S. Kale wrote:
This thread came up on kgdb-bugreport mailing list. Could you please suggest
us what's the correct way of fixing this problem?
1. When running a kgdb on RTL8139 ethernet interface: 8139too driver prints
too many "Out-of-sync dirty pointer" messages on console and g
komal wrote:
Hi all,
As the discussion was going on about the effects of trapping the
netpoll queue during KGDBoE debugging, I tried avoiding it. So in
eth_pre_exception_handler() I did not set net_poll_trap to 1 and did not
reset it back to 0 in eth_post_exception_handler()
file d
Stephen Hemminger wrote:
On Fri, 23 Feb 2007 11:10:40 -0700
Mark Huth <[EMAIL PROTECTED]> wrote:
Amit S. Kale wrote:
Hi Net Gurus,
This thread came up on kgdb-bugreport mailing list. Could you please suggest
us what's the correct way of fixing this problem?
1. When running a kgdb o
Stephen Hemminger wrote:
This thread came up on kgdb-bugreport mailing list. Could you please suggest
us what's the correct way of fixing this problem?
1. When running a kgdb on RTL8139 ethernet interface: 8139too driver prints
too many "Out-of-sync dirty pointer" messages on console and gdb
On Fri, 23 Feb 2007 22:16:59 +0300
Sergei Shtylyov <[EMAIL PROTECTED]> wrote:
> Hello.
>
> Stephen Hemminger wrote:
>
> >This thread came up on kgdb-bugreport mailing list. Could you please
> >suggest
> >us what's the correct way of fixing this problem?
>
> >1. When running a
Hello.
Stephen Hemminger wrote:
This thread came up on kgdb-bugreport mailing list. Could you please suggest
us what's the correct way of fixing this problem?
1. When running a kgdb on RTL8139 ethernet interface: 8139too driver prints
too many "Out-of-sync dirty pointer" messages on console
On Fri, 23 Feb 2007 22:09:16 +0300
Sergei Shtylyov <[EMAIL PROTECTED]> wrote:
> Hello.
>
> Stephen Hemminger wrote:
>
> >>>This thread came up on kgdb-bugreport mailing list. Could you please
> >>>suggest
> >>>us what's the correct way of fixing this problem?
>
> >>>1. When running a kgdb on
Hello.
Stephen Hemminger wrote:
This thread came up on kgdb-bugreport mailing list. Could you please suggest
us what's the correct way of fixing this problem?
1. When running a kgdb on RTL8139 ethernet interface: 8139too driver prints
too many "Out-of-sync dirty pointer" messages on console
On Fri, 23 Feb 2007 11:10:40 -0700
Mark Huth <[EMAIL PROTECTED]> wrote:
> Amit S. Kale wrote:
> > Hi Net Gurus,
> >
> > This thread came up on kgdb-bugreport mailing list. Could you please
> > suggest
> > us what's the correct way of fixing this problem?
> >
> > 1. When running a kgdb on RTL8139
Amit S. Kale wrote:
Hi Net Gurus,
This thread came up on kgdb-bugreport mailing list. Could you please suggest
us what's the correct way of fixing this problem?
1. When running a kgdb on RTL8139 ethernet interface: 8139too driver prints
too many "Out-of-sync dirty pointer" messages on consol
Hi Net Gurus,
This thread came up on kgdb-bugreport mailing list. Could you please suggest
us what's the correct way of fixing this problem?
1. When running a kgdb on RTL8139 ethernet interface: 8139too driver prints
too many "Out-of-sync dirty pointer" messages on console and gdb can't
connec
13 matches
Mail list logo
