Processed: Bug#553441: (ämne saknas)

[Debian Bug Tracking System]

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

> severity 553441 normal
Bug #553441 [firmware-ralink] firmware-ralink: Firmware not working with usb 
dongle rt2870sta
Severity set to 'normal' from 'important'

> 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

Bug#540923: marked as done (wireless card not working anymore after suspend-to-ram)

[Debian Bug Tracking System]

Your message dated Wed, 6 Jan 2010 05:32:29 +0100
with message-id <20100106043229.gn29...@gamma.logic.tuwien.ac.at>
and subject line Re: after suspend to ram wicd cannot find any networks anymore
has caused the Debian Bug report #540923,
regarding wireless card not working anymore after suspend-to-ram
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.)


-- 
540923: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=540923
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wicd
Version: 1.6.1-3
Severity: normal

Hi all,

this email is going cc to lkml and the iwl devel list since I don't know
where it actually belongs.

After suspend to ram and wake up, which works fine, the wireless card
does not work at all. I thought it is hal/dbus so I restarted the 
dbus service (which in turn restarted hal, wicd, and several others),
but to no effect. The wireless is gone, no network found.

If anyone on these lists can provide pointers how to debug that, or
where the bug really belong that would be fine.

kernel: 2.6.31-rc5
Debian/sid

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

Kernel: Linux 2.6.31-rc5 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages wicd depends on:
ii  adduser 3.110add and remove users and groups
ii  debconf [debconf-2.0]   1.5.27   Debian configuration management sy
ii  dhcp3-client3.1.2p1-1DHCP client
ii  dhcpcd  1:3.2.3-3DHCP client for automatically conf
ii  ethtool 6+20090307-1 display or change Ethernet device 
ii  iproute 20090324-1   networking and traffic control too
ii  lsb-base3.2-23   Linux Standard Base 3.2 init scrip
ii  net-tools   1.60-23  The NET-3 networking toolkit
ii  psmisc  22.8-1   utilities that use the proc file s
ii  python  2.5.4-2  An interactive high-level object-o
ii  python-dbus 0.83.0-1 simple interprocess messaging syst
ii  python-glade2   2.14.1-3 GTK+ bindings: Glade support
ii  python-gtk2 2.14.1-3 Python bindings for the GTK+ widge
ii  python-support  1.0.3automated rebuilding support for P
ii  python-urwid0.9.8.4-1curses-based UI/widget library for
ii  wireless-tools  29-2 Tools for manipulating Linux Wirel
ii  wpasupplicant   0.6.9-3  client support for WPA and WPA2 (I

Versions of packages wicd recommends:
ii  gksu  2.0.2-2+b1 graphical frontend to su
ii  sudo  1.7.2-2Provide limited super user privile

Versions of packages wicd suggests:
ii  pm-utils  1.2.5-4utilities and scripts for power ma

-- debconf information:
* wicd/users: norbert
* wicd/notice:


--- End Message ---
--- Begin Message ---
I am closing this bug. I found out that it actually depends on the
access point. With some points I have no problem to associate
after s2r. Only that the one I have at home seems to be on the bad
side.

So it is not 100% reproducible, I guess we forget it.

Best wishes

Norbert

Norbert Preiningprein...@{jaist.ac.jp, logic.at, debian.org}
JAIST, JapanTU Wien, Austria   Debian TeX Task Force
DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094

COTTERSTOCK (n.)
A piece of wood used to stir paint and thereafter stored uselessly in
a shed in perpetuity.
--- Douglas Adams, The Meaning of Liff

--- End Message ---

Bug#562975: linux-2.6: patch for CVE-2009-3939

[Ben Hutchings]

On Tue, 2010-01-05 at 22:47 -0500, Michael Gilbert wrote:
> > Actually, no Debian release contains a kernel version affected by
> > CVE-2009-3889.
> 
> CVE-2009-3889 was fixed in upstream commit 66dca9b8 in linux 2.6.27, so
> debian's 2.6.24 and 2.6.26 are affected, but 2.6.18 and 2.6.32 are not.
> You can look at the dbg_lvl permissions, for example in the 2.6.32
> kernel, to see that they are correctly restrictive, S_IWUSR.

Yes, I can see that.  I was checking which versions had the dbg_lvl
parameter and I must have got confused.

> > CVE-2009-3889 should be dealt with at the same time.  That covers the
> > dbg_lvl parameter which is also world-writable.
> 
> For 2.6.32, CVE-2009-3939 will need to be patched separately since
> CVE-2009-3889 is already fixed there.
> 
> As a minor aside, please include nn-submitter in your replies so
> your bug reporters get CC'd.  I just happened to be looking at my
> submitted bugs recently when I came across your messages.

Sorry; I usually do that.

Ben.

-- 
Ben Hutchings
Horngren's Observation:
   Among economists, the real world is often a special case.


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

Bug#449272: marked as done (Alternative (buggy, incomplete) firewire stack shipped instead of the stable one)

[Debian Bug Tracking System]

Your message dated Wed, 06 Jan 2010 04:24:57 +
with message-id <1262751897.2377.16.ca...@localhost>
and subject line Re: Alternative (buggy, incomplete) firewire stack shipped 
instead of the stable one
has caused the Debian Bug report #449272,
regarding Alternative (buggy, incomplete) firewire stack shipped instead of the 
stable one
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.)


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

Debian choose to ship the alternative firewire stack on recent kernels.
Firewire maintainers are not recommending this (see
http://wiki.linux1394.org/JujuMigration) yet, since this new firewire stack
is incomplete. For instance, I can't do ethernet over firewire with 2.6.22,
I have to go back to 2.6.18, which gives me other kind of trouble.


-- Package-specific info:
** Version:
Linux version 2.6.22-3-686 (Debian 2.6.22-5) (m...@debian.org) (gcc version
4.1.3 20071019 (prerelease) (Debian 4.1.2-17)) #1 SMP Mon Oct 22 22:11:56
UTC 2007
--- End Message ---
--- Begin Message ---
DV capture works for me using the test program included in
.
Therefore I believe that kino is at fault, not the kernel.

Ben.

-- 
Ben Hutchings
Horngren's Observation:
   Among economists, the real world is often a special case.


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

Bug#555010: marked as done (Errors in new firewire stack, DV camera don't work anymore)

[Debian Bug Tracking System]

Your message dated Wed, 06 Jan 2010 04:24:57 +
with message-id <1262751897.2377.16.ca...@localhost>
and subject line Re: Alternative (buggy, incomplete) firewire stack shipped 
instead of the stable one
has caused the Debian Bug report #449272,
regarding Errors in new firewire stack, DV camera don't work anymore
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.)


-- 
449272: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=449272
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dvgrab
Version: 3.4-1
Severity: grave
Justification: renders package unusable

Dvgrab needs the kernel creates a dv1394 device to be usable. The newer kernels 
uses a new ieee1394 stack and only creates a fw0 device, so dvgrab starts the 
record and ends a bit later because it dont find the video device.
Dvgrab should uncompatible with newer kernel versions, those that uses the nre 
ieee1394 stack.


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

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

Versions of packages dvgrab depends on:
ii  libavc1394-0   0.5.3-1+b2control IEEE 1394 audio/video devi
ii  libc6  2.9-25GNU C Library: Shared libraries
ii  libdv4 1.0.0-2   software library for DV format dig
ii  libgcc11:4.4.1-4 GCC support library
ii  libiec61883-0  1.2.0-0.1 an partial implementation of IEC 6
ii  libjpeg62  6b-15 The Independent JPEG Group's JPEG 
ii  libquicktime1  3:1.1.3-0.4   library for reading and writing Qu
ii  libraw1394-11  2.0.2-2   library for direct access to IEEE 
ii  libstdc++6 4.4.1-4   The GNU Standard C++ Library v3
ii  zlib1g 1:1.2.3.3.dfsg-15 compression library - runtime

dvgrab recommends no packages.

dvgrab suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
DV capture works for me using the test program included in
.
Therefore I believe that kino is at fault, not the kernel.

Ben.

-- 
Ben Hutchings
Horngren's Observation:
   Among economists, the real world is often a special case.


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

Processed: unmerging 545112, tagging 545112 ..., reassign 545112 to dvgrab, severity of 545112 is grave

[Debian Bug Tracking System]

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

> unmerge 545112
Bug#545112: Errors in new firewire stack, DV camera don't work anymore
Bug#449272: Alternative (buggy, incomplete) firewire stack shipped instead of 
the stable one
Bug#555010: Errors in new firewire stack, DV camera don't work anymore
Disconnected #545112 from all other report(s).

> tags 545112 - moreinfo
Bug #545112 [linux-2.6] Errors in new firewire stack, DV camera don't work 
anymore
Removed tag(s) moreinfo.
> retitle 545112 dvgrab: does not work properly with Juju firewire stack
Bug #545112 [linux-2.6] Errors in new firewire stack, DV camera don't work 
anymore
Changed Bug title to 'dvgrab: does not work properly with Juju firewire stack' 
from 'Errors in new firewire stack, DV camera don't work anymore'
> reassign 545112 dvgrab
Bug #545112 [linux-2.6] dvgrab: does not work properly with Juju firewire stack
Bug reassigned from package 'linux-2.6' to 'dvgrab'.
Bug No longer marked as found in versions 2.6.30-8 and 2.6.31-1~experimental.2.
> # dvgrab appears to be useless with the Debian-packaged kernel
> severity 545112 grave
Bug #545112 [dvgrab] dvgrab: does not work properly with Juju firewire stack
Severity set to 'grave' from 'important'

>
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

Bug#562975: linux-2.6: patch for CVE-2009-3939

[Michael Gilbert]

> Actually, no Debian release contains a kernel version affected by
> CVE-2009-3889.

CVE-2009-3889 was fixed in upstream commit 66dca9b8 in linux 2.6.27, so
debian's 2.6.24 and 2.6.26 are affected, but 2.6.18 and 2.6.32 are not.
You can look at the dbg_lvl permissions, for example in the 2.6.32
kernel, to see that they are correctly restrictive, S_IWUSR.

> CVE-2009-3889 should be dealt with at the same time.  That covers the
> dbg_lvl parameter which is also world-writable.

For 2.6.32, CVE-2009-3939 will need to be patched separately since
CVE-2009-3889 is already fixed there.

As a minor aside, please include nn-submitter in your replies so
your bug reporters get CC'd.  I just happened to be looking at my
submitted bugs recently when I came across your messages.

Thanks,
Mike



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#545112: Errors in new firewire stack, DV camera don't work anymore

[Ben Hutchings]

I wrote a really simple DV capture program myself (see below), and it
works just fine with the Debian packaged kernel
(linux-image-2.6.32-trunk-amd64 2.6.32-3).  dvgrab continues to fail.  I
conclude that dvgrab is at fault, not the kernel.

Note that this program writes DV to stdout; you had better redirect it!

Ben.

/* BEGIN */
#include 
#include 
#include 
#include 

#include 

static unsigned long long total_len;
static unsigned int dropped_packets;
static unsigned int dropped_frames;
static unsigned int complete_frames;

static unsigned int seq_count;
static unsigned int next_seq_num;
static unsigned int next_block_num;
static unsigned char frame_buf[144000];

static enum raw1394_iso_disposition
receive(raw1394handle_t handle,
unsigned char * data,
unsigned int len,
unsigned char channel,
unsigned char tag,
unsigned char sy,
unsigned int cycle,
unsigned int dropped)
{
total_len += len;
dropped_packets += dropped;

if (len == 488)
{
unsigned int seq_num, typed_block_num, block_num;

// Skip firewire header
data += 8;

// Find position of these blocks in the sequence
seq_num = data[1] >> 4;
typed_block_num = data[2];
block_num = -1;
switch (data[0] >> 5)
{
case 0:
// Header: position 0
if (typed_block_num == 0)
block_num = 0;
break;
case 3:
// Audio: position 6 or 102
if (typed_block_num < 9)
block_num = 6 + typed_block_num * 16;
break;
case 4:
// Video: any other position divisible by 6
if (typed_block_num < 135)
block_num = 7 + typed_block_num + typed_block_num / 15;
break;
}

// Are these the blocks we're expecting?
if (seq_num == next_seq_num && block_num == next_block_num)
{
// Set sequence count from the first block of the frame
if (seq_num == 0 && block_num == 0)
seq_count = (data[3] & 0x80) ? 12 : 10;

// Append blocks to frame
memcpy(frame_buf + (seq_num * 150 + block_num) * 80, data, 480);

// Advance position in sequence
next_block_num = block_num + 6;
if (next_block_num == 150)
{
// Advance to next sequence
next_block_num = 0;
++next_seq_num;
if (next_seq_num == seq_count)
{
// Finish frame
write(1, frame_buf, seq_count * 150 * 80);
++complete_frames;
next_seq_num = 0;
}
}
}
else if (next_seq_num != 0 || next_block_num != 0)
{
++dropped_frames;
next_seq_num = 0;
next_block_num = 0;
}
}

return RAW1394_ISO_OK;
}

int main(void)
{
raw1394handle_t handle;
int n_ports, n_ports_again, i;
struct raw1394_portinfo * ports;

handle = raw1394_new_handle();
if (!handle)
{
perror("raw1394_new_handle");
return 1;
}
n_ports = raw1394_get_port_info(handle, NULL, 0);
assert(n_ports >= 0);
ports = calloc(n_ports, sizeof(*ports));
if (!ports)
{
perror("calloc");
return 1;
}
n_ports_again = raw1394_get_port_info(handle, ports, n_ports);
if (n_ports > n_ports_again)
n_ports = n_ports_again;
if (n_ports == 0)
{
fprintf(stderr, "no remote ports found\n");
return 1;
}

for (i = 0; i < n_ports; i++)
fprintf(stderr, "node %d name \"%s\"\n", ports[i].nodes, ports[i].name);
fprintf(stderr, "selected node %d\n", ports[0].nodes);

if (raw1394_set_port(handle, 0))
{
perror("raw1394_set_port");
return 1;
}

if (raw1394_iso_recv_init(handle, receive, /*buf_packets=*/ 600,
  /*max_packet_size=*/ 496, /*channel=*/ 63,
  /*mode=*/ RAW1394_DMA_DEFAULT,
  /*irq_interval=*/ 100))
{
perror("raw1394_iso_recv_init");
return 1;
}

if (raw1394_iso_recv_start(handle, -1, -1, -1))
{
perror("raw1394_iso_recv_start");
return 1;
}

fprintf(stderr, "Press any key to exit\n");

for (;;)
{
int fw_fd = raw1394_get_fd(handle);
fd_set rfds, xfds;

FD_ZERO(&rfds);
FD_ZERO(&xfds);
FD_SET(0, &rfds);
FD_SET(fw_fd, &rfds);
FD_SET(fw_fd, &xfds);
if (select(fw_fd + 1, &rfds, NULL, &xfds, NULL) <= 0 ||
FD_ISSET(0, &rfds) || FD_ISSET(fw_fd, &xfds) ||
raw1394_loop_iterate(handle) < 0)
break;
}

raw1394_iso_stop(handle);
raw1394_iso_shutdown(handle);

fprintf(stderr, "Total length received: %llu\n

Uploading linux-2.6 to unstable

[Ben Hutchings]

I intend to upload linux-2.6 including the changes from 2.6.32.3 once
that's released (probably in the next 2 days).  This includes fixes for
the build failures in vserver on ia64 and s390.  Let me know if you have
any objections or other changes that I should wait for.

Ben.

-- 
Ben Hutchings
Horngren's Observation:
   Among economists, the real world is often a special case.


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

Processed: bug 563693 is forwarded to http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=1947

[Debian Bug Tracking System]

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

> forwarded 563693 http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=1947
Bug #563693 [linux-2.6] linux-image-2.6.32-trunk-amd64: iwl3945 chokes at 
currently packaged firmware. Makes adapter keep restarting
Set Bug forwarded-to-address to 
'http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=1947'.
>
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

Processed: reassign 563868 to linux-2.6, reassign 563870 to linux-2.6, merging 563868 563870

[Debian Bug Tracking System]

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

> reassign 563868 linux-2.6 2.6.30-8squeeze1
Bug #563868 [linux-image-2.6-686] [linux-image-2.6-686] only 2 hotkey on 4 
configurable on eeepc 901
Bug reassigned from package 'linux-image-2.6-686' to 'linux-2.6'.
Bug No longer marked as found in versions linux-latest-2.6/21.
Bug #563868 [linux-2.6] [linux-image-2.6-686] only 2 hotkey on 4 configurable 
on eeepc 901
There is no source info for the package 'linux-2.6' at version 
'2.6.30-8squeeze1' with architecture ''
Unable to make a source version for version '2.6.30-8squeeze1'
Bug Marked as found in versions 2.6.30-8squeeze1.
> reassign 563870 linux-2.6 2.6.30-8squeeze1
Bug #563870 [linux-image-2.6-686] [linux-image-2.6-2-686] only 2 hotkey on 4 
configurable on eeepc 901
Bug reassigned from package 'linux-image-2.6-686' to 'linux-2.6'.
Bug No longer marked as found in versions linux-latest-2.6/21.
Bug #563870 [linux-2.6] [linux-image-2.6-2-686] only 2 hotkey on 4 configurable 
on eeepc 901
There is no source info for the package 'linux-2.6' at version 
'2.6.30-8squeeze1' with architecture ''
Unable to make a source version for version '2.6.30-8squeeze1'
Bug Marked as found in versions 2.6.30-8squeeze1.
> merge 563868 563870
Bug#563868: [linux-image-2.6-686] only 2 hotkey on 4 configurable on eeepc 901
Bug#563870: [linux-image-2.6-2-686] only 2 hotkey on 4 configurable on eeepc 901
Merged 563868 563870.

>
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

Bug#563870: [linux-image-2.6-2-686] only 2 hotkey on 4 configurable on eeepc 901

[Rémi Bemol]

Package: linux-image-2.6-686
Version: 2.6.30+21
Severity: normal

--- Please enter the report below this line. ---

on the eeepc 901 there is 4 hotkeys on the top left on the keyboard.
We will call them 0, 1, 2, 3


If you go to keyboard shortcut you can easily configure the touch 2 and
3 if you click on a short cut and press the hotkey 2, you will see
write "XF86Launch3" but if you want to use it, some time is working,
some time is not working, Some time you configured it and it's working
but after when you change it, you still have the old who working...

but if you press on the hotkey number 1 nothing happening.
if you press on the hotkey number 0 it's working, but it's lock the
screen. after you can see that it's have work and it's write
"XF86ScreenSaver"


Well.

I expect to be able to configure all my hotkeys
I don't want that the hotkey1 be the screen saver. I don't want
screensaver, I want to user this hotkey for instance for run my
internet browser.

I'm not sure that it's in linux package, but I removed and purge
the package "eeepc-acpi-scripts" then I suppose that is not in it.



--- System information. ---
Architecture: i386
Kernel:   Linux 2.6.30-2-686

Debian Release: squeeze/sid
  500 testing security.debian.org 
  500 testing ftp.fr.debian.org 
  500 karmic  ppa.launchpad.net 

--- Package information. ---
Depends   (Version) | Installed
===-+-===
linux-image-2.6.30-2-686| 2.6.30-8squeeze1


Package's Recommends field is empty.

Package's Suggests field is empty.









-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#563868: [linux-image-2.6-686] only 2 hotkey on 4 configurable on eeepc 901

[Rémi Bemol]

Package: linux-image-2.6-686
Version: 2.6.30+21
Severity: normal

--- Please enter the report below this line. ---

on the eeepc 901 there is 4 hotkeys on the top left on the keyboard.
We will call them 0, 1, 2, 3


If you go to keyboard shortcut you can easily configure the touch 2 and
3 if you click on a short cut and press the hotkey 2, you will see
write "XF86Launch3" but if you want to use it, some time is working,
some time is not working, Some time you configured it and it's working
but after when you change it, you still have the old who working...

but if you press on the hotkey number 1 nothing happening.
if you press on the hotkey number 0 it's working, but it's lock the
screen. after you can see that it's have work and it's write
"XF86ScreenSaver"


Well.

I expect to be able to configure all my hotkeys
I don't want that the hotkey1 be the screen saver. I don't want
screensaver, I want to user this hotkey for instance for run my
internet browser.

I'm not sure that it's in linux package, but I removed and purge
the package "eeepc-acpi-scripts" then I suppose that is not in it.



--- System information. ---
Architecture: i386
Kernel:   Linux 2.6.30-2-686

Debian Release: squeeze/sid
  500 testing security.debian.org 
  500 testing ftp.fr.debian.org 
  500 karmic  ppa.launchpad.net 

--- Package information. ---
Depends   (Version) | Installed
===-+-===
linux-image-2.6.30-2-686| 2.6.30-8squeeze1


Package's Recommends field is empty.

Package's Suggests field is empty.








-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: severity of 563693 is important

[Debian Bug Tracking System]

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

> severity 563693 important
Bug #563693 [linux-2.6] linux-image-2.6.32-trunk-amd64: iwl3945 chokes at 
currently packaged firmware. Makes adapter keep restarting
Severity set to 'important' from 'grave'

>
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

Re: Nouveau kernel driver

[Ben Hutchings]

On Tue, 2010-01-05 at 22:15 +, Chris Lamb wrote:
> Ben Hutchings wrote:
> 
> > I'd like to pull nouveau from 2.6.33 into Debian's 2.6.32.  I'm hoping
> > this would allow for replacement of nv and its dodgy source with nouveau
> 
> This sounds like a good idea, but I should probably point out that I don't
> think we will be able to replace nv in squeeze with nouveau.

Why not?  Does it not support all the same hardware as nv, or is it
still too unstable?

> Would this this affect whether you want to spend time on it now? As you
> imply, we get this "for free" by waiting for .33, and I will have to get
> some -snapshot packages into testing anyway..

squeeze will be released with 2.6.32.  The release of .33 will be too
close to the freeze date.

Ben.

-- 
Ben Hutchings
Horngren's Observation:
   Among economists, the real world is often a special case.


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

Re: Nouveau kernel driver

[Chris Lamb]

Ben Hutchings wrote:

> I'd like to pull nouveau from 2.6.33 into Debian's 2.6.32.  I'm hoping
> this would allow for replacement of nv and its dodgy source with nouveau

This sounds like a good idea, but I should probably point out that I don't
think we will be able to replace nv in squeeze with nouveau.

Would this this affect whether you want to spend time on it now? As you
imply, we get this "for free" by waiting for .33, and I will have to get
some -snapshot packages into testing anyway..


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org
   `-


signature.asc
Description: PGP signature

Bug#563852: thinkpad_acpi: LED restriction does not add safety, please enable CONFIG_THINKPAD_ACPI_UNSAFE_LEDS

[Lars Stoltenow]

Package: linux-2.6
Severity: normal


The kernel guys decided it would be a good idea to cripple thinkpad_acpi by
not allowing the state of some hardware LEDs to be set, like the dock and
battery. They say that allowing these LEDs to be set can make users perform
actions dangerous to the hardware because firmware information might get lost.

I think that this change does not add safety at all, because the "unaware"
user which they reference in the docs doesn't play around with the LEDs anyway.
The LED devices are root writable only anyway, so evil guy wanting to destroy
other people's laptop could just load a fixed kernel module to control the
LEDs. The option is just a PITA for people that want to control the LEDs for
their own purposes, because they have to rebuild kernel modules. (No it's not
even a module load option like with the fan control switch, even though doing
funny things with the fan can cause much more damage to the hardware than
doing things to the LED.)

So there is no advantage in restricting access to the LEDs and therefore I'd
be thankful if future versions of the Debian kernel were built with
CONFIG_THINKPAD_ACPI_UNSAFE_LEDS enabled.

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

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



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#563847: Please enable the f-trace tracers

[Troy Heber]

Source: linux-2.6
Version: 2.6.32-3
Severity: wishlist

Currently Ftrace is enabled in the kernel, CONFIG_FTRACE=y and
CONFIG_DYNAMIC_FTRACE=y. However, some the most useful tracers, such
as CONFIG_FUNCTION_TRACER and CONFIG_STACK_TRACER, are disabled. For
example:

CONFIG_FTRACE=y
# CONFIG_FUNCTION_TRACER is not set
# CONFIG_IRQSOFF_TRACER is not set
# CONFIG_SYSPROF_TRACER is not set
# CONFIG_SCHED_TRACER is not set
# CONFIG_FTRACE_SYSCALLS is not set
...
# CONFIG_POWER_TRACER is not set
# CONFIG_STACK_TRACER is not set

Since Dynamic Ftrace is already enabled, I can't think of down side to
enabling the actual tracers. Please consider this a wishlist request
to enabled them.

Thanks,

Troy



signature.asc
Description: Digital signature

Bug#558237: linux-source-2.6.32: X with xserver-xorg-video-intel does not work any longer

[Emanuele Aina]

I have the same problem reported by Ludovico and, as noted in the
upstream bug report already pointed out by Reinhard [1], reducing the
amount of ram from 4G to something smaller (e.g. 3.5G) with the
mem=3500M kernel boot parameter causes the bug to disappear and can be
used as a temporary workaround.

[1] http://bugs.freedesktop.org/show_bug.cgi?id=25510








-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#563702: marked as done (linux-image-2.6.26-2-openvz-686: partition size truncate randomly (mdadm-raid1/lvm2))

[Debian Bug Tracking System]

Your message dated Tue, 5 Jan 2010 16:37:43 +0100
with message-id <20100105153742.gd6...@stro.at>
and subject line Re: Bug#563702: linux-image-2.6.26-2-openvz-686: partition 
size truncate randomly (mdadm-raid1/lvm2)
has caused the Debian Bug report #563702,
regarding linux-image-2.6.26-2-openvz-686: partition size truncate randomly 
(mdadm-raid1/lvm2)
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.)


-- 
563702: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563702
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.26-2-openvz-686
Version: 2.6.26-19lenny2
Severity: critical
Justification: causes serious data loss

[hope my translation was good]

sda1 boot scsi (sdb1 if sda fail) is/   1.9Go
md0 [sda3/sdc3] : raid1 linux (mdadm) & lvm /usr, /var  9Go
md1 [sdd1/sde1] : raid1   & lvm /var/www, /vz, ...  250Go

lvm on md1
/var/www 20Go in reality, but :

# df -h | grep www
/dev/mapper/satavol1-lvm--www
  1,9G  1,2G  626M  65% /mnt/satavol1/lvm-www

It's critical, there's nothing in syslog to explain, and some directory in 
/mnt/satavol1/lvm-www
aren't accessible until umount/mount !!
# umount /mnt/satavol1/lvm-www
umount: /dev/mapper/satavol1-lvm--www: not mounted
umount: /dev/mapper/satavol1-lvm--www: not mounted
#  mount /mnt/satavol1/lvm-www
# df -h | grep www
/dev/mapper/satavol1-lvm--www
   20G  8,7G   12G  44% /mnt/satavol1/lvm-www






since June 2009, df -h report 4 times 1.9G for my lv partition (note that 1.9 
is the size of my sda1 
partition instead more (40Go for example)

-- Package-specific info:
** Version:
Linux version 2.6.26-2-openvz-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 
22:06:32 UTC 2009

** Command line:
root=/dev/sda1 ro quiet vga=773

** Not tainted

** Kernel log:
[   27.508319] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[   27.557229] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[   27.753647] Linux agpgart interface v0.103
[   27.789506] parport_pc: VIA 686A/8231 detected
[   27.789519] parport_pc: probing current configuration
[   27.789545] parport_pc: Current parallel port base: 0x0
[   27.789555] parport_pc: VIA parallel port disabled in BIOS
[   27.810101] agpgart: Detected VIA Twister-K/KT133x/KM133 chipset
[   27.816692] agpgart: AGP aperture is 64M @ 0xe000
[   28.821295] input: Power Button (FF) as /class/input/input1
[   28.855381] ACPI: Power Button (FF) [PWRF]
[   28.85] input: Power Button (CM) as /class/input/input2
[   28.880288] ACPI: Power Button (CM) [PWRB]
[   28.880470] input: Sleep Button (CM) as /class/input/input3
[   28.915944] ACPI: Sleep Button (CM) [SLPB]
[   29.093211] input: PC Speaker as /class/input/input4
[   29.284272] ACPI: PCI Interrupt :00:07.5[C] -> Link [LNKD] -> GSI 15 
(level, low) -> IRQ 15
[   29.284439] PCI: Setting latency timer of device :00:07.5 to 64
[   29.889735] input: ImPS/2 Generic Wheel Mouse as /class/input/input5
[   31.905295] Adding 489972k swap on /dev/sda2.  Priority:-1 extents:1 
across:489972k
[   31.929984] Adding 489972k swap on /dev/sdb2.  Priority:-2 extents:1 
across:489972k
[   32.089661] EXT3 FS on sda1, internal journal
[   32.720016] loop: module loaded
[   32.845080] md: faulty personality registered for level -5
[   33.036467] md: bind
[   33.138892] raid1: raid set md1 active with 1 out of 2 mirrors
[   56.544042] ReiserFS: dm-10: found reiserfs format "3.6" with standard 
journal
[   56.544042] ReiserFS: dm-10: using ordered data mode
[   56.544042] ReiserFS: dm-10: journal params: device dm-10, size 8192, 
journal first block 18, max trans len 1024, max batch 900, max commit age 30, 
max trans age 30
[   56.562380] ReiserFS: dm-10: checking transaction log (dm-10)
[   56.584048] ReiserFS: dm-10: Using r5 hash to sort names
[   56.584048] kjournald starting.  Commit interval 5 seconds
[   56.685624] EXT3 FS on sdb1, internal journal
[   56.685637] EXT3-fs: mounted filesystem with ordered data mode.
[   56.709934] ReiserFS: dm-9: found reiserfs format "3.6" with standard journal
[   56.709981] ReiserFS: dm-9: using ordered data mode
[   56.714787] ReiserFS: dm-9: journal params: device dm-9, size 8192, journal 
first block 18, max trans len 1024, max batch 900, max commit age 30, max trans 
age 30
[   56.719487] ReiserFS: dm-9: checking transaction log (dm-9)
[   56.760840] ReiserFS: dm-9: Using r5 hash to sort names
[   56.808483] ReiserFS: d

Processed: Re: Bug#549185: libftdi1: ftdi_sio disconnects FT232RL after bitbanging

[Debian Bug Tracking System]

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

> reassign 549185 linux-2.6
Bug #549185 [libftdi1] libftdi1: ftdi_sio disconnects FT232RL after bitbanging
Bug reassigned from package 'libftdi1' to 'linux-2.6'.
Bug No longer marked as found in versions libftdi/0.13-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

Bug#563607: linux-source-2.6.30: Will not boot past the beginning of the GUI in Xwindow -- Window manager dies

[maximilian attems]

[ please keep bug report on cc, thanks ]

On Mon, Jan 04, 2010 at 03:03:01PM -0800, Willy Gommel wrote:
>
> actually, no. Part of the reason is that I didn't know that 2.6.32 was 
> available; another part of the reason is that, even knowing that it is 
> available, I don't know how to get access to it as you identified it. In 
> aptitude, I can find no more of the file name you gave than "linux-
> source-2.6.32" there. OTOH, I wonder whether you're talking about a pre-
> compiled image. If so, why? Actually, the precompiled image for 2.6.30 does 
> indeed work on my AMD-64 machine. That's why I specified "try to boot from my 
> own recompilation of the 2.6.30-8 kernel."
> 
> At any rate, my compilation of 2.6.32 hangs up identically to 2.6.30.

the 2.6.32 upload is in unstable, hasn't migrated to testing yet
and will take some time to do so, but just installs fine in testing.
you need to add an unstable deb apt line and then install the image
and then you can remove that line again.
 
> Thank you very much for your prompt reply!

you are more then welcome,
hope aboves helps? :)



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#504805: Boom

[Tom Laermans]

[57049.874985] iret exception:  [#1] SMP
[57049.875210] Modules linked in: xt_physdev iptable_filter ip_tables 
x_tables inet_diag ipv6 bridge ext3 jbd mbcache drbd cn loop evdev 
parport_pc parport i2c_i801 i2c_core pcspkr rng_core button intel_agp 
agpgart shpchp pci_hotplug i82875p_edac edac_core xfs dm_mirror dm_log 
dm_snapshot dm_mod raid1 md_mod sd_mod ide_cd_mod cdrom ata_piix 
ata_generic libata scsi_mod dock piix floppy e1000 ide_pci_generic 
ide_core ehci_hcd uhci_hcd usbcore thermal processor fan thermal_sys 
[last unloaded: scsi_wait_scan]

[57049.877978]
[57049.877978] Pid: 4564, comm: blkback.2.sda Not tainted 
(2.6.26-2-xen-686 #1)

[57049.877978] EIP: 0061:[] EFLAGS: 0002 CPU: 0
[57049.877978] EIP is at ioread8+0x16/0x2a
[57049.877978] EAX: 0001c850 EBX: 03e8 ECX: 010c2000 EDX: c807
[57049.877978] ESI: ce280028 EDI: ce28 EBP: ce28 ESP: cd1f5b70
[57049.877978]  DS: 007b ES: 007b FS: 00d8 GS:  SS: 0069
[57049.877978] Process blkback.2.sda (pid: 4564, ti=cd1f4000 
task=cd2a5b00 task.ti=cd1f4000)
[57049.877978] Stack: d115a26f d115bcc5 0016  ce280078 
ce28 ce281404 d115ba67
[57049.877978] ce280078 ce28 d114fe26 ce280078 
cef6f180 ce281528 d10dd426
[57049.877978]d11542da ce28 cef6f180 ce281528 d10dd426 
ce28 d1156501 d1154024

[57049.877978] Call Trace:
[57049.881623]  [] ata_sff_check_status+0x8/0xc [libata]
[57049.881623]  [] ata_sff_tf_load+0xe4/0x137 [libata]
[57049.881623]  [] ata_sff_qc_issue+0xbf/0x1d8 [libata]
[57049.881623]  [] ata_qc_issue+0x161/0x1b6 [libata]
[57049.881623]  [] scsi_done+0x0/0x16 [scsi_mod]
[57049.881623]  [] ata_scsi_translate+0xd2/0xf7 [libata]
[57049.881623]  [] scsi_done+0x0/0x16 [scsi_mod]
[57049.881623]  [] ata_scsi_queuecmd+0x1c7/0x1df [libata]
[57049.881623]  [] ata_scsi_rw_xlat+0x0/0x1c1 [libata]
[57049.881623]  [] scsi_dispatch_cmd+0x18b/0x205 [scsi_mod]
[57049.881623]  [] scsi_request_fn+0x29d/0x3af [scsi_mod]
[57049.881623]  [] __generic_unplug_device+0x1a/0x1c
[57049.881623]  [] elv_insert+0x102/0x196
[57049.885625]  [] __make_request+0x2fe/0x36e
[57049.885625]  [] generic_make_request+0x34d/0x37b
[57049.885625]  [] evtchn_do_upcall+0xfa/0x191
[57049.885625]  [] mempool_alloc+0x1c/0xba
[57049.885625]  [] submit_bio+0xc6/0xcd
[57049.885625]  [] bio_add_page+0x25/0x2c
[57049.885625]  [] dispatch_rw_block_io+0x4c5/0x55d
[57049.885625]  [] local_clock+0x2d/0x6f
[57049.885625]  [] get_nsec_offset+0xe/0x6a
[57049.885625]  [] __switch_to+0x376/0x42e
[57049.885625]  [] get_nsec_offset+0xe/0x6a
[57049.885625]  [] get_runstate_snapshot+0x69/0xec
[57049.885625]  [] get_nsec_offset+0xe/0x6a
[57049.885625]  [] get_runstate_snapshot+0x69/0xec
[57049.885625]  [] update_curr+0x47/0x79
[57049.885625]  [] __dequeue_entity+0x1f/0x71
[57049.885625]  [] schedule+0x631/0x6b1
[57049.889626]  [] md_wakeup_thread+0x1e/0x20 [md_mod]
[57049.889626]  [] blkif_schedule+0x39d/0x4b6
[57049.889626]  [] blkif_schedule+0x0/0x4b6
[57049.889626]  [] kthread+0x38/0x5f
[57049.889626]  [] kthread+0x0/0x5f
[57049.889626]  [] kernel_thread_helper+0x7/0x10
[57049.889626]  ===
[57049.889626] Code: c0 81 e2 ff ff 00 00 ee c3 ba 8b a4 32 c0 89 c8 e9 
f3 fd ff ff 3d ff ff 03 00 76 04 8a 00 eb 0b 3d 00 00 01 00 76 08 0f b7 
d0 ec <0f> b6 c0 c3 ba 9a a4 32 c0 e8 cf fd ff ff b8 ff 00 00 00 c3 3d

[57049.893632] EIP: [] ioread8+0x16/0x2a SS:ESP 0069:cd1f5b70
[57049.907810] ---[ end trace 40d498c3636b9d0c ]---

Is there actually any point in sending this, or will it just be ignored...




--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org