Date: Mon, 10 Jan 2000 15:00:09 -0800 (PST) From: Frank Mayhar <frank@exit.com> To: billf@chc-chimes.com (Bill Fumerola) Cc: michaelc@tmbbwmc.bbn.hp.com (#Michael Class), freebsd-current@FreeBSD.ORG Subject: Re: Neomagic Sounddriver hangs HP OB4150 Message-ID: <200001102300.PAA07661@realtime.exit.com> In-Reply-To: <Pine.BSF.4.10.10001101506460.9382-100000@jade.chc-chimes.com> from Bill Fumerola at "Jan 10, 2000 03:07:35 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Bill Fumerola wrote: > On Mon, 10 Jan 2000, #Michael Class wrote: > > > The Laptop is equipped with the following Neomagic-Chip: > > chip1: <NeoMagic MagicMedia 256AX Audio controller> irq 10 at device 0.1 on pci1 > > > > The Stack-Backtrace looks exactly the same as the other mail mentioned. A > > little bit further digging into this shows me that on this Laptop every > > read access to the second memory-area of the chip in the range of 0x600-0x8ff > > brings the machine to a halt. I can read successfully from the areas with > > offset 0x0-0x5ff and 0x900-0xFFF. The Header-File states that the mixer-I/O > > Area starts at offset 0x600. This access brings the machine to a halt during > > boot. > > > > Any suggestions of what I could try? > > Try providing us with real data. The boot message you gave us is when > pcisupport.c matches it, not when neomagic. matches it. It is impossible > to recieve the above message and then have the neomagic code fall on > its face. Um, no it's not. The very next thing that happens after that message comes out is that the nm_* routines are called to initialize the hardware and the driver. (In my case, though, it was the outw in ac97_init() that hung my machine.) -- Frank Mayhar frank@exit.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200001102300.PAA07661>