Bug 29573

Summary:

erroneous IRQ conflict message

Product:

[Retired] Red Hat Linux

Reporter:

Ed Ewing <ed>

Component:

kernel

Assignee:

Tim Waugh <twaugh>

Status:

CLOSED RAWHIDE

QA Contact:

David Lawrence <dkl>

Severity:

low

Docs Contact:

Priority:

low

Version:

7.1

CC:

ilchuk

Target Milestone:

---

Target Release:

---

Hardware:

i386

OS:

Linux

Whiteboard:

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2001-04-06 16:36:07 UTC

Type:

---

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Attachments:

Description	Flags
linux-sema.patch	none

Description Ed Ewing 2001-02-26 17:49:06 UTC

When lpd starts it scans all ports and then reports irq conflict. Have
added irq=none to modules.conf with no change on startup. Fisher beta did
not have this problem although lpd didn't start on boot.

One other note: there is no installed /proc/parport directory.

Thanks

Comment 1 Glen Foster 2001-02-26 23:22:57 UTC

This looks more like a kernel issue rather than an LPRng issue.

Comment 2 Tim Waugh 2001-02-27 15:13:59 UTC

Yes, the message is incorrect and should be ignored.
/proc/parport has moved to /proc/sys/dev/parport, and the ports have names
'parport0', 'parport1', instead of '0', '1', etc.

Comment 3 Ed Ewing 2001-02-27 15:30:56 UTC

I would like to ignore the error message but printing a simple page takes 
anywhere from 1 to 2 minutes

Comment 4 Tim Waugh 2001-02-27 15:34:20 UTC

If you print a page of text by printing directly to the port, is that slow too?

cat textfile > /dev/lp0

Also, is it consistently slow, or does print normally and then stall?

Comment 5 Tim Waugh 2001-02-27 15:36:27 UTC

See also bug #26996, which might or might not be what you're seeing.

Comment 6 Ed Ewing 2001-02-28 15:54:25 UTC

cat textfile > /dev/lp0 produces the same result. Have looked at Bug 26996 which 
appears to have a similar stalling problem except this printer stalls from the 
get go. Appears that much troubleshooting has occurred on 26996 with no solution 
yet.
Will try other options if requested.

Comment 7 Tim Waugh 2001-02-28 17:03:33 UTC

Please try this patch, which I think is the resolution for bug 26996.

Comment 8 Tim Waugh 2001-02-28 17:04:15 UTC

Created attachment 11360 [details]
linux-sema.patch

Comment 9 Tim Waugh 2001-03-09 17:58:25 UTC

Ed, are you still getting slow printing?

Comment 10 Ed Ewing 2001-03-10 15:59:33 UTC

Yes, because I was unable to successfully apply the linux-sema.patch and 
rebuild the kernel.

Comment 11 Tim Waugh 2001-03-11 11:11:19 UTC

Could you try a newer kernel?  -0.1.19 is in rawhide now.

Comment 12 Ed Ewing 2001-03-12 16:12:25 UTC

Printing is working using the -0.1.19 kernel!
Some other possibly irrelevent info:
1. Still receive the irq error message on boot.
2. Installed -i the -0.1.19 kernel and -U the headers.
3. Had to hand edit lilo.conf to add -0.1.19.

Thanks for your help.

Comment 13 Tim Waugh 2001-03-12 22:11:33 UTC

Okay, great.  I've made a patch to get rid of the warning message since it's 
triggered by unreliable information, and it's in my queue to send to Linus.

Comment 14 Arjan van de Ven 2001-03-21 18:08:07 UTC

I assume this patch is in our latest kernels and will close this bug.

Comment 15 Tim Waugh 2001-03-21 18:35:38 UTC

It isn't, although I've sent it to Linus twice now.

Comment 16 Tim Waugh 2001-04-06 16:36:03 UTC

FWIW, this cosmetic bug is fixed in 2.4.3.