Re: 2.6.18-rc6 (audio-related ?) oops during boot

[Takashi Iwai <tiwai@suse.de>]

At Wed, 6 Sep 2006 02:10:10 +0200,
Filip Sneppe wrote:
> 
> Hi,
> 
> On 9/5/06, Takashi Iwai <tiwai@suse.de> wrote:
> > At Tue, 5 Sep 2006 12:13:24 +0200,
> > Filip Sneppe wrote:
> > >
> > > Hi,
> > >
> > > I tried out 2.6.18-rc6 today and got this during the boot on my
> > > Debian testing machine:
> > >
> > > pnp: Device 00:04 disabled.
> > > cs: IO port probe 0x100-0x4ff: clean.
> > > cs: IO port probe 0x800-0x8ff: clean.
> > > cs: IO port probe 0xc00-0xcff: clean.
> > > cs: IO port probe 0xa00-0xaff: clean.
> > > Adding 730948k swap on /dev/hda2.  Priority:-1 extents:1 across:730948k
> > > EXT3 FS on hda5, internal journal
> > > kobject_add failed for audio with -EEXIST, don't try to register
> > > things with the same name in the same directory.
> > >  [<b01aa41c>] kobject_add+0x13c/0x163
> > >  [<b0205b01>] class_device_add+0x9f/0x3c1
> > >  [<b01aa19c>] kobject_get+0x12/0x17
> > >  [<b01aa49d>] kobject_init+0x32/0x43
> > >  [<b0205eaf>] class_device_create+0x76/0x98
> > >  [<f091c195>] sound_insert_unit+0xea/0x113 [soundcore]
> > >  [<f091c387>] register_sound_special_device+0x125/0x12d [soundcore]
> > >  [<b01ace3c>] vsnprintf+0x413/0x452
> > >  [<f0944d65>] snd_register_oss_device+0x111/0x16c [snd]
> > >  [<f0ae74e4>] register_oss_dsp+0x31/0x53 [snd_pcm_oss]
> > >  [<b0112318>] __activate_task+0x1c/0x28
> > >  [<b01a9fa6>] idr_get_new+0xf/0x30
> > >  [<b0177791>] proc_register+0x31/0xd6
> > >  [<b0177b93>] create_proc_entry+0x86/0x98
> > >  [<f094278e>] snd_create_proc_entry+0xb/0x1a [snd]
> > >  [<f094281e>] snd_info_register+0x81/0x86 [snd]
> > >  [<f0ae912c>] snd_pcm_oss_register_minor+0x31/0x122 [snd_pcm_oss]
> > >  [<b0161667>] alloc_inode+0xf5/0x182
> > >  [<b0161e21>] new_inode+0x16/0x6f
> > >  [<b0160440>] d_instantiate+0x3a/0x70
> > >  [<b017fb6e>] sysfs_new_dirent+0x1a/0x62
> > >  [<b017fc64>] sysfs_make_dirent+0x19/0x6e
> > >  [<b017f610>] sysfs_add_file+0x48/0x63
> > >  [<b0139e0b>] free_hot_cold_page+0x8d/0xd8
> > >  [<f0963fa8>] snd_pcm_notify+0x7a/0x9a [snd_pcm]
> > >  [<f0889061>] alsa_pcm_oss_init+0x61/0x6e [snd_pcm_oss]
> > >  [<b012b225>] sys_init_module+0x13aa/0x1506
> > >  [<b0102a09>] sysenter_past_esp+0x56/0x79
> > > device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@redhat.com
> > > kjournald starting.  Commit interval 5 seconds
> > > EXT3 FS on hda1, internal journal
> > > EXT3-fs: mounted filesystem with ordered data mode.
> > > kjournald starting.  Commit interval 5 seconds
> > > EXT3 FS on hda8, internal journal
> > > EXT3-fs: mounted filesystem with ordered data mode.
> > > kjournald starting.  Commit interval 5 seconds
> > > EXT3 FS on hda6, internal journal
> >
> > Did you load any other OSS modules in prior?
> >
> >
> 
> This happened during the boot, so I don't know exactly what was already loaded.
> The only modules that I know for sure are loaded at boot, are:
> 
> ide-cd
> ide-disk
> ide-generic
> psmouse
> sound
> snd-mixer-oss
> snd-pcm-oss

Hm it looks OK.  So, you loaded snd-mixer-oss and snd-pcm-oss before
any other ALSA drivers, right?  Then it's weird.
The only caller of snd_pcm_oss_register_minor() is
snd_pcm_dev_reigster(), and it's never called unless you initialize a
sound card.

Could you check what entries exist in /sys/class/sound?

Also, what is the reason to load snd-mixer-oss and snd-pcm-oss at this
point at all?


Takashi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/