Date: Fri, 18 Aug 2000 12:29:22 -0700 (PDT) From: visigoth@telemere.net To: freebsd-gnats-submit@FreeBSD.org Subject: kern/20706: recent newbus mod's to dpt seem to have broken it.. Message-ID: <20000818192922.A756B37B423@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 20706 >Category: kern >Synopsis: recent newbus mod's to dpt seem to have broken it.. >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Aug 18 12:30:00 PDT 2000 >Closed-Date: >Last-Modified: >Originator: Damieon Stark >Release: FreeBSD 4.1-STABLE >Organization: Telemere Technologies Inc >Environment: Working: 4.1-STABLE (kernel and world) from ~Aug 5 2000 Broken: Kernel as of newbus commits on the 10th ( I think ) >Description: When booting a "DPT PM3334UW FW Rev. 07M0, 2 channels, 64 CCBs" on 4.1-STABLE the bios asigns an irq and the kernel seems to think it is on a different one. Causing a kernel panic during boot. On my machine the bios asigns an IRQ of 9, but the kernel comes up with 16. In reading sys/dev/dpt/dpt.h I saw a comment about information read from the dpt being both Big endian, as well as in network byte order, This seems like a reasonable place to think the problem may be.... But not YET being a wizard, I don't know. Plus I don't know anything about newbus yet.. ;) >How-To-Repeat: Compile a newbusified dpt kernel (after aug 10) and try to boot up a DPT PM3334UW. (pci) >Fix: possible endian-ness/byte order missmatch in dpt_read_conf? or in the way newbus handles the data... Again, don't know.... >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000818192922.A756B37B423>