Re: Softupdate panic: softdep_update_inodeblock: update failed
On 12 Sep, Martin Blapp wrote: > Just a thought ... What type of disks are you using? I'm running SCSI >> here. > > ATA ... But I should see disk errors then ... > > I've bought now new disks and will try to build on them. It's not that I think your hardware is defective. I'm wondering if differences in the disk driver code and differences in the I/O completion order might be the reason that you are seeing problems but I am not. There also may be code modifications that were committed at about the same time as the compiler upgrade that are causing the problems that you are seeing. A binary search between a version of the source that was working for you and a version that exhibits these errors would probably be informative, but that would be a fairly major undertaking. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Softupdate panic: softdep_update_inodeblock: update failed
Hi, > > options DISABLE_PSE > options DISABLE_PG_G I use that too. With them enabled I see memory corruption. > Just a thought ... What type of disks are you using? I'm running SCSI > here. ATA ... But I should see disk errors then ... I've bought now new disks and will try to build on them. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Softupdate panic: softdep_update_inodeblock: update failed
On 12 Sep, Martin Blapp wrote: > > Hi, > >> If I were you I'd start swapping memory modules, because I'm not having > > Already did that. I even used ECC ram. > >> any trouble with -CURRENT and I havn't seen anyone else having trouble. > > Did you try to build a huge project ? If I don't compile anything big > and load the machine it works perfectly. > >> Did you compile your kernel with any wierd optimizations? > > No. > > And this system works perfectly before after I turned on PG_G. > > The instability began after gcc3.2 import. I've haven't had any trouble building and running openoffice since the 3.2 import. I had to add the following kernel options: options DISABLE_PSE options DISABLE_PG_G because I was seeing memory corruption after the system had been in use for a while. If I ran a number of "make buildworld" runs one after another, I'd start seeing compile errors after about five or six buildworld runs. I never saw any kernel panics either with or without these options, ether doing system rebuilds or building openoffice. I last cvsup'ed and rebuilt the system about three days ago. Since then, the only problems I've had are a few warnings about lock order reversals and kernel malloc calls with locks held, and some problems that the DEBUG_VFS_LOCKS option found in the nfs client code. Just a thought ... What type of disks are you using? I'm running SCSI here. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Softupdate panic: softdep_update_inodeblock: update failed
Hi, > > Oh ok, wierd... I've only tried (unsuccessfully, the compiler errors out) > > kde3, and some make worlds and stuff. I guess that's not strenuous enough. > > kde3 compiled okay for me with Alexander Kabaev's gcc patch posted to > this ML. I could compile KDE, XFree86 and make buildworld on this box without a problem with Alexanders patches. They just don't seem to be that big as OpenOffice. And OO uses threaded programs to build. (6,8 billion of code with mozilla not counting). Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Softupdate panic: softdep_update_inodeblock: update failed
Kenneth Culver wrote: > Oh ok, wierd... I've only tried (unsuccessfully, the compiler errors out) > kde3, and some make worlds and stuff. I guess that's not strenuous enough. kde3 compiled okay for me with Alexander Kabaev's gcc patch posted to this ML. Regards, -- Michael Nottebrock "And the reasons? There are no reasons." msg42906/pgp0.pgp Description: PGP signature
Re: Softupdate panic: softdep_update_inodeblock: update failed
Oh ok, wierd... I've only tried (unsuccessfully, the compiler errors out) kde3, and some make worlds and stuff. I guess that's not strenuous enough. Ken On Thu, 12 Sep 2002, Martin Blapp wrote: > > Hi, > > > If I were you I'd start swapping memory modules, because I'm not having > > Already did that. I even used ECC ram. > > > any trouble with -CURRENT and I havn't seen anyone else having trouble. > > Did you try to build a huge project ? If I don't compile anything big > and load the machine it works perfectly. > > > Did you compile your kernel with any wierd optimizations? > > No. > > And this system works perfectly before after I turned on PG_G. > > The instability began after gcc3.2 import. > > Martin > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Softupdate panic: softdep_update_inodeblock: update failed
It may not be memory corruption. I get this panic on various versions of STABLE on different pieces of hardware. See 42235 and 42277. -Kip --- Martin Blapp <[EMAIL PROTECTED]> wrote: > > Hi, > > > If I were you I'd start swapping memory modules, > because I'm not having > > Already did that. I even used ECC ram. > > > any trouble with -CURRENT and I havn't seen anyone > else having trouble. > > Did you try to build a huge project ? If I don't > compile anything big > and load the machine it works perfectly. > > > Did you compile your kernel with any wierd > optimizations? > > No. > > And this system works perfectly before after I > turned on PG_G. > > The instability began after gcc3.2 import. > > Martin > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of > the message > > __ Yahoo! - We Remember 9-11: A tribute to the more than 3,000 lives lost http://dir.remember.yahoo.com/tribute To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Softupdate panic: softdep_update_inodeblock: update failed
Hi, > If I were you I'd start swapping memory modules, because I'm not having Already did that. I even used ECC ram. > any trouble with -CURRENT and I havn't seen anyone else having trouble. Did you try to build a huge project ? If I don't compile anything big and load the machine it works perfectly. > Did you compile your kernel with any wierd optimizations? No. And this system works perfectly before after I turned on PG_G. The instability began after gcc3.2 import. Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Softupdate panic: softdep_update_inodeblock: update failed
> I just got thisone ... This is CURRENT from 2 hours ago. > > Dammnit. Is this mem corruption ? > If I were you I'd start swapping memory modules, because I'm not having any trouble with -CURRENT and I havn't seen anyone else having trouble. Did you compile your kernel with any wierd optimizations? Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Softupdate panic: softdep_update_inodeblock: update failed
I just got thisone ... This is CURRENT from 2 hours ago.
Dammnit. Is this mem corruption ?
#10 0xc01edb18 in panic (fmt=0x0) at /usr/src/sys/kern/kern_shutdown.c:479
#11 0xc02b3539 in softdep_update_inodeblock (ip=0xce432300, bp=0xd878cc84,
waitfor=0) at /usr/src/sys/ufs/ffs/ffs_softdep.c:4672
#12 0xc02a7648 in ffs_update (vp=0xcedaede0, waitfor=0)
at /usr/src/sys/ufs/ffs/ffs_inode.c:109
#13 0xc02bce8c in ufs_inactive (ap=0x0) at /usr/src/sys/ufs/ufs/ufs_inode.c:121
#14 0xc02c354b in ufs_vnoperate (ap=0x0)
at /usr/src/sys/ufs/ufs/ufs_vnops.c:2724
#15 0xc02322ed in vrele (vp=0xcedaede0) at vnode_if.h:906
#16 0xc023af4d in vn_close (vp=0xcedaede0, flags=0, file_cred=0x0, td=0x0)
at /usr/src/sys/kern/vfs_vnops.c:319
#17 0xc023bc62 in vn_closefile (fp=0x0, td=0xcc383e40)
at /usr/src/sys/kern/vfs_vnops.c:884
#18 0xc01d49db in fdrop_locked (fp=0xcc361ca8, td=0xcc383e40) at file.h:256
#19 0xc01d46f5 in fdrop (fp=0xcc361ca8, td=0xcc383e40)
at /usr/src/sys/kern/kern_descrip.c:1637
#20 0xc01d46ab in closef (fp=0xcc361ca8, td=0xcc3
at /usr/src/sys/kern/kern_descrip.c:1623
#21 0xc01d309b in close (td=0xcc383e40, uap=0x0)
at /usr/src/sys/kern/kern_descrip.c:832
#22 0xc03008b4 in syscall (frame=
{tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 0, tf_esi = 672319120, tf_eb
p = -1077943144, tf_isp = -391561868, tf_ebx = 672240892, tf_edx = 24, tf_ecx =
0, tf_eax = 6, tf_trapno = 12, tf_err = 2, tf_eip = 671844223, tf_cs = 31, tf_ef
lags = 518, tf_esp = -1077943172, tf_ss = 47})
at /usr/src/sys/i386/i386/trap.c:1050
#23 0xc02f36cd in Xint0x80_syscall () at {standard input}:140
(kgdb) list
4667FREE_LOCK(&lk);
4668if (gotit &&
4669(error = BUF_WRITE(inodedep->id_buf)) != 0)
4670softdep_error("softdep_update_inodeblock: bwrite", error
);
4671if ((inodedep->id_state & DEPCOMPLETE) == 0)
4672panic("softdep_update_inodeblock: update failed");
4673}
4674
4675/*
4676 * Merge the a new inode dependency list (such as id_newinoupdt) into an
(kgdb) p inodedep->id_state
There is no member named id_state.
type = struct inodedep {
struct worklist id_list;
struct {
struct inodedep *le_next;
struct inodedep **le_prev;
} id_hash;
struct fs *id_fs;
ino_t id_ino;
nlink_t id_nlinkdelta;
struct {
struct inodedep *le_next;
struct inodedep **le_prev;
} id_deps;
struct buf *id_buf;
long int id_savedextsize;
off_t id_savedsize;
struct workhead id_pendinghd;
struct workhead id_bufwait;
struct workhead id_inowait;
struct allocdirectlst id_inoupdt;
struct allocdirectlst id_newinoupdt;
struct allocdirectlst id_extupdt;
struct allocdirectlst id_newextupdt;
union {
(kgdb) p gotit
$6 = -834460928
(kgdb) p inodedep->id_buf
---Can't read userspace from dump, or kernel process---
(kgdb) p inodedep
$7 = (struct inodedep *) 0x0
Huh. What's going on here ?
Martin
Martin Blapp, <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
ImproWare AG, UNIXSP & ISP, Zurlindenstrasse 29, 4133 Pratteln, CH
Phone: +41 061 826 93 00: +41 61 826 93 01
PGP:
PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E
--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
