Your message dated Sun, 23 Jun 2013 16:09:12 +0200
with message-id <20130623140911.GC5918@pisco.westfalen.local>
and subject line Closing
has caused the Debian Bug report #531217,
regarding BUG: warning at kernel/cpu.c:51/unlock_cpu_hotplug()
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
531217: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=531217
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6-686
Hi,
I've being using debian 5.0, with Linux version 2.6.18-6-686 (Debian
2.6.18.dfsg.1-23etch1) (da...@debian.org) (gcc version 4.1.2 20061115
(prerelease) (Debian 4.1.1-21)) #1 SMP Fri Dec 12 16:48:28 UTC 2008.
In this server is running zimbra 5.0.14. When I used dmesg, this warning
messages appear:
BUG: warning at kernel/cpu.c:51/unlock_cpu_hotplug()
[<c0132a2c>] unlock_cpu_hotplug+0x2c/0x54
[<c011871b>] sched_getaffinity+0x67/0x6e
[<c0118741>] sys_sched_getaffinity+0x1f/0x41
[<c0102c11>] sysenter_past_esp+0x56/0x79
I would like to know how can I proceed? Upgrade to the kernel?
thanks,
Eduardo Eloy Irgang
eduardo_irg...@yahoo.com.br
Veja quais são os assuntos do momento no Yahoo! +Buscados
http://br.maisbuscados.yahoo.com
--- End Message ---
--- Begin Message ---
Hi,
your bug has been filed against the "linux-2.6" source package and was filed for
a kernel older than the recently released Debian 7.x / Wheezy with a severity
less than important.
We don't have the ressources to reproduce the complete backlog of all older
kernel
bugs, so we're closing this bug for now. If you can reproduce the bug with
Debian Wheezy
or a more recent kernel from testing or unstable, please reopen the bug by
sending
a mail to cont...@bugs.debian.org with the following three commands included in
the
mail:
reopen BUGNUMBER
reassign BUGNUMBER src:linux
thanks
Cheers,
Moritz
--- End Message ---
