Re: Panic: Initiate_write_inodeblock_ufs1: already started

2003-01-05 Thread phk
In message 063601c2b4d0$ff02dc50$471b3dd4@dual, Willem Jan Withagen writes:
Recompiled the kernel (GENERIC) and installed.

But now it panics on:
Initiate_write_inodeblock_ufs1: already started.

When does it panic ?  in the boot sequence ?  after ?  

Can you get me the first 4-5 lines of the output from trace ?

-- 
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Panic: Initiate_write_inodeblock_ufs1: already started

2003-01-05 Thread David O'Brien
On Sun, Jan 05, 2003 at 05:01:15PM +0100, [EMAIL PROTECTED] wrote:
 In message 063601c2b4d0$ff02dc50$471b3dd4@dual, Willem Jan Withagen writes:
 But now it panics on:
 Initiate_write_inodeblock_ufs1: already started.
 
 When does it panic ?  in the boot sequence ?  after ?  

After about 24 hrs for me.
 
 Can you get me the first 4-5 lines of the output from trace ?

(kgdb) bt
#0  0xc01ccb5b in doadump ()
#1  0xc01cd05e in boot ()
#2  0xc01cd309 in panic ()
#3  0xc028aaf2 in initiate_write_inodeblock_ufs1 ()
#4  0xc028a500 in softdep_disk_io_initiation ()
#5  0xc019bb79 in spec_strategy ()
#6  0xc019ae18 in spec_vnoperate ()
#7  0xc020cdd3 in bwrite ()
#8  0xc020e270 in vfs_bio_awrite ()
#9  0xc019b937 in spec_fsync ()
#10 0xc019ae18 in spec_vnoperate ()
#11 0xc021ca24 in sched_sync ()
#12 0xc01b9f25 in fork_exit ()

Sorry already built a new kernel, so I don't have kernel.debug any longer.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Panic: Initiate_write_inodeblock_ufs1: already started

2003-01-05 Thread phk
In message [EMAIL PROTECTED], David O'Brien writes:
On Sun, Jan 05, 2003 at 05:01:15PM +0100, [EMAIL PROTECTED] wrote:
 In message 063601c2b4d0$ff02dc50$471b3dd4@dual, Willem Jan Withagen writes:
 But now it panics on:
 Initiate_write_inodeblock_ufs1: already started.
 
 When does it panic ?  in the boot sequence ?  after ?  

After about 24 hrs for me.

Ok, I just found another stupid bug and committed a fix.

Can I get you (and others who see this) to upgrade your
sources so you have rev 1.351 of kern/vfs_bio.c ?

-- 
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message