"WARNING: at /build/buildd/linux-2.6.38/kernel/printk.c:288 do_syslog+0xa4/0x4c0()" shown after syslog-ng installation

[Juozas Pocius]

Installed syslog-ng; The system log viewer, terminal and firefox browser was open and then this "bug" popped up. It's nature remains unknown to me as now. Some messages might be Lithuanian.

ProblemType: KernelOops
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.38-8-generic 2.6.38-8.42
Regression: No
Reproducible: No
ProcVersionSignature: hostname 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: juozas 1514 F.... pulseaudio
CRDA: Error: [Errno 2] Toks failas ar aplankas neegzistuoja
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfcffc000 irq 44'
   Mixer name : 'Realtek ALC887'
   Components : 'HDA:10ec0887,1043840b,00100202'
   Controls : 24
   Simple ctrls : 14
Card1.Amixer.info:
 Card hw:1 'NVidia'/'HDA NVidia at 0xfeafc000 irq 16'
   Mixer name : 'Nvidia GPU 0b HDMI/DP'
   Components : 'HDA:10de000b,10de0101,00100100'
   Controls : 16
   Simple ctrls : 4
Date: Thu Apr 14 11:30:59 2011
Failure: oops
Frequency: I don't know.
HibernationDevice: RESUME=UUID=b1a27474-7155-4552-9820-32b1c3fb6ae7
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.

 vboxnet0 no wireless extensions.
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=427aaa6f-4f6c-411b-a11e-d671b7557303 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-2.6.38-8-generic N/A
 linux-backports-modules-2.6.38-8-generic N/A
 linux-firmware 1.50
RfKill:

SourcePackage: linux
Title: WARNING: at /build/buildd/linux-2.6.38/kernel/printk.c:288 do_syslog+0xa4/0x4c0()
UpgradeStatus: Upgraded to natty on 2011-04-08 (5 days ago)
dmi.bios.date: 06/01/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0505
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5G41-M LE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0505:bd06/01/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5G41-MLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Serge Hallyn (serge-hallyn)]

Thanks for taking the time to submit this bug and helping to make Ubuntu better.

syslog-ng is using the cap_sys_admin capability rather than cap_syslog. The message you saw is just a warning and will only be printed once. If anything else happened, or anything was broken, then that would be unrelated to this message, so please point it out.

Upstream does not yet have an update to accommodate the new capability, so I'm proposing a patch (in a linked bzr tree) which should fix the message.

[Serge Hallyn (serge-hallyn)]

Could you try this package and confirm that it fixes the problem and doesn't introduce any new ones?

I've tested it locally and it seemed good.

[Serge Hallyn (serge-hallyn)]

note that enhancing the same patch to also remove cap_sys_admin from the capabilities lists also works fine on my test box.

It seems a bit late in the cycle to risk that though.

[Juozas Pocius (juozaspo)]

well, i removed syslog-ng and went back to rsyslog since this looks working better, though i might try that as soon when possible :)

[Jeremy Foshee (jeremyfoshee)]

Set Won't Fix for Natty. The development task will remain open so that we can track this issue.

~JFo

[sankari (istenber)]

I got this same bug. It somehow prevents me to report it automatically, but starts bug reporting tool which is annoying.

This doesn't seem to have any effect on system functioning.

[ 17.039616] WARNING: at /build/buildd/linux-2.6.38/kernel/printk.c:288 do_syslog+0xa4/0x4c0()
[ 17.039619] Hardware name: 945GCT-M2
[ 17.039621] Attempt to access syslog with CAP_SYS_ADMIN but no CAP_SYSLOG (deprecated).
[ 17.039623] Modules linked in: microcode parport_pc ppdev snd_hda_codec_idt snd_hda_intel snd_hda_codec snd_hwdep snd_pcm i915 snd_seq_midi snd_rawmidi joydev snd_seq_midi_event snd_seq snd_timer snd_seq_device drm_kms_helper snd drm ndiswrapper serio_raw soundcore i2c_algo_bit video snd_page_alloc it87 hwmon_vid coretemp lp parport usbhid hid 8139too 8139cp btrfs zlib_deflate libcrc32c
[ 17.039666] Pid: 1038, comm: syslog-ng Tainted: P 2.6.38-7-generic #39-Ubuntu
[ 17.039669] Call Trace:
[ 17.039675] [<c104f912>] ? warn_slowpath_common+0x72/0xa0
[ 17.039679] [<c1050a54>] ? do_syslog+0xa4/0x4c0
[ 17.039683] [<c1050a54>] ? do_syslog+0xa4/0x4c0
[ 17.039687] [<c104f9e3>] ? warn_slowpath_fmt+0x33/0x40
[ 17.039691] [<c1050a54>] ? do_syslog+0xa4/0x4c0
[ 17.039696] [<c1175ac7>] ? proc_lookup+0x17/0x20
[ 17.039700] [<c11700c1>] ? proc_root_lookup+0x21/0x50
[ 17.039705] [<c112fdf7>] ? d_alloc_and_lookup+0x37/0x70
[ 17.039708] [<c116f823>] ? proc_reg_open+0x33/0x140
[ 17.039712] [<c116f823>] ? proc_reg_open+0x33/0x140
[ 17.039716] [<c117a310>] ? kmsg_open+0x20/0x30
[ 17.039719] [<c116f878>] ? proc_reg_open+0x88/0x140
[ 17.039722] [<c117a2c0>] ? kmsg_release+0x0/0x30
[ 17.039726] [<c117a2f0>] ? kmsg_open+0x0/0x30
[ 17.039730] [<c1125031>] ? __dentry_open+0xc1/0x280
[ 17.039734] [<c112639e>] ? nameidata_to_filp+0x6e/0x80
[ 17.039737] [<c116f7f0>] ? proc_reg_open+0x0/0x140
[ 17.039741] [<c11337ff>] ? finish_open+0xaf/0x1a0
[ 17.039744] [<c11330a8>] ? do_path_lookup+0x68/0x120
[ 17.039748] [<c1133e47>] ? do_filp_open+0x207/0x6e0
[ 17.039753] [<c10b44a2>] ? call_rcu_sched+0x12/0x20
[ 17.039757] [<c127b8f2>] ? copy_to_user+0x42/0x60
[ 17.039762] [<c1126406>] ? do_sys_open+0x56/0x120
[ 17.039766] [<c11264fe>] ? sys_open+0x2e/0x40
[ 17.039772] [<c1509904>] ? syscall_call+0x7/0xb
[ 17.039775] ---[ end trace 090de38aa73ca534 ]---

[Alessandro Menti (elgaton)]

Confirmed on Ubuntu 11.04 and 11.10 per bug #759590 and bug #883572.

According to https://bugs.launchpad.net/ubuntu/+source/syslog-ng/+bug/759590/comments/3, an easy workaround is to update to at least syslog-ng 3.3.

[Peter Czanik (pczanik)]

Tested on Ubuntu 11.10: syslog-ng 3.3 packages from one of the syslog-ng developers work fine, without the warning message.

deb http://packages.madhouse-project.org/ubuntu oneiric syslog-ng
deb-src http://packages.madhouse-project.org/ubuntu oneiric syslog-ng

syslog-ng was updated to 3.3.1 in Debian unstable ( http://packages.qa.debian.org/s/syslog-ng.html ), so it can be fixed for ubuntu 12.04

[penalvch (penalvch)]

Jouzas Pocius, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.