Hard lock with sis7018 and solaris 10 x86 b72

OSS specific Solaris discussion (x86/SPARC)

Moderators: hannu, dev, kodachi, cesium

Hard lock with sis7018 and solaris 10 x86 b72

Postby boera » Thu Jan 27, 2005 10:44 pm

The machine locks up immediately after loading oss if the AC 97 modem is
disabled in BIOS. The lockup appears after about 30s if the modem is enabled
in BIOS.
Motherboard: SiS 730s , on-board sis 7018 audio

P.S. It's not a hardware issue because ALSA workd just fine (on Linux of course).
boera
 

Re: Hard lock with sis7018 and solaris 10 x86 b72

Postby dev » Fri Jan 28, 2005 2:46 am

boera wrote:The machine locks up immediately after loading oss if the AC 97 modem is
disabled in BIOS. The lockup appears after about 30s if the modem is enabled
in BIOS.
Motherboard: SiS 730s , on-board sis 7018 audio

P.S. It's not a hardware issue because ALSA workd just fine (on Linux of course).



Hi,


Can you check if our OSS drivers on Linux also hardlock?.


We'll double check the drivers as soon as we can get our SiS7018
mobo installed with Solaris.


best regards
Dev Mazumdar
dev
 
Posts: 576
Joined: Fri Sep 12, 2003 6:08 am
Location: Culver City, CA

Postby Guest » Fri Jan 28, 2005 3:05 pm

The answer is yes, unfortunately (see my previous post from the
Linux section).
But the lockup appears only with the 2.6.x kernel.
Recently I have tested with 2.4.26 and after I try to switch
in the audio file to a different position, the driver "unloads"
automatically with the following error:
IRQ storm detected, but it doesn't lock up the system.
After that any attempt to load the oss modules is unsuccesful.
If I try modprobe trident && rrmod trident
one can load again the oss modules with soundon.
The strange thing is that I don't have anything on the same
interrupt.
With Solaris it seems that the oss modules load fine in console mode,
I can do a
cat *.au > /dev/audio
but with X started it will lockup shortly after using /dev/dsp with xmms.
In this evening I will make some additional tests (e.g. loading the oss modules right after boot, before X and different settings in the BIOS).
Thank you for your quick reply.
Best regards,
Boer Attila
Guest
 

Postby dev » Sat Jan 29, 2005 7:55 pm

Anonymous wrote:The answer is yes, unfortunately (see my previous post from the
Linux section).
But the lockup appears only with the 2.6.x kernel.
Recently I have tested with 2.4.26 and after I try to switch
in the audio file to a different position, the driver "unloads"
automatically with the following error:
IRQ storm detected, but it doesn't lock up the system.
After that any attempt to load the oss modules is unsuccesful.
If I try modprobe trident && rrmod trident
one can load again the oss modules with soundon.
The strange thing is that I don't have anything on the same
interrupt.
With Solaris it seems that the oss modules load fine in console mode,
I can do a
cat *.au > /dev/audio
but with X started it will lockup shortly after using /dev/dsp with xmms.
In this evening I will make some additional tests (e.g. loading the oss modules right after boot, before X and different settings in the BIOS).
Thank you for your quick reply.
Best regards,
Boer Attila


Hi,


I've just got my SiS 630E motherboard that has the same SiS7018 audio device and it's working perfectly under SuSE 9.2 with OSS 3.99.2a. I've also installed Solaris x86 B74 and it's working as well.

You may need to do the following:

1) eeprom acpi-user-options=0x2
2) edit /etc/system and add: set pcplusmp:apic_forceload-1
3) reboot

Now get the OSS 3.99.2a for Solaris (get the Combo version (isa/pci))
and before you install this combo version, uninstall the current version
by typing /usr/lib/oss/scripts/uninstall.sh

Install the OSS drivers and reboot and then run soundon and see if that works.

best regards
Dev Mazumdar
dev
 
Posts: 576
Joined: Fri Sep 12, 2003 6:08 am
Location: Culver City, CA

Postby boera » Sat Jan 29, 2005 10:24 pm

Still locks up.
Discovered that the same lockup appears with FreeBSD 5.3 release also.
The strange thing is that it works fine with the old trident module from
the linux kernel, with ALSA and with the FreeBSD t4dwave driver.

Best regards,
Boer Attila
boera
 

Postby dev » Sat Jan 29, 2005 10:47 pm

boera wrote:Still locks up.
Discovered that the same lockup appears with FreeBSD 5.3 release also.
The strange thing is that it works fine with the old trident module from
the linux kernel, with ALSA and with the FreeBSD t4dwave driver.

Best regards,
Boer Attila


Hi,

What is the make and model of your motherboard?.




regards
Dev
dev
 
Posts: 576
Joined: Fri Sep 12, 2003 6:08 am
Location: Culver City, CA

Postby dev » Sun Jan 30, 2005 4:00 am

boera wrote:Still locks up.
Discovered that the same lockup appears with FreeBSD 5.3 release also.
The strange thing is that it works fine with the old trident module from
the linux kernel, with ALSA and with the FreeBSD t4dwave driver.

Best regards,
Boer Attila


Hi,

Please try the Solaris x86 drivers again, we've made a few minor changes and tell me if this works on your system.

If this works, we'll also update the Linux and FreeBSD versions.


best regards
Dev Mazumdar
dev
 
Posts: 576
Joined: Fri Sep 12, 2003 6:08 am
Location: Culver City, CA

Postby boera » Sun Jan 30, 2005 8:34 am

Still locks sup.
The behaviour is the same. It doesn't lock up immediately after
running soundon, but after we make some skips in the audio file
(with xmms or mplayer). With xmms and OSS output the lockup
happens after about 2-3 skips, with the Solaris audio plugin
later.
The motherboard is Mercury with the sis 730s chipset.
It's very stable, because I have a home web server on this machine
and it I didn't have lockups, so it's not hardware related.
We had another problem with oss+sis7018 in the past (lockup immediately
after running soundon) but that was fixed by enabling the AC 97 modem
in the bios. Now I have tried different settings in the BIOS but
without success.
If on sis 630 works fine, the conclusion is that the 730 motherboard has
some glitches which interact badly with OSS.
boera
 

Postby Guest » Sun Jan 30, 2005 1:32 pm

Important!!!
I didn't observe one thing until now.
The lockup happens only with the Virtual Mixer Pro enabled.
It seems that without the virtual mixer the latest combo version
works fine.

Best regards,
Boer Attila
Guest
 

Postby boera » Sun Jan 30, 2005 1:37 pm

Oops, I forgot to log in.
boera
 
Posts: 1
Joined: Sun Jan 30, 2005 1:35 pm
Location: Brasov - Romania

Postby dev » Sun Jan 30, 2005 8:46 pm

Anonymous wrote:Important!!!
I didn't observe one thing until now.
The lockup happens only with the Virtual Mixer Pro enabled.
It seems that without the virtual mixer the latest combo version
works fine.

Best regards,
Boer Attila


Wait, with SiS7018 you should not need virtual mixer pro.

I will now check why vmix pro hangs SiS7018. SiS7018 provides hardware mixing so you really don't need vmix (only thing vmix will provide is fidelity enhance and equalizers).

Glad to hear that the drivers are working without VMIX PRO.


best regards
Dev
dev
 
Posts: 576
Joined: Fri Sep 12, 2003 6:08 am
Location: Culver City, CA

Postby dev » Mon Jan 31, 2005 12:30 am

Anonymous wrote:Important!!!
I didn't observe one thing until now.
The lockup happens only with the Virtual Mixer Pro enabled.
It seems that without the virtual mixer the latest combo version
works fine.

Best regards,
Boer Attila



Hi,

OK we found the problem with virtual mixer and have updated the OSS/Solaris
(as well as linux versions). Please run ossupdate and update your current
OSS drivers and check it out with the Virtual Mixer enabled.


best regards
Dev Mazumdar
dev
 
Posts: 576
Joined: Fri Sep 12, 2003 6:08 am
Location: Culver City, CA

Postby Guest » Mon Dec 26, 2005 9:47 am

[quote="boera"]Still locks sup.
The behaviour is the same. It doesn't lock up immediately after
running soundon, but after we make some skips in the audio file
(with xmms or mplayer). With xmms and OSS output the lockup
happens after about 2-3 skips, with the Solaris audio plugin
later.
The motherboard is Mercury with the sis 730s chipset.
It's very stable, because I have a home web server on this machine
and it I didn't have lockups, so it's not hardware related.
We had another problem with oss+sis7018 in the past (lockup immediately
after running soundon) but that was fixed by enabling the AC 97 modem
in the bios. Now I have tried different settings in the BIOS but
without success.
If on sis 630 works fine, the conclusion is that the 730 motherboard has
some glitches which interact badly with OSS.[/quote]
Guest
 


Return to Solaris

Who is online

Users browsing this forum: No registered users and 1 guest

cron