[lkml]   [1998]   [Sep]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Next round of console patches
Tom Eastep writes:
> This is a multi-part message in MIME format.
> --------------CB6C14F6D5EFAD11DA024FFC
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
> Richard Gooch wrote:
> >
> >
> > OK, I think I know what might be happening here. Can you please send
> > me the output of your boot logs (with the call to mtrr_add() removed
> > but with CONFIG_MTRR enabled)?
> The attached log show booting with mtrr_add() removed and with the
> rest of patch-con118 applied (the one I sent you earlier was without
> the latest console patches).

Ah, OK, I've just sent you a message asking for the mtrr_add() call to
be replaced with a printk(). Please do that for patch-con118 applied.
In other words, take 2.1.118, apply patch-con-118 and then replace the
mtrr_add() with printk().

> > Then compile a UP kernel with mtrr_add() put back in and tell me how
> > that works.
> It boots without any problem...

OK, if UP works fine with 2.1.118+patch-con118 that confirms my
suspicions. However, the boot logs you sent me confuses things a bit,
so I really need the boot logs I described above (dmesg output, not
the logfile variety).



To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:44    [W:0.079 / U:8.500 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site