Bug#613909: Suggests grub instead of grub-pc

[Eugen Dedu]

Package: linux-image-2.6.37-1-amd64
Version: 2.6.37-1
Severity: minor

This package suggests grub instead of grub-pc.

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



--
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/4d5e2b59.8080...@pu-pm.univ-fcomte.fr

Re: does squeeze have these fixes?

[Aleksandar Kostadinov]

On Wed, Feb 16, 2011 at 2:19 PM, Ben Hutchings  wrote:
> On Wed, 2011-02-16 at 09:09 +0200, Aleksandar Kostadinov wrote:
>> https://bugzilla.kernel.org/show_bug.cgi?id=19462
>>
>> I'm seeing similar errors on my acer notebook like in the bugzilla
>> above. Could anybody confirm if squeeze has these fixes already
>> backported?
>
> This fix was included in the 'longterm' 2.6.32.28 release and our
> version 2.6.32-30.

Thank you for the information. The bug must be something else then.  I
have compiled 2.6.37 from sid and I can't make it crash for a few
hours. With the stock squeeze kernel it crashes soon after
hibernate-ram/restore. I'm attaching a kerneloops.log
Interesting is that everytime I've seen this it says:
last sysfs file:
/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:2a/PNP0C0A:00/power_supply/BAT1/charge_full

With lenny kernel I don't experience crashes but see ACPI errors in
the log. I've never looked at them though because everything was
functioning fine.
Also with 2.6.37 I see the following in the dmesg output which I think
might be related:
[0.166935] ACPI: EC: Look up EC in DSDT
[0.175530] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored

Do you think this bug can be fixed in squeeze or should I plan for
compiling upstream kernels for the time being?

Thank you again,
Aleksandar
Kernel failure message 1:
BUG: unable to handle kernel paging request at f72f7900
IP: [] ext3_iget+0x65/0x355 [ext3]
*pde = 7067 *pte = 6c00 
Oops:  [#1] SMP 
last sysfs file: 
/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:2a/PNP0C0A:00/power_supply/BAT1/charge_full
Modules linked in: nls_utf8 nls_cp437 vfat fat snd_seq_dummy usb_storage tun 
kvm ipt_REJECT xt_state xt_owner iptable_filter ipt_MASQUERADE xt_comment 
xt_tcpudp iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 
ip_tables x_tables acpi_cpufreq cpufreq_powersave cpufreq_conservative 
cpufreq_stats cpufreq_userspace parport_pc ppdev lp parport uinput microcode 
ext2 sha256_generic aes_i586 aes_generic cbc fuse loop dm_crypt 
snd_hda_codec_realtek arc4 snd_hda_intel ecb snd_hda_codec snd_usb_audio 
snd_usb_lib snd_hwdep snd_seq_midi snd_rawmidi i915 snd_pcm_oss 
snd_seq_midi_event drm_kms_helper snd_mixer_oss snd_seq snd_seq_device joydev 
snd_pcm ath drm snd_timer i2c_i801 yenta_socket snd i2c_algo_bit rsrc_nonstatic 
acer_wmi psmouse cfg80211 serio_raw evdev video wmi pcspkr ac i2c_core 
container button rng_core battery output soundcore processor rfkill 
snd_page_alloc ext3 jbd mbcache dm_mod usbhid hid sg sr_mod sd_mod cdrom 
crc_t10dif ata_generic b44 sdhci_pci ssb ata_piix sdhci pcmcia thermal libata 
uhci_hcd mmc_core led_class pcmcia_core mii thermal_sys ehci_hcd scsi_mod 
usbcore nls_base [last unloaded: mac80211]

Pid: 22409, comm: find Not tainted (2.6.32-5-686 #1) Aspire 5610Z
EIP: 0060:[] EFLAGS: 00010286 CPU: 0
EIP is at ext3_iget+0x65/0x355 [ext3]
EAX: f297d8c0 EBX: eef9d69c ECX: f2dc1e20 EDX: 
ESI: f72f7900 EDI: eef9d600 EBP: f651d400 ESP: f2dc1e1c
 DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Process find (pid: 22409, ti=f2dc task=ee448880 task.ti=f2dc)
Stack:
 f297d8c0 f297d8c0 0900 0005 a98a f2b65880 f6ab829c f2dc1ed4
<0> f80dab03 c2af3170 f80e32cc f2b65880 f6ab829c c10b9889 f2dc1e8c f2dc1e80
<0> f6fafb80 f6ab8314 f2dc1ed4 f660a000 f6ab829c f660a011 c10ba0f8 ee448880
Call Trace:
 [] ? ext3_lookup+0x66/0xae [ext3]
 [] ? do_lookup+0xa6/0x116
 [] ? __link_path_walk+0x4b7/0x5de
 [] ? path_walk+0x4f/0xa3
 [] ? do_path_lookup+0x1f/0x69
 [] ? user_path_at+0x37/0x5f
 [] ? cp_new_stat64+0xf7/0x109
 [] ? vfs_fstatat+0x2a/0x50
 [] ? sys_fstatat64+0x19/0x2e
 [] ? sysenter_do_call+0x12/0x28
Code: ff 31 c9 c7 47 54 00 00 00 00 8d 54 24 04 e8 57 fd ff ff 85 c0 89 c6 0f 
88 d8 02 00 00 8b 44 24 04 89 04 24 8b 70 18 03 74 24 08 <8b> 06 66 89 43 72 0f 
b7 46 02 89 43 2c 0f b7 46 18 89 43 30 8b 
EIP: [] ext3_iget+0x65/0x355 [ext3] SS:ESP 0068:f2dc1e1c
CR2: f72f7900
---[ end trace cf9981a5c294985d ]---

Bug#605090: Updated patch

[Yves-Alexis Perez]

On lun., 2011-02-14 at 13:25 +0100, Bastian Blank wrote:
> On Mon, Feb 14, 2011 at 11:02:53AM +0100, Yves-Alexis Perez wrote:
> > On jeu., 2011-02-10 at 10:51 +0100, Bastian Blank wrote:
> > > Please start with it. I don't want random code drops _right_ _now_.
> > Well, I've started to setup a git tree, but it's a bit hard to make the
> > kernel package git transition myself.
> 
> I thought about using something derived from the stable tree. You need
> it to do proper patch imports anyway.

I already use the (upstream) stable tree, but that doesn't give me the
Debian patches applied, which is what really matters here.
> 
> > >   - Arbitrary fixes must go to mainline.
> > “arbitrary fixes” are picked up from mainline, which is why I remove
> > them from the patch since they're already backported into Debian.
> 
> No. I meant the "arbitrary" fixes like the const-ness changes.

Those are not arbitraty fixes, the const make sense if the rodata part
is really enforced. This is the kind of thing which is upstreamable
(though DEBUG_RODATA only does part of the job KERNEXEC does) but that
doesn't mean we shouldn't have them now.

Regards,
-- 
Yves-Alexis Perez
ANSSI/ACE/LAM


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

Bug#613501: Workaround available in openvz git

[maximilian attems]

On Fri, Feb 18, 2011 at 07:27:27AM +0100, Ola Lundqvist wrote:
> Hi Maks
> 
> Do you know when the next squeeze upload would be? Is it for the next
> point release (and if so, do you know when that is?) or should we try
> to convince the security team that this is actually a security issue.
> 
> Data corruption is not a nice thing I would say...
> 
> // Ola

why do you toppost, it is missing all relevant info!?
 
> On Thu, Feb 17, 2011 at 07:18:11PM +0100, maximilian attems wrote:
> > On Thu, 17 Feb 2011, Vladimir Kuklin wrote:
> > 
> > > 
> > > git commit is here:
> > > 
> > > http://git.openvz.org/?p=linux-2.6.32-openvz;a=commit;h=3e89668abca56e6e11e1bbb9cbac1008d3c2357b
> > > 
> > > Please, don't forward it again to openvz devs. Just include it into
> > > patchset for 2.6.32-5-openvz kernel update.
> > 
> > it is included, add info to changelog so it will be closed on next
> > squeeze upload.

upload is planed after next stable release, most probably monday.





-- 
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/20110218094644.gq5...@vostochny.stro.at

Processed: tagging 613909

[Debian Bug Tracking System]

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

> # Automatically generated email from bts, devscripts version 2.10.35lenny7
> tags 613909 + pending
Bug #613909 [linux-image-2.6.37-1-amd64] Suggests grub instead of grub-pc
Added tag(s) pending.
>
End of message, stopping processing here.

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

Re: Bug#613845: base: Speaker doesn't work but headphones works well. Laptop HP G62.

[Holger Levsen]

severity 613845 normal
reassign 613845 linux-2.6
tags 613845 + moreinfo
thanks

Hi Andrii,

please send you full dmesg output to 613845@bugs.d.o and give 2.6.37 from 
unstable a try and report back as well. Thanks.


cheers,
Holger

On Donnerstag, 17. Februar 2011, Andrii Grytsenko wrote:
> Package: base
> Severity: important
> Tags: squeeze
>
>
>
> -- System Information:
> Debian Release: 6.0
>   APT prefers squeeze-updates
>   APT policy: (500, 'squeeze-updates'), (500, 'stable')
> Architecture: i386 (i686)
>
> Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
>
> I can't make my audio system works properly on my HP G62 laptop. I can hear
> the sound only in my headphone, and my speaker and microphone don't work at
> all.
>
> Here some information:
>
> # cat /proc/asound/card0/codec#* | grep Codec
> Codec: Realtek ID 270
> Codec: Intel G45 DEVIBX
>
> # aplay -l output:
>  List of PLAYBACK Hardware Devices 
> card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic]
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
> card 0: Intel [HDA Intel], device 3: INTEL HDMI [INTEL HDMI]
>   Subdevices: 1/1
>   Subdevice #0: subdevice #0
>
> # lspci | grep -i audio
> 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High
> Definition Audio (rev 05)
>
> Alsa information:
> # dpkg -l | grep alsa
> ii  alsa-base1.0.23+dfsg-2
> ALSA driver configuration files ii  alsa-utils  
> 1.0.23-3  Utilities for configuring and using ALSA
> ii  bluez-alsa   4.66-3   
> Bluetooth ALSA support ii  libsdl1.2debian-alsa 1.2.14-6.1 
>   Simple DirectMedia Layer (with X11 and ALSA options)
>
>
> Try to emulate such behave in console (without X). Run mpg123 and got the
> same stuff - can only hear sound through headphones.
>
> My /etc/modprobe.d/alsa-base.conf looks like:
> # autoloader aliases
> install sound-slot-0 /sbin/modprobe snd-card-0
> install sound-slot-1 /sbin/modprobe snd-card-1
> install sound-slot-2 /sbin/modprobe snd-card-2
> install sound-slot-3 /sbin/modprobe snd-card-3
> install sound-slot-4 /sbin/modprobe snd-card-4
> install sound-slot-5 /sbin/modprobe snd-card-5
> install sound-slot-6 /sbin/modprobe snd-card-6
> install sound-slot-7 /sbin/modprobe snd-card-7
> # Cause optional modules to be loaded above generic modules
> install snd /sbin/modprobe --ignore-install snd && { /sbin/modprobe --quiet
> snd-ioctl32 ; /sbin/modprobe --quiet snd-seq ; } install snd-rawmidi
> /sbin/modprobe --ignore-install snd-rawmidi && { /sbin/modprobe --quiet
> snd-seq-midi ; : ; } install snd-emu10k1 /sbin/modprobe --ignore-install
> snd-emu10k1 && { /sbin/modprobe --quiet snd-emu10k1-synth ; : ; }
>
> # Prevent abnormal drivers from grabbing index 0
> options bt87x index=-2
> options cx88_alsa index=-2
> options snd-atiixp-modem index=-2
> options snd-intel8x0m index=-2
> options snd-via82xx-modem index=-2
> # Keep snd-pcsp from beeing loaded as first soundcard
> options snd-pcsp index=-2
> # Keep snd-usb-audio from beeing loaded as first soundcard
> options snd-usb-audio index=-2
>
>
> Appended to config next line:
> options snd-hda-intel model=basic
>
> then change it to
> options snd-hda-intel model=hp
>
> And even try to comment out:
> options snd-intel8x0m index=-2
>
> After any changes reboot the system or run alsa force-reload. But nothing
> help me.
>
> Also tried to delete pulseaudio:
> apt-get purge pulseaudio
>
> But this step was unsuccessful too.




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

Bug#613922: linux: Radeon DRM doesn't initialise properly (firmware fails to load?)

[Owen Riddy]

Package: linux-2.6
Version: 2.6.37-1
Severity: important
File: linux


I have a Radeon 3450 grampics card (AMD/ATI) and lived on Squeeze until the 
recent release. The card was well supported by the new Open Source graphics 
driver (radeon).
Whenever I compiled a newer vanilla kernel KMS didn't work (starting with 
2.6.33, I belive. It was a while ago) and X wouldn't load. Every so often I 
tried a different kernel, and the problem remained. On X, the system would 
completely hang (including access to virtual terminals). I assumed a 
mis-configured kernel and gave up.

This debian kernel image seems to have the same problem. After upgrading, I get 
a suspicious 180 second pause when the kernel "populates /dev", which I now 
attribute to a bug, possibly in the firmware loading code. I'm getting an error 
message about modprobe blocking (in dmesg).

To be sure I havn't tainted the configuration, I installed the Squeeze release 
base system, upgraded to wheezy, rebooted to test KMS (virtual terminal screen 
resolution was large, suggesting it worked), upgraded to unstable and rebooed, 
at which point I get the 180 second hang and modrpboe errors, as well as a 
rather low resolution VT.

This renders X unusable. Does this report go here, or upstream?

-- Package-specific info:
** Version:
Linux version 2.6.37-1-686 (Debian 2.6.37-1) (b...@decadent.org.uk) (gcc 
version 4.4.5 (Debian 4.4.5-10) ) #1 SMP Tue Feb 15 18:21:50 UTC 2011

** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.37-1-686 
root=/dev/mapper/cyclone--rootspace-squeeze ro quiet

** Not tainted

** Kernel log:
[  240.684226]  [] ? mutex_lock+0x17/0x24
[  240.684228]  [] ? mutex_lock+0x17/0x24
[  240.684232]  [] ? __driver_attach+0x27/0x5b
[  240.684235]  [] ? bus_for_each_dev+0x37/0x5f
[  240.684238]  [] ? driver_attach+0x11/0x13
[  240.684241]  [] ? __driver_attach+0x0/0x5b
[  240.684243]  [] ? bus_add_driver+0x87/0x1bb
[  240.684246]  [] ? kset_find_obj_hinted+0x43/0x7d
[  240.684250]  [] ? alsa_card_azx_init+0x0/0x14 [snd_hda_intel]
[  240.684253]  [] ? driver_register+0x7a/0xd9
[  240.684258]  [] ? alsa_card_azx_init+0x0/0x14 [snd_hda_intel]
[  240.684262]  [] ? __pci_register_driver+0x33/0x89
[  240.684266]  [] ? alsa_card_azx_init+0x0/0x14 [snd_hda_intel]
[  240.684269]  [] ? do_one_initcall+0x68/0x10f
[  240.684272]  [] ? sys_init_module+0xca5/0xe36
[  240.684285]  [] ? sysenter_do_call+0x12/0x28
[  360.684027] INFO: task modprobe:699 blocked for more than 120 seconds.
[  360.684096] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  360.684185] modprobe  D f455bcc0 0   699  1 0x
[  360.684189]  f719f1c0 0082 f715fb70 f455bcc0   f715fb70 
c1444200
[  360.684193]  f719f360 c1444200 33bc2000 0001 f719f360 f719f364 c1444200 
f719f1c0
[  360.684198]  c1444200 f454f124 f90883fc 0180 10ec0888 f4d3f060 f71e0800 
f44fa000
[  360.684202] Call Trace:
[  360.684212]  [] ? azx_probe+0x900/0x934 [snd_hda_intel]
[  360.684217]  [] ? azx_send_cmd+0x0/0x126 [snd_hda_intel]
[  360.684222]  [] ? azx_get_response+0x0/0x202 [snd_hda_intel]
[  360.684227]  [] ? __mutex_lock_common+0xe9/0x13a
[  360.684230]  [] ? __mutex_lock_slowpath+0xf/0x11
[  360.684233]  [] ? mutex_lock+0x17/0x24
[  360.684235]  [] ? mutex_lock+0x17/0x24
[  360.684239]  [] ? __driver_attach+0x27/0x5b
[  360.684242]  [] ? bus_for_each_dev+0x37/0x5f
[  360.684244]  [] ? driver_attach+0x11/0x13
[  360.684247]  [] ? __driver_attach+0x0/0x5b
[  360.684249]  [] ? bus_add_driver+0x87/0x1bb
[  360.684253]  [] ? kset_find_obj_hinted+0x43/0x7d
[  360.684257]  [] ? alsa_card_azx_init+0x0/0x14 [snd_hda_intel]
[  360.684260]  [] ? driver_register+0x7a/0xd9
[  360.684264]  [] ? alsa_card_azx_init+0x0/0x14 [snd_hda_intel]
[  360.684268]  [] ? __pci_register_driver+0x33/0x89
[  360.684272]  [] ? alsa_card_azx_init+0x0/0x14 [snd_hda_intel]
[  360.684275]  [] ? do_one_initcall+0x68/0x10f
[  360.684278]  [] ? sys_init_module+0xca5/0xe36
[  360.684292]  [] ? sysenter_do_call+0x12/0x28
[  480.684020] INFO: task modprobe:699 blocked for more than 120 seconds.
[  480.684110] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  480.684199] modprobe  D f455bcc0 0   699  1 0x
[  480.684203]  f719f1c0 0082 f715fb70 f455bcc0   f715fb70 
c1444200
[  480.684207]  f719f360 c1444200 33bc2000 0001 f719f360 f719f364 c1444200 
f719f1c0
[  480.684211]  c1444200 f454f124 f90883fc 0180 10ec0888 f4d3f060 f71e0800 
f44fa000
[  480.684216] Call Trace:
[  480.684226]  [] ? azx_probe+0x900/0x934 [snd_hda_intel]
[  480.684231]  [] ? azx_send_cmd+0x0/0x126 [snd_hda_intel]
[  480.684236]  [] ? azx_get_response+0x0/0x202 [snd_hda_intel]
[  480.684241]  [] ? __mutex_lock_common+0xe9/0x13a
[  480.684244]  [] ? __mutex_lock_slowpath+0xf/0x11
[  480.684247]  [] ? mutex_lock+0x17/0x24
[  480.684249]  [] ? mutex_lock+0x17/0x24
[  480.684253]  [] ? __driver_attach+0x27/0x5b
[  480.684256]  [] ? bus_for

Processed: Re: Bug#613845: base: Speaker doesn't work but headphones works well. Laptop HP G62.

[Debian Bug Tracking System]

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

> severity 613845 normal
Bug #613845 [base] base: Speaker doesn't work but headphones works well. Laptop 
HP G62.
Severity set to 'normal' from 'important'

> reassign 613845 linux-2.6
Bug #613845 [base] base: Speaker doesn't work but headphones works well. Laptop 
HP G62.
Bug reassigned from package 'base' to 'linux-2.6'.
> tags 613845 + moreinfo
Bug #613845 [linux-2.6] base: Speaker doesn't work but headphones works well. 
Laptop HP G62.
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#613925: [linux-2.6] Reiserfs hung with data loss with 2.6.36/2.6.37 regresse from 2.6.33

[Bastien ROUCARIES]

Package: linux-2.6
Severity: grave
tags: upstream
forwarded: https://lkml.org/lkml/2011/2/16/249

i suffer since three month of severe crash with data loss (reiserfschk  
--rebuild-tree is often needed and moreover twice I need to 
restore from backup).

I have reported to upstream and Rafael J. Wysocki advices to report under my 
distribution bugzilla.

The upstream report has some trace on it, but his busy and could not help.

Thank you

Bastien




--- System information. ---
Architecture: amd64
Kernel:   Linux 2.6.37-trunk-amd64

Debian Release: wheezy/sid
  550 testing ftp.fr.debian.org 
  500 unstableftp.fr.debian.org 
1 experimentalftp.fr.debian.org 

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.






-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/201102181130.24414.roucaries.bastien+deb...@gmail.com

Processed: Re: Bug#613790: pm-utils: eeepc 1005 PE recently stopped resuming from hibernate

[Debian Bug Tracking System]

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

> severity 611750 important
Bug #611750 [linux-image-2.6.32-5-686] Asus EeePC resume from hibernation fails
Severity set to 'important' from 'normal'

> forcemerge 611750 613790
Bug#611750: Asus EeePC resume from hibernation fails
Bug#613790: pm-utils: eeepc 1005 PE recently stopped resuming from hibernate
Forcibly Merged 611750 613790.

> thanks
Stopping processing here.

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

Re: Bug#613790: pm-utils: eeepc 1005 PE recently stopped resuming from hibernate

[Michael Biebl]

severity 611750 important
forcemerge 611750 613790
thanks

Am 18.02.2011 12:01, schrieb Paolo Casaschi:
> Looks like the same as http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611750
> It also affected my netbook, not an eeepc, but using intel i915 also.
> 
> Workaround: downgrade kernel to linux-image-2.6.32-5-686_2.6.32-29_i386
> You can find it here: http://snapshot.debian.org

Thanks for the feedback. I've merged the bug report and bumped the severity to
important due to the high number of users confirming it.

I hope someone from the kernel team finds some time to look into this.

Regards,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Processed: severity of 613925 is important

[Debian Bug Tracking System]

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

> # maybe even normal :P
> severity 613925 important
Bug #613925 [linux-2.6] [linux-2.6] Reiserfs hung with data loss with 
2.6.36/2.6.37 regresse from 2.6.33
Severity set to 'important' from 'grave'

> thanks
Stopping processing here.

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

Bug#613845: base: Speaker doesn't work but headphones works well. Laptop HP G62.

[Andrii Grytsenko]

There is some additional information I just find out that only speaker works
fine. I plugged my headphones in and speaker was keeping working like
nothing changed. So after kernel upgrading speaker and headphones switched
over. And as result now I have worked speaker and non-worked headphones.

Bug#613922: linux: Radeon DRM doesn't initialise properly (firmware fails to load?)

[maximilian attems]

On Fri, Feb 18, 2011 at 09:23:22PM +1100, Owen Riddy wrote:
> Package: linux-2.6
> Version: 2.6.37-1
> Severity: important
> File: linux
> 
> 
> I have a Radeon 3450 grampics card (AMD/ATI) and lived on Squeeze until the 
> recent release. The card was well supported by the new Open Source graphics 
> driver (radeon).
> Whenever I compiled a newer vanilla kernel KMS didn't work (starting with 
> 2.6.33, I belive. It was a while ago) and X wouldn't load. Every so often I 
> tried a different kernel, and the problem remained. On X, the system would 
> completely hang (including access to virtual terminals). I assumed a 
> mis-configured kernel and gave up.
> 
> This debian kernel image seems to have the same problem. After upgrading, I 
> get a suspicious 180 second pause when the kernel "populates /dev", which I 
> now attribute to a bug, possibly in the firmware loading code. I'm getting an 
> error message about modprobe blocking (in dmesg).
> 
> To be sure I havn't tainted the configuration, I installed the Squeeze 
> release base system, upgraded to wheezy, rebooted to test KMS (virtual 
> terminal screen resolution was large, suggesting it worked), upgraded to 
> unstable and rebooed, at which point I get the 180 second hang and modrpboe 
> errors, as well as a rather low resolution VT.
> 
> This renders X unusable. Does this report go here, or upstream?
> 

please report upstream on http://bugzilla.freedesktop.org/
and let us know the bug nr for tracking progress.

thank you.

-- 
maks



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110218113033.ga3...@vostochny.stro.at

Processed: tagging 613845, found 613845 in 2.6.32-30

[Debian Bug Tracking System]

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

> tags 613845 - squeeze
Bug #613845 [linux-2.6] base: Speaker doesn't work but headphones works well. 
Laptop HP G62.
Removed tag(s) squeeze.
> found 613845 2.6.32-30
Bug #613845 [linux-2.6] base: Speaker doesn't work but headphones works well. 
Laptop HP G62.
There is no source info for the package 'linux-2.6' at version '2.6.32-30' with 
architecture ''
Unable to make a source version for version '2.6.32-30'
Bug Marked as found in versions 2.6.32-30.
> thanks
Stopping processing here.

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

Re: Re: Bug#613790: pm-utils: eeepc 1005 PE recently stopped resuming from hibernate

[Paolo Casaschi]

Looks like the same as http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611750
It also affected my netbook, not an eeepc, but using intel i915 also.

Workaround: downgrade kernel to linux-image-2.6.32-5-686_2.6.32-29_i386
You can find it here: http://snapshot.debian.org

--
Paolo


-- 
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/AANLkTi=hqjnnnyuu0govt2vdvvb9mwt7gej-nt6xt...@mail.gmail.com

Bug#613925: [linux-2.6] Reiserfs hung with data loss with 2.6.36/2.6.37 regresse from 2.6.33

[Ben Hutchings]

On Fri, 2011-02-18 at 11:30 +0100, Bastien ROUCARIES wrote: 
> Package: linux-2.6
> Severity: grave
> tags: upstream
> forwarded: https://lkml.org/lkml/2011/2/16/249
> 
> i suffer since three month of severe crash with data loss (reiserfschk
> --rebuild-tree is often needed and moreover twice I need to 
> restore from backup).

This is quite possibly a hardware problem.  In any case, I would suggest
you switch to ext4 as reiserfsck is known to be very unreliable.

Ben.

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


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

Bug#613925: [linux-2.6] Reiserfs hung with data loss with 2.6.36/2.6.37 regresse from 2.6.33

[roucaries bastien]

On Fri, Feb 18, 2011 at 1:48 PM, Ben Hutchings  wrote:
> On Fri, 2011-02-18 at 11:30 +0100, Bastien ROUCARIES wrote:
>> Package: linux-2.6
>> Severity: grave
>> tags: upstream
>> forwarded: https://lkml.org/lkml/2011/2/16/249
>>
>> i suffer since three month of severe crash with data loss (reiserfschk
>> --rebuild-tree is often needed and moreover twice I need to
>> restore from backup).
>
> This is quite possibly a hardware problem.  In any case, I would suggest
> you switch to ext4 as reiserfsck is known to be very unreliable.

I do not think so. It seems to be related to the transition from big
kernel lock to finer lock.

I work fine with previous kernel but in this case I have some problems
with my network card.

And it is not an option to immediatly move to ext4

Bastien

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



--
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/AANLkTi=DvkjazNppJuLh2enzwzjhw=gxhjqjnfysr...@mail.gmail.com

Bug#544997: marked as done (nvidiafb: BUG: soft lockup - CPU#1 stuck for 61s!)

[Debian Bug Tracking System]

Your message dated Fri, 18 Feb 2011 14:01:23 +0100
with message-id <20110218130123.ga5...@jwilk.net>
and subject line Re: Bug#544997: nvidiafb: BUG: soft lockup - CPU#1 stuck for 
61s!
has caused the Debian Bug report #544997,
regarding nvidiafb: BUG: soft lockup - CPU#1 stuck for 61s!
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.)


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

Package: linux-2.6
Version: 2.6.30-6
Severity: normal

This bug is quite reproducible on my machine:

0. Start gpm.

1. Repeat a few times, until the screen freezes:

   - Select a large amount of text with mouse.

   - Switch to another vt.

2. Wait a few minutes.

3. The screen unfreezes, but is totally garbled, and dmesg shows 
something like this:


[ 9677.637004] BUG: soft lockup - CPU#1 stuck for 61s! [events/1:10]
[ 9677.637004] Modules linked in: tun kvm_amd kvm binfmt_misc nvidiafb fb_ddc 
vgastate nf_conntrack_ipv6 ip6table_filter ip6_tables xt_MARK iptable_mangle 
iptable_nat nf_nat ipt_REJECT xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 
xt_state nf_conntrack iptable_filter ip_tables x_tables fuse powernow_k8 it87 
hwmon_vid snd_hda_codec_realtek arc4 ecb tvaudio tda7432 tuner_simple 
tuner_types snd_hda_intel snd_hda_codec rt61pci tuner crc_itu_t snd_hwdep 
rt2x00pci snd_pcm rt2x00lib bttv ir_common snd_seq led_class snd_timer 
i2c_algo_bit input_polldev snd_seq_device v4l2_common mac80211 videodev 
v4l1_compat snd soundcore videobuf_dma_sg serio_raw videobuf_core btcx_risc 
k8temp evdev psmouse snd_page_alloc cfg80211 tveeprom i2c_nforce2 eeprom_93cx6 
i2c_core processor button ext3 jbd mbcache sd_mod crc_t10dif ide_cd_mod cdrom 
ide_pci_generic ata_generic sata_nv libata forcedeth scsi_mod amd74xx ide_core 
ohci_hcd ehci_hcd usbcore floppy thermal fan thermal_sys [last unloaded: 
scsi_wait_scan]
[ 9677.637004] 
[ 9677.637004] Pid: 10, comm: events/1 Not tainted (2.6.30-1-686 #1) M61SME-S2

[ 9677.637004] EIP: 0060:[] EFLAGS: 0293 CPU: 1
[ 9677.637004] EIP is at NVDmaWait+0xb1/0x17c [nvidiafb]
[ 9677.637004] EAX: f944 EBX: c3f0e324 ECX:  EDX: 26b1f186
[ 9677.637004] ESI:  EDI: 3b9ac9ff EBP: f900 ESP: f7079e00
[ 9677.637004]  DS: 007b ES: 007b FS: 00d8 GS:  SS: 0068
[ 9677.637004] CR0: 8005003b CR2: 4da3f670 CR3: 03a99000 CR4: 06d0
[ 9677.637004] DR0:  DR1:  DR2:  DR3: 
[ 9677.637004] DR6: 0ff0 DR7: 0400
[ 9677.637004] Call Trace:
[ 9677.637004]  [] ? nvidiafb_imageblit+0x1d2/0x39b [nvidiafb]
[ 9677.637004]  [] ? bit_putcs+0x32a/0x37c
[ 9677.637004]  [] ? fbcon_clear_margins+0x3a/0x3d
[ 9677.637004]  [] ? nvidiafb_setcolreg+0x1c2/0x1d4 [nvidiafb]
[ 9677.637004]  [] ? fbcon_putcs+0xa7/0xb2
[ 9677.637004]  [] ? bit_putcs+0x0/0x37c
[ 9677.637004]  [] ? do_update_region+0xcb/0x101
[ 9677.637004]  [] ? redraw_screen+0x10e/0x160
[ 9677.637004]  [] ? bit_cursor+0x0/0x446
[ 9677.637004]  [] ? complete_change_console+0x2c/0xb7
[ 9677.637004]  [] ? console_callback+0x4d/0xf4
[ 9677.637004]  [] ? worker_thread+0x13c/0x1bd
[ 9677.637004]  [] ? console_callback+0x0/0xf4
[ 9677.637004]  [] ? autoremove_wake_function+0x0/0x2d
[ 9677.637004]  [] ? worker_thread+0x0/0x1bd
[ 9677.637004]  [] ? kthread+0x42/0x67
[ 9677.637004]  [] ? kthread+0x0/0x67
[ 9677.637004]  [] ? kernel_thread_helper+0x7/0x10
[ 9743.137002] BUG: soft lockup - CPU#1 stuck for 61s! [events/1:10]
[ 9743.137004] Modules linked in: tun kvm_amd kvm binfmt_misc nvidiafb fb_ddc 
vgastate nf_conntrack_ipv6 ip6table_filter ip6_tables xt_MARK iptable_mangle 
iptable_nat nf_nat ipt_REJECT xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 
xt_state nf_conntrack iptable_filter ip_tables x_tables fuse powernow_k8 it87 
hwmon_vid snd_hda_codec_realtek arc4 ecb tvaudio tda7432 tuner_simple 
tuner_types snd_hda_intel snd_hda_codec rt61pci tuner crc_itu_t snd_hwdep 
rt2x00pci snd_pcm rt2x00lib bttv ir_common snd_seq led_class snd_timer 
i2c_algo_bit input_polldev snd_seq_device v4l2_common mac80211 videodev 
v4l1_compat snd soundcore videobuf_dma_sg serio_raw videobuf_core btcx_risc 
k8temp evdev psmouse snd_page_alloc cfg80211 tveeprom i2c_nforce2 eeprom_93cx6 
i2c_core processor button ext3 jbd mbcache sd_mod crc_t10dif ide_cd_mod cdrom 
ide_pci_generic ata_generic sata_nv libata forcedeth scsi_mod amd74xx ide_core 
ohci_hcd ehci_hcd usbcore floppy thermal fan thermal_sys [last unloaded: 
scsi_wait_scan]
[ 9743.137004] 
[ 9743.137004] Pid: 10, comm: events/1 Not tainted (2.6.30-1-686 #1) M61SME-S2

[ 9743.137004] EIP: 0060:[] EFL

Bug#599161: xen-linux-system-2.6.32-5-xen-amd64: Clock moved forward 50 minutes, caused Xen HVM domU restart

[Olivier Hanesse]

Hello,

I am got this issue on several (10+) Xen 4.0 servers without HVM:

linux-image-2.6.32-bpo.5-xen-amd64  2.6.32-29~bpo50+1  Linux
2.6.32 for 64-bit PCs, Xen dom0 suppor
xen-hypervisor-4.0-amd644.0.1-1The
Xen Hypervisor on AMD64

Each times there is this strange "50min" :

Nov  4 13:33:55  kernel: [591694.109052] Clocksource tsc unstable (delta =
-2999660340870 ns)
Nov 16 19:04:27 kernel: [102888.814677] Clocksource tsc unstable (delta =
-2999660352101 ns)
Nov 28 08:16:52 kernel: [2671840.236281] Clocksource tsc unstable (delta =
-299966013 ns)
Nov 29 08:59:54 kernel: [171581.195202] Clocksource tsc unstable (delta =
-2999660341178 ns)
Dec  8 12:58:09  kernel: [3108143.298526] Clocksource tsc unstable (delta =
-2999660353020 ns)
Dec 27 02:34:16 kernel: [1012551.748589] Clocksource tsc unstable (delta =
-2999660334211 ns)
Jan 12 09:12:53  kernel: [6537645.820016] Clocksource tsc unstable (delta =
-2999660339286 ns)
Jan 28 11:04:54  kernel: [5352834.035048] Clocksource tsc unstable (delta =
-2999660330184 ns)
Feb  9 21:04:03  kernel: [6415408.244988] Clocksource tsc unstable (delta =
-2999660342333 ns)
Feb 10 04:19:24 kernel: [4306193.416722] Clocksource tsc unstable (delta =
-2999660332510 ns)

after that ntp in Dom0 fails with : ntpd[6834]: time correction of -3000
seconds exceeds sanity limit (1000); set clock manually to the correct UTC
time
Same things with ntp in domU.

I didn't have this kind of issue with Xen Lenny.

Regards

Olivier

Bug#613973: linux-image-2.6.37-1-686: Disturbing [Hardware Error] MCE messages in 2.6.37

[Agustin Martin]

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

Hi,

After upgrade to 2.6.37, I started having tons of errors like those shown
below, about MCE. This happens in all terminals, in a sid box that did not
show this problem until 2.6.37 is installed.

[  300.004017] [Hardware Error]: No human readable MCE decoding support on this 
CPU type.
[  300.004025] [Hardware Error]: Run the message through 'mcelog --ascii' to 
decode.
[  300.004028] Disabling lock debugging due to kernel taint
[  300.004031] [Hardware Error]: No human readable MCE decoding support on this 
CPU type.
[  300.004033] [Hardware Error]: Run the message through 'mcelog --ascii' to 
decode.
[  300.004036] [Hardware Error]: Machine check events logged
[  450.004015] [Hardware Error]: No human readable MCE decoding support on this 
CPU type.
[  450.004024] [Hardware Error]: Run the message through 'mcelog --ascii' to 
decode.
[  450.004027] [Hardware Error]: No human readable MCE decoding support on this 
CPU type.
[  450.004030] [Hardware Error]: Run the message through 'mcelog --ascii' to 
decode.
[  450.004033] [Hardware Error]: Machine check events logged
[  525.004016] [Hardware Error]: No human readable MCE decoding support on this 
CPU type.
[  525.004023] [Hardware Error]: Run the message through 'mcelog --ascii' to 
decode.
[  525.004026] [Hardware Error]: No human readable MCE decoding support on this 
CPU type.
[  525.004029] [Hardware Error]: Run the message through 'mcelog --ascii' to 
decode.
[  525.004032] [Hardware Error]: Machine check events logged
[  562.504013] [Hardware Error]: No human readable MCE decoding support on this 
CPU type.
[  562.504019] [Hardware Error]: Run the message through 'mcelog --ascii' to 
decode.
[  562.504023] [Hardware Error]: No human readable MCE decoding support on this 
CPU type.
[  562.504025] [Hardware Error]: Run the message through 'mcelog --ascii' to 
decode.


Browsing a bit about this, seems that Andi Kleen patch in

  
http://git.kernel.org/?p=linux/kernel/git/ak/linux-mce-2.6.git;a=commitdiff;h=6e3c7411d2b86bff210c59caa432e8e862037bfd

may help.

Pointed to it by last question in

 http://www.mcelog.org/faq.html

Sending minimal info because above info seems enough. Let me know if
extensive info is needed. Running on AMD K7.


-- Package-specific info:
** Version:
Linux version 2.6.37-1-686 (Debian 2.6.37-1) (b...@decadent.org.uk) (gcc 
version 4.4.5 (Debian 4.4.5-10) ) #1 SMP Tue Feb 15 18:21:50 UTC 2011

** Command line:
root=/dev/mapper/debian-sid ro 

** Tainted: M (16)
 * System experienced a machine check exception.

** Model information
not available

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

Kernel: Linux 2.6.37-1-686 (SMP w/1 CPU core) 
Locale: LANG=es_ES, LC_CTYPE=es_ES (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

-- 
Agustin



-- 
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/20110218155951.ga4...@agmartin.aq.upm.es

Bug#613979: linux-image-2.6.37-1-amd64: kernel oops with snd-hda-intel: BUG: unable to handle kernel paging request at ffffc90011c08000

[Paul Menzel]

Package: linux-2.6
Version: 2.6.37-1
Severity: important

Dear Debian folks,


upgrading to DebPkg:linux-image-2.6.37-1-amd64 from linux-image-2.6.32-5-amd64 
gives an oops with `snd-hda-intel` and audio does not work anymore, since no 
sound devices are shown. You can see the trace in the below (pasted by your 
reportbug scripts) Linux kernel log.

Is the ALSA version in Debian Sid/unstable not compatible or is there another 
problem?

Additionally the boot process stops for over a minute at `Loading LIRC 
modules`(?).


Thanks,

Paul

-- Package-specific info:
** Version:
Linux version 2.6.37-1-amd64 (Debian 2.6.37-1) (b...@decadent.org.uk) (gcc 
version 4.4.5 (Debian 4.4.5-10) ) #1 SMP Tue Feb 15 20:01:26 UTC 2011

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

** Tainted: D (128)
 * Kernel has oopsed before.

** Kernel log:
[   41.265636] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
[   41.680357] HDA Intel :20:01.0: PCI INT A -> GSI 17 (level, low) -> IRQ 
17
[   41.680444] HDA Intel :20:01.0: setting latency timer to 64
[   41.680462] BUG: unable to handle kernel paging request at c90011c08000
[   41.680617] IP: [] azx_probe+0x3ad/0x86b [snd_hda_intel]
[   41.680728] PGD 13781a067 PUD 13781b067 PMD 1300ba067 PTE 80fd0173
[   41.680956] Oops: 0009 [#1] SMP 
[   41.681098] last sysfs file: /sys/module/snd_pcm/initstate
[   41.681159] CPU 0 
[   41.681203] Modules linked in: snd_hda_intel(+) snd_hda_codec snd_hwdep 
snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event 
tpm_tis tpm snd_seq tpm_bios psmouse parport_pc snd_timer snd_seq_device 
parport processor evdev snd i2c_viapro thermal_sys amd64_edac_mod k8temp 
i2c_core soundcore shpchp pcspkr serio_raw asus_atk0110 pci_hotplug edac_core 
button snd_page_alloc edac_mce_amd ext3 jbd mbcache sha256_generic cryptd 
aes_x86_64 aes_generic cbc dm_crypt dm_mod raid1 md_mod usbhid hid sg sd_mod 
crc_t10dif sr_mod cdrom ata_generic uhci_hcd sata_via pata_via libata ehci_hcd 
usbcore scsi_mod via_rhine mii nls_base [last unloaded: scsi_wait_scan]
[   41.684180] 
[   41.684180] Pid: 1153, comm: work_for_cpu Not tainted 2.6.37-1-amd64 #1 
M2V-MX SE/System Product Name
[   41.684180] RIP: 0010:[]  [] 
azx_probe+0x3ad/0x86b [snd_hda_intel]
[   41.684180] RSP: 0018:88013153fe50  EFLAGS: 00010286
[   41.684180] RAX: c90011c08000 RBX: 88013029ec00 RCX: 0006
[   41.684180] RDX:  RSI: 0246 RDI: 0246
[   41.684180] RBP: 88013341d000 R08:  R09: 0040
[   41.684180] R10: 0286 R11: 3731 R12: 88013029c400
[   41.684180] R13:  R14:  R15: 88013341d090
[   41.684180] FS:  () GS:8800bfc0() 
knlGS:f7610ab0
[   41.684180] CS:  0010 DS:  ES:  CR0: 8005003b
[   41.684180] CR2: c90011c08000 CR3: 000132f57000 CR4: 06f0
[   41.684180] DR0:  DR1:  DR2: 
[   41.684180] DR3:  DR6: 0ff0 DR7: 0400
[   41.684180] Process work_for_cpu (pid: 1153, threadinfo 88013153e000, 
task 8801303c86c0)
[   41.684180] Stack:
[   41.684180]  0005 8123ad65 000136c0 
88013029c400
[   41.684180]  8801303c8998 88013341d000 88013341d090 
8801322d9dc8
[   41.684180]  88013341d208   
811ad232
[   41.684180] Call Trace:
[   41.684180]  [] ? __pm_runtime_set_status+0x162/0x186
[   41.684180]  [] ? local_pci_probe+0x49/0x92
[   41.684180]  [] ? do_work_for_cpu+0x0/0x1b
[   41.684180]  [] ? do_work_for_cpu+0x0/0x1b
[   41.684180]  [] ? do_work_for_cpu+0xb/0x1b
[   41.684180]  [] ? kthread+0x7a/0x82
[   41.684180]  [] ? kernel_thread_helper+0x4/0x10
[   41.684180]  [] ? kthread+0x0/0x82
[   41.684180]  [] ? kernel_thread_helper+0x0/0x10
[   41.684180] Code: f4 01 00 00 ef 31 f6 48 89 df e8 29 dd ff ff 85 c0 0f 88 
2b 03 00 00 48 89 ef e8 b4 39 c3 e0 8b 7b 40 e8 fc 9d b1 e0 48 8b 43 38 <66> 8b 
10 66 89 14 24 8b 43 14 83 e8 03 83 f8 01 77 32 31 d2 be 
[   41.684180] RIP  [] azx_probe+0x3ad/0x86b [snd_hda_intel]
[   41.684180]  RSP 
[   41.684180] CR2: c90011c08000
[   41.684180] ---[ end trace 8d1f3ebc136437fd ]---
[   42.127750] input: ImPS/2 Logitech Wheel Mouse as 
/devices/platform/i8042/serio1/input/input5
[   63.455908] EXT3-fs (dm-1): using internal journal
[   63.800394] loop: module loaded
[   65.413037] Adding 4194300k swap on /dev/mapper/speicher-swap.  Priority:-1 
extents:1 across:4194300k 
[   67.008724] fuse init (API version 7.15)
[   67.140105] EXT3-fs: barriers not enabled
[   67.142596] kjournald starting.  Commit interval 5 seconds
[   67.147077] EXT3-fs (md0): using internal journal
[   67.147221] EXT3-fs (md0): mounted filesystem with ordered data mode
[   67.217115] EXT3-fs: barr

Bug#590105: LS-CHL support

[Sébastien LALLEMAND]

hi,
is LS-CHL supported in debian now ? Can we install squeeze on the LS-CHL ?


2011/1/28 Martin Michlmayr 

> * cvel...@gmail.com  [2011-01-15 22:37]:
> > I'm also trying to install Squeeze on a LS-CHL (LS-C640L-EU) and can
> > confirm, that it still does not recognise the sata drive.
>
> LS-CHL has been added to the mainline kernel in the meantime:
>
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=4bba1c34e0a70d0db2506e1b68f69d7edc8afd78
> so we can add it to the Debian kernel.  I'll look into this in a few
> weeks.
>
> --
> Martin Michlmayr
> http://www.cyrius.com/
>

Bug#613501: Workaround available in openvz git

[Ola Lundqvist]

Hi Maks

On Fri, Feb 18, 2011 at 09:46:44AM +, maximilian attems wrote:
> On Fri, Feb 18, 2011 at 07:27:27AM +0100, Ola Lundqvist wrote:
> > Hi Maks
> > 
> > Do you know when the next squeeze upload would be? Is it for the next
> > point release (and if so, do you know when that is?) or should we try
> > to convince the security team that this is actually a security issue.
> > 
> > Data corruption is not a nice thing I would say...
> > 
> > // Ola
> 
> why do you toppost, it is missing all relevant info!?

No special reason.

> > On Thu, Feb 17, 2011 at 07:18:11PM +0100, maximilian attems wrote:
> > > On Thu, 17 Feb 2011, Vladimir Kuklin wrote:
> > > 
> > > > 
> > > > git commit is here:
> > > > 
> > > > http://git.openvz.org/?p=linux-2.6.32-openvz;a=commit;h=3e89668abca56e6e11e1bbb9cbac1008d3c2357b
> > > > 
> > > > Please, don't forward it again to openvz devs. Just include it into
> > > > patchset for 2.6.32-5-openvz kernel update.
> > > 
> > > it is included, add info to changelog so it will be closed on next
> > > squeeze upload.
> 
> upload is planed after next stable release, most probably monday.

That is really great! Perfect.

// Ola

> 
> 

-- 
 --- Inguza Technology AB --- MSc in Information Technology 
/  o...@inguza.comAnnebergsslingan 37\
|  o...@debian.org   654 65 KARLSTAD|
|  http://inguza.com/Mobile: +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/20110218211105.gc4...@inguza.net

Bug#611750: 2nd update (Re: Bug#613790: pm-utils: eeepc 1005 PE recently stopped resuming from hibernate)

[Emmanuel Charpentier]

[ I Cc 611...@bugs.debian.org, which mi bug report seems to be a duplicate 
of... ]

Dear all,

A couple more data points :

1) I tried Sebastian Andrzej Siewio's 2.6.30 partially unpatched kernel,
to no avail : my eee 1005PE still rebooted when trying to resume from
hibernation (yes, I first rebooted on this partially patched kernel
*before* hibernating...).

2) restoring a 2.6.29 kernel from snapshots.debian.org "solved" the
problem (for some small value of "solution").

Hence :

1) At least on some eee hardware,
drm-i915-overlay-ensure-that-the-reg_bo-is-in-the-gtt-prior-to-writing.patch is 
*not* the sole culprit.

2) Temporarily pinning the linux-image-2.6.32-5-586 package to 2.6.30
may alleviate the problem, but cuts you off the opportunity to
auto-upgrade to a future and hyothetical 2.6.31 package. Is there a way
to configure apt to still auto-update if possible but to avoid 2.6.30 ?

Question :

Did someone tried to recompile the 2.6.30 package with the *three*
drm-i915 patches reversed ? I used to recompile my kernels (after all,
I'm following Debian on and off since about 1998...), but I'm no longer
aware of the current "official" procedures to do so (any pointer to a
*synthetic* doc ? ) and somewhat reluctant to undertake this on a
netbook... :-).

Sincerely yours,

Emmanuel Charpentier






-- 
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/1298066180.3549.22.ca...@portable-ec.bacbuc.dyndns.org

Bug#613922: linux: Radeon DRM doesn't initialise properly (firmware fails to load?)

[Owen]

Reported to:

https://bugs.freedesktop.org/show_bug.cgi?id=34462



-- 
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/87lj1dgfu6.wl%owen.ri...@gmail.com

Re: For discussion: security support strategy for the wheezy kernel

[Michael Gilbert]

On Mon, 7 Feb 2011 22:54:53 -0500 Michael Gilbert wrote:
> On Sun, 6 Feb 2011 21:58:08 -0400, Joey Hess wrote:
> > Michael Gilbert wrote:
> > > Another issue was that a lot of vulnerabilities that were found in that
> > > time frame were actually flaws in new kernel code, so testing/unstable
> > > were vulnerable, but the stable kernel itself was unaffected, so it was
> > > a bit safer to be running the stable kernel since the code was older
> > > (i.e. there was more time to find and fix issues).  For example, the
> > > vulnerability for one of the local privilege escalations that was
> > > exploited in the wild was introduced in 2.6.30, so lenny wasn't
> > > affected, but testing/unstable were.
> > 
> > LWN's analysis of age of introduction of kernel security holes in 2010
> > doesn't seem to agree? http://lwn.net/Articles/410606/
> > 
> > | So, in a sense, the above-mentioned kernel hacker was correct - an
> > | awful lot of the vulnerabilities fixed over the last year predate the
> > | git era, and are thus over five years old.
> 
> LWN's analysis is far from comprehensive, and the conclusions are not
> based in sufficiently rigorous analysis, but instead on the usual
> numbers game.  Their reporting is however very useful as a basis for
> further research.  
> 
> The first fact that they completely miss is that not all CVEs are
> created equal.  A memory info disclosure gets a CVE just like a 
> privilege escalation that has known exploits, but both are on the same
> playing field in the numbers game. Annecdotally, CVE-2010-3301 and
> CVE-2010-1146 had an exploit in the wild, and 2.6.26 was never
> affected.  The only issue that had an in-the-wild exploit affecting
> lenny in that list (that I'm aware of) was CVE-2010-3081 (and lenny
> would have sidestepped that too if it had had been even more
> conservative and gone with the older/stabler 2.6.25).
> 
> Even playing the numbers game with a bit more thoughtful analysis with
> the LWN data, lenny looks a lot better.  It can be seen that lenny
> (2.6.26) was vulnerable to 69% (36 out of 52) of the vulnerabilities
> listed there, and squeeze (2.6.32) was vulnerable to 98% (51 out of
> 52).  In my opinion that's a rather substantial difference, and thus a
> problem worth pondering.

So, now that I've had some time to contemplate the replies on this
issue, I have a much better appreciation of the need to keep unstable
closely in line with upstream development, and thus don't want to push
the original solution anymore. Also 2.6.37 is in unstable now, so that
idea is impossible, which is OK.

However, as I justify above, there is still a problem, and I think it
can still be solved relatively easily and without too much impact.
This time I suggest blocking 2.6.37 so 2.6.32 remains in testing for a
while.  This will allow it to get updates in sync with stable kernel
security updates (without any additional effort by Dann, Moritz, and
other kernel team members other than the package upload to testing as
well).

This will also help to provide a bit more stability for CUT [0].  Over
a 1.5-year period (the non-freeze timeframe) roughly 6 new upstream
kernels will be released, and each new kernel comes along with a high
probability of introducing breakage.  I'm trying to provide CUT
releases once a month, so every 3 months I will be looking at a likely
broken CUT release (or 25% of the time).  However, if there is just one
kernel transition in testing development cycle, then there is only 1
likely broken period (or 4% of the time).

Anyway, I know that the fact that this may have a future effect on my
efforts isn't a great argument, but this does impact whether CUT will be
successful, which impacts the whole project.  I wonder if we can at
least try it for a few months, and if there really are problems with
keeping the old kernel in testing, then we can just end this experiment
and unblock the newer upstream version.

If there is some concurrence on this, I'll submit an RC blocker bug on
the kernel.  Note there are only 8 days to discuss before the
transition is automatic (I think the current RC blocker [1] may
disappear by then).

Best wishes,
Mike

[0] http://lists.alioth.debian.org/pipermail/cut-team/2011-February/000195.html
[1] http://qa.debian.org/excuses.php?package=linux-2.6


-- 
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/20110218172432.239da727.michael.s.gilb...@gmail.com

Processed: Also in unstable

[Debian Bug Tracking System]

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

> found 613534 2.6.37-1
Bug #613534 [linux-2.6] regression: ThinkVantage button doesn't work on 
ThinkPad R61i since 2.6.37
There is no source info for the package 'linux-2.6' at version '2.6.37-1' with 
architecture ''
Unable to make a source version for version '2.6.37-1'
Bug Marked as found in versions 2.6.37-1.
> thanks
Stopping processing here.

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

Bug#613979: linux-image-2.6.37-1-amd64: kernel oops with snd-hda-intel: BUG: unable to handle kernel paging request at ffffc90011c08000

[Ben Hutchings]

On Fri, 2011-02-18 at 17:41 +0100, Paul Menzel wrote:
> Package: linux-2.6
> Version: 2.6.37-1
> Severity: important
> 
> Dear Debian folks,
> 
> 
> upgrading to DebPkg:linux-image-2.6.37-1-amd64 from
> linux-image-2.6.32-5-amd64 gives an oops with `snd-hda-intel` and
> audio does not work anymore, since no sound devices are shown. You can
> see the trace in the below (pasted by your reportbug scripts) Linux
> kernel log.
> 
> Is the ALSA version in Debian Sid/unstable not compatible or is there
> another problem?

I'm not sure what you mean by 'the ALSA version'.  ALSA is made up of
kernel drivers and libasound in user-space.  The drivers are included in
the kernel package and cannot be incompatible with it.  The interface
between the drivers and libasound is not supposed to change in an
incompatible way, and in any case a user process should not be able to
crash the kernel.

So I think this is just a bug in the driver.  Please report it upstream
at  under product 'Drivers', component
'Sound(ALSA)'.  Let us know the bug number or URL so we can track it.

> Additionally the boot process stops for over a minute at `Loading LIRC
> modules`(?).
[...]

I don't see any LIRC modules in the list of loaded modules.  This may be
a bug in the lirc package.  In any case, you need to make a separate bug
report for each bug.

Ben.

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


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

Processed: tagging 613979

[Debian Bug Tracking System]

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

> tags 613979 + moreinfo
Bug #613979 [linux-2.6] linux-image-2.6.37-1-amd64: kernel oops with 
snd-hda-intel: BUG: unable to handle kernel paging request at c90011c08000
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Processed: reassign 596741 to src:linux-2.6 ...

[Debian Bug Tracking System]

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

> reassign 596741 src:linux-2.6
Bug #596741 [pm-utils] regression: CPU fan fast after resume: won't climb back 
down
Bug reassigned from package 'pm-utils' to 'src:linux-2.6'.
> forwarded 596741 https://bugzilla.kernel.org/show_bug.cgi?id=29412
Bug #596741 [src:linux-2.6] regression: CPU fan fast after resume: won't climb 
back down
Set Bug forwarded-to-address to 
'https://bugzilla.kernel.org/show_bug.cgi?id=29412'.
> thanks
Stopping processing here.

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

Bug#596741: Processed: Re: Processed: bug 596741 is not forwarded, tagging 596741, reassign 596741 to gnome-power-manager

[Jon Dowland]

Sorry for the delay, I only just saw your reply.

On Fri, Dec 17, 2010 at 11:14:08PM +0100, Michael Biebl wrote:
> Hm, why is that a pm-utils issue?
> 
> If you simply run
> echo "mem" > /sys/power/state (given your hardware doesn't need any quirks)
> is the problem gone?

Sorry for the delay, yep that is all that is needed to
reproduce the problem, reassigning accordingly.


-- 
Jon Dowland



-- 
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/20110218225038.ga3...@tchicaya.lan

Re: For discussion: security support strategy for the wheezy kernel

[Ben Hutchings]

On Fri, 2011-02-18 at 17:24 -0500, Michael Gilbert wrote:
[...]
> If there is some concurrence on this, I'll submit an RC blocker bug on
> the kernel.  Note there are only 8 days to discuss before the
> transition is automatic (I think the current RC blocker [1] may
> disappear by then).

I don't recall anyone agreeing with your idea to stop following
upstream.  Please let this drop.

Ben.

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


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

Re: [cut-team] For discussion: security support strategy for the wheezy kernel

[Lucas Nussbaum]

On 18/02/11 at 17:24 -0500, Michael Gilbert wrote:
> On Mon, 7 Feb 2011 22:54:53 -0500 Michael Gilbert wrote:
> > On Sun, 6 Feb 2011 21:58:08 -0400, Joey Hess wrote:
> > > Michael Gilbert wrote:
> > > > Another issue was that a lot of vulnerabilities that were found in that
> > > > time frame were actually flaws in new kernel code, so testing/unstable
> > > > were vulnerable, but the stable kernel itself was unaffected, so it was
> > > > a bit safer to be running the stable kernel since the code was older
> > > > (i.e. there was more time to find and fix issues).  For example, the
> > > > vulnerability for one of the local privilege escalations that was
> > > > exploited in the wild was introduced in 2.6.30, so lenny wasn't
> > > > affected, but testing/unstable were.
> > > 
> > > LWN's analysis of age of introduction of kernel security holes in 2010
> > > doesn't seem to agree? http://lwn.net/Articles/410606/
> > > 
> > > | So, in a sense, the above-mentioned kernel hacker was correct - an
> > > | awful lot of the vulnerabilities fixed over the last year predate the
> > > | git era, and are thus over five years old.
> > 
> > LWN's analysis is far from comprehensive, and the conclusions are not
> > based in sufficiently rigorous analysis, but instead on the usual
> > numbers game.  Their reporting is however very useful as a basis for
> > further research.  
> > 
> > The first fact that they completely miss is that not all CVEs are
> > created equal.  A memory info disclosure gets a CVE just like a 
> > privilege escalation that has known exploits, but both are on the same
> > playing field in the numbers game. Annecdotally, CVE-2010-3301 and
> > CVE-2010-1146 had an exploit in the wild, and 2.6.26 was never
> > affected.  The only issue that had an in-the-wild exploit affecting
> > lenny in that list (that I'm aware of) was CVE-2010-3081 (and lenny
> > would have sidestepped that too if it had had been even more
> > conservative and gone with the older/stabler 2.6.25).
> > 
> > Even playing the numbers game with a bit more thoughtful analysis with
> > the LWN data, lenny looks a lot better.  It can be seen that lenny
> > (2.6.26) was vulnerable to 69% (36 out of 52) of the vulnerabilities
> > listed there, and squeeze (2.6.32) was vulnerable to 98% (51 out of
> > 52).  In my opinion that's a rather substantial difference, and thus a
> > problem worth pondering.
> 
> So, now that I've had some time to contemplate the replies on this
> issue, I have a much better appreciation of the need to keep unstable
> closely in line with upstream development, and thus don't want to push
> the original solution anymore. Also 2.6.37 is in unstable now, so that
> idea is impossible, which is OK.
> 
> However, as I justify above, there is still a problem, and I think it
> can still be solved relatively easily and without too much impact.
> This time I suggest blocking 2.6.37 so 2.6.32 remains in testing for a
> while.  This will allow it to get updates in sync with stable kernel
> security updates (without any additional effort by Dann, Moritz, and
> other kernel team members other than the package upload to testing as
> well).

You base your reasoning on the assumption that CUT users prefer a more
stable kernel to a more recent kernel. I'm tempted to think the
opposite.

- lucas


-- 
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/20110219064759.ga30...@xanadu.blop.info