> > Hi, > > The problem reproduces on a 2.4.18-19 kernel as well. Took > some more time but finally it roared its ugly head. > > This is the stack trace from the new kernel: > > > c01190b8 f3791eb4 set_running_and_schedule > > c010a8b0 f3791ed0 enable_irq > > c014200c f3791f0c IO_APIC_get_PCI_irq_vector > > c0155595 f3791f0c clear_inode > > c01556639 f3791f60 invalidate_inodes > > c0149629 f3791f8 set_binfmt > > c0157c58 f3791f94 sys_umount > > c0108cab 0f3791fc0 sys_sigaltstack > > > Andrew Morton suggested a buffer.c patch for reducing search > complexity, which I will try next. > > Any further comments/suggestions are welcome > > > > -----Original Message----- > > From: Arjan van de Ven [mailto:arjanv@redhat.com] > > Sent: Thursday, January 09, 2003 1:58 AM > > To: yuval yeret > > Cc: linux-kernel@vger.kernel.org; Yuval Yeret > > Subject: Re: 2.4.18-14 kernel stuck during ext3 umount with ping > > stillresponding > > > > > > On Thu, 2003-01-09 at 10:38, yuval yeret wrote: > > > Hi, > > > > > > I'm running a 2.4.18-14 kernel with a heavy IO profile > > using ext3 over RAID > > > 0+1 volumes. > > > > > > >From time to time I get a black screen stuck machine while > > trying to umount > > > a volume during an IO workload (as part of a failback > > solution - but after > > > killing all IO processes ), with ping still responding, but > > everything else > > > mostly dead. > > > > > > > > I'm hoping the ext3fix.patch will solve this problem... am > > trying that now. > > > > this got fixed in the recent erratum kernel 2.4.18-19.8.0 > > > _______________________________________________ Ext3-users@redhat.com https://listman.redhat.com/mailman/listinfo/ext3-users
