Bug#992328: snmpd init script isn't sourcing /etc/default/snmpd, uses always default parameters
Package: snmpd Version: 5.7.3+dfsg-5+deb10u2 When starting snmpd on a non-systemd machine the init script /etc/init.d/snmpd fails to source the file /etc/default/snmpd which results in SNMPDOPTS specified in the default file being ignored: % grep ^SNMPDOPTS /etc/default/snmpd SNMPDOPTS='-Lf /dev/null -u Debian-snmp -g Debian-snmp -I -smux,mteTrigger,mteTriggerConf -p /run/snmpd.pid' % service snmpd restart [ ok ] Restarting SNMP Services: snmpd. % ps auxf|grep snmpd Debian-+ 3480 0.0 0.0 33872 8344 ?S12:28 0:00 /usr/sbin/snmpd -Lsd -Lf /dev/null -u Debian-snmp -g Debian-snmp -I -smux mteTrigger mteTriggerConf -p /run/snmpd.pid Please note the parameter "-Lsd" to snmpd in the process list which is not present in SNMPDOPTS in /etc/default/snmpd. Snippet from the init script: DEFAULT_SNMPDOPTS="-Lsd -Lf /dev/null -u Debian-snmp -g Debian-snmp -I -smux,mteTrigger,mteTriggerConf" [ -z "$SNMPDOPTS" ] && SNMPDOPTS=$DEFAULT_SNMPDOPTS It checks $SNMPDOPTS which isn't defined because the defaults file wasn't sourced. The init script from snmpd from stretch has these lines: # Reads config file (will override defaults above) [ -r /etc/default/snmpd ] && . /etc/default/snmpd After updating snmpd from stretch to buster the default file is being ignored. This affects buster (oldstable) snmpd-5.7.3+dfsg-5+deb10u2 bullseye (stable) snmpd-5.9+dfsg-3+b1
Bug#844446: Same on linux-image-4.9.0-1-amd64-4.9.6-3
Same issue with linux-image-4.9.0-1-amd64-4.9.6-3 but slightly different path: Machine boots but many programs such as 'hostname` do segfault. Workaround: Remove from the VM xml ii linux-base 4.5 ii linux-image-4.7.0-1-amd64 4.7.8-1<-- works fine ii linux-image-4.8.0-2-amd64 4.8.15-2 <-- kernel panic ii linux-image-4.9.0-1-amd64 4.9.6-3<-- segfaults, root readonly, no network ii linux-image-amd64 4.8+77 For google: WARNING: CPU: 0 PID: 0 at /build/linux-8fxPc5/linux-4.9.6/arch/x86/kernel/fpu/xstate.c:593 fpu__init_system_xstate+0x53b/0x98 [0.00] Call Trace: [0.00] [] ? dump_stack+0x5c/0x78 [0.00] [] ? __warn+0xbe/0xe0 [0.00] [] ? warn_slowpath_fmt+0x5f/0x80 [0.00] [] ? xfeature_size+0x5a/0x78 [0.00] [] ? fpu__init_system_xstate+0x53b/0x981 [0.00] [] ? msr_clear_bit+0x36/0xa0 [0.00] [] ? fpu__init_system+0x208/0x30b [0.00] [] ? setup_arch+0xb8/0xcc6 [0.00] [] ? printk+0x57/0x73 [0.00] [] ? early_idt_handler_array+0x120/0x120 [0.00] [] ? start_kernel+0xab/0x463 [0.00] [] ? early_idt_handler_array+0x120/0x120 [0.00] [] ? x86_64_start_kernel+0x14c/0x170 Please see attached file 'dmesg-4.9.0-1-amd64.txt`.Source: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=86 [0.00] Linux version 4.9.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 20170124 (Debian 6.3.0-5) ) #1 SMP Debian 4.9.6-3 (2017-01-28) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-1-amd64 root=/dev/mapper/vgiceteasys-root ro clocksource=hpet elevator=deadline ipv6.disable=1 quiet [0.00] [ cut here ] [0.00] WARNING: CPU: 0 PID: 0 at /build/linux-8fxPc5/linux-4.9.6/arch/x86/kernel/fpu/xstate.c:593 fpu__init_system_xstate+0x53b/0x981 [0.00] XSAVE consistency problem, dumping leaves [0.00] Modules linked in: [0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 4.9.0-1-amd64 #1 Debian 4.9.6-3 [0.00] b9928e34 ba203e08 [0.00] b9676dde 000a ba203e60 0340 [0.00] ba203e90 ba203e9c 0100 b9676e5f [0.00] Call Trace: [0.00] [] ? dump_stack+0x5c/0x78 [0.00] [] ? __warn+0xbe/0xe0 [0.00] [] ? warn_slowpath_fmt+0x5f/0x80 [0.00] [] ? xfeature_size+0x5a/0x78 [0.00] [] ? fpu__init_system_xstate+0x53b/0x981 [0.00] [] ? msr_clear_bit+0x36/0xa0 [0.00] [] ? fpu__init_system+0x208/0x30b [0.00] [] ? setup_arch+0xb8/0xcc6 [0.00] [] ? printk+0x57/0x73 [0.00] [] ? early_idt_handler_array+0x120/0x120 [0.00] [] ? start_kernel+0xab/0x463 [0.00] [] ? early_idt_handler_array+0x120/0x120 [0.00] [] ? x86_64_start_kernel+0x14c/0x170 [0.00] ---[ end trace 8ee85f510287bc4a ]--- [0.00] CPUID[0d, 00]: eax=0007 ebx=0340 ecx=0340 edx= [0.00] CPUID[0d, 01]: eax=000f ebx= ecx= edx= [0.00] CPUID[0d, 02]: eax=0100 ebx=0240 ecx= edx= [0.00] CPUID[0d, 03]: eax= ebx= ecx= edx= [0.00] CPUID[0d, 04]: eax= ebx= ecx= edx= [0.00] CPUID[0d, 05]: eax= ebx= ecx= edx= [0.00] CPUID[0d, 06]: eax= ebx= ecx= edx= [0.00] CPUID[0d, 07]: eax= ebx= ecx= edx= [0.00] CPUID[0d, 08]: eax= ebx= ecx= edx= [0.00] CPUID[0d, 09]: eax= ebx= ecx= edx= [0.00] CPUID[0d, 0a]: eax= ebx= ecx= edx= [0.00] CPUID[0d, 0b]: eax= ebx= ecx= edx= [0.00] CPUID[0d, 0c]: eax= ebx= ecx= edx= [0.00] CPUID[0d, 0d]: eax= ebx= ecx= edx= [0.00] CPUID[0d, 0e]: eax= ebx= ecx= edx= [0.00] CPUID[0d, 0f]: eax= ebx= ecx= edx= [0.00] CPUID[0d, 10]: eax= ebx= ecx= edx= [0.00] CPUID[0d, 11]: eax= ebx= ecx= edx= [0.00] CPUID[0d, 12]: eax= ebx= ecx= edx= [0.00] CPUID[0d, 13]: eax= ebx= ecx= edx= [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' [0.00] [ cut here ] [0.00] WARNING: CPU:
Bug#844446: Still an issue
This is still an issue with latest kernel in stretch. KVM/QEMU Guest VM running Debian stretch on top of Host running Debian jessie with libvirt guest settings: ---snip--- 4 ---snip--- Processor on Host is: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 94 model name : Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz stepping: 3 microcode : 0x55 cpu MHz : 800.000 cache size : 8192 KB physical id : 0 siblings: 8 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 22 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon p ebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_t imer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm m px rdseed adx smap clflushopt bogomips: 6816.04 clflush size: 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management: Guest VM running ii linux-base 4.5 ii linux-image-4.7.0-1-amd64 4.7.8-1<-- works fine ii linux-image-4.8.0-2-amd64 4.8.15-2 <-- kernel panic ii linux-image-amd64 4.8+77 Workaround Removing libvirt block ---snip--- ---snip--- fixes the problem, guest VM kernel boots without problems.
Bug#847981: Duplicate of 844446
This seems to be a duplicate of #86 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=86
Bug#844315: tzdata version breaks dist-upgrade leaving version from oldstable security installed
I like my systems to have packages from stable and stable security only. So when I do a dist-upgrade and remove old/outdated/not needed packages I expect to have all remaining packages to be from stable. tzdata - although with a newer version - being stuck on oldstable, is not expected. It doesn't break anything in terms of "something doesn't work" but more in terms of "it simply shouldn't be this way". So, I'm with you - "critical" might not be the appropriate severity here. Marcel
Bug#844315: tzdata version breaks dist-upgrade leaving version from oldstable security installed
Package: tzdata Version: 2016i-0+deb7u1 Severity: critical Upgrading a fully updated wheezy system (incl. security repo) to jessie (incl. security repo) results in tzdata not being updated because the version in wheezy-security is newer than in jessie. Package tzdata on amd64 wheezy: 2016d-0+deb7u1 wheezy-security: 2016i-0+deb7u1 jessie: 2016f-0+deb8u1 jessie-updates: 2016i-0+deb8u1 jessie-proposed-updates: 2016i-0+deb8u1 Using only the main repo + security repo results in tzdata not being updates since wheezy-securities '2016i-0+deb7u1' is higher than jessies '2016f-0+deb8u1'. Comment from IRC: That's indeed unfortunate. You can work around the problem by adding jessie-updates, though. I think it's because wheezy didn't have a wheezy-updates, so all updates must go through wheezy-security, whereas in jessie all non-critical updates go through jessie-updates, and get wrapped up in point releases every few months. It's still a bug though, I'd report it on the tzdata package. Might warrant a RC severity, since it breaks automatic upgrades and is easy to fix.
Bug#834416: Acknowledgement (xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: Invalid argument)
Just had a chat in #xfs on freenode and it might be that a previous xfs_growfs under an older kernel didn't zero enough. When I recall it correctly the XFS filesystem in question was resized in the past under then stable Debian Wheezy (might even have been resized under Debian Squeeze). Chat for reference: < bfoster> strange, seems like it is running a verifier on the secondary sb's < bfoster> e.g., commit 1375cb65e, but that fix seems to go way back < bfoster> did growfs run and fail prior to the run with these reported errors? < thermoman> bfoster: never had problems before < thermoman> but the FS might have been created with an older xfsprogs and it has been definately be resized before < bfoster> or hmm, perhaps its remnants from a previous growfs < bfoster> ok, I think that makes more sense, you went from 109 ags to 160 some odd ags < bfoster> and grow/repair is complaining about ags below that 109 threshold < bfoster> which suggests the previous grows didn't zero enough, or whatever that old problem was < bfoster> I think the kernel you're on now should "do the right thing" Might be related: http://xfs.org/index.php/XFS_FAQ#Q:_I.27m_getting_.22Internal_error_xfs_sb_read_verify.22_errors_when_I_try_to_run_xfs_growfs_under_kernels_v3.10_through_v3.12
Bug#834416: xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: Invalid argument
Package: xfsprogs
Version: 3.2.1
Severity: important
xfs_growfs did corrupt a filesystem on a up2date Debian Jessie system.
Might be a kernel problem and not xfsprogs related.
% pvresize /dev/vda2
% xfs_growfs /dev/mapper/vg0-home
meta-data=/dev/mapper/vg0-home isize=256agcount=109, agsize=229376
blks
= sectsz=512 attr=2, projid32bit=0
= crc=0finobt=0
data = bsize=4096 blocks=24878080,
imaxpct=25
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0 ftype=0
log =internal bsize=4096 blocks=2560, version=2
= sectsz=512 sunit=0 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: Invalid argument
data blocks changed from 24878080 to 37985280
% dmesg
[ 806.321683] XFS (dm-2): bad magic number
[ 806.321699] XFS (dm-2): metadata I/O error: block 0x968
("xfs_trans_read_buf_map") error 22 numblks 1
[ 806.322715] XFS (dm-2): error 22 reading secondary superblock for ag
86
[ 806.323088] XFS (dm-2): bad magic number
[ 806.323096] XFS (dm-2): metadata I/O error: block 0x984
("xfs_trans_read_buf_map") error 22 numblks 1
[ 806.324175] XFS (dm-2): error 22 reading secondary superblock for ag
87
[ 806.324697] XFS (dm-2): bad magic number
[ 806.324705] XFS (dm-2): metadata I/O error: block 0x9a0
("xfs_trans_read_buf_map") error 22 numblks 1
[ 806.325727] XFS (dm-2): error 22 reading secondary superblock for ag
88
[ 806.326075] XFS (dm-2): bad magic number
[ 806.326082] XFS (dm-2): metadata I/O error: block 0x9bc
("xfs_trans_read_buf_map") error 22 numblks 1
[ 806.327061] XFS (dm-2): error 22 reading secondary superblock for ag
89
[..]
% umount /home
% xfs_repair /dev/mapper/vg0-home
xfs_repair /dev/mapper/vg0-home
Phase 1 - find and verify superblock...
- reporting progress in intervals of 15 minutes
Phase 2 - using internal log
- zero log...
- scan filesystem freespace and inode maps...
zeroing unused portion of secondary superblock (AG #9)
zeroing unused portion of secondary superblock (AG #64)
zeroing unused portion of secondary superblock (AG #66)
zeroing unused portion of secondary superblock (AG #61)
zeroing unused portion of secondary superblock (AG #58)
zeroing unused portion of secondary superblock (AG #62)
zeroing unused portion of secondary superblock (AG #59)
zeroing unused portion of secondary superblock (AG #63)
bad magic number
bad on-disk superblock 86 - bad magic number
primary/secondary superblock 86 conflict - AG superblock geometry info
conflicts with filesystem geometry
reset bad sb for ag 86
bad magic number
bad on-disk superblock 87 - bad magic number
primary/secondary superblock 87 conflict - AG superblock geometry info
conflicts with filesystem geometry
reset bad sb for ag 87
zeroing unused portion of secondary superblock (AG #60)
bad magic number
bad magic number
bad magic number
bad on-disk superblock 90 - bad magic number
primary/secondary superblock 90 conflict - AG superblock geometry info
conflicts with filesystem geometry
zeroing unused portion of secondary superblock (AG #90)
non-null project quota inode field in superblock 90
reset bad sb for ag 90
bad on-disk superblock 88 - bad magic number
primary/secondary superblock 88 conflict - AG superblock geometry info
conflicts with filesystem geometry
zeroing unused portion of secondary superblock (AG #88)
non-null project quota inode field in superblock 88
reset bad sb for ag 88
bad on-disk superblock 89 - bad magic number
primary/secondary superblock 89 conflict - AG superblock geometry info
conflicts with filesystem geometry
zeroing unused portion of secondary superblock (AG #89)
non-null project quota inode field in superblock 89
reset bad sb for ag 89
bad magic number
bad on-disk superblock 91 - bad magic number
primary/secondary superblock 91 conflict - AG superblock geometry info
conflicts with filesystem geometry
reset bad sb for ag 91
bad magic number
bad magic number
bad on-disk superblock 93 - bad magic number
primary/secondary superblock 93 conflict - AG superblock geometry info
conflicts with filesystem geometry
reset bad sb for ag 93
bad magic number
bad on-disk superblock 95 - bad magic number
primary/secondary superblock 95 conflict - AG superblock geometry info
conflicts with filesystem geometry
reset bad sb for ag 95
bad on-disk superblock 94 - bad magic number
primary/secondary superblock 94 conflict - AG superblock geometry info
conflicts with filesystem geometry
reset bad sb for ag 94
bad magic number
bad on-disk superblock 96 - bad magic number
primary/secondary superblock 96 conflict - AG superblock geometry info
conflicts with filesystem geometry
reset bad sb for ag 96
bad magic number
bad on-disk superblock 97 - bad magic number
Bug#820110: backuppc: Lib.pm: Unescaped left brace in regex is deprecated
Package: backuppc
Version: 3.3.1-2
Severity: normal
Tags: patch
As of Perl 5.22.0 in some cases curly brackets needs to be escaped.
More info here:
http://perldoc.perl.org/perlre.html#Quantifiers
"If a curly bracket occurs in any other context and does not form
part of a backslashed sequence like \x{...} , it is treated as a
regular character. However, a deprecation warning is raised for
all such occurrences, and in Perl v5.26, literal uses of a curly
bracket will be required to be escaped, say by preceding them
with a backslash ("\{" ) or enclosing them within square brackets
("[{]" ). This change will allow for future syntax extensions
(like making the lower bound of a quantifier optional),
and better error checking of quantifiers.
/usr/share/backuppc/lib/BackupPC/Lib.pm contains such braces in
regexp that throw warnings like:
Unescaped left brace in regex is deprecated, passed through in
regex; marked by <-- HERE in m/\${ <-- HERE (\w+)}(\+?)/
at /usr/share/backuppc/lib/BackupPC/Lib.pm line 1269.
Unescaped left brace in regex is deprecated, passed through in
regex; marked by <-- HERE in m/(.*)\${ <-- HERE (\w+)}(\+?)(.*)/
at /usr/share/backuppc/lib/BackupPC/Lib.pm line 1274.
patch attached.
Marcel--- /usr/share/backuppc/lib/BackupPC/Lib.pm 2016-01-06 12:44:15.0 +0100
+++ /usr/share/backuppc/lib/BackupPC/Lib.pm 2016-04-05 16:23:35.706625290 +0200
@@ -1262,7 +1262,7 @@
#
# Replace scalar variables first
#
-$arg =~ s[\${(\w+)}(\+?)]{
+$arg =~ s[\$\{(\w+)}(\+?)]{
exists($vars->{$1}) && ref($vars->{$1}) ne "ARRAY"
? ($2 eq "+" ? $bpc->shellEscape($vars->{$1}) : $vars->{$1})
: "\${$1}$2"
@@ -1271,7 +1271,7 @@
# Now replicate any array arguments; this just works for just one
# array var in each argument.
#
-if ( $arg =~ m[(.*)\${(\w+)}(\+?)(.*)] && ref($vars->{$2}) eq "ARRAY" ) {
+if ( $arg =~ m[(.*)\$\{(\w+)}(\+?)(.*)] && ref($vars->{$2}) eq "ARRAY" ) {
my $pre = $1;
my $var = $2;
my $esc = $3;
Bug#820092: libcgi-pm-perl
Package: backuppc Version: 3.3.1-2 Severity: normal when upgrading the server that hosts backuppc from jessie to (yet unreleased stretch), backuppc will produce HTTP 500 errors when trying to view the perl-based backuppc dashboard from a web browser. The error logged in the webservers logfile is: Can't locate CGI.pm in @INC (you may need to install the CGI module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.22.1 /usr/local/share/perl/5.22.1 /usr/lib/x86_64-linux-gnu/perl5/5.22 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.22 /usr/share/perl/5.22 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/backuppc/lib/realindex.cgi line 50.: /usr/share/backuppc/cgi-bin/index.cgi Workaround: manually install package libcgi-pm-perl In current stable Debian jessie the package 'perl-modules' contains the file CGI.pm. CGI.pm is not shipped in perl-modules-5.22 anymore. Marcel
Bug#820084: please remove
Hi, the bug should have been filed with the postfix package and not os-prober - my mistake. Please remove/close/invalid this bug. I resent the bug report with the right package name in it so there is no need to assign this bug report to the postfix package. Thanks Marcel
Bug#820090: chroot default value in master.cf changed from yes to no in Postfix 3.0 - init script needs to reflect this
Package: postfix
Version: 3.0.4-5
Severity: important
when upgrading postfix from jessie to (yet unreleased stretch) postfix
warns that master.cf my contain default value '-' for the chroot
column but the default of that chroot value depends on postfix setting
'compatibility_level'.
Please see
http://www.postfix.org/COMPATIBILITY_README.html#chroot
for more details.
postfix init.d script contains this:
---snip---
config_dir=$($POSTCONF -h config_directory)
# see if anything is running chrooted.
NEED_CHROOT=$(awk '/^[0-9a-z]/ && ($5 ~ "[-yY]") { print "y"; exit}'
${config_dir}/master.cf)
---snip---
This needs to be modified to take the output of
`postconf compatibility_level' into account.
If compatibility_level < 2, default value '-' equals to: do chroot.
If compatibility_level >= 2, default value '-' equals to: don't chroot.
Marcel
Bug#820084: chroot default value in master.cf changed from yes to no in Postfix 3.0 - init script needs to reflect this
Package: os-prober
Version: 3.0.4-5
Severity: normal
when upgrading postfix from jessie to (yet unreleased stretch) postfix
warns
that master.cf my contain default value '-' for the chroot column but
the default
of that chroot value depends on postfix setting 'compatibility_level'.
Please see http://www.postfix.org/COMPATIBILITY_README.html#chroot for
more details.
postfix init.d script contains this:
---snip---
config_dir=$($POSTCONF -h config_directory)
# see if anything is running chrooted.
NEED_CHROOT=$(awk '/^[0-9a-z]/ && ($5 ~ "[-yY]") { print "y"; exit}'
${config_dir}/master.cf)
---snip---
This needs to be modified to take the output of 'postconf
compatibility_level'
into account.
If compatibility_level < 2 then the default '-' equals do chroot.
If compatibility_level >= 2 then the default '-' equals don't chroot.
Marcel
Bug#809260: SQL Injection still in the code
Guys,
you just reopened the SQL injection vuln again!
Have a look at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807599#57
where I have described this already.
cacti-0.8.7g-1+squeeze9+deb6u12 is vulnerable now again to SQL
Injection.
Test it:
http://example.com/cacti/graph.php?action=properties_graph_id=3363_id=1%20and%20benchmark(2000%2csha1(1))--%20_type=tree_start=1449752140_end=1449838540
You have to edit
/usr/share/cacti/site/include/top_graph_header.php
and add the line
input_validate_input_regex(get_request_var("rra_id"),
"^([0-9]+|all)$");
in the input validation block.
Bug#807599: Broken cacti image on 0.8.7g-1+squeeze9+deb6u11
Hi,
the build 0.8.7g-1+squeeze9+deb6u11 on Squeeze LTS has the bug fixed -
because now it's broken!
Request the URL
http://example.com/cacti/graph.php?action=view_graph_id=3171_id=all
And you'll get the error:
PHP Fatal error: Call to undefined function
input_validate_input_regex() in /usr/share/cacti/site/graph.php on line
31
This is no wonder because /usr/share/cacti/site/graph.php looks like:
input_validate_input_regex(get_request_var_request("rra_id"),
"^([0-9]+|all)$");
input_validate_input_number(get_request_var_request("local_graph_id"));
input_validate_input_number(get_request_var_request("graph_end"));
input_validate_input_number(get_request_var_request("graph_start"));
input_validate_input_regex(get_request_var_request("view_type"),
"^([a-zA-Z0-9]+)$");
/* */
include("./include/auth.php");
include_once("./lib/rrd.php");
include_once("./lib/html_tree.php");
include_once("./include/top_graph_header.php");
[..]
There is no function 'input_validate_input_regex' defined not any
include done
before on line 31 input_validate_input_regex is used.
This is very dangerous because one could think moving the 4 lines
include block before
the first input_validate_input_ line *reopens* the sql injection!
Please fix this and test afterwards with the URL
http://example.com/cacti/graph.php?action=properties_graph_id=3363_id=1
and benchmark(2000%2csha1(1))--
_type=tree_start=1449752140_end=1449838540
Bug#807599: Fix for broken cacti image on 0.8.7g-1+squeeze9+deb6u11
The much better solution to fix this would be keeping the
include block over the input_validate_* calls in graph.php
(which without more modifications would reopen the sql injection vuln)
and then fix this in
/usr/share/cacti/site/include/top_graph_header.php
where you just have to add the line
input_validate_input_regex(get_request_var("rra_id"),
"^([0-9]+|all)$");
in the input validation block.
Bug#788062: os-prober corrupts LVs/partitions while being mounted inside a VM
Package: os-prober Version: 1.65 Severity: critical update-grub on a vhost running qemu/kvm virtual machines while grub and os-prober is installed on the host might corrupt guest virtual machines / guest disks. Host % lvs LV VGAttr LSize root vg_foobar_sys -wi-ao 3.00g var_logvg_foobar_sys -wi-ao 500.00m vm-lukevg_foobar_dom -wi-ao 40.00g % virsh list --all IdNameState - 9 luke running % virsh domblklist luke Target Source vda/dev/vg_foobar_dom/vm-luke % apt-get upgrade (linux-image-3.16.0-4-amd64 gets upgraded) (update-grub is called) % dmesg Jun 08 09:31:25 sirius os-prober[7402]: debug: running /usr/lib/os-probes/50mounted-tests on /dev/mapper/vg_foobar_dom-vm--luke Jun 08 09:31:25 sirius kernel: EXT4-fs (dm-3): VFS: Can't find ext4 filesystem Jun 08 09:31:25 sirius kernel: EXT4-fs (dm-3): VFS: Can't find ext4 filesystem Jun 08 09:31:25 sirius kernel: EXT4-fs (dm-3): VFS: Can't find ext4 filesystem Jun 08 09:31:25 sirius kernel: XFS (dm-3): Invalid superblock magic number Jun 08 09:31:25 sirius kernel: FAT-fs (dm-3): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! Jun 08 09:31:25 sirius kernel: FAT-fs (dm-3): bogus number of reserved sectors Jun 08 09:31:25 sirius kernel: FAT-fs (dm-3): Can't find a valid FAT filesystem Jun 08 09:31:25 sirius kernel: FAT-fs (dm-3): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! Jun 08 09:31:25 sirius kernel: FAT-fs (dm-3): bogus number of reserved sectors Jun 08 09:31:25 sirius kernel: FAT-fs (dm-3): Can't find a valid FAT filesystem Jun 08 09:31:25 sirius kernel: VFS: Can't find a Minix filesystem V1 | V2 | V3 on device dm-3. Jun 08 09:31:25 sirius kernel: hfsplus: unable to find HFS+ superblock Jun 08 09:31:25 sirius kernel: qnx4: no qnx4 filesystem (no root dir). Jun 08 09:31:25 sirius kernel: You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ... WARNING Wrong ufstype may corrupt your filesystem, default is ufstype=old Inside guest 'luke' === [1100902.892807] end_request: I/O error, dev vda, sector 10774672 [1100902.893914] Buffer I/O error on device dm-2, logical block 10002 [1100902.894781] lost page write due to I/O error on dm-2 [1100902.895219] end_request: I/O error, dev vda, sector 31670147 [1100902.897132] I/O error in filesystem (dm-2) meta-data dev dm-2 block 0x1400f83 (xlog_iodone) error 5 buf count 1024 [1100902.898819] xfs_force_shutdown(dm-2,0x2) called from line 1043 of file /build/linux-2.6-pYQHNk/linux-2.6-2.6.32/debian/build/source_amd64_none/fs/xfs/xfs_log.c. Return address = 0xa01fcb89 [1100902.898827] Filesystem dm-2: Log I/O Error Detected. Shutting down filesystem: dm-2 [1100902.899984] Please umount the filesystem, and rectify the problem(s) [1100934.617120] Filesystem dm-2: xfs_log_force: error 5 returned. [1100970.617117] Filesystem dm-2: xfs_log_force: error 5 returned. [1101006.616137] Filesystem dm-2: xfs_log_force: error 5 returned. It's a bad idea to try to mount every block device found in the system whilst the devices are being used. This could lead to catastrophic failure if I/O heavy VMs get their disks corrupted this way. To me this happened only to one out of 18 VMs but all but 'luke' didn't have much I/O at the time. Workaround == % apt-get purge os-prober OR echo 'GRUB_DISABLE_OS_PROBER=true' /etc/default/grub -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701814: os-prober
Hi, please see #788062 which just corrupted a fs mounted inside a qemu VM. On the host (Debian Jessie) grub-mount was available! thermoman -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650724: Bug still present in wheezy
Hi, this bug is still present in current wheezy release. It seems Grub has problems with LVM where at least one PV is on a partition and not on the whole disk. % fdisk -lu /dev/cciss/c0d? Disk /dev/cciss/c0d0: 36.4 GB, 36385505280 bytes 255 heads, 32 sectors/track, 8709 cylinders, total 71065440 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000a669d Device Boot Start End Blocks Id System /dev/cciss/c0d0p1 *2048 391167 194560 83 Linux /dev/cciss/c0d0p2 3911687106355135336192 8e Linux LVM Disk /dev/cciss/c0d1: 293.6 GB, 293563949056 bytes 255 heads, 32 sectors/track, 70265 cylinders, total 573367088 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x Disk /dev/cciss/c0d1 doesn't contain a valid partition table % pvs PVVG Attr 1st PE PSize DevSize Used PFree /dev/cciss/c0d0p2 vg_mariner5 a--1.00m 33.70g 33.70g 15.00g 18.70g /dev/cciss/c0d1 vg_mariner5 a--1.00m 273.40g 273.40g 60.00g 213.40g % vgs VG #PV #LV #SN Attr VSize VFree #PV #LV #SN #Ext Free Ext vg_mariner5 2 4 0 wz--n- 307.09g 232.09g 2 4 0 78616 59416 4.00m % lvs LVVG Attr LSize Origin Snap% #Seg Start SSize PE Ranges root vg_mariner5 -wi-ao-- 5.00g 10 5.00g /dev/cciss/c0d0p2:0-1279 var vg_mariner5 -wi-ao-- 10.00g 10 10.00g /dev/cciss/c0d0p2:1280-3839 home vg_mariner5 -wi-ao-- 50.00g 10 50.00g /dev/cciss/c0d1:0-12799 mysql vg_mariner5 -wi-ao-- 10.00g 10 10.00g /dev/cciss/c0d1:12800-15359 % df -hT FilesystemType Size Used Avail Use% Mounted on rootfsrootfs5.0G 761M 4.0G 16% / udev devtmpfs 10M 0 10M 0% /dev tmpfs tmpfs 3.2G 224K 3.2G 1% /run /dev/mapper/vg_mariner5-root ext4 5.0G 761M 4.0G 16% / tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs tmpfs 6.3G 0 6.3G 0% /run/shm /dev/mapper/vg_mariner5-var xfs10G 179M 9.9G 2% /var /dev/mapper/vg_mariner5-mysql xfs10G 182M 9.9G 2% /var/lib/mysql /dev/mapper/vg_mariner5-home xfs50G 4.0G 46G 8% /home /dev/cciss/c0d0p1 ext2 184M 22M 154M 13% /boot % cat /boot/grub/device.map (hd0) /dev/cciss/c0d0 (hd1) /dev/cciss/c0d1 % grub-probe --target=device /usr/share/grub/unicode.pf2 error: physical volume pv0 not found. error: physical volume pv0 not found. error: physical volume pv0 not found. error: physical volume pv0 not found. /dev/mapper/vg_mariner5-root % grub-probe --target=abstraction / error: physical volume pv0 not found. error: physical volume pv0 not found. error: physical volume pv0 not found. error: physical volume pv0 not found. lvm % grub-probe --device /dev/mapper/vg_mariner5-root --target=fs error: physical volume pv0 not found. error: physical volume pv0 not found. error: physical volume pv0 not found. error: physical volume pv0 not found. ext2 Deleting device.map and running grub-mkdevicemap does not change anything. * If i change device.map to (hd0) /dev/cciss/c0d0p2 (hd1) /dev/cciss/c0d1 All errors go away! * Verbose Output when device.map has c0d0 in it: % grub-probe -vv --target=abstraction / grub-core/disk/raid.c:740: Scanning for dmraid_nv RAID devices on disk hd0 grub-probe: info: Scanning for dmraid_nv RAID devices on disk hd0. grub-core/kern/disk.c:245: Opening `hd0'... grub-probe: info: the size of hd0 is 71065440. grub-core/kern/emu/hostdisk.c:716: opening the device `/dev/cciss/c0d0' in open_device() grub-core/kern/disk.c:338: Closing `hd0'. grub-core/kern/disk.c:245: Opening `hd0'... grub-probe: info: the size of hd0 is 71065440. grub-core/kern/disk.c:338: Closing `hd0'. grub-core/disk/raid.c:740: Scanning for dmraid_nv RAID devices on disk hd1 grub-probe: info: Scanning for dmraid_nv RAID devices on disk hd1. grub-core/kern/disk.c:245: Opening `hd1'... grub-probe: info: the size of hd1 is 573367088. grub-core/kern/emu/hostdisk.c:716: opening the device `/dev/cciss/c0d1' in open_device() grub-core/kern/disk.c:338: Closing `hd1'. grub-core/kern/disk.c:245: Opening `hd1'... grub-probe: info: the size of hd1 is 573367088. grub-core/kern/disk.c:338: Closing `hd1'. grub-probe: info: scanning hd0 for LVM. grub-core/kern/disk.c:245: Opening `hd0'... grub-probe: info: the size of hd0 is 71065440. grub-core/kern/emu/hostdisk.c:716: opening the device `/dev/cciss/c0d0' in open_device() grub-probe: info: no
Bug#644362: Bug still present in current wheezy Kernel
Hi, i just installed a Proliant DL380 G5 Server with a SmartArray 400 controller from the latest wheezy netboot and can confirm what the bug is still present in latest wheezy kernel in combination with hpacucli. ii linux-image-3.2.0-4-amd64 3.2.41-2 No matter if i use the latest hpacucli with native x64 binaries ii hpacucli 9.20.9.0-1 or an older version that needs 32bit libs ii hpacucli 9.0-24.1 As soon as the create command is issued load rises to 1.00 and the kernel messages start rolling in at intervals of 120 seconds. This is kind of a real bummer for users of debian on HP servers and should be noted in the release notes! Yours Marcel -- Registrierter Linux User #307343 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#598844: 02_cacherejectmsg.patch does modify wrong variable
Hi, Jan Wagner's patch 02_cacherejectmsg.patch from policyd-weight_0.1.15.2-2.debian.tar.gz does modify $REJECTMSG instead of $CACHEREJECTMSG. Original policyd-weight config == $REJECTMSG= 550 Mail appeared to be SPAM or forged. Ask your Mail/DNS-Administrator to correct HELO and DNS MX settings or to get removed from DNSBLs; $CACHEREJECTMSG = '550 temporarily blocked because of previous errors'; policyd-weight-0.1.15.2-2 with applied faulty debian patch == $REJECTMSG= 550 [cached] Mail appeared to be SPAM or forged. Ask your Mail/DNS-Administrator to correct HELO and DNS MX settings or to get removed from DNSBLs; $CACHEREJECTMSG = '550 temporarily blocked because of previous errors'; suggested fix = $REJECTMSG= 550 Mail appeared to be SPAM or forged. Ask your Mail/DNS-Administrator to correct HELO and DNS MX settings or to get removed from DNSBLs; $CACHEREJECTMSG = $REJECTMSG . [cached]; Marcel. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#612439: Acknowledgement (lvconvert --merge breaks Logical Volumes)
What snapshot targets does your kernel contain? (run 'dmsetup targets' and check for a line starting 'snapshot-merge') % dmsetup targets snapshot-origin v1.7.0 snapshot v1.7.0 striped v1.3.0 linear v1.1.0 errorv1.0.1 % strings /lib/modules/$(uname -r)/kernel/drivers/md/dm-* | grep merge blk_queue_merge_bvec Check your kernel message log for any related errors. nothing in there Run the command with - for more detailed information about what's going wrong. see attachment. i believe there is no snapshot-merge target in this kernel version. Marcel.% lvs vg0 LVVG Attr LSize Origin Snap% #Seg #Str Start SSize PE Ranges test vg0 owi-a- 4.00m 110 4.00m /dev/loop5:0-0 test-snap vg0 swi-a- 4.00m test 0.29110 4.00m /dev/loop5:1-1 % lvconvert - --merge vg0/test-snap #lvmcmdline.c:1035 Processing: lvconvert - --merge vg0/test-snap #lvmcmdline.c:1038 O_DIRECT will be used #config/config.c:987 Setting global/locking_type to 1 #config/config.c:987 Setting global/wait_for_locks to 1 #locking/locking.c:240 File-based locking selected. #config/config.c:964 Setting global/locking_dir to /var/lock/lvm #activate/activate.c:361 Getting target version for snapshot #ioctl/libdm-iface.c:1821 dm version OF [16384] #ioctl/libdm-iface.c:1821 dm versions OF [16384] #activate/activate.c:361 Getting target version for snapshot-origin #ioctl/libdm-iface.c:1821 dm versions OF [16384] #toollib.c:198 Using logical volume(s) on command line #locking/file_locking.c:235 Locking /var/lock/lvm/V_vg0 WB #locking/file_locking.c:141 _do_flock /var/lock/lvm/V_vg0:aux WB #locking/file_locking.c:141 _do_flock /var/lock/lvm/V_vg0 WB #locking/file_locking.c:51 _undo_flock /var/lock/lvm/V_vg0:aux #device/dev-io.c:487 Opened /dev/loop0 RO #device/dev-io.c:260 /dev/loop0: size is 0 sectors #filters/filter.c:154 /dev/loop0: Skipping: Too small to hold a PV #device/dev-io.c:533 Closed /dev/loop0 #filters/filter.c:129 /dev/cdrom1: Skipping: Unrecognised LVM device type 11 #device/dev-io.c:487 Opened /dev/root RW O_DIRECT #device/dev-io.c:134 /dev/root: block size is 4096 bytes #label/label.c:184 /dev/root: No label detected #device/dev-io.c:533 Closed /dev/root #device/dev-io.c:487 Opened /dev/vda RO #device/dev-io.c:260 /dev/vda: size is 18874368 sectors #device/dev-io.c:134 /dev/vda: block size is 4096 bytes #filters/filter.c:160 /dev/vda: Skipping: Partition table signature found #device/dev-io.c:533 Closed /dev/vda #device/dev-io.c:487 Opened /dev/loop1 RO #device/dev-io.c:260 /dev/loop1: size is 0 sectors #filters/filter.c:154 /dev/loop1: Skipping: Too small to hold a PV #device/dev-io.c:533 Closed /dev/loop1 #device/dev-io.c:487 Opened /dev/dm-1 RW O_DIRECT #device/dev-io.c:134 /dev/dm-1: block size is 4096 bytes #label/label.c:184 /dev/dm-1: No label detected #device/dev-io.c:533 Closed /dev/dm-1 #device/dev-io.c:487 Opened /dev/vda1 RW O_DIRECT #device/dev-io.c:134 /dev/vda1: block size is 1024 bytes #label/label.c:184 /dev/vda1: No label detected #device/dev-io.c:533 Closed /dev/vda1 #device/dev-io.c:487 Opened /dev/loop2 RO #device/dev-io.c:260 /dev/loop2: size is 0 sectors #filters/filter.c:154 /dev/loop2: Skipping: Too small to hold a PV #device/dev-io.c:533 Closed /dev/loop2 #device/dev-io.c:487 Opened /dev/dm-2 RW O_DIRECT #device/dev-io.c:134 /dev/dm-2: block size is 4096 bytes #label/label.c:184 /dev/dm-2: No label detected #device/dev-io.c:533 Closed /dev/dm-2 #device/dev-io.c:487 Opened /dev/vda2 RW O_DIRECT #device/dev-io.c:134 /dev/vda2: block size is 4096 bytes #label/label.c:160 /dev/vda2: lvm2 label detected #cache/lvmcache.c:1136 lvmcache: /dev/vda2: now in VG #orphans_lvm2 (#orphans_lvm2) #format_text/format-text.c:1137 /dev/vda2: Found metadata at 6656 size 1652 (in area at 4096 size 1044480) for vg_s16 (cAN0Mz-z3eC-6KXD-GCXt-HYli-D89G-5KEvoT) #cache/lvmcache.c:1136 lvmcache: /dev/vda2: now in VG vg_s16 with 1 mdas #cache/lvmcache.c:923 lvmcache: /dev/vda2: setting vg_s16 VGID to cAN0Mzz3eC6KXDGCXtHYliD89G5KEvoT #cache/lvmcache.c:1173 lvmcache: /dev/vda2: VG vg_s16: Set creation host to han-solo. #device/dev-io.c:533 Closed /dev/vda2 #device/dev-io.c:487 Opened /dev/loop3 RO #device/dev-io.c:260 /dev/loop3: size is 0 sectors #filters/filter.c:154 /dev/loop3: Skipping: Too small to hold a PV #device/dev-io.c:533 Closed /dev/loop3 #device/dev-io.c:487 Opened /dev/dm-3 RW O_DIRECT #device/dev-io.c:134
Bug#612439: lvconvert --merge breaks Logical Volumes
Package: lvm2
Version: 2.02.66-5
When i want to restore a logical volume's content from one of it's
snapshots you can use the command:
lvconvert --merge vg/lv-snap
according to manpage:
lvconvert --merge vg00/lvol1_snap
merges vg00/lvol1_snap into its origin.
Problem:
Can't expand LV test: snapshot target support missing from kernel?
Reproducible:
100%
Example:
% dd if=/dev/zero of=/var/tmp/disk bs=1M count=10
% losetup /dev/loop5 /var/tmp/disk
% pvcreate /dev/loop5
Physical volume /dev/loop5 successfully created
% vgcreate vg0 /dev/loop5
Volume group vg0 successfully created
% lvcreate --name test --extents 1 vg0
Logical volume test created
% lvcreate --snapshot vg0/test -n test-snap --extents 1
Logical volume test-snap created
% md5sum /dev/vg0/test{,-snap}
b5cfa9d6c8febd618f91ac2843d50a1c /dev/vg0/test
b5cfa9d6c8febd618f91ac2843d50a1c /dev/vg0/test-snap
% echo changing-some-stuff /dev/vg0/test
% md5sum /dev/vg0/test{,-snap}
0a03546bcdfe5d9f3853c200fffe41f8 /dev/vg0/test
b5cfa9d6c8febd618f91ac2843d50a1c /dev/vg0/test-snap
% lvs vg0
LVVG Attr LSize Origin Snap% Move Log Copy% Convert
test vg0 owi-a- 4.00m
test-snap vg0 swi-a- 4.00m test 0.29
% lvconvert --merge vg0/test-snap
Can't expand LV test: snapshot target support missing from kernel?
Failed to suspend origin test
% lvchange --available n vg0/test
% lvs vg0
LVVG Attr LSize Origin Snap% Move Log Copy% Convert
test vg0 owi--- 4.00m
test-snap vg0 swi--- 4.00m test
% lvconvert --merge vg0/test-snap
Merging of volume test-snap started.
Conversion starts after activation.
% lvchange --available y vg0/test
Can't expand LV test: snapshot target support missing from kernel?
% lvs vg0
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
test vg0 Owi--- 4.00m
At this point LV ,test' can't be accessed anymore.
*
* The only solution here is to restore the LVM metadata for this VG
* from /etc/lvm/archive or to recreate the LV with option --zero n
* on the same extends as before (check with lvs -o +seg_pe_ranges).
*
Expected behaviour:
% lvconvert --merge /dev/vg0/test-snap
Merging of volume test-snap started.
test: Merged: 0,1%
Merge of snapshot into logical volume test has finished.
Logical volume test-snap successfully removed
% md5sum /dev/vg0/test
b5cfa9d6c8febd618f91ac2843d50a1c /dev/vg0/test
More Info:
% lsmod|grep snap
dm_snapshot18481 0
dm_mod 53754 55 dm_snapshot,dm_mirror,dm_log
% dpkg -l | grep linux-image
ii linux-image-2.6.32-5-amd64 2.6.32-30
ii linux-image-amd64 2.6.32+29
% uname -a
Linux han-solo 2.6.32-5-amd64 #1 SMP Wed Jan 12 03:40:32 UTC 2011 x86_64
GNU/Linux
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#612439: Acknowledgement (lvconvert --merge breaks Logical Volumes)
Severity: important The PV with it's only 10 MByte is not the problem. Problem occured on production machine with 500 gig free on VG which rendered the LV unaccessible. Recovering was possible with described commands in original bug report. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589009: Test Case
HOST % cat /etc/debian_version squeeze/sid % dpkg-query -W | egrep 'linux|kvm|vde|python|libc6|iproute|bridge|adduser|libaio' adduser 3.112 bridge-utils1.4-5 iproute 20100519-3 kvm 1:0.12.5+dfsg-1 libaio1 0.3.107-7 libc6 2.11.2-2 libc6-i386 2.11.2-2 libselinux1 2.0.96-1 libvdeplug2 2.2.3-3 linux-base 2.6.32-20 linux-image-2.6.32-5-amd64 2.6.32-20 linux-image-amd64 2.6.32+28 python 2.6.5-13 python-minimal 2.6.5-13 python-reportbug4.12.6 python-support 1.0.9 python2.6 2.6.6~rc1-1 python2.6-minimal 2.6.6~rc1-1 qemu-kvm0.12.5+dfsg-1 util-linux 2.17.2-3.1 % cat /etc/libvirt/qemu/source/s15.xml domain type='kvm' names15/name uuid92dfd544-9638-11df-b6c6-18a905632d8c/uuid memory1048576/memory vcpu cpuset='0-5'1/vcpu os type arch='x86_64' machine='pc-0.12'hvm/type boot dev='hd'/ boot dev='cdrom'/ /os features acpi/ apic/ pae/ /features clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashrestart/on_crash devices emulator/usr/bin/kvm/emulator disk type='file' device='cdrom' source file='/var/lib/libvirt/iso/grml64'/ target dev='hda' bus='ide'/ readonly/ /disk disk type='block' device='disk' source dev='/dev/vg_hansolo_dom/vm_s15'/ target dev='vda' bus='virtio'/ /disk interface type='bridge' mac address='52:54:00:1e:ef:9f'/ source bridge='kvm0'/ model type='virtio'/ /interface serial type='pty' target port='0'/ /serial console type='pty' target port='0'/ /console graphics type='vnc' port='5915' autoport='no' keymap='de'/ /devices /domain % virsh define /etc/libvirt/qemu/source/s15.xml Domain s15 defined from /etc/libvirt/qemu/source/s15.xml % virsh start s15 Domain s15 started (ssh into s15 and generate some traffic, e.g. update-pciids) % tail -f /var/log/libvirt/qemu/s15.log LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/sbin: /bin:/usr/sbin:/usr/bin HOME=/ QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-0.12 -enable-kvm -m 1024 -smp 1,sockets=1,cores=1,threads=1 -name s15 -uuid 92dfd544-9638-11df-b6c6-18a905632d8c -nodefaults -chardev socket,id=monitor,path=/var/lib/libvirt/qemu /s15.monitor,server,nowait -mon chardev=monitor,mode=readline -rtc base=utc -boot cd -drive file=/var/lib/libvirt/ iso/grml64,if=none,media=cdrom,id=drive-ide0-0-0, readonly=on,format=raw -device ide-drive,bus=ide.0, unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -drive file= /dev/vg_hansolo_dom/vm_s15,if=none,id=drive-virtio-disk0, boot=on,format=raw -device virtio-blk-pci,bus=pci.0, addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0 -device virtio-net-pci,vlan=0,id=net0, mac=52:54:00:1e:ef:9f,bus=pci.0,addr=0x3 -net tap,fd=64,vlan=0,name=hostnet0 -chardev pty,id=serial0 -device isa-serial,chardev=serial0 -usb -vnc 127.0.0.1:15 -k de -vga cirrus -device virtio-balloon-pci,id=balloon0, bus=pci.0,addr=0x5 char device redirected to /dev/pts/2 virtio-net truncating packet GUEST = Stock Lenny, no 3rd-party Packages installed. % cat /etc/debian_version 5.0.5 % dpkg-query -W | egrep 'linux|python|libc6|iproute|adduser' adduser 3.110 iproute 20080725-2 libc6 2.7-18lenny4 libselinux1 2.0.65-5 linux-image-2.6-amd64 2.6.26+17+lenny1 linux-image-2.6.26-2-amd64 2.6.26-24lenny1 python 2.5.2-3 python-minimal 2.5.2-3 python2.5 2.5.2-15+lenny1 python2.5-minimal 2.5.2-15+lenny1 util-linux 2.13.1.1-1 Running grml64 2010.04 (Grmlmonster) with 2.6.33-grml64 on the same VM with virtio network the problem can't be reproduced by me. It seems the problem lies with lenny kernel running inside the VM. Marcel. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589009: Test Case II
You aren't using vde, are you? Nope. Host has a bridge configured in /etc/network/interfaces (kvm0) where each guests eth0 is added to. I do run tagged VLANs on the bridge and so do the guests. Each guest has to setup VLANs on it's eth0. Were you able to reproduce this issue with 2.6.33 guest kernel and using qemu-kvm 0.12.4 (the previous one) ? Can't say as i didn't assume the guests kernel had anything to do with it. As soon as i discovered my VMs are crashing using virtio i changed them all to e1000. Thanks for looking into it! Marcel. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589009: Test Case II
Some results playing around with kernel and ethtool in guest. Same config as above except kernel. GUEST = Lenny Kernel with virtio % uname -a ; ethtool -k eth0 Linux test 2.6.26-2-amd64 #1 SMP Thu Aug 19 00:37:36 UTC 2010 x86_64 GNU/Linux Cannot get device rx csum settings: Operation not supported Cannot get device tx csum settings: Operation not supported Cannot get device scatter-gather settings: Operation not supported Cannot get device tcp segmentation offload settings: Operation not supported Cannot get device udp large send offload settings: Operation not supported Cannot get device generic segmentation offload settings: Operation not supported Cannot get device flags: Operation not supported Offload parameters for eth0: no offload info available Result: Machine crashes as soon as there is traffic on guests eth0. Squeeze Kernel with virtio -- % uname -a ; ethtool -k eth0 Linux test 2.6.32-5-amd64 #1 SMP Thu Aug 12 13:01:50 UTC 2010 x86_64 GNU/Linux Offload parameters for eth0: rx-checksumming: off tx-checksumming: off scatter-gather: off tcp segmentation offload: off udp fragmentation offload: off generic segmentation offload: off large receive offload: off Result: Works! No crashes after putting some load on guests eth0. Only for reference: Lenny Kernel with e1000 --- % uname -a ; ethtool -k eth0 Linux test 2.6.26-2-amd64 #1 SMP Thu Aug 19 00:37:36 UTC 2010 x86_64 GNU/Linux Cannot get device flags: Operation not supported Offload parameters for eth0: rx-checksumming: on tx-checksumming: on scatter-gather: on tcp segmentation offload: on udp fragmentation offload: off generic segmentation offload: on large receive offload: off Result: works Squeeze Kernel with e1000 - % uname -a ; ethtool -k eth0 Linux test 2.6.32-5-amd64 #1 SMP Thu Aug 12 13:01:50 UTC 2010 x86_64 GNU/Linux Offload parameters for eth0: rx-checksumming: on tx-checksumming: on scatter-gather: on tcp segmentation offload: on udp fragmentation offload: off generic segmentation offload: on large receive offload: off -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589009: Lenny Kernel Upgrade?
Thanks for figureing out the problem here :) Important question not asked by now: Will there be an upgrade to the current lenny kernel with this fix applied? Even though a workaround exists (using e1000), it would be nice to be able to use virtio even with squeeze almost at the finish line... :) Marcel. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589009: Bug still present in 0.12.5+dfsg-1
Package: qemu-kvm Version: Version: 0.12.5+dfsg-1 With latest kvm updates in squeeze the bug is still present. Guest crashes as soon as you generate some traffic on the virtio interface. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/16 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages qemu-kvm depends on: ii adduser 3.112add and remove users and groups ii bridge-utils1.4-5Utilities for configuring the Linu ii iproute 20100519-3 networking and traffic control too ii libaio1 0.3.107-7Linux kernel AIO access library - ii libasound2 1.0.23-1 shared library for ALSA applicatio ii libbluetooth3 4.66-1 Library to use the BlueZ Linux Blu ii libbrlapi0.54.2-3braille display access via BRLTTY ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib ii libcurl3-gnutls 7.21.0-1 Multi-protocol file transfer libra ii libgnutls26 2.8.6-1 the GNU TLS library - runtime libr ii libncurses5 5.7+20100313-2 shared libraries for terminal hand ii libpci3 1:3.1.7-4Linux PCI Utilities (shared librar ii libpulse0 0.9.21-3+b1 PulseAudio client libraries ii libsasl2-2 2.1.23.dfsg1-5 Cyrus SASL - authentication abstra ii libsdl1.2debian 1.2.14-6 Simple DirectMedia Layer ii libuuid12.17.2-3.1 Universally Unique ID library ii libvdeplug2 2.2.3-3 Virtual Distributed Ethernet - Plu ii libx11-62:1.3.3-3X11 client-side library ii python 2.6.5-11 interactive high-level object-orie ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages qemu-kvm recommends: ii linux-image-2.6.32-5-amd64 [l 2.6.32-18 Linux 2.6.32 for 64-bit PCs Versions of packages qemu-kvm suggests: pn debootstrap none (no description available) pn samba none (no description available) pn vde2 none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589009: KVM guests crash when network link gets saturated with virtio-net truncating packet
Package: qemu-kvm Version: Version: 0.12.4+dfsg-1 Severity: important Tags: patch When using virtio for KVM guest networking the guest will crash as soon as their network link gets saturated with incoming packets. /var/log/libvirt/qemu/vm-name.log on host contains: LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin HOME=/ QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc-0.12 -enable-kvm -m 8192 -smp 8,sockets=8,cores=1,threads=1 -name s8 -uuid 6e047bee-8f21-11df-b6b5-43c8479dea48 -nodefaults -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/s8.monitor,server,nowait -mon chardev=monitor,mode=readline -rtc base=utc -boot cd -drive file=/var/lib/libvirt/iso/grml64,if=none,media=cdrom,id=drive-ide0-0-0,readonly=on -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -drive file=/dev/hansolo_vgdom/vm_s8,if=none,id=drive-virtio-disk0,boot=on -device virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0 -device virtio-net-pci,vlan=0,id=net0,mac=52:54:00:1a:1a:56,bus=pci.0,addr=0x5 -net tap,fd=62,vlan=0,name=hostnet0 -chardev pty,id=serial0 -device isa-serial,chardev=serial0 -usb -vnc 127.0.0.1:8 -k de -vga cirrus -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3 char device redirected to /dev/pts/2 virtio-net truncating packet Ubuntu Bugreport: https://bugs.edge.launchpad.net/ubuntu/+source/qemu-kvm/+bug/458521 Patch: http://launchpadlibrarian.net/34603683/patch Reproduced this with apt-get install vim inside guest. As soon as the guest retrieves data from debian mirror in our LAN the machine crashes. Changing NIC of guest from virtio to e1000 fixed it. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#526983: Soft Lockups in KVM guest related to r8169 transmit timeouts?
Hi, contrary to my comment 38 in #526983 the issue seems not to be fixed with latest kernel. In fact, r8169 transmit timeout on host occurs the same time as soft lockup in kvm guest occurs. from this time on the kvm process runs at 100% on the host and programs such as top can't be started anymore in kvm guest; shutdown of kvm guest doesn't work eighter, only destroy works. seems to be triggered when kvm guest has some more traffic than normal. host: lenny 64bit, linux-image-2.6.26-2-amd64 2.6.26-21 with kvm-72+dfsg-5~lenny4 kvm guest: lenny 32bit, linux-image-2.6.26-2-6862.6.26-21 kvm guest started via /usr/bin/kvm -S -M pc -m 2048 -smp 1 -name foobar -monitor pty -boot cd -drive file=/dev/vgdom/foobar,if=virtio,index=0,boot=on -drive file=/var/lib/libvirt/iso/grml-medium_2009.10.iso,if=virtio,media=cdrom,index=2 -net nic,macaddr=54:52:00:00:74:01,vlan=0,model=virtio -net tap,fd=22,script=,vlan=0,ifname=vnet4 -serial pty -parallel none -usb -vnc 127.0.0.1:74 -k de Any ideas? host systems /var/log/messages Jan 31 23:42:00 wtf kernel: [977284.375745] NETDEV WATCHDOG: eth0: transmit timed out Jan 31 23:42:00 wtf kernel: [977284.375745] [ cut here ] Jan 31 23:42:00 wtf kernel: [977284.375745] WARNING: at net/sched/sch_generic.c:222 dev_watchdog+0xa6/0xfb() Jan 31 23:42:00 wtf kernel: [977284.375745] Modules linked in: iptable_nat nf_nat xt_multiport xt_limit xt_tcpudp nf_conntrack_ipv4 xt_state nf_conntrack ipt_REJECT iptable_filter ip_tables x_tables tun sha256_generic aes_x86_64 aes_generic cbc dm_crypt crypto_blkcipher kvm_intel kvm bridge ext2 f71882fg ext3 jbd mbcache dm_mirror dm_log dm_snapshot dm_mod raid1 md_mod sd_mod ahci libata scsi_mod dock r8169 processor thermal_sys [last unloaded: scsi_wait_scan] Jan 31 23:42:00 wtf kernel: [977284.375745] Pid: 0, comm: swapper Not tainted 2.6.26-2-amd64 #1 Jan 31 23:42:00 wtf kernel: [977284.375745] Jan 31 23:42:00 wtf kernel: [977284.375745] Call Trace: Jan 31 23:42:00 wtf kernel: [977284.375745] IRQ [80234a0c] warn_on_slowpath+0x51/0x7a Jan 31 23:42:00 wtf kernel: [977284.375745] [803cc8f6] dev_watchdog+0x0/0xfb Jan 31 23:42:00 wtf kernel: [977284.375745] [802354a7] printk+0x4e/0x56 Jan 31 23:42:00 wtf kernel: [977284.375745] [8023cfbd] lock_timer_base+0x26/0x4b Jan 31 23:42:00 wtf kernel: [977284.375745] [8023d14c] __mod_timer+0xbd/0xcc Jan 31 23:42:00 wtf kernel: [977284.375745] [802438ef] queue_delayed_work_on+0xb8/0xc8 Jan 31 23:42:00 wtf kernel: [977284.375745] [803cc8f6] dev_watchdog+0x0/0xfb Jan 31 23:42:00 wtf kernel: [977284.375745] [803cc99c] dev_watchdog+0xa6/0xfb Jan 31 23:42:00 wtf kernel: [977284.375745] [803cc8f6] dev_watchdog+0x0/0xfb Jan 31 23:42:00 wtf kernel: [977284.375745] [8023ca7d] run_timer_softirq+0x16a/0x1e2 Jan 31 23:42:00 wtf kernel: [977284.375745] [80239449] __do_softirq+0x5c/0xd1 Jan 31 23:42:00 wtf kernel: [977284.375745] [8020d2cc] call_softirq+0x1c/0x28 Jan 31 23:42:00 wtf kernel: [977284.375745] [8020f3d8] do_softirq+0x3c/0x81 Jan 31 23:42:00 wtf kernel: [977284.375745] [802393a7] irq_exit+0x3f/0x85 Jan 31 23:42:00 wtf kernel: [977284.375745] [8021aa6b] smp_apic_timer_interrupt+0x8c/0xa4 Jan 31 23:42:00 wtf kernel: [977284.375745] [8020ccf2] apic_timer_interrupt+0x72/0x80 Jan 31 23:42:00 wtf kernel: [977284.375745] EOI [8021a817] lapic_next_event+0x0/0x13 Jan 31 23:42:00 wtf kernel: [977284.375745] [8021a826] lapic_next_event+0xf/0x13 Jan 31 23:42:00 wtf kernel: [977284.375745] [8042a54d] _spin_unlock_irqrestore+0x7/0xe Jan 31 23:42:00 wtf kernel: [977284.375745] [8024d814] tick_notify+0x1e9/0x33b Jan 31 23:42:00 wtf kernel: [977284.375745] [802498fc] notifier_call_chain+0x29/0x4c Jan 31 23:42:00 wtf kernel: [977284.375745] [8024d2ce] clockevents_notify+0x24/0x6d Jan 31 23:42:00 wtf kernel: [977284.375745] [a000828f] :processor:acpi_idle_enter_bm+0x2d5/0x327 Jan 31 23:42:00 wtf kernel: [977284.375745] [803aa804] cpuidle_idle_call+0x7a/0xb2 Jan 31 23:42:00 wtf kernel: [977284.375745] [803aa78a] cpuidle_idle_call+0x0/0xb2 Jan 31 23:42:00 wtf kernel: [977284.375745] [8020ac7e] cpu_idle+0x8e/0xb8 Jan 31 23:42:00 wtf kernel: [977284.375745] Jan 31 23:42:00 wtf kernel: [977284.375745] ---[ end trace c2e0b14640bc17c0 ]--- Jan 31 23:42:00 wtf kernel: [977284.417786] r8169: eth0: link up kvm guest dmesg (nothing in logs): [1267143826.640016] BUG: soft lockup - CPU#0 stuck for 1179869831s! [pure-ftpd:4742] [1267143826.640016] Modules linked in: xfs ext2 virtio_net button ext3 jbd mbcache dm_mirror dm_log dm_snapshot dm_mod virtio_blk ide_cd_mod cdrom ata_generic libata scsi_mod dock ide_pci_generic virtio_pci piix ide_core [last unloaded:
Bug#496917: Soft Lockups
Hi Ben, do you recommend using linux-image-2.6.26-2-amd64-2.6.26-21 for the host OS or for the guest? I'm asking because with host: linux-image-2.6.26-2-amd64 version 2.6.26-21 kvm version 72+dfsg-5~lenny4 guest: linux-image-2.6.26-2-686 version 2.6.26-19lenny2 the soft lockups still occur: Jan 17 19:53:05 cookie kernel: [345213.390483] BUG: soft lockup - CPU#1 stuck for 73s! [sshd:7411] Jan 17 19:53:05 cookie kernel: [345213.390483] Modules linked in: xfs ext2 button ext3 jbd mbcache dm_mirror dm_log dm_snapshot dm_mod sd_mod ide_cd_mod cdrom ata_generic libata dock ide_pci_generic sym53c8xx scsi_transport_spi scsi_mod e1 000 piix ide_core [last unloaded: scsi_wait_scan] Jan 17 19:53:05 cookie kernel: [345213.390483] Jan 17 19:53:05 cookie kernel: [345213.390483] Pid: 7411, comm: sshd Not tainted (2.6.26-2-686 #1) Jan 17 19:53:05 cookie kernel: [345213.390483] EIP: 0060:[c027cf81] EFLAGS: 0282 CPU: 1 Jan 17 19:53:05 cookie kernel: [345213.390483] EIP is at tcp_sendmsg+0x783/0x8e3 Jan 17 19:53:05 cookie kernel: [345213.390483] EAX: f7ce5540 EBX: f7e06c80 ECX: 0778 EDX: f7e06c80 Jan 17 19:53:05 cookie kernel: [345213.390483] ESI: f79b8180 EDI: 0001 EBP: c16d00c0 ESP: f7dede1c Jan 17 19:53:05 cookie kernel: [345213.390483] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 Jan 17 19:53:05 cookie kernel: [345213.390483] CR0: 8005003b CR2: bff09ce0 CR3: 37a17000 CR4: 06d0 Jan 17 19:53:05 cookie kernel: [345213.390483] DR0: DR1: DR2: DR3: Jan 17 19:53:05 cookie kernel: [345213.390483] DR6: 0ff0 DR7: 0400 Jan 17 19:53:05 cookie kernel: [345213.390483] [c024efdf] ? sock_aio_write+0xdd/0xea Jan 17 19:53:05 cookie kernel: [345213.390483] [c01742ea] ? do_sync_write+0xbf/0x100 Jan 17 19:53:05 cookie kernel: [345213.390483] [c013199c] ? autoremove_wake_function+0x0/0x2d Jan 17 19:53:05 cookie kernel: [345213.390483] [c01baa3f] ? security_file_permission+0xc/0xd Jan 17 19:53:05 cookie kernel: [345213.390483] [c0174a6d] ? vfs_write+0x94/0x120 Jan 17 19:53:05 cookie kernel: [345213.390483] [c017502e] ? sys_write+0x3c/0x63 Jan 17 19:53:05 cookie kernel: [345213.390483] [c01038ce] ? syscall_call+0x7/0xb Jan 17 19:53:05 cookie kernel: [345213.390483] === Jan 17 19:55:46 cookie kernel: [345374.926484] BUG: soft lockup - CPU#1 stuck for 90s! [sshd:7411] Jan 17 19:55:46 cookie kernel: [345374.926484] Modules linked in: xfs ext2 button ext3 jbd mbcache dm_mirror dm_log dm_snapshot dm_mod sd_mod ide_cd_mod cdrom ata_generic libata dock ide_pci_generic sym53c8xx scsi_transport_spi scsi_mod e1 000 piix ide_core [last unloaded: scsi_wait_scan] Jan 17 19:55:46 cookie kernel: [345374.926484] Jan 17 19:55:46 cookie kernel: [345374.926484] Pid: 7411, comm: sshd Not tainted (2.6.26-2-686 #1) Jan 17 19:55:46 cookie kernel: [345374.926484] EIP: 0060:[c02b9bb3] EFLAGS: 0246 CPU: 1 Jan 17 19:55:46 cookie kernel: [345374.926484] EIP is at _spin_unlock_irqrestore+0x7/0x10 Jan 17 19:55:46 cookie kernel: [345374.926484] EAX: 0246 EBX: f7b32430 ECX: 00fd EDX: 0246 Jan 17 19:55:46 cookie kernel: [345374.926484] ESI: f78003e0 EDI: 2210 EBP: 0200 ESP: f7dedc44 Jan 17 19:55:46 cookie kernel: [345374.926484] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 Jan 17 19:55:46 cookie kernel: [345374.926484] CR0: 8005003b CR2: 0804d013 CR3: 37a17000 CR4: 06d0 Jan 17 19:55:46 cookie kernel: [345374.926484] DR0: DR1: DR2: DR3: Jan 17 19:55:46 cookie kernel: [345374.926484] DR6: 0ff0 DR7: 0400 Jan 17 19:55:46 cookie kernel: [345374.926484] [f8864e57] ? e1000_xmit_frame+0xa59/0xaa3 [e1000] Jan 17 19:55:46 cookie kernel: [345374.926484] [c011b6fc] ? default_wake_function+0x0/0x8 Jan 17 19:55:46 cookie kernel: [345374.926484] [c0258f16] ? dev_hard_start_xmit+0x1eb/0x24f Jan 17 19:55:46 cookie kernel: [345374.926484] [c0266fb6] ? __qdisc_run+0xa8/0x17c Jan 17 19:55:46 cookie kernel: [345374.926484] [c025b091] ? dev_queue_xmit+0x19f/0x2be Jan 17 19:55:46 cookie kernel: [345374.926484] [c02768e7] ? ip_finish_output+0x1c5/0x1fc Jan 17 19:55:46 cookie kernel: [345374.926484] [c027646e] ? ip_local_out+0x15/0x17 Jan 17 19:55:46 cookie kernel: [345374.926484] [c0276e9b] ? ip_queue_xmit+0x25f/0x2a1 Jan 17 19:55:46 cookie kernel: [345374.926484] [c02853e8] ? tcp_transmit_skb+0x6a2/0x6d5 Jan 17 19:55:46 cookie kernel: [345374.926484] [c0284948] ? tcp_current_mss+0xaa/0xc8 Jan 17 19:55:46 cookie kernel: [345374.926484] [c02869b7] ? __tcp_push_pending_frames+0x60b/0x6b2 Jan 17 19:55:46 cookie kernel: [345374.926484] [c027b927] ? sk_stream_alloc_skb+0x24/0xad Jan 17 19:55:46 cookie kernel: [345374.926484] [c027cff3] ? tcp_sendmsg+0x7f5/0x8e3 Jan 17 19:55:46 cookie kernel: [345374.926484] [c024efdf] ? sock_aio_write+0xdd/0xea Jan 17 19:55:46 cookie kernel: [345374.926484] [c0133e56] ? enqueue_hrtimer+0xc9/0xd4 Jan 17 19:55:46 cookie kernel:
Bug#526983: r8169
Marcel Meckel deb...@thermoman.de using unknown hardware reported as fixed in 2.6.26-21 06:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 02) as reported in comment 38. Marcel. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#526983: r8169
linux-image-2.6.26-2-amd64-2.6.26-21 fixes this r8169 issue for me. No more problems. Thanks! Marcel. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#526983: r8169
Package: linux-image-2.6.26-2-amd64 Version: 2.6.26-20 Severity: important Just installed 2.6.26-20 (there was no -21) from lenny-proposed-updates and there is the same error: % dmesg [20575.258740] CE: hpet increasing min_delta_ns to 15000 nsec [22731.176203] NETDEV WATCHDOG: eth0: transmit timed out [22731.176203] [ cut here ] [22731.176203] WARNING: at net/sched/sch_generic.c:222 dev_watchdog+0xa6/0xfb() [22731.176203] Modules linked in: sha256_generic aes_x86_64 aes_generic cbc dm_crypt crypto_blkcipher iptable_nat nf_nat xt_multiport xt_limit xt_tcpudp nf_conntrack_ipv4 xt_state nf_conntrack ipt_REJECT iptable_filter ip_tables x_tables tun kvm_intel kvm bridge ext2 f71882fg ext3 jbd mbcache dm_mirror dm_log dm_snapshot dm_mod raid1 md_mod sd_mod ahci libata scsi_mod dock r8169 processor thermal_sys [last unloaded: scsi_wait_scan] [22731.176203] Pid: 0, comm: swapper Not tainted 2.6.26-2-amd64 #1 [22731.176203] [22731.176203] Call Trace: [22731.176203] IRQ [80234a0c] warn_on_slowpath+0x51/0x7a [22731.176203] [803cc7f6] dev_watchdog+0x0/0xfb [22731.176203] [802354a7] printk+0x4e/0x56 [22731.176203] [8023cfb9] lock_timer_base+0x26/0x4b [22731.176203] [8023d148] __mod_timer+0xbd/0xcc [22731.176203] [802438eb] queue_delayed_work_on+0xb8/0xc8 [22731.176203] [803cc7f6] dev_watchdog+0x0/0xfb [22731.176203] [803cc89c] dev_watchdog+0xa6/0xfb [22731.176203] [803cc7f6] dev_watchdog+0x0/0xfb [22731.176203] [8023ca79] run_timer_softirq+0x16a/0x1e2 [22731.176203] [80239447] __do_softirq+0x5c/0xd1 [22731.176203] [8020d2cc] call_softirq+0x1c/0x28 [22731.176203] [8020f3d8] do_softirq+0x3c/0x81 [22731.176203] [802393a7] irq_exit+0x3f/0x83 [22731.176203] [8021aa6b] smp_apic_timer_interrupt+0x8c/0xa4 [22731.176203] [8020ccf2] apic_timer_interrupt+0x72/0x80 [22731.176203] EOI [a000826d] :processor:acpi_idle_enter_bm+0x2b3/0x327 [22731.176203] [8026] rcu_needs_cpu+0x32/0x41 [22731.176203] [803aa704] cpuidle_idle_call+0x7a/0xb2 [22731.176203] [803aa68a] cpuidle_idle_call+0x0/0xb2 [22731.176203] [8020ac79] cpu_idle+0x89/0xb3 [22731.176203] [22731.176203] ---[ end trace 23d925b5bc3e605e ]--- [22731.190601] r8169: eth0: link up % lsmod Module Size Used by sha256_generic 13696 0 aes_x86_64 12416 2 aes_generic32552 1 aes_x86_64 cbc 7936 1 dm_crypt 17032 1 crypto_blkcipher 21636 3 cbc,dm_crypt iptable_nat 9872 1 nf_nat 23192 1 iptable_nat xt_multiport7424 2 xt_limit7172 1 xt_tcpudp 7680 1 nf_conntrack_ipv4 19352 8 iptable_nat,nf_nat xt_state6656 5 nf_conntrack 71440 4 iptable_nat,nf_nat,nf_conntrack_ipv4,xt_state ipt_REJECT 7552 2 iptable_filter 7424 1 ip_tables 21520 2 iptable_nat,iptable_filter x_tables 25224 7 iptable_nat,xt_multiport,xt_limit,xt_tcpudp,xt_state,ipt_REJECT,ip_tables tun14084 5 kvm_intel 39776 5 kvm 127592 1 kvm_intel bridge 53544 0 ext2 66576 1 f71882fg 15244 0 ext3 125072 2 jbd51240 1 ext3 mbcache12804 2 ext2,ext3 dm_mirror 20608 0 dm_log 13956 1 dm_mirror dm_snapshot19400 0 dm_mod 58864 22 dm_crypt,dm_mirror,dm_log,dm_snapshot raid1 24192 3 md_mod 80292 4 raid1 sd_mod 29376 8 ahci 33036 6 libata165600 1 ahci scsi_mod 161016 2 sd_mod,libata dock 14112 1 libata r8169 31364 0 processor 42304 8 thermal_sys17728 1 processor % cat /proc/version Linux version 2.6.26-2-amd64 (Debian 2.6.26-20) (da...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Mon Oct 26 10:39:40 UTC 2009 Marcel. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#526983: r8169
Ok now there is 2.6.26-21 ... just booted this kernel and will report back with details. Marcel. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#526983: r8169
Package: linux-image-2.6.26-2-amd64 Version: 2.6.26-19lenny2 Severity: important I can confirm this problem with latest debian lenny packages. Error when network load is high: Jan 12 14:16:17 wtf kernel: [1967737.278889] NETDEV WATCHDOG: eth0: transmit timed out Jan 12 14:16:17 wtf kernel: [1967737.278929] [ cut here ] Jan 12 14:16:17 wtf kernel: [1967737.278958] WARNING: at net/sched/sch_generic.c:222 dev_watchdog+0xa6/0xfb() Jan 12 14:16:17 wtf kernel: [1967737.279018] Modules linked in: kvm_intel kvm tun sha256_generic aes_x86_64 aes_generic cbc dm_crypt crypto_blkcipher iptable_nat nf_nat xt_multiport xt_limit xt_tcpudp nf_conntrack_ipv4 xt_state nf_conntrack ipt_REJECT iptable_filter ip_tables x_tables bridge ext2 f71882fg ext3 jbd mbcache dm_mirror dm_log dm_snapshot dm_mod raid1 md_mod sd_mod ahci r8169 libata scsi_mod dock processor thermal_sys [last unloaded: kvm] Jan 12 14:16:17 wtf kernel: [1967737.279304] Pid: 0, comm: swapper Not tainted 2.6.26-2-amd64 #1 Jan 12 14:16:17 wtf kernel: [1967737.279333] Jan 12 14:16:17 wtf kernel: [1967737.279333] Call Trace: Jan 12 14:16:17 wtf kernel: [1967737.279375] IRQ [80234a0c] warn_on_slowpath+0x51/0x7a Jan 12 14:16:17 wtf kernel: [1967737.279412] [803cc816] dev_watchdog+0x0/0xfb Jan 12 14:16:17 wtf kernel: [1967737.279441] [80235461] printk+0x4e/0x56 Jan 12 14:16:17 wtf kernel: [1967737.279470] [8023cf75] lock_timer_base+0x26/0x4b Jan 12 14:16:17 wtf kernel: [1967737.279500] [8023d104] __mod_timer+0xbd/0xcc Jan 12 14:16:17 wtf kernel: [1967737.279530] [802438a3] queue_delayed_work_on+0xb8/0xc8 Jan 12 14:16:17 wtf kernel: [1967737.279561] [803cc816] dev_watchdog+0x0/0xfb Jan 12 14:16:17 wtf kernel: [1967737.279589] [803cc8bc] dev_watchdog+0xa6/0xfb Jan 12 14:16:17 wtf kernel: [1967737.279617] [803cc816] dev_watchdog+0x0/0xfb Jan 12 14:16:17 wtf kernel: [1967737.279646] [8023ca35] run_timer_softirq+0x16a/0x1e2 Jan 12 14:16:17 wtf kernel: [1967737.279677] [80239403] __do_softirq+0x5c/0xd1 Jan 12 14:16:17 wtf kernel: [1967737.279707] [8020d2cc] call_softirq+0x1c/0x28 Jan 12 14:16:17 wtf kernel: [1967737.279736] [8020f3d8] do_softirq+0x3c/0x81 Jan 12 14:16:17 wtf kernel: [1967737.279764] [80239363] irq_exit+0x3f/0x83 Jan 12 14:16:17 wtf kernel: [1967737.279792] [8021aa7b] smp_apic_timer_interrupt+0x8c/0xa4 Jan 12 14:16:17 wtf kernel: [1967737.279823] [8020ccf2] apic_timer_interrupt+0x72/0x80 Jan 12 14:16:17 wtf kernel: [1967737.279852] EOI [a000826d] :processor:acpi_idle_enter_bm+0x2b3/0x327 Jan 12 14:16:17 wtf kernel: [1967737.279909] [803aa728] cpuidle_idle_call+0x7a/0xb2 Jan 12 14:16:17 wtf kernel: [1967737.279938] [803aa6ae] cpuidle_idle_call+0x0/0xb2 Jan 12 14:16:17 wtf kernel: [1967737.279967] [8020ac79] cpu_idle+0x89/0xb3 Jan 12 14:16:17 wtf kernel: [1967737.279996] Jan 12 14:16:17 wtf kernel: [1967737.280016] ---[ end trace db0b2e9f487d3b4d ]--- Jan 12 14:16:17 wtf kernel: [1967737.299403] r8169: eth0: link up Seems like the interface went down and came up right away - i didn't even noticed this problem until i checked dmesg. Maybe the counter is wrong or there are really this many packets dropped: % ifconfig eth0 Link encap:Ethernet HWaddr 00:24:21:XX:XX:XX inet addr:XXX.XXX.XXX.XXX Bcast:XXX.XXX.XXX.255 Mask:255.255.255.255 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:96607465 errors:0 dropped:34911509435217 overruns:0 frame:0 TX packets:116667448 errors:0 dropped:46 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:86936665600 (80.9 GiB) TX bytes:112516773583 (104.7 GiB) Interrupt:250 Base address:0x6000 Hardware: % lspci -nn 00:00.0 Host bridge [0600]: Intel Corporation X58 I/O Hub to ESI Port [8086:3405] (rev 13) 00:01.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 [8086:3408] (rev 13) 00:03.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 [8086:340a] (rev 13) 00:07.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 7 [8086:340e] (rev 13) 00:14.0 PIC [0800]: Intel Corporation 5520/5500/X58 I/O Hub System Management Registers [8086:342e] (rev 13) 00:14.1 PIC [0800]: Intel Corporation 5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers [8086:3422] (rev 13) 00:14.2 PIC [0800]: Intel Corporation 5520/5500/X58 I/O Hub Control Status and RAS Registers [8086:3423] (rev 13) 00:14.3 PIC [0800]: Intel Corporation 5520/5500/X58 I/O Hub Throttle Registers [8086:3438] (rev 13) 00:1a.0 USB Controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #4 [8086:3a37] 00:1a.1 USB Controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #5 [8086:3a38] 00:1a.2
Bug#527039: perl: Regex fails when string is too long
Package: perl
Version: 5.10.0-19
Severity: important
In 5.10 and newer a regex begins to fail if a matching string
is longer than 32767 chars.
Upstream bug: http://rt.perl.org/rt3/Public/Bug/Display.html?id=65372
Script to reproduce:
---
use strict;
use warnings;
parse(x x 32767);
parse(x x 32768);
sub parse {
my $xml = shift;
$xml = html${xml}/html;
my $tag = html;
if ( $xml =~ m{$tag(.|\n)*?/$tag}i ) {
print matched\n;
}
else {
print didn't match\n;
}
}
---
-- System Information:
Debian Release: 5.0.1
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-1-686-bigmem (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages perl depends on:
ii libc6 2.7-18 GNU C Library: Shared libraries
ii libdb4.6 4.6.21-11 Berkeley v4.6 Database Libraries [
ii libgdbm3 1.8.3-3GNU dbm database routines (runtime
ii perl-base 5.10.0-19 minimal Perl system
ii perl-modules 5.10.0-19 Core Perl modules
Versions of packages perl recommends:
ii netbase 4.34 Basic TCP/IP networking system
Versions of packages perl suggests:
pn libterm-readline-gnu-perl | l none (no description available)
pn perl-doc none (no description available)
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523026: dovecot-common: dovecot init script sends SIGUSR1 on reload instead of SIGHUP
Subject: dovecot-common: dovecot init script sends SIGUSR1 on reload instead of SIGHUP Package: dovecot-common Version: 1:1.0.15-2.3 Severity: minor Tags: patch -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686-bigmem (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages dovecot-common depends on: ii adduser 3.110 add and remove users and groups ii libc6 2.7-18 GNU C Library: Shared libraries ii libcomerr21.41.3-1 common error description library ii libkrb53 1.6.dfsg.4~beta1-5 MIT Kerberos runtime libraries ii libldap-2.4-2 2.4.11-1 OpenLDAP libraries ii libmysqlclient15off 5.0.51a-24 MySQL database client library ii libpam-runtime1.0.1-5Runtime support for the PAM librar ii libpam0g 1.0.1-5Pluggable Authentication Modules l ii libpq58.3.6-1PostgreSQL C client library ii libsqlite3-0 3.5.9-6SQLite 3 shared library ii libssl0.9.8 0.9.8g-15 SSL shared libraries ii openssl 0.9.8g-15 Secure Socket Layer (SSL) binary a ii ucf 3.0016 Update Configuration File: preserv ii zlib1g1:1.2.3.3.dfsg-12 compression library - runtime dovecot-common recommends no packages. dovecot-common suggests no packages. -- no debconf information patch: --- /etc/init.d/dovecot.orig2009-04-08 00:47:19.0 +0200 +++ /etc/init.d/dovecot 2009-04-08 00:35:14.0 +0200 @@ -121,7 +121,7 @@ # restarting (for example, when it is sent a SIGHUP), # then implement that here. # -start-stop-daemon --stop --signal USR1 --quiet --pidfile $PIDFILE --name $NAME +start-stop-daemon --stop --signal HUP --quiet --pidfile $PIDFILE --name $NAME return 0 } -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
