2.4.0-test9 kernel problems (was 2.4 kernel problems on 386)
I had problems loading a variant of this kernel on a 386. The problems are now more obvious, as I've tried to operate this kernel, compiled for a 386, on my pentium pro. In this case, the kernel starts up, but has no communication with the screen. No messages are logged to the screen. However, the messages are logged to the disk. A message : Cannot find map file, and also : Warning: unable to open an initial console. appear on the log, I can forward more detail to anyone who is interested. When I run the kernel on a 386, as far as I can tell, the machine just plain halts and does nothing. If the kernel is compiled using gcc version 2.95.2, then it reboots on a 386. On the Pentium Pro, the behaviour is the same. Seems a bit odd that what would be a standard patch seems to be causing this problem. Could be that a file or device is expected on the filesystem, but it is not obvious from the logs. There could indeed be a triple fault, as a previous participant suggested - but I would not know. Getting the kernel to at least print on my pentium pro would be a start. Any ideas ? I'm not on the list, so please copy me in correspondence. Thanks, -- John August Some of us are paying for sins we have committed. Others are paying for sins we still have to commit. - 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/
2.4.0-test9 kernel problems (was 2.4 kernel problems on 386)
I had problems loading a variant of this kernel on a 386. The problems are now more obvious, as I've tried to operate this kernel, compiled for a 386, on my pentium pro. In this case, the kernel starts up, but has no communication with the screen. No messages are logged to the screen. However, the messages are logged to the disk. A message : Cannot find map file, and also : Warning: unable to open an initial console. appear on the log, I can forward more detail to anyone who is interested. When I run the kernel on a 386, as far as I can tell, the machine just plain halts and does nothing. If the kernel is compiled using gcc version 2.95.2, then it reboots on a 386. On the Pentium Pro, the behaviour is the same. Seems a bit odd that what would be a standard patch seems to be causing this problem. Could be that a file or device is expected on the filesystem, but it is not obvious from the logs. There could indeed be a triple fault, as a previous participant suggested - but I would not know. Getting the kernel to at least print on my pentium pro would be a start. Any ideas ? I'm not on the list, so please copy me in correspondence. Thanks, -- John August Some of us are paying for sins we have committed. Others are paying for sins we still have to commit. - 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/
Re: 2.4 kernel problems on 386
This was implied in my last email, but I thought I'd say it explicitly : I've had 2.0.36 and 2.2.15 kernels boot properly on the netstation - is it possible for whatever 386 stuff included in these kernels to become lost on the 2.2.4 kernel I've been using ? -- John August - 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/
Re: 2.4 kernel problems on 386
What you're seeing is a tripple fault. I don't know why this is happening, but usually it has something to do with the double-fault mechanism being damaged (or not set-up) when a double-fault occurs. You mentiuon 386 - I rememeber in OS/2 we have many work-arounds for Intel processor errata - it might be possible that Linux hasn't catered for all the I32 386 errata - some of these errata apply to memory management and that's significant since a tripple fault is often caused by either stack faults or descriptor faults - both memory problems (I am assuming without checking the Linux uses a task switch for a double-fault, if it doesn't then a simple double-fault caused by a stack exception in ring 0 will result ina tripple fault.). Again, if this is a 386 issue then you should be aware of the increased instrcution set for 486, 586 etc.. Richard Moore - RAS Project Lead - Linux Technology Centre (PISC). http://oss.software.ibm.com/developerworks/opensource/linux Office: (+44) (0)1962-817072, Mobile: (+44) (0)7768-298183 IBM UK Ltd, MP135 Galileo Centre, Hursley Park, Winchester, SO21 2JN, UK [EMAIL PROTECTED] on 04/10/2000 11:22:19 Please respond to [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: Richard J Moore/UK/IBM) Subject: 2.4 kernel problems on 386 I'm trying to get a linux-2.4.0-test9-pre7 kernel with riel's recent memory swap patch going on a 386 - swapping problems with the 2.2.15 kernel I was using prompted this. I'm trying to make it run on a bull netstation, which means using bootp and etherboot tagged kernels. When I compile using gcc version 2.95.2, the resultant kernel reboots the machine each time its starts up - it does not get started. When I compile using gcc2.7.2.3, the machine just halts, with "Ok, booting the kernel" staying on the screen. I am not on the kernel list, so please send me any replies. I have not at this stage tried to see if any non patched versions of the kernel will work, nor have I tried to see if the kernel boots on my Pentium Pro (but could do so with some prompting). Regards, -- John August - 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/ - 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/
2.4 kernel problems on 386
I'm trying to get a linux-2.4.0-test9-pre7 kernel with riel's recent memory swap patch going on a 386 - swapping problems with the 2.2.15 kernel I was using prompted this. I'm trying to make it run on a bull netstation, which means using bootp and etherboot tagged kernels. When I compile using gcc version 2.95.2, the resultant kernel reboots the machine each time its starts up - it does not get started. When I compile using gcc2.7.2.3, the machine just halts, with "Ok, booting the kernel" staying on the screen. I am not on the kernel list, so please send me any replies. I have not at this stage tried to see if any non patched versions of the kernel will work, nor have I tried to see if the kernel boots on my Pentium Pro (but could do so with some prompting). Regards, -- John August - 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/
2.4 kernel problems on 386
I'm trying to get a linux-2.4.0-test9-pre7 kernel with riel's recent memory swap patch going on a 386 - swapping problems with the 2.2.15 kernel I was using prompted this. I'm trying to make it run on a bull netstation, which means using bootp and etherboot tagged kernels. When I compile using gcc version 2.95.2, the resultant kernel reboots the machine each time its starts up - it does not get started. When I compile using gcc2.7.2.3, the machine just halts, with "Ok, booting the kernel" staying on the screen. I am not on the kernel list, so please send me any replies. I have not at this stage tried to see if any non patched versions of the kernel will work, nor have I tried to see if the kernel boots on my Pentium Pro (but could do so with some prompting). Regards, -- John August - 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/
Re: 2.4 kernel problems on 386
What you're seeing is a tripple fault. I don't know why this is happening, but usually it has something to do with the double-fault mechanism being damaged (or not set-up) when a double-fault occurs. You mentiuon 386 - I rememeber in OS/2 we have many work-arounds for Intel processor errata - it might be possible that Linux hasn't catered for all the I32 386 errata - some of these errata apply to memory management and that's significant since a tripple fault is often caused by either stack faults or descriptor faults - both memory problems (I am assuming without checking the Linux uses a task switch for a double-fault, if it doesn't then a simple double-fault caused by a stack exception in ring 0 will result ina tripple fault.). Again, if this is a 386 issue then you should be aware of the increased instrcution set for 486, 586 etc.. Richard Moore - RAS Project Lead - Linux Technology Centre (PISC). http://oss.software.ibm.com/developerworks/opensource/linux Office: (+44) (0)1962-817072, Mobile: (+44) (0)7768-298183 IBM UK Ltd, MP135 Galileo Centre, Hursley Park, Winchester, SO21 2JN, UK [EMAIL PROTECTED] on 04/10/2000 11:22:19 Please respond to [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: Richard J Moore/UK/IBM) Subject: 2.4 kernel problems on 386 I'm trying to get a linux-2.4.0-test9-pre7 kernel with riel's recent memory swap patch going on a 386 - swapping problems with the 2.2.15 kernel I was using prompted this. I'm trying to make it run on a bull netstation, which means using bootp and etherboot tagged kernels. When I compile using gcc version 2.95.2, the resultant kernel reboots the machine each time its starts up - it does not get started. When I compile using gcc2.7.2.3, the machine just halts, with "Ok, booting the kernel" staying on the screen. I am not on the kernel list, so please send me any replies. I have not at this stage tried to see if any non patched versions of the kernel will work, nor have I tried to see if the kernel boots on my Pentium Pro (but could do so with some prompting). Regards, -- John August - 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/ - 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/
Re: 2.4 kernel problems on 386
This was implied in my last email, but I thought I'd say it explicitly : I've had 2.0.36 and 2.2.15 kernels boot properly on the netstation - is it possible for whatever 386 stuff included in these kernels to become lost on the 2.2.4 kernel I've been using ? -- John August - 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/
