Hi Robert,
> Chances are, if you change an important variable such as memory size, it
> will change the failure mode for this bug. Carefully marking the memory
Sigh.
Looks like you are right. After running the system now for 8 hours,
I got exactly the same crash as before. Again. It's the sam
On Sun, Sep 15, 2002 at 07:56:09PM -0700, David O'Brien wrote:
> On Sun, Sep 15, 2002 at 09:47:28PM +, justin wrote:
> > >> SORRY IF THIS IS A REPEAT!
> >
> > I have recompiled my base the past 2 days now, and pkg_add will segfault
> > signal 10 and core dumps after the second file transfer I
Stefan Farfeleder <[EMAIL PROTECTED]> writes:
> [CC'ing David O'Brien as he did the update to 3.39]
>
> On Tue, Sep 17, 2002 at 09:38:10AM -0700, Lars Eggert wrote:
> > Robert Suetterlin wrote:
> > > I currently upgraded my 4.4 to 4.7-PRE and now tried to get from
> > >there to -CURRENT.
> > >
Hi,
Just to follow up, I tried a few other floppy images, and
succeeded with the floppy images that are part of the 8/31 -CURRENT
snapshot. I can't figure out what the problem was with the newer
floppy images.
--
Craig Rodrigues
http://www.gis.net/~craigr
[EMAIL PROTECTED]
On Tue
uhm, i just got another one. i guess the hd is broken and also managed to
cause the previous panic.
(da0:ahc0:0:0:0): SCB 0x27 - timed out
ahc_pci0: Dumping Card State while idle, at SEQADDR 0x8
ACCUM = 0x47, SINDEX = 0x9e, DINDE
On Tue, Sep 17, 2002 at 11:39:50AM +0200, Robert Suetterlin wrote:
> Hello!
>
> I currently upgraded my 4.4 to 4.7-PRE and now tried to get from
> there to -CURRENT.
>
> Unfortunately ``make buildworld'' fails during stage 2 when building
> ``usr.bin/file'':
> usr/src/usr.bin/file/..
On Tue, Sep 17, 2002 at 07:03:22PM -0600, Kenneth D. Merry wrote:
> On Wed, Sep 18, 2002 at 02:53:49 +0200, [EMAIL PROTECTED] wrote:
> >
> > hi
> >
> > while trying to upgrade a -current box with an older scsi hd a scsi error
> > seemed to have triggered a panic (actually the first ever on that
On Tue, 17 Sep 2002, Martin Blapp wrote:
> If you don't beleave it or not. I've taken out again (I've already
> switched them once) one bank of 512M ram and since then I've not had any
> panics anymore.
>
> Can a ram error occur after a system has been fine one month ?
Chances are, if you ch
walt wrote:
> > This is the TLB problem we all keep talking about...
> > I just got the most recent IA-32 manuals from Intel in the mail,
> > and they still don't seem to be aware of the issue...
>
> Is this an Intel-specific problem, then?
No. AMD has it too.
-- Terry
To Unsubscribe: send ma
On Tue, Sep 17, 2002 at 19:03:22 -0600, Kenneth D. Merry wrote:
> On Wed, Sep 18, 2002 at 02:53:49 +0200, [EMAIL PROTECTED] wrote:
> >
> > hi
> >
> > while trying to upgrade a -current box with an older scsi hd a scsi error
> > seemed to have triggered a panic (actually the first ever on that bo
On Wed, Sep 18, 2002 at 02:53:49 +0200, [EMAIL PROTECTED] wrote:
>
> hi
>
> while trying to upgrade a -current box with an older scsi hd a scsi error
> seemed to have triggered a panic (actually the first ever on that box):
>
> (da0:ahc0:0:0:0): READ(10). CDB: 28 0 0 4b 94 df 0 0 20 0
> (da0:ah
hi
while trying to upgrade a -current box with an older scsi hd a scsi error
seemed to have triggered a panic (actually the first ever on that box):
(da0:ahc0:0:0:0): READ(10). CDB: 28 0 0 4b 94 df 0 0 20 0
(da0:ahc0:0:0:0): CAM Status: SCSI Status Error
(da0:ahc0:0:0:0): SCSI Status: Check Con
Hi,
I bought a second machine to install FreeBSD-current, so that
I can learn how to do kernel debugging via a serial cable.
I cannot install FreeBSD-current on this machine.
The machine is an IBM PIII-450
Here is what I did:
(1) Obtained kern.flp and mfsroot.flp floppy images from the
9/1
Greetings,
Is the Intel Mobile Cardbus cards which are based on the Intel
82550 chips supported under FreeBSD -current using the fxp driver?
Cheers,
Vince - [EMAIL PROTECTED] - Vice President __
Unix Networking Operations - FreeBSD-Real Unix for Free / / / /
Terry Lambert wrote:
> Martin Blapp wrote:
>>Can a ram error occur after a system has been fine one month ?
>
>
> No.
>
> This is the TLB problem we all keep talking about...
> I just got the most recent IA-32 manuals from Intel in the mail,
> and they still don't seem to be aware of the issue
Joe Marcus Clarke wrote:
> I just cvsup'd -CURRENT two hours ago, built world and kernel, then
> rebooted...same as always. Now, nautilus-2.0.7 fails to start with a
> thread abort...
I saw the same error starting last night. Mozilla also.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
Terry Lambert wrote:
> Martin Blapp wrote:
> > If you don't beleave it or not. I've taken out again (I've already
> > switched them once) one bank of 512M ram and since then I've not
> > had any panics anymore.
> >
> > Can a ram error occur after a system has been fine one month ?
>
> No.
Let me
Martin Blapp wrote:
> If you don't beleave it or not. I've taken out again (I've already
> switched them once) one bank of 512M ram and since then I've not
> had any panics anymore.
>
> Can a ram error occur after a system has been fine one month ?
No.
This is the TLB problem we all keep talkin
Hi,
I see now another possibility. I've taken out at the same
time my Radeon 8500, which I'd also used in the previous
system.
I just noted that Michael Reifenberger, which has seen
the same corruption, has - oh wonder -
the same card inside. I'll try again with and without this
card, and with
On 17-Sep-2002 Martin Blapp wrote:
>
> Hi all,
>
> If you don't beleave it or not. I've taken out again (I've already
> switched them once) one bank of 512M ram and since then I've not
> had any panics anymore.
>
> Can a ram error occur after a system has been fine one month ?
Yes.
--
John
Hi all,
If you don't beleave it or not. I've taken out again (I've already
switched them once) one bank of 512M ram and since then I've not
had any panics anymore.
Can a ram error occur after a system has been fine one month ?
Martin
Martin Blapp, <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
-
I just cvsup'd -CURRENT two hours ago, built world and kernel, then
rebooted...same as always. Now, nautilus-2.0.7 fails to start with a
thread abort.
Fatal error '_pq_insert_head: prioq not protected!' at line 185 in file
/usr/src/lib/libc_r/uthread/uthread_priority_queue.c (errno = 22)
Fatal e
[CC'ing David O'Brien as he did the update to 3.39]
On Tue, Sep 17, 2002 at 09:38:10AM -0700, Lars Eggert wrote:
> Robert Suetterlin wrote:
> > I currently upgraded my 4.4 to 4.7-PRE and now tried to get from
> >there to -CURRENT.
> >
> >Unfortunately ``make buildworld'' fails during stage 2
Terry Lambert wrote:
> Nate Lawson wrote:
> > > 0xc02fd315 is in pmap_remove_pages (/usr/src/sys/i386/i386/pmap.c:2941).
> > > 2936#ifdef PMAP_REMOVE_PAGES_CURPROC_ONLY
> > > 2937pte = vtopte(pv->pv_va);
> > > 2938#else
> > > 2939pte = pmap_pte_quick
Nate Lawson wrote:
> On Tue, 17 Sep 2002, Martin Blapp wrote:
> > Hope this helps people. After I've disabled the secondlevel
> > CPU cache, the panic is now always at the same place:
> >
> > 0xc02fd315 is in pmap_remove_pages (/usr/src/sys/i386/i386/pmap.c:2941).
> > 2936#ifdef PMAP_REMOVE_P
Nate Lawson wrote:
> > 0xc02fd315 is in pmap_remove_pages (/usr/src/sys/i386/i386/pmap.c:2941).
> > 2936#ifdef PMAP_REMOVE_PAGES_CURPROC_ONLY
> > 2937pte = vtopte(pv->pv_va);
> > 2938#else
> > 2939pte = pmap_pte_quick(pv->pv_pmap, pv->pv_va);
> > 294
Hi,
> Try building your kernel with "options PMAP_REMOVE_PAGES_CURPROC_ONLY" and
> see if the panic goes away. If that works, the problem is
> pmap_pte_quick().
I'll do ASAP. I'm at work at the moment, and the box in question is
at home :).
Thanks very much for looking into that !
> In looki
On Tue, 17 Sep 2002, Martin Blapp wrote:
> Hope this helps people. After I've disabled the secondlevel
> CPU cache, the panic is now always at the same place:
>
> 0xc02fd315 is in pmap_remove_pages (/usr/src/sys/i386/i386/pmap.c:2941).
> 2936#ifdef PMAP_REMOVE_PAGES_CURPROC_ONLY
> 2937
Robert Suetterlin wrote:
> I currently upgraded my 4.4 to 4.7-PRE and now tried to get from
> there to -CURRENT.
>
> Unfortunately ``make buildworld'' fails during stage 2 when building
> ``usr.bin/file'':
> usr/src/usr.bin/file/../../contrib/file/file.h:45: stdint.h: No such
>
Hi all,
Hope this helps people. After I've disabled the secondlevel
CPU cache, the panic is now always at the same place:
0xc02fd315 is in pmap_remove_pages (/usr/src/sys/i386/i386/pmap.c:2941).
2936#ifdef PMAP_REMOVE_PAGES_CURPROC_ONLY
2937pte = vtopte(pv->pv_va);
2938
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
On my current system updated yesterday, I've hit triple [sic!] panic
doing cvs up of ports tree:
panic: kmem_malloc(4096): kmem_map too small: 22067920 total allocated
syncing disks... panic: bwrite: buffer is no busy???
Uptime: 22m0s
Dumping 64 MB
ata0: reseting devices ..
panic: bremfree: remo
Hi,
> I was seeing random-looking memory corruption on my Athlon box during
> repeated buildworld runs without these options. I've also got 1GB of
> RAM, so the source tree would remain cached in RAM after the first run.
> The memory corruption would show up as damage to random files in the
> s
On 17 Sep, Michael Reifenberger wrote:
> On Tue, 17 Sep 2002, Martin Blapp wrote:
>
>> Date: Tue, 17 Sep 2002 02:29:41 +0200 (CEST)
>> From: Martin Blapp <[EMAIL PROTECTED]>
>> To: [EMAIL PROTECTED]
>> Cc: Michael Reifenberger <[EMAIL PROTECTED]>, Peter Wemm <[EMAIL PROTECTED]>,
>> [EMAIL PR
Hello!
I currently upgraded my 4.4 to 4.7-PRE and now tried to get from
there to -CURRENT.
Unfortunately ``make buildworld'' fails during stage 2 when building
``usr.bin/file'':
usr/src/usr.bin/file/../../contrib/file/file.h:45: stdint.h: No such
file or directory
There
On Tue, 17 Sep 2002, Martin Blapp wrote:
> Date: Tue, 17 Sep 2002 02:29:41 +0200 (CEST)
> From: Martin Blapp <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Cc: Michael Reifenberger <[EMAIL PROTECTED]>, Peter Wemm <[EMAIL PROTECTED]>,
> [EMAIL PROTECTED]
> Subject: Re: filesystem corruption ?
37 matches
Mail list logo
