My only issue is that this happens on upgrade. At which point, the 2.6.15 kernel is not booted, so this cannot be a bug in that package. It may be a bug in 2.6.12 kernel, but the fact that it only occurs on upgrade leads me to believe that pcmcia-cs or something is doing the wrong this on upgrade (peforming tasks that should only be done when 2.6.15 is finally booted).
My only issue is that this happens on upgrade. At which point, the 2.6.15 kernel is not booted, so this cannot be a bug in that package. It may be a bug in 2.6.12 kernel, but the fact that it only occurs on upgrade leads me to believe that pcmcia-cs or something is doing the wrong this on upgrade (peforming tasks that should only be done when 2.6.15 is finally booted).