I can reproduce this on my system as well:
# uname -a
Linux myhost 2.6.32-5-amd64 #1 SMP Mon Mar 7 21:35:22 UTC 2011 x86_64
GNU/Linux
# apt-cache policy lvm2
lvm2:
Installed: 2.02.84-3
Candidate: 2.02.84-3
Version table:
*** 2.02.84-3 0
500 http://ftp.au.debian.org/debian/
Incidentally, this appears to be related to
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549691 which has a
workaround.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On 08/12/09 21:11, Dominic Hargreaves wrote:
On Tue, Dec 08, 2009 at 08:08:52PM +1000, Paul Gear wrote:
Upgrading my system to 3.6.1-4+etch1 (as announced in DSA-1944-1) causes
Request Tracker to report 'not logged in' every time a link is clicked
or a form is submitted. This occurs no matter
This bug continues to affect linux-image-2.6.26-2-xen-686 version
2.6.26-21lenny4 for me.
My dom0 is Ubuntu hardy running linux-image-2.6.24-27-xen version
2.6.24-27.67.
Here are two examples of the crash from within the domU - they both
occurred simply when running aptitude install
Package: postgresql-common
Version: 94lenny1
Followup-For: Bug #539585
Most of my postgresql-7.4 databases (all execpt for the two template
databases) used UNICODE encoding, yet when i upgraded to postgresql-8.3,
they were all converted back to SQL_ASCII, breaking my web apps
(drupal). The only
Package: request-tracker3.6
Version: 3.6.1-4+etch1
Severity: normal
Upgrading my system to 3.6.1-4+etch1 (as announced in DSA-1944-1) causes
Request Tracker to report 'not logged in' every time a link is clicked
or a form is submitted. This occurs no matter which user i login as. I
found some
Moritz Muehlenhoff wrote:
On Tue, Jan 22, 2008 at 11:07:58PM +0100, maximilian attems wrote:
On Wed, Jan 23, 2008 at 07:51:43AM +1000, Paul Gear wrote:
I assume by kerneloops you mean the ksymoops package? Is there anything
special i need to do to enable serial output?
no i mean
, and there is no later version available, therefore i believe
this is a bug in etch.
Sincerely,
Paul Gear
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
maximilian attems wrote:
...
My report is bizarre to you because i am only typing out what is on the
screen manually. I have no experience in kernel debugging. I read
these pages:
i see, well yes without serial or netconsole the ouptut cannot be
really processed.
2.6.24rc6 has fared no better on my machine:
DR0: DR1: DR2:
DR3: DR6: 0ff0 DR7: 0400
Process modprobe (pid: 2064, threadinfo 8102585c000, task
81012779c040)
Stack: 810127678a40 81012be8930
Here are some summaries of panics on recent kernels with without irqpoll.
2.6.24rc6 with irqpoll
--
Call Trace: mmput do_exit oops_end kernel_math_error error_exit
get_page_from_freelist sock_sendmsg find_lock_page __alloc_pages
do_wp_cache handle_mm_fault sk_free
Bastian Blank wrote:
On Tue, Jan 15, 2008 at 10:10:15AM +1000, Paul Gear wrote:
RIP free_pages_bulk
[...]
RIP: kmem_cache_free
[...]
RIP: refresh_cpu_vm_stats
general protection fault: [2] SMP
CPU 1
This looks like broken memory or other component.
That might be a good call
The results seem to be a little inconsistent in their display. Here's
another panic (on linux-image-2.6.22-3-amd64 version 2.6.22-6~bpo40+1)
and the boot process prior to it:
Starting the hotplug events dispatcher: udevd.
Synthesizing the initial hotplug events...done.
Waiting for /dev to be
maximilian attems wrote:
On Fri, 21 Dec 2007, Paul Gear wrote:
Hi kernel team,
Just wondering if you have any thoughts on this bug yet. It is a high
priority bug (as it prevents the system from booting), but i forgot to
classify it as such.
can you install 2.6.23 from unstable, install
Package: linux-image-2.6.18-5-amd64
Version: 2.6.18.dfsg.1-13etch5
(This bug *might* be a duplicate of #446744)
Ever since etch was upgraded to linux-image-2.6.18-5, my system has been
unable to boot. It kernel panics on boot, but not during the mount of
the root file system. I'm unable to
Here is a partial record of the crash on 2.6.18-5-amd64 with
all-generic-ide and irqpoll removed from the command line:
Stack has:
vgacon_cursor
__down_read
__down_read
blocking_notifier_call_chain
do_exit
do_unblank_screen
kernel_math_error
do_invalid_op
__pagevec_lru_add_active
vsnprintf
Here is a partial record of the panic on 2.6.18-5-vserver-amd64 with the
all-generic-ide and irqpoll command line parameters removed:
Partial stack (what i can see of it):
unmap_region
do_munmap
__down_write_nested
sys_munmap
system_call
Code: 7e f9 e9 d3 fe ff ff f3 90 83 3b
console shuts ip
Here is a partial panic transcript from linux-image-2.6.22-3-amd64
(2.6.22-6~bpo40+1) from backports:
Stack:
free_hot_cold_page
__pagevec_free
release_pages
free_pages_and_swap_cache
exit_mmap
mmput
do_exit
sys_exit_group
system_call
Code: 48 89 46 08 48 89 75 28 48 89 78 08 48 89 41 50 4a ff 84
Here are the kernels on my system which do not boot:
linux-image-2.6.18-5-amd64 2.6.18.dfsg.1-13etch5
linux-image-2.6.18-5-vserver-amd64 2.6.18.dfsg.1-13etch5
linux-image-2.6.22-3-amd64 2.6.22-6~bpo40+1
linux-image-2.6.22-3-vserver-amd64 2.6.22-6~bpo40+1
Here are the kernels which do boot:
Zealot wrote:
Package: shorewall
Version: 3.2.6-2
Shorewall do not process mss=value in interface properly. It not only
decrease mss, but also increase the mss
...
May be this patch is helpful, it prevent shorewall from increasing the mss.
...
I forwarded this message to the Shorewall
Debian Bug Tracking System wrote:
...
Marek wrote:
...
in 'policy':
lan dsl DROP info3/minute
in 'rules':
ACCEPT lan:10.0.1.25dsl all
ACCEPT lan:10.0.1.26dsl all
after startup, logging/dropping rules from iptables -L -n in chain
Aurélien Le Provost - Ribaltchenko wrote:
Package: shorewall
Version: 3.2.6-2
Severity: minor
Hi,
In /etc/shorewall/shorewall.conf I have
VERBOSITY=0
because I don't want my console spamed by shorewall. But it has no effect...
Don't know why.
This is a case of Shorewall FAQ 16:
I have tested amarok with a newly-created ~/.kde/share/config/amarokrc
and did not configure last.fm track submission. It has been operating
reliably for me ever since. I expect that this means that something is
misconfigured on my system (e.g. proxy settings), but it still shouldn't
cause the
I seem to have a very similar problem to that originally described.
My software versions:
ii amarok 1.4.4-4
versatile and easy to use audio player for KDE
ii amarok-engines 1.4.4-4
output engines for the
Package: installation-reports
Boot method: netinst CD
Image version:
http://cdimage.debian.org/cdimage/daily-builds/etch_d-i/current/amd64/iso-cd/debian-testing-amd64-netinst.iso
Date: 2007-02-07 19:00-ish UTC +1000
Machine: ASUS P4MVDC-MX
Processor: Celeron D 331 (EM64T, 2.66 GHz)
Memory: 1024
Package: installation-reports
Boot method: netinst CD
Image version:
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso
Date: Fri Dec 15 21:47:35 EST 2006 (AEST, GMT+10)
Machine: Intel G965 BLKDG965WHMKR
Processor: Intel Core 2 Duo
Lorenzo Martignoni wrote:
* Greg Norris [EMAIL PROTECTED]:
At the very least, README.Debian should be updated to reflect this
change in behaviour. Currently the file says:
1. AUTOMATIC STARTUP
In order to avoid the startup of the firewall on an unconfigured
Jari Aalto wrote:
Package: shorewall
Version: 3.0.4-1
Severity: wishlist
Please add new rule similar to:
DNS/ACCPEPT
but for whois queries:
WHOIS/ACCEPT
The port in question is tcp 43
I've added this upstream. File is in CVS HEAD now.
--
Paul
http://paulgear.webhop.net
--
Johannes Graumann wrote:
Package: shorewall
Version: 3.0.4-1
Severity: normal
The recent update to 3.0.4-1 presents the problem of installing a new
/etc/shorewall/shorewall.conf file without making the admin aware of
customization
being lost as is usually done (debconf issue - I
Thijs Kinkhorst wrote:
/etc/init.d/shorewall stop will keep applied some of the shorewall settings
I experienced a problem that I think reduces to the same issue: I executed
/etc/init.d/shorewall stop, thinking that it would disable the shorewall
rules and hence enable all traffic. However,
Jeroen van Wolffelaar wrote:
Package: shorewall
Version: 2.2.3-2
...
The default shorewall config says:
| # Setting DISABLE_IPV6=Yes will cause Shorewall to disable IPV6 traffic
| # to/from and through your firewall system. This requires that you have
| # ip6tables installed.
|
Package: sysstat
Version: 5.0.6-5
Sysstat enforces a 7-day limit on the time for which performance data is
kept. On production systems a longer period is desirable. The attached
patches (to /etc/default/sysstat and /usr/lib/sysstat/sa2, respectively)
implement this functionality.
--
Paul
I was able to reproduce this bug on amavisd-new 20030616p10-5. It
occurred when i commented out the name of the pid file in
/etc/amavis/amavisd.conf and tried to restart amavisd. Because
/etc/init.d/amavis assumes that the pid file is the same as what is set
in /etc/amavis/amavisd.conf by
33 matches
Mail list logo
