Bug#608185: Bug #608185: btrfs-tools: balance tree action should be only triggered by root

2010-12-28 Thread Aron Xu 
I think a workaround (geteuid test) is needed to be settled in
btrfs-tools, but not just wait for a kernel change.


-- 
Regards,
Aron Xu



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktinlla_nf7n45qm0kohj==d4ax0way9w+j09j...@mail.gmail.com

Bug#608240: linux-image-2.6.26-2-r5k-cobalt: USB subsystem crashes causing EXT3 buffer I/O error and data loss on MIPS system

2010-12-28 Thread Arthur Tyde 
Package: linux-image-2.6.26-2-r5k-cobalt
Version: 2.6.26-26lenny1
Severity: critical

Using a PCI USB adapter in Cobalt Qube - access to simple external
hard disks is unreliable.  Even when in an idle
state the subsystem (after some variable period of time) crashes
causing data loss and inability to access the drive.  Have tried
multiple USB PCI cards with the same results.

[lspci]
00:00.0 Host bridge: Marvell Technology Group Ltd. Device 4146 (rev 11)
00:07.0 Ethernet controller: Digital Equipment Corporation DECchip
21142/43 (rev 41)
00:09.0 ISA bridge: VIA Technologies, Inc. VT82C586/A/B PCI-to-ISA
[Apollo VP] (rev 27)
00:09.1 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:09.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1
Controller (rev 02)
00:0a.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1
Controller (rev 62)
00:0a.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1
Controller (rev 62)
00:0a.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 65)
00:0a.3 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306 Fire II
IEEE 1394 OHCI Link Layer Controller (rev 80)
00:0c.0 Ethernet controller: Digital Equipment Corporation DECchip
21142/43 (rev 41)

[lsusb]
Bus 003 Device 003: ID 04fc:0c25 Sunplus Technology Co., Ltd SATALink SPIF225A
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

[dmesg]
Buffer I/O error on device sda1, logical block 520
[17212924.352000] EXT3-fs error (device sda1): ext3_readdir: directory
#2 contains a hole at offset 0
[17212924.368000] Buffer I/O error on device sda1, logical block 0
[17212924.368000] lost page write due to I/O error on sda1
[17212928.912000] EXT3-fs error (device sda1): ext3_find_entry:
reading directory #2 offset 0
[17212928.932000] [ cut here ]
[17212928.936000] WARNING: at fs/buffer.c:1186 mark_buffer_dirty+0xc4/0xdc()
[17212928.944000] Modules linked in: sd_mod usb_storage scsi_mod nfsd
lockd nfs_acl auth_rpcgss sunrpc exportfs ipv6 loop ohci1394 ehci_hcd
uhci_hcd ieee1394 usbcore
[17212928.96] Call Trace:
[17212928.964000] [<80086b00>] dump_stack+0x8/0x34
[17212928.968000] [<800a4090>] warn_on_slowpath+0x60/0x88
[17212928.972000] [<80139ec0>] mark_buffer_dirty+0xc4/0xdc
[17212928.98] [<80173f08>] ext3_commit_super+0x5c/0x9c
[17212928.984000] [<80174db0>] ext3_handle_error+0x94/0xfc
[17212928.988000] [<80174f00>] ext3_error+0x58/0x6c
[17212928.996000] [<80170af4>] ext3_find_entry+0x51c/0x6e4
[17212929.00] [<80172a98>] ext3_lookup+0x50/0x118
[17212929.004000] [<8011861c>] do_lookup+0x1e0/0x210
[17212929.012000] [<8011a8d0>] __link_path_walk+0x500/0xe24
[17212929.016000] [<8011b244>] path_walk+0x50/0xe0
[17212929.02] [<8011b4ec>] do_path_lookup+0x74/0x190
[17212929.024000] [<8011c14c>] __user_walk_fd+0x54/0x88
[17212929.032000] [<80113aa0>] vfs_stat_fd+0x28/0x68
[17212929.036000] [<80113be0>] sys_stat64+0x20/0x50
[17212929.04] [<800890ec>] stack_done+0x20/0x3c
[17212929.044000]
[17212929.048000] ---[ end trace 37ff880bcc35af8e ]---
[17212929.052000] Buffer I/O error on device sda1, logical block 0
[17212929.052000] lost page write due to I/O error on sda1
[17224550.32] EXT3-fs error (device sda1): ext3_readdir: directory
#2 contains a hole at offset 0
[17224550.332000] Buffer I/O error on device sda1, logical block 0
[17224550.332000] lost page write due to I/O error on sda1
[17224550.36] EXT3-fs error (device sda1): ext3_get_inode_loc:
unable to read inode block - inode=2, block=8
[17224550.372000] Buffer I/O error on device sda1, logical block 0
[17224550.372000] lost page write due to I/O error on sda1
[17224550.392000] EXT3-fs error (device sda1) in
ext3_reserve_inode_write: IO failure
[17224550.404000] Buffer I/O error on device sda1, logical block 0
[17224550.404000] lost page write due to I/O error on sda1
[17224553.712000] EXT3-fs error (device sda1): ext3_readdir: directory
#2 contains a hole at offset 0
[17224553.724000] Buffer I/O error on device sda1, logical block 0
[17224553.724000] lost page write due to I/O error on sda1
[17224553.748000] EXT3-fs error (device sda1): ext3_get_inode_loc:
unable to read inode block - inode=2, block=8
[17224553.76] Buffer I/O error on device sda1, logical block 0
[17224553.76] lost page write due to I/O error on sda1
[17224553.78] EXT3-fs error (device sda1) in
ext3_reserve_inode_write: IO failure
[17224553.792000] Buffer I/O error on device sda1, logical block 0
[17224553.792000] lost page write due to I/O error on sda1
[17224555.936000] journal_bmap: journal block not found at offset 4672 on sda1
[17224555.944000] Aborting journal on device sda1.
[17224555.948000] Buffer I/O error on device sda1, logical block 525
[17224555.948000] lost page write due to I/O error on sda1

-- System Information:
Debian Releas

Processed: forcibly merging 580507 608229

2010-12-28 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> forcemerge 580507 608229
Bug#580507: linux-image-2.6.32-5-openvz-amd64: CONFIG_NF_CONNTRACK_IPV6 is not 
set
Bug#608229: linux-image-2.6-openvz-amd64: ip6tables state match support
Forcibly Merged 580507 608229.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
580507: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580507
608229: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608229
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.129358123521520.transcr...@bugs.debian.org

Processed: reassign 608229 to linux-2.6

2010-12-28 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> reassign 608229 linux-2.6
Bug #608229 [linux-image-2.6-openvz-amd64] linux-image-2.6-openvz-amd64: 
ip6tables state match support
Bug reassigned from package 'linux-image-2.6-openvz-amd64' to 'linux-2.6'.
Bug No longer marked as found in versions linux-latest-2.6/28.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
608229: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608229
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.129358122921506.transcr...@bugs.debian.org

Bug#604083: closed by Ben Hutchings (Bug#604083: fixed in linux-2.6 2.6.32-29)

2010-12-28 Thread Ivan Sergio Borgonovo 
On Fri, 10 Dec 2010 14:51:24 +
ow...@bugs.debian.org (Debian Bug Tracking System) wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the linux-2.6 package:
> 
> #604083: add support for megaraid 9240 9260 9280 8704 8708 8880
> 
> 
> It has been closed by Ben Hutchings .
> 
> Their explanation is attached below along with your original
> report. If this explanation is unsatisfactory and you have not
> received a better one in a separate message then please contact
> Ben Hutchings  by replying to this email.

I didn't have any chance to put my hands on a box with that
controller for a long time but today I installed squeeze with no
problem.

I can confirm it actually works.

Thanks

-- 
Ivan Sergio Borgonovo
http://www.webthatworks.it




-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20101229005705.043ff...@dawn.webthatworks.it

Kredit ot swedcredit.lv! Eto dlja vas!

2010-12-28 Thread PazinojumsNr18 
Akcija!

Informejam, ka sakara ar Swed credit ielausanos Latvijas interneta un SMS 
kreditu tirgu, tagad tu vari sanemt aizdevumu TUKSTOTS (1000) latus lidz pat 1 
gadam, NEKADI PROCENTI, NEKADAS KOMISIJAS. Steidzies izmantot!

http://WWW.SMSKREDIT.INFO - un Tavi sapni piepildisies.



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/auto-000253945...@fe01-cgp.akado.ru

Bug#608229: linux-image-2.6-openvz-amd64: ip6tables state match support

2010-12-28 Thread maximilian attems 
forcemerge 580507 608229
stop

On Tue, Dec 28, 2010 at 11:43:41PM +0100, David Mlady wrote:
> Package: linux-image-2.6-openvz-amd64
> Version: 2.6.32+28
> Severity: normal
> Tags: ipv6
> 
> Hello,
> I have problem with ip6table and state match support. I'm using Squeeze and 
> this issue is only with linux-image-2.6-openvz-amd64, standard kernel 
> (linux-image-2.6-amd64) works well.
> 
> How to reproduce:
> /sbin/ip6tables -A STATE -m state --state RELATED,ESTABLISHED -j ACCEPT
> 
> Output with openvz kernel is "ip6tables: No chain/target/match by that name." 
> and "can't load conntrack support for proto=10" in syslog.

this will be fixed for 2.6.32-30



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20101228224942.gk20...@vostochny.stro.at

Bug#608229: linux-image-2.6-openvz-amd64: ip6tables state match support

2010-12-28 Thread David Mlady 
Package: linux-image-2.6-openvz-amd64
Version: 2.6.32+28
Severity: normal
Tags: ipv6

Hello,
I have problem with ip6table and state match support. I'm using Squeeze and 
this issue is only with linux-image-2.6-openvz-amd64, standard kernel 
(linux-image-2.6-amd64) works well.

How to reproduce:
/sbin/ip6tables -A STATE -m state --state RELATED,ESTABLISHED -j ACCEPT

Output with openvz kernel is "ip6tables: No chain/target/match by that name." 
and "can't load conntrack support for proto=10" in syslog.


-- 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/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20101228224341.11954.53426.report...@localhost

Bug#585419: marked as done (drop vol_id related code from get_fstype in /usr/share/initramfs-tools/scripts/functions)

2010-12-28 Thread Debian Bug Tracking System 
Your message dated Tue, 28 Dec 2010 22:24:56 +0100
with message-id <20101228212456.gb14...@stro.at>
and subject line Re: Bug#585419: drop vol_id related code from get_fstype in 
/usr/share/initramfs-tools/scripts/functions
has caused the Debian Bug report #585419,
regarding drop vol_id related code from get_fstype in 
/usr/share/initramfs-tools/scripts/functions
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.)


-- 
585419: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=585419
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: initramfs-tools
Version: 0.96.1
Severity: wishlist
Tags: patch


Hi.

May I suggest to drop the code from get_fstype in 
/usr/share/initramfs-tools/scripts/functions
that uses vol_id.

AFAIK vol_id is no longer available in udev or any other Debian package,
so this is dead code.

Attached is a patch for this.


Cheers,
Chris.
--- /usr/share/initramfs-tools/scripts/functions2010-06-08 
12:10:38.0 +0200
+++ /usr/share/initramfs-tools/scripts/functions2010-06-10 
14:50:25.822262987 +0200
@@ -285,13 +285,10 @@
local FS FSTYPE FSSIZE RET
FS="${1}"
 
-   # vol_id has a more complete list of file systems,
-   # but fstype is more robust
+   # blk_id has a more complete list of file systems, but fstype is more 
robust
eval $(fstype "${FS}" 2> /dev/null)
if [ "$FSTYPE" = "unknown" ] &&  command -v blkid >/dev/null 2>&1 ; then
FSTYPE=$(blkid -o value -s TYPE "${FS}")
-   elif [ "$FSTYPE" = "unknown" ] && [ -x /lib/udev/vol_id ]; then
-   FSTYPE=$(/lib/udev/vol_id -t "${FS}" 2> /dev/null)
fi
RET=$?
 
--- End Message ---
--- Begin Message ---
On Thu, 10 Jun 2010, Christoph Anton Mitterer wrote:

> May I suggest to drop the code from get_fstype in 
> /usr/share/initramfs-tools/scripts/functions
> that uses vol_id.
> 
> AFAIK vol_id is no longer available in udev or any other Debian package,
> so this is dead code.

it may be dead code, but it hurts nobody and I prefer to keep at least
one distribution backward compatibility. It helps on distribution upgrades
and peoples with mixed setups. Squeeze is not yet released and thus the
current stable is using vol_id. So I'd think it is reasonable to axe it
after the Wheezy release.

The comment got updated and we will axe the vol_id referred code,
added fixme notice on the vol_id invocation in preinst.
 
> Attached is a patch for this.
> 

Closing in order to cleanup the initramfs-tools bug reports.

Anyway thanks for the patch and happy 2011.

-- 
maks

--- End Message ---

Bug#607879: Fwd: Bug#607879: System hangs up with mmap.c:873!

2010-12-28 Thread Grzegorz Wyrobek 
> Are you creating them with live-helper?

No.

> After I removed package 'console-kit-dae' it looks stable.

So it will be checked.

Processed: tagging 502792

2010-12-28 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 502792 + pending
Bug #502792 [initramfs-tools] initramfs-tools: mkinitramfs-kpkg ignores UMASK 
setting
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
502792: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502792
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.12935682185342.transcr...@bugs.debian.org

Bug#491321: marked as done (initramfs-tools: does not support splashy)

2010-12-28 Thread Debian Bug Tracking System 
Your message dated Tue, 28 Dec 2010 21:25:12 +0100
with message-id <20101228202512.ga14...@stro.at>
and subject line Re: Bug#491321: initramfs-tools: does not support splashy
has caused the Debian Bug report #491321,
regarding initramfs-tools: does not support splashy
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.)


-- 
491321: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=491321
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: initramfs-tools
Version: 0.92e
Severity: normal


While there are multiple calls to usplash in initramfs functions there
is no support for splashy. On systems that spend substantial part of
boot in the initramfs this is inadequate.

I attach a patch that should solve the problem but ideally the script
should be reworked so that the presence of splash solutions is tested
only in one place.

Thanks

Michal
--- /usr/share/initramfs-tools/scripts/functions2008-04-02 
22:19:58.0 +0200
+++ chroot/usr/share/initramfs-tools/scripts/functions  2008-07-18 
16:12:45.0 +0200
@@ -25,7 +25,9 @@
 {
if [ -x /sbin/usplash_write ]; then
/sbin/usplash_write "TEXT $@"
-   fi
+   else ; if [ -x /sbin/splashy_update ] ; then
+   /sbin/splashy_update "TEXT $@"
+   fi ; fi
_log_msg "Begin: $@ ..."
 }
 
@@ -33,7 +35,9 @@
 {
if [ -x /sbin/usplash_write ]; then
/sbin/usplash_write "SUCCESS ok"
-   fi
+   else ; if [ -x /sbin/splashy_update ] ; then
+   /sbin/splashy_update "SUCCESS ok"
+   fi ; fi
_log_msg "Done."
update_progress
 }
@@ -51,14 +55,18 @@
 
if [ -x /sbin/usplash_write ]; then
/sbin/usplash_write "PROGRESS $PROGRESS_STATE"
-   fi
+   else ; if [ -x /sbin/splashy_update ] ; then
+   /sbin/splashy_update "PROGRESS $PROGRESS_STATE"
+   fi ; fi
 }
 
 panic()
 {
if [ -x /sbin/usplash_write ]; then
/sbin/usplash_write "QUIT"
-   fi
+   else ; if [ -x /sbin/splashy_update ] ; then
+   /sbin/splashy_update "QUIT"
+   fi ; fi
# Disallow console access
if [ -n "${panic}" ]; then
sleep ${panic}
--- End Message ---
--- Begin Message ---
On Wed, 24 Mar 2010, maximilian attems wrote:

> On Fri, 18 Jul 2008, Michal Suchanek wrote:
> 
> > While there are multiple calls to usplash in initramfs functions there
> > is no support for splashy. On systems that spend substantial part of
> > boot in the initramfs this is inadequate.
> 

thanks a lot for the provided patch.

Splashy will not be released with upcomming Squeeze and I do not expect
a lot of activity later on. You'll find a branch "maks/nuke_usplash"
http://git.debian.org/?p=kernel/initramfs-tools.git;a=summary
where any usplash ref is gone. Anyway out of scope of this bug.

Closing in order to further clean up initramfs-tools bugreports.

best wishes for 2011

-- 
maks

--- End Message ---

Processed: Re: Bug#608185: btrfs-tools: balance tree action should be only triggered by root

2010-12-28 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> reassign 608185 linux-2.6
Bug #608185 [btrfs-tools] btrfs-tools: balance tree action should be only 
triggered by root
Bug reassigned from package 'btrfs-tools' to 'linux-2.6'.
Bug No longer marked as found in versions btrfs-tools/0.19+20100601-3.
> severity 608185 important
Bug #608185 [linux-2.6] btrfs-tools: balance tree action should be only 
triggered by root
Severity set to 'important' from 'serious'

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
608185: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608185
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.129356467523551.transcr...@bugs.debian.org

Bug#607879: System hangs up with mmap.c:873!

2010-12-28 Thread Lukasz Szotek 
I can confirm this bug too.
It happens under VirtualBox and 2 testing PCs.

But I think I managed to solve this problem for me.
After I removed package 'console-kit-dae' it looks stable.
So I think this is problem with console-kit-dae or console-kit-dae+aufs.

kern.log
Description: Binary data

Bug#607669: marked as done (linux-image-2.6.37-rc5-amd64: Dell Latitude D630 backlight fails to resume to "on")

2010-12-28 Thread Debian Bug Tracking System 
Your message dated Tue, 28 Dec 2010 14:36:46 +0100
with message-id <201012281436.47210.did...@raboud.com>
and subject line Re: Bug#607669: linux-image-2.6.37-rc5-amd64: Dell Latitude 
D630 backlight fails to resume to "on"
has caused the Debian Bug report #607669,
regarding linux-image-2.6.37-rc5-amd64: Dell Latitude D630 backlight fails to 
resume to "on"
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.)


-- 
607669: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607669
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 2.6.37~rc5-1~experimental.3
Severity: normal
Tags: experimental

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi, 

when running the 3.6.37-rc5 kernel, I noticed that my screen fails to
"relight" after being suspended by the desktop manager (inactivitiy timeout).
I can reliably reproduce this (and recover) by following these steps:

1) boot, up to a running X
2) $ xset dpms force off
3) move mouse

Now the screen is on, things work, but I cannot light the screen more than a
bare minimum (using the Fn-{up,down} "hardware" keys), while I can before step
2. I can recover from this situation by suspending-to-ram and waking up again.

This is also a regression from the Squeeze-Sid kernel (2.6.32-29), but I think
it worked with 2.6.36.

Cheers, 

OdyX

- -- Package-specific info:
** Version:
Linux version 2.6.37-rc5-amd64 (Debian 2.6.37~rc5-1~experimental.3) 
(b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.5-7) ) #1 SMP Sat Dec 11 
19:38:02 UTC 2010

** Command line:
BOOT_IMAGE=/vmlinuz-2.6.37-rc5-amd64 root=/dev/mapper/Tamino-Root ro quiet 
splash

** Not tainted

** Kernel log:
[ 9368.431655] uhci_hcd :00:1d.1: setting latency timer to 64
[ 9368.431682] usb usb6: root hub lost power or was reset
[ 9368.431694] uhci_hcd :00:1d.2: PCI INT C -> GSI 22 (level, low) -> IRQ 22
[ 9368.431701] uhci_hcd :00:1d.2: setting latency timer to 64
[ 9368.431728] usb usb7: root hub lost power or was reset
[ 9368.431742] ehci_hcd :00:1d.7: PCI INT A -> GSI 20 (level, low) -> IRQ 20
[ 9368.431748] ehci_hcd :00:1d.7: setting latency timer to 64
[ 9368.431796] pci :00:1e.0: setting latency timer to 64
[ 9368.431808] ata_piix :00:1f.1: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 9368.431813] ata_piix :00:1f.1: setting latency timer to 64
[ 9368.431864] ahci :00:1f.2: setting latency timer to 64
[ 9368.431980] ata5: port disabled. ignoring.
[ 9368.431989] pci :00:1c.5: wake-up capability disabled by ACPI
[ 9368.432016] tg3 :09:00.0: PME# disabled
[ 9368.432052] i915 :00:02.0: setting latency timer to 64
[ 9368.439031] sd 0:0:0:0: [sda] Starting disk
[ 9368.472278] dell-wmi: Unknown key e043 pressed
[ 9368.484437] firewire_core: skipped bus generations, destroying all nodes
[ 9368.515466] serial 00:09: activated
[ 9368.760091] ata3: SATA link down (SStatus 0 SControl 300)
[ 9368.792078] usb 7-1: reset full speed USB device using uhci_hcd and address 2
[ 9368.984133] firewire_core: rediscovered device fw0
[ 9369.040077] usb 3-2: reset full speed USB device using uhci_hcd and address 2
[ 9369.216013] btusb 3-2:1.0: no reset_resume for driver btusb?
[ 9369.216018] btusb 3-2:1.1: no reset_resume for driver btusb?
[ 9369.216341] ata4.00: configured for UDMA/33
[ 9369.304096] usb 7-2: reset full speed USB device using uhci_hcd and address 3
[ 9369.513976] usb 7-1.2: reset full speed USB device using uhci_hcd and 
address 4
[ 9369.620975] usbfs 7-1.2:1.0: no reset_resume for driver usbfs?
[ 9371.188263] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 9371.195573] ata1.00: configured for UDMA/100
[ 9371.205301] dell-wmi: Unknown key e044 pressed
[ 9371.356279] PM: resume of devices complete after 2937.594 msecs
[ 9371.356773] PM: Finishing wakeup.
[ 9371.356775] Restarting tasks ... 
[ 9371.358520] usb 7-1.2: usbfs: process 2398 (pcscd) did not claim interface 0 
before use
[ 9371.373314] done.
[ 9371.373321] video LNXVIDEO:01: Restoring backlight state
[ 9371.422636] composite sync not supported
[ 9373.495513] cfg80211: Calling CRDA to update world regulatory domain
[ 9373.529139] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection 
driver for Linux, in-tree:s
[ 9373.529142] iwl3945: Copyright(c) 2003-2010 Intel Corporation
[ 9373.529227] iwl3945 :0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 9373.529247] iwl3945 :0c:00.0: setting latency timer to 64
[ 9373.582914] iwl3945 :0c:00.0: Tunable channels: 13 802.11bg, 23 802.11a 
channels
[ 9373.582918] iwl3945 :0c:00.0: Detected Intel Wirel

Bug#599161: confirmation of the bug

2010-12-28 Thread Paweł Puterla 
Hi

I only wanted (for now) to confirm that the bug exists. I have the same
kernel+hvm version as the reporter.
Today we just noticed exactly +2999sec (50min) time skew on our dom0.

The only kernel message I got was:

[3103167.615818] Clocksource tsc unstable (delta = -2999660326203 ns)


I will also try to look after the bug report on xen-* lists.
Just wanted to confirm Mark's report.


-- 
Paweł Puterla
Network and Systems Administrator
eCard S.A.
Office: Królewska 16 Street, 00-103 Warsaw, POLAND
Phone: +48 22 493 44 24
ppute...@ecard.pl 
/eCard S.A. Joint Stock Company, with its registered office in Gdańsk
(80-387 Gdańsk), Arkońska 11 Street, entered into the Register of
Enterpreneurs of the National Court Register by the District Court for
the City of Gdańsk, VII Commercial Division of the National Court
Register 042304, with the initial capital fully collected in the
amount of PLN 11 000 000,00 , NIP no: 521-31-03-040, with Management
Board consisting of: Ewa Bereśniewicz-Kozłowska - President of
Management Board , Tomasz Krasiński - Vice President of Management
Board, Alicja Kuran-Kawka - Member of Management Board. /

Bug#607709: XEN kernel crash on DNS process

2010-12-28 Thread Giuseppe Sacco 
Hi all,
I confirm the problem is really XEN related. We made more tests with non
XEN kernel and we never got the error reported here.
Now we are going to run again a XEN dom0 kernel, updating to latest
kernel (from 2.6.32-27 to 2.6.32-29). I will report here more
information whenever I collect them.

The problem is: when the system crash, the machine is still powered on
but nobody may connect and login. So, we are going to log in on the
console and leave a shell opened. When the kernel will hang, we'll try
to issue «xm dmesg» command.

Setting syslog on a remote machine, would this help at all?

Thanks,
Giuseppe




--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1293537131.15990.25.ca...@scarafaggio

Bug#607879: System hangs up with mmap.c:873!

2010-12-28 Thread Timo Juhani Lindfors 
Ronny Standtke  writes:
> I can confirm this bug.
> I created a Debian Live system based on Squeeze and on many machines the 
> system just hangs when shutting down.
>
> My latest test was on a Dell Optiplex SX280. I will attach the entries in 
> kern.log and the output of lspci on this system.

ok, does it happen if you boot the livecd under qemu?




-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/84r5d2rvha@sauna.l.org

Bug#607879: System hangs up with mmap.c:873!

2010-12-28 Thread Ronny Standtke 
I can confirm this bug.
I created a Debian Live system based on Squeeze and on many machines the 
system just hangs when shutting down.

My latest test was on a Dell Optiplex SX280. I will attach the entries in 
kern.log and the output of lspci on this system.
00:00.0 Host bridge: Intel Corporation 82915G/P/GV/GL/PL/910GL Memory 
Controller Hub (rev 04)
00:01.0 PCI bridge: Intel Corporation 82915G/P/GV/GL/PL/910GL PCI Express Root 
Port (rev 04)
00:02.0 VGA compatible controller: Intel Corporation 82915G/GV/910GL Integrated 
Graphics Controller (rev 04)
00:02.1 Display controller: Intel Corporation 82915G Integrated Graphics 
Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI 
Express Port 1 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
USB UHCI #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
USB UHCI #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
USB UHCI #3 (rev 03)
00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
USB UHCI #4 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
USB2 EHCI Controller (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d3)
00:1e.2 Multimedia audio controller: Intel Corporation 82801FB/FBM/FR/FW/FRW 
(ICH6 Family) AC'97 Audio Controller (rev 03)
00:1f.0 ISA bridge: Intel Corporation 82801FB/FR (ICH6/ICH6R) LPC Interface 
Bridge (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) 
IDE Controller (rev 03)
00:1f.2 IDE interface: Intel Corporation 82801FB/FW (ICH6/ICH6W) SATA 
Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus 
Controller (rev 03)
02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5751 Gigabit 
Ethernet PCI Express (rev 01)
Dec 28 10:44:58 debian kernel: [   84.124117] [ cut here ]
Dec 28 10:44:58 debian kernel: [   84.124191] kernel BUG at /build/buildd-linux-2.6_2.6.32-29-i386-Of6Yt1/linux-2.6-2.6.32/debian/build/source_i386_none/mm/mmap.c:873!
Dec 28 10:44:58 debian kernel: [   84.124346] invalid opcode:  [#1] SMP 
Dec 28 10:44:58 debian kernel: [   84.124413] last sysfs file: /sys/devices/virtual/sound/timer/uevent
Dec 28 10:44:58 debian kernel: [   84.124496] Modules linked in: ppdev lp sco bridge stp bnep l2cap bluetooth rfkill vboxnetadp vboxnetflt vboxdrv uinput fuse dm_crypt dm_mod snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd parport_pc dcdbas soundcore parport psmouse pcspkr snd_page_alloc i2c_i801 rng_core serio_raw evdev processor ext4 jbd2 crc16 ohci_hcd squashfs loop aufs(C) nls_utf8 nls_cp437 vfat fat ext2 mbcache ide_generic ide_core sg i915 sd_mod crc_t10dif drm_kms_helper sr_mod cdrom drm i2c_algo_bit usbhid hid usb_storage ata_generic tg3 i2c_core ata_piix video libata thermal uhci_hcd libphy output ehci_hcd scsi_mod button thermal_sys usbcore nls_base [last unloaded: scsi_wait_scan]
Dec 28 10:44:58 debian kernel: [   84.125836] 
Dec 28 10:44:58 debian kernel: [   84.125864] Pid: 2475, comm: console-kit-dae Tainted: G C (2.6.32-5-686 #1) OptiPlex SX280   
Dec 28 10:44:58 debian kernel: [   84.125993] EIP: 0060:[] EFLAGS: 00010202 CPU: 0
Dec 28 10:44:58 debian kernel: [   84.126071] EIP is at find_mergeable_anon_vma+0xbd/0x14b
Dec 28 10:44:58 debian kernel: [   84.126141] EAX: dbdab478 EBX: dbdab490 ECX: dbdab478 EDX: dc39bdc0
Dec 28 10:44:58 debian kernel: [   84.126224] ESI: dc39b0b0 EDI: dc39bdc0 EBP: 00100073 ESP: db99be80
Dec 28 10:44:58 debian kernel: [   84.126306]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Dec 28 10:44:58 debian kernel: [   84.126378] Process console-kit-dae (pid: 2475, ti=db99a000 task=dcdfb740 task.ti=db99a000)
Dec 28 10:44:58 debian kernel: [   84.126484] Stack:
Dec 28 10:44:58 debian kernel: [   84.126514]  dbb56200 e00e6a3f db9b06e0 b66d6000 dc39b0b0  dc39b0b0 
Dec 28 10:44:58 debian kernel: [   84.126654] <0> dc3bba00 c10a22bd 0001 c1856c60 dd780b64 b66d6218 c1099709 b66d6218
Dec 28 10:44:58 debian kernel: [   84.126808] <0> dc39b0b0 dc3bba00 0001 b66b9000 0200 c126d2bf df1e6d00 e00e6593
Dec 28 10:44:58 debian kernel: [   84.126967] Call Trace:
Dec 28 10:44:58 debian kernel: [   84.127019]  [] ? aufs_fault+0xf1/0xfb [aufs]
Dec 28 10:44:58 debian kernel: [   84.128004]  [] ? anon_vma_prepare+0x1d/0x8c
Dec 28 10:44:58 debian kernel: [   84.136836]  [] ? __do_fault+0xb2/0x3b1
Dec 28 10:44:58 debian kernel: [   84.136836]  [] ? down_read+0x8/0x16
Dec 28 10:44:58 debian kernel: [   84.136836]  [] ? si_read_lock+0x7b/0x83 [aufs]
Dec 28 10:44:58 debian kernel: [   84.136836]  [] ? handle_mm_fault+0x48f/0x959
Dec 28 10:44:58 debian kernel: [   84.136836]  [] ? vma_link+0x4e/0x68
Dec 28 10:44:58 deb