I'm sorry, I should have mentioned that I have been able to produce this
problem since late 1.3. After using 2.0.2x, and having this problem, I
back-graded to lower 2.0.x's, and eventually to 1.3.9x, and still had the
problem.
I also do not have an sk_g16. I only have a 2940 and 3c509 in the
machine, yet receive the same current->tss3 message.
> Yes, actually -- you can test the following patch against v2.1.30, seeing
I will upgrade (redhat) to 2.1, but the machine it initially had the
problem was supposed to be a production machine, that I put together for
an off-hours intranet cdrom and web server job I landed..
> as I don't even have an sk_g16 card. I fixed a bunch of the obvious
> ones in v2.0.30, and it will now boot without going south, but a lot more
Do you mean David's 2.0.30, or some other pre-release? I had no problems
booting either. I could produce it with simply 'cp' of a CDROM to a 2.1
gig disk. The load was also usually high. (I was testing a new
motherboard, and used this stress test until I was sure it was a
motherboard problem) This took between 10 and 20 minutes to happen, or I
could use the sample code sent to the list a month ago, and produce the
problem immediately:
void main ()
{
int fd;
void *p;
char buf[1024];
fd = open("test", O_RDONLY);
p = mmap(NULL, 200, PROT_WRITE, MAP_PRIVATE, fd, 0);
strncpy (buf, p, 100);
printf ("%s\n", buf);
munmap (p, 200);
exit (0);
}
-- Dave