Processing of tgt_1.0.4-1_amd64.changes

2010-05-05 Thread Archive Administrator 
tgt_1.0.4-1_amd64.changes uploaded successfully to localhost
along with the files:
  tgt_1.0.4-1.dsc
  tgt_1.0.4.orig.tar.gz
  tgt_1.0.4-1.debian.tar.gz
  tgt_1.0.4-1_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/e1o9zyw-0006dv...@ries.debian.org

Processed: Re: Bug#580265: Failed netinst

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

 reassign 580265 linux-2.6 2.6.32-9
Bug #580265 [installation-reports] Failed netinst
Bug reassigned from package 'installation-reports' to 'linux-2.6'.
Bug #580265 [linux-2.6] Failed netinst
There is no source info for the package 'linux-2.6' at version '2.6.32-9' with 
architecture ''
Unable to make a source version for version '2.6.32-9'
Bug Marked as found in versions 2.6.32-9.
 thanks
Stopping processing here.

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


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

Re: Bug#580265: Failed netinst

2010-05-05 Thread Frans Pop 
reassign 580265 linux-2.6 2.6.32-9
thanks

On Tuesday 04 May 2010, Gmail Notifier wrote:
 00:19.0 Ethernet controller [0200]: Intel Corporation 82578DC Gigabit
 Network Connection [8086:10f0] (rev 06)
         Subsystem: Intel Corporation Device [8086:0037]
         Kernel driver in use: e1000e

 Comments/Problems:

 Did not find my e1000e network interface, even after selecting it
 explicitly from the list. After installing without using a net
 connection, a simple modprobe e1000e and dhclient made the net
 connection work. The following were added automaticly to /etc/modules
 by the installation:

 e100
 e1000
 e1000e

 But booting with these in /etc/modules did not make the network
 interface work. Had to do modprobe e1000e manually after each boot.

This sounds like a kernel issue. Reassigning to the kernel team.

Cheers,
FJP


--
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/201005051041.20978.elen...@planet.nl

Bug#576635: Same here

2010-05-05 Thread Oren Held 

I'm experiencing the same with linux-image-2.6.32-3-amd64 : 2.6.32-9.

Rebooting back to the good linux-image-2.6.32-1-amd64 makes it work.

I think this bug should have higher severity priority.



--
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/4be1302b.3030...@held.org.il

Bug#576635: Same here

2010-05-05 Thread Oren Held 

Maybe it has to do with this issue:

http://bugzilla.kernel.org/show_bug.cgi?id=15424 (contains a link to the 
patch inside)




--
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/4be13800.8000...@held.org.il

tgt_1.0.4-1_amd64.changes ACCEPTED

2010-05-05 Thread Archive Administrator 



Accepted:
tgt_1.0.4-1.debian.tar.gz
  to main/t/tgt/tgt_1.0.4-1.debian.tar.gz
tgt_1.0.4-1.dsc
  to main/t/tgt/tgt_1.0.4-1.dsc
tgt_1.0.4-1_amd64.deb
  to main/t/tgt/tgt_1.0.4-1_amd64.deb
tgt_1.0.4.orig.tar.gz
  to main/t/tgt/tgt_1.0.4.orig.tar.gz


Override entries for your package:
tgt_1.0.4-1.dsc - source net
tgt_1.0.4-1_amd64.deb - optional net

Announcing to debian-devel-chan...@lists.debian.org


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/e1o9bbf-nm...@ries.debian.org

Bug#580265: Failed netinst

2010-05-05 Thread Notifier 
On Wed, May 5, 2010 at 10:41 AM, Frans Pop elen...@planet.nl wrote:
 reassign 580265 linux-2.6 2.6.32-9
 thanks

 On Tuesday 04 May 2010, Gmail Notifier wrote:
 00:19.0 Ethernet controller [0200]: Intel Corporation 82578DC Gigabit
 Network Connection [8086:10f0] (rev 06)
 Subsystem: Intel Corporation Device [8086:0037]
 Kernel driver in use: e1000e

 Comments/Problems:

 Did not find my e1000e network interface, even after selecting it
 explicitly from the list. After installing without using a net
 connection, a simple modprobe e1000e and dhclient made the net
 connection work. The following were added automaticly to /etc/modules
 by the installation:

 e100
 e1000
 e1000e

 But booting with these in /etc/modules did not make the network
 interface work. Had to do modprobe e1000e manually after each boot.

 This sounds like a kernel issue. Reassigning to the kernel team.

 Cheers,
 FJP


I have a correction to make, it was only the DHCP part that didn't
work when booting into the installed kernel. The e1000e driver is
loaded correctly, and the other (incorrect) drivers can't be seen when
doing lsmod. The detection in the installation is still broken
though.

If it's any help, the installed kernel is 2.6.32-trunk-amd64, and the
one used on the USB key is 2.6.30-2-amd64. The network also worked
fine with the installed kernel being 2.6.32-3-amd64. I remember
reading that Linus and Molnar had problems with this driver in one of
the latest kernels, maybe updating the USB key kernel would fix it.

When making the USB key I used the boot.img.gz from
http://ftp.nl.debian.org/debian/dists/testing/main/installer-amd64/current/images/hd-media/
and the netinstall image
http://cdimage.debian.org/cdimage/squeeze_di_alpha1/amd64/iso-cd/debian-testing-amd64-netinst.iso



-- 
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/k2w63ae10171005050312y9798ebb6wcb65af4f79f7e...@mail.gmail.com

Bug#580026: [drm/i915] invalid opcode: 0000 [#1] SMP in i915_gem_execbuffer

2010-05-05 Thread Thiemo Nagel 

On 05/03/2010 03:20 PM, Ben Hutchings wrote:

It was only accepted earlier today, so it may take another day to
propagate.


I've installed it.  Let's see whether I hit the problem again.  I assume 
the odds are low, though, as I've only seen it once in 2.6.32-4.


Cheers, Thiemo



--
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/4be14ef2.5060...@googlemail.com

Bug#580265: Failed netinst

2010-05-05 Thread Notifier 
On Wed, May 5, 2010 at 12:12 PM, Notifier notif...@gmail.com wrote:
 On Wed, May 5, 2010 at 10:41 AM, Frans Pop elen...@planet.nl wrote:
 reassign 580265 linux-2.6 2.6.32-9
 thanks

 On Tuesday 04 May 2010, Gmail Notifier wrote:
 00:19.0 Ethernet controller [0200]: Intel Corporation 82578DC Gigabit
 Network Connection [8086:10f0] (rev 06)
         Subsystem: Intel Corporation Device [8086:0037]
         Kernel driver in use: e1000e

 Comments/Problems:

 Did not find my e1000e network interface, even after selecting it
 explicitly from the list. After installing without using a net
 connection, a simple modprobe e1000e and dhclient made the net
 connection work. The following were added automaticly to /etc/modules
 by the installation:

 e100
 e1000
 e1000e

 But booting with these in /etc/modules did not make the network
 interface work. Had to do modprobe e1000e manually after each boot.

 This sounds like a kernel issue. Reassigning to the kernel team.

 Cheers,
 FJP


 I have a correction to make, it was only the DHCP part that didn't
 work when booting into the installed kernel. The e1000e driver is
 loaded correctly, and the other (incorrect) drivers can't be seen when
 doing lsmod. The detection in the installation is still broken
 though.

 If it's any help, the installed kernel is 2.6.32-trunk-amd64, and the
 one used on the USB key is 2.6.30-2-amd64. The network also worked
 fine with the installed kernel being 2.6.32-3-amd64. I remember
 reading that Linus and Molnar had problems with this driver in one of
 the latest kernels, maybe updating the USB key kernel would fix it.

 When making the USB key I used the boot.img.gz from
 http://ftp.nl.debian.org/debian/dists/testing/main/installer-amd64/current/images/hd-media/
 and the netinstall image
 http://cdimage.debian.org/cdimage/squeeze_di_alpha1/amd64/iso-cd/debian-testing-amd64-netinst.iso


Another followup: I tried the daily build of the netinst with the
daily USB stick image, and the hardware detection worked, so this can
probably be closed. Maybe add this to the errata.



--
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/i2y63ae10171005050838vb0ebe801r7497714f6a25e...@mail.gmail.com

Processing of linux-2.6_2.6.33-1~experimental.5_amd64.changes

2010-05-05 Thread Archive Administrator 
linux-2.6_2.6.33-1~experimental.5_amd64.changes uploaded successfully to 
localhost
along with the files:
  linux-2.6_2.6.33-1~experimental.5.dsc
  linux-2.6_2.6.33-1~experimental.5.diff.gz
  linux-doc-2.6.33_2.6.33-1~experimental.5_all.deb
  linux-manual-2.6.33_2.6.33-1~experimental.5_all.deb
  linux-patch-debian-2.6.33_2.6.33-1~experimental.5_all.deb
  linux-source-2.6.33_2.6.33-1~experimental.5_all.deb
  linux-support-2.6.33-2_2.6.33-1~experimental.5_all.deb
  firmware-linux-free_2.6.33-1~experimental.5_all.deb
  linux-base_2.6.33-1~experimental.5_all.deb
  linux-image-2.6.33-2-amd64_2.6.33-1~experimental.5_amd64.deb
  linux-headers-2.6.33-2-amd64_2.6.33-1~experimental.5_amd64.deb
  linux-headers-2.6.33-2-common_2.6.33-1~experimental.5_amd64.deb
  linux-headers-2.6.33-2-all_2.6.33-1~experimental.5_amd64.deb
  linux-headers-2.6.33-2-all-amd64_2.6.33-1~experimental.5_amd64.deb
  linux-libc-dev_2.6.33-1~experimental.5_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/e1o9ih8-000893...@ries.debian.org

linux-2.6_2.6.33-1~experimental.5_amd64.changes ACCEPTED

2010-05-05 Thread Archive Administrator 



Accepted:
firmware-linux-free_2.6.33-1~experimental.5_all.deb
  to main/l/linux-2.6/firmware-linux-free_2.6.33-1~experimental.5_all.deb
linux-2.6_2.6.33-1~experimental.5.diff.gz
  to main/l/linux-2.6/linux-2.6_2.6.33-1~experimental.5.diff.gz
linux-2.6_2.6.33-1~experimental.5.dsc
  to main/l/linux-2.6/linux-2.6_2.6.33-1~experimental.5.dsc
linux-base_2.6.33-1~experimental.5_all.deb
  to main/l/linux-2.6/linux-base_2.6.33-1~experimental.5_all.deb
linux-doc-2.6.33_2.6.33-1~experimental.5_all.deb
  to main/l/linux-2.6/linux-doc-2.6.33_2.6.33-1~experimental.5_all.deb
linux-headers-2.6.33-2-all-amd64_2.6.33-1~experimental.5_amd64.deb
  to 
main/l/linux-2.6/linux-headers-2.6.33-2-all-amd64_2.6.33-1~experimental.5_amd64.deb
linux-headers-2.6.33-2-all_2.6.33-1~experimental.5_amd64.deb
  to 
main/l/linux-2.6/linux-headers-2.6.33-2-all_2.6.33-1~experimental.5_amd64.deb
linux-headers-2.6.33-2-amd64_2.6.33-1~experimental.5_amd64.deb
  to 
main/l/linux-2.6/linux-headers-2.6.33-2-amd64_2.6.33-1~experimental.5_amd64.deb
linux-headers-2.6.33-2-common_2.6.33-1~experimental.5_amd64.deb
  to 
main/l/linux-2.6/linux-headers-2.6.33-2-common_2.6.33-1~experimental.5_amd64.deb
linux-image-2.6.33-2-amd64_2.6.33-1~experimental.5_amd64.deb
  to 
main/l/linux-2.6/linux-image-2.6.33-2-amd64_2.6.33-1~experimental.5_amd64.deb
linux-libc-dev_2.6.33-1~experimental.5_amd64.deb
  to main/l/linux-2.6/linux-libc-dev_2.6.33-1~experimental.5_amd64.deb
linux-manual-2.6.33_2.6.33-1~experimental.5_all.deb
  to main/l/linux-2.6/linux-manual-2.6.33_2.6.33-1~experimental.5_all.deb
linux-patch-debian-2.6.33_2.6.33-1~experimental.5_all.deb
  to main/l/linux-2.6/linux-patch-debian-2.6.33_2.6.33-1~experimental.5_all.deb
linux-source-2.6.33_2.6.33-1~experimental.5_all.deb
  to main/l/linux-2.6/linux-source-2.6.33_2.6.33-1~experimental.5_all.deb
linux-support-2.6.33-2_2.6.33-1~experimental.5_all.deb
  to main/l/linux-2.6/linux-support-2.6.33-2_2.6.33-1~experimental.5_all.deb


Override entries for your package:
firmware-linux-free_2.6.33-1~experimental.5_all.deb - optional kernel
linux-2.6_2.6.33-1~experimental.5.dsc - source devel
linux-base_2.6.33-1~experimental.5_all.deb - optional kernel
linux-doc-2.6.33_2.6.33-1~experimental.5_all.deb - optional doc
linux-headers-2.6.33-2-all-amd64_2.6.33-1~experimental.5_amd64.deb - optional 
kernel
linux-headers-2.6.33-2-all_2.6.33-1~experimental.5_amd64.deb - optional kernel
linux-headers-2.6.33-2-amd64_2.6.33-1~experimental.5_amd64.deb - optional kernel
linux-headers-2.6.33-2-common_2.6.33-1~experimental.5_amd64.deb - optional 
kernel
linux-image-2.6.33-2-amd64_2.6.33-1~experimental.5_amd64.deb - optional kernel
linux-libc-dev_2.6.33-1~experimental.5_amd64.deb - optional devel
linux-manual-2.6.33_2.6.33-1~experimental.5_all.deb - optional doc
linux-patch-debian-2.6.33_2.6.33-1~experimental.5_all.deb - optional kernel
linux-source-2.6.33_2.6.33-1~experimental.5_all.deb - optional kernel
linux-support-2.6.33-2_2.6.33-1~experimental.5_all.deb - optional devel

Announcing to debian-devel-chan...@lists.debian.org
Closing bugs: 563313 569034 573912 576723 


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/e1o9izd-ih...@ries.debian.org

Bug#563313: marked as done (lm-sensors: sensors not working after suspend)

2010-05-05 Thread Debian Bug Tracking System 
Your message dated Wed, 05 May 2010 17:39:53 +
with message-id e1o9izd-io...@ries.debian.org
and subject line Bug#563313: fixed in linux-2.6 2.6.33-1~experimental.5
has caused the Debian Bug report #563313,
regarding lm-sensors: sensors not working after suspend
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.)


-- 
563313: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563313
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: lm-sensors
Version: 1:3.1.1-4
Severity: normal

I have dell studio 1555 after suspend sensors don't show temperature of some 
devces. As a result after some time devises reach top temperature and system 
turns off, because of overheat(fans don't working). Full shut down is needed I 
am not shure if it is problem of this package but problem is serious.


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

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

Versions of packages lm-sensors depends on:
ii  libc6 2.10.2-2   GNU C Library: Shared libraries
ii  libsensors4   1:3.1.1-4  library to read temperature/voltag
ii  lsb-base  3.2-23 Linux Standard Base 3.2 init scrip
ii  perl  5.10.1-8   Larry Wall's Practical Extraction 
ii  sed   4.2.1-6The GNU sed stream editor

lm-sensors recommends no packages.

Versions of packages lm-sensors suggests:
ii  i2c-tools 3.0.2-3heterogeneous set of I2C tools for
pn  read-edid none (no description available)
ii  sensord   1:3.1.1-4  hardware sensor information loggin

-- no debconf information


---End Message---
---BeginMessage---
Source: linux-2.6
Source-Version: 2.6.33-1~experimental.5

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.33-1~experimental.5_all.deb
  to main/l/linux-2.6/firmware-linux-free_2.6.33-1~experimental.5_all.deb
linux-2.6_2.6.33-1~experimental.5.diff.gz
  to main/l/linux-2.6/linux-2.6_2.6.33-1~experimental.5.diff.gz
linux-2.6_2.6.33-1~experimental.5.dsc
  to main/l/linux-2.6/linux-2.6_2.6.33-1~experimental.5.dsc
linux-base_2.6.33-1~experimental.5_all.deb
  to main/l/linux-2.6/linux-base_2.6.33-1~experimental.5_all.deb
linux-doc-2.6.33_2.6.33-1~experimental.5_all.deb
  to main/l/linux-2.6/linux-doc-2.6.33_2.6.33-1~experimental.5_all.deb
linux-headers-2.6.33-2-all-amd64_2.6.33-1~experimental.5_amd64.deb
  to 
main/l/linux-2.6/linux-headers-2.6.33-2-all-amd64_2.6.33-1~experimental.5_amd64.deb
linux-headers-2.6.33-2-all_2.6.33-1~experimental.5_amd64.deb
  to 
main/l/linux-2.6/linux-headers-2.6.33-2-all_2.6.33-1~experimental.5_amd64.deb
linux-headers-2.6.33-2-amd64_2.6.33-1~experimental.5_amd64.deb
  to 
main/l/linux-2.6/linux-headers-2.6.33-2-amd64_2.6.33-1~experimental.5_amd64.deb
linux-headers-2.6.33-2-common_2.6.33-1~experimental.5_amd64.deb
  to 
main/l/linux-2.6/linux-headers-2.6.33-2-common_2.6.33-1~experimental.5_amd64.deb
linux-image-2.6.33-2-amd64_2.6.33-1~experimental.5_amd64.deb
  to 
main/l/linux-2.6/linux-image-2.6.33-2-amd64_2.6.33-1~experimental.5_amd64.deb
linux-libc-dev_2.6.33-1~experimental.5_amd64.deb
  to main/l/linux-2.6/linux-libc-dev_2.6.33-1~experimental.5_amd64.deb
linux-manual-2.6.33_2.6.33-1~experimental.5_all.deb
  to main/l/linux-2.6/linux-manual-2.6.33_2.6.33-1~experimental.5_all.deb
linux-patch-debian-2.6.33_2.6.33-1~experimental.5_all.deb
  to main/l/linux-2.6/linux-patch-debian-2.6.33_2.6.33-1~experimental.5_all.deb
linux-source-2.6.33_2.6.33-1~experimental.5_all.deb
  to main/l/linux-2.6/linux-source-2.6.33_2.6.33-1~experimental.5_all.deb
linux-support-2.6.33-2_2.6.33-1~experimental.5_all.deb
  to main/l/linux-2.6/linux-support-2.6.33-2_2.6.33-1~experimental.5_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 563...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
maximilian attems m...@debian.org (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

Bug#573912: marked as done (linux-2.6: please enable ramzswap/compcache)

2010-05-05 Thread Debian Bug Tracking System 
Your message dated Wed, 05 May 2010 17:39:53 +
with message-id e1o9izd-iz...@ries.debian.org
and subject line Bug#573912: fixed in linux-2.6 2.6.33-1~experimental.5
has caused the Debian Bug report #573912,
regarding linux-2.6: please enable ramzswap/compcache
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.)


-- 
573912: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573912
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: consider enabling CONFIG_RAMZSWAP in 2.6.33+
Severity: wishlist

please consider setting CONFIG_RAMZSWAP (a.k.a. compcache), which enables a ram
based compressed swap device. i think it can be enabled as a module, but i'm
not sure.

this feature is very useful to thin clients, embedded devices, or other
environments with limited ram and no conventional swap device available.

live well,
  vagrant


---End Message---
---BeginMessage---
Source: linux-2.6
Source-Version: 2.6.33-1~experimental.5

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.33-1~experimental.5_all.deb
  to main/l/linux-2.6/firmware-linux-free_2.6.33-1~experimental.5_all.deb
linux-2.6_2.6.33-1~experimental.5.diff.gz
  to main/l/linux-2.6/linux-2.6_2.6.33-1~experimental.5.diff.gz
linux-2.6_2.6.33-1~experimental.5.dsc
  to main/l/linux-2.6/linux-2.6_2.6.33-1~experimental.5.dsc
linux-base_2.6.33-1~experimental.5_all.deb
  to main/l/linux-2.6/linux-base_2.6.33-1~experimental.5_all.deb
linux-doc-2.6.33_2.6.33-1~experimental.5_all.deb
  to main/l/linux-2.6/linux-doc-2.6.33_2.6.33-1~experimental.5_all.deb
linux-headers-2.6.33-2-all-amd64_2.6.33-1~experimental.5_amd64.deb
  to 
main/l/linux-2.6/linux-headers-2.6.33-2-all-amd64_2.6.33-1~experimental.5_amd64.deb
linux-headers-2.6.33-2-all_2.6.33-1~experimental.5_amd64.deb
  to 
main/l/linux-2.6/linux-headers-2.6.33-2-all_2.6.33-1~experimental.5_amd64.deb
linux-headers-2.6.33-2-amd64_2.6.33-1~experimental.5_amd64.deb
  to 
main/l/linux-2.6/linux-headers-2.6.33-2-amd64_2.6.33-1~experimental.5_amd64.deb
linux-headers-2.6.33-2-common_2.6.33-1~experimental.5_amd64.deb
  to 
main/l/linux-2.6/linux-headers-2.6.33-2-common_2.6.33-1~experimental.5_amd64.deb
linux-image-2.6.33-2-amd64_2.6.33-1~experimental.5_amd64.deb
  to 
main/l/linux-2.6/linux-image-2.6.33-2-amd64_2.6.33-1~experimental.5_amd64.deb
linux-libc-dev_2.6.33-1~experimental.5_amd64.deb
  to main/l/linux-2.6/linux-libc-dev_2.6.33-1~experimental.5_amd64.deb
linux-manual-2.6.33_2.6.33-1~experimental.5_all.deb
  to main/l/linux-2.6/linux-manual-2.6.33_2.6.33-1~experimental.5_all.deb
linux-patch-debian-2.6.33_2.6.33-1~experimental.5_all.deb
  to main/l/linux-2.6/linux-patch-debian-2.6.33_2.6.33-1~experimental.5_all.deb
linux-source-2.6.33_2.6.33-1~experimental.5_all.deb
  to main/l/linux-2.6/linux-source-2.6.33_2.6.33-1~experimental.5_all.deb
linux-support-2.6.33-2_2.6.33-1~experimental.5_all.deb
  to main/l/linux-2.6/linux-support-2.6.33-2_2.6.33-1~experimental.5_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 573...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
maximilian attems m...@debian.org (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, 05 May 2010 16:38:53 +0200
Source: linux-2.6
Binary: linux-source-2.6.33 linux-doc-2.6.33 linux-manual-2.6.33 
linux-patch-debian-2.6.33 firmware-linux-free linux-support-2.6.33-2 linux-base 
linux-libc-dev linux-headers-2.6.33-2-all linux-headers-2.6.33-2-all-alpha 
linux-headers-2.6.33-2-common linux-image-2.6.33-2-alpha-generic 
linux-headers-2.6.33-2-alpha-generic linux-image-2.6.33-2-alpha-smp 
linux-headers-2.6.33-2-alpha-smp linux-image-2.6.33-2-alpha-legacy 
linux-headers-2.6.33-2-alpha-legacy linux-headers-2.6.33-2-all-amd64 
linux-image-2.6.33-2-amd64 linux-headers-2.6.33-2-amd64 
linux-headers-2.6.33-2-all-armel linux-image-2.6.33-2-iop32x 
linux-headers-2.6.33-2-iop32x linux-image-2.6.33-2-ixp4xx 
linux-headers-2.6.33-2-ixp4xx linux-image-2.6.33-2-kirkwood 
linux-headers-2.6.33-2-kirkwood linux-image-2.6.33-2-orion5x 
linux-headers-2.6.33-2-orion5x

Bug#576723: marked as done (linux-2.6: [2.6.33] mising rt2860sta; rt2800 not suitable for replacement)

2010-05-05 Thread Debian Bug Tracking System 
Your message dated Wed, 05 May 2010 17:39:53 +
with message-id e1o9izd-j4...@ries.debian.org
and subject line Bug#576723: fixed in linux-2.6 2.6.33-1~experimental.5
has caused the Debian Bug report #576723,
regarding linux-2.6: [2.6.33] mising rt2860sta; rt2800 not suitable for 
replacement
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.)


-- 
576723: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576723
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 2.6.33-1~experimental.2, 2.6.33-1~experimental.4
Severity: normal
Tags: experimental
user: debian-eeepc-de...@lists.alioth.debian.org
usertag: features
usertag: 901

Hi,

The 2.6.33 linux-image in experimental removed the rt2860sta driver 
from staging and it seems to offer the rt2800 driver as a replacement. 
The later doesn't work for me, however. I can't associate with my 
access point using WPA2.

Hardware is Asus EeePC 901 (details in the info below).

Would it be possible to restore rt2860sta?


-- Package-specific info:
** Version:
Linux version 2.6.33-2-686 (Debian 2.6.33-1~experimental.4) (m...@debian.org) 
(gcc version 4.3.4 (Debian 4.3.4-8) ) #1 SMP Thu Mar 18 07:30:30 UTC 2010

** Command line:
BOOT_IMAGE=/vmlinuz-2.6.33-2-686 root=UUID=4e436c23-73dc-44f1-85be-ffc868c92769 
ro quiet i915.modeset=1 acpi_osi=Linux rfkill.default_state=1

** Not tainted

** Kernel log:
[3.497662] usb usb4: Product: UHCI Host Controller
[3.497666] usb usb4: Manufacturer: Linux 2.6.33-2-686 uhci_hcd
[3.497671] usb usb4: SerialNumber: :00:1d.2
[3.504715] hub 4-0:1.0: USB hub found
[3.504729] hub 4-0:1.0: 2 ports detected
[3.504849] uhci_hcd :00:1d.3: PCI INT D - GSI 16 (level, low) - IRQ 16
[3.504866] uhci_hcd :00:1d.3: setting latency timer to 64
[3.504873] uhci_hcd :00:1d.3: UHCI Host Controller
[3.504893] uhci_hcd :00:1d.3: new USB bus registered, assigned bus 
number 5
[3.504951] uhci_hcd :00:1d.3: irq 16, io base 0xdc00
[3.505035] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001
[3.505042] usb usb5: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
[3.505047] usb usb5: Product: UHCI Host Controller
[3.505052] usb usb5: Manufacturer: Linux 2.6.33-2-686 uhci_hcd
[3.505057] usb usb5: SerialNumber: :00:1d.3
[3.509041] hub 5-0:1.0: USB hub found
[3.509054] hub 5-0:1.0: 2 ports detected
[3.533294] eeepc_laptop: Eee PC Hotkey Driver
[3.533313] eeepc_laptop: Hotkey init flags 0x41
[3.672083] usb 1-8: new high speed USB device using ehci_hcd and address 2
[3.820149] [drm] Initialized drm 1.1.0 20060810
[3.949161] i915 :00:02.0: PCI INT A - GSI 16 (level, low) - IRQ 16
[3.949171] i915 :00:02.0: setting latency timer to 64
[3.993935] [drm] set up 7M of stolen space
[4.124233] rt2800pci :01:00.0: PCI INT A - GSI 19 (level, low) - IRQ 
19
[4.124247] rt2800pci :01:00.0: setting latency timer to 64
[4.226869] phy0: Selected rate control algorithm 'minstrel'
[4.228381] Registered led device: rt2800pci-phy0::radio
[4.228478] Registered led device: rt2800pci-phy0::assoc
[4.228574] Registered led device: rt2800pci-phy0::quality
[4.233376] usb 1-8: New USB device found, idVendor=05e3, idProduct=0505
[4.233384] usb 1-8: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[4.233390] usb 1-8: Product: USB 2.0 Camera
[4.264156] elantech.c: assuming hardware version 2, firmware version 2.48
[4.367916] elantech.c: Synaptics capabilities query result 0x00, 0x02, 0x64.
[4.372520] [drm] initialized overlay support
[4.641088] Linux video capture interface: v2.00
[4.660808] uvcvideo: Found UVC 1.00 device USB 2.0 Camera (05e3:0505)
[4.829636] [drm:edid_is_valid] *ERROR* EDID checksum is invalid, remainder 
is 219
[4.829705] [drm:edid_is_valid] *ERROR* Raw EDID:
[4.829765] 300 ff ff ff ff ff ff 00 06 af 20 10 00 00 00 00  .. 
.
[4.829771] 301 12 01 03 80 13 0b 78 0a fa 56 92 56 54 98 24  
...x..V.VT.$
[4.829777] 31a 4f 54 00 00 00 01 01 01 01 01 01 01 01 01 01  
.OT.
[4.829783] 301 01 01 01 01 01 b0 13 00 40 41 58 19 20 18 88  
.@ax. ..
[4.829788] 303 01 c3 71 00 00 00 18 00 00 00 0f 00 00 00 00  
...q
[4.829794] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  

[4.829800] 300 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  

[4.829805] 300 00 00 00 00 00 00 00 00 00 00 00 df ff ff ff  

[

Bug#563313: that's not fair!

2010-05-05 Thread Γιώργος Πάλλας 
Ben Hutchings wrote:
 On Tue, May 04, 2010 at 02:23:20PM +0300, Γιώργος Πάλλας wrote:
   
 I regularly follow testing's upgrades. So I was with 2.6.30, the sensors  
 were working fine. I got 2.6.32-3 sensors broken. And I must wait until  
 2.6.32-12 (!) to get it working again? Why doesn't a patch slip into  
 2.6.32-3 ??
 Am I missing something?
 

 Yes, you are confused about the current version.

 First, package names do not contain the package version.  For example,
 there were several versions of linux-image-2.6.32-3-686, none of which
 was version 2.6.32-3.  The number 3 here is an ABI version which is used
 to associate the kernel with additional kernel modules.  Whenever the
 ABI changes the additional modules must be rebuilt.  Not every package
 version requires a new ABI version.

 Second, the latest kernel versions appear in unstable, not testing.
 As of today, version 2.6.32-12 is available in unstable.

 Ben.

   

Oh, OK, sorry for the misunderstanding! I tried 2.6.32-5 and it works fine!





smime.p7s
Description: S/MIME Cryptographic Signature

Bug#580422: [sparc] Irrecoverable deferred error trap

2010-05-05 Thread dann frazier 
Source: linux-2.6
Version: 2.6.26-22
Severity: serious
Tags: patch, lenny

I have a sparc that fails to boot a lenny kernel.

The issue was reported upstream by another Debian user here:
 http://permalink.gmane.org/gmane.linux.ports.sparc/13092

And was resolved by the following patch:

commit bdd32ce95f79fb5cc964cd789d7ae4500bba7c6f
Author: David S. Miller da...@davemloft.net
Date:   Sun Apr 4 01:12:50 2010 -0700

sunxvr500: Ignore secondary output PCI devices.

These just represent the secondary and further heads attached to the
card, and they have different sets of PCI bar registers to map.

So don't try to drive them in the main driver.

Reported-by: Frans van Berckel fberc...@xs4all.nl
Tested-by: Frans van Berckel fberc...@xs4all.nl
Signed-off-by: David S. Miller da...@davemloft.net

diff --git a/drivers/video/sunxvr500.c b/drivers/video/sunxvr500.c
index 4cd5049..3803745 100644
--- a/drivers/video/sunxvr500.c
+++ b/drivers/video/sunxvr500.c
@@ -242,11 +242,27 @@ static int __devinit e3d_set_fbinfo(struct e3d_info *ep)
 static int __devinit e3d_pci_register(struct pci_dev *pdev,
  const struct pci_device_id *ent)
 {
+   struct device_node *of_node;
+   const char *device_type;
struct fb_info *info;
struct e3d_info *ep;
unsigned int line_length;
int err;
 
+   of_node = pci_device_to_OF_node(pdev);
+   if (!of_node) {
+   printk(KERN_ERR e3d: Cannot find OF node of %s\n,
+  pci_name(pdev));
+   return -ENODEV;
+   }
+
+   device_type = of_get_property(of_node, device_type, NULL);
+   if (!device_type) {
+   printk(KERN_INFO e3d: Ignoring secondary output device 
+  at %s\n, pci_name(pdev));
+   return -ENODEV;
+   }
+
err = pci_enable_device(pdev);
if (err  0) {
printk(KERN_ERR e3d: Cannot enable PCI device %s\n,
@@ -265,13 +281,7 @@ static int __devinit e3d_pci_register(struct pci_dev *pdev,
ep-info = info;
ep-pdev = pdev;
spin_lock_init(ep-lock);
-   ep-of_node = pci_device_to_OF_node(pdev);
-   if (!ep-of_node) {
-   printk(KERN_ERR e3d: Cannot find OF node of %s\n,
-  pci_name(pdev));
-   err = -ENODEV;
-   goto err_release_fb;
-   }
+   ep-of_node = of_node;
 
/* Read the PCI base register of the frame buffer, which we
 * need in order to interpret the RAMDAC_VID_*FB* values in






-- 
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/20100505212020.gg8...@lackof.org

Processed: tagging 580422

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

 # Automatically generated email from bts, devscripts version 2.10.35lenny7
 tags 580422 + pending
Bug #580422 [src:linux-2.6] [sparc] Irrecoverable deferred error trap
Added tag(s) pending.

End of message, stopping processing here.

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


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

Processed: tagging 562486

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

 # Automatically generated email from bts, devscripts version 2.10.35lenny7
 tags 562486 + pending
Bug #562486 [linux-2.6] linux-2.6: please enable tomoyo
Added tag(s) pending.

End of message, stopping processing here.

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


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

Bug#367026: marked as done (linux-image-2.6.15-1-486: HID sermouse driver fails to detect Logitech mouse on ttyS0)

2010-05-05 Thread Debian Bug Tracking System 
Your message dated Wed, 5 May 2010 23:43:47 +0200
with message-id 20100505214347.ga5...@galadriel.inutil.org
and subject line Re: Nope, stll doesn't work
has caused the Debian Bug report #367026,
regarding linux-image-2.6.15-1-486: HID sermouse driver fails to detect 
Logitech mouse on ttyS0
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.)


-- 
367026: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=367026
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-image-2.6.15-1-486
Version: 2.6.15-8
Severity: normal


Using the mousedev module doesn't work with sermouse, for my mouse (the 
mouse is not detected, as evidenced by udev not create a new 
/dev/input/mouse0 when modprobe sermouse is performed, and X loading, 
but with a frozen mouse pointer (because /dev/input/mice always exists 
when mousedev is in use, but there really isn't a detected mouse).

My mouse is an old Logitech (which uses the Microsoft protocol, when 
using /dev/ttyS0 for X) PS/2 mouse with a PS/2 mouse to serial computer 
adapter (which works, since specifying /dev/ttyS0 and Microsoft mode 
results in a working mouse for X).

This is probably an upstream issue, as I found one reference while 
Googling.  Unfortunately there didn't seem to be any followups, only an 
indication that it didn't work.  The URL of that message is:

http://www.ussg.iu.edu/hypermail/linux/kernel/0312.2/0778.html

Cheers,

Daniel


-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (300, 'testing')
Architecture: i386 (i586)
Kernel: Linux 2.6.15-1-486
Locale: LANG=en_CA, LC_CTYPE=en_CA (charmap=ISO-8859-1)

Versions of packages linux-image-2.6.15-1-486 depends on:
ii  module-init-tools 3.2.2-2tools for managing Linux
kernel mo ii  yaird [linux-initramfs-tool]  0.0.12-9   Yet Another
mkInitRD

-- debconf information:
  linux-image-2.6.15-1-486/postinst/kimage-is-a-directory:
  linux-image-2.6.15-1-486/preinst/initrd-2.6.15-1-486:
  linux-image-2.6.15-1-486/preinst/overwriting-modules-2.6.15-1-486:
true linux-image-2.6.15-1-486/postinst/create-kimage-link-2.6.15-1-486:
true linux-image-2.6.15-1-486/preinst/lilo-has-ramdisk:
  linux-image-2.6.15-1-486/preinst/lilo-initrd-2.6.15-1-486: true
  linux-image-2.6.15-1-486/postinst/bootloader-error-2.6.15-1-486:
  linux-image-2.6.15-1-486/prerm/removing-running-kernel-2.6.15-1-486:
true linux-image-2.6.15-1-486/preinst/elilo-initrd-2.6.15-1-486: true
  linux-image-2.6.15-1-486/postinst/depmod-error-2.6.15-1-486: false
  linux-image-2.6.15-1-486/preinst/abort-install-2.6.15-1-486:
  linux-image-2.6.15-1-486/postinst/old-initrd-link-2.6.15-1-486: true
  linux-image-2.6.15-1-486/prerm/would-invalidate-boot-loader-2.6.15-1-486:
true linux-image-2.6.15-1-486/preinst/abort-overwrite-2.6.15-1-486:
  linux-image-2.6.15-1-486/postinst/old-dir-initrd-link-2.6.15-1-486:
true
linux-image-2.6.15-1-486/postinst/bootloader-test-error-2.6.15-1-486:
linux-image-2.6.15-1-486/preinst/bootloader-initrd-2.6.15-1-486: true
linux-image-2.6.15-1-486/postinst/old-system-map-link-2.6.15-1-486:
true
linux-image-2.6.15-1-486/preinst/already-running-this-2.6.15-1-486:
linux-image-2.6.15-1-486/preinst/failed-to-move-modules-2.6.15-1-486:
linux-image-2.6.15-1-486/postinst/depmod-error-initrd-2.6.15-1-486:
false


---End Message---
---BeginMessage---
On Wed, May 05, 2010 at 01:24:41AM -0400, Daniel Dickinson wrote:
 On Sat, 1 May 2010 23:08:54 +0200
 Moritz Muehlenhoff j...@inutil.org wrote:
 
  On Wed, Feb 25, 2009 at 08:43:10PM -0500, Daniel Dickinson wrote:
   In response to your query; I don't have the Logitech mouse anymore
   but I just tested and Microsoft mice don't work so it probably is
   still not working for any serial mice.
  
  Please report this bug upstream at the upstream bugzilla
  (http://bugzilla.kernel.org), so that it can be investigated/
  fixed upstream and backported for Squeeze.
  (Product: Drivers, Component: Input Devices)
  
  Once done, please add the bug number to this bug.
  
  (We're asking you to file the bug report yourself, since the
  kernel.org developers will have specific inquiries to your
  hardware/setup)
  
 
 Sorry, I gave up on serial mice and really don't care about them any
 more.  There's not enough other people like to need them for me to view
 it worthwhile from a community point of view, and I don't need it
 myself at this point.

Ok, closing the bug, then.

Cheers,
   Moritz

---End Message---

Bug#561026: marked as done (linux-image-2.6.26-2-686: r8169 don't function with RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02))

2010-05-05 Thread Debian Bug Tracking System 
Your message dated Wed, 5 May 2010 23:45:25 +0200
with message-id 20100505214525.ga5...@galadriel.inutil.org
and subject line Re: Bug#561026: linux-image-2.6.26-2-686: r8169 don't function 
with RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)
has caused the Debian Bug report #561026,
regarding linux-image-2.6.26-2-686: r8169 don't function with RTL8101E/RTL8102E 
PCI Express Fast Ethernet controller (rev 02)
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.)


-- 
561026: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561026
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-image-2.6.26-2-686
Version: 2.6.26-19lenny2
Severity: important
Tags: patch

Kernel modul r8169 doesn't function with Realtek Semiconductor Co., Ltd. 
RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02). I downloaded 
the driver from
http://download1.opendrivers.com/uploaddrv/network/realtek/r8101-1.014.00.tar.bz2,
 compiled and installed. Nevertheless I had problems with the driver r8169: 
after
reboot the r8169 will always be loaded instead of the r8101 modul. I changed 
grep r8101 *
modules.alias:alias pci:v10ECd8136sv*sd*bc*sc*i* r8101
modules.dep:/lib/modules/2.6.26-2-686/kernel/drivers/net/r8101.ko:
modules.pcimap:r81010x10ec 0x8136 0x 0x 
0x 0x 0x0
Nevertheless the r8169 modul will be there after reboot. I have to rmmod r8169 
and modprobe r8101 after each reboot.

-- Package-specific info:
** Version:
Linux version 2.6.26-2-686 (Debian 2.6.26-19lenny2) (da...@debian.org) (gcc 
version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Wed Nov 4 
20:45:37 UTC 2009

** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.26-2-686 root=/dev/sda7 vga=791

** Tainted: P (1)

** Kernel log:
[   14.389602] EXT3-fs: sda10: couldn't mount because of unsupported optional 
features (240).
[   14.500010] kjournald starting.  Commit interval 5 seconds
[   14.500129] EXT3 FS on sda11, internal journal
[   14.500129] EXT3-fs: mounted filesystem with ordered data mode.
[   14.537085] kjournald starting.  Commit interval 5 seconds
[   14.537215] EXT3 FS on sda12, internal journal
[   14.537215] EXT3-fs: mounted filesystem with ordered data mode.
[   14.589520] kjournald starting.  Commit interval 5 seconds
[   14.591459] EXT3 FS on sda15, internal journal
[   14.591459] EXT3-fs: mounted filesystem with ordered data mode.
[   15.365519] ACPI: PCI interrupt for device :03:00.0 disabled
[   15.426670] r8101 Fast Ethernet driver 1.013.00-NAPI loaded
[   15.426670] ACPI: PCI Interrupt :03:00.0[A] - GSI 17 (level, low) - 
IRQ 17
[   15.426670] PCI: Setting latency timer of device :03:00.0 to 64
[   15.426670] r8101: This product is covered by one or more of the following 
patents: US5,307,459, US5,434,872, US5,732,094, US6,570,884, US6,115,776, and 
US6,327,625.
[   15.426670] eth0: Identified chip type is 'RTL8103E'.
[   15.426670] eth0: RTL8101E at 0xf89cc000, 00:26:9e:36:b9:b2, IRQ 17
[   15.429147] r8101  Copyright (C) 2009  Realtek NIC software team 
nic...@realtek.com 
[   15.429149]  This program comes with ABSOLUTELY NO WARRANTY; for details, 
please see http://www.gnu.org/licenses/. 
[   15.429150]  This is free software, and you are welcome to redistribute it 
under certain conditions; see http://www.gnu.org/licenses/. 
[   15.803668] r8101: eth0: link down
[   17.253644] r8101: eth0: link up
[   18.658698] NET: Registered protocol family 10
[   18.658698] lo: Disabled Privacy Extensions
[   19.126801] lp: driver loaded but no devices found
[   19.209270] ppdev: user-space parallel port driver
[   23.519374] Bluetooth: Core ver 2.11
[   23.519374] NET: Registered protocol family 31
[   23.519374] Bluetooth: HCI device and connection manager initialized
[   23.519374] Bluetooth: HCI socket layer initialized
[   23.556443] Bluetooth: L2CAP ver 2.9
[   23.556543] Bluetooth: L2CAP socket layer initialized
[   23.726132] Bluetooth: RFCOMM socket layer initialized
[   23.726132] Bluetooth: RFCOMM TTY layer initialized
[   23.726132] Bluetooth: RFCOMM ver 1.8
[   24.570356] /dev/vmmon[2994]: Module vmmon: registered with major=10 
minor=165
[   24.570356] /dev/vmmon[2994]: Initial HV check: anyNotCapable=1 
anyUnlocked=0 anyEnabled=0 anyDisabled=0
[   24.570356] /dev/vmmon[2994]: Module vmmon: initialized
[   24.578356] /dev/vmci[3006]: VMCI: Driver initialized.
[   24.578356] /dev/vmci[3006]: Module vmci: registered with major=10 minor=60
[   24.578356] /dev/vmci[3006]: Module vmci: initialized
[   25.102311] /dev/vmnet: open

Processed: Re: rt2860-source: connection drops - debian kernel 2.6.32

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

 tags 562981 moreinfo
Bug #562981 [linux-2.6] rt2860-source: connection drops - debian kernel 2.6.32
Added tag(s) moreinfo.
 thanks
Stopping processing here.

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


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

Processed: Re: i915: KMS framebuffer fails to work, only X works

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

 tags 567965 moreinfo
Bug #567965 [linux-2.6] i915: KMS framebuffer fails to work, only X works
Added tag(s) moreinfo.
 thanks
Stopping processing here.

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


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

Bug#580424: linux-image-2.6.32-5-686 breaks framebuffer and X

2010-05-05 Thread Luca Falavigna 
Package: linux-2.6
Version: 2.6.32-12
Severity: normal

Recent upgrade of kernel linux-image-2.6.32-5-686 broke framebuffer support on 
VTs
and limits maximum resolution to 1024x768 while running X.

Rebooting with linux-image-2.6.32-3-686, everything is fine.

-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
not available

** PCI devices:
00:00.0 Host bridge [0600]: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] 
[1106:0305] (rev 02)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- 
TAbort- MAbort+ SERR- PERR- INTx-
Latency: 8
Region 0: Memory at e000 (32-bit, prefetchable) [size=64M]
Capabilities: access denied
Kernel driver in use: agpgart-via

00:01.0 PCI bridge [0604]: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP] 
[1106:8305] (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- 
TAbort- MAbort+ SERR- PERR- INTx-
Latency: 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 9000-9fff
Memory behind bridge: dde0-dfef
Prefetchable memory behind bridge: d5b0-ddcf
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR-
BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: access denied

00:07.0 ISA bridge [0601]: VIA Technologies, Inc. VT82C686 [Apollo Super South] 
[1106:0686] (rev 22)
Subsystem: VIA Technologies, Inc. VT82C686/A PCI to ISA Bridge 
[1106:0686]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping+ SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- 
TAbort- MAbort- SERR- PERR- INTx-
Latency: 0
Kernel driver in use: parport_pc

00:07.1 IDE interface [0101]: VIA Technologies, Inc. 
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571] (rev 10) 
(prog-if 8a [Master SecP PriP])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- 
TAbort- MAbort- SERR- PERR- INTx-
Latency: 32
Region 0: [virtual] Memory at 01f0 (32-bit, non-prefetchable) 
[size=8]
Region 1: [virtual] Memory at 03f0 (type 3, non-prefetchable) 
[size=1]
Region 2: [virtual] Memory at 0170 (32-bit, non-prefetchable) 
[size=8]
Region 3: [virtual] Memory at 0370 (type 3, non-prefetchable) 
[size=1]
Region 4: I/O ports at ffa0 [size=16]
Capabilities: access denied
Kernel driver in use: VIA_IDE

00:07.2 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI USB 1.1 
Controller [1106:3038] (rev 10) (prog-if 00 [UHCI])
Subsystem: First International Computer, Inc. VA-502 Mainboard 
[0925:1234]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- 
TAbort- MAbort+ SERR- PERR- INTx-
Latency: 64, Cache Line Size: 32 bytes
Interrupt: pin D routed to IRQ 9
Region 4: I/O ports at c000 [size=32]
Capabilities: access denied
Kernel driver in use: uhci_hcd

00:07.3 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI USB 1.1 
Controller [1106:3038] (rev 10) (prog-if 00 [UHCI])
Subsystem: First International Computer, Inc. VA-502 Mainboard 
[0925:1234]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- 
TAbort- MAbort- SERR- PERR- INTx-
Latency: 64, Cache Line Size: 32 bytes
Interrupt: pin D routed to IRQ 9
Region 4: I/O ports at c400 [size=32]
Capabilities: access denied
Kernel driver in use: uhci_hcd

00:07.4 SMBus [0c05]: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] 
[1106:3057] (rev 30)
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- 
TAbort- MAbort- SERR- PERR- INTx-
Interrupt: pin ? routed to IRQ 11
Capabilities: access denied

00:07.5 Multimedia audio controller [0401]: VIA Technologies, Inc. VT82C686 
AC97 Audio Controller [1106:3058] (rev 20)
Subsystem: Giga-byte Technology Onboard Audio [1458:7600]
Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-

Bug#561890: lenny kernel memory leak?

2010-05-05 Thread Moritz Muehlenhoff 
On Mon, Dec 21, 2009 at 01:59:33AM +, Ben Hutchings wrote:
  Forwarded Message 
 From: Mikko Rapeli mikko.rap...@iki.fi
 To: Debian kernel team debian-kernel@lists.debian.org
 Subject: Re: lenny kernel memory leak?
 Date: Mon, 21 Dec 2009 00:53:35 +0200
 
 On Sun, Dec 20, 2009 at 04:30:54PM +, Ben Hutchings wrote:
  Try c95edf5432f097c926dd3f59239ecde80da3b214 rt2x00: Properly clean up
  beacon skbs.
 
 With this I got kernel panics at boot when loading the modules. Maybe it
 depends on some other patches.
 
   http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=e7087a828f8714e464fff18d93618727530dfd89;hp=5adf6d63c1697ce1835daf2b5393488a71ee0dca
 
 This is now in. Will see if it makes any difference in a few days.

Did it fix the issue?

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/20100505214742.ga5...@galadriel.inutil.org

Bug#565225: /var/lib/dpkg/info/linux-base.postinst will need to be adjusted too

2010-05-05 Thread jidanni 
Note /var/lib/dpkg/info/linux-base.postinst also has
/etc/initramfs-tools/conf.d/resume in 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/871vdq3szp@jidanni.org

Bug#562981: rt2860-source: connection drops - debian kernel 2.6.32

2010-05-05 Thread Moritz Muehlenhoff 
tags 562981 moreinfo
thanks

On Tue, Dec 29, 2009 at 08:39:12PM +, Ben Hutchings wrote:
 On Tue, 2009-12-29 at 12:02 -0600, Timothee Besset wrote:
  Package: rt2860-source
  Severity: important
  
  On latest sid kernel:
  Linux plageis 2.6.32-trunk-amd64 #1 SMP Thu Dec 17 06:29:18 UTC 2009
  x86_64 GNU/Linux
  
  My wireless connection suddenly drops after 20 to 30 minutes of usage,
  especially when I run the program synergy between my machines (if I am
  not running synergy it can take many hours between every drops).
  
  In the syslog I see:
  ERROR!!! RTMPCancelTimer failed, Timer hasn't been initialize!
  right as the connection drops
  
  at that point only solution is:
  ifdown wlan0 ; rmmod rt2860sta ; sleep 2 ; modprobe rt2860sta ; ifup wlan0
  
  I am not sure where else to report this, I found this package from
  http://wiki.debian.org/rt2860sta and the vendor's support page returns a
  404 (http://www.ralinktech.com/ralink/Home/Support/Linux.html)
 
 rt2860sta is now included in kernel packages (among the 'staging'
 drivers).  This bug has been reassigned accordingly.  Please follow up
 to this bug report (#562981) using reportbug, which should automatically
 include some useful information about your system.

Timothee, does this still occur with latest kernels? If so, could
you follow up as outlined by Ben?

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/20100505215128.ga5...@galadriel.inutil.org

Bug#567034: [xserver-xorg-video-intel] when using KMS, X puts the monitor directly into power saving mode upon startup[945G]

2010-05-05 Thread Moritz Muehlenhoff 
tags 567034 moreinfo
thanks

On Tue, Jan 26, 2010 at 01:51:38PM -0600, Joe Neal wrote:
 Package: xserver-xorg-video-intel
 Version: 2:2.9.1-2
 Severity: important
 
 --- Please enter the report below this line. ---
 When X starts the monitor immediately flashes that it is going into power 
 saving mode, before a display manager has a chance to start.   It wakes upon 
 entering ctl-alt-F1 through ctl-alt-F6 but returns to power saving mode with 
 control-alt-F7.
 
 Top, etc indicates that X is in fact running. 
 
 Disabling KMS solves the problem
 
 Attached is a log from one of the failed X startup attempts rather than the 
 most recent successful one without KMS.
 
 If any further info is needed, let me know.

There have been a lot of changes to the KMS code, does this still occur with
latest sid kernels?

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/20100505215307.ga6...@galadriel.inutil.org

Bug#580426: check for effects of GRUB_DISABLE_LINUX_UUID=true

2010-05-05 Thread jidanni 
Package: linux-base
Version: 2.6.33-1~experimental.4
Severity: wishlist

Hello. I notice the linux-base package snoops around to get a list of
changes the user needs to approve.

Well, there is one item it forgot to investigate:
If the user has
GRUB_DISABLE_LINUX_UUID=true in his grub configuration,
well, he will very likely get stuck in waiting for the root filesystem
and thus no be able to boot, at least with linux-image-2.6.33-2-686,
with more than a single partition.

Therefore your script should perhaps poke around /boot/grub/grub.cfg,
update the entries there, and warn the user not to probably use
GRUB_DISABLE_LINUX_UUID=true anymore.

P.S., I am very curious, if one day, for some reason, the user finds
himself locked out of the system due to not having the proper UUID at
boot, whereas in the past, he could edit the boot command line (e.g.,
by typing e in grub), and fill in some guesses like /dev/hda1,
/dev/hda2 etc. until he got the right one where the root filesystem
lives, but nowadays, with no alternative to the very long UUID strings,
there is no way he is going to guess it, so he won't be booting for a
very long while?

E.g., when I noticed the above problem, that I still was using
/dev/hda11 in /boot/grub/grub.cfg and what thus no longer to boot upon
upgrading to linux-image-2.6.33-2-686, than goodness I had an older
kernel that could still boot using /dev/hda11 so I could get in and
rerun grub without GRUB_DISABLE_LINUX_UUID=true in order to make a
/boot/grub/grub.cfg that linux-image-2.6.33-2-686 could deal with.

So maybe this new UUID stuff should be fitted with an escape hatch,
where saying something like UUID=/dev/hda11 could perhaps be give the
user a tiny chance to be able to boot in case he somehow doesn't have
the full UUID at hand.

P.S., I took a look in /var/lib/dpkg/info/linux-base.postinst and all I
can say is that the bottom line is are you sure there is UUIDs on each
relevant line in /boot/grub/grub.cfg.

Note that I use
grub-pc:
  Installed: 1.96+20080724-16
  Candidate: 1.98-1
but that shouldn't matter, as your script shouldn't need to know exactly
which version I use or why I hold back a little.



-- 
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/87fx26t6he@jidanni.org

Bug#567965: i915: KMS framebuffer fails to work, only X works

2010-05-05 Thread Moritz Muehlenhoff 
tags 567965 moreinfo
thanks

On Mon, Feb 01, 2010 at 04:10:32PM +0100, Julian Andres Klode wrote:
 Package: linux-2.6
 Version: 2.6.32-5
 Severity: important
 
 Since a few days, my screen stays black except for VT7 where X is
 running. As soon as the kernel is loaded, the screen turns black
 until X is loaded. When X is loaded, switching to anything else
 than VT7 just causes the mouse pointer to disappear, but the
 image from X is still displayed.
 
 I don't know when exactly this started to happen, but I
 know that my last kernel update was 2.6.32-3 = 2.6.32-5.

There have been many changes to the KMS code, does this still occur with
current sid kernel and X.org?

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/20100505215642.ga6...@galadriel.inutil.org

Re: [kernel] r15627 - in dists/sid/linux-2.6/debian: . config

2010-05-05 Thread maximilian attems 
On Wed, May 05, 2010 at 09:41:18PM +, Moritz Muehlenhoff wrote:
 Author: jmm
 Date: Wed May  5 21:41:16 2010
 New Revision: 15627
 
 Log:
 Enable tomoyo (Closes: #562486)

nack,
according to above nobody did the size check.

what about abi check, not possibly done!?
 


-- 
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/20100505215152.gs19...@baikonur.stro.at

Bug#580426: marked as done (check for effects of GRUB_DISABLE_LINUX_UUID=true)

2010-05-05 Thread Debian Bug Tracking System 
Your message dated Thu, 6 May 2010 00:10:06 +0200
with message-id 20100505221006.gu19...@baikonur.stro.at
and subject line Re: Bug#580426: check for effects of 
GRUB_DISABLE_LINUX_UUID=true
has caused the Debian Bug report #580426,
regarding check for effects of GRUB_DISABLE_LINUX_UUID=true
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.)


-- 
580426: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580426
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-base
Version: 2.6.33-1~experimental.4
Severity: wishlist

Hello. I notice the linux-base package snoops around to get a list of
changes the user needs to approve.

Well, there is one item it forgot to investigate:
If the user has
GRUB_DISABLE_LINUX_UUID=true in his grub configuration,
well, he will very likely get stuck in waiting for the root filesystem
and thus no be able to boot, at least with linux-image-2.6.33-2-686,
with more than a single partition.

Therefore your script should perhaps poke around /boot/grub/grub.cfg,
update the entries there, and warn the user not to probably use
GRUB_DISABLE_LINUX_UUID=true anymore.

P.S., I am very curious, if one day, for some reason, the user finds
himself locked out of the system due to not having the proper UUID at
boot, whereas in the past, he could edit the boot command line (e.g.,
by typing e in grub), and fill in some guesses like /dev/hda1,
/dev/hda2 etc. until he got the right one where the root filesystem
lives, but nowadays, with no alternative to the very long UUID strings,
there is no way he is going to guess it, so he won't be booting for a
very long while?

E.g., when I noticed the above problem, that I still was using
/dev/hda11 in /boot/grub/grub.cfg and what thus no longer to boot upon
upgrading to linux-image-2.6.33-2-686, than goodness I had an older
kernel that could still boot using /dev/hda11 so I could get in and
rerun grub without GRUB_DISABLE_LINUX_UUID=true in order to make a
/boot/grub/grub.cfg that linux-image-2.6.33-2-686 could deal with.

So maybe this new UUID stuff should be fitted with an escape hatch,
where saying something like UUID=/dev/hda11 could perhaps be give the
user a tiny chance to be able to boot in case he somehow doesn't have
the full UUID at hand.

P.S., I took a look in /var/lib/dpkg/info/linux-base.postinst and all I
can say is that the bottom line is are you sure there is UUIDs on each
relevant line in /boot/grub/grub.cfg.

Note that I use
grub-pc:
  Installed: 1.96+20080724-16
  Candidate: 1.98-1
but that shouldn't matter, as your script shouldn't need to know exactly
which version I use or why I hold back a little.


---End Message---
---BeginMessage---
On Thu, May 06, 2010 at 04:54:05AM +0800, jida...@jidanni.org wrote:
 Package: linux-base
 Version: 2.6.33-1~experimental.4
 Severity: wishlist
 
 Hello. I notice the linux-base package snoops around to get a list of
 changes the user needs to approve.
 
 Well, there is one item it forgot to investigate:
 If the user has
 GRUB_DISABLE_LINUX_UUID=true in his grub configuration,

such a configuration is not default and user fault.

not supported.

 well, he will very likely get stuck in waiting for the root filesystem
 and thus no be able to boot, at least with linux-image-2.6.33-2-686,
 with more than a single partition.
 
 Therefore your script should perhaps poke around /boot/grub/grub.cfg,
 update the entries there, and warn the user not to probably use
 GRUB_DISABLE_LINUX_UUID=true anymore.
 
 P.S., I am very curious, if one day, for some reason, the user finds
 himself locked out of the system due to not having the proper UUID at
 boot, whereas in the past, he could edit the boot command line (e.g.,
 by typing e in grub), and fill in some guesses like /dev/hda1,
 /dev/hda2 etc. until he got the right one where the root filesystem
 lives, but nowadays, with no alternative to the very long UUID strings,
 there is no way he is going to guess it, so he won't be booting for a
 very long while?
 
 E.g., when I noticed the above problem, that I still was using
 /dev/hda11 in /boot/grub/grub.cfg and what thus no longer to boot upon
 upgrading to linux-image-2.6.33-2-686, than goodness I had an older
 kernel that could still boot using /dev/hda11 so I could get in and
 rerun grub without GRUB_DISABLE_LINUX_UUID=true in order to make a
 /boot/grub/grub.cfg that linux-image-2.6.33-2-686 could deal with.
 
 So maybe this new UUID stuff should be fitted with an escape hatch,
 where saying something like UUID=/dev/hda11 could perhaps be give the
 user a tiny chance to be able to boot in case

Processed: Re: Bug#580424: linux-image-2.6.32-5-686 breaks framebuffer and X

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

 tags 580424 moreinfo
Bug #580424 [linux-2.6] linux-image-2.6.32-5-686 breaks framebuffer and X
Added tag(s) moreinfo.
 stop
Stopping processing here.

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


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

Processed: severity of 579852 is important

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

 severity 579852 important
Bug #579852 [linux-modules-2.6.26-2-xen-amd64] ext3_free_blocks: Freeing blocks 
not in datazone error on heavy disk activity
Severity set to 'important' from 'grave'

 thanks
Stopping processing here.

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


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

Processed: severity of 576800 is important

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

 severity 576800 important
Bug #576800 [linux-2.6] libc6: Cannot create new processes after hibernating
Severity set to 'important' from 'critical'

 thanks
Stopping processing here.

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


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

Processed: severity of 580068 is important

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

 severity 580068 important
Bug #580068 [linux-2.6] Data corruption using NFS + dm-crypt
Severity set to 'important' from 'grave'

 thanks
Stopping processing here.

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


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

Bug#580424: linux-image-2.6.32-5-686 breaks framebuffer and X

2010-05-05 Thread maximilian attems 
tags 580424 moreinfo
stop

On Wed, May 05, 2010 at 11:48:23PM +0200, Luca Falavigna wrote:
 Package: linux-2.6
 Version: 2.6.32-12
 Severity: normal
 
 Recent upgrade of kernel linux-image-2.6.32-5-686 broke framebuffer support 
 on VTs
 and limits maximum resolution to 1024x768 while running X.
 
 Rebooting with linux-image-2.6.32-3-686, everything is fine.

there were many changes since, did you check 2.6.32-4-686??
 
also what is your /proc/cmdline

it be cool if you'd specify the error and also send a dmesg.



-- 
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/20100505220714.gt19...@baikonur.stro.at

openvz patch updated to v2.6.32-avdeyev

2010-05-05 Thread maximilian attems 
linux-2.6 2.6.32-12 contains aboves latest openvz patch.
please hammer it out.

2.6.32-12 might reach testing, depending on assesment of
http://bugs.debian.org/572618

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/20100505160052.ga15...@stro.at

Bug#580435: smartmontools not checked for

2010-05-05 Thread jidanni 
Package: linux-base
Version: 2.6.33-1~experimental.4
X-debbugs-Cc: smartmonto...@packages.debian.org
Severity: wishlist

/var/lib/dpkg/info/linux-base.postinst doesn't detect that
/etc/smartd.conf had /dev/hda listed. Now smartmontools doesn't start
with linux-image-2.6.33-2-686 .

I looked in /dev/disk/by-uuid but did not see a way to refer to an
entire disk, so don't know how to fix it by hand.



-- 
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/87iq716gvf@jidanni.org

Bug#577227: linux-2.6: [INTL:pt] Updated Portuguese translation for debconf messages

2010-05-05 Thread Américo Monteiro 
Package: linux-2.6
Version: n/a
Tags: l10n, patch
Severity: wishlist

Updated Portuguese translation for linux-2.6's debconf messages.
Translator: Américo Monteiro a_monte...@netcabo.pt
Feel free to use it.

For translation updates please contact 'Last Translator' or the
Portuguese Translation Team traduz at debianpt.org.

This patch was updated after the revision on the english messages made by 
Christian Perrier.

-- 
Best regards,

Américo Monteiro
Traduz - Portuguese Translation Team
http://www.DebianPT.org
# Translation of linux-2.6 debconf messages to Portuguese
# Copyright (C) 2010 the linux-2.6's copyright holder
# This file is distributed under the same license as the linux-2.6 package.
#
# Américo Monteiro a_monte...@netcabo.pt, 2010.
msgid 
msgstr 
Project-Id-Version: linux-2.6 2.6.32-11\n
Report-Msgid-Bugs-To: \n
POT-Creation-Date: 2010-04-23 22:14+0200\n
PO-Revision-Date: 2010-04-23 22:12+0100\n
Last-Translator: Américo Monteiro a_monte...@netcabo.pt\n
Language-Team: Portuguese tra...@debianpt.org\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit\n
X-Generator: Lokalize 1.0\n
Plural-Forms: nplurals=2; plural=(n != 1);\n

#. Type: boolean
#. Description
#: ../linux-base.templates:2001
msgid Update disk device IDs in system configuration?
msgstr 
Actualizar os IDs dos dispositivos de disco na configuração do sistema?

#. Type: boolean
#. Description
#: ../linux-base.templates:2001
msgid 
The new Linux kernel version provides different drivers for some PATA (IDE) 
controllers. The names of some hard disk, CD-ROM, and tape devices may 
change.
msgstr 
A nova versão de kernel Linux disponibiliza drivers diferentes para alguns 
controladores PATA (IDE). Os nomes de alguns discos rígidos, CD-ROM e 
dispositivos de fita magnética poderão mudar.

#. Type: boolean
#. Description
#: ../linux-base.templates:2001
msgid 
It is now recommended to identify disk devices in configuration files by 
label or UUID (unique identifier) rather than by device name, which will 
work with both old and new kernel versions.
msgstr 
Agora é recomendado identificar os dispositivos de discos nos ficheiros de 
configuração pela etiqueta ou UUID (identificador único) em vez do nome de 
dispositivo, o qual irá funcionar com ambas versões de kernel antiga e nova.

#. Type: boolean
#. Description
#: ../linux-base.templates:2001
msgid 
If you choose to not update the system configuration automatically, you must 
update device IDs yourself before the next system reboot or the system may 
become unbootable.
msgstr 
Se escolher não actualizar a configuração do sistema automaticamente, você 
tem de actualizar os IDs dos dispositivos antes de reiniciar o sistema ou o 
sistema pode não arrancar.

#. Type: boolean
#. Description
#. Type: boolean
#. Description
#: ../linux-base.templates:3001 ../linux-base.templates:4001
msgid Apply configuration changes to disk device IDs?
msgstr 
Aplicar estas alterações de configuração aos IDs de dispositivos de discos?

#. Type: boolean
#. Description
#: ../linux-base.templates:3001
msgid These devices will be assigned UUIDs or labels:
msgstr A estes dispositivos serão atribuídos UUIDs ou etiquetas:

#. Type: boolean
#. Description
#. Type: boolean
#. Description
#: ../linux-base.templates:3001 ../linux-base.templates:4001
msgid These configuration files will be updated:
msgstr Estes ficheiros de configuração irão ser actualizados:

#. Type: boolean
#. Description
#. Type: boolean
#. Description
#: ../linux-base.templates:3001 ../linux-base.templates:4001
msgid The device IDs will be changed as follows:
msgstr Os IDs de dispositivos irão ser alterados de acordo com o seguinte:

#. Type: error
#. Description
#: ../linux-base.templates:5001
msgid Configuration files still contain deprecated device names
msgstr 
Os ficheiros de configuração ainda contêm nomes obsoletos de dispositivos

#. Type: error
#. Description
#: ../linux-base.templates:5001
msgid 
The following configuration files still use some device names that may 
change when using the new kernel:
msgstr 
Os seguintes ficheiros de configuração ainda usam alguns nomes de 
dispositivos que podem alterar quando usar o novo kernel:

#. Type: error
#. Description
#: ../linux-base.templates:6001
msgid Boot loader configuration check needed
msgstr Necessária verificação da configuração do gestor de arranque

#. Type: error
#. Description
#: ../linux-base.templates:6001
msgid 
The boot loader configuration for this system was not recognized. These 
settings in the configuration may need to be updated:
msgstr 
A configuração do gestor de arranque para este sistema não foi reconhecida. 
Estas definições na configuração podem precisar de ser actualizadas:

#. Type: error
#. Description
#: ../linux-base.templates:6001
msgid 
 * The root device ID passed as a kernel parameter;\n
 * The boot device ID used to install and update the boot loader.
msgstr 
 * O ID do dispositivo root passado como parâmetro do

Bug#580426: check for effects of GRUB_DISABLE_LINUX_UUID=true

2010-05-05 Thread Ben Hutchings 
On Thu, 2010-05-06 at 04:54 +0800, jida...@jidanni.org wrote:
 Package: linux-base
 Version: 2.6.33-1~experimental.4
 Severity: wishlist
 
 Hello. I notice the linux-base package snoops around to get a list of
 changes the user needs to approve.
 
 Well, there is one item it forgot to investigate:
 If the user has
 GRUB_DISABLE_LINUX_UUID=true in his grub configuration,
 well, he will very likely get stuck in waiting for the root filesystem
 and thus no be able to boot, at least with linux-image-2.6.33-2-686,
 with more than a single partition.
 
 Therefore your script should perhaps poke around /boot/grub/grub.cfg,
 update the entries there, and warn the user not to probably use
 GRUB_DISABLE_LINUX_UUID=true anymore.

Well, if you do that, it's your own problem.  We cannot cover every
possible strange configuration.

 P.S., I am very curious, if one day, for some reason, the user finds
 himself locked out of the system due to not having the proper UUID at
 boot, whereas in the past, he could edit the boot command line (e.g.,
 by typing e in grub), and fill in some guesses like /dev/hda1,
 /dev/hda2 etc. until he got the right one where the root filesystem
 lives, but nowadays, with no alternative to the very long UUID strings,
 there is no way he is going to guess it, so he won't be booting for a
 very long while?
[...]

Device names still work, they just changed (and may change again if you
have a USB storage device plugged in).

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


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

Processed: tagging 580426

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

 tags 580426 wontfix
Bug #580426 {Done: maximilian attems m...@stro.at} [linux-base] check for 
effects of GRUB_DISABLE_LINUX_UUID=true
Added tag(s) wontfix.
 thanks
Stopping processing here.

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


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

Bug#580124: linux-image-2.6.32-4-amd64: kernel allocation failure in iwl_rx_allocate

2010-05-05 Thread Ben Hutchings 
On Mon, 2010-05-03 at 23:58 +0530, Ritesh Raj Sarraf wrote:
 Package: linux-2.6
 Version: 2.6.32-11
 Severity: normal
 
 I often keep getting this allocation failure message. My gut feel is
 that it gets triggered when I do some I/O. Today, it got triggered when
 I was copying a couple of Gig data from my local encrypted backup
 partition to an external USB disk.
[...]

This is a bug/limitation in the iwlwifi drivers.  It appears to be fixed
in Linux 2.6.33, but it requires quite a large change.  The next release
of Debian will be based on Linux 2.6.32 and I don't know whether we will
be able to apply that change.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


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

Bug#580124: linux-image-2.6.32-4-amd64: kernel allocation failure in iwl_rx_allocate

2010-05-05 Thread Ben Hutchings 
tag 580124 fixed-upstream
thanks

This should be fixed by the following upstream changes included in Linux
2.6.33:

commit 2f301227a1ede57504694e1f64839839f5737cac
Author: Zhu Yi yi@intel.com
Date:   Fri Oct 9 17:19:45 2009 +0800

iwlwifi: use paged Rx

commit fafaf31bf9f965d91462ee115e27ef6c262b74ea
Author: Shanyu Zhao shanyu.z...@intel.com
Date:   Thu Feb 11 10:42:22 2010 -0800

iwlwifi: fix AMSDU Rx after paged Rx patch

I don't know whether it is possible to cherry-pick them.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


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

Processed: Re: Bug#580124: linux-image-2.6.32-4-amd64: kernel allocation failure in iwl_rx_allocate

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

 tag 580124 fixed-upstream
Bug #580124 [linux-2.6] linux-image-2.6.32-4-amd64: kernel allocation failure 
in iwl_rx_allocate
Added tag(s) fixed-upstream.
 thanks
Stopping processing here.

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


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