[lkml]   [1996]   [Sep]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Processes hanging on 2.0.20; not just on Alphas anymore :(
>>>>> "Alan" == Alan Cox <> writes:

sb> I've got a machine with a 3c509 that booted fine with 2.0.20 (and
sb> previous 2.0 versions) but won't boot with 2.0.21.
sb> Sep 20 18:35:07 riker kernel: 3c509.c:1.07 6/15/95
sb> The card gets autodetected, but the first ifconfig command on the
sb> 3c509 gives a `try again' error message.

Alan> You have two devices on the same interrupt (at least thats what
Alan> it thinks)

Sigh. You're right:
Sep 20 18:35:07 riker kernel: Linux version 2.0.21 ( (gcc version 2.7.2) #2 Fri Sep 20 18:13:16 PDT 1996
Sep 20 18:35:07 riker kernel: STALLION: EasyIO found, unit=0 io=2a0 irq=10 nrpanels=1 nrports=4
Sep 20 18:35:07 riker kernel: eth0: 3c509 at 0x310 tag 1, AUI port, address 00 00 c5 4a 19 9e, IRQ 10.

I forgot I hand patched drivers/char/stallion.c to use a different
interrupt, and then used a fresh distribution to compile 2.0.21 (first
time for that since 1.3.86, 50 patches ago?).

The single feature I'd like to see in Linux 2.1 is a method of
configuring all the drivers without having to touch the source code
(stallion.c and the sbpcd come immediately to mind).

Good luck with 2.1 ...
-- baur
Unsolicited commercial e-mail will be billed at $250/message.
What are the last two letters of "doesn't" and "can't"?
Coincidence? I think not.

 \ /
  Last update: 2005-03-22 13:38    [W:0.145 / U:0.252 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site