Re: stuck on TLB IPI wait (CPU#0) at 2.2.17+reiserfs+ide+raid

2000-09-22 Thread Andrew Morton

Andi Kleen wrote:
> 
> On Mon, Sep 18, 2000 at 10:06:37AM -0600, Andreas Dilger wrote:
> > Chris, you write:
> > > > my box sometimes hang up at high load avarage with "stuck on TLB
> > > > IPI wait (CPU#0)" messages.
> > >
> > > This is a known issue with the way reiserfs uses the scheduler task queue.
> > > The following patch from Andi Kleen should take care of it for you:
> > >
> > > --- linux/kernel/sched.c-o  Wed Feb  9 14:27:20 2000
> > > +++ linux/kernel/sched.cWed Mar 29 12:53:41 2000
> > > @@ -803,6 +803,7 @@
> > > goto handle_bh_back;
> > >
> > >  handle_tq_scheduler:
> > > +   __sti();
> > > run_task_queue(_scheduler);
> > > goto tq_scheduler_back;
> >
> > Does this have an impact on the system when not using reiserfs?  What
> > is it that reiserfs does that affects the scheduler?
> 
> reiserfs has a slightly longer tq_scheduler function to do the slow part
> of the end_io handler. Some kernel subsystems enter the scheduler inside
> __cli() and it does no good to execute the reiserfs task queue function
> with interrupts off (causing the stuck on TLB IPI wait messages)

The __sti() can be moved right up to the start of schedule() and
then removed from release_kernel_lock().

Or just find out who is calling schedule() with interrupts disabled
and make them stop it.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



Re: stuck on TLB IPI wait (CPU#0) at 2.2.17+reiserfs+ide+raid

2000-09-22 Thread Andrew Morton

Andi Kleen wrote:
 
 On Mon, Sep 18, 2000 at 10:06:37AM -0600, Andreas Dilger wrote:
  Chris, you write:
my box sometimes hang up at high load avarage with "stuck on TLB
IPI wait (CPU#0)" messages.
  
   This is a known issue with the way reiserfs uses the scheduler task queue.
   The following patch from Andi Kleen should take care of it for you:
  
   --- linux/kernel/sched.c-o  Wed Feb  9 14:27:20 2000
   +++ linux/kernel/sched.cWed Mar 29 12:53:41 2000
   @@ -803,6 +803,7 @@
   goto handle_bh_back;
  
handle_tq_scheduler:
   +   __sti();
   run_task_queue(tq_scheduler);
   goto tq_scheduler_back;
 
  Does this have an impact on the system when not using reiserfs?  What
  is it that reiserfs does that affects the scheduler?
 
 reiserfs has a slightly longer tq_scheduler function to do the slow part
 of the end_io handler. Some kernel subsystems enter the scheduler inside
 __cli() and it does no good to execute the reiserfs task queue function
 with interrupts off (causing the stuck on TLB IPI wait messages)

The __sti() can be moved right up to the start of schedule() and
then removed from release_kernel_lock().

Or just find out who is calling schedule() with interrupts disabled
and make them stop it.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



Re: stuck on TLB IPI wait (CPU#0) at 2.2.17+reiserfs+ide+raid

2000-09-19 Thread Hisaaki Shibata

Thanks, Chris Mason,

> > few weeks ago, I installed a PROMISE Ultra66 IDE card into my SMP Linux
> > box. But my box sometimes hang up at high load average with "stuck on TLB
> > IPI wait (CPU#0)" messages.

> > My kernel is linux-2.2.17 with following patches.
> > linux-2.2.17-reiserfs-3.5.25-patch.gz
> > ide.2.2.17.all.2904.patch.bz2
> > raid-2.2.17-A0

> This is a known issue with the way reiserfs uses the scheduler task queue.
> The following patch from Andi Kleen should take care of it for you:
> 
> --- linux/kernel/sched.c-oWed Feb  9 14:27:20 2000
> +++ linux/kernel/sched.c  Wed Mar 29 12:53:41 2000
> @@ -803,6 +803,7 @@
>   goto handle_bh_back;
>  
>  handle_tq_scheduler:
> + __sti(); 
>   run_task_queue(_scheduler);
>   goto tq_scheduler_back;

After using this patch, My linux box work very well with high load average
and heavy disk access application like encoding MP3s.

Thank you very much and best regards,

-- 
 W  [EMAIL PROTECTED]
 |O-O|  Hisaaki Shibata @ Fukuoka-shi JAPAN
0(mmm)0 P-mail: 070-5419-3233IRC: #luky
   ~http://his.luky.org/ last update:2000.3.12
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



Re: stuck on TLB IPI wait (CPU#0) at 2.2.17+reiserfs+ide+raid

2000-09-19 Thread Hisaaki Shibata

Thanks, Chris Mason,

  few weeks ago, I installed a PROMISE Ultra66 IDE card into my SMP Linux
  box. But my box sometimes hang up at high load average with "stuck on TLB
  IPI wait (CPU#0)" messages.

  My kernel is linux-2.2.17 with following patches.
  linux-2.2.17-reiserfs-3.5.25-patch.gz
  ide.2.2.17.all.2904.patch.bz2
  raid-2.2.17-A0

 This is a known issue with the way reiserfs uses the scheduler task queue.
 The following patch from Andi Kleen should take care of it for you:
 
 --- linux/kernel/sched.c-oWed Feb  9 14:27:20 2000
 +++ linux/kernel/sched.c  Wed Mar 29 12:53:41 2000
 @@ -803,6 +803,7 @@
   goto handle_bh_back;
  
  handle_tq_scheduler:
 + __sti(); 
   run_task_queue(tq_scheduler);
   goto tq_scheduler_back;

After using this patch, My linux box work very well with high load average
and heavy disk access application like encoding MP3s.

Thank you very much and best regards,

-- 
 W  [EMAIL PROTECTED]
 |O-O|  Hisaaki Shibata @ Fukuoka-shi JAPAN
0(mmm)0 P-mail: 070-5419-3233IRC: #luky
   ~http://his.luky.org/ last update:2000.3.12
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



Re: stuck on TLB IPI wait (CPU#0) at 2.2.17+reiserfs+ide+raid

2000-09-18 Thread Andi Kleen

On Mon, Sep 18, 2000 at 10:06:37AM -0600, Andreas Dilger wrote:
> Chris, you write:
> > > my box sometimes hang up at high load avarage with "stuck on TLB
> > > IPI wait (CPU#0)" messages.
> > 
> > This is a known issue with the way reiserfs uses the scheduler task queue.
> > The following patch from Andi Kleen should take care of it for you:
> > 
> > --- linux/kernel/sched.c-o  Wed Feb  9 14:27:20 2000
> > +++ linux/kernel/sched.cWed Mar 29 12:53:41 2000
> > @@ -803,6 +803,7 @@
> > goto handle_bh_back;
> >  
> >  handle_tq_scheduler:
> > +   __sti(); 
> > run_task_queue(_scheduler);
> > goto tq_scheduler_back;
> 
> Does this have an impact on the system when not using reiserfs?  What
> is it that reiserfs does that affects the scheduler?

reiserfs has a slightly longer tq_scheduler function to do the slow part
of the end_io handler. Some kernel subsystems enter the scheduler inside 
__cli() and it does no good to execute the reiserfs task queue function
with interrupts off (causing the stuck on TLB IPI wait messages)

-Andi

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



Re: stuck on TLB IPI wait (CPU#0) at 2.2.17+reiserfs+ide+raid

2000-09-18 Thread Andreas Dilger

Chris, you write:
> > my box sometimes hang up at high load avarage with "stuck on TLB
> > IPI wait (CPU#0)" messages.
> 
> This is a known issue with the way reiserfs uses the scheduler task queue.
> The following patch from Andi Kleen should take care of it for you:
> 
> --- linux/kernel/sched.c-oWed Feb  9 14:27:20 2000
> +++ linux/kernel/sched.c  Wed Mar 29 12:53:41 2000
> @@ -803,6 +803,7 @@
>   goto handle_bh_back;
>  
>  handle_tq_scheduler:
> + __sti(); 
>   run_task_queue(_scheduler);
>   goto tq_scheduler_back;

Does this have an impact on the system when not using reiserfs?  What
is it that reiserfs does that affects the scheduler?

Cheers, Andreas
-- 
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/   -- Dogbert
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



Re: stuck on TLB IPI wait (CPU#0) at 2.2.17+reiserfs+ide+raid

2000-09-18 Thread Chris Mason



--On 09/16/00 10:53:04 +0900 Hisaaki Shibata <[EMAIL PROTECTED]> wrote:

> Hi!
> 
> few weeks ago, I installed a PROMISE Ultra66 IDE card into my SMP Linux
> box. But my box sometimes hang up at high load avarage with "stuck on TLB
> IPI wait (CPU#0)" messages.
> I upgrade my kernel to 2.2.17 but it also hangs.
> 
> My kernel is linux-2.2.17 with following pathes.
> linux-2.2.17-reiserfs-3.5.25-patch.gz
> ide.2.2.17.all.2904.patch.bz2
> raid-2.2.17-A0
> 
> Without reiserFS and ide patch, My box worked very well at 2.2.16+raid
> patch.
> 
> Please show me what to report to contribute to kernel hackers.
> 

This is a known issue with the way reiserfs uses the scheduler task queue.
The following patch from Andi Kleen should take care of it for you:

--- linux/kernel/sched.c-o  Wed Feb  9 14:27:20 2000
+++ linux/kernel/sched.cWed Mar 29 12:53:41 2000
@@ -803,6 +803,7 @@
goto handle_bh_back;
 
 handle_tq_scheduler:
+   __sti(); 
run_task_queue(_scheduler);
goto tq_scheduler_back;







-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



Re: stuck on TLB IPI wait (CPU#0) at 2.2.17+reiserfs+ide+raid

2000-09-18 Thread Andi Kleen

On Mon, Sep 18, 2000 at 10:06:37AM -0600, Andreas Dilger wrote:
 Chris, you write:
   my box sometimes hang up at high load avarage with "stuck on TLB
   IPI wait (CPU#0)" messages.
  
  This is a known issue with the way reiserfs uses the scheduler task queue.
  The following patch from Andi Kleen should take care of it for you:
  
  --- linux/kernel/sched.c-o  Wed Feb  9 14:27:20 2000
  +++ linux/kernel/sched.cWed Mar 29 12:53:41 2000
  @@ -803,6 +803,7 @@
  goto handle_bh_back;
   
   handle_tq_scheduler:
  +   __sti(); 
  run_task_queue(tq_scheduler);
  goto tq_scheduler_back;
 
 Does this have an impact on the system when not using reiserfs?  What
 is it that reiserfs does that affects the scheduler?

reiserfs has a slightly longer tq_scheduler function to do the slow part
of the end_io handler. Some kernel subsystems enter the scheduler inside 
__cli() and it does no good to execute the reiserfs task queue function
with interrupts off (causing the stuck on TLB IPI wait messages)

-Andi

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



stuck on TLB IPI wait (CPU#0) at 2.2.17+reiserfs+ide+raid

2000-09-15 Thread Hisaaki Shibata

Hi!

few weeks ago, I installed a PROMISE Ultra66 IDE card into my SMP Linux box.
But my box sometimes hang up at high load avarage with "stuck on TLB IPI
wait (CPU#0)" messages.
I upgrade my kernel to 2.2.17 but it also hangs.

My kernel is linux-2.2.17 with following pathes.
linux-2.2.17-reiserfs-3.5.25-patch.gz
ide.2.2.17.all.2904.patch.bz2
raid-2.2.17-A0

Without reiserFS and ide patch, My box worked very well at 2.2.16+raid patch.

Please show me what to report to contribute to kernel hackers.


Some infomation;
=
/proc/ide/pdc202xx 

PDC20262 Chipset.
--- General Status ---
Burst Mode   : enabled
Host Mode: Normal
Bus Clocking : 33 PCI Internal
IO pad select: 4 mA
Status Polling Period: 0
Interrupt Check Status Polling Delay : 0
--- Primary Channel  Secondary Channel ---
enabled  enabled 
66 Clocking enabled  enabled 
   Mode MASTER  Mode MASTER
FIFO Empty   FIFO Empty  
--- drive0 - drive1  drive0 -- drive1 
DMA enabled:yes  no  yes   no 
DMA Mode:   UDMA 4   NOTSET  UDMA 4NOTSET
PIO Mode:   PIO 4NOTSET   PIO 4NOTSET

=
/proc/mdstat 

Personalities : [raid1] 
read_ahead 1024 sectors
md0 : active raid1 hdg4[1] hde4[0] 15607040 blocks [2/2] [UU] resync=34%
 finish=110.1min
unused devices: 

=
/proc/version
 
Linux version 2.2.17-reiserfs-3.5.25-ide.all.2904-RAID ([EMAIL PROTECTED])
 (gcc version 2.95.3 19991030 (prerelease)) #2 SMP Sat Sep 9 17:44:48 JST 2000

=
/proc/interrupts 

   CPU0   CPU1   
  0: 195968 196009IO-APIC-edge  timer
  1:301276IO-APIC-edge  keyboard
  2:  0  0  XT-PIC  cascade
  8:  0  1IO-APIC-edge  rtc
 13:  1  0  XT-PIC  fpu
 15:  0  0IO-APIC-edge  ide1
 16: 271935 271902   IO-APIC-level  ide2, ide3
 17:   2200   2085   IO-APIC-level  eth0
 18:  7  7   IO-APIC-level  ncr53c8xx
NMI:  0
ERR:  0

=
/proc/modules 

nfsd  144996   8 (autoclean)
lockd  32712   0 (autoclean) [nfsd]
sunrpc 56004   0 (autoclean) [nfsd lockd]
eepro100   16568   1 (autoclean)
raid1   8292   1
ncr53c8xx  53392   0 (unused)
sd_mod 17512   0 (unused)
scsi_mod   61880   2 [ncr53c8xx sd_mod]



Best Regards,

-- 
 W  [EMAIL PROTECTED]
 |O-O|  Hisaaki Shibata @ Fukuoka-shi, JAPAN
0(mmm)0 P-mail: 070-5419-3233IRC: #luky
   ~http://his.luky.org/ last update:2000.3.12
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



stuck on TLB IPI wait (CPU#0) at 2.2.17+reiserfs+ide+raid

2000-09-15 Thread Hisaaki Shibata

Hi!

few weeks ago, I installed a PROMISE Ultra66 IDE card into my SMP Linux box.
But my box sometimes hang up at high load avarage with "stuck on TLB IPI
wait (CPU#0)" messages.
I upgrade my kernel to 2.2.17 but it also hangs.

My kernel is linux-2.2.17 with following pathes.
linux-2.2.17-reiserfs-3.5.25-patch.gz
ide.2.2.17.all.2904.patch.bz2
raid-2.2.17-A0

Without reiserFS and ide patch, My box worked very well at 2.2.16+raid patch.

Please show me what to report to contribute to kernel hackers.


Some infomation;
=
/proc/ide/pdc202xx 

PDC20262 Chipset.
--- General Status ---
Burst Mode   : enabled
Host Mode: Normal
Bus Clocking : 33 PCI Internal
IO pad select: 4 mA
Status Polling Period: 0
Interrupt Check Status Polling Delay : 0
--- Primary Channel  Secondary Channel ---
enabled  enabled 
66 Clocking enabled  enabled 
   Mode MASTER  Mode MASTER
FIFO Empty   FIFO Empty  
--- drive0 - drive1  drive0 -- drive1 
DMA enabled:yes  no  yes   no 
DMA Mode:   UDMA 4   NOTSET  UDMA 4NOTSET
PIO Mode:   PIO 4NOTSET   PIO 4NOTSET

=
/proc/mdstat 

Personalities : [raid1] 
read_ahead 1024 sectors
md0 : active raid1 hdg4[1] hde4[0] 15607040 blocks [2/2] [UU] resync=34%
 finish=110.1min
unused devices: none

=
/proc/version
 
Linux version 2.2.17-reiserfs-3.5.25-ide.all.2904-RAID ([EMAIL PROTECTED])
 (gcc version 2.95.3 19991030 (prerelease)) #2 SMP Sat Sep 9 17:44:48 JST 2000

=
/proc/interrupts 

   CPU0   CPU1   
  0: 195968 196009IO-APIC-edge  timer
  1:301276IO-APIC-edge  keyboard
  2:  0  0  XT-PIC  cascade
  8:  0  1IO-APIC-edge  rtc
 13:  1  0  XT-PIC  fpu
 15:  0  0IO-APIC-edge  ide1
 16: 271935 271902   IO-APIC-level  ide2, ide3
 17:   2200   2085   IO-APIC-level  eth0
 18:  7  7   IO-APIC-level  ncr53c8xx
NMI:  0
ERR:  0

=
/proc/modules 

nfsd  144996   8 (autoclean)
lockd  32712   0 (autoclean) [nfsd]
sunrpc 56004   0 (autoclean) [nfsd lockd]
eepro100   16568   1 (autoclean)
raid1   8292   1
ncr53c8xx  53392   0 (unused)
sd_mod 17512   0 (unused)
scsi_mod   61880   2 [ncr53c8xx sd_mod]



Best Regards,

-- 
 W  [EMAIL PROTECTED]
 |O-O|  Hisaaki Shibata @ Fukuoka-shi, JAPAN
0(mmm)0 P-mail: 070-5419-3233IRC: #luky
   ~http://his.luky.org/ last update:2000.3.12
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/