On Fri, 2003-11-28 at 08:49, Yuriy Tsibizov wrote:
> >> It looks very similar to
> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=59576. You can revert to
> >> version 1.28 of net/bpf.h if you need tcpdump on lo, tun, ic, plip,
> >> disc or gif interface right now.
>
> > just to note: I ran tcpdump
On Fri, 28 Nov 2003, Yuriy Tsibizov wrote:
> >> It looks very similar to
> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=59576. You can revert to
> >> version 1.28 of net/bpf.h if you need tcpdump on lo, tun, ic, plip,
> >> disc or gif interface right now.
>
> > just to note: I ran tcpdump on tunN
>> It looks very similar to
>> http://www.freebsd.org/cgi/query-pr.cgi?pr=59576. You can revert to
>> version 1.28 of net/bpf.h if you need tcpdump on lo, tun, ic, plip,
>> disc or gif interface right now.
> just to note: I ran tcpdump on tunN (which was a pppoe interface) w/o
> problems two days
On Thursday 27 November 2003 06:38 am, Bjoern A. Zeeb wrote:
> On Thu, 27 Nov 2003, Yuriy Tsibizov wrote:
>
> Hi,
>
> > >i got a panic on recent -CURRENT:
> > >
> > ># tcpdump -i lo0 port 23 &
> > >[1] 507
> > >listening on lo0
> > >
> > ># telnet localhost
> > >Trying ::1...
> > >
> > >Wed Nov 26
On Thu, 27 Nov 2003, Yuriy Tsibizov wrote:
Hi,
> >i got a panic on recent -CURRENT:
>
> ># tcpdump -i lo0 port 23 &
> >[1] 507
> >listening on lo0
>
> ># telnet localhost
> >Trying ::1...
>
> >Wed Nov 26 14:51:23 MSK 2003
> >Debugger+0x55: xchgl %ebx,in_Debugger.0
> []
>
> It looks very si
On Wed, Nov 26, 2003 at 03:00:35PM +0300, ?? ? ?? wrote:
> i got a panic on recent -CURRENT:
>
> # tcpdump -i lo0 port 23 &
> [1] 507
> listening on lo0
This is a known bug; silby@ is working to fix "lo" and the rest of the
affected network drivers. See PR kern/59576.
Here's
>i got a panic on recent -CURRENT:
># tcpdump -i lo0 port 23 &
>[1] 507
>listening on lo0
># telnet localhost
>Trying ::1...
>Wed Nov 26 14:51:23 MSK 2003
>Debugger+0x55: xchgl %ebx,in_Debugger.0
>db> tr
> Debugger(c0898daf,0,c087197f,d629d8dc,100) at Debugger+0x55
> panic(c087197f,c0854d72,c
On Wednesday 26 November 2003 04:00 am, Дейтер Александр Валериевич wrote:
> i got a panic on recent -CURRENT:
>
> # tcpdump -i lo0 port 23 &
> [1] 507
> listening on lo0
>
> # telnet localhost
> Trying ::1...
>
> Wed Nov 26 14:51:23 MSK 2003
> Debugger+0x55: xchgl %ebx,in_Debugger.0
> db> tr
>
i got a panic on recent -CURRENT:
# tcpdump -i lo0 port 23 &
[1] 507
listening on lo0
# telnet localhost
Trying ::1...
Wed Nov 26 14:51:23 MSK 2003
Debugger+0x55: xchgl %ebx,in_Debugger.0
db> tr
Debugger(c0898daf,0,c087197f,d629d8dc,100) at Debugger+0x55
panic(c087197f,c0854d72,c168bd00,c095c
On 13-Nov-2003 Xin LI/ÀîöÎ wrote:
> Yes I have device apic enabled, and after setting options NO_MIXED_MODE, the
> problem persists. However, fortunatelly, the spurious.patch seemed to solved
> the problem, and the system has been up for 9 hours without panic'ing as I
> described before.
>
> Do y
well?
-Original Message-
From: John Baldwin [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 13, 2003 12:29 AM
To: Xin LI/李鑫
Cc: [EMAIL PROTECTED]
Subject: RE: Recent -CURRENT panic (New interrupt code related?); backtrace
included
> Do you have 'device apic' enabled? If so,
This should be fixed now.
In message <[EMAIL PROTECTED]>, "Alex Deiter" writes:
>Recent i386 CURRENT panic at boot diskless PC:
>
>Mounting root from nfs:
>NFS ROOT: 1.1.1.1:/i386/netboot
>Interface fxp0 IP-Address 1.1.1.2 Broadcast 1.1.1.255
>Loading configuration files.
>Entropy harvesting:
Recent i386 CURRENT panic at boot diskless PC:
Mounting root from nfs:
NFS ROOT: 1.1.1.1:/i386/netboot
Interface fxp0 IP-Address 1.1.1.2 Broadcast 1.1.1.255
Loading configuration files.
Entropy harvesting: interrupts ethernet point_to_point.
Starting file system checks:
cp: utmp: Read-only fil
On 12-Nov-2003 Xin LI/李鑫 wrote:
> Hello,
>
> On recently compiled kernels, I often get panics which seemed to be interrupt
> related. Among
> other things, almost all of them claims that "Kernel trap 30", which seemd to be
> strange.
>
> The kernel I am currently running, namely,
>
> FreeBSD
Hello,
On recently compiled kernels, I often get panics which seemed to be interrupt related.
Among other things, almost all of them claims that "Kernel trap 30", which seemd to be
strange.
The kernel I am currently running, namely,
FreeBSD servers.frontfree.net 5.1-CURRENT FreeBSD 5.1-CURREN
On Wed, Oct 15, 2003 at 01:13:17PM +0400, ?? ? ?? wrote:
> > I think that's due to a recent commit of ume. It might not yet be fixed.
>
> I'm sorry, my src/sys/crypto/rijndael/rijndael-api-fst.c have a version 1.8.
> But last commit ume:
>
> Fix alignment problem on 64 bit ar
> I think that's due to a recent commit of ume. It might not yet be fixed.
I'm sorry, my src/sys/crypto/rijndael/rijndael-api-fst.c have a version 1.8.
But last commit ume:
Fix alignment problem on 64 bit arch.
I only tested if it doesn't break anything on i368. Since I
have no 64 bit machi
On Wed, Oct 15, 2003 at 12:04:57PM +0400, ?? ? ?? wrote:
> Got folowing panic on Netra T1 sparc64:
>
> Timecounters tick every 10.000 msec
> panic: trap: memory address not aligned
> Debugger("panic")
> Stopped at Debugger+0x1c: ta %xcc, 1
> db> trace
> panic
Got folowing panic on Netra T1 sparc64:
Timecounters tick every 10.000 msec
panic: trap: memory address not aligned
Debugger("panic")
Stopped at Debugger+0x1c: ta %xcc, 1
db> trace
panic() at panic+0xf0
trap() at trap+0x394
-- memory address not aligned sfar=0xc037e7c1 sfsr=0x40
19 matches
Mail list logo
