From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fresh compiled kernels no longer boot..?
Date: Sun, 25 Jan 2004 18:52:39 -0500 [thread overview]
Message-ID: <18e3056b13bce290bf6a93c5b70d3afd@plan9.bell-labs.com> (raw)
In-Reply-To: <200401252343.i0PNhqm08381@zamenhof.cs.utwente.nl>
On Sun Jan 25 18:45:41 EST 2004, Axel.Belinfante@cs.utwente.nl wrote:
> i wrote:
> > jmk wrote:
> > > On Sun Jan 25 17:38:41 EST 2004, presotto@closedmind.org wrote:
> > > > The 486 problems shouldn't bother a K6 which is a pentium comnpatible machine.
> > > > However, jmk has already fixed that for 486's. If you want, you could comment
> > > > out lines 900 and 901 in 9/pc/devarch.c and see if it helps.
> > > >
> > > > Unfortinately, I don't have a matching processor. I did make a cpu kernel from
> > > > the distribution and it worked on a Xeon but that doesn't tell you much I guess.
> > >
> > > The DX value from the cpuid instruction shows the processor has the capabilities
> > > which were missing on Lucio's SiS processor and causing it to reboot, so that shouldn't
> > > be the problem.
> >
> > i commented out those lines, without result.
> > got my serial cable and added some print statements to main.c;
> > it seems to die in cpuidentify().
> > I'll try adding some more print statements and see what I learn.
>
> It seems that my machine did not like the line (guarded by an if statement):
>
> rdmsr(0x1B, &apicbase);
>
> near the end of cpuidentify().
>
> Now that I'm looking at sources, that piece of code seems to be gone... :-)
>
> Axel.
My fault. That code was in my private copy and I updated the main tree before
taking it out. I took it when looking at your problem when I realised is shouldn't
have been there.
Sorry.
next prev parent reply other threads:[~2004-01-25 23:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-25 22:05 Axel Belinfante
2004-01-25 22:37 ` David Presotto
2004-01-25 23:02 ` jmk
2004-01-25 23:12 ` Axel Belinfante
2004-01-25 23:43 ` Axel Belinfante
2004-01-25 23:52 ` jmk [this message]
2004-01-26 0:13 ` Axel Belinfante
2004-01-26 0:52 ` boyd, rounin
2004-02-11 23:30 ` matt
2004-02-12 2:54 ` boyd, rounin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18e3056b13bce290bf6a93c5b70d3afd@plan9.bell-labs.com \
--to=jmk@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).