I have tried to change /etc/init.d/alsasound to bypass this error, It is successful till the login page (I hear login sound)
After I login, the volume is really quiet and I barely hear a small noise when running music for example.
I am supposed each time I login to do any of the above workarounds.

I'm seeing the "file descriptor in bad state" message at boot as well with 3.7.0 (Intel HDA), using KDE here and once the audio control centre has identified the new devices, and deleted the old, it doesn't appear to have any adverse effect on volumes - save and restore works OK across boots. I haven't tested if the HDMI output through my NVidia card works though, maybe that's what the errors are related to._________________Jingle Jangle Jewellery

EddyC, since you are using the gnome profile, am I correct to assume you are using Gnome? Can you temporarily install some other WM or DE (such as XFCE, LXDM or Fluxbox) and see if you have the same problem?_________________Gentoo Studio in open beta. Feedback wanted.

EddyC, since you are using the gnome profile, am I correct to assume you are using Gnome? Can you temporarily install some other WM or DE (such as XFCE, LXDM or Fluxbox) and see if you have the same problem?

It appears as if this is just another bug showing up in 3.7.0. At first blush, 3.7.0 seems to have some pretty intense bugs.

I have one machine that just won't run with it. This is a headless server that somehow forgot that it has reiserfs. I had to rustle up a monitor and power cord and backpedal it to 3.6.8, which of course, booted quite normally.

On this machine, it won't load the wireless driver (ndiswrapper), and I get a general feeling of instability from this batch of source. I'd recommend writing bug reports on all the separate audio issues. You can start with Gentoo's Bugzilla, but you will most likely also have to post a bug report at the kernel-dot-org Bugzilla as well. If the ndiswrapper bug hasn't been fixed yet, I'll probably end my day sending that one along. It's been a while since I posted a bug report. Woohoo! More emails!

Not sure if this is related, but for my sound card (creative xfi) I had to reset / save mixer levels after switching to 3.7.0. It would print a similar message to the OP's (didn't write it down though) and cause noise. So something about the asound.state file changed.

See if it still happens when you delete/rename /etc/asound.state /var/lib/alsa/asound.state and (after a reboot) you recreate them using /etc/init.d/alsasound save and alsactl store

EddyC, since you are using the gnome profile, am I correct to assume you are using Gnome? Can you temporarily install some other WM or DE (such as XFCE, LXDM or Fluxbox) and see if you have the same problem?

Not sure if this is related, but for my sound card (creative xfi) I had to reset / save mixer levels after switching to 3.7.0. It would print a similar message to the OP's (didn't write it down though) and cause noise. So something about the asound.state file changed.

See if it still happens when you delete/rename /etc/asound.state /var/lib/alsa/asound.state and (after a reboot) you recreate them using /etc/init.d/alsasound save and alsactl store

EddyC, see pappy_mcfae's post above. It is likely this is a kernel bug, and you could either file a bug report or downgrade to a kernel that does not have this issue._________________Gentoo Studio in open beta. Feedback wanted.

There are times when I wonder what's happening at kernel-dot-com. There was a period of time before KMS became stable that I had to stick with an older kernel source that didn't demand it. That period was about nine months long. What a drag.

I say again folks, send bug reports. Even better, perhaps post the bug report here so others can see if it fits their situation as well. That way, they can keep an eye on coming changes.