Vojtech Pavlik wrote:
> Just one question: How to reproduce it? Just by loading the module?
Yes, 'modprobe ns558' generates the oops. Thereafter, lsmod
reports that ns558 is initializing.
Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
Vojtech Pavlik wrote:
Just one question: How to reproduce it? Just by loading the module?
Yes, 'modprobe ns558' generates the oops. Thereafter, lsmod
reports that ns558 is initializing.
Stephen
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
Vojtech Pavlik wrote:
> This is weird - there were no changes in joystick code between the two
> as far as I know. Have you tried loading the modules manually?
No I haven't. And, as I said in my reply to Alan's message, I can't
even get the failure to repeat reliably (or at all) any more. I'll
Alan Cox wrote:
> No joystick changes in 12->13. Is the fail repeatable ?
It seems not. It failed on two successive boots last night, but
this morning I booted the machine 3 times and the joystick was
recognized just fine each time.
Flaky hardware? The plug is screwed in and the joystick
Vojtech Pavlik wrote:
This is weird - there were no changes in joystick code between the two
as far as I know. Have you tried loading the modules manually?
No I haven't. And, as I said in my reply to Alan's message, I can't
even get the failure to repeat reliably (or at all) any more. I'll
Alan Cox wrote:
No joystick changes in 12-13. Is the fail repeatable ?
It seems not. It failed on two successive boots last night, but
this morning I booted the machine 3 times and the joystick was
recognized just fine each time.
Flaky hardware? The plug is screwed in and the joystick works
into it (unless I'm completely misunderstanding the log
messages).
Anyway, I've attached the .config for the ac12 kernel - the ac13
kernel is the same except I've enabled ECN. I've also attached
the initial log messages for the ac12 and ac13 boots on the machine
in question.
Stephen Thomas
kernel: Linux
into it (unless I'm completely misunderstanding the log
messages).
Anyway, I've attached the .config for the ac12 kernel - the ac13
kernel is the same except I've enabled ECN. I've also attached
the initial log messages for the ac12 and ac13 boots on the machine
in question.
Stephen Thomas
kernel: Linux
;
else/* Compile goes crump here. */
another_thing();
Stephen Thomas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please re
/* Compile goes crump here. */
another_thing();
Stephen Thomas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://w
Manfred Spraul wrote:
> Could you try the attached oneliner patches?
>
> patch-tulip-fix1 is integrated in -ac15, and I send patch-tulip-typo to
> Alan a few seconds ago.
Just booted ac15 with the typo patch applied, seems to work well enough
for me to be sending you this and there are no
On trying 2.4.1-ac13 I hit the tulip driver problems reported elsewhere,
and ac14 does not seem to fix the problem on my machine. Attached is an
extract from my /var/log/messages.
Stephen Thomas
Feb 15 16:07:32 triumph kernel: Linux version 2.4.1-ac14
([EMAIL PROTECTED]) (gcc version 2.95.2
On trying 2.4.1-ac13 I hit the tulip driver problems reported elsewhere,
and ac14 does not seem to fix the problem on my machine. Attached is an
extract from my /var/log/messages.
Stephen Thomas
Feb 15 16:07:32 triumph kernel: Linux version 2.4.1-ac14
([EMAIL PROTECTED]) (gcc version 2.95.2
Manfred Spraul wrote:
Could you try the attached oneliner patches?
patch-tulip-fix1 is integrated in -ac15, and I send patch-tulip-typo to
Alan a few seconds ago.
Just booted ac15 with the typo patch applied, seems to work well enough
for me to be sending you this and there are no obvious
ignature of the OPL3 device, it gets 0xff from the inb() (line
195 of drivers/sound/opl3.c in test11pre1), while the corresponding
code in 2.2.18pre19 gets 0x00.
Stephen Thomas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
e, it gets 0xff from the inb() (line
195 of drivers/sound/opl3.c in test11pre1), while the corresponding
code in 2.2.18pre19 gets 0x00.
Stephen Thomas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
16 matches
Mail list logo
