Messages in this thread | | | Date | Sun, 10 Jan 1999 22:54:12 -0600 (CST) | From | Eric Furbish <> | Subject | Re: ISSUE: lp locks system when polling printer in 2.2.0pre5 |
| |
Yep, it's during bootup. I recompiled with magic-sysrq enabled, and gave it a try. If I use Alt-SysRq-p right after it gives that "lp0: using parport0 (polling)" message, it gives me this:
EIP: 0010:[<c0108ae8>] EFLAGS: 00000246 EAX: 00000000 EBX: c02b6320 ECX: 0000000a EDX: c02b6320 ESI: 00000001 EDI: 0000000a EBP: c0003e48 DS: 0018 ES: 0018 CR0: 80050036 CR2: 00000000 CR3: 00101000
If I press any of the SysRq combinations after waiting for another second or so, none of them work at all (whether I've already used it once or not). I'm something of a virgin at this, so I'm not sure what I need to do with this above output... is there some documentation somewhere? I assume those numbers are meaningless without looking at other things (whatever those may be :).
The parport messages I get on bootup are as follows: parport0: PC-style at 0x378 [SPP,PS2] lp0: using parport0 (polling).
eric
On Sun, 10 Jan 1999, Tim Waugh wrote:
> On Sat, 9 Jan 1999, Eric Furbish wrote: > > > I'm not exactly sure what "polling the printer" means, but I assume it > > means it's trying to test communication with the printer. The exact > > kernel message is "lp0: using parport0 (polling)." The code relevant to > > that printk is in lp.c. There are no print jobs in progress when I > > reboot, and nothing at all is using the printer driver -- lpd is shutdown > > alltogether, and nothing else is accessing it as far as I can tell. > > So it's when the machine is booting up that you see the problem? Right, I > was confused for a while -- I thought you meant during the shutdown -r > sequence. > > The message just means that when the printer driver _is_ used, it will > poll the printer to see when it's ready, instead of using interrupts to > find out. > > Do you have magic-sysrq enabled? Try Alt-SysRq-P to find out the program > counter, and see where that is in the kernel. > > It's more likely that the next driver in line for initialisation is the > one you're having trouble with, but in case it's lp, what parport messages > do you see on boot-up? > > Tim. > */
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |