On Sun, Feb 26, 2006 at 11:34:11PM -0800, Kent Stewart wrote:
> It also occurs on RELENG_5 but that machine is my gateway and firewall.
>
> It may be trying to confuse me but I have to use the NIC in XP before it
> will panic on the FreeBSD boot. My sacrificial machine only runs
> 6-stable and
On Sunday 26 February 2006 16:18, Kris Kennaway wrote:
> On Sun, Feb 26, 2006 at 03:51:44PM -0800, Kent Stewart wrote:
> > One thing, the developer's handbook only talks about "option DDB"
> > but that won't compile until you have added KDB.
>
> Please send-pr about this to get the docs updated.
>
On Sun, Feb 26, 2006 at 03:51:44PM -0800, Kent Stewart wrote:
> One thing, the developer's handbook only talks about "option DDB" but
> that won't compile until you have added KDB.
Please send-pr about this to get the docs updated.
> Now, I got it to panic but it took 5 or 6 tries. "At will" mu
On Sunday 26 February 2006 12:42, Kris Kennaway wrote:
> On Sun, Feb 26, 2006 at 12:39:22PM -0800, Kent Stewart wrote:
> > On Sunday 26 February 2006 12:29, Kris Kennaway wrote:
> > > On Sun, Feb 26, 2006 at 11:24:28AM -0800, Kent Stewart wrote:
> > > > > Unfortunately without a traceback the panic
On Sun, Feb 26, 2006 at 12:39:22PM -0800, Kent Stewart wrote:
> On Sunday 26 February 2006 12:29, Kris Kennaway wrote:
> > On Sun, Feb 26, 2006 at 11:24:28AM -0800, Kent Stewart wrote:
> > > > Unfortunately without a traceback the panic string is useless
> > > > since it gives you no clue about how
On Sunday 26 February 2006 12:29, Kris Kennaway wrote:
> On Sun, Feb 26, 2006 at 11:24:28AM -0800, Kent Stewart wrote:
> > > Unfortunately without a traceback the panic string is useless
> > > since it gives you no clue about how the system got into that
> > > state. This kind of panic is often a
On Sun, Feb 26, 2006 at 11:24:28AM -0800, Kent Stewart wrote:
> > Unfortunately without a traceback the panic string is useless since
> > it gives you no clue about how the system got into that state. This
> > kind of panic is often a secondary effect of some other problem.
> >
>
> I can cause t
On Saturday 25 February 2006 22:13, Kris Kennaway wrote:
> On Sat, Feb 25, 2006 at 10:08:47PM -0800, Garrett Cooper wrote:
> > Kris Kennaway wrote:
> > >On Sat, Feb 25, 2006 at 10:33:06PM -0500, Robert Huff wrote:
> > >> I just had my -CURRENT* machine crash under moderate load. No
> > >>dump is
On Sat, Feb 25, 2006 at 11:26:00PM -0800, Garrett Cooper wrote:
> Kris Kennaway wrote:
>
> >On Sat, Feb 25, 2006 at 10:22:59PM -0800, Garrett Cooper wrote:
> >
> >
> >
> >>re0: diagnostic failed to receive packet in loopback mode
> >>re0: attach aborted due to hardware diagnostic failure
Kris Kennaway wrote:
On Sat, Feb 25, 2006 at 10:22:59PM -0800, Garrett Cooper wrote:
re0: diagnostic failed to receive packet in loopback mode
re0: attach aborted due to hardware diagnostic failure
panic: mtx_lock() of spin mutex (null) @
/usr/src/sys/netinet/in_pcb,c:862
"re0" i
On Sat, Feb 25, 2006 at 10:22:59PM -0800, Garrett Cooper wrote:
> re0: diagnostic failed to receive packet in loopback mode
> re0: attach aborted due to hardware diagnostic failure
> panic: mtx_lock() of spin mutex (null) @
> /usr/src/sys/netinet/in_pcb,c:862
>
> "re0"
Kris Kennaway wrote:
On Sat, Feb 25, 2006 at 10:08:47PM -0800, Garrett Cooper wrote:
Kris Kennaway wrote:
On Sat, Feb 25, 2006 at 10:33:06PM -0500, Robert Huff wrote:
I just had my -CURRENT* machine crash under moderate load. No
dump is available because the machine
On Sat, Feb 25, 2006 at 10:08:47PM -0800, Garrett Cooper wrote:
> Kris Kennaway wrote:
>
> >On Sat, Feb 25, 2006 at 10:33:06PM -0500, Robert Huff wrote:
> >
> >
> >>I just had my -CURRENT* machine crash under moderate load. No
> >>dump is available because the machine locked hard, but I did
Kris Kennaway wrote:
On Sat, Feb 25, 2006 at 10:33:06PM -0500, Robert Huff wrote:
I just had my -CURRENT* machine crash under moderate load. No
dump is available because the machine locked hard, but I did copy
this off the screen:
re0: diagnostic failed to receive packet in loopbac
Kris Kennaway writes:
> >Before I take this to current@ - has anyone seen anything like
> > this before? A quick check of the archives and the web in general
> > didn't show anything.
>
> You need to at least get a traceback from the panic, and preferably a
> crashdump.
Under
On Sat, Feb 25, 2006 at 10:33:06PM -0500, Robert Huff wrote:
>
> I just had my -CURRENT* machine crash under moderate load. No
> dump is available because the machine locked hard, but I did copy
> this off the screen:
>
> re0: diagnostic failed to receive packet in loopback mode
> re0: att
I just had my -CURRENT* machine crash under moderate load. No
dump is available because the machine locked hard, but I did copy
this off the screen:
re0: diagnostic failed to receive packet in loopback mode
re0: attach aborted due to hardware diagnostic failure
panic: mtx_lock() of spin
17 matches
Mail list logo
