public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ed Tomlinson <edt@aei.ca>
To: Jens Axboe <axboe@suse.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Time sliced CFQ #2
Date: Sun, 5 Dec 2004 12:58:28 -0500	[thread overview]
Message-ID: <200412051258.28914.edt@aei.ca> (raw)
In-Reply-To: <20041205151840.GE6430@suse.de>

On Sunday 05 December 2004 10:18, Jens Axboe wrote:
> On Sun, Dec 05 2004, Ed Tomlinson wrote:
> > Jens,
> > 
> > Booting 10-rc3 with this patch applied hangs when I su from root
> > to my working user.  Same kernel without elevator=cfq works.   By
> > hangs I mean that the su does not complete nor do logins to other
> > ids work.  The sysrq keys are active.  
> > 
> > Please let me know what other info will help.
> 
> What type of storage is involved, that's the main question?

IDE.  Just in case this is from the 10-rc3 boot with the default scheduler.  

Dec  5 09:25:17 bert kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
Dec  5 09:25:17 bert kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Dec  5 09:25:17 bert kernel: PIIX4: IDE controller at PCI slot 0000:00:14.1
Dec  5 09:25:17 bert kernel: PIIX4: chipset revision 1
Dec  5 09:25:17 bert kernel: PIIX4: not 100%% native mode: will probe irqs later
Dec  5 09:25:17 bert kernel:     ide0: BM-DMA at 0x10e0-0x10e7, BIOS settings: hda:DMA, hdb:pio
Dec  5 09:25:17 bert kernel:     ide1: BM-DMA at 0x10e8-0x10ef, BIOS settings: hdc:DMA, hdd:DMA
Dec  5 09:25:17 bert kernel: hda: Maxtor 6Y080L0, ATA DISK drive
Dec  5 09:25:17 bert kernel: elevator: using anticipatory as default io scheduler
Dec  5 09:25:17 bert kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Dec  5 09:25:17 bert kernel: hdc: HL-DT-ST RW/DVD GCC-4480B, ATAPI CD/DVD-ROM drive
Dec  5 09:25:17 bert kernel: hdd: HP COLORADO 20GB, ATAPI TAPE drive
Dec  5 09:25:17 bert kernel: ide1 at 0x170-0x177,0x376 on irq 15

Using udma2.

Ed

  reply	other threads:[~2004-12-05 17:58 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-04 10:49 [PATCH] Time sliced CFQ #2 Jens Axboe
2004-12-04 16:39 ` Jeff Sipek
2004-12-05 18:58   ` Jens Axboe
2004-12-06  0:29     ` Jeff Sipek
2004-12-06  1:59       ` Con Kolivas
2004-12-06  2:23         ` Jeff Sipek
2004-12-06  2:34           ` Con Kolivas
2004-12-06  5:00             ` Kyle Moffett
2004-12-06  5:14               ` Robert Love
2004-12-06  7:19                 ` Jens Axboe
2004-12-06 12:18                   ` Helge Hafting
2004-12-06 12:24                     ` Jens Axboe
2004-12-06 12:21                 ` Kyle Moffett
2004-12-06 16:42                   ` Robert Love
2004-12-06 17:42                     ` P
2004-12-06  7:15               ` Jens Axboe
2004-12-06  7:13       ` Jens Axboe
2004-12-05 14:21 ` Ed Tomlinson
2004-12-05 15:18   ` Jens Axboe
2004-12-05 17:58     ` Ed Tomlinson [this message]
2004-12-06  9:31 ` Prakash K. Cheemplavam
2004-12-06  9:35   ` Jens Axboe
2004-12-06 11:48     ` Ed Tomlinson
2004-12-06 12:31     ` Prakash K. Cheemplavam
2004-12-06 13:27       ` [PATCH] Time sliced CFQ #3 Jens Axboe
2004-12-06 14:01         ` Søren Lott
2004-12-06 15:01           ` Jens Axboe
2004-12-06 15:45             ` Jens Axboe
2004-12-06 15:07         ` Prakash K. Cheemplavam
2004-12-06 23:30         ` Ed Tomlinson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200412051258.28914.edt@aei.ca \
    --to=edt@aei.ca \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox