> > Shouldn't Athlons and AthlonXPs be able to use i686 (pentiumpro)
> > instruction set optimizations?
>
>No. They are different cpu cores that have different optimization
>strategies.
Yes, all Athlons can use i686 code while the k6's can't. Further, without
doing any scientific testing, I w
Hi,
I can't find the date or sender of the original email - the mailing list archives
haven't been updated since Feb 20 - but my Pentium 66 still panics during boot with a
kernel compiled today. Here's what I get...
atapci0: port
0x3f4-0x3f7,0x1f0-0x1f7 at device 1.0 on pci0
atapci0: Busmas
A panic also occurred on my Pentium (P54C) 66MHz, but backing identcpu.c
to 1.79 didn't stop the panic. Here is the panic info, copied by hand. (I
hope there are no typos!)
Lots of 'ad1: timeout waiting for DRQ' followed by
Fatal trap 12: page fault while in kernel mode
fault virtual address
At 08:19 AM 1/25/00 +0100, Soren Schmidt wrote:
> > On some older PCI systems, including my Pentium 66, the driver still detects
> > irq 0 for ata-pci0. Hardwiring it to irq 14 in the source as suggested recently
>is the >temporary fix I'm using.
>
>Could you send that patch around me please ?
>Huh, you have only told me about the missing CDROM (should be fixed
>with the commit I just did), what else seems to be a problem ??
On some older PCI systems, including my Pentium 66, the driver still detects
irq 0 for ata-pci0. Hardwiring it to irq 14 in the source as suggested recently is
t
Yes! That is exactly the problem I have been having since the 1999/10/09 12:57:15 PDT
ATA commit. Here is the link to the email I sent earlier:
http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=1326170+1331912+/usr/local/www/db/text/1999/freebsd-current/19991212.freebsd-current
Basically, on my Pen
At 07:40 AM 12/14/99 +0800, Peter Wemm wrote:
>Greg Lehey wrote:
> > On Friday, 10 December 1999 at 23:32:27 -0800, Mike Smith wrote:
> > > [missing attribution to Greg Childers <[EMAIL PROTECTED]>]
> > >> Except that ATA currently does not work on my system.
rom Poul Henning-Kamp (I hope thats the spelling) saying that
>it should be possible to use only raw devices throughout the system.
>This worked for a while but then other changes made it unable to boot.
>
>On Sat, 11 Dec 1999, Greg Childers wrote:
>
> > Hi,
> >
> &
Hi,
With a bit of investigating, I've found the problem described in my previous email
quoted at
the end of this message started with the commits listed below. A kernel built using
sources just before these commits works fine, whereas a kernel build just after freezes
after the line
Mounting
At 11:22 PM 12/10/99 +0100, Poul-Henning Kamp wrote:
> >This discussion is not going anywhere. Why can't everyone calm down and
> >find a comprise? Here's my proposal:
> >
> >1. leave the the code and config option in the source tree for now
> >2. remove all traces of wd in documentation/GENERIC/L
Hello,
Seems now is the time to raise problems with ATA, so here goes. I have used the ATA
driver
since its introduction into -current without problem until recently. A kernel from
October
5 worked fine. Now, it no longer works using ATA, but works fine using the old WD
drivers.
The console
I've updated to the latest -current, and things have gone awry. At boot,
the console freezes
at the end of the dmesg. The startup process continues, tho, and I can
telnet into the box. Then madness ensues. The contents of some files I
create disappears, top freezes after listing the process
Sounds like you want something like a FreeBSD version of DOS Linux. See
http://www.tux.org/pub/people/kent-robotti/index.html. How do they
overcome this problem?
Greg
At 02:45 PM 5/19/99 -0700, Carlos C. Tapang wrote:
>Thanks to all who pitched in their input to this issue. Most users of my
>sy
13 matches
Mail list logo
