Processed: fix pkg name which is part of linux-2.6

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 571305 linux-image-2.6.32-2-sb1-bcm91250a 2.6.32-5
Bug #571305 [linux-image-2.6.32-9-sb1-bcm91250a] Swarm does not boot on .32 
anymore.
Warning: Unknown package 'linux-image-2.6.32-9-sb1-bcm91250a'
Bug reassigned from package 'linux-image-2.6.32-9-sb1-bcm91250a' to 
'linux-image-2.6.32-2-sb1-bcm91250a'.
Bug No longer marked as found in versions 2.6.32-5.
Bug #571305 [linux-image-2.6.32-2-sb1-bcm91250a] Swarm does not boot on .32 
anymore.
There is no source info for the package 'linux-image-2.6.32-2-sb1-bcm91250a' at 
version '2.6.32-5' with architecture ''
Unable to make a source version for version '2.6.32-5'
Bug Marked as found in versions 2.6.32-5.
> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
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.126708332121572.transcr...@bugs.debian.org

Backporting HIGHPTE option patch from tip.git

[Ian Campbell]

Is it acceptable to backport
http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=commitdiff;h=a73a040e3b18521f83e726abacc2f3992a148388
 into the sid kernel?

This patch is a precursor to a Xen fix but since it touches generic code
I thought I would run it by the list first.

The patch adds a command line option to disable the effects of
CONFIG_HIGHPTE but does not change anything by default and is about as
safe as any patch could be.

The followup Xen patch is
http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commitdiff;h=9be6abceadd654543648b799ae430f30e09959ac
and disables HIGHPTE when running under Xen. It prevents crashes under
load due to HIGHPTE races which cannot be otherwise (easily) avoided
under Xen.

Ian.
-- 
Ian Campbell

It's NO USE ... I've gone to "CLUB MED"!!


signature.asc
Description: This is a digitally signed message part

Bug#567468: md homehost

[Goswin von Brederlow]

Neil Brown  writes:

> On Wed, 24 Feb 2010 14:41:16 +0100
> Goswin von Brederlow  wrote:
>
>> Neil Brown  writes:
>> 
>> > On Tue, 23 Feb 2010 07:27:00 +0100
>> > martin f krafft  wrote:
>> >> The only issue homehost protects against, I think, is machines that
>> >> use /dev/md0 directly from grub.conf or fstab.
>> >
>> > That is exactly correct.  If no code or config file depends on a name like
>> > /dev/mdX or /dev/md/foo, then you don't need to be concerned about the 
>> > whole
>> > homehost thing.
>> > You can either mount by fs-uuid, or mount e.g.
>> >/dev/disk/by-id/md-uuid-8fd0af3f:4fbb94ea:12cc2127:f9855db5 
>> 
>> What if you have two raids (one local, one from the other hosts that
>> broke down) and both have LVM on it with /dev/vg/root?
>> 
>> Shouldn't it only assemble the local raid (as md0 or whatever) and then
>> only start the local volume group? If it assembles the remote raid as
>> /dev/md127 as well then lvm will have problems and the boot will likely
>> (even randomly) go wrong since only one VG can be activated.
>> 
>> I think it is pretty common for admins to configure LVM to the same
>> volume group name on different systems. So if you consider raids being
>> pluged into other systems please keep this in mind.
>
> You are entirely correct.  However lvm problems are not my problems.
>
> It has always been my position that the best way to configure md is to
> explicitly list your arrays in mdadm.conf.  But people seem to not like this
> and want it to all be 'automatic'.  So I do my best to make it as automatic
> as possible but still remove as many of the possible confusion that this can
> cause as possible.  But I cannot remove them all.
>
> If you move disks around and boot and lvm gets confused because there are two
> things call "/dev/vg/root", then I'm sorry but there is nothing I can do
> about that.  If you had an mdadm.conf which listed you md arrays, and had
>auto -all
> then you can be sure that mdadm would not be contributing to this problem.
>
> NeilBrown

Yes you can do something about it: Only start the raid arrays with the
correct homehost.

If the homehost is only used to decide wether the prefered minor in the
metadata is used for the device name then I feel the feature is entirely
useless. It would only help in "stupid" configurations, i.e. when you
use the device name directly.

Another scenario where starting a raid with the wrong homehost would be
bad is when the raid is degraded and you have a global spare. You
probably wouldn't want the global spare of one host to be used to repair
a raid of another host.

MfG
Goswin

PS: If a raid is not listed in mdadm.conf doesn't it currently start too
but the name can be random?



-- 
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/87eik94wg1@frosties.localdomain

Processed: Re: Bug#571279: suspend-script: kernel errors when resuming from suspend

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 571279 linux-2.6
Bug #571279 [suspend-script] suspend-script: kernel errors when resuming from 
suspend
Warning: Unknown package 'suspend-script'
Bug reassigned from package 'suspend-script' to 'linux-2.6'.
> --
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
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.126708000228799.transcr...@bugs.debian.org

Bug#571301: Hung on Disk-Detect in 5.0.4 stable netinstall for AMD64

[Scott Nanni]

Package: linux-2.6
Version: 2.6.26-2-amd64

[ 3337.192061] INFO: task cdrom_id:2249 blocked for more than 120 seconds.
[ 3337.192064] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[ 3337.192067] cdrom_id  D 0002 0  2249  1
[ 3337.192071]  81003e993928 0082 e02087a5e0a8a4e0
8da5e0b8a4e0a6a4
[ 3337.192074]  81003d07cee0 81003f62a200 81003d07d168
95a4e020
[ 3337.192077]  a4e082a4e096a4e0 e0b2a4e0bea4e097 e0202c82a4e087a5
a4e020bea4e0afa4
[ 3337.192080] Call Trace:
[ 3337.192102]  [] schedule_timeout+0x1e/0xad
[ 3337.192129]  [] :ide_core:ide_do_request+0x1c/0x933
[ 3337.192141]  [] :ide_core:ide_do_request+0x1c/0x933
[ 3337.192146]  [] wait_for_common+0xcf/0x13a
[ 3337.192151]  [] default_wake_function+0x0/0xe
[ 3337.192164]  [] :ide_core:ide_do_drive_cmd+0xe2/0x109
[ 3337.192173]  [] :ide_cd_mod:ide_cd_queue_pc+0x42/0xca
[ 3337.192179]  [] blk_rq_init+0x1c/0x85
[ 3337.192185]  []
:ide_cd_mod:cdrom_check_status+0x68/0x77
[ 3337.192197]  [] blk_end_sync_rq+0x0/0x2e
[ 3337.192203]  []
:ide_cd_mod:ide_cdrom_check_media_change_real+0x1d/0x38
[ 3337.192211]  [] :cdrom:media_changed+0x44/0x74
[ 3337.192215]  [] check_disk_change+0x1f/0x76
[ 3337.192221]  [] :cdrom:cdrom_open+0x983/0xa14
[ 3337.192226]  [] dput+0x1c/0xdd
[ 3337.192230]  [] kobject_get+0x12/0x17
[ 3337.192234]  [] get_disk+0x40/0x5b
[ 3337.192237]  [] exact_lock+0xc/0x14
[ 3337.192243]  [] :ide_cd_mod:idecd_open+0x5b/0x89
[ 3337.192246]  [] blkdev_open+0x0/0x5d
[ 3337.192249]  [] do_open+0xd1/0x2e8
[ 3337.192253]  [] bdget+0x113/0x11b
[ 3337.192256]  [] blkdev_open+0x0/0x5d
[ 3337.192259]  [] blkdev_open+0x2e/0x5d
[ 3337.192264]  [] __dentry_open+0x12c/0x238
[ 3337.192269]  [] do_filp_open+0x3d7/0x7c4
[ 3337.192277]  [] do_page_fault+0x5d8/0x9c8
[ 3337.192281]  [] get_unused_fd_flags+0x71/0x115
[ 3337.192286]  [] do_sys_open+0x46/0xc3
[ 3337.192290]  [] system_call_after_swapgs+0x8a/0x8f
[ 3337.192295]
[ 3337.192297] INFO: task cdrom_id:3105 blocked for more than 120 seconds.
[ 3337.192299] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[ 3337.192301] cdrom_id  D 81003d81ec00 0  3105  1
[ 3337.192304]  81003d07bd20 0086 81003d0741ed
81003d07be68
[ 3337.192307]  81003d07d570 81003f6b10e0 81003d07d7f8
3d81ed58
[ 3337.192310]  8031b678 81003d94da40 8031247d
01013f407e40
[ 3337.192312] Call Trace:
[ 3337.192317]  [] kobject_get+0x12/0x17
[ 3337.192320]  [] get_disk+0x40/0x5b
[ 3337.192324]  [] __mutex_lock_slowpath+0x64/0x9b
[ 3337.192328]  [] blkdev_open+0x0/0x5d
[ 3337.192331]  [] mutex_lock+0xa/0xb
[ 3337.192334]  [] do_open+0xa0/0x2e8
[ 3337.192338]  [] blkdev_open+0x0/0x5d
[ 3337.192341]  [] blkdev_open+0x2e/0x5d
[ 3337.192345]  [] __dentry_open+0x12c/0x238
[ 3337.192349]  [] do_filp_open+0x3d7/0x7c4
[ 3337.192356]  [] do_page_fault+0x5d8/0x9c8
[ 3337.192360]  [] get_unused_fd_flags+0x71/0x115
[ 3337.192365]  [] do_sys_open+0x46/0xc3
[ 3337.192369]  [] system_call_after_swapgs+0x8a/0x8f
[ 3337.192373]
[ 3337.192375] INFO: task cdrom_id:5709 blocked for more than 120 seconds.
[ 3337.192377] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[ 3337.192379] cdrom_id  D 81003d81ec00 0  5709  1
[ 3337.192381]  81003b585d20 0082 81003b5841ed
81003b585e68
[ 3337.192384]  81003d07c850 81003d08c3c0 81003d07cad8
3d81ed58
[ 3337.192387]  8031b678 81003d94da40 8031247d
01013f407e40
[ 3337.192389] Call Trace:
[ 3337.192393]  [] kobject_get+0x12/0x17
[ 3337.192396]  [] get_disk+0x40/0x5b
[ 3337.192401]  [] __mutex_lock_slowpath+0x64/0x9b
[ 3337.192405]  [] blkdev_open+0x0/0x5d
[ 3337.192408]  [] mutex_lock+0xa/0xb
[ 3337.192410]  [] do_open+0xa0/0x2e8
[ 3337.192415]  [] blkdev_open+0x0/0x5d
[ 3337.192418]  [] blkdev_open+0x2e/0x5d
[ 3337.192421]  [] __dentry_open+0x12c/0x238
[ 3337.192426]  [] do_filp_open+0x3d7/0x7c4
[ 3337.192433]  [] do_page_fault+0x5d8/0x9c8
[ 3337.192437]  [] get_unused_fd_flags+0x71/0x115
[ 3337.192442]  [] do_sys_open+0x46/0xc3
[ 3337.192445]  [] system_call_after_swapgs+0x8a/0x8f
[ 3337.192450]
[ 3337.192452] INFO: task cdrom_id:6595 blocked for more than 120 seconds.
[ 3337.192454] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[ 3337.192456] cdrom_id  D 81003d81ec00 0  6595  1
[ 3337.192458]  81003d059d20 0082 81003d0541ed
81003d059e68
[ 3337.192461]  81003f867930 81003f6b03c0 81003f867bb8
3d81ed58
[ 3337.192463]  8031b678 81003d94da40 8031247d
01013f407e40
[ 3337.192466] Call Trace:
[ 3337.192470]  [] kobject_get+0x12/0x17
[ 3337.192473]  [] get_disk+0x40/0x5b
[ 3337.192478]  [] __mutex_lock_slowpath+0x64/0x9b
[ 3337.192481]  [] blkdev_open+0x0/0x5d
[ 3337.192485]  [] mutex_lock+0xa/0xb
[ 3337.192487]  [] do_open+0xa0/0x2e8
[ 

Bug#571266: linux-image-2.6.26-2-486: boot 486 kernel fails with root=LABEL=

[Ben Hutchings]

On Thu, 2010-02-25 at 06:39 +0100, Sven Joachim wrote:
> On 2010-02-25 02:24 +0100, Ben Hutchings wrote:
> 
> > On Wed, 2010-02-24 at 12:51 -0800, william estrada wrote:
> >> Package: linux-image-2.6.26-2-486
> >> Version: 2.6.26-21lenny3
> >> Severity: important
> >> 
> >> In grub.conf,
> >> 
> >>If I use root=/dev/hda3 my systems boots up and runs.
> >>If I use root=LABEL=/Lenny the system hangs on boot.
> > [...]
> >
> > We need to see the messages that are displayed in this case.
> 
> It is a bug in initramfs-tools, in the Lenny version you can't use
> slashes in labels.  See #489008.

That would be a problem, yes.  It is easy enough to work around, but
should probably be fixed in stable anyway since it is not at all obvious
what has gone wrong.

Ben.

-- 
Ben Hutchings
I'm always amazed by the number of people who take up solipsism because
they heard someone else explain it. - E*Borg on alt.fan.pratchett


signature.asc
Description: This is a digitally signed message part

Bug#571266: linux-image-2.6.26-2-486: boot 486 kernel fails with root=LABEL=

[Sven Joachim]

On 2010-02-25 02:24 +0100, Ben Hutchings wrote:

> On Wed, 2010-02-24 at 12:51 -0800, william estrada wrote:
>> Package: linux-image-2.6.26-2-486
>> Version: 2.6.26-21lenny3
>> Severity: important
>> 
>> In grub.conf,
>> 
>>If I use root=/dev/hda3 my systems boots up and runs.
>>If I use root=LABEL=/Lenny the system hangs on boot.
> [...]
>
> We need to see the messages that are displayed in this case.

It is a bug in initramfs-tools, in the Lenny version you can't use
slashes in labels.  See #489008.

Sven



-- 
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/87iq9lan7b@turtle.gmx.de

Bug#566726: marked as done (linux-source-2.6.32: compile fails with "multiple definition of `ieee80211_ " errors)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2010 04:51:55 +
with message-id 
and subject line Bug#566726: fixed in linux-2.6 2.6.32-9
has caused the Debian Bug report #566726,
regarding linux-source-2.6.32: compile fails with "multiple definition of 
`ieee80211_  " errors
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.)


-- 
566726: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566726
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-source-2.6.32
Version: 2.6.32-5
Severity: important

When I tried to compile a kernel it failed with the following messages:

  AR  arch/x86/lib/lib.a
  LD  vmlinux.o
net/built-in.o: In function `ieee80211_wake_queue':
(.text+0xbb5ed): multiple definition of `ieee80211_wake_queue'
drivers/built-in.o:(.text+0x15e699): first defined here
net/built-in.o: In function `ieee80211_rx':
(.text+0xb70f6): multiple definition of `ieee80211_rx'
drivers/built-in.o:(.text+0x164999): first defined here
net/built-in.o: In function `ieee80211_stop_queue':
(.text+0xba8d0): multiple definition of `ieee80211_stop_queue'
drivers/built-in.o:(.text+0x15c0f5): first defined here
make[1]: *** [vmlinux.o] Error 1

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.30-20091002 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-source-2.6.32 depends on:
ii  binutils  2.20-5 The GNU assembler, linker and bina
ii  bzip2 1.0.5-3high-quality block-sorting file co

Versions of packages linux-source-2.6.32 recommends:
ii  gcc   4:4.3.4-1  The GNU C compiler
ii  libc6-dev [libc-dev]  2.10.2-2   GNU C Library: Development Librari
ii  make  3.81-7 An utility for Directing compilati

Versions of packages linux-source-2.6.32 suggests:
ii  kernel-package12.032 A utility for building Linux kerne
ii  libncurses5-dev [ncurses- 5.7+20090803-2 developer's libraries and docs for
pn  libqt3-mt-dev  (no description available)

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: linux-2.6
Source-Version: 2.6.32-9

We believe that the bug you reported is fixed in the latest version of
linux-2.6, which is due to be installed in the Debian FTP archive:

firmware-linux-free_2.6.32-9_all.deb
  to main/l/linux-2.6/firmware-linux-free_2.6.32-9_all.deb
linux-2.6_2.6.32-9.diff.gz
  to main/l/linux-2.6/linux-2.6_2.6.32-9.diff.gz
linux-2.6_2.6.32-9.dsc
  to main/l/linux-2.6/linux-2.6_2.6.32-9.dsc
linux-doc-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-9_all.deb
linux-headers-2.6.32-3-all-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-all-amd64_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-all_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-all_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-amd64_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-common-vserver_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-common-vserver_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-common_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-common_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb
linux-image-2.6.32-3-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-3-amd64_2.6.32-9_amd64.deb
linux-image-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb
linux-libc-dev_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-libc-dev_2.6.32-9_amd64.deb
linux-manual-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-9_all.deb
linux-patch-debian-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-9_all.deb
linux-source-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-source-2.6.32_2.6.32-9_all.deb
linux-support-2.6.32-3_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-support-2.6.32-3_2.6.32-9_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 566...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maint

Bug#508108: marked as done (Please enable XVR-500 and XVR-2500 fb drivers for sparc)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2010 04:51:54 +
with message-id 
and subject line Bug#508108: fixed in linux-2.6 2.6.32-9
has caused the Debian Bug report #508108,
regarding Please enable XVR-500 and XVR-2500 fb drivers for sparc
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.)


-- 
508108: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508108
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 2.6.26-11
Severity: wishlist

We have recently found out that Debian installation UI looks much 
better on various SunBlade systems if the framebuffer drivers for 
XVR-500 and XVR-2500 cards (CONFIG_FB_XVR500, CONFIG_FB_XVR2500) are 
enabled [0,1]. If there is going to be another kernel rebuild before 
lenny, it would be great to enable these drivers. As cards are 
sparc-specific, it is sufficient to enable them for sparc. Also, it 
would be nice to apply the attached simple patch, which adds the PCI 
ID of a card I have in my SunBlade 1000 [1], it appears that it's the 
same chip (same device ID), but manufactured by a different company. 
I've sent the patch to David Miller to be included upstream, however 
haven't heard back yet [2].

[0] http://lists.debian.org/debian-boot/2008/12/msg00040.html
[1] http://lists.debian.org/debian-boot/2008/12/msg00042.html
[2] http://marc.info/?l=linux-sparc&m=122816564110952&w=2
-- 
Jurij Smakov   ju...@wooyd.org
Key: http://www.wooyd.org/pgpkey/  KeyID: C99E03CC
diff -aur a/drivers/video/sunxvr500.c b/drivers/video/sunxvr500.c
--- a/drivers/video/sunxvr500.c	2008-11-20 18:02:37.0 -0500
+++ b/drivers/video/sunxvr500.c	2008-12-01 15:43:04.0 -0500
@@ -396,6 +396,7 @@
 
 static struct pci_device_id e3d_pci_table[] = {
 	{	PCI_DEVICE(PCI_VENDOR_ID_3DLABS, 0x7a0),	},
+	{	PCI_DEVICE(PCI_VENDOR_ID_IGRAPH, 0x7a0),	},
 	{	PCI_DEVICE(PCI_VENDOR_ID_3DLABS, 0x7a2),	},
 	{	.vendor = PCI_VENDOR_ID_3DLABS,
 		.device = PCI_ANY_ID,
diff -aur a/include/linux/pci_ids.h b/include/linux/pci_ids.h
--- a/include/linux/pci_ids.h	2008-11-20 18:02:37.0 -0500
+++ b/include/linux/pci_ids.h	2008-12-01 15:43:04.0 -0500
@@ -930,6 +930,8 @@
 #define PCI_DEVICE_ID_SUN_TOMATILLO	0xa801
 #define PCI_DEVICE_ID_SUN_CASSINI	0xabba
 
+#define PCI_VENDOR_ID_IGRAPH		0x1091
+
 #define PCI_VENDOR_ID_CMD		0x1095
 #define PCI_DEVICE_ID_CMD_643		0x0643
 #define PCI_DEVICE_ID_CMD_646		0x0646
--- End Message ---
--- Begin Message ---
Source: linux-2.6
Source-Version: 2.6.32-9

We believe that the bug you reported is fixed in the latest version of
linux-2.6, which is due to be installed in the Debian FTP archive:

firmware-linux-free_2.6.32-9_all.deb
  to main/l/linux-2.6/firmware-linux-free_2.6.32-9_all.deb
linux-2.6_2.6.32-9.diff.gz
  to main/l/linux-2.6/linux-2.6_2.6.32-9.diff.gz
linux-2.6_2.6.32-9.dsc
  to main/l/linux-2.6/linux-2.6_2.6.32-9.dsc
linux-doc-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-9_all.deb
linux-headers-2.6.32-3-all-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-all-amd64_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-all_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-all_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-amd64_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-common-vserver_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-common-vserver_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-common_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-common_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb
linux-image-2.6.32-3-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-3-amd64_2.6.32-9_amd64.deb
linux-image-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb
linux-libc-dev_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-libc-dev_2.6.32-9_amd64.deb
linux-manual-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-9_all.deb
linux-patch-debian-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-9_all.deb
linux-source-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-source-2.6.32_2.6.32-9_all.deb
linux-support-2.6.32-3_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-support-2.6.32-3_2.6.32-9_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for repo

Bug#571019: marked as done (/dev/ttyS1 on openrd-base not working)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2010 04:51:55 +
with message-id 
and subject line Bug#571019: fixed in linux-2.6 2.6.32-9
has caused the Debian Bug report #571019,
regarding /dev/ttyS1 on openrd-base not working
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.)


-- 
571019: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571019
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 2.6.32-1

- Forwarded message from Luca Niccoli  -

Date: Mon, 22 Feb 2010 02:23:28 +0100
From: Luca Niccoli 
To: debian-...@lists.debian.org
Subject: /dev/ttyS1 on openrd

Hi,

today I tried to use the serial port on my openrd-base (the rs232, not
the one with the mini-usb connector).
After half an hour trying to understand why my ttl level shifter
didn't work, I tried on an other computer, and everything went fine =)
This thread [1] has a patch to enable UART1 by disabling the SDIO with
a boot parameter; it would be nice if it could be ported to debian
and/or upstream.
Cheers,

Luca

[1] http://groups.google.com/group/openrd/browse_thread/thread/7ba48f2d7916a88f


-- 
To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/4e9568871002211723p375422d8vce29e076809e3...@mail.gmail.com

- End forwarded message -

-- 
Martin Michlmayr
http://www.cyrius.com/


--- End Message ---
--- Begin Message ---
Source: linux-2.6
Source-Version: 2.6.32-9

We believe that the bug you reported is fixed in the latest version of
linux-2.6, which is due to be installed in the Debian FTP archive:

firmware-linux-free_2.6.32-9_all.deb
  to main/l/linux-2.6/firmware-linux-free_2.6.32-9_all.deb
linux-2.6_2.6.32-9.diff.gz
  to main/l/linux-2.6/linux-2.6_2.6.32-9.diff.gz
linux-2.6_2.6.32-9.dsc
  to main/l/linux-2.6/linux-2.6_2.6.32-9.dsc
linux-doc-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-9_all.deb
linux-headers-2.6.32-3-all-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-all-amd64_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-all_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-all_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-amd64_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-common-vserver_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-common-vserver_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-common_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-common_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb
linux-image-2.6.32-3-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-3-amd64_2.6.32-9_amd64.deb
linux-image-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb
linux-libc-dev_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-libc-dev_2.6.32-9_amd64.deb
linux-manual-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-9_all.deb
linux-patch-debian-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-9_all.deb
linux-source-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-source-2.6.32_2.6.32-9_all.deb
linux-support-2.6.32-3_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-support-2.6.32-3_2.6.32-9_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 571...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
maximilian attems  (supplier of updated linux-2.6 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 24 Feb 2010 17:06:27 +0100
Source: linux-2.6
Binary: linux-source-2.6.32 linux-doc-2.6.32 linux-manual-2.6.32 
linux-patch-debian-2.6.32 firmware-linux-free linux-support-2.6.32-3 linux-base 
linux-libc-dev linux-headers-2.6.32-3-all linux-headers-2.6.32-3-all-alpha 
linux-headers-2.6.32-3-common linux-image-2.6.32-3-alpha-generic 
linux-headers-2.6.32-3-alpha-generic linux-image-2.6.32-3-alpha-smp 
linux-headers-2.6.32-3-alpha-smp linux-image-2.6.32-3-alpha-legacy 
linux-headers

Bug#542208: marked as done (linux-image-2.6.30-1-amd64: Created /etc/kernel-img.conf has reference to non-existent manpage)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2010 04:51:54 +
with message-id 
and subject line Bug#542208: fixed in linux-2.6 2.6.32-9
has caused the Debian Bug report #542208,
regarding linux-image-2.6.30-1-amd64: Created /etc/kernel-img.conf has 
reference to non-existent manpage
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.)


-- 
542208: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542208
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.30-1-amd64
Version: 2.6.30-5
Severity: minor

In postinst, /etc/kernel-img.conf is created with a reference to a
non-existent man page:

print CONF "# See kernel-img.conf(5) for details\n";



-- Package-specific info:
** Version:
Linux version 2.6.30-1-amd64 (Debian 2.6.30-5) (m...@debian.org) (gcc version 
4.3.3 (Debian 4.3.3-5) ) #1 SMP Mon Aug 3 12:28:22 UTC 2009


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable-i386
  APT policy: (500, 'unstable-i386'), (500, 'transitional-i386'), (500, 
'transitional'), (500, 'testing-i386'), (500, 'stable-i386'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental-i386'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages linux-image-2.6.30-1-amd64 depends on:
ii  debconf [debconf-2.0] 1.5.27 Debian configuration management sy
ii  initramfs-tools [linux-initra 0.93.4 tools for generating an initramfs
ii  module-init-tools 3.9-2  tools for managing Linux kernel mo

linux-image-2.6.30-1-amd64 recommends no packages.

Versions of packages linux-image-2.6.30-1-amd64 suggests:
ii  grub  0.97-55GRand Unified Bootloader (dummy pa
ii  grub-legacy [grub]0.97-55GRand Unified Bootloader (Legacy v
pn  linux-doc-2.6.30   (no description available)

-- 
Emmanuel LACOUR - elac...@home-dn.net


--- End Message ---
--- Begin Message ---
Source: linux-2.6
Source-Version: 2.6.32-9

We believe that the bug you reported is fixed in the latest version of
linux-2.6, which is due to be installed in the Debian FTP archive:

firmware-linux-free_2.6.32-9_all.deb
  to main/l/linux-2.6/firmware-linux-free_2.6.32-9_all.deb
linux-2.6_2.6.32-9.diff.gz
  to main/l/linux-2.6/linux-2.6_2.6.32-9.diff.gz
linux-2.6_2.6.32-9.dsc
  to main/l/linux-2.6/linux-2.6_2.6.32-9.dsc
linux-doc-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-9_all.deb
linux-headers-2.6.32-3-all-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-all-amd64_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-all_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-all_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-amd64_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-common-vserver_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-common-vserver_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-common_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-common_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb
linux-image-2.6.32-3-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-3-amd64_2.6.32-9_amd64.deb
linux-image-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb
linux-libc-dev_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-libc-dev_2.6.32-9_amd64.deb
linux-manual-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-9_all.deb
linux-patch-debian-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-9_all.deb
linux-source-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-source-2.6.32_2.6.32-9_all.deb
linux-support-2.6.32-3_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-support-2.6.32-3_2.6.32-9_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 542...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
maximilian attems  (supplier of updated linux-2.6 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
admi

Bug#568903: marked as done (Enable USB/IP staging drivers)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2010 04:51:55 +
with message-id 
and subject line Bug#568903: fixed in linux-2.6 2.6.32-9
has caused the Debian Bug report #568903,
regarding Enable USB/IP staging drivers
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.)


-- 
568903: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568903
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Severity: wishlist

Please consider including the USB/IP drivers from the
staging directory:

CONFIG_USB_IP_COMMON=m
CONFIG_USB_IP_VHCI_HCD=m
CONFIG_USB_IP_HOST=m

As I understand, the drivers remain in staging not so much
because of quality issues but due to discussions about the
userspace API, which may still change.

The only users of the API which exist today are the usbip 
userspace tools through libusbip0. It should be possible to
adapt those if/when the API changes.

If these modules were provided in linux-2.6, we could drop
the usbip-source module package.

Max


--- End Message ---
--- Begin Message ---
Source: linux-2.6
Source-Version: 2.6.32-9

We believe that the bug you reported is fixed in the latest version of
linux-2.6, which is due to be installed in the Debian FTP archive:

firmware-linux-free_2.6.32-9_all.deb
  to main/l/linux-2.6/firmware-linux-free_2.6.32-9_all.deb
linux-2.6_2.6.32-9.diff.gz
  to main/l/linux-2.6/linux-2.6_2.6.32-9.diff.gz
linux-2.6_2.6.32-9.dsc
  to main/l/linux-2.6/linux-2.6_2.6.32-9.dsc
linux-doc-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-9_all.deb
linux-headers-2.6.32-3-all-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-all-amd64_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-all_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-all_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-amd64_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-common-vserver_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-common-vserver_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-common_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-common_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb
linux-image-2.6.32-3-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-3-amd64_2.6.32-9_amd64.deb
linux-image-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb
linux-libc-dev_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-libc-dev_2.6.32-9_amd64.deb
linux-manual-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-9_all.deb
linux-patch-debian-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-9_all.deb
linux-source-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-source-2.6.32_2.6.32-9_all.deb
linux-support-2.6.32-3_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-support-2.6.32-3_2.6.32-9_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 568...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
maximilian attems  (supplier of updated linux-2.6 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 24 Feb 2010 17:06:27 +0100
Source: linux-2.6
Binary: linux-source-2.6.32 linux-doc-2.6.32 linux-manual-2.6.32 
linux-patch-debian-2.6.32 firmware-linux-free linux-support-2.6.32-3 linux-base 
linux-libc-dev linux-headers-2.6.32-3-all linux-headers-2.6.32-3-all-alpha 
linux-headers-2.6.32-3-common linux-image-2.6.32-3-alpha-generic 
linux-headers-2.6.32-3-alpha-generic linux-image-2.6.32-3-alpha-smp 
linux-headers-2.6.32-3-alpha-smp linux-image-2.6.32-3-alpha-legacy 
linux-headers-2.6.32-3-alpha-legacy linux-headers-2.6.32-3-all-amd64 
linux-image-2.6.32-3-amd64 linux-headers-2.6.32-3-amd64 
linux-headers-2.6.32-3-common-vserver linux-image-2.6.32-3-vserver-amd64 
linux-headers-2.6.32-3-vserver-amd64 linux-headers-2.6.32-3-all-armel 
linux-image-2.6.32-3-iop32x linux-headers-2.6.32-3-iop32x 
linux-image-2.6.32-3-ixp4xx linux-headers-2.6.32-3-ixp4xx 
linux-image-2.6.32-3-kirkwood linux-headers-2.6.32-3-kir

Bug#567747: marked as done (KMS/i945 fails to find LVDS)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2010 04:51:55 +
with message-id 
and subject line Bug#569314: fixed in linux-2.6 2.6.32-9
has caused the Debian Bug report #569314,
regarding KMS/i945 fails to find LVDS
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.)


-- 
569314: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=569314
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xserver-xorg-video-intel
Version: 2:2.9.1-2
Severity: important

Today after upgrade to version 2:2.9.1-2 and reboot when start X all system 
lock up. I don't know if also upgrade xserver-xorg cause the problem.

-- Package-specific info:
/var/lib/x11/X.roster does not exist.

/var/lib/x11/X.md5sum does not exist.

X server symlink status:
lrwxrwxrwx 1 root root 13 Jan 23 21:09 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 1710344 Jan 20 17:01 /usr/bin/Xorg

/var/lib/x11/xorg.conf.roster does not exist.

VGA-compatible devices on PCI bus:
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 
943/940GML Express Integrated Graphics Controller (rev 03)

/etc/X11/xorg.conf does not exist.

Xorg X server log files on system:
-rw-r--r-- 1 root root 8851 Jan 29 09:18 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file
/var/log/Xorg.0.log:

X.Org X Server 1.7.4
Release Date: 2010-01-08
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.32-trunk-686 i686 Debian
Current Operating System: Linux antares 2.6.32-trunk-686 #1 SMP Sun Jan 10 
06:32:16 UTC 2010 i686
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-trunk-686 
root=UUID=0b37cf53-e58e-4842-b547-a18799b62814 ro quiet
Build Date: 20 January 2010  10:52:55PM
xorg-server 2:1.7.4-2 (bgog...@debian.org) 
Current version of pixman: 0.16.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Jan 29 09:18:42 2010
(II) Loader magic: 0x81e7680
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 6.0
X.Org XInput driver : 7.0
X.Org Server Extension : 2.0
(++) using VT number 7

(--) PCI:*(0:0:2:0) 8086:27a2:103c:30b2 Intel Corporation Mobile 945GM/GMS, 
943/940GML Express Integrated Graphics Controller rev 3, Mem @ 
0xd420/524288, 0xc000/268435456, 0xd430/262144, I/O @ 0x1800/8
(--) PCI: (0:0:2:1) 8086:27a6:103c:30b2 Intel Corporation Mobile 945GM/GMS/GME, 
943/940GML Express Integrated Graphics Controller rev 3, Mem @ 0xd428/524288
(==) Using default built-in configuration (30 lines)
(==) --- Start of built-in configuration ---
Section "Device"
Identifier  "Builtin Default intel Device 0"
Driver  "intel"
EndSection
Section "Screen"
Identifier  "Builtin Default intel Screen 0"
Device  "Builtin Default intel Device 0"
EndSection
Section "Device"
Identifier  "Builtin Default vesa Device 0"
Driver  "vesa"
EndSection
Section "Screen"
Identifier  "Builtin Default vesa Screen 0"
Device  "Builtin Default vesa Device 0"
EndSection
Section "Device"
Identifier  "Builtin Default fbdev Device 0"
Driver  "fbdev"
EndSection
Section "Screen"
Identifier  "Builtin Default fbdev Screen 0"
Device  "Builtin Default fbdev Device 0"
EndSection
Section "ServerLayout"
Identifier  "Builtin Default Layout"
Screen  "Builtin Default intel Screen 0"
Screen  "Builtin Default vesa Screen 0"
Screen  "Builtin Default fbdev Screen 0"
EndSection
(==) --- End of built-in configuration ---
(==) ServerLayout "Builtin Default Layout"
(**) |-->Screen "Builtin Default intel Screen 0" (0)
(**) |   |-->Monitor ""
(**) |   |-->Device "Builtin Default intel Device 0"
(==) No monitor specified for screen "Builtin Default intel Screen 0".
Using a default monitor configuration.
(**) |-->Screen "Builtin Default vesa Screen 0" (1)
(**) |   |-->Monitor ""
(**) |   |-->Device "Builtin Default vesa Device 0"
(==) No monitor specified for screen "Builtin Default vesa Screen 0".
Using a default mon

Bug#569725: marked as done (reportbug data collection failure due to include-usb)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2010 04:51:55 +
with message-id 
and subject line Bug#569725: fixed in linux-2.6 2.6.32-9
has caused the Debian Bug report #569725,
regarding reportbug data collection failure due to include-usb
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.)


-- 
569725: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=569725
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: linux-2.6
Version: 2.6.32-8
Severity: minor

Coin,

When filing a BR on the kernel using reportbug, i was asked whether i  
wanted to continue sending the report or not after the  
'/usr/share/bug/linux-image-2.6.32-2-amd64/script' script failed with  
error code 256.


After a few tests, i found the culprit is 'include-usb', because the  
lsusb command does not always return 0, even when nothing goes wrong.  
In fact, the reason is in the lsusb manpage:

  RETURN VALUE
   If the specified device is not found, a non-zero exit code is returned.
and there is no USB available on this host ('/dev/bus/usb' does not  
even exist).


Regards.

--
Marc Dequènes (Duck)


pgp9WcUrtqHPE.pgp
Description: PGP Digital Signature
--- End Message ---
--- Begin Message ---
Source: linux-2.6
Source-Version: 2.6.32-9

We believe that the bug you reported is fixed in the latest version of
linux-2.6, which is due to be installed in the Debian FTP archive:

firmware-linux-free_2.6.32-9_all.deb
  to main/l/linux-2.6/firmware-linux-free_2.6.32-9_all.deb
linux-2.6_2.6.32-9.diff.gz
  to main/l/linux-2.6/linux-2.6_2.6.32-9.diff.gz
linux-2.6_2.6.32-9.dsc
  to main/l/linux-2.6/linux-2.6_2.6.32-9.dsc
linux-doc-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-9_all.deb
linux-headers-2.6.32-3-all-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-all-amd64_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-all_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-all_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-amd64_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-common-vserver_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-common-vserver_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-common_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-common_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb
linux-image-2.6.32-3-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-3-amd64_2.6.32-9_amd64.deb
linux-image-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb
linux-libc-dev_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-libc-dev_2.6.32-9_amd64.deb
linux-manual-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-9_all.deb
linux-patch-debian-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-9_all.deb
linux-source-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-source-2.6.32_2.6.32-9_all.deb
linux-support-2.6.32-3_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-support-2.6.32-3_2.6.32-9_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 569...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
maximilian attems  (supplier of updated linux-2.6 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 24 Feb 2010 17:06:27 +0100
Source: linux-2.6
Binary: linux-source-2.6.32 linux-doc-2.6.32 linux-manual-2.6.32 
linux-patch-debian-2.6.32 firmware-linux-free linux-support-2.6.32-3 linux-base 
linux-libc-dev linux-headers-2.6.32-3-all linux-headers-2.6.32-3-all-alpha 
linux-headers-2.6.32-3-common linux-image-2.6.32-3-alpha-generic 
linux-headers-2.6.32-3-alpha-generic linux-image-2.6.32-3-alpha-smp 
linux-headers-2.6.32-3-alpha-smp linux-image-2.6.32-3-alpha-legacy 
linux-headers-2.6.32-3-alpha-legacy linux-headers-2.6.32-3-all-amd64 
linux-image-2.6.32-3-amd64 linux-headers-2.6.32-3-amd64 
linux-headers-2.6.32-3-common-vserver linux-image-2.6.32-3-vserver-amd64 
linux-headers-2.6.32-3-vserver-amd64 linux-headers-2.6.32-3-all-armel 
linux-image-2.6.32-

Bug#559037: marked as done (radeon DRI driver corrupts memory)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2010 04:51:54 +
with message-id 
and subject line Bug#550562: fixed in linux-2.6 2.6.32-9
has caused the Debian Bug report #550562,
regarding radeon DRI driver corrupts memory
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.)


-- 
550562: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550562
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-games
Version: 1:2.28.1-1
Severity: critical
Justification: breaks the whole system

Upon starting Gnome Solitaire Games, a window frame very briefly appears and
then immediately terminates. Initially, it appears as if just the application
has terminated. But after that, no other program or command will run but cause
a segmentation fault. Shutdown is not possible any more, init also fails.


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.30-6-p4pe (PREEMPT)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages gnome-games depends on:
ii  ggzcore-bin0.0.14.1-1GGZ Gaming Zone: various command-l
ii  gnome-games-data   1:2.28.1-1data files for the GNOME games
ii  gnuchess   5.07-6Plays a game of chess, either agai
ii  guile-1.8-libs 1.8.7+1-2 Main Guile libraries
ii  libatk1.0-01.28.0-1  The ATK accessibility toolkit
ii  libc6  2.10.1-7  GNU C Library: Shared libraries
ii  libcairo2  1.8.8-2   The Cairo 2D vector graphics libra
ii  libcanberra-gtk0   0.22-1Gtk+ helper for playing widget eve
ii  libcanberra0   0.22-1a simple abstract interface for pl
ii  libclutter-1.0-0   1.0.6-1   Open GL based interactive canvas l
ii  libclutter-gtk-0.10-0  0.10.2-1  Open GL based interactive canvas l
ii  libgcc11:4.4.2-3 GCC support library
ii  libgconf2-42.28.0-1  GNOME configuration database syste
ii  libggz20.0.14.1-1GGZ Gaming Zone: common utilities 
ii  libggzcore90.0.14.1-1GGZ Gaming Zone: core client front
ii  libggzmod4 0.0.14.1-1GGZ Gaming Zone: game frontend lib
ii  libglib2.0-0   2.22.2-2  The GLib library of C routines
ii  libgtk2.0-02.18.3-1  The GTK+ graphical user interface 
ii  libice62:1.0.5-1 X11 Inter-Client Exchange library
ii  libpango1.0-0  1.26.0-1  Layout and rendering of internatio
ii  librsvg2-2 2.26.0-1  SAX-based renderer library for SVG
ii  librsvg2-common2.26.0-1  SAX-based renderer library for SVG
ii  libsm6 2:1.1.1-1 X11 Session Management library
ii  libstdc++6 4.4.2-3   The GNU Standard C++ Library v3
ii  libx11-6   2:1.2.2-1 X11 client-side library
ii  libxml22.7.6.dfsg-1  GNOME XML library
ii  mesa-utils 7.6-1 Miscellaneous Mesa GL utilities
ii  python 2.5.4-2   An interactive high-level object-o
ii  python-bugbuddy2.26.0-1  Python module for bug-buddy
ii  python-gconf   2.28.0-1  Python bindings for the GConf conf
ii  python-gtk22.16.0-1  Python bindings for the GTK+ widge
ii  python-gtkglext1   1.1.0-3.1 GtkGLext python bindings
ii  python-opengl  3.0.0~c1-1Python bindings to OpenGL
ii  zlib1g 1:1.2.3.3.dfsg-15 compression library - runtime

Versions of packages gnome-games recommends:
ii  gnome-games-extra-data2.28.0-1   games for the GNOME desktop (extra
ii  gvfs  1.4.1-5userspace virtual filesystem - ser

Versions of packages gnome-games suggests:
pn  gnome-hearts   (no description available)

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: linux-2.6
Source-Version: 2.6.32-9

We believe that the bug you reported is fixed in the latest version of
linux-2.6, which is due to be installed in the Debian FTP archive:

firmware-linux-free_2.6.32-9_all.deb
  to main/l/linux-2.6/firmware-linux-free_2.6.32-9_all.deb
linux-2.6_2.6.32-9.diff.gz
  to main/l/linux-2.6/linux-2.6_2.6.32-9.diff.gz
linux-2.6_2.6.32-9.dsc
  to main/l/linux-2.6/linux-2.6_2.6.32-9.dsc
linux-doc-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-doc-2.

Bug#567747: marked as done (KMS/i945 fails to find LVDS)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2010 04:51:55 +
with message-id 
and subject line Bug#567747: fixed in linux-2.6 2.6.32-9
has caused the Debian Bug report #567747,
regarding KMS/i945 fails to find LVDS
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.)


-- 
567747: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567747
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xserver-xorg-video-intel
Version: 2:2.9.1-2
Severity: important

Today after upgrade to version 2:2.9.1-2 and reboot when start X all system 
lock up. I don't know if also upgrade xserver-xorg cause the problem.

-- Package-specific info:
/var/lib/x11/X.roster does not exist.

/var/lib/x11/X.md5sum does not exist.

X server symlink status:
lrwxrwxrwx 1 root root 13 Jan 23 21:09 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 1710344 Jan 20 17:01 /usr/bin/Xorg

/var/lib/x11/xorg.conf.roster does not exist.

VGA-compatible devices on PCI bus:
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 
943/940GML Express Integrated Graphics Controller (rev 03)

/etc/X11/xorg.conf does not exist.

Xorg X server log files on system:
-rw-r--r-- 1 root root 8851 Jan 29 09:18 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file
/var/log/Xorg.0.log:

X.Org X Server 1.7.4
Release Date: 2010-01-08
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.32-trunk-686 i686 Debian
Current Operating System: Linux antares 2.6.32-trunk-686 #1 SMP Sun Jan 10 
06:32:16 UTC 2010 i686
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-trunk-686 
root=UUID=0b37cf53-e58e-4842-b547-a18799b62814 ro quiet
Build Date: 20 January 2010  10:52:55PM
xorg-server 2:1.7.4-2 (bgog...@debian.org) 
Current version of pixman: 0.16.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Jan 29 09:18:42 2010
(II) Loader magic: 0x81e7680
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 6.0
X.Org XInput driver : 7.0
X.Org Server Extension : 2.0
(++) using VT number 7

(--) PCI:*(0:0:2:0) 8086:27a2:103c:30b2 Intel Corporation Mobile 945GM/GMS, 
943/940GML Express Integrated Graphics Controller rev 3, Mem @ 
0xd420/524288, 0xc000/268435456, 0xd430/262144, I/O @ 0x1800/8
(--) PCI: (0:0:2:1) 8086:27a6:103c:30b2 Intel Corporation Mobile 945GM/GMS/GME, 
943/940GML Express Integrated Graphics Controller rev 3, Mem @ 0xd428/524288
(==) Using default built-in configuration (30 lines)
(==) --- Start of built-in configuration ---
Section "Device"
Identifier  "Builtin Default intel Device 0"
Driver  "intel"
EndSection
Section "Screen"
Identifier  "Builtin Default intel Screen 0"
Device  "Builtin Default intel Device 0"
EndSection
Section "Device"
Identifier  "Builtin Default vesa Device 0"
Driver  "vesa"
EndSection
Section "Screen"
Identifier  "Builtin Default vesa Screen 0"
Device  "Builtin Default vesa Device 0"
EndSection
Section "Device"
Identifier  "Builtin Default fbdev Device 0"
Driver  "fbdev"
EndSection
Section "Screen"
Identifier  "Builtin Default fbdev Screen 0"
Device  "Builtin Default fbdev Device 0"
EndSection
Section "ServerLayout"
Identifier  "Builtin Default Layout"
Screen  "Builtin Default intel Screen 0"
Screen  "Builtin Default vesa Screen 0"
Screen  "Builtin Default fbdev Screen 0"
EndSection
(==) --- End of built-in configuration ---
(==) ServerLayout "Builtin Default Layout"
(**) |-->Screen "Builtin Default intel Screen 0" (0)
(**) |   |-->Monitor ""
(**) |   |-->Device "Builtin Default intel Device 0"
(==) No monitor specified for screen "Builtin Default intel Screen 0".
Using a default monitor configuration.
(**) |-->Screen "Builtin Default vesa Screen 0" (1)
(**) |   |-->Monitor ""
(**) |   |-->Device "Builtin Default vesa Device 0"
(==) No monitor specified for screen "Builtin Default vesa Screen 0".
Using a default mon

Bug#570407: marked as done (ubifs errors on OpenRD)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2010 04:51:55 +
with message-id 
and subject line Bug#570407: fixed in linux-2.6 2.6.32-9
has caused the Debian Bug report #570407,
regarding ubifs errors on OpenRD
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.)


-- 
570407: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570407
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 2.6.32-5

Gert Doering reports ubifs errors on the OpenRD:

- Forwarded message from GertDoering -

Date: Wed, 10 Feb 2010 12:42:30 -0800 (PST)
To: OpenRD 

[...]

If I boot the Debian kernel, ubifs complains about write errors and
mounts the file system read-only:

[   27.235020] UBI error: ubi_io_write: error -5 while writing 512
bytes to PEB 2779:512, written 0 bytes
[   27.244537] UBI warning: ubi_eba_write_leb: failed to write VID
header to LEB 0:10, PEB 2779
[   27.256411] UBI: try another PEB
[   27.260170] UBI: run torture test for PEB 2779
[   27.264695] UBI error: ubi_io_write: error -5 while writing 512
bytes to PEB 2780:512, written 0 bytes
[   27.274062] UBI warning: ubi_eba_write_leb: failed to write VID
header to LEB 0:10, PEB 2780
[   27.311521] UBI: try another PEB
[   27.687329] UBI: PEB 2779 passed torture test, do not mark it a bad

... which is weird.

Anyway, I'm making progress...

gert

- End forwarded message -

-- 
Martin Michlmayr
http://www.cyrius.com/


--- End Message ---
--- Begin Message ---
Source: linux-2.6
Source-Version: 2.6.32-9

We believe that the bug you reported is fixed in the latest version of
linux-2.6, which is due to be installed in the Debian FTP archive:

firmware-linux-free_2.6.32-9_all.deb
  to main/l/linux-2.6/firmware-linux-free_2.6.32-9_all.deb
linux-2.6_2.6.32-9.diff.gz
  to main/l/linux-2.6/linux-2.6_2.6.32-9.diff.gz
linux-2.6_2.6.32-9.dsc
  to main/l/linux-2.6/linux-2.6_2.6.32-9.dsc
linux-doc-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-9_all.deb
linux-headers-2.6.32-3-all-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-all-amd64_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-all_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-all_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-amd64_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-common-vserver_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-common-vserver_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-common_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-common_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb
linux-image-2.6.32-3-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-3-amd64_2.6.32-9_amd64.deb
linux-image-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb
linux-libc-dev_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-libc-dev_2.6.32-9_amd64.deb
linux-manual-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-9_all.deb
linux-patch-debian-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-9_all.deb
linux-source-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-source-2.6.32_2.6.32-9_all.deb
linux-support-2.6.32-3_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-support-2.6.32-3_2.6.32-9_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 570...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
maximilian attems  (supplier of updated linux-2.6 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 24 Feb 2010 17:06:27 +0100
Source: linux-2.6
Binary: linux-source-2.6.32 linux-doc-2.6.32 linux-manual-2.6.32 
linux-patch-debian-2.6.32 firmware-linux-free linux-support-2.6.32-3 linux-base 
linux-libc-dev linux-headers-2.6.32-3-all linux-headers-2.6.32-3-all-alpha 
linux-headers-2.6.32-3-common linux-image-2.6.32-3-alpha-generic 
linux-headers-2.6.32-3-alpha-generic linux-image-2.6.32-3-alpha-smp 
linux-headers-2.6.32-3-alpha-smp linux-image-2.6.32-3-alpha-legacy 
linux-headers-2.6

Bug#568756: marked as done (please backport VEPA support for macvlan)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2010 04:51:55 +
with message-id 
and subject line Bug#568756: fixed in linux-2.6 2.6.32-9
has caused the Debian Bug report #568756,
regarding please backport VEPA support for macvlan
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.)


-- 
568756: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568756
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Severity: normal
Tags: patch

This will become very useful for some virtualization setups.

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=618e1b7482f7a8a4c6c6e8ccbe140e4c331df4e9

-- 
ciao,
Marco


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: linux-2.6
Source-Version: 2.6.32-9

We believe that the bug you reported is fixed in the latest version of
linux-2.6, which is due to be installed in the Debian FTP archive:

firmware-linux-free_2.6.32-9_all.deb
  to main/l/linux-2.6/firmware-linux-free_2.6.32-9_all.deb
linux-2.6_2.6.32-9.diff.gz
  to main/l/linux-2.6/linux-2.6_2.6.32-9.diff.gz
linux-2.6_2.6.32-9.dsc
  to main/l/linux-2.6/linux-2.6_2.6.32-9.dsc
linux-doc-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-9_all.deb
linux-headers-2.6.32-3-all-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-all-amd64_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-all_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-all_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-amd64_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-common-vserver_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-common-vserver_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-common_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-common_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb
linux-image-2.6.32-3-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-3-amd64_2.6.32-9_amd64.deb
linux-image-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb
linux-libc-dev_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-libc-dev_2.6.32-9_amd64.deb
linux-manual-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-9_all.deb
linux-patch-debian-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-9_all.deb
linux-source-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-source-2.6.32_2.6.32-9_all.deb
linux-support-2.6.32-3_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-support-2.6.32-3_2.6.32-9_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 568...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
maximilian attems  (supplier of updated linux-2.6 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 24 Feb 2010 17:06:27 +0100
Source: linux-2.6
Binary: linux-source-2.6.32 linux-doc-2.6.32 linux-manual-2.6.32 
linux-patch-debian-2.6.32 firmware-linux-free linux-support-2.6.32-3 linux-base 
linux-libc-dev linux-headers-2.6.32-3-all linux-headers-2.6.32-3-all-alpha 
linux-headers-2.6.32-3-common linux-image-2.6.32-3-alpha-generic 
linux-headers-2.6.32-3-alpha-generic linux-image-2.6.32-3-alpha-smp 
linux-headers-2.6.32-3-alpha-smp linux-image-2.6.32-3-alpha-legacy 
linux-headers-2.6.32-3-alpha-legacy linux-headers-2.6.32-3-all-amd64 
linux-image-2.6.32-3-amd64 linux-headers-2.6.32-3-amd64 
linux-headers-2.6.32-3-common-vserver linux-image-2.6.32-3-vserver-amd64 
linux-headers-2.6.32-3-vserver-amd64 linux-headers-2.6.32-3-all-armel 
linux-image-2.6.32-3-iop32x linux-headers-2.6.32-3-iop32x 
linux-image-2.6.32-3-ixp4xx linux-headers-2.6.32-3-ixp4xx 
linux-image-2.6.32-3-kirkwood linux-headers-2.6.32-3-kirkwood 
linux-image-2.6.32-3-orion5x linux-headers-2.6.32-3-orion5x 
linux-image-2.6.32-3-versatile linux-headers-2.6.32-3-versatile
 linux-headers-2.6.32-3-all-hppa linux-image-2.6.32-3-parisc 
linux-headers-2.6.32-3-parisc linux-image-2.6.32-3-parisc-smp 
linux-headers-2.6.32-3-parisc-smp linux-i

Bug#571266: marked as done (linux-image-2.6.26-2-486: boot 486 kernel fails with root=LABEL=)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2010 04:47:09 +
with message-id <1267073229.24602.156.ca...@localhost>
and subject line Re: Bug#571266: linux-image-2.6.26-2-486: boot 486 kernel 
fails with root=LABEL=
has caused the Debian Bug report #571266,
regarding linux-image-2.6.26-2-486: boot 486 kernel fails with root=LABEL=
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.)


-- 
571266: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571266
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.26-2-486
Version: 2.6.26-21lenny3
Severity: important

In grub.conf,

   If I use root=/dev/hda3 my systems boots up and runs.
   If I use root=LABEL=/Lenny the system hangs on boot.


-- System Information:
Debian Release: 5.0.4
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i586)

Kernel: Linux 2.6.26-2-486
Locale: LANG=en_US.UTF-8, LC_CTYPE=C (charmap=locale: Cannot set LC_MESSAGES to 
default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.26-2-486 depends on:
ii  debconf [debconf-2.0] 1.5.24 Debian configuration management sy
ii  initramfs-tools [linux-initra 0.92o  tools for generating an initramfs
ii  module-init-tools 3.4-1  tools for managing Linux kernel mo

linux-image-2.6.26-2-486 recommends no packages.

Versions of packages linux-image-2.6.26-2-486 suggests:
ii  grub   0.97-47lenny2 GRand Unified Bootloader (Legacy v
pn  linux-doc-2.6.26   (no description available)

-- debconf information:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_CTYPE = "C",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.26-2-486/postinst/depmod-error-2.6.26-2-486: false
  linux-image-2.6.26-2-486/preinst/initrd-2.6.26-2-486:
  linux-image-2.6.26-2-486/preinst/abort-install-2.6.26-2-486:
  linux-image-2.6.26-2-486/preinst/lilo-has-ramdisk:
  linux-image-2.6.26-2-486/preinst/lilo-initrd-2.6.26-2-486: true
* linux-image-2.6.26-2-486/postinst/create-kimage-link-2.6.26-2-486: true
  linux-image-2.6.26-2-486/preinst/elilo-initrd-2.6.26-2-486: true
  linux-image-2.6.26-2-486/postinst/bootloader-error-2.6.26-2-486:
  linux-image-2.6.26-2-486/preinst/overwriting-modules-2.6.26-2-486: true
  linux-image-2.6.26-2-486/postinst/old-system-map-link-2.6.26-2-486: true
  linux-image-2.6.26-2-486/prerm/removing-running-kernel-2.6.26-2-486: true
  linux-image-2.6.26-2-486/postinst/bootloader-test-error-2.6.26-2-486:
  linux-image-2.6.26-2-486/prerm/would-invalidate-boot-loader-2.6.26-2-486: true
  linux-image-2.6.26-2-486/preinst/failed-to-move-modules-2.6.26-2-486:
* linux-image-2.6.26-2-486/preinst/bootloader-initrd-2.6.26-2-486: true
  linux-image-2.6.26-2-486/preinst/abort-overwrite-2.6.26-2-486:
  linux-image-2.6.26-2-486/postinst/old-initrd-link-2.6.26-2-486: true
  linux-image-2.6.26-2-486/postinst/old-dir-initrd-link-2.6.26-2-486: true
  linux-image-2.6.26-2-486/postinst/kimage-is-a-directory:
  linux-image-2.6.26-2-486/postinst/depmod-error-initrd-2.6.26-2-486: false


--- End Message ---
--- Begin Message ---
On Wed, 2010-02-24 at 19:08 -0800, William Estrada wrote:
> Ben,
> 
>   Here is the messages just prior to the hang:
> > [   20.352999] usb usb1: New USB device found, idVendor=1d6b, 
> idProduct=0001
> > [   20.359059] usb usb1: New USB device strings: Mfr=3, Product=2, 
> SerialNumber=1
> > [   20.366678] usb usb1: Product: OHCI Host Controller
> > [   20.369285] usb usb1: Manufacturer: Linux 2.6.26-2-486 ohci_hcd
> > [   20.371163] usb usb1: SerialNumber: :00:13.0
> > [   20.688931] Uniform Multi-Platform E-IDE driver
> > [   20.695085] ide: Assuming 33MHz system bus speed for PIO modes; 
> override with idebus=xx
> > [   20.962297] SC1200: IDE controller (0x100b:0x0502 rev 0x01) at  
> PCI slot :00:12.2
> > [   20.967159] SC1200: not 100% native mode: will probe irqs later
> > [   20.974144] ide0: BM-DMA at 0xe000-0xe007
> > [   20.978144] ide1: BM-DMA at 0

linux-2.6_2.6.32-9_amd64.changes ACCEPTED

[Archive Administrator]

Accepted:
firmware-linux-free_2.6.32-9_all.deb
  to main/l/linux-2.6/firmware-linux-free_2.6.32-9_all.deb
linux-2.6_2.6.32-9.diff.gz
  to main/l/linux-2.6/linux-2.6_2.6.32-9.diff.gz
linux-2.6_2.6.32-9.dsc
  to main/l/linux-2.6/linux-2.6_2.6.32-9.dsc
linux-doc-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-9_all.deb
linux-headers-2.6.32-3-all-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-all-amd64_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-all_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-all_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-amd64_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-common-vserver_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-common-vserver_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-common_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-common_2.6.32-9_amd64.deb
linux-headers-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-headers-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb
linux-image-2.6.32-3-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-3-amd64_2.6.32-9_amd64.deb
linux-image-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-image-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb
linux-libc-dev_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-libc-dev_2.6.32-9_amd64.deb
linux-manual-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-9_all.deb
linux-patch-debian-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-9_all.deb
linux-source-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-source-2.6.32_2.6.32-9_all.deb
linux-support-2.6.32-3_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-support-2.6.32-3_2.6.32-9_all.deb


Override entries for your package:
firmware-linux-free_2.6.32-9_all.deb - optional kernel
linux-2.6_2.6.32-9.dsc - source devel
linux-doc-2.6.32_2.6.32-9_all.deb - optional doc
linux-headers-2.6.32-3-all-amd64_2.6.32-9_amd64.deb - optional kernel
linux-headers-2.6.32-3-all_2.6.32-9_amd64.deb - optional kernel
linux-headers-2.6.32-3-amd64_2.6.32-9_amd64.deb - optional kernel
linux-headers-2.6.32-3-common-vserver_2.6.32-9_amd64.deb - optional kernel
linux-headers-2.6.32-3-common_2.6.32-9_amd64.deb - optional kernel
linux-headers-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb - optional kernel
linux-image-2.6.32-3-amd64_2.6.32-9_amd64.deb - optional kernel
linux-image-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb - optional kernel
linux-libc-dev_2.6.32-9_amd64.deb - optional devel
linux-manual-2.6.32_2.6.32-9_all.deb - optional doc
linux-patch-debian-2.6.32_2.6.32-9_all.deb - optional kernel
linux-source-2.6.32_2.6.32-9_all.deb - optional kernel
linux-support-2.6.32-3_2.6.32-9_all.deb - optional devel

Announcing to debian-devel-chan...@lists.debian.org
Closing bugs: 503172 508108 542208 550562 566726 567747 568756 568903 569314 
569725 570407 571019 


Thank you for your contribution to Debian.


-- 
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/e1nkvha-0005ir...@ries.debian.org

Processed: tagging 444182

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # Automatically generated email from bts, devscripts version 2.10.35lenny7
> tags 444182 + pending
Bug #444182 [linux-2.6] linux-source-2.6.22: 
drivers-ata-ata_piix-postpone-pata.patch prevents my dvd writer to be detected
Bug #463833 [linux-2.6] SantaRosa PATA don't managed by ata_piix
Bug #535959 [linux-2.6] linux-2.6: Please enable libata for PATA/piix
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
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.126707111029792.transcr...@bugs.debian.org

Processed: reassign 299567 to oprofile

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 299567 oprofile
Bug #299567 [linux-2.6] kernel-image-2.6.8-2-686-smp: x86 has no uncompressed 
vmlinux (for oprofile)
Bug reassigned from package 'linux-2.6' to 'oprofile'.
Bug No longer marked as found in versions linux-2.6/2.6.30-3.
> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
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.126706871210348.transcr...@bugs.debian.org

Bug#569034: linux-2.6: Please support sh4 architecture

[Nobuhiro Iwamatsu]

Hi,

2010/2/25 Moritz Muehlenhoff :
> Hi,
>
> Nobuhiro Iwamatsu wrote:
>
>> I attached new patch.
>> Could you check ?
>
> | patches/bugfix/sh4/fix-decompress-output-addr.patch |   27 +
> | patches/debian/arch-sh4-fix-uimage-build.patch      |   10
>
> These patches aren't in current linux-2.6 git, have they been submitted
> upstream?

fix-decompress-output-addr.patch is already taken in by sh-2.6.
  
http://git.kernel.org/?p=linux/kernel/git/lethal/sh-2.6.git;a=commit;h=319c2cc761505ee54a9536c5d0b9c2ee3fb33866

arch-sh4-fix-uimage-build.patch is not bug in upstream.
Target board (sh7785lcr) of sh builds by default uImage. Because his
use u-boot for boot loader.
Therefore, I disable this function with this patch.

>
> | patches/bugfix/sh4/fix_pte_write.patch              |   45 ++
>
> This has been merged into 2.6.32.9, which has been pulled
> into the linux-2.6 in the mean time, please respin your patch.

Yes. I update patch and attached.

Best regards,
  Nobuhiro

-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6


0001-Add-support-sh4-v3.patch
Description: application/empty

Processed: tagging 571266

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 571266 moreinfo
Bug #571266 [linux-image-2.6.26-2-486] linux-image-2.6.26-2-486: boot 486 
kernel fails with root=LABEL=
Added tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
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.126706107314243.transcr...@bugs.debian.org

Bug#571266: linux-image-2.6.26-2-486: boot 486 kernel fails with root=LABEL=

[Ben Hutchings]

On Wed, 2010-02-24 at 12:51 -0800, william estrada wrote:
> Package: linux-image-2.6.26-2-486
> Version: 2.6.26-21lenny3
> Severity: important
> 
> In grub.conf,
> 
>If I use root=/dev/hda3 my systems boots up and runs.
>If I use root=LABEL=/Lenny the system hangs on boot.
[...]

We need to see the messages that are displayed in this case.

Ben.

-- 
Ben Hutchings
I say we take off; nuke the site from orbit.  It's the only way to be sure.


signature.asc
Description: This is a digitally signed message part

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 571253 uvcvideo mixer issues (with snd_mixer_oss)
Bug #571253 [aumix] aumix does not report/change settings correctly on 
additional devices
Changed Bug title to 'uvcvideo mixer issues (with snd_mixer_oss)' from 'aumix 
does not report/change settings correctly on additional devices'
> reassign 571253 linux-2.6
Bug #571253 [aumix] uvcvideo mixer issues (with snd_mixer_oss)
Bug reassigned from package 'aumix' to 'linux-2.6'.
Bug No longer marked as found in versions aumix/2.8-21.
> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
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.12670594096877.transcr...@bugs.debian.org

Bug#571242: linux-image-2.6.32-2-amd64: running 8 copies of bonnie deadlocks(?) in sync

[maximilian attems]

On Wed, Feb 24, 2010 at 11:00:17PM +, Ben Hutchings wrote:
> On Wed, Feb 24, 2010 at 05:02:41PM +0100, John Hughes wrote:
> > Package: linux-2.6
> > Version: 2.6.32-8
> > Severity: normal
> > 
> > 
> > Running 8 copies of bonnie++ on 8 different filesystems on 8 disks seems
> > to produce a deadlock in sync(2).
> > 
> > Initialy all the bonnie++ processes seem to be running ok, but after a while
> > only 2-3 of the disks are showing any I/O activiy and the dmesg output
> > shows:
> [...]
> 
> Please report this upstream at  under product
> 'File System', component 'VFS', and let us know the bug number.

if you can reproduce with 2.6.32-9, which currently is new,
prebuild uploaded packages are here:
http://charm.itp.tuwien.ac.at/~mattems/linux-image-2.6.32-3-amd64_2.6.32-9_amd64.deb
sha256sum signed
http://charm.itp.tuwien.ac.at/~mattems/linux-image-2.6.32-3-amd64_2.6.32-9_amd64.deb.sha256sum.asc



-- 
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/20100224230338.gn15...@baikonur.stro.at

Bug#571242: linux-image-2.6.32-2-amd64: running 8 copies of bonnie deadlocks(?) in sync

[Ben Hutchings]

On Wed, Feb 24, 2010 at 05:02:41PM +0100, John Hughes wrote:
> Package: linux-2.6
> Version: 2.6.32-8
> Severity: normal
> 
> 
> Running 8 copies of bonnie++ on 8 different filesystems on 8 disks seems
> to produce a deadlock in sync(2).
> 
> Initialy all the bonnie++ processes seem to be running ok, but after a while
> only 2-3 of the disks are showing any I/O activiy and the dmesg output
> shows:
[...]

Please report this upstream at  under product
'File System', component 'VFS', and let us know the bug number.

Ben.

-- 
Ben Hutchings
Tomorrow will be cancelled due to lack of interest.



-- 
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/20100224230016.ga21...@decadent.org.uk

Bug#568603: marked as done (linux-image-2.6.32-trunk-amd64: oops on startup: Kernel failure: EDAC amd64: WARNING: ECC is disabled by BIOS)

[Debian Bug Tracking System]

Your message dated Wed, 24 Feb 2010 23:53:53 +0100
with message-id <20100224225353.ga8...@galadriel.inutil.org>
and subject line Re: linux-image-2.6.32-trunk-amd64: Comfirmed and Fixed in 
Kernel Bug Tracker - Patch available - Please reopen.
has caused the Debian Bug report #568603,
regarding linux-image-2.6.32-trunk-amd64: oops on startup: Kernel failure: EDAC 
 amd64: WARNING: ECC is disabled by BIOS
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.)


-- 
568603: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568603
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 2.6.32-5
Severity: normal

Hi,

I just reinstall my distribution and change from x86 arch to amd64 arch.

On fist startup, when kde load is finished, a kernel oops is raised:
"
Kernel failure message 1: EDAC amd64: WARNING: ECC is disabled by BIOS.
Module will NOT be loaded. Either Enable ECC in the BIOS, or set
'ecc_enable_override'.
Also, use of the override can cause unknown side effects. amd64_edac: probe
of :00:18.2 failed with error -22 k8temp :00:18.3: Temperature
readouts might be wrong - check erratum #141
input: PC Speaker as /devices/platform/pcspkr/input/input5 parport_pc 00:0a:
reported by Plug and Play ACPI parport0: PC-style at 0x378, irq 7
[PCSPP,TRISTATE,EPP] i2c i2c-0: nForce2 SMBus adapter at 0x1c00 ACPI: I/O
resource nForce2_smbus [0x1c40-0x1c7f] conflicts with ACPI region SM00
[0x1c40-0x1c45]
ACPI: If an ACPI driver is available for this device, you should use it
instead of the native driver nForce2_smbus :00:01.1: Error probing SMB2.
ACPI: PCI Interrupt Link [AAZA] enabled at IRQ 20 HDA Intel :00:06.1:
PCI INT B -> Link[AAZA] -> GSI 20 (level, low) -> IRQ 20 HDA Intel
:00:06.1: setting latency timer to 64
input: HDA Digital PCBeep as /devices/pci:00/:00:06.1/input/input6
Adding 2650684k swap on /dev/sda5. Priority:-1 extents:1 across:2650684k
loop: module loaded EXT4-fs (sda3): mounted filesystem with ordered data
mode alloc irq_desc for 30 on node 0 alloc kstat_irqs on node 0 forcedeth
:00:08.0: irq 30 for MSI/MSI-X fuse init (API version 7.13)
powernow-k8: Found 1 AMD Athlon(tm) 64 X2 Dual Core Processor 5600+
processors (2 cpu cores) (version 2.20.00)
[Firmware Bug]: powernow-k8: No compatible ACPI _PSS objects found.
[Firmware Bug]: powernow-k8: Try again with latest BIOS.
"

I found the same problem on ubuntu bug tracker:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/422536 and it is seem
to be fixed.

I did not notice any visible consequences on the system yet.
Is there a risk of data loss or others serious consequences? (I hesitate to
reconnect and set up a raid1 soft on this system.)

Best regards,

Thomas PIERSON

(I join a kernel log)

-- Package-specific info:
** Version:
Linux version 2.6.32-trunk-amd64 (Debian 2.6.32-5) (b...@decadent.org.uk)
(gcc version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Sun Jan 10 22:40:40 UTC 2010

** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.32-trunk-amd64
root=UUID=c1d7fb62-3c1c-4f17-b8fe-7df24a4eb91f ro quiet

** Not tainted


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages linux-image-2.6.32-trunk-amd64 depends on:
ii  debconf [debconf-2.0] 1.5.28 Debian configuration management
sy
ii  initramfs-tools [linux-initra 0.93.4 tools for generating an
initramfs
ii  module-init-tools 3.11-1 tools for managing Linux kernel
mo

Versions of packages linux-image-2.6.32-trunk-amd64 recommends:
pn  firmware-linux-free(no description available)

Versions of packages linux-image-2.6.32-trunk-amd64 suggests:
pn  grub | lilo(no description available)
pn  linux-doc-2.6.32   (no description available)

Versions of packages linux-image-2.6.32-trunk-amd64 is related to:
pn  firmware-bnx2  (no description available)
pn  firmware-bnx2x (no description available)
pn  firmware-ipw2x00   (no description available)
pn  firmware-ivtv  (no description available)
pn  firmware-iwlwifi   (no description available)
pn  firmware-linux (no description available)
pn  firmware-linux-nonfree (no description available)
pn  firmware-qlogic(no description available)

Bug#567468: md homehost

[Neil Brown]

On Wed, 24 Feb 2010 14:41:16 +0100
Goswin von Brederlow  wrote:

> Neil Brown  writes:
> 
> > On Tue, 23 Feb 2010 07:27:00 +0100
> > martin f krafft  wrote:
> >> The only issue homehost protects against, I think, is machines that
> >> use /dev/md0 directly from grub.conf or fstab.
> >
> > That is exactly correct.  If no code or config file depends on a name like
> > /dev/mdX or /dev/md/foo, then you don't need to be concerned about the whole
> > homehost thing.
> > You can either mount by fs-uuid, or mount e.g.
> >/dev/disk/by-id/md-uuid-8fd0af3f:4fbb94ea:12cc2127:f9855db5 
> 
> What if you have two raids (one local, one from the other hosts that
> broke down) and both have LVM on it with /dev/vg/root?
> 
> Shouldn't it only assemble the local raid (as md0 or whatever) and then
> only start the local volume group? If it assembles the remote raid as
> /dev/md127 as well then lvm will have problems and the boot will likely
> (even randomly) go wrong since only one VG can be activated.
> 
> I think it is pretty common for admins to configure LVM to the same
> volume group name on different systems. So if you consider raids being
> pluged into other systems please keep this in mind.

You are entirely correct.  However lvm problems are not my problems.

It has always been my position that the best way to configure md is to
explicitly list your arrays in mdadm.conf.  But people seem to not like this
and want it to all be 'automatic'.  So I do my best to make it as automatic
as possible but still remove as many of the possible confusion that this can
cause as possible.  But I cannot remove them all.

If you move disks around and boot and lvm gets confused because there are two
things call "/dev/vg/root", then I'm sorry but there is nothing I can do
about that.  If you had an mdadm.conf which listed you md arrays, and had
   auto -all
then you can be sure that mdadm would not be contributing to this problem.

NeilBrown



-- 
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/20100225093018.12d3e...@notabene.brown

Bug#522592: marked as done (Problems with TULIP DAVICOM DM9102)

[Debian Bug Tracking System]

Your message dated Wed, 24 Feb 2010 23:50:45 +0100
with message-id <20100224225045.ga8...@galadriel.inutil.org>
and subject line Re: your mail
has caused the Debian Bug report #522592,
regarding Problems with TULIP DAVICOM DM9102
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.)


-- 
522592: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522592
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.26-1-686
Version: 2.6.26-13


Problems with Davicom Network Card, using DMFE and TULIP driver.


maxim...@maximiliano:~$ sudo mii-diag
Using the default interface 'eth0'.
Basic registers of MII PHY #1:  3100 7809 0181 b841 01e1   .
 Basic mode control register 0x3100: Auto-negotiation enabled.
 Basic mode status register 0x7809 ... 7809.
   Link status: not established.
   End of basic transceiver information.

maxim...@maximiliano:~$ sudo mii-tool
eth0: negotiated 100baseTx-FD, link ok
SIOCGMIIPHY on 'eth1' failed: Operation not supported



> [ 2707.147623] Linux Tulip driver version 1.1.15-NAPI (Feb 27, 2007)
> [ 2707.152789] tulip0:  MII transceiver #1 config 1000 status 7809
> advertising 01e1.
> [ 2707.158313] eth0: Davicom DM9102/DM9102A rev 64 at Port 0xac00,
> 00:08:a1:82:31:32, IRQ 16.
> [ 2716.13] NETDEV WATCHDOG: eth0: transmit timed out
> [ 2716.001374] :01:08.0: tulip_stop_rxtx() failed (CSR5 0xfc108100
> CSR6 0x20e)
>
> [ 5404.13] NETDEV WATCHDOG: eth0: transmit timed out
> [ 5404.001372] :01:08.0: tulip_stop_rxtx() failed (CSR5 0xfc12
> CSR6 0x20e)
> [ 5420.16] NETDEV WATCHDOG: eth0: transmit timed out
> [ 5420.001376] :01:08.0: tulip_stop_rxtx() failed (CSR5 0xfc12
> CSR6 0x20e)
>
>
> 01:08.0 Ethernet controller: Davicom Semiconductor, Inc. 21x4x
> DEC-Tulip compatible 10/100 Ethernet (rev 40)
> Subsystem: Device 3030:5032
> Flags: bus master, medium devsel, latency 32, IRQ 16
> I/O ports at ac00 [size=256]
> Memory at dfefe000 (32-bit, non-prefetchable) [size=256]
> [virtual] Expansion ROM at dfd0 [disabled] [size=256K]
> Capabilities: [50] Power Management version 2
> Kernel driver in use: tulip
> Kernel modules: dmfe, tulip
>
>
> maxim...@maximiliano:~$ sudo tulip-diag -aem
> tulip-diag.c:v2.18 11/12/2003 Donald Becker (bec...@scyld.com)
>  http://www.scyld.com/diag/index.html
> Index #1: Found a Davicom DM9102 adapter at 0xac00.
>  * A potential Tulip chip has been found, but it appears to be active.
>  * Either shutdown the network, or use the '-f' flag to see all values.
> Davicom DM9102 chip registers at 0xac00:
>  0x00: de00   2ffed000 2ffed800 fc12 020e2002
> ebef
>  Port selection is MII, half-duplex.
>  Transmit started, Receive started.
>   The Rx process state is 'Reading a Rx descriptor'.
>   The Tx process state is 'Reading a Tx descriptor'.
>   The transmit threshold is 128.
>
> cat /proc/interrupts
>  16:400   IO-APIC-fasteoi   eth0
>
> maxim...@maximiliano:~$ cat /proc/irq/16/spurious
> count 3
> unhandled 0
> last_unhandled 0 ms
>
> Linux Maximiliano 2.6.26-1-686 #1 SMP Sat Jan 10 18:29:31 UTC 2009
> i686 GNU/Linux
>
> maxim...@maximiliano:~$ sudo modinfo tulip
> filename:   /lib/modules/2.6.26-1-686/kernel/drivers/net/tulip/tulip.ko
> version:1.1.15-NAPI
> license:GPL
> description:Digital 21*4* Tulip ethernet driver
> author: The Linux Kernel Team
> srcversion: D7C7C035C1D0941EE9D11CC
> alias:  pci:v1414d0002sv*sd*bc*sc*i*
> alias:  pci:v14EAdAB08sv*sd*bc*sc*i*
> alias:  pci:v10B7d9300sv*sd*bc*sc*i*
> alias:  pci:v17B3dAB08sv*sd*bc*sc*i*
> alias:  pci:v1737dAB08sv*sd*bc*sc*i*
> alias:  pci:v1737dAB09sv*sd*bc*sc*i*
> alias:  pci:v1626d8410sv*sd*bc*sc*i*
> alias:  pci:v14F1d1803sv*sd*bc*sc*i*
> alias:  pci:v1186d1591sv*sd*bc*sc*i*
> alias:  pci:v1186d1561sv*sd*bc*sc*i*
> alias:  pci:v1186d1541sv*sd*bc*sc*i*
> alias:  pci:v1113d9511sv*sd*bc*sc*i*
> alias:  pci:v1113d1217sv*sd*bc*sc*i*
> alias:  pci:v1113d1216sv*sd*bc*sc*i*
> alias:  pci:v1282d9102sv*sd*bc*sc*i*
> alias:  pci:v1282d9100sv*sd*bc*sc*i*
> alias:  pci:v8086d0039sv*sd*bc*sc*i*
> alias:  pci:v11F6d9881sv*sd*bc*sc*i*
> alias:  pci:v1259dA120sv*sd*bc*sc*i*
> alias:  pci:v104Ad2774

Bug#567468: md homehost

[Neil Brown]

On Wed, 24 Feb 2010 18:52:57 +0100
"Mario 'BitKoenig' Holbe"  wrote:

> On Wed, Feb 24, 2010 at 02:13:53PM +0100, Goswin von Brederlow wrote:
> > grub.cfg (grub2) uses UUID for grub itself. But the kernel can be bootet
> > with root=/dev/md0. But in that case where does it get the homehost from
> > and since when does kernel raid autoconfig have a homehost?
> 
> The homehost attribute does only exist with v1 superblocks. And there is
> no in-kernel auto-assembly for v1 superblocks.
> v0.9 superblocks (for which in-kernel auto-assembly is deprecated but
> still provided) have no homehost.
>

Not entirely correct.  The 'homehost' is encoded in the uuid of v0.90
metadata, so it does affect them too.

in-kernel autodetect does not make use of 'homehost' and so does not protect
you from the potential confusions that homehost tries to protect you from.

NeilBrown



-- 
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/20100225092338.5e20f...@notabene.brown

Bug#464191: Sound broken with linux-image-2.6.24-1-686

[Moritz Muehlenhoff]

severity 464191 wishlist
retitle 464191 Reintroduce Maestro firmware
tags 464191 wontfix
thanks

> >On Tue, Feb 12, 2008 at 06:23:17PM -0500, Rob Bochan wrote:
> >>So now I've got to recompile my kernel just to have sound?
> >>How nice. I haven't had to do that since about 1998. I guess this is good
> >>enough reason as any to remove Debian from my laptop. Sad too, it's been
> >>Debian since before Woody was released.
> >
> >You do not need to recompile the kernel, you need the appropriate binary
> >firmware blob.  Get the firmware package
> >
> > ftp://ftp.alsa-project.org/pub/firmware/alsa-firmware-1.0.16.tar.bz2
> >
> >and run ./configure && make && make install
> >
> >After this you should have the following files present:
> >
> > /lib/firmware/ess/maestro3_assp_kernel.fw
> > /lib/firmware/ess/maestro3_assp_minisrc.fw
> >
> >Then, run rmmod snd_maestro3 and modprobe snd_maestro3 again.

> Thank you Gabor. I got my sounds back on this prescription!
> 
> I hope it will be fixed on next kernels release though.

We cannot distribute the firmware unfortunately. However, there are
instructions how to fix this locally: http://wiki.debian.org/snd-maestro3

Cheers,
Moritz



-- 
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/20100224221024.ga3...@galadriel.inutil.org

Bug#562486: please enable tomoyo

[Moritz Muehlenhoff]

On Mon, Feb 15, 2010 at 08:54:59AM +0100, Bastian Blank wrote:
> On Sun, Feb 14, 2010 at 10:56:10PM +0100, Moritz Muehlenhoff wrote:
> > I'll enable tomoyo next weekend unless further objections arise.
> 
> It can't be built as a module, so you have to check space constraints.

What constraints specifically are you referring to?

Cheers,
Moritz



-- 
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/20100224215832.ga2...@galadriel.inutil.org

Bug#490376: marked as done (kernel BUG at mm/remap.c:669)

[Debian Bug Tracking System]

Your message dated Wed, 24 Feb 2010 23:12:17 +0100
with message-id <20100224221217.ga5...@galadriel.inutil.org>
and subject line Re: kernel BUG at mm/remap.c:669
has caused the Debian Bug report #490376,
regarding kernel BUG at mm/remap.c:669
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.)


-- 
490376: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=490376
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.25-2-486
Version: 2.6.25-6
Severity: normal

Hi,

I was running a shell script which basically created small (<3kB) files when
this bug occured. At that moment the directory contained ca. 300.000 files. If I
could provide further information please send a short note.


-- Package-specific info:
** Version:
Linux version 2.6.25-2-486 (Debian 2.6.25-6) (m...@debian.org) (gcc version 
4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 Fri Jun 27 02:39:22 UTC 2008

** Command line:
root=/dev/hda1 ro 

** Tainted: G (128)

** Kernel log:
[4.358556] Probing IDE interface ide1...
[5.219759] hdc: AOPEN CD-RW CRW5232 1.05 20040324, ATAPI CD/DVD-ROM drive
[6.001496] hdd: HL-DT-ST DVDRAM GSA-4163B, ATAPI CD/DVD-ROM drive
[6.057257] hdc: host max PIO5 wanted PIO255(auto-tune) selected PIO4
[6.057441] hdc: UDMA/33 mode selected
[6.057960] hdd: host max PIO5 wanted PIO255(auto-tune) selected PIO4
[6.058757] hdd: UDMA/33 mode selected
[6.059259] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
[6.059377] ide1 at 0x170-0x177,0x376 on irq 15
[6.133828] hda: max request size: 512KiB
[6.179376] hda: 781422768 sectors (400088 MB) w/8192KiB Cache, 
CHS=48641/255/63
[6.203403] hda: cache flushes supported
[6.203403]  hda: hda1 hda2 hda3 hda4 < hda5 hda6 >
[6.242345] hdc: ATAPI 40X CD-ROM CD-R/RW drive, 2048kB Cache
[6.242583] Uniform CD-ROM driver Revision: 3.20
[6.256089] hdd: ATAPI 40X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache
[6.485959] PM: Starting manual resume from disk
[6.532269] kjournald starting.  Commit interval 5 seconds
[6.532269] EXT3-fs: mounted filesystem with ordered data mode.
[7.605530] udevd version 124 started
[9.330509] Linux agpgart interface v0.103
[9.355408] agpgart: Detected VIA KT266/KY266x/KT333 chipset
[9.365537] agpgart: AGP aperture is 128M @ 0xd000
[9.565205] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[9.594629] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[   10.044537] NET: Registered protocol family 23
[   10.853611] input: Power Button (FF) as /class/input/input1
[   10.891307] ACPI: Power Button (FF) [PWRF]
[   10.891508] input: Power Button (CM) as /class/input/input2
[   10.917631] ACPI: Power Button (CM) [PWRB]
[   10.917834] input: Sleep Button (CM) as /class/input/input3
[   10.940926] ACPI: Sleep Button (CM) [SLPB]
[   11.903680] Real Time Clock Driver v1.12ac
[   12.165631] input: PC Speaker as /class/input/input4
[   13.016318] parport_pc 00:0a: reported by Plug and Play ACPI
[   13.016433] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE]
[   13.277193] logips2pp: Detected unknown logitech mouse model 57
[   13.740051] input: ImExPS/2 Logitech Explorer Mouse as /class/input/input5
[   14.506818] ACPI: PCI Interrupt :00:11.5[C] -> Link [LNKC] -> GSI 5 
(level, low) -> IRQ 5
[   14.507110] PCI: Setting latency timer of device :00:11.5 to 64
[   15.918919] Adding 1951856k swap on /dev/hda6.  Priority:-1 extents:1 
across:1951856k
[   16.324427] EXT3 FS on hda1, internal journal
[   17.001294] loop: module loaded
[   17.108852] device-mapper: uevent: version 1.0.3
[   17.111336] device-mapper: ioctl: 4.13.0-ioctl (2007-10-18) initialised: 
dm-de...@redhat.com
[   17.951303] kjournald starting.  Commit interval 5 seconds
[   17.951358] EXT3 FS on hda5, internal journal
[   17.951358] EXT3-fs: mounted filesystem with ordered data mode.
[   17.971181] kjournald starting.  Commit interval 5 seconds
[   17.971181] EXT3-fs: mounted filesystem with ordered data mode.
[   18.150510] SGI XFS with ACLs, security attributes, realtime, large block 
numbers, no debug enabled
[   18.158208] SGI XFS Quota Management subsystem
[   18.353728] XFS mounting filesystem hda3
[   18.418616] Ending clean XFS mount for filesystem: hda3
[   19.606956] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
[   21.678370] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
[   21.789918] NET: Registered protocol family 10
[   21.791083] lo: Disabled Privacy Extensions
[   22.553156] lp0: using parport0 (interrupt-driven).
[   22.576059] ppdev: user-spac

Bug#490618: marked as done (RTC compiled into kernel stops use of rtc-cmos and therefore ACPI wakeup)

[Debian Bug Tracking System]

Your message dated Wed, 24 Feb 2010 23:12:50 +0100
with message-id <20100224221250.ga5...@galadriel.inutil.org>
and subject line Re: RTC compiled into kernel stops use of rtc-cmos and 
therefore ACPI wakeup
has caused the Debian Bug report #490618,
regarding RTC compiled into kernel stops use of rtc-cmos and therefore ACPI 
wakeup
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.)


-- 
490618: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=490618
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.25-2-amd64
Version: 2.6.25-6

It seems rtc is compiled into the kernel instead of as a module.
As a result rtc-cmos will not work and there is no way of using
ACPI wakeup as the old /proc/acpi/alarm has been removed.

Is there any workaround available? ie. disable the rtc driver so
rtc-cmos can take over? or a way to restore the /proc/acpi/alarm.

Thanks.


  Start at the new Yahoo!7 for a better online experience. www.yahoo7.com.au


--- End Message ---
--- Begin Message ---
On Tue, Jul 28, 2009 at 01:09:47PM +0200, Moritz Muehlenhoff wrote:
> On Sat, Jul 12, 2008 at 10:31:05PM -0700, Lindsay Powles wrote:
> > Package: linux-image-2.6.25-2-amd64
> > Version: 2.6.25-6
> > 
> > It seems rtc is compiled into the kernel instead of as a module.
> > As a result rtc-cmos will not work and there is no way of using
> > ACPI wakeup as the old /proc/acpi/alarm has been removed.
> > 
> > Is there any workaround available? ie. disable the rtc driver so
> > rtc-cmos can take over? or a way to restore the /proc/acpi/alarm.
> 
> Is this fixed in the 2.6.26 kernel from stable?

No further feedback, closing the bug.

If this can be reproduced with current kernels, please reopen this bug.

Cheers,
Moritz

--- End Message ---

Processed: Re: Bug#464191: Sound broken with linux-image-2.6.24-1-686

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 464191 wishlist
Bug #464191 [linux-2.6] Sound broken with linux-image-2.6.24-1-686
Bug #465161 [linux-2.6] alsa-base: Alsa fails to find maestro3 soundcard with 
Maestro3: probe of :00:08.0 failed with error -2
Severity set to 'wishlist' from 'normal'

Severity set to 'wishlist' from 'normal'

> retitle 464191 Reintroduce Maestro firmware
Bug #464191 [linux-2.6] Sound broken with linux-image-2.6.24-1-686
Bug #465161 [linux-2.6] alsa-base: Alsa fails to find maestro3 soundcard with 
Maestro3: probe of :00:08.0 failed with error -2
Changed Bug title to 'Reintroduce Maestro firmware' from 'Sound broken with 
linux-image-2.6.24-1-686'
Changed Bug title to 'Reintroduce Maestro firmware' from 'alsa-base: Alsa fails 
to find maestro3 soundcard with Maestro3: probe of :00:08.0 failed with 
error -2'
> tags 464191 wontfix
Bug #464191 [linux-2.6] Reintroduce Maestro firmware
Bug #465161 [linux-2.6] Reintroduce Maestro firmware
Added tag(s) wontfix.
Added tag(s) wontfix.
> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
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.126704943810697.transcr...@bugs.debian.org

Bug#489206: marked as done (Entering passphrase doesn't honor console/serial selection properly)

[Debian Bug Tracking System]

Your message dated Wed, 24 Feb 2010 23:11:39 +0100
with message-id <20100224221139.ga4...@galadriel.inutil.org>
and subject line Re: [Pkg-cryptsetup-devel] Bug#489206: Entering passphrase 
doesn't honor console/serial selection properly
has caused the Debian Bug report #489206,
regarding Entering passphrase doesn't honor console/serial selection properly
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.)


-- 
489206: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=489206
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cryptsetup
Version: 2:1.0.6-2
Severity: normal

Hi,

I'm seeing issues wrt to entering dm-crypt passphrases when using the
kernel parameters 'console=tty0 console=ttyS0,115200' (to get the boot
log on both the screen and on the serial console (COM1).

In such a case I can only enter the passphrase on the serial console,
but _not_ on the normal keyboard/screen, which is obviously a bug.

If I only provided 'console=ttyS0,115200' the behviour would be ok, but
when using 'console=tty0 console=ttyS0,115200' both consoles (serial and
VGA) should work.


Thanks, Uwe.
-- 
http://www.hermann-uwe.de  | http://www.holsham-traders.de
http://www.crazy-hacks.org | http://www.unmaintained-free-software.org


--- End Message ---
--- Begin Message ---
On Sat, Aug 15, 2009 at 07:29:21PM +0200, Moritz Muehlenhoff wrote:
> On Thu, Jul 16, 2009 at 02:22:09AM +0200, Jonas Meurer wrote:
> > reassign 489206 linux-2.6
> > thanks
> > 
> > 
> > On 04/07/2008 Uwe Hermann wrote:
> > > Package: cryptsetup
> > > Version: 2:1.0.6-2
> > > Severity: normal
> > > 
> > > Hi,
> > > 
> > > I'm seeing issues wrt to entering dm-crypt passphrases when using the
> > > kernel parameters 'console=tty0 console=ttyS0,115200' (to get the boot
> > > log on both the screen and on the serial console (COM1).
> > > 
> > > In such a case I can only enter the passphrase on the serial console,
> > > but _not_ on the normal keyboard/screen, which is obviously a bug.
> > > 
> > > If I only provided 'console=ttyS0,115200' the behviour would be ok, but
> > > when using 'console=tty0 console=ttyS0,115200' both consoles (serial and
> > > VGA) should work.
> > 
> > Hey,
> > 
> > I really don't see how that one can be fixed in cryptsetup. It's rather
> > a kernel bug. Thus reassigning the bug to linux-2.6.
> 
> Does it work with more recent kernels?

No further feedback, closing the bug.

If this can be reproduced with current kernels, please reopen this bug.

Cheers,
Moritz

--- End Message ---

Bug#464145: marked as done (linux-image-2.6.22-2-686: network performance degrades over time with peer-to-peer file transfer)

[Debian Bug Tracking System]

Your message dated Wed, 24 Feb 2010 23:02:07 +0100
with message-id <20100224220207.ga3...@galadriel.inutil.org>
and subject line Re: linux-image-2.6.22-2-686: network performance degrades 
over time with peer-to-peer file transfer
has caused the Debian Bug report #464145,
regarding linux-image-2.6.22-2-686: network performance degrades over time with 
peer-to-peer file transfer
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.)


-- 
464145: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464145
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.22-2-686
Version: 2.6.22-4
Severity: normal

Everytime I use a P2P file transfer application, in my case either amule
or ktorrent, the network bandwidth systematically gets smaller and
smaller over time.

After a day using P2P, on FTP servers where I typically have 700kb/s
transfers, even after stopping all other file transfer network activity,
I usually get around 100kb/s.

Stopping and restarting my PPPoE connection usually was not enough to
get back my full bandwidth, but doing it to the underlying Ethernet
connection also was.

Could it be a memory leak or slow data corruption that arise only with
long-living connections, inside the via_rhine driver (this is my PCI
card 00:12.0)?

-- Package-specific info:
** Version:
Linux version 2.6.22-2-686 (Debian 2.6.22-4) (wa...@debian.org) (gcc version 
4.1.3 20070812 (prerelease) (Debian 4.1.2-15)) #1 SMP Fri Aug 31 00:24:01 UTC 
2007

** Not tainted

** Kernel log:
[drm] Initialized drm 1.1.0 20060810
[drm] Initialized radeon 1.27.0 20060524 on minor 0
agpgart: Found an AGP 3.5 compliant device at :00:00.0.
agpgart: Device is in legacy mode, falling back to 2.x
agpgart: Putting AGP V2 device at :00:00.0 into 1x mode
agpgart: Putting AGP V2 device at :01:00.0 into 1x mode
[drm] Setting GART location based on new memory map
[drm] writeback test succeeded in 1 usecs
usb 1-1: USB disconnect, address 3
usb 1-1.1: USB disconnect, address 5
usb 1-1.2: USB disconnect, address 6
usb 1-1: new full speed USB device using uhci_hcd and address 7
usb 1-1: configuration #1 chosen from 1 choice
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 2 ports detected
usb 1-1.1: new low speed USB device using uhci_hcd and address 8
usb 1-1.1: configuration #1 chosen from 1 choice
input: Logitech USB Receiver as /class/input/input7
input: USB HID v1.10 Keyboard [Logitech USB Receiver] on usb-:00:10.0-1.1
input: Logitech USB Receiver as /class/input/input8
input,hiddev96: USB HID v1.10 Mouse [Logitech USB Receiver] on 
usb-:00:10.0-1.1
usb 4-4: new high speed USB device using ehci_hcd and address 6
usb 4-4: configuration #1 chosen from 1 choice
Initializing USB Mass Storage driver...
scsi1 : SCSI emulation for USB Mass Storage devices
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usb-storage: device found at 6
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
scsi 1:0:0:0: Direct-Access Maxtor 6 L300R0PQ: 0 ANSI: 0
sd 1:0:0:0: [sda] 586114704 512-byte hardware sectors (300091 MB)
sd 1:0:0:0: [sda] Write Protect is off
sd 1:0:0:0: [sda] Mode Sense: 33 00 00 00
sd 1:0:0:0: [sda] Assuming drive cache: write through
sd 1:0:0:0: [sda] 586114704 512-byte hardware sectors (300091 MB)
sd 1:0:0:0: [sda] Write Protect is off
sd 1:0:0:0: [sda] Mode Sense: 33 00 00 00
sd 1:0:0:0: [sda] Assuming drive cache: write through
 sda: sda1 sda2 sda3 sda4
sd 1:0:0:0: [sda] Attached SCSI disk
Filesystem "dm-1": Disabling barriers, not supported by the underlying device
XFS mounting filesystem dm-1
Starting XFS recovery on filesystem: dm-1 (logdev: internal)
Ending XFS recovery on filesystem: dm-1 (logdev: internal)
Filesystem "dm-30": Disabling barriers, not supported by the underlying device
XFS mounting filesystem dm-30
Starting XFS recovery on filesystem: dm-30 (logdev: internal)
Ending XFS recovery on filesystem: dm-30 (logdev: internal)
Filesystem "dm-16": Disabling barriers, not supported by the underlying device
XFS mounting filesystem dm-16
Starting XFS recovery on filesystem: dm-16 (logdev: internal)
Ending XFS recovery on filesystem: dm-16 (logdev: internal)
Filesystem "dm-3": Disabling barriers, not supported by the underlying device
XFS mounting filesystem dm-3
Ending clean XFS mount for filesystem: dm-3
Filesystem "dm-17": Disabling barriers, not supported by the underlying device
XFS mounting filesystem dm-17
Ending clean XFS mount for filesystem: dm-17
Filesystem "dm-18": Disabling barriers, not suppor

Re: Xen dom0 2.6.32 stable branch

[Ian Campbell]

On Wed, 2010-02-24 at 18:29 +0100, Bastian Blank wrote:
> On Wed, Feb 24, 2010 at 03:42:32PM +0100, Bastian Blank wrote:
> > http://hermes.jura.uni-tuebingen.de/~blank/debian/xen-test/
> 
> It seems to run. 

I get a panic very early on "No available IRQ to bind to: increase
nr_irqs!". Will investigate tomorrow.

Ian.
-- 
Ian Campbell

Sometimes a man who deserves to be looked down upon because he is a
fool is despised only because he is a lawyer.
-- Montesquieu


signature.asc
Description: This is a digitally signed message part

linux-2.6_2.6.32-9_amd64.changes is NEW

[Archive Administrator]

firmware-linux-free_2.6.32-9_all.deb
  to main/l/linux-2.6/firmware-linux-free_2.6.32-9_all.deb
linux-2.6_2.6.32-9.diff.gz
  to main/l/linux-2.6/linux-2.6_2.6.32-9.diff.gz
linux-2.6_2.6.32-9.dsc
  to main/l/linux-2.6/linux-2.6_2.6.32-9.dsc
linux-doc-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-9_all.deb
(new) linux-headers-2.6.32-3-all-amd64_2.6.32-9_amd64.deb optional kernel
All header files for Linux 2.6.32
 This package depends against all architecture-specific kernel header files
 for Linux kernel version 2.6.32, generally used for building out-of-tree
 kernel modules.
(new) linux-headers-2.6.32-3-all_2.6.32-9_amd64.deb optional kernel
All header files for Linux 2.6.32
 This package depends against all architecture-specific kernel header files
 for Linux kernel version 2.6.32, generally used for building out-of-tree
 kernel modules.
(new) linux-headers-2.6.32-3-amd64_2.6.32-9_amd64.deb optional kernel
Header files for Linux 2.6.32-3-amd64
 This package provides the architecture-specific kernel header files for
 Linux kernel 2.6.32-3-amd64, generally used for building out-of-tree
 kernel modules.  These files are going to be installed into
 /usr/src/linux-headers-2.6.32-3-amd64, and can be used for building
 modules that load into the kernel provided by the
 linux-image-2.6.32-3-amd64 package.
(new) linux-headers-2.6.32-3-common-vserver_2.6.32-9_amd64.deb optional kernel
Common header files for Linux 2.6.32-3-vserver
 This package provides the architecture-specific common kernel header files
 for Linux kernel version 2.6.32-3-vserver, generally used for building
 out-of-tree kernel modules.  To obtain a complete set of headers you also
 need to install the linux-headers-2.6.32-3-(flavour) package, matching the
 flavour of the kernel you intend the build for.
(new) linux-headers-2.6.32-3-common_2.6.32-9_amd64.deb optional kernel
Common header files for Linux 2.6.32-3
 This package provides the architecture-specific common kernel header files
 for Linux kernel version 2.6.32-3, generally used for building out-of-tree
 kernel modules.  To obtain a complete set of headers you also need to
 install the linux-headers-2.6.32-3-(flavour) package, matching the flavour
 of the kernel you intend the build for.
(new) linux-headers-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb optional kernel
Header files for Linux 2.6.32-3-vserver-amd64
 This package provides the architecture-specific kernel header files for
 Linux kernel 2.6.32-3-vserver-amd64, generally used for building
 out-of-tree kernel modules.  These files are going to be installed into
 /usr/src/linux-headers-2.6.32-3-vserver-amd64, and can be used for
 building modules that load into the kernel provided by the
 linux-image-2.6.32-3-vserver-amd64 package.
(new) linux-image-2.6.32-3-amd64_2.6.32-9_amd64.deb optional kernel
Linux 2.6.32 for 64-bit PCs
 The Linux kernel 2.6.32 and modules for use on PCs with AMD64 or Intel 64
 processors.
 .
 This kernel also runs on a Xen hypervisor.  It supports only unprivileged
 (domU) operation.
(new) linux-image-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb optional kernel
Linux 2.6.32 for 64-bit PCs, Linux-VServer support
 The Linux kernel 2.6.32 and modules for use on PCs with AMD64 or Intel 64
 processors.
 .
 This kernel includes support for Linux-VServer virtualization.
 .
 This kernel also runs on a Xen hypervisor.  It supports only unprivileged
 (domU) operation.
linux-libc-dev_2.6.32-9_amd64.deb
  to main/l/linux-2.6/linux-libc-dev_2.6.32-9_amd64.deb
linux-manual-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-9_all.deb
linux-patch-debian-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-9_all.deb
linux-source-2.6.32_2.6.32-9_all.deb
  to main/l/linux-2.6/linux-source-2.6.32_2.6.32-9_all.deb
(new) linux-support-2.6.32-3_2.6.32-9_all.deb optional devel
Support files for Linux 2.6.32
 This package provides support files for the Linux kernel build, e.g.
 scripts to handle ABI information and for generation of build system meta
 data.
Changes: linux-2.6 (2.6.32-9) unstable; urgency=high
 .
  [ Ben Hutchings ]
  * Do not build obsolete lgs8gl5 driver
  * [x86] Enable USB IP drivers (Closes: #568903)
  * Ignore failure of lsusb when gathering information for bug reports
(Closes: #569725)
  * macvlan: Add bridge, VEPA and private modes (Closes: #568756)
  * [sparc] sunxvr500: Support Intergraph graphics chips again
(Closes: #508108)
  * sfc: Apply fixes from 2.6.33
  * ath9k: Add support for AR2427
  * fs/exec.c: fix initial stack reservation (regression in 2.6.32.9)
 .
  [ maximilian attems]
  * Postinst don't refercence k-p related manpage. (closes: #542208)
  * Postinst only write kernel-img.conf for palo boxes.
  * Enable VT_HW_CONSOLE_BINDING for unbinding efifb. (closes: #569314)
  * hwmon: Add driver for VIA CPU core temperature.
  * wireless: report reasonable bitrate for MCS rates through wext.
  * efifb: fix framebuffer handoff. (b

Re: [ubuntu-x] Status of kernel X drivers

[Julien Cristau]

On Sun, Feb 21, 2010 at 23:20:14 +, Ben Hutchings wrote:

> Fedora has been backporting drm (and nouveau) for a long time but it's
> not so clear what means for RHEL.
> 
> I think this is something we will also consider doing in Debian.  A year
> from now I expect nv to be dead and radeon UMS to be removed upstream,
> making it impractical to backport new hardware support.  Given that, the
> maintenance burden for 2.6.33 drm should be lower.  But this is really
> outside my area of expertise and certainly not my decision to make.
> 
For radeon it seems clear that we need the 2.6.33 code or stay with UMS,
and nouveau is not in .32, so basically the question seems to be about
i915.  My impression is that 2.6.32 was quite bad, and 2.6.32.x has
gotten it into a better shape (except for 8xx, but that's been broken
for quite a while, and not just with kms, so...).  Now if we're
confident that either i915 in 2.6.33 is better than .32.9 already or
that the regressions it introduces can be fixed in the next month or
couple of months, then backporting drm from .33 seems like it would be a
good thing to do for squeeze.

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#571266: linux-image-2.6.26-2-486: boot 486 kernel fails with root=LABEL=

[william estrada]

Package: linux-image-2.6.26-2-486
Version: 2.6.26-21lenny3
Severity: important

In grub.conf,

   If I use root=/dev/hda3 my systems boots up and runs.
   If I use root=LABEL=/Lenny the system hangs on boot.


-- System Information:
Debian Release: 5.0.4
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i586)

Kernel: Linux 2.6.26-2-486
Locale: LANG=en_US.UTF-8, LC_CTYPE=C (charmap=locale: Cannot set LC_MESSAGES to 
default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.26-2-486 depends on:
ii  debconf [debconf-2.0] 1.5.24 Debian configuration management sy
ii  initramfs-tools [linux-initra 0.92o  tools for generating an initramfs
ii  module-init-tools 3.4-1  tools for managing Linux kernel mo

linux-image-2.6.26-2-486 recommends no packages.

Versions of packages linux-image-2.6.26-2-486 suggests:
ii  grub   0.97-47lenny2 GRand Unified Bootloader (Legacy v
pn  linux-doc-2.6.26   (no description available)

-- debconf information:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_CTYPE = "C",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.26-2-486/postinst/depmod-error-2.6.26-2-486: false
  linux-image-2.6.26-2-486/preinst/initrd-2.6.26-2-486:
  linux-image-2.6.26-2-486/preinst/abort-install-2.6.26-2-486:
  linux-image-2.6.26-2-486/preinst/lilo-has-ramdisk:
  linux-image-2.6.26-2-486/preinst/lilo-initrd-2.6.26-2-486: true
* linux-image-2.6.26-2-486/postinst/create-kimage-link-2.6.26-2-486: true
  linux-image-2.6.26-2-486/preinst/elilo-initrd-2.6.26-2-486: true
  linux-image-2.6.26-2-486/postinst/bootloader-error-2.6.26-2-486:
  linux-image-2.6.26-2-486/preinst/overwriting-modules-2.6.26-2-486: true
  linux-image-2.6.26-2-486/postinst/old-system-map-link-2.6.26-2-486: true
  linux-image-2.6.26-2-486/prerm/removing-running-kernel-2.6.26-2-486: true
  linux-image-2.6.26-2-486/postinst/bootloader-test-error-2.6.26-2-486:
  linux-image-2.6.26-2-486/prerm/would-invalidate-boot-loader-2.6.26-2-486: true
  linux-image-2.6.26-2-486/preinst/failed-to-move-modules-2.6.26-2-486:
* linux-image-2.6.26-2-486/preinst/bootloader-initrd-2.6.26-2-486: true
  linux-image-2.6.26-2-486/preinst/abort-overwrite-2.6.26-2-486:
  linux-image-2.6.26-2-486/postinst/old-initrd-link-2.6.26-2-486: true
  linux-image-2.6.26-2-486/postinst/old-dir-initrd-link-2.6.26-2-486: true
  linux-image-2.6.26-2-486/postinst/kimage-is-a-directory:
  linux-image-2.6.26-2-486/postinst/depmod-error-initrd-2.6.26-2-486: false



-- 
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/20100224205121.18304.79046.report...@server.mt-umunhum-wireless.net

Processing of linux-2.6_2.6.32-9_amd64.changes

[Archive Administrator]

linux-2.6_2.6.32-9_amd64.changes uploaded successfully to localhost
along with the files:
  linux-2.6_2.6.32-9.dsc
  linux-2.6_2.6.32-9.diff.gz
  linux-doc-2.6.32_2.6.32-9_all.deb
  linux-manual-2.6.32_2.6.32-9_all.deb
  linux-patch-debian-2.6.32_2.6.32-9_all.deb
  linux-source-2.6.32_2.6.32-9_all.deb
  linux-support-2.6.32-3_2.6.32-9_all.deb
  firmware-linux-free_2.6.32-9_all.deb
  linux-image-2.6.32-3-amd64_2.6.32-9_amd64.deb
  linux-headers-2.6.32-3-amd64_2.6.32-9_amd64.deb
  linux-headers-2.6.32-3-common_2.6.32-9_amd64.deb
  linux-headers-2.6.32-3-all_2.6.32-9_amd64.deb
  linux-headers-2.6.32-3-all-amd64_2.6.32-9_amd64.deb
  linux-libc-dev_2.6.32-9_amd64.deb
  linux-image-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb
  linux-headers-2.6.32-3-vserver-amd64_2.6.32-9_amd64.deb
  linux-headers-2.6.32-3-common-vserver_2.6.32-9_amd64.deb

Greetings,

Your Debian queue daemon (running on host ries.debian.org)


-- 
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/e1nkna3-0003go...@ries.debian.org

Bug#571257: ath5k and athros wireless fails to work since last kernel update

[Jim Ham]

Package: linux-image-2.6.30-2-amd64
Version: 2.6.32-5

I'm not sure where to report this.

Debian sqeeze
Fujitsu Lifebook A3130
uname -a reports: Linux WideBook 2.6.32-trunk-amd64 #1 SMP Sun Jan 10
22:40:40 UTC 2010 x86_64 GNU/Linux

The Athros wireless chip is built in on this notebook. All worked well
until the last kernel update. Now the athros chip associates during
boot, but  deassociates later. From dmesg:
[  428.084211] ath0: deauthenticating from 00:16:01:4a:c8:a3 by local
choice (reason=3)

lspci reports:
...
07:00.0 Ethernet controller: Atheros Communications Inc. AR5001 Wireless
Network Adapter (rev 01
...

This has a secondary effect in that both top and bottom panels in Gnome
don't work as long as there is no internet. If I plug in the hardware
port eth0, do an ifdown, then ifup on eth0 the banners start to work
after a while. This seems to be a very strange side affect!

Once I know where to send this report I can include the logs.

Regards,

Jim Ham





-- 
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/1267038552.10137.3.ca...@localhost

Processed: Re: Bug#571257: ath5k and athros wireless fails to work since last kernel update

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 571257 linux-2.6
Bug #571257 [linux-image-2.6.30-2-amd64] ath5k and athros wireless fails to 
work since last kernel update
Warning: Unknown package 'linux-image-2.6.30-2-amd64'
Bug reassigned from package 'linux-image-2.6.30-2-amd64' to 'linux-2.6'.
Bug No longer marked as found in versions 2.6.32-5.
> --
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
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.126703983731009.transcr...@bugs.debian.org

Re: Xen dom0 2.6.32 stable branch

[Ian Campbell]

On Wed, 2010-02-24 at 15:42 +0100, Bastian Blank wrote: 
> On Wed, Feb 24, 2010 at 01:53:09PM +, Ian Campbell wrote:
> > On Wed, 2010-02-24 at 14:39 +0100, Bastian Blank wrote:
> > > Already on it. It seems to need a hypervisor update as well.
> > I believe this branch needs either Xen 4.0 or 3.4 with a patch
> > backported for the new dom0 APIC interfaces, I think that it is in
> > xen-3.4-testing.hg but not an actual release yet. Do you need me to find
> > the patch in question?
> 
> It looks like this is the setup_gsi command, which is in 3.4.3-rc2.

Yes, I think it's: 
changeset:   19862:608ebc959c35
user:Keir Fraser 
date:Tue Dec 22 11:37:01 2009 +
files:   xen/arch/x86/mpparse.c xen/arch/x86/physdev.c 
xen/include/public/physdev.h
description:
x86: Add a new physdev_op PHYSDEVOP_setup_gsi for GSI setup.

GSI 0-15 is setup by hypervisor, and GSI > =16 is setup by dom0
this physdev_op PHYSDEVOP_setup_gsi. This patch can help dom0
to get rid of intrusive changes of ioapic.

Signed-off-by: Xiantao Zhang 
xen-unstable changeset:   20491:d44371e6e5d6
xen-unstable date:Tue Nov 24 14:43:07 2009 +

which applies cleanly to the existing 3.4.2-2 package. (BTW did you get
my mails to pkg-xen-devel?)

> > Once you are at the point at which additional testing etc is useful
> > please let me know, I'd be glad to give it a go!
> 
> http://hermes.jura.uni-tuebingen.de/~blank/debian/xen-test/
> 
[...]

Thanks, will give them a go (including the subsequent update you posted)

Ian.

-- 
Ian Campbell

A great nation is any mob of people which produces at least one honest
man a century.


signature.asc
Description: This is a digitally signed message part

Re: [PATCH 2/2] auto_add_modules: Copy all modules from net, excluding some subdirectories

[maximilian attems]

On Sun, 22 Nov 2009, Ben Hutchings wrote:

> This removes the need to maintain an explicit list, which always has
> some drivers missing.
> 
> Signed-off-by: Ben Hutchings 
> ---
> This should also go some way to fixing #553024.
> 
> Ben.

thanks both applied:
http://git.debian.org/?p=kernel/initramfs-tools.git;a=summary


-- 
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/20100224175641.gi11...@stro.at

Bug#566401: Does not install firmware.agent into initramfs

[maximilian attems]

On Wed, Feb 24, 2010 at 06:22:36PM +0100, Marco d'Itri wrote:
> On Feb 24, maximilian attems  wrote:
> 
> > shall the udev hook take care of it to add it anyway
> > and i remove the addition?
> udev now installs it, but it cannot be removed from initramfs-tools
> until there will be a versioned dependency which will guarantee a
> working system (and I do not want to add one just for this).

well, right I could add one on initramfs-tools side, but then people
have pain on dist-upgrade.
let's keep that bug report and I'll remove the addition postsqueeze and
then bump dep on that udev version that first shipped 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/20100224174242.gl15...@baikonur.stro.at

Bug#565696: initramfs-tools: Support for AoE

[C.J. Adams-Collier]

Yeah, I have some revisions.  I don't want that version going in to an
official repository.  Mostly I wanted to open a dialogue.

I'm using the modified version in order to build an initrd for use in a
KVM virtual server.  I did a write-up:

http://wp.colliertech.org/cj/?p=678

Basically, the idea is to make it possible to do diskless virtual
machines with a minimum of fuss.  I can't think of any easy way to make
all the moving parts fit together.  I'm wrapping up an unrelated project
at work, but I expect I'll have a bit more time to poke at this in the
near future.

Cheers,

C.J.


On Wed, 2010-02-24 at 18:30 +0100, maximilian attems wrote: 
> On Sun, 17 Jan 2010, C.J. Adams-Collier wrote:
> 
> > Package: initramfs-tools
> > Version: 0.92bubuntu53
> > Severity: wishlist
> > 
> > 
> > http://lists.debian.org/debian-kernel/2010/01/msg00368.html
> > 
> 
> hmm this patch looks clean, not a real objection.
> 
> just missing a motivation, why one would want that?
> do you have any refines since.
> 
> currently not sure why mailine initramfs-tools should care
> about aoe or iscsi or fibre channel over ethernet,
> but maybe someone else also wants to jump in for support!?
> 
> thanks + kind regards



signature.asc
Description: This is a digitally signed message part

Bug#571215: Backlight turned off during bootup

[Uli Schlachter]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

maximilian attems wrote:
> On Wed, Feb 24, 2010 at 03:29:04PM +0100, Uli Schlachter wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA256
>>
>> maximilian attems wrote:
>>> On Wed, Feb 24, 2010 at 12:58:54PM +0100, Uli Schlachter wrote:
 This morning when I booted my laptop, right after grub was done, the 
 backlight
 turned off. I collected the attached info by entering my HDD passphrase 
 blindly
 and starting up X (which partly worked but was damn slow).

 Kernel is 2.6.32-trunk-amd64.
>>> old, newer one is available in unstable: 2.6.32-8, check against it.
>> Uhm, I might be blind...
>> I installed the following. I'll report back with the results this
>> evening.
>>
>> [AKTUALISIERUNG] linux-image-2.6-amd64 2.6.32+23 -> 2.6.32+24
> 
> please corret your apt sources or whatever, I spoke about unstable
> and there you have linux-image-2.6.32-2-amd64

I'm now running this (thanks for the hint with the package name):
$ uname -a
Linux psytux 2.6.32-2-amd64 #1 SMP Fri Feb 12 00:01:47 UTC 2010 x86_64 GNU/Linux

>> ii  hotkey-setup0.1-23
>> auto-configures laptop hotkeys
> 
> nuke it and reboot, probably cures your trouble not to have it.

Neither of this helped my backlight, but booting with vga=ext as suggested by
Marco d'Itri made everything work (and the kernel suddenly starts to notice my
second screen...)

Julien Cristau wrote:
> On Wed, Feb 24, 2010 at 12:58:54 +0100, Uli Schlachter wrote:
>> > Feb 24 12:34:40 psytux kernel: [0.548357] vesafb: framebuffer at 
>> > 0x8000, mapped to 0xc9001098, using 5120k, total 5120k
>> > Feb 24 12:34:40 psytux kernel: [0.548360] vesafb: mode is 
>> > 1280x1024x32, linelength=5120, pages=0
>> > Feb 24 12:34:40 psytux kernel: [0.548362] vesafb: scrolling: redraw
>> > Feb 24 12:34:40 psytux kernel: [0.548364] vesafb: Truecolor: 
>> > size=8:8:8:8, shift=24:16:8:0
>> > Feb 24 12:34:40 psytux kernel: [0.588241] Console: switching to colour 
>> > frame buffer device 160x64
>> > Feb 24 12:34:40 psytux kernel: [0.628004] fb0: VESA VGA frame buffer 
>> > device
> [...]
>> > Feb 24 12:34:40 psytux kernel: [0.732304] [drm] Initialized drm 1.1.0 
>> > 20060810
>> > Feb 24 12:34:40 psytux kernel: [0.743618] i915 :00:02.0: PCI INT A 
>> > -> GSI 16 (level, low) -> IRQ 16
>> > Feb 24 12:34:40 psytux kernel: [0.743622] i915 :00:02.0: setting 
>> > latency timer to 64
>> > Feb 24 12:34:40 psytux kernel: [0.758588]   alloc irq_desc for 29 on 
>> > node -1
>> > Feb 24 12:34:40 psytux kernel: [0.758592]   alloc kstat_irqs on node -1
>> > Feb 24 12:34:40 psytux kernel: [0.758601] i915 :00:02.0: irq 29 
>> > for MSI/MSI-X
>> > Feb 24 12:34:40 psytux kernel: [0.758608] [drm] set up 63M of stolen 
>> > space
>> > Feb 24 12:34:40 psytux kernel: [1.320148] [drm] TV-20: set mode NTSC 
>> > 480i 0
>> > Feb 24 12:34:40 psytux kernel: [1.466907] fb: conflicting fb hw usage 
>> > inteldrmfb vs VESA VGA - removing generic driver
>> > Feb 24 12:34:40 psytux kernel: [1.467017] fb1: inteldrmfb frame buffer 
>> > device
> 
> Screwed up handoff from vesafb to i915.  Should be fixed with today's
> 2.6.32-9 hopefully.  Although really you shouldn't be using vesafb.

Uhm, I don't think I'm using vesafb on purpose, am I?
My current /proc/cmdline is this: (no idea where I got that video= from)
BOOT_IMAGE=//vmlinuz-2.6.32-2-amd64 root=/dev/mapper/psytux-root ro video=i915
quiet vga=ext

I'll try 2.6.32-9 once it hits my mirror.

Cheers,
Uli
- --
- - Buck, when exactly did you lose your mind?
- - Three months ago. I woke up one morning married to a pineapple.
  An ugly pineapple... But I loved her!
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iQEcBAEBCAAGBQJLhWYrAAoJECLkKOvLj8sG7XQH/1Nir1cpi+fdEf6LLM6ekvMO
x5j53+uV3rZvwKbDU4UdOEwetMMQso4qffhAgNvFGwsjKO5skwaEO8YsCt7SB3Qf
zARMozNYxaqqo1w6VUap0upI7/rgQsMQoq4EmEJx3TE0ksRpyMiTX6znef/BeM+0
ZWvGv8nKk3u+0YjP0BJae31rVdc9MgbfvqlJM+fHjzZaVPUnZ18gi8o6hUkRXizo
zuv8LB3F6EdSrhMLCfd8E42sOfPtGwOcTlfQ8LpsvoKCkkObISn39zt+ahSPIn7Q
DlM3gu9iTY9TklgfnfhcpglSv1udAo5lO6vJl62mCi9UkuSPbtWW/dGY4aPSImc=
=Bre8
-END PGP SIGNATURE-



-- 
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/4b85662c.2090...@znc.in

Bug#569034: linux-2.6: Please support sh4 architecture

[Moritz Muehlenhoff]

Hi,

Nobuhiro Iwamatsu wrote:

> I attached new patch.
> Could you check ?

| patches/bugfix/sh4/fix-decompress-output-addr.patch |   27 +
| patches/debian/arch-sh4-fix-uimage-build.patch  |   10

These patches aren't in current linux-2.6 git, have they been submitted
upstream?

| patches/bugfix/sh4/fix_pte_write.patch  |   45 ++

This has been merged into 2.6.32.9, which has been pulled
into the linux-2.6 in the mean time, please respin your patch.

Cheers,
Moritz



-- 
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/20100224173909.ga7...@inutil.org

Bug#299567: kernel-image-2.6.8-2-686-smp: x86 has no uncompressed vmlinux (for oprofile)

[Moritz Muehlenhoff]

On Tue, Oct 06, 2009 at 01:43:03AM +0100, Ben Hutchings wrote:
> On Mon, 2009-10-05 at 11:57 +0200, Michal Suchanek wrote:
> > 2009/10/5 Ben Hutchings :
> > > While we still aren't providing an uncompressed vmlinux image, it is now
> > > possible to extract one from vmlinuz.  The following Python script does
> > > the job; give it the filename of the compressed image followed by the
> > > filename for the uncompressed image.
> > >
> > > Ben.
> > >
> > 
> > Yes, I thought this should be possible but did not find a tool for
> > decompressing the kernel.
> > 
> > Does the script also work for non-x86 architectures (or are there any
> > that do compress the kernel besides x86 and have usable precompiled
> > kernels)?
> 
> Don't know; I've never tried it.
> 
> > I guess if this is packaged with oprofile and pointers to the
> > decompression tool are added to its documentation this would resolve
> > the issue. Perhaps even oprofile upstream might be interested in
> > including the script.
> 
> Perhaps, though I expect they would prefer a C program.  It shouldn't
> take long to translate to C though.  Maybe I'll do that.

Maybe we should reassign this to the orofile package for now so that
they can include your Python script for Squeeze?

Cheers,
Moritz



-- 
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/20100224173920.gb7...@inutil.org

Bug#565225: don't assume RESUME partition will never change

[maximilian attems]

On Wed, 13 Jan 2010, Ben Hutchings wrote:

> Or even to store the UUID of the swap partition.
> 
> maks, is this another one for the libata transition script?

yes, indeed it is.



-- 
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/20100224173747.gh11...@stro.at

Fix for drm/agpgart init issue

[Bastian Blank]

Hi

Currently the drm drivers needs a correctly inizialized agpgart.
However there is no proper dependency possible, so this is quiet racy.
It fails with the following error:

| [drm:drm_fill_in_dev] *ERROR* Cannot initialize the agpgart module.

One quick fix is to make all the agp drivers built-in.

Bastian

-- 
Those who hate and fight must stop themselves -- otherwise it is not stopped.
-- Spock, "Day of the Dove", stardate unknown


signature.asc
Description: Digital signature

Bug#567468: md homehost

[Mario 'BitKoenig' Holbe]

On Wed, Feb 24, 2010 at 02:13:53PM +0100, Goswin von Brederlow wrote:
> grub.cfg (grub2) uses UUID for grub itself. But the kernel can be bootet
> with root=/dev/md0. But in that case where does it get the homehost from
> and since when does kernel raid autoconfig have a homehost?

The homehost attribute does only exist with v1 superblocks. And there is
no in-kernel auto-assembly for v1 superblocks.
v0.9 superblocks (for which in-kernel auto-assembly is deprecated but
still provided) have no homehost.


just my 2 cents
   Mario
-- 
The secret that the NSA could read the Iranian secrets was more
important than any specific Iranian secrets that the NSA could
read.   -- Bruce Schneier


signature.asc
Description: Digital signature

Bug#565696: initramfs-tools: Support for AoE

[maximilian attems]

On Sun, 17 Jan 2010, C.J. Adams-Collier wrote:

> Package: initramfs-tools
> Version: 0.92bubuntu53
> Severity: wishlist
> 
> 
> http://lists.debian.org/debian-kernel/2010/01/msg00368.html
> 

hmm this patch looks clean, not a real objection.

just missing a motivation, why one would want that?
do you have any refines since.

currently not sure why mailine initramfs-tools should care
about aoe or iscsi or fibre channel over ethernet,
but maybe someone else also wants to jump in for support!?

thanks + kind regards



-- 
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/20100224173015.gg11...@stro.at

Bug#566295: initramfs-tools: Deviation from Documentation/filesystems/nfs/nfsroot.txt WRT multiple net devs

[maximilian attems]

hello vagrant,

could you please review belows patch.
if you see no objection, I'd just merge it.

thanks maks

On Fri, 22 Jan 2010, Tim Small wrote:

> Package: initramfs-tools
> Version: 0.93.4
> Severity: normal
> Tags: patch
> 
> /usr/share/initramfs-tools/scripts/functions attempts to follow the
> semantics described in Documentation/filesystems/nfs/nfsroot.txt with
> respect to IP autoconfiguration, however a significant departure from
> the behaviour is that nfsroot.txt says:
> 
>   Name of network device to use.
> 
>  Default: If the host only has one device, it is used.
>  Otherwise the device is determined using
>  autoconfiguration. This is done by sending
>  autoconfiguration requests out of all devices,
>  and using the device that received the first reply.
> 
> 
> initramfs-tools currently requires a device to be hard-coded, but this
> is not much use if the network device is not known ahead of time.  If
> the device specified in either /etc/initramfs-tools/initramfs.conf or
> on the ip=xxx kernel command line.
> 
> Moreover a combination of the kernel commandline and the contents of
> /etc/initramfs-tools/initramfs.conf is currently used which can be
> misleading.
> 
> With the attached patch, it is possible to specify either:
> 
> DEVICE="all" or DEVICE="" in the /etc/initramfs-tools/initramfs.conf
> 
> The patch is against lenny, I've not had a chance to test it on sid but
> it looks like it should apply (modulo the change of the relevant env
> variable).
> 
> Many Thanks,
> 
> Tim.
> 
> -- Package-specific info:
> -- /proc/cmdline
> root=/dev/md0 ro console=tty0 
> 
> -- /proc/filesystems
>   ext3
>   vfat
>   fuseblk
> 
> -- lsmod
> Module  Size  Used by
> ftdi_sio   57736  0 
> pl2303 21508  0 
> ark311616004  0 
> usbserial  36592  3 ftdi_sio,pl2303,ark3116
> dm_hp_sw7168  0 
> dm_multipath   21392  1 dm_hp_sw
> dm_mirror  20608  0 
> dm_log 13956  1 dm_mirror
> battery16904  0 
> usbhid 45920  0 
> hid41792  1 usbhid
> ff_memless  9224  1 usbhid
> fuse   54176  1 
> enclosure  13632  0 
> ipt_REDIRECT6272  1 
> nls_utf86272  0 
> nls_cp437  11136  0 
> vfat   14976  0 
> fat51128  1 vfat
> nls_base   12932  4 nls_utf8,nls_cp437,vfat,fat
> radeon133920  2 
> drm91360  3 radeon
> vzethdev   14720  0 
> vznetdev   24456  1 
> simfs   8944  1 
> vzrst 122920  0 
> vzcpt 106424  0 
> tun15492  2 vzrst,vzcpt
> vzdquota   42740  1 [permanent]
> vzmon  31376  5 vzethdev,vznetdev,vzrst,vzcpt
> vzdev   7568  4 vzethdev,vznetdev,vzdquota,vzmon
> xt_length   6400  0 
> ipt_ttl 6144  0 
> xt_tcpmss   6656  0 
> xt_dscp 7168  0 
> iTCO_wdt   15696  1 
> authenc 9984  2 
> esp4   10880  2 
> aead   11904  2 authenc,esp4
> xfrm4_mode_tunnel   6912  4 
> deflate 7424  0 
> zlib_deflate   24088  1 deflate
> zlib_inflate   18944  1 deflate
> ctr 8832  0 
> twofish11136  0 
> twofish_common 18560  1 twofish
> camellia   25216  0 
> serpent23296  0 
> blowfish   13056  0 
> des_generic21376  0 
> cbc 7936  2 
> aes_x86_64 12416  2 
> aes_generic32552  1 aes_x86_64
> xcbc8968  0 
> sha256_generic 13696  0 
> sha1_generic6912  0 
> crypto_null 7680  2 
> af_key 32280  0 
> xt_tcpudp   7680  88 
> xt_DSCP 7808  34 
> ipt_MASQUERADE  6528  2 
> iptable_nat11652  1 
> nf_nat_ftp  7296  0 
> nf_nat 22548  4 
> ipt_REDIRECT,ipt_MASQUERADE,iptable_nat,nf_nat_ftp
> xt_TCPMSS   8576  3 
> ipt_LOG10372  46 
> ipt_REJECT  7552  0 
> iptable_mangle  8704  1 
> iptable_filter  8320  1 
> xt_multiport7424  0 
> xt_state6656  13 
> xt_limit7172  50 
> xt_conntrack8704  0 
> nf_conntrack_ftp   12728  1 nf_nat_ftp
> nf_conntrack_ipv4  24352  16 iptable_nat,nf_nat
> nf_conntrack   82688  7 
> iptable_nat,nf_nat_ftp,nf_nat,xt_state,xt_conntrack,nf_conntrack_ftp,nf_conntrack_ipv4
> ip_tables  21776  3 iptable_nat,iptable_mangle,iptable_filter
> x_tables   25736  17 
> ipt_REDIRECT,xt_length,ipt_ttl,xt_tcpmss,xt_dscp,xt_tcpudp,xt_DSCP,ipt_MASQUERAD

Processed: tagging 565386

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 565386 pending
Bug #565386 [initramfs-tools] mention file is in /etc/initramfs-tools
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
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.12670330603513.transcr...@bugs.debian.org

Bug#535008: configure_networking: support BOOTIF variable set by pxelinux

[maximilian attems]

hello vagrant,

pushing backlog out, finaly. thanks for your patience. :)

On Wed, 03 Feb 2010, Vagrant Cascadian wrote:

> updated patch against current master, using only shell, and with a cleaner
> method to convert BOOTF to a typical mac address.

cool, thanks.
applied
http://git.debian.org/?p=kernel/initramfs-tools.git;a=summary
 
> it may need special handling to make sure BOOTIF is exported, such as if run
> from the scripts/*-top/*.

hmmm ?? don't get that part, do you want an 
export BOOTIF= in init?
 
> since it's a whole block of code, maybe it could go into it's own function.

we don't need to be to pendantic..
 
> please consider applying this patch for squeeze. :)

done and thank you! hope you are all well, happy to read you!

greetings
maks



-- 
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/20100224171645.gd11...@stro.at

Bug#566401: Does not install firmware.agent into initramfs

[maximilian attems]

On Sat, 23 Jan 2010, Marco d'Itri wrote:

> 
> > But I'm actually surprised that not udev is taking care of installing
> > firmware.agent.
> Me too, but it has always worked this way.
> I would not mind doing it in a udev script (and I see no harm in adding
> this to the next release), but I do not want to add just for this a
> versioned conflict which will make upgrades more complex so
> initramfs-tools will need to be fixed anyway.

shall the udev hook take care of it to add it anyway
and i remove the addition?

thanks for the notice



-- 
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/20100224171926.ge11...@stro.at

Re: Bug#566401: Does not install firmware.agent into initramfs

[Marco d'Itri]

On Feb 24, maximilian attems  wrote:

> shall the udev hook take care of it to add it anyway
> and i remove the addition?
udev now installs it, but it cannot be removed from initramfs-tools
until there will be a versioned dependency which will guarantee a
working system (and I do not want to add one just for this).

-- 
ciao,
Marco


signature.asc
Description: Digital signature

Re: Xen dom0 2.6.32 stable branch

[Bastian Blank]

On Wed, Feb 24, 2010 at 03:42:32PM +0100, Bastian Blank wrote:
> http://hermes.jura.uni-tuebingen.de/~blank/debian/xen-test/

It seems to run.  But for a working xend, it needs a further update.

> 755fea06af4bab521a01062a7efaedfe99c36075  libxen-dev_3.4.3~rc2-1_amd64.deb
> ca67a4cb6213f0fe6930ead54f4b8c931c9f1b15  libxenstore3.0_3.4.3~rc2-1_amd64.deb
> c909fcf69b260e6897c9e33b8ead744cdc742f75  
> linux-headers-2.6.32-3-common-xen_2.6.32-9_amd64.deb
> a74f633d305a409deb36c1800c46f2a5402f23a3  
> linux-headers-2.6.32-3-xen-amd64_2.6.32-9_amd64.deb
> 21c6f3e5cbdb058d1508903552b3fee54eb3d35b  
> linux-image-2.6.32-3-xen-amd64_2.6.32-9_amd64.deb
> e4434a66faff150f9d4884a8b7c277c2df9c8040  xen-3_3.4.3~rc2-1.dsc
> a982b20d03a7cf0f87d60b7b4aae0aa4c5a93e07  xen-3_3.4.3~rc2-1.tar.gz
> a58c938408140d7a6ae07b7a2bf838f2cfbf87c6  xen-docs-3.4_3.4.3~rc2-1_all.deb
> e39e92b123354f0af32e3302341c23d6910e3a8b  
> xen-hypervisor-3.4-amd64_3.4.3~rc2-1_amd64.deb
> b07b02dd9abad66058ea2fb16a3c5ef3d70eb06c  xenstore-utils_3.4.3~rc2-1_amd64.deb
> 98d633b8cc4feeb0c6571fdc28e6c1730e305c2a  xen-utils-3.4_3.4.3~rc2-1_amd64.deb
dc4f295e056e62b87a0781b4861f62dd742c64dc  xen-common_3.4.2-3.dsc
42fe2a206a2663b4166f6a14dd15631c6cf77974  xen-common_3.4.2-3.tar.gz
c8c36d28c41d4d2bb78baf5299c08d94b202af21  xen-utils-common_3.4.2-3_all.deb

| host   : test
| release: 2.6.32-3-xen-amd64
| version: #1 SMP Wed Feb 24 13:59:02 UTC 2010
| machine: x86_64
| nr_cpus: 2
| nr_nodes   : 1
| cores_per_socket   : 2
| threads_per_core   : 1
| cpu_mhz: 1995
| hw_caps: 
bfebfbff:20100800::0140:e3bd::0001:
| virt_caps  : hvm
| total_memory   : 2039
| free_memory: 129
| node_to_cpu: node0:0-1
| node_to_memory : node0:129
| xen_major  : 3
| xen_minor  : 4
| xen_extra  : 
| xen_caps   : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 
hvm-3.0-x86_32p hvm-3.0-x86_64 
| xen_scheduler  : credit
| xen_pagesize   : 4096
| platform_params: virt_start=0x8000
| xen_changeset  : unavailable
| cc_compiler: gcc version 4.4.3 (Debian 4.4.3-2) 
| cc_compile_by  : waldi
| cc_compile_domain  : debian.org
| cc_compile_date: Wed Feb 24 14:37:59 UTC 2010
| xend_config_format : 4

However the machine seems to crash if I try to start X.

Bastian

-- 
Every living thing wants to survive.
-- Spock, "The Ultimate Computer", stardate 4731.3


signature.asc
Description: Digital signature

Bug#557033: linux-image-2.6.31-1-amd64: Kernel logs WARNING at hpet.c:390.

[maximilian attems]

hello

[ please keep bug report on cc this is not private conversation
  and got lost in such! ]

On Sat, 06 Feb 2010, Gerry Butler wrote:

> Thank you. 
> 
> I can't start linux at all with 2.6.32. 
> 
> apt-get warned that some drivers used on the system are unavailable. 

you seem to confuse firmware and drivers.
and rtl8168d can not be related to booting unless you are netbooting,
which i kind of doubt.
 
> It will be a week or more before I can devote more time to it. Anyhow, at 
> this point I don't know how to get the required drivers. When I installed 
> 2.6.31, I didn't need to get any additional drivers. 
> 
> When I try to boot, very early in the boot process it dumps a trace to the 
> screen then freezes. ctrl-alt-del does nothing, and I need to hit the system 
> reset button to continue (ie, to reboot). 
> 
> This is how I installed it:
> 
>   apt-get -t sid install linux-image-2.6-amd64
> 
> I'm fairly new to linux (coming from Windows), so I'm not sure if I've just 
> made some stupid mistake.

well unless you can't reproduce the message with 2.6.32
this bug can be closed.

for assistance on the upgrade just use the #debian irc channel.
it is for user support.

kind regards

-- 
maks



-- 
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/20100224171000.gc11...@stro.at

Processed: tagging 535008

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 535008 pending
Bug #535008 [initramfs-tools] configure_networking: support BOOTIF variable set 
by pxelinux
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
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.126703185430016.transcr...@bugs.debian.org

Bug#571215: Backlight turned off during bootup

[Julien Cristau]

On Wed, Feb 24, 2010 at 12:58:54 +0100, Uli Schlachter wrote:

> Feb 24 12:34:40 psytux kernel: [0.548357] vesafb: framebuffer at 
> 0x8000, mapped to 0xc9001098, using 5120k, total 5120k
> Feb 24 12:34:40 psytux kernel: [0.548360] vesafb: mode is 1280x1024x32, 
> linelength=5120, pages=0
> Feb 24 12:34:40 psytux kernel: [0.548362] vesafb: scrolling: redraw
> Feb 24 12:34:40 psytux kernel: [0.548364] vesafb: Truecolor: 
> size=8:8:8:8, shift=24:16:8:0
> Feb 24 12:34:40 psytux kernel: [0.588241] Console: switching to colour 
> frame buffer device 160x64
> Feb 24 12:34:40 psytux kernel: [0.628004] fb0: VESA VGA frame buffer 
> device
[...]
> Feb 24 12:34:40 psytux kernel: [0.732304] [drm] Initialized drm 1.1.0 
> 20060810
> Feb 24 12:34:40 psytux kernel: [0.743618] i915 :00:02.0: PCI INT A -> 
> GSI 16 (level, low) -> IRQ 16
> Feb 24 12:34:40 psytux kernel: [0.743622] i915 :00:02.0: setting 
> latency timer to 64
> Feb 24 12:34:40 psytux kernel: [0.758588]   alloc irq_desc for 29 on node 
> -1
> Feb 24 12:34:40 psytux kernel: [0.758592]   alloc kstat_irqs on node -1
> Feb 24 12:34:40 psytux kernel: [0.758601] i915 :00:02.0: irq 29 for 
> MSI/MSI-X
> Feb 24 12:34:40 psytux kernel: [0.758608] [drm] set up 63M of stolen space
> Feb 24 12:34:40 psytux kernel: [1.320148] [drm] TV-20: set mode NTSC 480i > 0
> Feb 24 12:34:40 psytux kernel: [1.466907] fb: conflicting fb hw usage 
> inteldrmfb vs VESA VGA - removing generic driver
> Feb 24 12:34:40 psytux kernel: [1.467017] fb1: inteldrmfb frame buffer 
> device

Screwed up handoff from vesafb to i915.  Should be fixed with today's
2.6.32-9 hopefully.  Although really you shouldn't be using vesafb.

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#571242: linux-image-2.6.32-2-amd64: running 8 copies of bonnie deadlocks(?) in sync

[John Hughes]

Package: linux-2.6
Version: 2.6.32-8
Severity: normal


Running 8 copies of bonnie++ on 8 different filesystems on 8 disks seems
to produce a deadlock in sync(2).

Initialy all the bonnie++ processes seem to be running ok, but after a while
only 2-3 of the disks are showing any I/O activiy and the dmesg output
shows:

[  360.284601] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  360.284693] bonnieD 88034ac0f9f0 0  2941   2937 0x0008
[  360.284697]  88063d4b54c0 0082 880338e8fe88 
880338e8fe84
[  360.284700]  0003 000155c0 f8a0 
880338e8ffd8
[  360.284703]  000155c0 000155c0 88033cf5cdb0 
88033cf5d0a8
[  360.284706] Call Trace:
[  360.284715]  [] ? __mutex_lock_common+0x10b/0x17b
[  360.284720]  [] ? try_to_wake_up+0x249/0x259
[  360.284722]  [] ? mutex_lock+0x1a/0x31
[  360.284726]  [] ? sync_filesystems+0x13/0xe3
[  360.284728]  [] ? sys_sync+0x12/0x2e
[  360.284733]  [] ? system_call_fastpath+0x16/0x1b
[  360.284736] INFO: task bonnie:2946 blocked for more than 120 seconds.

At this point any attempt to use "sync" hangs.

The system seems to work again if the bonnie++ processes are killed.


-- Package-specific info:
** Version:
Linux version 2.6.32-2-amd64 (Debian 2.6.32-8) (b...@decadent.org.uk) (gcc 
version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Fri Feb 12 00:01:47 UTC 2010

** Command line:
BOOT_IMAGE=/vmlinuz-2.6.32-2-amd64 root=/dev/mapper/caronia_vg-root ro quiet

** Not tainted

** Kernel log:
[  181.785606] kjournald starting.  Commit interval 5 seconds
[  181.791652] EXT3 FS on sdo, internal journal
[  181.791657] EXT3-fs: mounted filesystem with ordered data mode.
[  181.797389] kjournald starting.  Commit interval 5 seconds
[  181.797486] EXT3 FS on sdp, internal journal
[  181.797491] EXT3-fs: mounted filesystem with ordered data mode.
[  181.802969] kjournald starting.  Commit interval 5 seconds
[  181.803069] EXT3 FS on sdq, internal journal
[  181.803074] EXT3-fs: mounted filesystem with ordered data mode.
[  360.284498] INFO: task bonnie:2941 blocked for more than 120 seconds.
[  360.284601] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  360.284693] bonnieD 88034ac0f9f0 0  2941   2937 0x0008
[  360.284697]  88063d4b54c0 0082 880338e8fe88 
880338e8fe84
[  360.284700]  0003 000155c0 f8a0 
880338e8ffd8
[  360.284703]  000155c0 000155c0 88033cf5cdb0 
88033cf5d0a8
[  360.284706] Call Trace:
[  360.284715]  [] ? __mutex_lock_common+0x10b/0x17b
[  360.284720]  [] ? try_to_wake_up+0x249/0x259
[  360.284722]  [] ? mutex_lock+0x1a/0x31
[  360.284726]  [] ? sync_filesystems+0x13/0xe3
[  360.284728]  [] ? sys_sync+0x12/0x2e
[  360.284733]  [] ? system_call_fastpath+0x16/0x1b
[  360.284736] INFO: task bonnie:2946 blocked for more than 120 seconds.
[  360.284807] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  360.284890] bonnieD 88034ac4f9f0 0  2946   2937 0x
[  360.284893]  88063e4a0e20 0082 880338051e88 
880338051e84
[  360.284895]  0003 000155c0 f8a0 
880338051fd8
[  360.284898]  000155c0 000155c0 88033cf5bf90 
88033cf5c288
[  360.284900] Call Trace:
[  360.284903]  [] ? __mutex_lock_common+0x10b/0x17b
[  360.284905]  [] ? try_to_wake_up+0x249/0x259
[  360.284907]  [] ? mutex_lock+0x1a/0x31
[  360.284909]  [] ? sync_filesystems+0x13/0xe3
[  360.284911]  [] ? sys_sync+0x12/0x2e
[  360.284914]  [] ? system_call_fastpath+0x16/0x1b
[  360.284916] INFO: task bonnie:2947 blocked for more than 120 seconds.
[  360.284983] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  360.285066] bonnieD 88034ac755c0 0  2947   2937 0x
[  360.285068]  88033cf5d4c0 0082 88033822be88 
88033822be84
[  360.285071]  88033cfebb80 81047f3d f8a0 
88033822bfd8
[  360.285073]  000155c0 000155c0 88033cf5b880 
88033cf5bb78
[  360.285076] Call Trace:
[  360.285078]  [] ? finish_task_switch+0x3a/0xa7
[  360.285081]  [] ? __mutex_lock_common+0x10b/0x17b
[  360.285083]  [] ? mutex_lock+0x1a/0x31
[  360.285085]  [] ? sync_filesystems+0x13/0xe3
[  360.285087]  [] ? sys_sync+0x12/0x2e
[  360.285090]  [] ? system_call_fastpath+0x16/0x1b
[  360.285092] INFO: task bonnie:2948 blocked for more than 120 seconds.
[  360.285159] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  360.285242] bonnieD  0  2948   2937 0x
[  360.285245]  814491f0 0086 88033cf5d4f8 
88034ac155c0
[  360.285247]  88034ac155c0  f8a0 
880338223fd8
[  360.285250]  000155c0 000155c0 88033cf5d4c0 
88033cf5d

Re: linux-firmware-nonfree: Add prism54 softmac firmware

[Chase Douglas]

> > I checked
> > the lucid kernel and we do have prism54 built as a module still. So, are
> > we going to leave the prism54 module in, in which case we need to
> > restore the prism54 firmware?
> 
> Yes I'd restore the prism54 firmware until the coast is clear with
> p54pci for all. Its not the case so far as per reports.
> 
> > Or are we going to remove it, in which
> > case the firmware package I uploaded was fine? I'm assuming at this
> > point we'll be leaving it in though.
> 
> I'd say keep it for now.

We've decided to keep things as is from Karmic to Lucid in an effort to
not screw things up for people who already have their wireless working.
This means we'll be shipping both prism54 and p54* drivers.

I have uploaded a new linux-firmware-nonfree package that contains all
the prism54 firmware for all the drivers:

http://kernel.ubuntu.com/~cndougla/linux-firmware-nonfree/

Thanks,
Chase


-- 
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/1267023249.32025.26.ca...@cndougla-ubuntu

Bug#571215: Backlight turned off during bootup

[maximilian attems]

On Wed, Feb 24, 2010 at 03:29:04PM +0100, Uli Schlachter wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> maximilian attems wrote:
> > On Wed, Feb 24, 2010 at 12:58:54PM +0100, Uli Schlachter wrote:
> >> This morning when I booted my laptop, right after grub was done, the 
> >> backlight
> >> turned off. I collected the attached info by entering my HDD passphrase 
> >> blindly
> >> and starting up X (which partly worked but was damn slow).
> >>
> >> Kernel is 2.6.32-trunk-amd64.
> > 
> > old, newer one is available in unstable: 2.6.32-8, check against it.
> 
> Uhm, I might be blind...
> I installed the following. I'll report back with the results this
> evening.
> 
> [AKTUALISIERUNG] linux-image-2.6-amd64 2.6.32+23 -> 2.6.32+24

please corret your apt sources or whatever, I spoke about unstable
and there you have linux-image-2.6.32-2-amd64
 
> ii  hotkey-setup0.1-23
> auto-configures laptop hotkeys

nuke it and reboot, probably cures your trouble not to have 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/20100224143652.gk15...@baikonur.stro.at

Bug#571215: Backlight turned off during bootup

[Uli Schlachter]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

maximilian attems wrote:
> On Wed, Feb 24, 2010 at 12:58:54PM +0100, Uli Schlachter wrote:
>> This morning when I booted my laptop, right after grub was done, the 
>> backlight
>> turned off. I collected the attached info by entering my HDD passphrase 
>> blindly
>> and starting up X (which partly worked but was damn slow).
>>
>> Kernel is 2.6.32-trunk-amd64.
> 
> old, newer one is available in unstable: 2.6.32-8, check against it.

Uhm, I might be blind...
I installed the following. I'll report back with the results this
evening.

[AKTUALISIERUNG] linux-image-2.6-amd64 2.6.32+23 -> 2.6.32+24

> also do you have hotkey-setup installed, please post
> dpkg -l hotkey-setup

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion
Description
+++-===-===-==
ii  hotkey-setup0.1-23
auto-configures laptop hotkeys

- --
- - Buck, when exactly did you lose your mind?
- - Three months ago. I woke up one morning married to a pineapple.
  An ugly pineapple... But I loved her!
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iQEcBAEBCAAGBQJLhTetAAoJECLkKOvLj8sGHr0H/AxR8fFEfXjQh7595yujIBve
HoeYEwaBUbkJ9GM4N3D3IHecidR5eRzFtOCl1UAb+gPs6PgWdjMRhDDO43RBaLpq
0FDCJ+/IzD8L0iNK5cA95vFiYlScoKl6a+5SMJMUnTT9xXK6RE1rqyOthfIw6seN
rXEAV4leBO+WTXA8ACBunC9xStZjeHyv/tVuLz+tC3FID6qAEHAPCH3bpbINMGCH
vq9CyGOW02Yl96mVnIhB3IgVZAuhKDOHMy/3lS+82nn7cduTvsQv028GSRdDNmYt
r76Qt2be+NIDREZxyFpk3rtd+Lh5JjIgsbAlVNEEqWK2DpSF6YhqQLu9oqqdOj8=
=kwmP
-END PGP SIGNATURE-



-- 
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/4b8537b0.5090...@znc.in

Re: Xen dom0 2.6.32 stable branch

[Bastian Blank]

On Wed, Feb 24, 2010 at 01:53:09PM +, Ian Campbell wrote:
> On Wed, 2010-02-24 at 14:39 +0100, Bastian Blank wrote:
> > Already on it. It seems to need a hypervisor update as well.
> I believe this branch needs either Xen 4.0 or 3.4 with a patch
> backported for the new dom0 APIC interfaces, I think that it is in
> xen-3.4-testing.hg but not an actual release yet. Do you need me to find
> the patch in question?

It looks like this is the setup_gsi command, which is in 3.4.3-rc2.

> Once you are at the point at which additional testing etc is useful
> please let me know, I'd be glad to give it a go!

http://hermes.jura.uni-tuebingen.de/~blank/debian/xen-test/

755fea06af4bab521a01062a7efaedfe99c36075  libxen-dev_3.4.3~rc2-1_amd64.deb
ca67a4cb6213f0fe6930ead54f4b8c931c9f1b15  libxenstore3.0_3.4.3~rc2-1_amd64.deb
c909fcf69b260e6897c9e33b8ead744cdc742f75  
linux-headers-2.6.32-3-common-xen_2.6.32-9_amd64.deb
a74f633d305a409deb36c1800c46f2a5402f23a3  
linux-headers-2.6.32-3-xen-amd64_2.6.32-9_amd64.deb
21c6f3e5cbdb058d1508903552b3fee54eb3d35b  
linux-image-2.6.32-3-xen-amd64_2.6.32-9_amd64.deb
9aba2b365cdfe1533d7e826ecef5daf77df646f2  qemu-xen_3.4.2-1.debian.tar.gz
cb43a8ae7ee29bdcfd07eb4ae866ce5bc6e8e38d  qemu-xen_3.4.2.orig.tar.gz
3d5a7315b1a2dd080c5206a322ebc74caefb79e9  xen-3_3.4.3~rc2-1_amd64.build
ac26e84dbe38182409ac09e451fc102264067f6c  xen-3_3.4.3~rc2-1_amd64.changes
e4434a66faff150f9d4884a8b7c277c2df9c8040  xen-3_3.4.3~rc2-1.dsc
a982b20d03a7cf0f87d60b7b4aae0aa4c5a93e07  xen-3_3.4.3~rc2-1.tar.gz
a58c938408140d7a6ae07b7a2bf838f2cfbf87c6  xen-docs-3.4_3.4.3~rc2-1_all.deb
e39e92b123354f0af32e3302341c23d6910e3a8b  
xen-hypervisor-3.4-amd64_3.4.3~rc2-1_amd64.deb
b07b02dd9abad66058ea2fb16a3c5ef3d70eb06c  xenstore-utils_3.4.3~rc2-1_amd64.deb
98d633b8cc4feeb0c6571fdc28e6c1730e305c2a  xen-utils-3.4_3.4.3~rc2-1_amd64.deb

Bastian

-- 
Our way is peace.
-- Septimus, the Son Worshiper, "Bread and Circuses",
   stardate 4040.7.


signature.asc
Description: Digital signature

Bug#571215: Backlight turned off during bootup

[maximilian attems]

On Wed, Feb 24, 2010 at 12:58:54PM +0100, Uli Schlachter wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> Package: udev
> Version: 151-2
> thanks
> 
> Yesterday, I had the following upgrades:
> ===
> [AKTUALISIERUNG] gstreamer0.10-alsa 0.10.25-7 -> 0.10.26-1
> [AKTUALISIERUNG] gstreamer0.10-plugins-base 0.10.25-7 -> 0.10.26-1
> [AKTUALISIERUNG] gstreamer0.10-plugins-good 0.10.17-1 -> 0.10.18-1
> [AKTUALISIERUNG] gstreamer0.10-x 0.10.25-7 -> 0.10.26-1
> [AKTUALISIERUNG] libapr1 1.3.8-1 -> 1.4.2-3
> [AKTUALISIERUNG] libcompress-raw-zlib-perl 2.023-1 -> 2.024-1
> [AKTUALISIERUNG] libcompress-zlib-perl 2.022-1 -> 2.024-1
> [AKTUALISIERUNG] libgstreamer-plugins-base0.10-0 0.10.25-7 -> 0.10.26-1
> [AKTUALISIERUNG] libgstreamer0.10-0 0.10.25-4+b1 -> 0.10.26-1
> [AKTUALISIERUNG] libgudev-1.0-0 150-2 -> 151-2
> [AKTUALISIERUNG] libio-compress-perl 2.022-1 -> 2.024-1
> [AKTUALISIERUNG] libmailtools-perl 2.05-1 -> 2.06-1
> [AKTUALISIERUNG] libudev0 150-2 -> 151-2
> [AKTUALISIERUNG] python-gst0.10 0.10.17-1+b1 -> 0.10.18-1
> [AKTUALISIERUNG] traceroute 2.0.13-2 -> 1:2.0.13-3
> [AKTUALISIERUNG] udev 150-2 -> 151-2
> ===
> 
> (After this, the initrd was regenerated)
> 
> This morning when I booted my laptop, right after grub was done, the backlight
> turned off. I collected the attached info by entering my HDD passphrase 
> blindly
> and starting up X (which partly worked but was damn slow).
> 
> Kernel is 2.6.32-trunk-amd64.

old, newer one is available in unstable: 2.6.32-8, check against it.

also do you have hotkey-setup installed, please post
dpkg -l hotkey-setup



-- 
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/20100224133046.gj15...@baikonur.stro.at

Re: Xen dom0 2.6.32 stable branch

[Ian Campbell]

On Wed, 2010-02-24 at 14:39 +0100, Bastian Blank wrote:
> On Wed, Feb 24, 2010 at 01:02:28PM +, Ian Campbell wrote:
> > On Wed, 2010-02-24 at 13:05 +0100, Josip Rodin wrote:
> > > This is the new upstream default branch, with paravirt_ops dom0, and based
> > > on 2.6.32-stable, so it's presumably suitable for inclusion as a new patch
> > > that would restore our packages linux-image-2.6-xen-{686,amd64} which were
> > > previously based on forward-ported .18 dom0 patches. Yay.
> > Yes, I was planning to take a look at this sometime soon unless someone
> > else (Bastian?) gets there first.
> 
> Already on it. It seems to need a hypervisor update as well.

Awesome!

I believe this branch needs either Xen 4.0 or 3.4 with a patch
backported for the new dom0 APIC interfaces, I think that it is in
xen-3.4-testing.hg but not an actual release yet. Do you need me to find
the patch in question?

Once you are at the point at which additional testing etc is useful
please let me know, I'd be glad to give it a go!

Ian.

-- 
Ian Campbell
Current Noise: My Dying Bride - Into The Lake Of Ghosts

Even if you persuade me, you won't persuade me.
-- Aristophanes


-- 
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/1267019589.11737.7809.ca...@zakaz.uk.xensource.com

Processed: Re: Bug#571215: Backlight turned off during bootup

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 571215 linux-2.6
Bug #571215 [udev] Backlight turned off during bootup
Bug reassigned from package 'udev' to 'linux-2.6'.
Bug No longer marked as found in versions udev/151-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
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.126701893020173.transcr...@bugs.debian.org

Bug#567468: md homehost

[Goswin von Brederlow]

Neil Brown  writes:

> On Tue, 23 Feb 2010 07:27:00 +0100
> martin f krafft  wrote:
>> The only issue homehost protects against, I think, is machines that
>> use /dev/md0 directly from grub.conf or fstab.
>
> That is exactly correct.  If no code or config file depends on a name like
> /dev/mdX or /dev/md/foo, then you don't need to be concerned about the whole
> homehost thing.
> You can either mount by fs-uuid, or mount e.g.
>/dev/disk/by-id/md-uuid-8fd0af3f:4fbb94ea:12cc2127:f9855db5 

What if you have two raids (one local, one from the other hosts that
broke down) and both have LVM on it with /dev/vg/root?

Shouldn't it only assemble the local raid (as md0 or whatever) and then
only start the local volume group? If it assembles the remote raid as
/dev/md127 as well then lvm will have problems and the boot will likely
(even randomly) go wrong since only one VG can be activated.

I think it is pretty common for admins to configure LVM to the same
volume group name on different systems. So if you consider raids being
pluged into other systems please keep this in mind.

MfG
Goswin



-- 
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/87d3zulpj7@frosties.localdomain

Re: Xen dom0 2.6.32 stable branch

[Bastian Blank]

On Wed, Feb 24, 2010 at 01:02:28PM +, Ian Campbell wrote:
> On Wed, 2010-02-24 at 13:05 +0100, Josip Rodin wrote:
> > This is the new upstream default branch, with paravirt_ops dom0, and based
> > on 2.6.32-stable, so it's presumably suitable for inclusion as a new patch
> > that would restore our packages linux-image-2.6-xen-{686,amd64} which were
> > previously based on forward-ported .18 dom0 patches. Yay.
> Yes, I was planning to take a look at this sometime soon unless someone
> else (Bastian?) gets there first.

Already on it. It seems to need a hypervisor update as well.

Bastian

-- 
Murder is contrary to the laws of man and God.
-- M-5 Computer, "The Ultimate Computer", stardate 4731.3


-- 
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/20100224133908.gb23...@wavehammer.waldi.eu.org

Bug#567468: md homehost

[Goswin von Brederlow]

martin f krafft  writes:

> also sprach Goswin von Brederlow  [2010.02.23.0831 +0100]:
>> Both filesystems and LVM have UUIDs. Does dm-crypt / LUKS have one
>> too?
>
> LVM already identifies PVs using UUIDs, so if you are using
> anything-on-LVM-on-md, you need not worry about device names anyway.
>
> dm-crypt currently needs to be told explicitly to use a base device
> using /dev/disk/by-uuid if you want it to be flexible.
>
> The only issue homehost protects against, I think, is machines that
> use /dev/md0 directly from grub.conf or fstab.

grub.cfg (grub2) uses UUID for grub itself. But the kernel can be bootet
with root=/dev/md0. But in that case where does it get the homehost from
and since when does kernel raid autoconfig have a homehost?

Any other case you have an initramfs that can use LABEL or UUID. Same
for fstab.

MfG
Goswin



-- 
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/87y6iilqsu@frosties.localdomain

Re: Xen dom0 2.6.32 stable branch

[Ian Campbell]

On Wed, 2010-02-24 at 13:05 +0100, Josip Rodin wrote:
> Hi,
> 
> Just in case I'm the first to notice, we now have:
> http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=shortlog;h=refs/heads/xen/stable
> 
> This is the new upstream default branch, with paravirt_ops dom0, and based
> on 2.6.32-stable, so it's presumably suitable for inclusion as a new patch
> that would restore our packages linux-image-2.6-xen-{686,amd64} which were
> previously based on forward-ported .18 dom0 patches. Yay.

Yes, I was planning to take a look at this sometime soon unless someone
else (Bastian?) gets there first.

Ian.
-- 
Ian Campbell
Current Noise: My Dying Bride - She Is The Dark

F:  When into a room I plunge, I
Sometimes find some VIOLET FUNGI.
Then I linger, darkly brooding
On the poison they're exuding.
-- The Roguelet's ABC


-- 
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/1267016548.11737.7756.ca...@zakaz.uk.xensource.com

Bug#552706: BUG: soft lockup - CPU#0 stuck for 61s! - :nfs:nfs_access_cache_shrinker

[Bernd Zeimetz]

Moritz Muehlenhoff wrote:
> Does this error still occur with 2.6.26-21 from the latest point
> update, which introduced two patches which might have fixed this error?

We'll give it a try as soon as time permits, the machine is turned off right now
and other models are in production and not using NFS.

-- 
 Bernd ZeimetzDebian GNU/Linux Developer
 http://bzed.dehttp://www.debian.org
 GPG Fingerprints: 06C8 C9A2 EAAD E37E 5B2C BE93 067A AD04 C93B FF79
   ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F



-- 
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/4b851f0f.7030...@debian.org

Processed: tagging 550562

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # Automatically generated email from bts, devscripts version 2.10.35lenny7
> tags 550562 + pending
Bug #550562 [linux-2.6] radeon: system freeze on some OpenGl functions
Bug #550977 [linux-2.6] radeon DRI driver corrupts memory
Bug #559037 [linux-2.6] radeon DRI driver corrupts memory
Bug #560126 [linux-2.6] xserver-xorg-video-radeon: Launching GL Apps Corrupts 
System
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
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.126701326925560.transcr...@bugs.debian.org

Processed: tagging 550562

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 550562 - moreinfo
Bug #550562 [linux-2.6] radeon: system freeze on some OpenGl functions
Bug #550977 [linux-2.6] radeon DRI driver corrupts memory
Bug #559037 [linux-2.6] radeon DRI driver corrupts memory
Bug #560126 [linux-2.6] xserver-xorg-video-radeon: Launching GL Apps Corrupts 
System
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
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.126701313215378.transcr...@bugs.debian.org

Xen dom0 2.6.32 stable branch

[Josip Rodin]

Hi,

Just in case I'm the first to notice, we now have:
http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=shortlog;h=refs/heads/xen/stable

This is the new upstream default branch, with paravirt_ops dom0, and based
on 2.6.32-stable, so it's presumably suitable for inclusion as a new patch
that would restore our packages linux-image-2.6-xen-{686,amd64} which were
previously based on forward-ported .18 dom0 patches. Yay.

-- 
 2. That which causes joy or happiness.


-- 
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/20100224120553.ga2...@orion.carnet.hr

Bug#571096: marked as done (Badness after waking up on iBook G4)

[maximilian attems]

On Tue, 23 Feb 2010, Philipp Kern wrote:

> maximilian,
> 
> am Tue, Feb 23, 2010 at 05:42:28PM +0100 hast du folgendes geschrieben:
> > the double resume happened a lot on gnome desktops afaik.
> > this points to gnome-power-manager or such, are you running latest
> > 2.6.28.3-2 ??
> 
> I do.

hmm strange, this one fixed it for me, do you want this reassigned to it
so that gnome maintainer can ask for specific hints?



-- 
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/20100224105716.gl12...@stro.at

Bug#571085: no write access in /home reiserfs (encrypted) 2.6.32-2-686

[robi]

hello,
I think is a bug from kernel because if I boot with kernel 2.6.26-2-686 I don't 
get this error.
Which kind of information do you need?
Also, I posted this message in debian-user mailing list but nobody answered yet.
thank you,
robi


On Tue, 23 Feb 2010 13:01:01 +0100
maximilian attems  wrote:

> reassign 571085 linux-2.6
> tags 571085 moreinfo
> stop
> 
> On Tue, Feb 23, 2010 at 12:03:57PM +0100, robi wrote:
> > Package: linux-image-2.6.32-2-686 
> > hello,
> > I have upgraded kernel to 2.6.32-2-686 from 2.6.26-2-686.
> > After that, when I boot my laptop (debian lenny) I get the error about no 
> > write access to /home.
> > It's mounted with rw options and it's encrypted from /dev/mapper/dat-home.
> > After rebooting the system, everything works well without problems, 
> > but if I switch off my laptop, next time I boot I get the same error. 
> > Please, could you help me?
> > thank you
> > robi
> 
> this report misses a lot of information, please follow up with reportbug:
> reportbug -N 571085
> 
> also why do you think that this is a kernel bug?
> no evindence so far, it seem you better need support in that case
> ask in debian-user mailinglist.
> 
> thanks



-- 
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/20100224094842.05062ea4.r...@ecn.org