Re: OSS SBLive driver causes kernel panic with 5.0 current

2003-03-20 Thread Jody Franklin
David Schultz wrote:
Thus spake Andre Guibert de Bruet [EMAIL PROTECTED]:

On Fri, 7 Mar 2003, Jody Franklin wrote:


I'd been keeping up with current (world/kernel) every other week or so,
and until this week I had no real problems. But after the build I did on
March 3rd my soundcard driver (4Front's SBLive/Audigy driver) causes a
kernel panic on load. If I don't load the driver the system boots fine,
and runs with no other problems.
This is the message I get from the debugger when I load the driver:

panic: Invalid major (-1030904368) in make_dev

I've posted this info to their support forums also, their last responce
was to see what they broke.
Please don't cross-post -current and -questions.

Major numbers are now being allocated dynamically. Sounds like the emu10k1
driver doesn't like this. My guess is, it's probably in the process of
being converted over...


His post refers to the commercial driver, which still needs to be
converted.


As of the 12th 4Front's last word was that they are using 
/usr/share/examples/cdev as an example for their code, and that example 
causes the same panic as their driver. Thus asking that the examples be 
updated to match the current kernel so that they can update their driver.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message


Re: OSS SBLive driver causes kernel panic with 5.0 current

2003-03-15 Thread Andre Guibert de Bruet

On Fri, 7 Mar 2003, Jody Franklin wrote:

 I'd been keeping up with current (world/kernel) every other week or so,
 and until this week I had no real problems. But after the build I did on
 March 3rd my soundcard driver (4Front's SBLive/Audigy driver) causes a
 kernel panic on load. If I don't load the driver the system boots fine,
 and runs with no other problems.

 This is the message I get from the debugger when I load the driver:

 panic: Invalid major (-1030904368) in make_dev

 I've posted this info to their support forums also, their last responce
 was to see what they broke.

Please don't cross-post -current and -questions.

Major numbers are now being allocated dynamically. Sounds like the emu10k1
driver doesn't like this. My guess is, it's probably in the process of
being converted over...

Regards,

 Andre Guibert de Bruet | Enterprise Software Consultant 
 Silicon Landmark, LLC. | http://siliconlandmark.com/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message


Re: OSS SBLive driver causes kernel panic with 5.0 current

2003-03-15 Thread David Schultz
Thus spake Andre Guibert de Bruet [EMAIL PROTECTED]:
 
 On Fri, 7 Mar 2003, Jody Franklin wrote:
 
  I'd been keeping up with current (world/kernel) every other week or so,
  and until this week I had no real problems. But after the build I did on
  March 3rd my soundcard driver (4Front's SBLive/Audigy driver) causes a
  kernel panic on load. If I don't load the driver the system boots fine,
  and runs with no other problems.
 
  This is the message I get from the debugger when I load the driver:
 
  panic: Invalid major (-1030904368) in make_dev
 
  I've posted this info to their support forums also, their last responce
  was to see what they broke.
 
 Please don't cross-post -current and -questions.
 
 Major numbers are now being allocated dynamically. Sounds like the emu10k1
 driver doesn't like this. My guess is, it's probably in the process of
 being converted over...

His post refers to the commercial driver, which still needs to be
converted.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message


OSS SBLive driver causes kernel panic with 5.0 current

2003-03-07 Thread Jody Franklin
I'd been keeping up with current (world/kernel) every other week or so,
and until this week I had no real problems. But after the build I did on
March 3rd my soundcard driver (4Front's SBLive/Audigy driver) causes a
kernel panic on load. If I don't load the driver the system boots fine,
and runs with no other problems.
This is the message I get from the debugger when I load the driver:

panic: Invalid major (-1030904368) in make_dev

I've posted this info to their support forums also, their last responce
was to see what they broke.
Jody





To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message


Re: SBlive driver

2000-04-10 Thread Otter

Doug Barton wrote:
 
 Cameron Grant wrote:
 
  cg  2000/04/01 23:41:21 PST
 
Added files:
  sys/dev/sound/pciemu10k1.c emu10k1.h
Log:
unfinished sblive driver, playback/mixer only for now - not enabled in
conf/files
 
i don't seem to be clearing the cache right resulting in a short initial
burst of noise, despite doing the same as creative and alsa.  i'm committing
now so more eyes can pore over the code.
 
 I finally got around to testing this, and it's causing my machine to
 reboot. I cvsup'ed the latest -current sources, made world, built and
 installed a new kernel after adding 'device pcm', and rebooted. The card
 was detected during boot, and after making snd0, 'cat /dev/sndstat'
 reports:
 
 FreeBSD Audio Driver (newpcm) Apr  9 2000 18:53:41
 Installed devices:
 pcm0: Creative EMU10K1 at io 0xb800 irq 5 (1p/0r channels duplex)
 
 I use xfce as my WM, and when I enabled xfsound (which uses esound to
 play its sounds) my machine immediately locked up,

Maybe you should try another audio app. I made world again last night
(April 9,2000)and use XMMS and mpg_123 for my use (listening to
shoutcast servers and local files). XMMS plays without a hitch. I
don't do any recording, so that's not an issue. Mpg123 works just as
well, but it's for use on the command line. Both can be found in your
ports collection.
-Otter


 then after a few
 seconds it spontaneously rebooted. I have the following in my kernel
 config:
 
 makeoptions DEBUG=-g#Build kernel with gdb(1) debug
 symbols
 options INVARIANT_SUPPORT
 options INVARIANTS
 options DDB
 
 In spite of that, I get no debug, no crash dump (I have dumpdev in my
 /etc/rc.conf.local), nothing but a reboot. I repeated the same
 experiment, same result.
 
 Let me know if there is anything I can do to help.
 
 Doug
 --
 Excess on occasion is exhilarating.  It prevents moderation from
 acquiring the deadening effect of a habit.
 -- W. Somerset Maugham
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-current" in the body of the message


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: SBlive driver

2000-04-10 Thread Doug Barton

Otter wrote:
 
 Maybe you should try another audio app.

I plan to do that when I have time to handle a system that might reboot
spontaneously. However I figured Cameron (et al) would want to know
about the rebooting problem with esound (at least for me).

Doug
-- 
Excess on occasion is exhilarating.  It prevents moderation from
acquiring the deadening effect of a habit.
-- W. Somerset Maugham


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: SBlive driver

2000-04-10 Thread Kent Hauser

Doug,

On my -CURRENT system (from last week), I also found that
the SBlive driver caused spontaneous reset -- no panic, no
dump, just reset. I was using "realaudio7" as my audio
source. 

Kent


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: SBlive driver

2000-04-10 Thread Martin Minkus

On Mon, 10 Apr 2000, Kent Hauser wrote:

 Doug,
 
 On my -CURRENT system (from last week), I also found that
 the SBlive driver caused spontaneous reset -- no panic, no
 dump, just reset. I was using "realaudio7" as my audio
 source. 
 
 Kent

I moved the SB Live driver from 5.0 into 4.0, and am using it with no ill
effect. xmms, and several other programs (like emulators) use it fine,
perfect crisp sound (only wavs play bad?), and 4.0 has not been crashing,
or resetting, or anything. I've been using it like this for a few days.

When will it be backported into 4.0? *hint* *hint*

martin.

--
Martin Minkus aka DiSKiLLeR
Email: [EMAIL PROTECTED]   Web: http://www.diskiller.net

I live in a world of paradox... my willingness to destroy is
your chance for improvement, my hate is your faith, my failure
is your victory - a victory that won't last.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



SBlive driver

2000-04-09 Thread Doug Barton

Cameron Grant wrote:
 
 cg  2000/04/01 23:41:21 PST
 
   Added files:
 sys/dev/sound/pciemu10k1.c emu10k1.h
   Log:
   unfinished sblive driver, playback/mixer only for now - not enabled in
   conf/files
 
   i don't seem to be clearing the cache right resulting in a short initial
   burst of noise, despite doing the same as creative and alsa.  i'm committing
   now so more eyes can pore over the code.

I finally got around to testing this, and it's causing my machine to
reboot. I cvsup'ed the latest -current sources, made world, built and
installed a new kernel after adding 'device pcm', and rebooted. The card
was detected during boot, and after making snd0, 'cat /dev/sndstat'
reports:

FreeBSD Audio Driver (newpcm) Apr  9 2000 18:53:41
Installed devices:
pcm0: Creative EMU10K1 at io 0xb800 irq 5 (1p/0r channels duplex)

I use xfce as my WM, and when I enabled xfsound (which uses esound to
play its sounds) my machine immediately locked up, then after a few
seconds it spontaneously rebooted. I have the following in my kernel
config:

makeoptions DEBUG=-g#Build kernel with gdb(1) debug
symbols
options INVARIANT_SUPPORT
options INVARIANTS
options DDB

In spite of that, I get no debug, no crash dump (I have dumpdev in my
/etc/rc.conf.local), nothing but a reboot. I repeated the same
experiment, same result.

Let me know if there is anything I can do to help.

Doug
-- 
Excess on occasion is exhilarating.  It prevents moderation from
acquiring the deadening effect of a habit.
-- W. Somerset Maugham


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message