Re: ATA DMA support is broken
On Tue, Oct 03, 2000 at 10:25:34PM +0200, Soren Schmidt wrote: Are you sure this is with the latest changes ? -Søren I have a similar issue since approximately 4 hours ago. I also do not use the GENERIC.hints and made some attempts to tune them... although NOTES would lead me to believe I do not, I now need the hints for both ata.0 and ata.1. This is a Dell Inspiron (7500) laptop. Relevant dmesg: atapci0: Intel PIIX4 ATA33 controller port 0x1050-0x105f at device 7.1 on pci0 atapci0: Busmastering DMA enabled ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0 ata1 at port 0x170-0x177,0x376 irq 15 on isa0 ata1-master: identify retries exceeded ad0: 11513MB FUJITSU MHK2120AT [23392/16/63] at ata0-master BIOSPIO N.B. My normally recognized DVD drive is not recognized. It is the master on the secondary controller. -- :Kevin M. Dulzo: eyes betray a soul and bear its thinking beyond words they say so many things to me --vnvnation To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Apparant lockups/process wedging.
I have had several lockups since I gave -current a whirl. I finally have a crash dump so hopefully can help isolate the issue. These seems to be repeatable easily by rebooting without powering off (on my one machine). sh (pid 6) has locked, other startup proceeses spawned from /etc/rc (named for example) have locked. By locking, they just spin off into lala land and chew on CPU time, as well they become uninterruptable and prevent the machine from entering multi-user mode. I can provide dmesg/kernel config/hints/dump to anyone but I felt too much to dump down the list. The 'where' output of gdb -k only seems to show my manual break and 'panic' calls. -- :Kevin M. Dulzo: eyes betray a soul and bear its thinking beyond words they say so many things to me --vnvnation To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
IPX requires 'device random'
I am not aware of the full status of IPX networking support in -current, but I migrated my -stable kernel config as best I could. Kernel compilation completes, but linking fails due to a rand_ function not being present ( I do not have the exact error handy, but can generate for anyone who wants it.) A simple 'device random' to compile the support in statically rectifies the problem. -- :Kevin M. Dulzo: eyes betray a soul and bear its thinking beyond words they say so many things to me --vnvnation To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
