mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Con Kolivas <conman@kolivas.net>
To: linux-kernel@vger.kernel.org
Subject: Wrong priority reporting with new 0(1) scheduler;  USB changes to 2.4.18 pre/rc1 breaks HPOJ
Date: Sat, 16 Feb 2002 01:29:41 +1100	[thread overview]
Message-ID: <20020215142941.79B12942@pc.kolivas.net> (raw)

Priority reporting issue:

I've applied the 0(1) scheduler patch in conjunction with the preemptible 
patch to 2.4.18 pre (sched-O1-2.4.18-pre8-K3.patch and 
preempt-kernel-rml-2.4.18-rc1-ingo-K3-1.patch)

I found that top and other process managers (like kpm) report the priority as 
9 instead of 0 for nice level 0 applications with the preemptible patch, and 
15 with both preemptible and 0(1). Nice'd applications can have their 
priority reported as high as 39. It seems to read it as 15-20 higher than 
the nice value. The kernel appears to work flawlessly otherwise.


USB issue:

The USB changes after 2.4.17 up to and including 2.4.18 rc1 cause the hp 
officejet drivers to fail on my machine. While the usb mouse continues to 
work, the hp ptal-init probe cannot find the device when scanning 
/dev/usb/lp0. The device is still reported correctly in 
/proc/bus/usb/devices. This is with both the usb-uhci and the uhci drivers.

Hardware configuration:
Soltek 65KV apollo pro via motherboard with PIII 933. HP Officejet G55.

Regards,
Con Kolivas

(Please cc: me if any correspondence is appropriate as I am not subscribed to 
lkml)

             reply	other threads:[~2002-02-15 14:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-15 14:29 Con Kolivas [this message]
2002-02-15 16:00 ` Greg KH

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=20020215142941.79B12942@pc.kolivas.net \
    --to=conman@kolivas.net \
    --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

all inboxes | Powered by JetHome®