Prev: Linux compatible mainboards -another thought
Next: Turning on/off webcam IR leds
From: Redalert Commander on 22 Apr 2010 17:10
Hi,

I was fiddling around in virtualbox when suddenly the sound started
stuttering on the host system.
After I killed rhythmbox, sounds wouldn't play anymore (tried rhythmbox
and aplay).
I noticed the following entries in the logfile:
/var/log/kern.log
Apr 22 21:41:19 pc-steven kernel: [ 775.696004] eth0: no IPv6 routers
present
Apr 22 21:41:20 pc-steven kernel: [ 776.473516] end_request: I/O error,
dev fd0, sector 0
Apr 22 21:41:20 pc-steven kernel: [ 776.504018] end_request: I/O error,
dev fd0, sector 0
Apr 22 21:47:33 pc-steven kernel: [ 1149.761000] warning: `VirtualBox'
uses 32-bit capabilities (legacy support in use)
Apr 22 21:48:40 pc-steven kernel: [ 1216.577409] __ratelimit: 1628
callbacks suppressed
Apr 22 21:48:45 pc-steven kernel: [ 1221.584815] __ratelimit: 1426
callbacks suppressed
Apr 22 21:48:50 pc-steven kernel: [ 1226.603878] __ratelimit: 1126
callbacks suppressed

Those __ratelimit entries started piling up quite rapidly (starting at
the point where sound started stuttering), closing rhythmbox reduced
these number to around 500, then closing down virtual box reduced the
number to less than 100.

After rebooting (I rebooted twice to make sure), the sound didn't come
up again, and looking at the logs I noticed the following in dmesg
[ 4.308987] ENS1371 0000:07:00.0: PCI INT A -> GSI 16 (level, low) ->
IRQ 16
[ 5.782051] AC'97 0 access is not valid [0xffffffff], removing mixer.
[ 5.800009] ENS1371 0000:07:00.0: PCI INT A disabled
[ 5.800014] ENS1371: probe of 0000:07:00.0 failed with error -5

During boot an error was displayed about the sound card right after the
line "waiting for /dev to be fully populated".

I turned off the machine, flipped the power button on the power supply
into 'off' mode and removed the sound card.
Not noticing anything strange or burnt, I put it back in, same slot
(PCI) and let the machine start up again, the error was gone and sound
was restored.

But I still wonder what the cause of this issue was, a bug? A spark
somewhere in the universe?

Can anyone shine a light on this?
The system is running Debian Squeeze, fully up to date, using nvidia
driver 195.36.15, apart from that and the virtualbox modules, it's a
pretty basic desktop install.

If someone needs additional information, don't hesitate to ask.
Up until now, I have been unable to reproduce the problem.

Best regards,
Steven


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/1271970278.2660.22.camel(a)pc-steven.LAN
 | 
Pages: 1
Prev: Linux compatible mainboards -another thought
Next: Turning on/off webcam IR leds