DragonFly kernel List (threaded) for 2007-06
DragonFly BSD
DragonFly kernel List (threaded) for 2007-06
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: Decision time.... should NATA become the default for this release?


To: Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>
From: Sascha Wildner <saw@xxxxxxxxx>
Date: Sat, 02 Jun 2007 22:01:36 +0200

Matthew Dillon wrote:
:OK, relevant lines from NATA and ATA follow.

Ok. Hmm. It looks ok.

    (1) Is your ATA device on the PCI bus or is it a legacy ISA device?
	Do a normal ATA boot and run pciconf -l.

Seems to be on the PCI bus. Here's the complete output:


agp0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x71908086 rev=0x03 hdr=0x00
pcib1@pci0:1:0: class=0x060400 card=0x00000000 chip=0x71918086 rev=0x03 hdr=0x01
isab0@pci0:7:0: class=0x060100 card=0x00000000 chip=0x71108086 rev=0x02 hdr=0x00
atapci0@pci0:7:1: class=0x010180 card=0x00000000 chip=0x71118086 rev=0x01 hdr=0x00
uhci0@pci0:7:2: class=0x0c0300 card=0x00000000 chip=0x71128086 rev=0x01 hdr=0x00
none0@pci0:7:3: class=0x068000 card=0x00000000 chip=0x71138086 rev=0x02 hdr=0x00
pcm0@pci0:9:0: class=0x040100 card=0x0001125d chip=0x1978125d rev=0x10 hdr=0x00
cbb0@pci0:10:0: class=0x060700 card=0xac1c104c chip=0xac1c104c rev=0x01 hdr=0x02
cbb1@pci0:10:1: class=0x060700 card=0xac1c104c chip=0xac1c104c rev=0x01 hdr=0x02
none1@pci0:12:0: class=0x078000 card=0x04401468 chip=0x044811c1 rev=0x01 hdr=0x00
none2@pci1:0:0: class=0x030000 card=0x4c421002 chip=0x4c421002 rev=0xdc hdr=0x00


	I'm a bit worried that it just stopped working entirely with the most
	recent update to HEAD.  The Intel chipinit code basically didn't
	change at all.

Sorry for not mentioning this earlier, it no longer is stuck at the sbin/init line but gets a bit further (just happened from one reboot to the other):


----------
start_init: trying /sbin/init
pid 4 (rcorder), uid 0: exited on signal 11
Segmentation fault
pid 5 (sysctl), uid 0: exited on signal 11
Segmentation fault
pid 6 (rcorder), uid 0: exited on signal 11
Segmentation fault

Sat Jun 2 23:52:08 CEST 2007
Jun 2 23:52:08 init: can't exec getty '/usr/libexec/getty' for port /dev/ttyv2: No such file or directory
Jun 2 23:52:08 init: can't exec getty '/usr/libexec/getty' for port /dev/ttyv0: No such file or directory
Jun 2 23:52:08 init: can't exec getty '/usr/libexec/getty' for port /dev/ttyv1: No such file or directory
Jun 2 23:52:08 init: can't exec getty '/usr/libexec/getty' for port /dev/ttyv4: No such file or directory
Jun 2 23:52:08 init: can't exec getty '/usr/libexec/getty' for port /dev/ttyv3: No such file or directory
Jun 2 23:52:08 init: can't exec getty '/usr/libexec/getty' for port /dev/ttyv5: No such file or directory
Jun 2 23:52:08 init: can't exec getty '/usr/libexec/getty' for port /dev/ttyv6: No such file or directory
Jun 2 23:52:08 init: can't exec getty '/usr/libexec/getty' for port /dev/ttyv7: No such file or directory
[getty errors repeat every few seconds]
----------


Why it was stuck at the sbin/init line earlier, don't ask me. I'm pretty sure that everything was recompiled properly.


    (2) Please try this patch.  I noticed that some bits in reg54
	were being improperly overwritten for UDMA2 mode.  If you look
	at the original code, the clause for UDMA5 overwrites the
	bits that were set or cleared for UDMA2.

The patch had no effect.


Sascha

--
http://yoyodyne.ath.cx



[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]