Processed: Re: hda-intel: azx_get_response timeout, switching to polling mode: last cmd=0x01db0000

[Debian Bug Tracking System]

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

> forwarded 653524 http://thread.gmane.org/gmane.linux.kernel/1233816
Bug #653524 [linux-2.6] hda-intel: azx_get_response timeout, switching to 
polling mode: last cmd=0x01db
Set Bug forwarded-to-address to 
'http://thread.gmane.org/gmane.linux.kernel/1233816'.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
653524: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653524
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.132514537218739.transcr...@bugs.debian.org

Processed: Re: CPU#0 stuck for 23s, system does not boot

[Debian Bug Tracking System]

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

> severity 646429 important
Bug #646429 [linux-2.6] linux-image-2.6.39-bpo.2-686-pae: CPU lockup on bogus 
values in alarmclock
Severity set to 'important' from 'normal'

> merge 646429 653331
Bug#646429: linux-image-2.6.39-bpo.2-686-pae: CPU lockup on bogus values in 
alarmclock
Bug#653331: linux-image-3.1.0-1-686-pae: CPU#0 stuck for 23s, system does not 
boot
Merged 646429 653331.

> quit
Stopping processing here.

Please contact me if you need assistance.
-- 
646429: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646429
653331: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653331
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.132513785518851.transcr...@bugs.debian.org

Bug#653331: CPU#0 stuck for 23s, system does not boot

[Jonathan Nieder]

severity 646429 important
merge 646429 653331
quit

P. wrote:

> A friend (thanks FrodoBaggins!) suggested Bug#646429
> (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646429) may be the
> same problem.
[...]
> Indeed: stars. After entering "echo +300 >
> /sys/class/rtc/rtc0/wakealarm" a proper value is shown, but is
> instantly forgotten on reboot or powerdown. A couple of
> kernel-reloadings using kexec appear to show that updating the
> wakealarm makes the difference between kernel 3.1 booting or not.

Thanks; merging.

> I haven't tried his patch, for two reasons: #1 I'm not very
> experienced with kernel compilation. #2 It would take approximately
> two eternities on the laptop in question.

There have been some rtc changes upstream:

 - v3.2-rc5~43^2~4 (rtc: Disable the alarm in the hardware,
   2011-11-22), cherry-picked as v3.1.5~23

 - v3.2-rc7~23^2~2 (rtc: Expire alarms after the time is set,
   2011-12-09)

but neither seems relevant.

My advice:

 - Please test version 3.1.5 or newer from sid, testing, or
   experimental.
 - If that reproduces the problem, please also try 3.2-rc7 or newer
   from experimental.
 - If that reproduces the problem, please send a summary of the
   problem to rtc-li...@googlegroups.com, cc-ing
   linux-ker...@vger.kernel.org, Alessandro Zummo
   , John Stultz , and
   either me or this bug log so we can track it.  Be sure to include
   a link to  for the diagnosis and
   be ready to answer questions if the developers have any.
 - If you find yourself wanting to test a patch, see [1] for
   instructions and feel free to do the actual building on some beefy
   machine other than the one you're testing on. :)

Thanks much, and good luck,
Jonathan

[1] http://kernel-handbook.alioth.debian.org/ch-common-tasks.html



-- 
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/20111229055039.GA28780@elie.Belkin

Bug#653331: linux-image-3.1.0-1-686-pae: CPU#0 stuck for 23s, system does not boot

[P.]

A friend (thanks FrodoBaggins!) suggested Bug#646429 
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646429) may be the same 
problem. Indeed, the contents of /proc/driver/rtc look like this:

rtc_time: 02:30:46
rtc_date: 2011-12-29
alrm_time   : 07:05:49
alrm_date   : -02-30
alarm_IRQ   : no
alrm_pending: no
24hr: yes
periodic_IRQ: no
update_IRQ  : no
HPET_emulated   : no
DST_enable  : no
periodic_freq   : 1024
batt_status : okay

Indeed: stars. After entering "echo +300 > /sys/class/rtc/rtc0/wakealarm" a 
proper value is shown, but is instantly forgotten on reboot or powerdown. A 
couple of kernel-reloadings using kexec appear to show that updating the 
wakealarm makes the difference between kernel 3.1 booting or not.

I haven't tried his patch, for two reasons: #1 I'm not very experienced with 
kernel compilation. #2 It would take approximately two eternities on the laptop 
in question. But assuming there's nothing totally wacky in the patch, it would 
most likely be the solution indeed.



--
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/1325129884.86618.yahoomailclas...@web27005.mail.ukl.yahoo.com

Bug#653524: hda-intel: azx_get_response timeout, switching to polling mode: last cmd=0x01db0000

[Petr Baudis]

Package: linux-2.6
Version: 3.1.5-1
Severity: normal

Dear Maintainer,

this bug is twofold - I'm not sure which of the two problems is the real
culprit of the issue I'm seeing, and if it's worth fixing both or just
either one. It boils down to sometimes choppy playback and mainly
applications getting stuck on some audio operations.

(i) hda-intel on my motherboard is sensitive to changing volume during
playback. If I start playback (e.g. mplayer) and start changing volume
levels in alsamixer wildly, in a few seconds the playback will stutter
for a bit and

hda-intel: azx_get_response timeout, switching to polling mode: last 
cmd=0x01db

gets logged.

(ii) After this happens, the playback will get slightly choppy, but that
is barely ever noticeable. The real issue is that applications will
get stuck on some audio operations - most notably, when mplayer stops
playing a song, it will do SNDCTL_DSP_SYNC:

03:52:14.774972 ioctl(4, SNDCTL_DSP_SYNC, 0) = ? ERESTARTSYS (To be 
restarted)
03:52:16.813873 --- SIGINT (Interrupt) @ 0 (0) ---
03:52:16.814479 write(2, "\n", 1)   = 1
03:52:16.821637 write(2, "\nMPlayer interrupted by signal 2"..., 54) = 
54
03:52:16.835238 rt_sigreturn(0x29)  = 16
03:52:16.835348 ioctl(4, SNDCTL_DSP_SYNC, 0) = ? ERESTARTSYS (To be 
restarted)
03:52:18.393655 --- SIGINT (Interrupt) @ 0 (0) ---
03:52:18.393782 write(2, "\n", 1)   = 1
03:52:18.400725 write(2, "\nMPlayer interrupted by signal 2"..., 54) = 
54
03:52:18.415261 close(4294967295)   = -1 EBADF (Bad file descriptor)
03:52:18.416276 exit_group(1)   = ?

When in the polling mode, *sometimes* the SNDCTL_DSP_SYNC will hang
indefinitely. I suspect this also causes my Flash sound playback
to break, but I do not have that confirmed 100%.

Removing the snd-intel-hda module and re-modprobing it will fix the
issue until next time the volume adjustment causes a switch to the
polling mode.

This did not use to happen at least back around 2.6.32. These kernel
versions had different issue with this particular chipset and mapping
DMA space above 4GiB boundary with >4GiB RAM installed, though. Not
sure if this bug does not have something still to do with that (though
similar symptoms disappeared for the network card).

I'd be willing to do some bisecting if people believe it would make
sense.


-- Package-specific info:
** Version:
Linux version 3.1.0-1-amd64 (Debian 3.1.1-1) (b...@decadent.org.uk) (gcc 
version 4.6.2 (Debian 4.6.2-4) ) #1 SMP Mon Nov 14 08:02:25 UTC 2011

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.1.0-1-amd64 
root=UUID=29bbc355-270a-4327-a49f-136e4a62fd94 ro quiet

** Tainted: O (4096)
 * Out-of-tree module has been loaded.

** Kernel log:
[2174402.896629] snd_hda_intel :01:00.1: PCI INT B disabled
[2174402.924482] snd_hda_intel :00:14.2: PCI INT A disabled
[2174405.457990] snd_hda_intel :00:14.2: PCI INT A -> GSI 16 (level, low) 
-> IRQ 16
[2174405.458166] snd_hda_intel :00:14.2: irq 43 for MSI/MSI-X
[2174405.852109] hda_codec: AD1988: BIOS auto-probing.
[2174405.852420] input: HDA Digital PCBeep as 
/devices/pci:00/:00:14.2/input/input10
[2174405.877935] snd_hda_intel :01:00.1: PCI INT B -> GSI 19 (level, low) 
-> IRQ 19
[2174405.878113] snd_hda_intel :01:00.1: irq 44 for MSI/MSI-X
[2174405.878166] snd_hda_intel :01:00.1: setting latency timer to 64
[2174405.892565] HDMI status: Codec=0 Pin=3 Presence_Detect=0 ELD_Valid=0
[2174405.893243] input: HDA ATI HDMI HDMI/DP as 
/devices/pci:00/:00:02.0/:01:00.1/sound/card2/input11
[2175405.280022] hda-intel: azx_get_response timeout, switching to polling 
mode: last cmd=0x01db

[2175808.496464] snd_hda_intel :01:00.1: PCI INT B disabled
[2175808.528486] snd_hda_intel :00:14.2: PCI INT A disabled

[2175811.100597] snd_hda_intel :00:14.2: PCI INT A -> GSI 16 (level, low) 
-> IRQ 16
[2175811.100774] snd_hda_intel :00:14.2: irq 43 for MSI/MSI-X
[2175811.496115] hda_codec: AD1988: BIOS auto-probing.
[2175811.496406] input: HDA Digital PCBeep as 
/devices/pci:00/:00:14.2/input/input12
[2175811.513015] snd_hda_intel :01:00.1: PCI INT B -> GSI 19 (level, low) 
-> IRQ 19
[2175811.513199] snd_hda_intel :01:00.1: irq 44 for MSI/MSI-X
[2175811.513256] snd_hda_intel :01:00.1: setting latency timer to 64
[2175811.533844] HDMI status: Codec=0 Pin=3 Presence_Detect=0 ELD_Valid=0
[2175811.534515] input: HDA ATI HDMI HDMI/DP as 
/devices/pci:00/:00:02.0/:01:00.1/sound/card2/input13

[2175932.840016] hda-intel: azx_get_response timeout, switching to polling 
mode: last cmd=0x01db

** Model information
sys_vendor: System manufacturer
product_name: System Product Name
product_version: System Version
chassis_vendor: Chassis Manufacture
chassis_version: Chassis Version
bios_vendor: American Megatrends Inc.
bios_version: 1009   
board_vendor: ASUSTeK Computer INC.
board_name: M2R32

Bug#653331: linux-image-3.1.0-1-686-pae: CPU#0 stuck for 23s, system does not boot

[P.]

--- On Wed, 28/12/11, Ben Hutchings  wrote:

> From: Ben Hutchings 
> Subject: Re: Bug#653331: linux-image-3.1.0-1-686-pae: CPU#0 stuck for 23s, 
> system does not boot
> To: "P." 
> Cc: 653...@bugs.debian.org
> Date: Wednesday, 28 December, 2011, 16:53
> On Wed, 2011-12-28 at 01:35 +, P.
> wrote:
> [...]
> > I think I have it:
> > http://tinypic.com/r/2ni9xu1/5
> > http://tinypic.com/r/166wrxk/5
> [...]
> 
> This is useful.  Did you also get a list of function
> names after this?  
> 
> Ben.

I decided to take a stab at making a serial console work so I could post the 
full log in text. I managed to make it work:


   GNU GRUB  version 1.99-14

 +--+
 |Debian GNU/Linux, with Linux 3.1.0-1-686-pae  |
 |Debian GNU/Linux, with Linux 3.1.0-1-686-pae (recovery mode)  |
 |Debian GNU/Linux, with Linux 3.1.0-1-486  |
 |Debian GNU/Linux, with Linux 3.1.0-1-486 (recovery mode)  |
 |Debian GNU/Linux, with Linux 2.6.32-5-686 |
 |Debian GNU/Linux, with Linux 2.6.32-5-686 (recovery mode) |
 |  |
 |  |
 |  |
 |  |
 |  |
 |  |
 +--+

  Use the ^ and v keys to select which entry is highlighted.
  Press enter to boot the selected OS, 'e' to edit the commands
  before booting or 'c' for a command-line.
Loading Linux 3.1.0-1-686-pae ...
Loading initial ramdisk ...
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Linux version 3.1.0-1-686-pae (Debian 3.1.5-1) 
(b...@decadent.org.uk) (gcc version 4.6.2 (Debian 4.6.2-4) ) #1 SMP Sun Dec 11 
20:40:16 UTC 2011
[0.00] BIOS-provided physical RAM map:
[0.00]  BIOS-e820:  - 0009fc00 (usable)
[0.00]  BIOS-e820: 0009fc00 - 000a (reserved)
[0.00]  BIOS-e820: 000f - 0010 (reserved)
[0.00]  BIOS-e820: 0010 - 177fb000 (usable)
[0.00]  BIOS-e820: 177fb000 - 177ff000 (ACPI data)
[0.00]  BIOS-e820: 177ff000 - 1780 (ACPI NVS)
[0.00]  BIOS-e820:  - 0001 (reserved)
[0.00] Notice: NX (Execute Disable) protection missing in CPU!
[0.00] DMI 2.3 present.
[0.00] last_pfn = 0x177fb max_arch_pfn = 0x100
[0.00] PAT not supported by CPU.
[0.00] init_memory_mapping: -177fb000
[0.00] RAMDISK: 16b42000 - 1744e000
[0.00] ACPI: RSDP 000f5ab0 00014 (v00 ASUS  )
[0.00] ACPI: RSDT 177fb000 0002C (v01 ASUS   A1F  30303031 MSFT 
31313031)
[0.00] ACPI: FACP 177fb080 00074 (v01 ASUS   A1F  30303031 MSFT 
31313031)
[0.00] ACPI: DSDT 177fb100 036ED (v01   ASUS A1F  1000 INTL 
02002015)
[0.00] ACPI: FACS 177ff000 00040
[0.00] ACPI: BOOT 177fb040 00028 (v01 ASUS   A1F  30303031 MSFT 
31313031)
[0.00] 0MB HIGHMEM available.
[0.00] 375MB LOWMEM available.
[0.00]   mapped low ram: 0 - 177fb000
[0.00]   low ram: 0 - 177fb000
[0.00] Zone PFN ranges:
[0.00]   DMA  0x0010 -> 0x1000
[0.00]   Normal   0x1000 -> 0x000177fb
[0.00]   HighMem  empty
[0.00] Movable zone start PFN for each node
[0.00] early_node_map[2] active PFN ranges
[0.00] 0: 0x0010 -> 0x009f
[0.00] 0: 0x0100 -> 0x000177fb
[0.00] Using APIC driver default
[0.00] ACPI: PM-Timer IO Port: 0xe408
[0.00] SMP: Allowing 1 CPUs, 0 hotplug CPUs
[0.00] Local APIC disabled by BIOS -- you can enable it with "lapic"
[0.00] APIC: disable apic facility
[0.00] APIC: switched to apic NOOP
[0.00] PM: Registered nosave memory: 0009f000 - 000a
[0.00] PM: Registered nosave memory: 000a - 000f
[0.00] PM: Registered nosave memory: 000f - 0010
[0.00] Allocating PCI resources starting at 1780 (gap: 
1780:e87f)
[0.00] Booting paravirtualized kernel on bare hardware
[0.00] setup_percpu: NR_CPUS:32 nr_cpumask_bits:32 nr_cpu_ids:1 
nr_node_ids:1
[0.00] PERCPU: Embedded 13 pages/cpu @d680 s31744 r0 d21504 u2097152
[0.00] 

Bug#652737: linux-image-2.6.32-5-686: ethernet device eth0 (module atl1c) fails. After module reload device is not present any more.

[Ben Hutchings]

On Tue, 2011-12-20 at 13:44 +0100, erik wrote:
> Package: linux-2.6
> Version: 2.6.32-39
> Severity: important
> 
> 
> Description:
> 
> When using wired connection after a short while ethernet connection
> hangs. After unloading atl1c and reloading module it may work again.
> Mostly it ends up with a error message ( kernel:[  371.156342]
> Disabling IRQ #19  kernel:[  774.643828] do_IRQ: 1.177 No irq handler
> for vector (irq -1)) and there is no more eth device present. Only
> reboot changes this. 
[...]

It sounds as if the network controller has switched from MSI to 'legacy'
interrupt mode.  The log shows that it was assigned legacy IRQ 19
(shared with USB) but then switched to MSI IRQ 29.  But I don't
understand why that would happen.

It's probably irrelevant, but can you try removing 'acpi_osi=Linux' from
the kernel command line?

Also, can you test Linux 3.1 from the testing or unstable distribution?
You will need to upgrade initramfs-tools and linux-base, but nothing
else.

Ben.

-- 
Ben Hutchings
Design a system any fool can use, and only a fool will want to use it.


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

Bug#616153: marked as done (i915(?) hangs on resume sometimes)

[Debian Bug Tracking System]

Your message dated Wed, 28 Dec 2011 23:15:02 +0100
with message-id <1325110502.6875.10.camel@deadeye>
and subject line Re: i915(?) hangs on resume sometimes
has caused the Debian Bug report #616153,
regarding i915(?) hangs on resume sometimes
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.)


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

After suspending to RAM and then resuming, the screen sometimes
remains black (but with the backlight on) and the unlock prompt does not
appear when I press a key.  However, magic-SysRq still works.  I infer
from this that the i915 driver or hardware, rather than the keyboard
driver or anything more fundamental, has locked up.

The system resumed reliably with 2.6.32-30.

The kernel log below shows a suspend and resume cycle where this
occurred.

Ben.

-- Package-specific info:
** Version:
Linux version 2.6.37-2-amd64 (Debian 2.6.37-2) (b...@decadent.org.uk) (gcc 
version 4.4.5 (Debian 4.4.5-12) ) #1 SMP Sat Feb 26 22:11:24 UTC 2011

** Command line:
BOOT_IMAGE=/vmlinuz-2.6.37-2-amd64 root=/dev/mapper/deadeye-root ro 
root=/dev/mapper/deadeye-root ro

** Not tainted

** Kernel log:
[20365.668149] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) 
done.
[20365.684185] Suspending console(s) (use no_console_suspend to debug)
[20365.832885] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[20365.833352] sd 0:0:0:0: [sda] Stopping disk
[20365.932485] ehci_hcd :00:1d.7: PCI INT D disabled
[20365.932509] uhci_hcd :00:1d.2: PCI INT C disabled
[20365.932531] uhci_hcd :00:1d.1: PCI INT B disabled
[20365.932559] uhci_hcd :00:1d.0: PCI INT A disabled
[20365.932653] ehci_hcd :00:1a.7: PCI INT C disabled
[20365.932667] HDA Intel :00:1b.0: PCI INT B disabled
[20365.932674] uhci_hcd :00:1a.1: PCI INT B disabled
[20365.932698] uhci_hcd :00:1a.0: PCI INT A disabled
[20365.933396] e1000e :00:19.0: wake-up capability enabled by ACPI
[20365.948112] i915 :00:02.0: power state changed by ACPI to D3
[20366.832896] ata_piix :00:1f.2: PCI INT B disabled
[20366.848056] PM: suspend of devices complete after 1163.468 msecs
[20366.892027] ehci_hcd :00:1d.7: power state changed by ACPI to D3
[20366.916037] uhci_hcd :00:1d.2: power state changed by ACPI to D3
[20366.940037] uhci_hcd :00:1d.0: power state changed by ACPI to D3
[20366.980037] ehci_hcd :00:1a.7: power state changed by ACPI to D3
[20367.004037] uhci_hcd :00:1a.1: power state changed by ACPI to D3
[20367.004148] PM: late suspend of devices complete after 156.085 msecs
[20367.004386] ACPI: Preparing to enter system sleep state S3
[20367.184051] PM: Saving platform NVS memory
[20367.204456] Disabling non-boot CPUs ...
[20367.312023] CPU 1 is now offline
[20367.312027] SMP alternatives: switching to UP code
[20367.318428] Extended CMOS year: 2000
[20367.318428] PM: Restoring platform NVS memory
[20367.318428] Extended CMOS year: 2000
[20367.318428] Enabling non-boot CPUs ...
[20367.318428] SMP alternatives: switching to SMP code
[20367.337843] Booting Node 0 Processor 1 APIC 0x1
[20367.428382] NMI watchdog enabled, takes one hw-pmu counter.
[20367.444155] CPU1 is up
[20367.444555] ACPI: Waking up from system sleep state S3
[20367.820031] uhci_hcd :00:1a.1: power state changed by ACPI to D0
[20367.828037] uhci_hcd :00:1a.1: power state changed by ACPI to D0
[20367.836037] uhci_hcd :00:1a.1: power state changed by ACPI to D0
[20367.844037] uhci_hcd :00:1a.1: power state changed by ACPI to D0
[20367.852036] ehci_hcd :00:1a.7: power state changed by ACPI to D0
[20367.860036] ehci_hcd :00:1a.7: power state changed by ACPI to D0
[20367.868037] uhci_hcd :00:1d.0: power state changed by ACPI to D0
[20367.876037] uhci_hcd :00:1d.0: power state changed by ACPI to D0
[20367.884037] uhci_hcd :00:1d.0: power state changed by ACPI to D0
[20367.892037] uhci_hcd :00:1d.0: power state changed by ACPI to D0
[20367.900037] uhci_hcd :00:1d.2: power state changed by ACPI to D0
[20367.908037] uhci_hcd :00:1d.2: power state changed by ACPI to D0
[20367.916036] uhci_hcd :00:1d.2: power state changed by ACPI to D0
[20367.924037] uhci_hcd :00:1d.2: power state changed by ACPI to D0
[20367.932036] ehci_hcd :00:1d.7: power state changed by ACPI to D0
[20367.940037] ehci_hcd :00:1d.7: power state changed by ACPI to D0
[20367.956039] firewire_ohci :15:00.1: BAR 0: set to [mem 
0xf8301000-0xf83017ff] (PC

Processed: closing 627701, closing 627699

[Debian Bug Tracking System]

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

> close 627701 2.6.32-35
Bug#627701: HP Smart Array controllers (hpsa driver)
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug marked as fixed in version 2.6.32-35, send any further explanations to Ben 
Hutchings 

> close 627699 2.6.32-35
Bug#627699: Brocade Ethernet adapters (bna driver)
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug marked as fixed in version 2.6.32-35, send any further explanations to Ben 
Hutchings 

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
627699: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627699
627701: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627701
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.132511002926995.transcr...@bugs.debian.org

Processed: closing 627703

[Debian Bug Tracking System]

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

> close 627703 2.6.32-35
Bug#627703: PMC-Sierra SAS/SATA HBAs (pm8001 driver)
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug marked as fixed in version 2.6.32-35, send any further explanations to Ben 
Hutchings 

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
627703: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627703
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.132510998726899.transcr...@bugs.debian.org

Processed: retitle 652897 to isci driver missing from installer

[Debian Bug Tracking System]

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

> retitle 652897 isci driver missing from installer
Bug #652897 {Done: Bastian Blank } [src:linux-2.6] SATA 
Controller Driver Not Working
Changed Bug title to 'isci driver missing from installer' from 'SATA Controller 
Driver Not Working'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
652897: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652897
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.132510907522246.transcr...@bugs.debian.org

Processed: fixed 646376 in 3.2~rc4-1~experimental.1

[Debian Bug Tracking System]

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

> # fixed upstream in 3.2-rc1
> fixed 646376 3.2~rc4-1~experimental.1
Bug #646376 [linux-2.6] xserver-xorg-video-ati: Massive screen corruption in 
few hours after login
There is no source info for the package 'linux-2.6' at version 
'3.2~rc4-1~experimental.1' with architecture ''
Unable to make a source version for version '3.2~rc4-1~experimental.1'
Bug Marked as fixed in versions 3.2~rc4-1~experimental.1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
646376: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646376
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.132510812415784.transcr...@bugs.debian.org

Processed: tagging 646376

[Debian Bug Tracking System]

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

> tags 646376 + pending
Bug #646376 [linux-2.6] xserver-xorg-video-ati: Massive screen corruption in 
few hours after login
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
646376: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646376
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.132510809615697.transcr...@bugs.debian.org

Bug#643817: Fix for CVE-2011-2699 can result in crash in VM hosts

[Ben Hutchings]

On Wed, 2011-12-28 at 01:11 +0100, Ben Hutchings wrote:
> On Sat, 2011-12-24 at 12:52 +0100, Moritz Mühlenhoff wrote:
> > On Fri, Sep 30, 2011 at 03:31:42AM +0100, Ben Hutchings wrote:
> > > Package: linux-2.6
> > > Version: 2.6.32-36
> > > Severity: serious
> > > Tags: security patch
> > > 
> > > VM guests using the virtio_net driver may take advantage of UFO (UDP
> > > fragmentation offload) which results in the VM host performing
> > > fragmentation.  As discussed in
> > > , the new IPv6
> > > fragment ID generator will crash in this case because the expected
> > > routing context is missing.
> > > 
> > > No fix is yet available, so we should revert the original fix and
> > > sort this out properly later.
> > 
> > Do you know if a fix for 2.6.32 is now available?
> 
> I *think* that we should be able to use this fix from 3.0-stable:
> 
> commit a1b7ab0836a56fa4c9578f88ba1042398d7d9316
> Author: Jason Wang 
> Date:   Sun Oct 9 10:56:44 2011 +0800
> 
> ipv6: fix NULL dereference in udp6_ufo_fragment()

Try as I might, I couldn't reproduce the crash that this fixes.  But the
fix certainly seems reasonable.  And there shouldn't be any other
callers that need to be considered, as they would have caused a build
failure in 2.6.32-36.

I'm attaching my test program that sends a packet requiring UFO through
a tun device.  You will need to enable forwarding from the tun device to
some other device, add routes and select source and destination addresses
such that the kernel will try to forward the packet.

Ben.

-- 
Ben Hutchings
Hoare's Law of Large Problems:
Inside every large problem is a small problem struggling to get out.

/*
 * tun_ufo.c - test for UFO regression fixed by
 * commit a1b7ab0836a56fa4c9578f88ba1042398d7d9316 in 3.0-stable
 *
 * Ben Hutchings, with checksum code cribbed from Linux.  GPLv2.
 */

#include 
#include 
#include 
#include 
#include 
#include 

#include 
#include 
#include 

#include 
#include 
#include 
#include 
#include 
#include 

#define constant_htons(x) ((u_short)((u_short)(x) >> 8 | (u_short)(x) << 8))

static struct {
struct virtio_net_hdr gso;
struct ip6_hdr ip;
struct udphdr udp;
char body[2000];
} __attribute__((packed)) packet = {
.gso = {
	.flags = VIRTIO_NET_HDR_F_NEEDS_CSUM,
	.gso_type = VIRTIO_NET_HDR_GSO_UDP,
	.hdr_len = sizeof(packet.ip) + sizeof(packet.udp),
	.gso_size = 1000,
	.csum_start = sizeof(packet.ip),
	.csum_offset = sizeof(packet.ip) + offsetof(struct udphdr, check),
},
.ip = {
	.ip6_plen = constant_htons(sizeof(packet.udp) + sizeof(packet.body)),
	.ip6_hlim = 10,
	.ip6_nxt = IPPROTO_UDP,
	.ip6_src.s6_addr = { 0xfe,0x80,0,0, 0,0,0,0,
			 0x50,0x54,0,0xff, 0xfe,0xa4,0x67,0xd7 },
	.ip6_dst.s6_addr = { 0xfe,0x80,0,0, 0,0,0,0,
			 0xfc,0x54,0,0xff, 0xfe,0xa4,0x67,0xd7 },
},
.udp = {
	.source = constant_htons(1234),
	.dest = constant_htons(5678),
	.len = constant_htons(sizeof(packet.udp) + sizeof(packet.body)),
}
};

static unsigned short from32to16(unsigned long x)
{
	/* add up 16-bit and 16-bit for 16+c bit */
	x = (x & 0x) + (x >> 16);
	/* add up carry.. */
	x = (x & 0x) + (x >> 16);
	return x;
}

static unsigned int do_csum(const unsigned char *buff, int len)
{
	int odd, count;
	unsigned long result = 0;

	if (len <= 0)
		goto out;
	odd = 1 & (unsigned long) buff;
	if (odd) {
		result = *buff;
		len--;
		buff++;
	}
	count = len >> 1;		/* nr of 16-bit words.. */
	if (count) {
		if (2 & (unsigned long) buff) {
			result += *(unsigned short *) buff;
			count--;
			len -= 2;
			buff += 2;
		}
		count >>= 1;		/* nr of 32-bit words.. */
		if (count) {
			unsigned long carry = 0;
			do {
unsigned long w = *(unsigned int *) buff;
count--;
buff += 4;
result += carry;
result += w;
carry = (w > result);
			} while (count);
			result += carry;
			result = (result & 0x) + (result >> 16);
		}
		if (len & 2) {
			result += *(unsigned short *) buff;
			buff += 2;
		}
	}
	if (len & 1)
		result += *buff;
	result = from32to16(result);
	if (odd)
		result = ((result >> 8) & 0xff) | ((result & 0xff) << 8);
out:
	return result;
}

static u_short csum_fold(u_int csum)
{
	u_int sum = csum;
	sum = (sum & 0x) + (sum >> 16);
	sum = (sum & 0x) + (sum >> 16);
	return (u_short)~sum;
}

u_short ip_fast_csum(const void *iph, unsigned int ihl)
{
	return (u_short)~do_csum(iph, ihl*4);
}

static u_short csum_ipv6_magic(const struct in6_addr *saddr,
			   const struct in6_addr *daddr,
			   u_int len, unsigned short proto,
			   u_int csum)
{

	int carry;
	u_int ulen;
	u_int uproto;
	u_int sum = (u_int)csum;

	sum += (u_int)saddr->s6_addr32[0];
	carry = (sum < (u_int)saddr->s6_addr32[0]);
	sum += carry;

	sum += (u_int)saddr->s6_addr32[1];
	carry = (sum < (u_int)saddr->s6_addr32[1]);
	sum += carry;

	sum += (u_int)saddr->s6_addr32[2];
	carry = (sum < (u_int)saddr->s6_addr32[2]);
	sum += carry;

	sum += (u_int)saddr->s6_addr32[3

Processed: unarchiving 643817

[Debian Bug Tracking System]

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

> unarchive 643817
Bug #643817 {Done: Ben Hutchings } [linux-2.6] Fix for 
CVE-2011-2699 can result in crash in VM hosts
Unarchived Bug 643817
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
643817: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643817
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.13251058365554.transcr...@bugs.debian.org

Bug#653179: [rt2x00-users] Fwd: linux-image-3.1.0-1-amd64: Can't switch off WoW option of RT5390 wi-fi card, notebook wakes on wi-fi activity

[Ivo Van Doorn]

On Wed, Dec 28, 2011 at 12:09 PM, Gertjan van Wingerde
 wrote:
> On 12/28/11 08:56, Helmut Schaa wrote:
>> Hi,
>>
>> Am Sonntag, 25. Dezember 2011, 09:07:42 schrieb pol kh:
>>> I'd like to be able to manage WoW option on Ralink 5390 on my HP Pavilion
>>> dv6-6030er. WoW is enabled by default in BIOS, which is locked by vendor.
>>> So I can't switch it off. Using ethtool doesn't help, because driver can't
>>> hanlder with WoW. My notebook wakes on wi-fi activity when I'd like it to
>>> be asleep. I had sent a bug report to Debian GNU/Linux maintainers and got
>>> the following answer (below my bug report is attached):
>>
>> this sounds really strange :). Unfortunately nobody is working on WoW support
>> for rt2x00 currently.
>>
>> Ivo, Gertjan, do we have any information yet how WoW for the ralink devices
>> is supposed to work? Since the WoW framework was already merged AFAIK it 
>> might
>> be a trivial thing to add ...
>
> No, I've never seen any information about this.
>
> A quick look at the Ralink legacy drivers also reveal that these do not
> contain any code for this, so it will be difficult to add support for
> this in rt2x00.

Even the specsheets don't contain any reference about WoW, so I really
can't say anything about it either.

Ivo



-- 
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/CAOZOX0Vz1GNjnJ2z2ABd=nyff9rsiufhfwbkmxefdrvgp8l...@mail.gmail.com

linux-2.6_3.2~rc7-1~experimental.1_amd64.changes ACCEPTED into experimental

[Debian FTP Masters]

Accepted:
acpi-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  to 
main/l/linux-2.6/acpi-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
ata-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  to 
main/l/linux-2.6/ata-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
btrfs-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  to 
main/l/linux-2.6/btrfs-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
cdrom-core-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  to 
main/l/linux-2.6/cdrom-core-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
core-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  to 
main/l/linux-2.6/core-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
crc-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  to 
main/l/linux-2.6/crc-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
crypto-dm-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  to 
main/l/linux-2.6/crypto-dm-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
crypto-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  to 
main/l/linux-2.6/crypto-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
efi-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  to 
main/l/linux-2.6/efi-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
event-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  to 
main/l/linux-2.6/event-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
ext2-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  to 
main/l/linux-2.6/ext2-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
ext3-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  to 
main/l/linux-2.6/ext3-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
ext4-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  to 
main/l/linux-2.6/ext4-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
fat-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  to 
main/l/linux-2.6/fat-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
fb-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  to 
main/l/linux-2.6/fb-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
firewire-core-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  to 
main/l/linux-2.6/firewire-core-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
floppy-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  to 
main/l/linux-2.6/floppy-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
i2c-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  to 
main/l/linux-2.6/i2c-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
ide-core-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  to 
main/l/linux-2.6/ide-core-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
ide-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  to 
main/l/linux-2.6/ide-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
input-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  to 
main/l/linux-2.6/input-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
irda-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  to 
main/l/linux-2.6/irda-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
isofs-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  to 
main/l/linux-2.6/isofs-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
jfs-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  to 
main/l/linux-2.6/jfs-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
kernel-image-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  to 
main/l/linux-2.6/kernel-image-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
linux-2.6_3.2~rc7-1~experimental.1.diff.gz
  to main/l/linux-2.6/linux-2.6_3.2~rc7-1~experimental.1.diff.gz
linux-2.6_3.2~rc7-1~experimental.1.dsc
  to main/l/linux-2.6/linux-2.6_3.2~rc7-1~experimental.1.dsc
linux-2.6_3.2~rc7.orig.tar.gz
  to main/l/linux-2.6/linux-2.6_3.2~rc7.orig.tar.gz
linux-doc-3.2_3.2~rc7-1~experimental.1_all.deb
  to main/l/linux-2.6/linux-doc-3.2_3.2~rc7-1~experimental.1_all.deb
linux-headers-3.2.0-rc7-all-amd64_3.2~rc7-1~experimental.1_amd64.deb
  to 
main/l/linux-2.6/linux-headers-3.2.0-rc7-all-amd64_3.2~rc7-1~experimental.1_amd64.deb
linux-headers-3.2.0-rc7-all_3.2~rc7-1~experimental.1_amd64.deb
  to 
main/l/linux-2.6/linux-headers-3.2.0-rc7-all_3.2~rc7-1~experimental.1_amd64.deb
linux-headers-3.2.0-rc7-amd64_3.2~rc7-1~experimental.1_amd64.deb
  to 
main/l/linux-2.6/linux-headers-3.2.0-rc7-amd64_3.2~rc7-1~experimental.1_amd64.deb
linux-headers-3.2.0-rc7-common-rt_3.2~rc7-1~experimental.1_amd64.deb
  to 
main/l/linux-2.6/linu

Processed: tagging as pending bugs that are closed by packages in NEW

[Debian Bug Tracking System]

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

> # Wed Dec 28 19:03:06 UTC 2011
> # Tagging as pending bugs that are closed by packages in NEW
> # http://ftp-master.debian.org/new.html
> #
> # Source package in NEW: liblingua-identify-perl
> tags 653410 + pending
Bug #653410 [wnpp] ITP: liblingua-identify-perl -- Language identification 
module for perl
Added tag(s) pending.
> # Source package in NEW: ruby-serialport
> tags 597526 + pending
Bug #597526 [libserialport-ruby1.8] libserialport-ruby1.8: get/set line state 
(cts/dtr) is broken
Added tag(s) pending.
> # Source package in NEW: linux-2.6
> tags 586494 + pending
Bug #586494 {Done: dann frazier } [linux-2.6] 
linux-image-2.6.26-2-686: Dell PowerEdge 4200's don't work with  2.6.26
Added tag(s) pending.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
586494: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586494
653410: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653410
597526: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597526
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.13250990217223.transcr...@bugs.debian.org

linux-2.6_3.2~rc7-1~experimental.1_amd64.changes is NEW

[Debian FTP Masters]

(new) acpi-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb extra 
debian-installer
ACPI support modules
 This package contains kernel modules for ACPI.
(new) ata-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb extra 
debian-installer
ATA disk modules
 This package contains core ATA disk modules used by both PATA and SATA
 disk drivers.
(new) btrfs-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb 
extra debian-installer
BTRFS filesystem support
 This package contains the BTRFS filesystem module for the kernel.
(new) cdrom-core-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb 
standard debian-installer
CDROM support
 This package contains core CDROM support for the kernel.
(new) core-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb 
standard debian-installer
Core modules
 This package contains core modules for the kernel, that will almost
 always be needed.
(new) crc-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb extra 
debian-installer
CRC modules
 This package contains CRC support modules.
(new) crypto-dm-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb 
extra debian-installer
devicemapper crypto module
 This package contains the devicemapper crypto (dm-crypt) module.
(new) crypto-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb 
extra debian-installer
crypto modules
 This package contains crypto modules.
(new) efi-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb extra 
debian-installer
EFI modules
 This package contains EFI modules.
(new) event-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb 
extra debian-installer
Event support
 This package contains event drivers for the kernel.
(new) ext2-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb 
standard debian-installer
EXT2 filesystem support
 This package contains the EXT2 filesystem module for the kernel.
(new) ext3-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb 
standard debian-installer
EXT3 filesystem support
 This package contains the EXT3 filesystem module for the kernel.
(new) ext4-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb 
standard debian-installer
EXT4 filesystem support
 This package contains the EXT4 filesystem module for the kernel.
(new) fat-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb 
standard debian-installer
FAT filesystem support
 This package contains the FAT and VFAT filesystem modules for the kernel.
(new) fb-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb extra 
debian-installer
Frame buffer support
 This package contains Frame buffer drivers for the kernel.
(new) 
firewire-core-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb 
standard debian-installer
Core FireWire drivers
 This package contains core FireWire drivers for the kernel.
(new) floppy-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb 
standard debian-installer
Floppy driver
 This package contains the floppy driver for the kernel.
(new) i2c-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb extra 
debian-installer
i2c support modules
 This package contains basic i2c support modules.
(new) ide-core-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb 
standard debian-installer
IDE support
 This package contains core IDE support for the kernel.
(new) ide-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb 
standard debian-installer
IDE drivers
 This package contains IDE drivers for the kernel.
(new) input-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb 
extra debian-installer
Input devices support
 This package contains input device drivers for the kernel.
(new) irda-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb extra 
debian-installer
Infrared devices support
 This package contains infrared device drivers for the kernel.
(new) isofs-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb 
standard debian-installer
ISOFS filesystem support
 This package contains the ISOFS filesystem module for the kernel.
(new) jfs-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb 
standard debian-installer
JFS filesystem support
 This package contains the JFS filesystem module for the kernel.
(new) kernel-image-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb extra 
debian-installer
Linux kernel binary image for the Debian installer
 This package contains the kernel image for the Debian installer boot
 images.  It does _not_ provide a usable kernel for your full Debian
 system.
linux-2.6_3.2~rc7-1~experimental.1.diff.gz
  to main/l/linux-2.6/linux-2.6_3.2~rc7-1~experimental.1.diff.gz
linux-2.6_3.2~rc7-1~experimental.1.dsc
  to main/l/linux-2.6/linux-2.6_3.2~rc7-1~experimental.1.dsc
linux-2.6_3.2~rc7.orig.tar.gz
  to main/l/linux-2.6/linux-2.6_3.2~rc7.orig.tar.gz
linux-doc-3.2_3.2~rc7-1~experimental.1_all.deb
  to main/l/linux-2.6/linux-doc-3.2_3.2~rc7

Bug#644174: Info received (Bug#644174: Info received ())

[Mathieu Malaterre]

Looks like this is a duplicate of 623004



-- 
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/ca+7wuszv4f3wtofif-mhv6uzln8gzep5o0mp3cb6xomvnjf...@mail.gmail.com

Bug#644174: Info received ()

[Mathieu Malaterre]

Some more info. Running linux 3.0.2 eventually leads to:


[  484.679306] BUG: scheduling while atomic: swapper/0/0x1100
[  484.679315] Modules linked in: nls_utf8 nls_cp437 vfat fat cryptd
aes_x86_64 aes_generic cpufreq_stats cpufreq_powersave
cpufreq_conservative cpufreq_userspace acpi_cpufreq mperf parport_pc
ppdev lp parport rfcomm bridge stp bnep binfmt_misc uinput fuse loop
snd_hda_codec_realtek arc4 snd_hda_intel snd_hda_codec iwlwifi
snd_hwdep mac80211 snd_pcm btusb bluetooth i915 drm_kms_helper drm
snd_seq snd_timer snd_seq_device dell_laptop cfg80211 rfkill ac
uvcvideo psmouse videodev snd soundcore snd_page_alloc dell_wmi
tpm_tis media tpm serio_raw sparse_keymap v4l2_compat_ioctl32
i2c_algo_bit tpm_bios battery power_supply button i2c_i801 wmi
processor evdev video dcdbas i2c_core crc16 pcspkr usbhid hid ext3 jbd
mbcache sg sr_mod sd_mod cdrom crc_t10dif ums_realtek usb_storage uas
xhci_hcd ahci libahci libata scsi_mod ehci_hcd r8169 mii usbcore
usb_common thermal thermal_sys [last unloaded: scsi_wait_scan]
[  484.679466] CPU 0
[  484.679469] Modules linked in: nls_utf8 nls_cp437 vfat fat cryptd
aes_x86_64 aes_generic cpufreq_stats cpufreq_powersave
cpufreq_conservative cpufreq_userspace acpi_cpufreq mperf parport_pc
ppdev lp parport rfcomm bridge stp bnep binfmt_misc uinput fuse loop
snd_hda_codec_realtek arc4 snd_hda_intel snd_hda_codec iwlwifi
snd_hwdep mac80211 snd_pcm btusb bluetooth i915 drm_kms_helper drm
snd_seq snd_timer snd_seq_device dell_laptop cfg80211 rfkill ac
uvcvideo psmouse videodev snd soundcore snd_page_alloc dell_wmi
tpm_tis media tpm serio_raw sparse_keymap v4l2_compat_ioctl32
i2c_algo_bit tpm_bios battery power_supply button i2c_i801 wmi
processor evdev video dcdbas i2c_core crc16 pcspkr usbhid hid ext3 jbd
mbcache sg sr_mod sd_mod cdrom crc_t10dif ums_realtek usb_storage uas
xhci_hcd ahci libahci libata scsi_mod ehci_hcd r8169 mii usbcore
usb_common thermal thermal_sys [last unloaded: scsi_wait_scan]
[  484.679591]
[  484.679597] Pid: 0, comm: swapper Not tainted 3.2.0-rc4-amd64 #1
Dell Inc.  Dell System Vostro 3750/0VP036
[  484.679608] RIP: 0010:[]  []
intel_idle+0xea/0x119
[  484.679625] RSP: 0018:81601e88  EFLAGS: 0202
[  484.679630] RAX:  RBX: 811a5bfc RCX: 17b6
[  484.679636] RDX: 17b6 RSI:  RDI: 03e8
[  484.679641] RBP: 0004 R08: 17ba R09: 17ba
[  484.679647] R10: 81780640 R11: 81601fd8 R12: 8801bfa0e700
[  484.679652] R13: 8801bfa0e710 R14: 8801ad3c3ac8 R15: 8801bfa0e7f0
[  484.679659] FS:  () GS:8801bfa0()
knlGS:
[  484.679666] CS:  0010 DS:  ES:  CR0: 8005003b
[  484.679671] CR2: 0240b471 CR3: 01605000 CR4: 000406f0
[  484.679677] DR0:  DR1:  DR2: 
[  484.679683] DR3:  DR6: 0ff0 DR7: 0400
[  484.679689] Process swapper (pid: 0, threadinfo 8160,
task 8160d020)
[  484.679694] Stack:
[  484.679697]   17b6 

[  484.679708]  17b6 005caf48 8801bfa19870
81644a80
[  484.679718]  fff0 0004 81644bc0
8125bdf3
[  484.679728] Call Trace:
[  484.679741]  [] ? cpuidle_idle_call+0xec/0x179
[  484.679753]  [] ? cpu_idle+0xa1/0xe8
[  484.679764]  [] ? start_kernel+0x3bd/0x3c8
[  484.679773]  [] ? early_idt_handlers+0x140/0x140
[  484.679782]  [] ? x86_64_start_kernel+0x104/0x111
[  484.679787] Code: 29 f0 48 89 c7 e8 6b dc e6 ff 4c 69 e8 40 42 0f
00 48 89 04 24 48 89 54 24 08 48 89 44 24 18 48 89 54 24 20 49 01 d5
fb 66 66 90
[  484.679834]  66 90 85 1d b2 8b 46 00 75 0f 48 8d 74 24 2c bf 05 00 00 00
[  484.679858] Call Trace:
[  484.679866]  [] ? cpuidle_idle_call+0xec/0x179
[  484.679874]  [] ? cpu_idle+0xa1/0xe8
[  484.679882]  [] ? start_kernel+0x3bd/0x3c8
[  484.679891]  [] ? early_idt_handlers+0x140/0x140
[  484.679899]  [] ? x86_64_start_kernel+0x104/0x111
[  545.528641] BUG: scheduling while atomic: swapper/0/0x1100
[  545.528649] Modules linked in: nls_utf8 nls_cp437 vfat fat cryptd
aes_x86_64 aes_generic cpufreq_stats cpufreq_powersave
cpufreq_conservative cpufreq_userspace acpi_cpufreq mperf parport_pc
ppdev lp parport rfcomm bridge stp bnep binfmt_misc uinput fuse loop
snd_hda_codec_realtek arc4 snd_hda_intel snd_hda_codec iwlwifi
snd_hwdep mac80211 snd_pcm btusb bluetooth i915 drm_kms_helper drm
snd_seq snd_timer snd_seq_device dell_laptop cfg80211 rfkill ac
uvcvideo psmouse videodev snd soundcore snd_page_alloc dell_wmi
tpm_tis media tpm serio_raw sparse_keymap v4l2_compat_ioctl32
i2c_algo_bit tpm_bios battery power_supply button i2c_i801 wmi
processor evdev video dcdbas i2c_core crc16 pcspkr usbhid hid ext3 jbd
mbcache sg sr_mod sd_mod cdrom crc_t10dif ums_realtek usb_stora

Bug#644174: ACPI I/O resource conflicts with ACPI region SMBI

[Mathieu Malaterre]

On Thu, Dec 22, 2011 at 8:52 PM, Sarah Sharp
 wrote:
> On Thu, Dec 22, 2011 at 04:18:56PM +0100, Mathieu Malaterre wrote:
>> On Fri, Dec 16, 2011 at 11:27 AM, Jonathan Nieder  wrote:
>> >  - Please test a v3.2 release candidate from experimental.  The only
>> >   packages from outside squeeze that should be needed for this, aside
>> >   from the kernel image itself, are linux-base and initramfs-tools.
>> >
>> >  - If it reproduces the problem, please blacklist the xhci_hcd
>> >   module by writing
>> >
>> >        blacklist xhci_hcd
>> >
>> >   to a file /etc/modprobe.d/mm-blacklist-xhci.conf, run
>> >
>> >        update-initramfs -u -k all
>> >
>> >   and reboot to try again without USB 3.0 support.  If we're very
>> >   lucky, this will work around the problem.  In that case, please
>> >   write a summary of the problem to upstream
>> >   (linux-...@vger.kernel.org, cc-ing Sarah Sharp
>> >    and either me or this bug log so we
>> >   can track the resulting discussion).  Be sure to include:
>> >
>> >    - steps to reproduce the problem
>> >    - symptoms, and how they differ from what you expected
>> >    - ways to avoid triggering the problem (maybe some USB ports
>> >      trigger it and others don't? etc)
>> >    - full "dmesg" output from booting, and a photo of the screen
>> >      after reproducing the problem (ideally by running "modprobe
>> >      xhci_hcd" in the very same run of Linux), as attachments
>> >    - which kernel versions you've tested, and what happened with each
>> >    - a link to this bug log for the full story
>> >    - any other weird symptoms or observations
>>
>> System: Dell System Vostro 3750 / Portable Computer
>>
>> Ok. So I am running: 3.2.0-rc4-amd64 from debian experimental.
>>
>> No mouse plugged to USB 2.0/3.0 interface: boot is fine
>> Mouse plugged to USB 2.0 interface: boot is fine
>> Mouse plugged to USB 3.0 interface: boot simply stops
>
> Does the boot stop when you have a non-HID USB device plugged into the
> USB 3.0 port (e.g. hub or flash drive or USB speaker)?  It could be an
> issue with a buggy BIOS trying to use the mouse and keyboard (HID
> devices) attached to the USB 3.0 host.  Perhaps it changes the ACPI
> tables when it tries to use the USB 3.0 host controller, and
> accidentally overlaps the regions?  But if your keyboard and mouse were
> under USB 2.0, maybe it will only map in the USB 2.0 host controller.

I tried booting kernel 3.0.2 (debian/unstable 3.2.0-rc4-amd64) with a
USB key plugged into USB 3.0 and was stuck again. So I can confirm
that with a normal USB key (non-HID) plugged in USB 3.0 port, makes
the kernel refuse to boot.

After a normal boot, key appears as :
[  158.736727] usb 3-2: new high-speed USB device number 2 using xhci_hcd
[  158.755680] xhci_hcd :03:00.0: WARN: short transfer on control ep
[  158.756522] xhci_hcd :03:00.0: WARN: short transfer on control ep
[  158.757426] xhci_hcd :03:00.0: WARN: short transfer on control ep
[  158.758299] xhci_hcd :03:00.0: WARN: short transfer on control ep
[  158.758698] usb 3-2: New USB device found, idVendor=0951, idProduct=160f
[  158.758708] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  158.758714] usb 3-2: Product: DT Mini Slim
[  158.758719] usb 3-2: Manufacturer: Kingston
[  158.758723] usb 3-2: SerialNumber: 0019E06B07B5F9A1879A0D15
[  158.760294] scsi7 : usb-storage 3-2:1.0
[  159.760670] scsi 7:0:0:0: Direct-Access Kingston DT Mini Slim
  1.00 PQ: 0 ANSI: 2
[  159.763089] sd 7:0:0:0: Attached scsi generic sg2 type 0
[  159.763655] sd 7:0:0:0: [sdb] 15654848 512-byte logical blocks:
(8.01 GB/7.46 GiB)
[  159.763834] sd 7:0:0:0: [sdb] Write Protect is off
[  159.763841] sd 7:0:0:0: [sdb] Mode Sense: 16 0f 09 51
[  159.764012] sd 7:0:0:0: [sdb] Incomplete mode parameter data
[  159.764019] sd 7:0:0:0: [sdb] Assuming drive cache: write through
[  159.765193] sd 7:0:0:0: [sdb] Incomplete mode parameter data
[  159.765200] sd 7:0:0:0: [sdb] Assuming drive cache: write through
[  159.765778]  sdb: sdb1
[  159.766855] sd 7:0:0:0: [sdb] Incomplete mode parameter data
[  159.766865] sd 7:0:0:0: [sdb] Assuming drive cache: write through
[  159.766875] sd 7:0:0:0: [sdb] Attached SCSI removable disk


>> As suggested by Jonathan N. [1] here is what I did next:
>>
>> $ cat /etc/modprobe.d/mm-blacklist-xhci.conf
>> blacklist xhci_hcd
>> $ update-initramfs -u -k all
>> $ sudo reboot
>
> Were you blacklisting xhci only because of the "xhci_hcd :03:00.0:
> WARN: Stalled endpoint" messages?  Because those messages are harmless,
> and don't mean anything is *wrong* with the host controller.

I simply blindly follow the suggestion.

> Even if there's no xHCI driver loaded, it seems that ACPI is noticing
> the conflict between the PCI registers and another region.  So unloading
> the xHCI driver won't help your system boot.  You'd need to get a fix
> into the ACPI subsystem to work around the conflict.  I don't think any
> xHCI driver modification can 

Processing of linux-2.6_3.2~rc7-1~experimental.1_amd64.changes

[Debian FTP Masters]

linux-2.6_3.2~rc7-1~experimental.1_amd64.changes uploaded successfully to 
localhost
along with the files:
  linux-2.6_3.2~rc7-1~experimental.1.dsc
  linux-2.6_3.2~rc7.orig.tar.gz
  linux-2.6_3.2~rc7-1~experimental.1.diff.gz
  linux-support-3.2.0-rc7_3.2~rc7-1~experimental.1_all.deb
  linux-patch-debian-3.2_3.2~rc7-1~experimental.1_all.deb
  linux-source-3.2_3.2~rc7-1~experimental.1_all.deb
  linux-doc-3.2_3.2~rc7-1~experimental.1_all.deb
  linux-manual-3.2_3.2~rc7-1~experimental.1_all.deb
  linux-headers-3.2.0-rc7-amd64_3.2~rc7-1~experimental.1_amd64.deb
  linux-image-3.2.0-rc7-amd64-dbg_3.2~rc7-1~experimental.1_amd64.deb
  linux-image-3.2.0-rc7-amd64_3.2~rc7-1~experimental.1_amd64.deb
  xen-linux-system-3.2.0-rc7-amd64_3.2~rc7-1~experimental.1_amd64.deb
  linux-headers-3.2.0-rc7-common_3.2~rc7-1~experimental.1_amd64.deb
  linux-headers-3.2.0-rc7-all_3.2~rc7-1~experimental.1_amd64.deb
  linux-headers-3.2.0-rc7-all-amd64_3.2~rc7-1~experimental.1_amd64.deb
  linux-libc-dev_3.2~rc7-1~experimental.1_amd64.deb
  linux-headers-3.2.0-rc7-rt-amd64_3.2~rc7-1~experimental.1_amd64.deb
  linux-image-3.2.0-rc7-rt-amd64-dbg_3.2~rc7-1~experimental.1_amd64.deb
  linux-image-3.2.0-rc7-rt-amd64_3.2~rc7-1~experimental.1_amd64.deb
  xen-linux-system-3.2.0-rc7-rt-amd64_3.2~rc7-1~experimental.1_amd64.deb
  linux-headers-3.2.0-rc7-common-rt_3.2~rc7-1~experimental.1_amd64.deb
  kernel-image-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  nic-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  nic-extra-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  nic-wireless-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  nic-shared-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  serial-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  usb-serial-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  ppp-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  ide-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  pata-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  ide-core-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  cdrom-core-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  firewire-core-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  scsi-core-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  scsi-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  scsi-common-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  scsi-extra-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  plip-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  floppy-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  loop-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  btrfs-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  ext2-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  ext3-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  ext4-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  isofs-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  jfs-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  ntfs-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  reiserfs-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  xfs-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  fat-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  ufs-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  qnx4-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  md-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  multipath-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  usb-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  usb-storage-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  pcmcia-storage-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  fb-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  input-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  event-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  mouse-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  irda-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  parport-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  nic-pcmcia-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  pcmcia-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  nic-usb-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  sata-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  core-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  acpi-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  i2c-modules-3.2.0-rc7-amd64-di_3.2~rc7-1~experimental.1_amd64.udeb
  crc-modules-3.2.0-rc7-a

Bug#653331: linux-image-3.1.0-1-686-pae: CPU#0 stuck for 23s, system does not boot

[Ben Hutchings]

On Wed, 2011-12-28 at 01:35 +, P. wrote:
[...]
> I think I have it:
> http://tinypic.com/r/2ni9xu1/5
> http://tinypic.com/r/166wrxk/5
[...]

This is useful.  Did you also get a list of function names after this?  

Ben.

-- 
Ben Hutchings
Hoare's Law of Large Problems:
Inside every large problem is a small problem struggling to get out.


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

Bug#641749: firmware loading failure for AR3011 (0cf3:3000 or 0cf3:3005 ?)

[Andres Cimmarusti]

Dear all,

This is an upstream bug report for known bugs in at least 3 linux distros:

Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641749
Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=702375

***Steps to reproduce***

- Boot current Debian testing / Fedora 16 / Ubuntu 11.10 (using
kernels 3.1.x and 3.0.x)

***Expected behavior***

- Working bluetooth and no problems in rebooting laptop as occurs
using Ubuntu 11.04 / Fedora 15 and/or Debian Squeeze (using kernels
2.6.38 or newer)

- lsusb reveals this:

Bus 001 Device 004: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth

***Actual Result***

- Boot process stalls and fails to load firmware for this Atheros
AR3011 bluetooth module:

[9.335184] ath3k_load_firmware: Can't change to loading configuration err
[9.335413] ath3k: probe of 1-1.3:1.0 failed with error -110
[9.335459] usbcore: registered new interface driver ath3k

- lsusb of the device shows this:

Bus 001 Device 003: ID 0cf3:3000 Atheros Communications, Inc. AR3011
Bluetooth (no firmware)

- After login bluetooth does not work. Furthermore, choosing to
"Restart" the laptop causes it to hang at first pre-bios post screen.

***Things I've tried***

The weird part about this bug is that using Debian squeeze as a base,
I can run the newest kernels (2.6.39, 3.0.x and 3.1.x) and I have no
problems at all. Also the output of lsusb differs substantially from
the working vs broken system. Ubuntu 11.04 and Fedora 15 also work
fine using kernel 2.6.38.

Here is an example dmesg, using kernel 3.0.8 on Squeeze (no problem):

http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=56;filename=dmesg_stable%2B3.0.8.txt;att=2;bug=641749

And here is a similar 3.0.x Debian mainline kernel running on top of
Debian testing (wheezy):

http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=56;filename=dmesg_testing%2B3.0.0-2.txt;att=1;bug=641749

If you browse the Debian bug report link listed at the beginning of
this email, you will also be able to get logs for kernel 3.1.x.
Furthermore, I've tested downgrading the version of udev to the one
found in Debian squeeze (version 164) as well as usb-modeswitch (also
tried upgrading to the latest versions in Debian unstable), but this
has yielded no progress and no clues at all...the error messages
remain the same.

Help debugging this issue would be most welcome.

Best Regards

Andres Cimmarusti

PS: For reference this is a Linux Certified laptop model LC2131, also
known as the Zareason Strata Pro 13 or the ASI SpringPeak 13



-- 
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/CAH=dyrhhttmrjkvuo9qvj5_uqd+bjgcjjkamw8153rw1sfv...@mail.gmail.com

Processed: tagging 653423

[Debian Bug Tracking System]

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

> tags 653423 + pending
Bug #653423 [linux-2.6] linux-image-3.1.0-1-amd64: 3.1.5 kernel breaks iwlagn 
compatibility with 802.11n wifi access points
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
653423: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653423
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.132508925525690.transcr...@bugs.debian.org

Bug#652459: initramfs-tools: [patch] Please support mounting of /usr in the initramfs

[Roger Leigh]

On Sun, Dec 18, 2011 at 03:38:20AM +0100, Marco d'Itri wrote:
> On Dec 17, Roger Leigh  wrote:
> 
> > 1) Generation of /etc/fstab in the initramfs, including the rootfs
> >and all the filesystems desired to be mounted
> This is highly suboptimal, because it suddenly makes the initramfs not
> generic anymore.
> The initramfs should:
> - mount / as usual
> - look at the rootfs fstab
> - mount /usr using the information from the rootfs fstab

The attached patch does this.

Note that the patch isn't complete; it won't mount an LVM VG because
it lacks the LV activation performed for the root in
"scripts/local-top/lvm2".  I haven't included this in the patch
because I'm not sure of the best approach to take here.

Maybe it would make sense to make the existing scripts a bit more
generic, to permit setup of devices other than $ROOT?  Maybe if the
scripts were idempotent, they could be invoked multiple times (once
per device)?

I didn't want to do this without discussing it with you, so hope the
patch is useful as a basis for a complete solution.

Regarding mounting of /etc; I think this would be useful in a number
of uncommon situations.  I'll look at (separately) implementing an
--etc/etc= option similar to the existing root options which would
permit this to work, and keep the initramfs generic at the same time.
As for /usr above, having the ability to generically activate devices
other than $ROOT would also be useful here.


Regards,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux http://people.debian.org/~rleigh/
 `. `'   Printing on GNU/Linux?   http://gutenprint.sourceforge.net/
   `-GPG Public Key: 0x25BFB848   Please GPG sign your mail.
>From 02574bd223ac21ad18e5c4fa801766e7eaa7c00a Mon Sep 17 00:00:00 2001
From: Roger Leigh 
Date: Sat, 17 Dec 2011 11:47:59 +
Subject: [PATCH] scripts/local: Add parse_initramfs_fstab function and mount
 /usr

This parses /etc/fstab and /etc/fstab.d/*.fstab on the rootfs,
in order to obtain the mount information for /usr (if available).
If an entry for /usr exists, mount /usr immediately after mounting
the rootfs.
---
 scripts/local |   51 +++
 1 files changed, 51 insertions(+), 0 deletions(-)

diff --git a/scripts/local b/scripts/local
index 521e69a..fc70c02 100644
--- a/scripts/local
+++ b/scripts/local
@@ -1,5 +1,54 @@
 # Local filesystem mounting			-*- shell-script -*-
 
+# Find a specific fstab entry from the mounted rootfs
+# $1=mountpoint
+# $2=fstype (optional)
+# returns 0 on success, 1 on failure (not found or no fstab)
+parse_initramfs_fstab () {
+	local found
+	found=1
+	for file in ${rootmnt}/etc/fstab ${rootmnt}/etc/fstab.d/*.fstab; do
+		if [ -f "${file}" ]; then
+			while read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+			do
+case "${MNT_FSNAME}" in
+""|\#*)
+	continue;;
+esac
+
+if [ "$MNT_DIR" = "$1" ]; then
+	if [ -n "$2" ]; then
+		[ "$MNT_TYPE" = "$2" ] || continue;
+	fi
+	found=0;
+	break 2
+fi
+
+		done < "${file}"
+	fi
+	done
+	return $found
+}
+
+# /usr mounting
+mountusr()
+{
+	if parse_initramfs_fstab /usr; then
+		if [ "${readonly}" = "y" ]; then
+			roflag=-r
+		else
+			roflag=-w
+		fi
+
+		# FIXME This has no error checking
+		modprobe ${MNT_TYPE}
+
+		# FIXME This has no error checking
+		# Mount /usr
+		mount ${roflag} -t "${MNT_TYPE}" -o "${MNT_OPTS}" "${MNT_FSNAME}" "${rootmnt}${MNT_DIR}"
+	fi
+}
+
 pre_mountroot()
 {
 	[ "$quiet" != "y" ] && log_begin_msg "Running /scripts/local-top"
@@ -106,6 +155,8 @@ mountroot()
 		mount ${roflag} ${ROOTFLAGS} ${ROOT} ${rootmnt}
 	fi
 
+	mountusr
+
 	[ "$quiet" != "y" ] && log_begin_msg "Running /scripts/local-bottom"
 	run_scripts /scripts/local-bottom
 	[ "$quiet" != "y" ] && log_end_msg
-- 
1.7.7.3

Bug#649890: linux-image-2.6-686: Kernel Oops during upgrade, X module FBCON not available after restart

[axst]

Thanks. I believe you are right. There used to be occasional kernel oopses but 
I have not
seen any kernel oops recently.

Is there anything else you would like me to look for that might help narrow 
down this bug?

Axel



--
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.1112281601040.402@localhost.localdomain

Bug#649540: ACPI failures on Dell Latitude E6220

[Gabriel Kerneis]

Juliusz,

On Wed, Dec 21, 2011 at 05:37:39PM +0100, Juliusz Chroboczek wrote:
> This issue appears to be worked around by
>   linux-image-3.1.0-1-amd64 3.1.5-1
> Note that it is *not* fixed by
>   linux-image-3.2.0-rc4-amd64 3.2~rc4-1~experimental.1

I agree that kernel 3.1.5 (and 3.1.6) does not exhibit the "method
parse/execution failed" ACPI error, whereas 3.2~rc4 does.

> In case you're interested in what's going on under the hood -- the
> kernel is now able to put the processor in one of the low-power
> "package" states.  Previously, the cores were able to switch to
> low-power states, but the package remained in PC0.
> 
>  cr CPU%c0  GHz  TSC%c1%c3%c6%c7  %pc2  %pc3  %pc6  %pc7
>1.03 0.80 2.49   5.21   0.01   0.00  93.74  1.22  0.00  2.07 84.59
>0   0   2.32 0.80 2.49   3.02   0.03   0.00  94.63  1.22  0.00  2.07 84.59
>0   2   1.05 0.80 2.49   4.28   0.03   0.00  94.64  1.22  0.00  2.07 84.59
>1   1   0.60 0.80 2.49   6.55   0.00   0.00  92.85  1.22  0.00  2.07 84.59
>1   3   0.14 0.80 2.49   7.01   0.00   0.00  92.85  1.22  0.00  2.07 84.59

But what seems to really make a difference is adding i915.i915_enable_rc6=1 to
GRUB_CMDLINE_LINUX in /etc/default/grub (and run update-grub), not using a
different kernel.  Despite the ACPI error, using this option with kernel 3.2
boosts battery life and turbostat shows the package reaching PC7 more than 90%
of the time.

In other words, I am not convinced this ACPI issue is related with the battery
life (but I must admit I do not understand a lot about power-saving stuff).

Best regards,
-- 
Gabriel



-- 
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/20111228144359.gc22...@kerneis.info

Bug#651199: iwlwifi: Connection lost on "WPA: Group rekeying"

[Gabriel Kerneis]

On Wed, Dec 28, 2011 at 03:01:25PM +0100, Ben Hutchings wrote:
> On Wed, 2011-12-28 at 10:32 +0100, Andreas Gustafsson wrote:
> > I think I was a bit fast to cheer.
> > 
> > There is still problems but seem to be not as frequent.
> > 
> > Sometimes the link gets unusable after:
> > Dec 28 10:23:15 neith NetworkManager[1503]:  (wlan0): supplicant
> > connection state:  completed -> group handshake
> > Dec 28 10:23:15 neith wpa_supplicant[1681]: WPA: Group rekeying
> > completed with 00:30:bd:9d:ad:6b [GTK=TKIP]
> > Dec 28 10:23:15 neith NetworkManager[1503]:  (wlan0): supplicant
> > connection state:  group handshake -> completed
> 
> I don't often use WPA, but that looks to me like successful rekeying.

This is the whole issue: rekeying is successful according to the logs but the
connection becomes "frozen"(unable to ping the AP, although the association is
reported to be correct).

I can confirm that 3.1.6 does not fix the issue for me.

Best,
-- 
Gabriel



-- 
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/20111228144721.gd22...@kerneis.info

Bug#651199: iwlwifi: Connection lost on "WPA: Group rekeying"

[Ben Hutchings]

On Wed, 2011-12-28 at 10:32 +0100, Andreas Gustafsson wrote:
> I think I was a bit fast to cheer.
> 
> There is still problems but seem to be not as frequent.
> 
> Sometimes the link gets unusable after:
> Dec 28 10:23:15 neith NetworkManager[1503]:  (wlan0): supplicant
> connection state:  completed -> group handshake
> Dec 28 10:23:15 neith wpa_supplicant[1681]: WPA: Group rekeying
> completed with 00:30:bd:9d:ad:6b [GTK=TKIP]
> Dec 28 10:23:15 neith NetworkManager[1503]:  (wlan0): supplicant
> connection state:  group handshake -> completed

I don't often use WPA, but that looks to me like successful rekeying.

Ben.

-- 
Ben Hutchings
Hoare's Law of Large Problems:
Inside every large problem is a small problem struggling to get out.


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

Bug#653445: linux-image-3.1.0-1-amd64: iwlagn.ko fails to connect to 802.11n access point

[S. G.]

Package: linux-2.6
Version: 3.1.5-1
Severity: important
Tags: upstream

Dear Maintainer,

since upgrading the kernel from 3.1.1 to 3.1.5 wireless-n connection
establishment is not completed in a way that results in a usable connection.

Incoming IP packages can be observed using Whireshark but outgoing packages
seems not to be recognized by the receiving party: the ap/router does not
answer the DHCP requests.

A wireless-g connection works flawlessly.

Downgrading to kernel 3.1.1 lets the wireless-n problem disappear.

I discovered bug descriptions on Archlinux and Redhat which seem do cover this
issue and claim to have a fix:
https://bugs.archlinux.org/task/27581
https://bugzilla.redhat.com/show_bug.cgi?id=767173

Looking  forward to see a fix on Wheezy soon.

Cheers,
Sven



-- Package-specific info:
** Version:
Linux version 3.1.0-1-amd64 (Debian 3.1.5-1) (b...@decadent.org.uk) (gcc 
version 4.6.2 (Debian 4.6.2-7) ) #1 SMP Sun Dec 11 20:36:41 UTC 2011

** Command line:
BOOT_IMAGE=/vmlinuz-3.1.0-1-amd64 root=/dev/mapper/t500sg-root ro quiet

** Tainted: O (4096)
 * Out-of-tree module has been loaded.

** Kernel log:
[   74.017756] iwlagn :03:00.0: Radio type=0x0-0x2-0x0
[   74.168474] iwlagn :03:00.0: L1 Disabled; Enabling L0S
[   74.168854] iwlagn :03:00.0: Radio type=0x0-0x2-0x0
[   74.216495] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   78.530484] Bluetooth: RFCOMM TTY layer initialized
[   78.530490] Bluetooth: RFCOMM socket layer initialized
[   78.530491] Bluetooth: RFCOMM ver 1.11
[   78.583002] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   78.583005] Bluetooth: BNEP filters: protocol multicast
[   79.704906] lp: driver loaded but no devices found
[   79.906853] ppdev: user-space parallel port driver
[   82.987171] wlan0: authenticate with bc:05:43:fc:10:bd (try 1)
[   82.989664] wlan0: authenticated
[   82.995681] wlan0: associate with bc:05:43:fc:10:bd (try 1)
[   82.998163] wlan0: RX AssocResp from bc:05:43:fc:10:bd (capab=0x431 status=0 
aid=1)
[   82.998168] wlan0: associated
[   83.003828] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   94.188009] wlan0: no IPv6 routers present
[  104.576247] AIF:Spoofed packet: IN=wlan0 OUT= MAC= SRC=192.168.42.1 
DST=192.168.0.31 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 
DPT=137 LEN=58 
[  106.578827] AIF:Spoofed packet: IN=wlan0 OUT= MAC= SRC=192.168.42.1 
DST=192.168.0.31 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 
DPT=137 LEN=58 
[  106.579020] AIF:Spoofed packet: IN=wlan0 OUT= MAC= SRC=192.168.42.1 
DST=192.168.0.31 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 
DPT=137 LEN=58 
[  107.908017] Disabling lock debugging due to kernel taint
[  107.917722] vboxdrv: Found 2 processor cores.
[  107.918122] vboxdrv: fAsync=0 offMin=0x18f offMax=0x8a2
[  107.918184] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 
'normal'.
[  107.918187] vboxdrv: Successfully loaded version 4.1.8 (interface 
0x0019).
[  108.581633] AIF:Spoofed packet: IN=wlan0 OUT= MAC= SRC=192.168.42.1 
DST=192.168.0.31 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 
DPT=137 LEN=58 
[  109.273460] vboxpci: IOMMU not found (not registered)
[  415.611744] AIF:Spoofed packet: IN=wlan0 OUT= MAC= SRC=192.168.42.1 
DST=192.168.0.31 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 
DPT=137 LEN=58 
[  417.614309] AIF:Spoofed packet: IN=wlan0 OUT= MAC= SRC=192.168.42.1 
DST=192.168.0.31 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 
DPT=137 LEN=58 
[  417.614479] AIF:Spoofed packet: IN=wlan0 OUT= MAC= SRC=192.168.42.1 
DST=192.168.0.31 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 
DPT=137 LEN=58 
[  419.616917] AIF:Spoofed packet: IN=wlan0 OUT= MAC= SRC=192.168.42.1 
DST=192.168.0.31 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 
DPT=137 LEN=58 
[  724.699283] AIF:Spoofed packet: IN=wlan0 OUT= MAC= SRC=192.168.42.1 
DST=192.168.0.31 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 
DPT=137 LEN=58 
[  726.702177] AIF:Spoofed packet: IN=wlan0 OUT= MAC= SRC=192.168.42.1 
DST=192.168.0.31 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 
DPT=137 LEN=58 
[  726.702349] AIF:Spoofed packet: IN=wlan0 OUT= MAC= SRC=192.168.42.1 
DST=192.168.0.31 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 
DPT=137 LEN=58 
[  728.704859] AIF:Spoofed packet: IN=wlan0 OUT= MAC= SRC=192.168.42.1 
DST=192.168.0.31 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=137 
DPT=137 LEN=58 
[  753.681938] wlan0: deauthenticating from bc:05:43:fc:10:bd by local choice 
(reason=3)
[  753.701691] cfg80211: Calling CRDA to update world regulatory domain
[  756.859007] wlan0: authenticate with bc:05:43:fc:10:b9 (try 1)
[  757.056066] wlan0: authenticate with bc:05:43:fc:10:b9 (try 2)
[  757.057711] wlan0: authenticated
[  757.064163] wlan0: associate with bc:05:43:fc:10:b9 (try 1)
[  757.264072] wlan0: associate with bc:05:43:fc:10:b9 (try 2)
[  757.281243] 

Bug#653179: [rt2x00-users] Fwd: linux-image-3.1.0-1-amd64: Can't switch off WoW option of RT5390 wi-fi card, notebook wakes on wi-fi activity

[Gertjan van Wingerde]

On 12/28/11 08:56, Helmut Schaa wrote:
> Hi,
> 
> Am Sonntag, 25. Dezember 2011, 09:07:42 schrieb pol kh:
>> I'd like to be able to manage WoW option on Ralink 5390 on my HP Pavilion
>> dv6-6030er. WoW is enabled by default in BIOS, which is locked by vendor.
>> So I can't switch it off. Using ethtool doesn't help, because driver can't
>> hanlder with WoW. My notebook wakes on wi-fi activity when I'd like it to
>> be asleep. I had sent a bug report to Debian GNU/Linux maintainers and got
>> the following answer (below my bug report is attached):
> 
> this sounds really strange :). Unfortunately nobody is working on WoW support
> for rt2x00 currently.
> 
> Ivo, Gertjan, do we have any information yet how WoW for the ralink devices
> is supposed to work? Since the WoW framework was already merged AFAIK it might
> be a trivial thing to add ...

No, I've never seen any information about this.

A quick look at the Ralink legacy drivers also reveal that these do not
contain any code for this, so it will be difficult to add support for
this in rt2x00.

---
Gertjan



-- 
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/4efaf8e7.5080...@gmail.com

Processed: Re: Bug#653292: nfs exclusive lock does not work anymore after openvz kernel version : 2.6.32-35squeeze1

[Debian Bug Tracking System]

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

> forwarded 653292 http://bugzilla.openvz.org/show_bug.cgi?id=2122
Bug #653292 [linux-2.6] nfs exclusive lock does not work anymore after openvz 
kernel version : 2.6.32-35squeeze1
Set Bug forwarded-to-address to 
'http://bugzilla.openvz.org/show_bug.cgi?id=2122'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
653292: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653292
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.132506878826199.transcr...@bugs.debian.org

Processed: Re: Bug#652708: linux-image-2.6-openvz-amd64: Cannot mount Windows share

[Debian Bug Tracking System]

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

> forwarded 652708 http://bugzilla.openvz.org/show_bug.cgi?id=2121
Bug #652708 [linux-2.6] linux-image-2.6-openvz-amd64: Cannot mount Windows share
Set Bug forwarded-to-address to 
'http://bugzilla.openvz.org/show_bug.cgi?id=2121'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
652708: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652708
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.132506855925440.transcr...@bugs.debian.org

Bug#652708: linux-image-2.6-openvz-amd64: Cannot mount Windows share

[Ola Lundqvist]

forwarded 652708 http://bugzilla.openvz.org/show_bug.cgi?id=2121
thanks

Hi

Bug filed upstream.
http://bugzilla.openvz.org/show_bug.cgi?id=2121

Best regards,

// Ola

On Tue, Dec 20, 2011 at 09:23:09AM +0100, Martin Sin wrote:
> Package: linux-image-2.6-openvz-amd64
> Version: 2.6.32+29
> Severity: important
> 
> Hi,
> it isn't possible to mount Windows share on this kernel, for example:
> 
> sudo mount -t cifs ...
> 
> return this error message:
> 
> mount error(1): Operation not permitted
> 
> Best regards,
> Martin Sin.
> 
> -- System Information:
> Debian Release: 6.0.3
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 2.6.32-5-openvz-amd64 (SMP w/8 CPU cores)
> Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> 
> Versions of packages linux-image-2.6-openvz-amd64 depends on:
> ii  linux-image-2.6.32-5-openvz-a 2.6.32-39  Linux 2.6.32 for 64-bit PCs, 
> OpenV
> 
> linux-image-2.6-openvz-amd64 recommends no packages.
> 
> linux-image-2.6-openvz-amd64 suggests no packages.
> 
> -- 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/20111220082309.10109.84973.report...@alfabetix.zshk.cz
> 
> 

-- 
 - Ola Lundqvist ---
/  o...@debian.org Annebergsslingan 37  \
|  o...@inguza.com  654 65 KARLSTAD  |
|  http://inguza.com/  +46 (0)70-332 1551   |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36  4FE4 18A1 B1CF 0FE5 3DD9 /
 ---



-- 
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/20111228103549.ga11...@inguza.net

Bug#651199: iwlwifi: Connection lost on "WPA: Group rekeying"

[Andreas Gustafsson]

I think I was a bit fast to cheer.

There is still problems but seem to be not as frequent.

Sometimes the link gets unusable after:
Dec 28 10:23:15 neith NetworkManager[1503]:  (wlan0): supplicant
connection state:  completed -> group handshake
Dec 28 10:23:15 neith wpa_supplicant[1681]: WPA: Group rekeying
completed with 00:30:bd:9d:ad:6b [GTK=TKIP]
Dec 28 10:23:15 neith NetworkManager[1503]:  (wlan0): supplicant
connection state:  group handshake -> completed

Best regards,
Andreas

tis 2011-12-27 klockan 12:02 +0100 skrev Andreas Gustafsson:
> Version: 3.1.5-1 fixes this for me.
> 
> Best regards,
> Andreas
> 
> fre 2011-12-16 klockan 12:57 +0100 skrev Gabriel Kerneis:
> > Hi,
> > 
> > On Fri, Dec 16, 2011 at 03:17:30AM -0600, Jonathan Nieder wrote:
> > > There have been a few iwlwifi fixes upstream recently.  Could you
> > > try[1] v3.2-rc5 or later?
> > 
> > I did not test 3.2 yet but for people looking for a workaround until a fix 
> > is
> > available, the following seems to work for me (found on openSUSE's bug 
> > report):
> > $ echo options iwlagn swcrypto=1 > /etc/modprobe.d/iwlagn
> > 
> > Best,
> 





-- 
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/1325064723.2199.2.ca...@neith.impressions.se

Bug#653179: [rt2x00-users] Fwd: linux-image-3.1.0-1-amd64: Can't switch off WoW option of RT5390 wi-fi card, notebook wakes on wi-fi activity

[Helmut Schaa]

Hi,

Am Sonntag, 25. Dezember 2011, 09:07:42 schrieb pol kh:
> I'd like to be able to manage WoW option on Ralink 5390 on my HP Pavilion
> dv6-6030er. WoW is enabled by default in BIOS, which is locked by vendor.
> So I can't switch it off. Using ethtool doesn't help, because driver can't
> hanlder with WoW. My notebook wakes on wi-fi activity when I'd like it to
> be asleep. I had sent a bug report to Debian GNU/Linux maintainers and got
> the following answer (below my bug report is attached):

this sounds really strange :). Unfortunately nobody is working on WoW support
for rt2x00 currently.

Ivo, Gertjan, do we have any information yet how WoW for the ralink devices
is supposed to work? Since the WoW framework was already merged AFAIK it might
be a trivial thing to add ...

Helmut



-- 
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/189297114.zdgghwx...@helmutmobil.site