Bug#675302: nouveau: hard lockup when gdm3 starts
Hi, Gedalya wrote: Tried removing the nvidia stuff and booting up with nouveau. [...] Total system hang as soon as xorg starts. No response from keyboard, mouse, no response on the network (no ping, no ARP response) [...] Using an Nvidia GeForce GT 520. Do I understand correctly that the system works fine until X starts (e.g., if you use the text kernel command line option)? Does X with the fbdev driver work? (You can test by putting the following in /etc/X11/xorg.conf.) Section Device Identifier geforce Driver fbdev EndSection Does starting X with the nouveau driver work if you do not start a GNOME session? (You can test by running startx xterm if the xinit package is installed.) Thanks for a clear report. Hope that helps, Jonathan -- 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/20120531055946.GC1447@burratino
Bug#628444: Also in stable, now
Hi all I'm running stable (squeeze), with the standard 2.6.32-5 kernel, on a Lenovo Thinkpad X200 tablet; lspci says 03:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300 and the module is iwlagn, obviously. The machine has been running squeeze since it was released without any problems. But in the last few days, I have started having very frequent problems along the lines described. May 31 06:12:32 rigel kernel: [ 1029.842353] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready May 31 06:12:41 rigel kernel: [ 1038.685375] iwlagn :03:00.0: iwl_tx_agg_start on ra = a0:21:b7:4d:3d:9c tid = 0 May 31 06:14:43 rigel kernel: [ 1161.316130] No probe response from AP a0:21:b7:4d:3d:9c after 500ms, disconnecting. May 31 06:14:43 rigel kernel: [ 1161.320094] iwlagn :03:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0x May 31 06:14:43 rigel kernel: [ 1161.320094] iwlagn :03:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0x [...] At this point rmmod/modprobe do nothing at all, and the only solution is a reboot. This particular one was on wakeup, but frequently it's in the middle of normal use. Nothing's changed with the hardware: I did have the keyboard off a few weeks ago to remove a stuck stylus, but I don't think the timing is quite right to suggest I unseated the card at that point; also, the machine dual-boots into Windows, and I see no problems there, though I use it much less. However, I do keep the system updated, and I seem to recall that there was a new kernel *and firmware* version a little while ago as part of the 6.0.5 release. That was on May 12, and my problems started, according to the logs, after a reboot on May 14! I post this in the hope that someone might have some insight as a result of knowing what's changed in the latest stable release. In the meantime, I am going to try some of the workrounds described in this thread. Cheers Martin -- 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/CANGLxoas6uG26JCz9UaAKkUauNbQBVmfA6q0SE=xqe9l+ga...@mail.gmail.com
Bug#675302: nouveau: hard lockup when gdm3 starts
Gedalya wrote: On 5/31/2012 1:59 AM, Jonathan Nieder wrote: Does starting X with the nouveau driver work if you do not start a GNOME session? (You can test by running startx xterm if the xinit package is installed.) Interesting. Still working on this one. startx was complaining something about xorg.conf so I just renamed it, and then it started up. Pretty frozen at this point, no keyboard, only reset button helps, but I do get network response - there is ping, initial ssh response but nothing more, can't actually log in. Hm. Might be possible to get a log with netconsole[1]. [1] http://www.kernel.org/doc/Documentation/networking/netconsole.txt http://blog.mraw.org/2010/11/08/Debugging_using_netconsole/ -- 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/20120531063143.GD1447@burratino
Bug#675302: nouveau: hard lockup when gdm3 starts
On 5/31/2012 2:31 AM, Jonathan Nieder wrote: Gedalya wrote: On 5/31/2012 1:59 AM, Jonathan Nieder wrote: Does starting X with the nouveau driver work if you do not start a GNOME session? (You can test by running startx xterm if the xinit package is installed.) Interesting. Still working on this one. startx was complaining something about xorg.conf so I just renamed it, and then it started up. Pretty frozen at this point, no keyboard, only reset button helps, but I do get network response - there is ping, initial ssh response but nothing more, can't actually log in. Hm. Might be possible to get a log with netconsole[1]. [1] http://www.kernel.org/doc/Documentation/networking/netconsole.txt http://blog.mraw.org/2010/11/08/Debugging_using_netconsole/ Tried this again and this time I got a total hang again. Then I got it to work with the config file so I first tried fbdev and it worked, then when I switched to nouveau I got again this situation that it's pretty much hung but with ping. SSH does respond with failed authentication when it's the wrong password, but no successful login is possible. I'm gonna study netconsole now, let's see if I can figure it out. -- 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/4fc7117d.9040...@gedalya.net
Bug#675302: nouveau: hard lockup when gdm3 starts
On 5/31/2012 1:59 AM, Jonathan Nieder wrote: Hi, Gedalya wrote: Tried removing the nvidia stuff and booting up with nouveau. [...] Total system hang as soon as xorg starts. No response from keyboard, mouse, no response on the network (no ping, no ARP response) [...] Using an Nvidia GeForce GT 520. Do I understand correctly that the system works fine until X starts (e.g., if you use the text kernel command line option)? Yes. As long as X doesn't start it seems rock solid. Does X with the fbdev driver work? (You can test by putting the following in /etc/X11/xorg.conf.) Section Device Identifier geforce Driver fbdev EndSection Yes. This does work. BTW driver vesa hangs the same. Does starting X with the nouveau driver work if you do not start a GNOME session? (You can test by running startx xterm if the xinit package is installed.) Interesting. Still working on this one. startx was complaining something about xorg.conf so I just renamed it, and then it started up. Pretty frozen at this point, no keyboard, only reset button helps, but I do get network response - there is ping, initial ssh response but nothing more, can't actually log in. Thanks for a clear report. Hope that helps, Jonathan -- 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/4fc70ec3.7040...@gedalya.net
Processed: forcibly merging 675190 658325
Processing commands for cont...@bugs.debian.org: forcemerge 675190 658325 Bug #675190 [linux-2.6] BUG: unable to handle kernel paging request at 27c97000 during reboot under xen Bug #658325 [linux-2.6] linux-2.6: Kernel crash when Xen hot-unplug network device Severity set to 'minor' from 'important' There is no source info for the package 'linux-2.6' at version '3.2.1-2~bpo60+1' with architecture '' Unable to make a source version for version '3.2.1-2~bpo60+1' There is no source info for the package 'linux-2.6' at version '3.2.18-1' with architecture '' Unable to make a source version for version '3.2.18-1' Marked as found in versions 3.2.18-1. Added tag(s) moreinfo. Bug #675190 [linux-2.6] BUG: unable to handle kernel paging request at 27c97000 during reboot under xen There is no source info for the package 'linux-2.6' at version '3.2.1-2~bpo60+1' with architecture '' Unable to make a source version for version '3.2.1-2~bpo60+1' There is no source info for the package 'linux-2.6' at version '3.2.18-1' with architecture '' Unable to make a source version for version '3.2.18-1' Marked as found in versions 3.2.1-2~bpo60+1. Merged 658325 675190 thanks Stopping processing here. Please contact me if you need assistance. -- 658325: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658325 675190: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675190 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.133844998413524.transcr...@bugs.debian.org
Bug#675093: linux-image-3.2.0-2-amd64: USB timeout initializing reports with Eaton UPS
On Thu, 31 May 2012, Ben Hutchings wrote:
Package: linux-2.6
Version: 3.2.18-1
Severity: normal
It would seem that the kernel is doing something wrong when trying to
initalise an USB connection to an Eaton (formerly Merlin Gerin) Ellipse
Max UPS.
When the box is booting, the device's initialisation adds a ~15s delay,
then some USB error is reported (at timestamp 18.319789 in the kernel
log below).
Strangely enough, the device appears to work after that.
I am reporting this error for the kernel on this computer (which is a
x86-64 and includes various tainted modules), however it also occurs on
a much older x86 box running a Debian Squeeze with
linux-image-2.6.32-5-686 (no proprietary drivers loaded, either). The
device connected to that box is a different model of Eaton Ellipse Max
UPS. Both UPS's are brand new.
[...]
[5.167483] usb 2-2.4: New USB device found, idVendor=0463,
idProduct=
[5.167488] usb 2-2.4: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[5.167491] usb 2-2.4: Product: Ellipse MAX
[5.167493] usb 2-2.4: Manufacturer: EATON
[5.167496] usb 2-2.4: SerialNumber: ADKM25014
[5.208346] usb 2-1.2: reset high-speed USB device number 6 using
ehci_hcd
[5.384134] usb 2-1.2: reset high-speed USB device number 6 using
ehci_hcd
[5.560072] usb 2-1.2: reset high-speed USB device number 6 using
ehci_hcd
[5.736015] usb 2-1.2: reset high-speed USB device number 6 using
ehci_hcd
[5.869976] PM: Starting manual resume from disk
[5.869979] PM: Hibernation image partition 254:1 present
[5.869980] PM: Looking for hibernation image.
[5.870175] PM: Image not found (code -22)
[5.870178] PM: Hibernation image not present or could not be loaded.
[5.910554] EXT4-fs (dm-0): mounted filesystem with ordered data
mode. Opts: (null)
[ 18.319789] generic-usb 0003:0463:.0003: usb_submit_urb(ctrl) failed
[ 18.319850] generic-usb 0003:0463:.0003: timeout initializing reports
[ 18.320070] generic-usb 0003:0463:.0003: hiddev0,hidraw2: USB HID
Hmm, that's odd. This device has been on 'HID_QUIRK_NOGET' list for very
long time already (even before 2.6.32). Could you please apply the patch
below, modprobe hid module with 'debug=1' parameter, and send me the
output?
diff --git a/drivers/hid/usbhid/hid-core.c b/drivers/hid/usbhid/hid-core.c
index 482f936..25ebf54 100644
--- a/drivers/hid/usbhid/hid-core.c
+++ b/drivers/hid/usbhid/hid-core.c
@@ -397,6 +397,7 @@ static int hid_submit_ctrl(struct hid_device *hid)
r = usb_submit_urb(usbhid-urbctrl, GFP_ATOMIC);
if (r 0) {
hid_err(hid, usb_submit_urb(ctrl) failed: %d\n, r);
+ dump_stack();
return r;
}
usbhid-last_ctrl = jiffies;
--
Jiri Kosina
SUSE Labs
--
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/alpine.lnx.2.00.1205310950310.15...@pobox.suse.cz
Bug#675093: linux-image-3.2.0-2-amd64: USB timeout initializing reports with Eaton UPS
On 31/05/12 09:52, Jiri Kosina wrote:
Hmm, that's odd. This device has been on 'HID_QUIRK_NOGET' list for very
long time already (even before 2.6.32). Could you please apply the patch
below, modprobe hid module with 'debug=1' parameter, and send me the
output?
diff --git a/drivers/hid/usbhid/hid-core.c b/drivers/hid/usbhid/hid-core.c
index 482f936..25ebf54 100644
--- a/drivers/hid/usbhid/hid-core.c
+++ b/drivers/hid/usbhid/hid-core.c
@@ -397,6 +397,7 @@ static int hid_submit_ctrl(struct hid_device *hid)
r = usb_submit_urb(usbhid-urbctrl, GFP_ATOMIC);
if (r 0) {
hid_err(hid, usb_submit_urb(ctrl) failed: %d\n, r);
+ dump_stack();
return r;
}
usbhid-last_ctrl = jiffies;
This patch could not be applied to the Debian kernel source, somehow. I
have assumed the code I should modify is this:
if (usb_submit_urb(usbhid-urbctrl, GFP_ATOMIC)) {
usb_autopm_put_interface_async(usbhid-intf);
hid_err(hid, usb_submit_urb(ctrl) failed\n);
return -1;
}
(line 382 of drivers/hid/usbhid/hid-core.c) instead of what the patch
originally modifies.
Kernel is being compiled at the moment. Sorry for taking so long, it's
been a while since I had to do that.
--
Manu Benoît
--
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/4fc73091.2080...@nocternity.net
Bug#674411: linux-image-2.6.32-5-xen-686: Kernel crashes if AIO is used on pages belonging to guests
On Wed, 30 May 2012, Ian Campbell wrote:
On Thu, 2012-05-24 at 11:57 +, George Dunlap wrote:
Package: linux-2.6
Version: 2.6.32-45
Severity: normal
The kernel version in this package does not handle AIO to pages
owned by guest domains (foreign domains) properly. Newer versions of qemu
will attempt to use AIO for disk reads and writes; this causes domain 0 to
crash
if you're running.
Thanks George. Do you happen to have a log of the actual kernel crash?
I think Stefano (CCd) has been fixing this issue (or at least one which
sounds very similar) in the upstream kernels recently. Stefano is there
anything specific I can backport to a Jeremy xen.git 2.6.32 style pvops
kernel? Or is there another appropriate fix?
FYI Squeeze's kernel is based on e73f4955a821 from Jeremy's tree,
although with a bunch of fixes backported too.
We need to backport the m2p_override, this is a list of the relevant
upstream commits:
289b777eac19c811b474593b4d2fd14e46340c23
b5eafe924bb054d7c56e6ebd18106352e8a3f916
448f2831934381e9d3c4d93e700ba7bbe14612dc
9b705f0e98c489b18ba22a6eab9d694b546c8552
87f1d40a706bdebdc8f959b9ac291d0d8fdfcc7e
e1b478e4ec4477520767d1a920433626263a2a6b
b254244d2682fe975630f176c25acc4e088d
cf8d91633ddef9e816ccbf3da833c79ce508988d
0f4b49eaf25e661fbe63a5370b7781166b34d616
0930bba674e248b921ea659b036ff02564e5a5f4
dc4972a4e2f3fee1663bd0670dfc4cd798d5f9b2
The backport is non-trivial, but I can help.
As an alternative we could add a simple check to spot an attempt to use
AIO on a granted page and return an error (still better than crashing):
---
diff --git a/drivers/xen/gntdev.c b/drivers/xen/gntdev.c
index a33e443..f060770 100644
--- a/drivers/xen/gntdev.c
+++ b/drivers/xen/gntdev.c
@@ -573,6 +573,7 @@ static int gntdev_mmap(struct file *flip, struct
vm_area_struct *vma)
vma-vm_flags |= VM_RESERVED;
vma-vm_flags |= VM_DONTCOPY;
vma-vm_flags |= VM_DONTEXPAND;
+ vma-vm_flags |= VM_FOREIGN;
vma-vm_private_data = map;
map-vma = vma;
diff --git a/fs/aio.c b/fs/aio.c
index 02a2c93..70b8854 100644
--- a/fs/aio.c
+++ b/fs/aio.c
@@ -1655,6 +1655,8 @@ SYSCALL_DEFINE3(io_submit, aio_context_t, ctx_id, long,
nr,
for (i=0; inr; i++) {
struct iocb __user *user_iocb;
struct iocb tmp;
+ struct vm_area_struct *vma = NULL;
+ struct iovec *v = NULL;
if (unlikely(__get_user(user_iocb, iocbpp + i))) {
ret = -EFAULT;
@@ -1666,6 +1668,19 @@ SYSCALL_DEFINE3(io_submit, aio_context_t, ctx_id, long,
nr,
break;
}
+ down_read(current-mm-mmap_sem);
+ v = (struct iovec *) tmp.aio_buf;
+ /* just checking the first iovec is enough for now */
+ if (v != NULL)
+ vma = find_vma(current-mm, (unsigned long)
v-iov_base);
+ if (vma != NULL vma-vm_flags (VM_FOREIGN|VM_DONTEXPAND)) {
+ WARN_ONCE(1, missing AIO support on granted pages\n);
+ ret = -EFAULT;
+ up_read(current-mm-mmap_sem);
+ break;
+ }
+ up_read(current-mm-mmap_sem);
+
ret = io_submit_one(ctx, user_iocb, tmp);
if (ret)
break;
--
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/alpine.DEB.2.00.1205311104510.26786@kaball-desktop
Bug#675093: linux-image-3.2.0-2-amd64: USB timeout initializing reports with Eaton UPS
Alright, got the log you requested. [1.66] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [1.633359] ehci_hcd :00:1a.7: PCI INT C - GSI 18 (level, low) - IRQ 18 [1.633377] ehci_hcd :00:1a.7: setting latency timer to 64 [1.633381] ehci_hcd :00:1a.7: EHCI Host Controller [1.633407] ehci_hcd :00:1a.7: new USB bus registered, assigned bus number 1 [1.633435] ehci_hcd :00:1a.7: debug port 1 [1.634669] sky2 :06:00.0: eth0: addr 00:26:18:46:3a:05 [1.634694] sky2 :04:00.0: PCI INT A - GSI 17 (level, low) - IRQ 17 [1.634704] sky2 :04:00.0: setting latency timer to 64 [1.634732] sky2 :04:00.0: Yukon-2 EC Ultra chip revision 3 [1.634828] sky2 :04:00.0: irq 69 for MSI/MSI-X [1.635926] sky2 :04:00.0: eth1: addr 00:26:18:46:3a:04 [1.637332] ehci_hcd :00:1a.7: cache line size of 64 is not supported [1.637797] ehci_hcd :00:1a.7: irq 18, io mem 0xf7fff000 [1.638237] SCSI subsystem initialized [1.643732] libata version 3.00 loaded. [1.643746] firewire_ohci :08:02.0: PCI INT A - GSI 18 (level, low) - IRQ 18 [1.645046] uhci_hcd: USB Universal Host Controller Interface driver [1.652474] ehci_hcd :00:1a.7: USB 2.0 started, EHCI 1.00 [1.652506] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [1.652509] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [1.652512] usb usb1: Product: EHCI Host Controller [1.652515] usb usb1: Manufacturer: Linux 3.2.0-2-amd64 ehci_hcd [1.652518] usb usb1: SerialNumber: :00:1a.7 [1.652734] hub 1-0:1.0: USB hub found [1.652739] hub 1-0:1.0: 6 ports detected [1.652841] ehci_hcd :00:1d.7: PCI INT A - GSI 23 (level, low) - IRQ 23 [1.653059] ehci_hcd :00:1d.7: setting latency timer to 64 [1.653063] ehci_hcd :00:1d.7: EHCI Host Controller [1.653071] ehci_hcd :00:1d.7: new USB bus registered, assigned bus number 2 [1.653094] ehci_hcd :00:1d.7: debug port 1 [1.653710] ahci :05:00.0: version 3.0 [1.654234] pata_marvell :05:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [1.654257] pata_marvell :05:00.0: setting latency timer to 64 [1.654560] scsi0 : pata_marvell [1.654695] scsi1 : pata_marvell [1.654737] ata1: PATA max UDMA/100 cmd 0xcc00 ctl 0xc880 bmdma 0xc400 irq 16 [1.654739] ata2: PATA max UDMA/133 cmd 0xc800 ctl 0xc480 bmdma 0xc408 irq 16 [1.656976] ehci_hcd :00:1d.7: cache line size of 64 is not supported [1.656988] ehci_hcd :00:1d.7: irq 23, io mem 0xf7ffe000 [1.672622] ehci_hcd :00:1d.7: USB 2.0 started, EHCI 1.00 [1.672645] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 [1.672647] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [1.672649] usb usb2: Product: EHCI Host Controller [1.672650] usb usb2: Manufacturer: Linux 3.2.0-2-amd64 ehci_hcd [1.672652] usb usb2: SerialNumber: :00:1d.7 [1.672794] hub 2-0:1.0: USB hub found [1.672799] hub 2-0:1.0: 6 ports detected [1.672941] ata_piix :00:1f.2: version 2.13 [1.672956] ata_piix :00:1f.2: PCI INT B - GSI 20 (level, low) - IRQ 20 [1.672960] ata_piix :00:1f.2: MAP [ P0 P2 P1 P3 ] [1.672989] ata_piix :00:1f.2: setting latency timer to 64 [1.673255] scsi2 : ata_piix [1.673379] scsi3 : ata_piix [1.674515] ata3: SATA max UDMA/133 cmd 0x8000 ctl 0x7c00 bmdma 0x7480 irq 20 [1.674519] ata4: SATA max UDMA/133 cmd 0x7880 ctl 0x7800 bmdma 0x7488 irq 20 [1.674600] ata_piix :00:1f.5: PCI INT B - GSI 20 (level, low) - IRQ 20 [1.674604] ata_piix :00:1f.5: MAP [ P0 -- P1 -- ] [1.674630] ata_piix :00:1f.5: setting latency timer to 64 [1.674855] scsi4 : ata_piix [1.674978] scsi5 : ata_piix [1.675947] ata5: SATA max UDMA/133 cmd 0x9000 ctl 0x8c00 bmdma 0x8480 irq 20 [1.675950] ata6: SATA max UDMA/133 cmd 0x8880 ctl 0x8800 bmdma 0x8488 irq 20 [1.676019] uhci_hcd :00:1a.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [1.676026] uhci_hcd :00:1a.0: setting latency timer to 64 [1.676028] uhci_hcd :00:1a.0: UHCI Host Controller [1.676036] uhci_hcd :00:1a.0: new USB bus registered, assigned bus number 3 [1.676060] uhci_hcd :00:1a.0: irq 16, io base 0x9800 [1.676116] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001 [1.676119] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [1.676120] usb usb3: Product: UHCI Host Controller [1.676122] usb usb3: Manufacturer: Linux 3.2.0-2-amd64 uhci_hcd [1.676123] usb usb3: SerialNumber: :00:1a.0 [1.676235] hub 3-0:1.0: USB hub found [1.676239] hub 3-0:1.0: 2 ports detected [1.676300] uhci_hcd :00:1a.1: PCI INT B - GSI 21 (level, low) - IRQ 21 [1.676306] uhci_hcd :00:1a.1: setting latency timer to 64 [1.676309] uhci_hcd :00:1a.1: UHCI Host Controller [
Bug#628444: Also in stable, now
On Thu, 2012-05-31 at 07:03 +0100, Martin Hardcastle wrote: [...] However, I do keep the system updated, and I seem to recall that there was a new kernel *and firmware* version a little while ago as part of the 6.0.5 release. [...] There was no change to any firmware or to this driver in the 6.0.5 release. Ben. -- Ben Hutchings The obvious mathematical breakthrough [to break modern encryption] would be development of an easy way to factor large prime numbers. - Bill Gates signature.asc Description: This is a digitally signed message part
Bug#661151: [apparmor] Bug#661151: linux-2.6: lacks AppArmor kernel/userspace interface
Hi, Ben Hutchings wrote (31 May 2012 03:24:09 GMT) : What about this one: commit 1023c7c2f9d9c5707147479104312c4c3d1a2c2b Author: John Johansen john.johan...@canonical.com Date: Wed Aug 10 22:02:39 2011 -0700 AppArmor: compatibility patch for v5 network controll Add compatibility for v5 network rules. That will provide support for the network rules and if you are willing to carry it that would be greate but is not strictly necessary. Policy can still be loaded and introspected. If that patch is missing and if profile contains network rules the parser will complain about them not being enforced, but it will still load and enforce the rest of the policy Looking back over the bug log, I see that wasn't requested, so I'm only applying 'AppArmor: compatibility patch for v5 interface' now. Thanks a lot for applying this patch! This will make our work on AppArmor in Wheezy much easier, and user experience much better. However, yes, perhaps it was unclear, but my initial bug report (shyly) talked of the compatibility patch to solve both network mediation does not work at all issue and the introspection ones, so it would be absolutely wonderful if you could apply the part of the compatibility patch that deals with network too (FTR, this would bring Wheezy on par with what Ubuntu shipped before Precise). Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/85pq9klcgq@boum.org
Bug#673391: Revised patches for be2net
Ben, I am attaching the remaining to patches: 68aad78 sweep the floors and convert some .get_drvinfo routines to strlcpy e5686ad netdev: make net_device_ops const Please apply them too. Thanks, Sarvesh -Original Message- From: Ben Hutchings [mailto:b...@decadent.org.uk] Sent: Sunday, May 27, 2012 5:27 AM To: Bandi,Sarveshwar; 673...@bugs.debian.org Subject: Re: Bug#673391: Revised patches for be2net On Fri, 2012-05-25 at 09:30 -0700, sarveshwar.ba...@emulex.com wrote: Ben, I am attaching the revised patches as per your comments. I was not sure how to handle patches (4 of them) which involved changes to other drivers too. I intend to open separate bugs for each of them and send them. Hope that is ok. No, there's no need to open more bugs. I have also taken care of your comment to not change the return value in ndo_vlan_rx_[add/kill]_vid (8e586137e6b63af1e881b328466ab5ffbe562510). The patches also contain the upstream commit id thanks to your git-format-patch-for-backport script. Thanks. So the remaining 4 changes are: 68aad78 sweep the floors and convert some .get_drvinfo routines to strlcpy e5686ad netdev: make net_device_ops const It's absolutely fine to apply just the parts of these that affect your driver, as in your original series. 8e58613 net: make vlan ndo_vlan_rx_[add/kill]_vid return error value This should not be applied at all, as we don't want to change the kernel API. 786f528 ethtool: Null-terminate filename passed to ethtool_ops::flash_device I think this is an important bug fix (well I would do :-) so I'll apply it and also propose to David Miller that it goes into stable updates. Ben. -- Ben Hutchings The obvious mathematical breakthrough [to break modern encryption] would be development of an easy way to factor large prime numbers. - Bill Gates 0001-sweep-the-floors-and-convert-some-.get_drvinfo-routi.patch Description: 0001-sweep-the-floors-and-convert-some-.get_drvinfo-routi.patch 0027-netdev-make-net_device_ops-const.patch Description: 0027-netdev-make-net_device_ops-const.patch
Processing of initramfs-tools_0.103_amd64.changes
initramfs-tools_0.103_amd64.changes uploaded successfully to localhost along with the files: initramfs-tools_0.103.dsc initramfs-tools_0.103.tar.gz initramfs-tools_0.103_all.deb Greetings, Your Debian queue daemon (running on host franck.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/e1sa5zf-0002qk...@franck.debian.org
initramfs-tools_0.103_amd64.changes ACCEPTED into unstable
Accepted: initramfs-tools_0.103.dsc to main/i/initramfs-tools/initramfs-tools_0.103.dsc initramfs-tools_0.103.tar.gz to main/i/initramfs-tools/initramfs-tools_0.103.tar.gz initramfs-tools_0.103_all.deb to main/i/initramfs-tools/initramfs-tools_0.103_all.deb Changes: initramfs-tools (0.103) unstable; urgency=low . * [3fd3568] configure_networking: Use /run path for ipconfig generated script. * [886abf0] debian/control: Depend on newer klibc-utils for /run path. Override entries for your package: initramfs-tools_0.103.dsc - source utils initramfs-tools_0.103_all.deb - optional utils 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/e1sa7dq-0004lk...@franck.debian.org
Bug#628444: Also in stable, now
On 31 May 2012 14:12, Ben Hutchings b...@decadent.org.uk wrote: There was no change to any firmware or to this driver in the 6.0.5 release. So what's your explanation for the problem appearing immediately after the 6.0.5 release was installed? Just coincidence? I'm not trying to make any point in particular, just curious. Anyway, as the problem is now present in stable as well, I hope someone can find a fix. It makes the machine pretty much unusable for its intended purpose. Cheers Martin -- 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/CANGLxob5bN7GS4ERPJDEg5yKwP_G893GTCQjWg=22blntkg...@mail.gmail.com
Bug#628444: Also in stable, now
On Thu, May 31, 2012 at 06:15:53PM +0100, Martin Hardcastle wrote: On 31 May 2012 14:12, Ben Hutchings b...@decadent.org.uk wrote: There was no change to any firmware or to this driver in the 6.0.5 release. So what's your explanation for the problem appearing immediately after the 6.0.5 release was installed? Just coincidence? I'm not trying to make any point in particular, just curious. You rebooted. Problems often show up after a reboot. Anyway, as the problem is now present in stable as well, I hope someone can find a fix. It makes the machine pretty much unusable for its intended purpose. I don't think it's been established that the problem you're seeing is the same as the one reported here. In general there is not a one-to-one mapping of error messages to bugs. Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- 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/20120531174208.gd20...@decadent.org.uk
Bug#628444: Also in stable, now
On 31 May 2012 18:42, Ben Hutchings b...@decadent.org.uk wrote: You rebooted. Problems often show up after a reboot. Yeah: just to provide some additional information, I had actually rebooted the machine on previous occasions since first installing stable without this problem showing up. I don't think it's been established that the problem you're seeing is the same as the one reported here. OK: what information would you suggest I try to obtain in order to establish that? Martin -- 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/canglxoz91c20b-urklpbkyeln8d+9vyrnbjrrdc1o2a5bps...@mail.gmail.com
Processed: [bts-link] source package linux-2.6
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #375092 (http://bugs.debian.org/375092) # Bug title: [powerpc] kernel 2.6 IPS driver failure with IBM ServeRAID 4H adapter # * http://bugzilla.kernel.org/show_bug.cgi?id=12190 # * remote status changed: NEW - CLOSED # * remote resolution changed: (?) - OBSOLETE # * closed upstream tags 375092 + fixed-upstream Bug #375092 [linux-2.6] [powerpc] kernel 2.6 IPS driver failure with IBM ServeRAID 4H adapter Added tag(s) fixed-upstream. usertags 375092 - status-NEW Bug#375092: [powerpc] kernel 2.6 IPS driver failure with IBM ServeRAID 4H adapter Usertags were: status-NEW. Usertags are now: . usertags 375092 + status-CLOSED resolution-OBSOLETE Bug#375092: [powerpc] kernel 2.6 IPS driver failure with IBM ServeRAID 4H adapter There were no usertags set. Usertags are now: resolution-OBSOLETE status-CLOSED. # remote status report for #388453 (http://bugs.debian.org/388453) # Bug title: fails to handle interrupt # * http://bugzilla.kernel.org/show_bug.cgi?id=12796 # * remote status changed: NEW - CLOSED # * remote resolution changed: (?) - INSUFFICIENT-DATA # * closed upstream tags 388453 + fixed-upstream Bug #388453 [linux-2.6] fails to handle interrupt Added tag(s) fixed-upstream. usertags 388453 - status-NEW Bug#388453: fails to handle interrupt Usertags were: status-NEW. Usertags are now: . usertags 388453 + status-CLOSED resolution-INSUFFICIENT-DATA Bug#388453: fails to handle interrupt There were no usertags set. Usertags are now: resolution-INSUFFICIENT-DATA status-CLOSED. # remote status report for #499752 (http://bugs.debian.org/499752) # Bug title: linux-image-2.6.26-1-686: Seagate STT2A no longer works in 2.6.26 # * http://bugzilla.kernel.org/show_bug.cgi?id=12874 # * remote status changed: NEW - CLOSED # * remote resolution changed: (?) - OBSOLETE # * closed upstream tags 499752 + fixed-upstream Bug #499752 [linux-2.6] linux-image-2.6.26-1-686: Seagate STT2A no longer works in 2.6.26 Added tag(s) fixed-upstream. usertags 499752 - status-NEW Bug#499752: linux-image-2.6.26-1-686: Seagate STT2A no longer works in 2.6.26 Usertags were: status-NEW. Usertags are now: . usertags 499752 + status-CLOSED resolution-OBSOLETE Bug#499752: linux-image-2.6.26-1-686: Seagate STT2A no longer works in 2.6.26 There were no usertags set. Usertags are now: resolution-OBSOLETE status-CLOSED. # remote status report for #609846 (http://bugs.debian.org/609846) # Bug title: Toshiba Satellite battery not recognized by acpi # * http://bugzilla.kernel.org/show_bug.cgi?id=15707 # * remote status changed: (?) - REOPENED usertags 609846 + status-REOPENED Bug#609846: Toshiba Satellite battery not recognized by acpi There were no usertags set. Usertags are now: status-REOPENED. thanks Stopping processing here. Please contact me if you need assistance. -- 375092: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=375092 388453: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=388453 499752: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=499752 609846: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609846 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.133849200827077.transcr...@bugs.debian.org
[bts-link] source package src:linux-2.6
# # bts-link upstream status pull for source package src:linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #675022 (http://bugs.debian.org/675022) # Bug title: Frequent lockups when using icedove (thunderbird) # * https://bugs.freedesktop.org/show_bug.cgi?id=50455 # * remote status changed: (?) - RESOLVED # * remote resolution changed: (?) - FIXED usertags 675022 + status-RESOLVED resolution-FIXED 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/20120531192006.15207.55478.btsl...@busoni.debian.org
[bts-link] source package linux-2.6
# # bts-link upstream status pull for source package linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #375092 (http://bugs.debian.org/375092) # Bug title: [powerpc] kernel 2.6 IPS driver failure with IBM ServeRAID 4H adapter # * http://bugzilla.kernel.org/show_bug.cgi?id=12190 # * remote status changed: NEW - CLOSED # * remote resolution changed: (?) - OBSOLETE # * closed upstream tags 375092 + fixed-upstream usertags 375092 - status-NEW usertags 375092 + status-CLOSED resolution-OBSOLETE # remote status report for #388453 (http://bugs.debian.org/388453) # Bug title: fails to handle interrupt # * http://bugzilla.kernel.org/show_bug.cgi?id=12796 # * remote status changed: NEW - CLOSED # * remote resolution changed: (?) - INSUFFICIENT-DATA # * closed upstream tags 388453 + fixed-upstream usertags 388453 - status-NEW usertags 388453 + status-CLOSED resolution-INSUFFICIENT-DATA # remote status report for #499752 (http://bugs.debian.org/499752) # Bug title: linux-image-2.6.26-1-686: Seagate STT2A no longer works in 2.6.26 # * http://bugzilla.kernel.org/show_bug.cgi?id=12874 # * remote status changed: NEW - CLOSED # * remote resolution changed: (?) - OBSOLETE # * closed upstream tags 499752 + fixed-upstream usertags 499752 - status-NEW usertags 499752 + status-CLOSED resolution-OBSOLETE # remote status report for #609846 (http://bugs.debian.org/609846) # Bug title: Toshiba Satellite battery not recognized by acpi # * http://bugzilla.kernel.org/show_bug.cgi?id=15707 # * remote status changed: (?) - REOPENED usertags 609846 + status-REOPENED 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/20120531192006.15207.42824.btsl...@busoni.debian.org
Bug#675302: nouveau: hard lockup when gdm3 starts
On Thu, May 31, 2012 at 00:59:46 -0500, Jonathan Nieder wrote: (You can test by running startx xterm if the xinit package is installed.) You mean startx /usr/bin/xterm. Cheers, Julien -- 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/20120531211540.gl31...@radis.cristau.org
Bug#675302: nouveau: hard lockup when gdm3 starts
On 5/31/2012 2:31 AM, Jonathan Nieder wrote: Hm. Might be possible to get a log with netconsole[1]. [1]http://www.kernel.org/doc/Documentation/networking/netconsole.txt http://blog.mraw.org/2010/11/08/Debugging_using_netconsole/ Now tried running startx /usr/bin/xterm with nouveau, [ 82.427553] [drm] nouveau :01:00.0: PDISP: DCB for 6/0xbad00103 not found [ 82.428536] [drm] nouveau :01:00.0: PDISP: DCB for 0/0xbad00103 not found [ 82.429483] [drm] nouveau :01:00.0: Table 0x0103 not found for 0/2, using first I kept a previously opened ssh connection. When starting X, the screen went black, but didn't totally lock up until I killed the X process from SSH. No further netconsole output, the machine went totally dead. Rebooted, this time tried to start gdm3. This time we got some juice. [ 84.538008] [drm] nouveau :01:00.0: PDISP: DCB for 6/0xbad00103 not found [ 84.538990] [drm] nouveau :01:00.0: PDISP: DCB for 0/0xbad00103 not found [ 84.539937] [drm] nouveau :01:00.0: Table 0x0103 not found for 0/2, using first [ 85.216875] BUG: unable to handle kernel paging request at 8800f1d5f100 [ 85.216940] IP: [a0473eb8] evo_wait.constprop.13+0x3f/0xaa [nouveau] [ 85.216991] PGD 1606063 PUD 1fffc067 PMD 0 [ 85.217020] Oops: 0002 [#1] SMP [ 85.217045] CPU 2 [ 85.217057] Modules linked in: usb_storage uas netconsole configfs nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc ext2 loop firewire_sbp2 tpm_infineon nouveau mxm_wmi snd_hda_codec_hdmi wmi video snd_usb_audio snd_usbmidi_lib uvcvideo snd_rawmidi snd_hda_codec_realtek ttm snd_seq_device drm_kms_helper videodev iTCO_wdt iTCO_vendor_support parport_pc parport psmouse pcspkr serio_raw drm i2c_algo_bit i2c_i801 snd_hda_intel v4l2_compat_ioctl32 snd_hda_codec snd_hwdep snd_pcm snd_page_alloc media button processor tpm_tis tpm i2c_core tpm_bios evdev snd_timer snd soundcore thermal_sys ext4 crc16 jbd2 mbcache dm_mod raid1 md_mod sd_mod crc_t10dif sr_mod cdrom ata_generic usbhid hid pata_jmicron firewire_ohci firewire_core crc_itu_t uhci_hcd r8169 mii ahci libahci libata scsi_mod ehci_hcd usbcore usb_common [last unloaded: scsi_wait_scan] [ 85.217816] [ 85.217826] Pid: 2605, comm: Xorg Not tainted 3.2.0-2-amd64 #1 Gigabyte Technology Co., Ltd. EP45-UD3P/EP45-UD3P [ 85.217885] RIP: 0010:[a0473eb8] [a0473eb8] evo_wait.constprop.13+0x3f/0xaa [nouveau] [ 85.217942] RSP: 0018:88021be35cd8 EFLAGS: 00010212 [ 85.217969] RAX: 88003705f000 RBX: 88021cdc7000 RCX: [ 85.218003] RDX: 2eb40040 RSI: 0064 RDI: 88021cdc7000 [ 85.218037] RBP: 88021b66bac0 R08: R09: 8168d880 [ 85.218071] R10: ffea R11: ffea R12: 2eb40050 [ 85.218105] R13: 88021b859001 R14: 88021db4cbc0 R15: 88021dc03c00 [ 85.218140] FS: 7fbf30962880() GS:880227d0() knlGS: [ 85.218178] CS: 0010 DS: ES: CR0: 80050033 [ 85.218207] CR2: 8800f1d5f100 CR3: 00021dac7000 CR4: 000406e0 [ 85.218241] DR0: DR1: DR2: [ 85.218275] DR3: DR6: 0ff0 DR7: 0400 [ 85.218310] Process Xorg (pid: 2605, threadinfo 88021be34000, task 88021ddb35d0) [ 85.218348] Stack: [ 85.218359] 88021b859000 88021cdc7000 88021cdc7001 a0474303 [ 85.218406] 88021b859001 88021b859000 88021cdc7020 [ 85.218451] 88021b859001 a04746f4 c01c64a3 88021be35df0 [ 85.218497] Call Trace: [ 85.218519] [a0474303] ? nvd0_crtc_cursor_show+0x21/0xf8 [nouveau] [ 85.218562] [a04746f4] ? nvd0_crtc_cursor_set+0xd5/0xf1 [nouveau] [ 85.218602] [a029ad7c] ? drm_mode_cursor_ioctl+0xe5/0x13d [drm] [ 85.218703] [a028f61f] ? drm_ioctl+0x289/0x35e [drm] [ 85.218738] [a029ac97] ? drm_mode_setcrtc+0x376/0x376 [drm] [ 85.218772] [8134c42d] ? do_page_fault+0x2fc/0x337 [ 85.218802] [81106605] ? do_vfs_ioctl+0x459/0x49a [ 85.218831] [81106691] ? sys_ioctl+0x4b/0x72 [ 85.218859] [8134e452] ? system_call_fastpath+0x16/0x1b [ 85.21] Code: 89 fb 48 8b a8 08 0f 00 00 e8 06 f4 ff ff 89 c2 c1 ea 02 41 01 d4 41 81 fc ff 03 00 00 76 66 48 8b 45 10 be 00 00 64 00 48 89 df c7 04 90 00 00 00 20 31 d2 e8 ed f3 ff ff 45 31 c0 83 c9 ff ba [ 85.219253] RIP [a0473eb8] evo_wait.constprop.13+0x3f/0xaa [nouveau] [ 85.219299] RSP 88021be35cd8 [ 85.219316] CR2: 8800f1d5f100 Tried pinging the machine at this point and netconsole printed this: [ 240.648014] INFO: task kworker/2:1:30 blocked for more than 120 seconds. [ 240.648064] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 240.648122] kworker/2:1 D
Processed: tagging 647436
Processing commands for cont...@bugs.debian.org: tags 647436 + pending Bug #647436 [linux-2.6] Failure to boot on plain /dev/sdaN unless scsi_mod.scan=sync or rootdelay=60 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 647436: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647436 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.133852248815570.transcr...@bugs.debian.org
Processed: tagging 672891
Processing commands for cont...@bugs.debian.org: tags 672891 + pending Bug #672891 [linux-2.6] brcmsmac wireless brcms_c_wait_for_tx_completion warning Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 672891: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672891 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.133852331319376.transcr...@bugs.debian.org
Processed: tagging 671801
Processing commands for cont...@bugs.debian.org:
tags 671801 + pending
Bug #671801 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6]
linux-image-3.2.0-0.bpo.2-686-pae: please backport the 3.3 wacom driver to 3.2
Ignoring request to alter tags of bug #671801 to the same tags previously set
thanks
Stopping processing here.
Please contact me if you need assistance.
--
671801: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671801
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.133852332219435.transcr...@bugs.debian.org
Processed: tagging 672582
Processing commands for cont...@bugs.debian.org:
tags 672582 + pending
Bug #672582 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6]
[linux-2.6] No internal speaker sound: HP ENVY 17 Notebook PC
Ignoring request to alter tags of bug #672582 to the same tags previously set
thanks
Stopping processing here.
Please contact me if you need assistance.
--
672582: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672582
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.133852331719397.transcr...@bugs.debian.org
Processed: tagging 673186
Processing commands for cont...@bugs.debian.org:
tags 673186 + pending
Bug #673186 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6]
linux-image-3.2.0-2-686-pae: No support for DWA-140 rev.3 wireless (2001:3c15)
Ignoring request to alter tags of bug #673186 to the same tags previously set
thanks
Stopping processing here.
Please contact me if you need assistance.
--
673186: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673186
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.133852332619456.transcr...@bugs.debian.org
Processed: tagging 673320
Processing commands for cont...@bugs.debian.org:
tags 673320 + pending
Bug #673320 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6]
virtio-modules for sparc64
Ignoring request to alter tags of bug #673320 to the same tags previously set
thanks
Stopping processing here.
Please contact me if you need assistance.
--
673320: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673320
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.133852333019490.transcr...@bugs.debian.org
Processed: tagging 670958
Processing commands for cont...@bugs.debian.org:
tags 670958 + pending
Bug #670958 {Done: Ben Hutchings b...@decadent.org.uk} [src:linux-2.6]
[regression] HP ProBook 451x: udev/power_supply battery oscilates between
remove and add
Bug #638970 {Done: Ben Hutchings b...@decadent.org.uk} [src:linux-2.6]
[regression] HP ProBook 451x: udev/power_supply battery oscilates between
remove and add
Ignoring request to alter tags of bug #670958 to the same tags previously set
Ignoring request to alter tags of bug #638970 to the same tags previously set
thanks
Stopping processing here.
Please contact me if you need assistance.
--
638970: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638970
670958: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670958
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.133852333519512.transcr...@bugs.debian.org
Bug#675425: please update iwlwifi firmware
Package: firmware-iwlwifi Version: 0.35 Severity: normal Since recently, the linux kernels in Wheezy have been requesting for a newer iwlwifi firmware. Please update the firmware package. An excerpt from dmesg: [5.524632] iwlwifi :09:00.0: Firmware has old API version, expected v6, got v5. [5.524688] iwlwifi :09:00.0: New firmware can be obtained from http://www.intellinuxwireless.org/. [5.524742] iwlwifi :09:00.0: loaded firmware version 17.168.5.1 build 33993 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (200, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash firmware-iwlwifi depends on no packages. firmware-iwlwifi recommends no packages. Versions of packages firmware-iwlwifi suggests: ii initramfs-tools 0.102 ii linux-image-3.2.0-2-amd64 [linux-image] 3.2.18-1 ii linux-image-3.2.18-2-minimal [linux-image] 1 -- no debconf information -- 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/20120601044336.4676.6262.reportbug@kaiba.homelan
