Messages in this thread |  | | Date | Sun, 18 Aug 2002 14:20:20 -0700 | From | "Brian M. Sutin" <> | Subject | Bug Report ... Please Forward |
| |
Hello! I have found what I think to be a hardware compatibility bug with the basic operation of the kernel. I would appreciate if you could put me into contact with people who would be most interested in fixing this bug, as my participation will probably be necessary to solve the problem. Here is the report:
Short Summary:
On a Toshiba Libretto 70CT, the 2.4.18-3 kernel boots up until freeing the extra kernel memory. After this, the execve to /sbin/init returns success, but /sbin/init does not run.
Long Version:
The Toshiba Libretto 70CT has a 586 with MMX processor. It runs vanilla Redhat 6.2 fine (I forgot the kernel version, sorry...). It will not run Redhat 7.0 (kernel 2.2.late) or Redhat 7.3 (2.4.18-3), so the bug has existed for quite some time. The problem is that, on boot, I see:
...previous stuff... Freeing unused kernel memory: (some number) ...hangs forever here...
I tried having the kernel run the shell instead, but that did not work either. I also recompiled /sbin/init to print out a message to stderr first off, but nothing appeared.
I recompiled the kernel and started adding printk debugging statements. I found that search_binary_handler() (from fs/exec.c) returns success. At this point it is clear to me that I am not going to get any farther with printk statements.
I also tried to make an a.out executable (rather than an ELF), but the ld in Redhat is not compiled to create one, and I was unable to figure out how to configure the recompile of ld to make it do so. If someone could send me an a.out-style executable of some sort, that would be the next obvious test.
My info:
Brian Sutin sutin@ociw.edu (626) 304 - 0265 I will be out of town from 2002-08-21 to 2002-08-29.
-- Brian M. Sutin Optical Scientist Pasadena, CA The Observatories of the Carnegie Institution of Washington - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |