Bug#691427: journal commit I/O error on brand-new Thinkpad T430s ext4 on lvm on SSD

2012-10-25 Thread Didier Raboud
Source: linux
Version: 3.2.32-1
Severity: important
Tags: upstream

Hi dear linux maintainers,

I have setup a Debian Wheezy on a brand new Lenovo Thinkpad T430s with a
SSDSC2BW180A3L SSD drive. After the install, the user installed his usual
softwares (solr, apache, nodejs, …) and started work.

Under some load (importing thousands of records in MySQL via a hand-called PHP
script), the system reliably stops working fine enough because of journal
commit I/O error leading to a readonly filesystem. Then Gnome becomes
(obviously) unuseable and the only way out is a hard-reboot.

The disk looks fine (and is brand new), according to the BIOS disk report and
SMART tests, so the usual suspiscion that it might be broken is improbable.

We have reproduced this bug under 3.2.0-4 (3.2.23-1), 3.2.0-5 (3.2.32-1) and
3.5-trunk (3.5.5-1~experimental.1). The setup is an ext4 / (and /home) on LVM,
on the mentionned SSD.

What are the things we could do to help resolve this bug? Are there logs that
you might want to get? Please advise!

Cheers,

OdyX, on behalf of Dorian Villet, owner of the (unuseable) T430s.


-- 
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/20121025145608.8828.41282.reportbug@gyllingar



Bug#661112: Resume from suspend does not fully turn on laptop screen

2012-03-02 Thread Didier Raboud
Le vendredi, 24 février 2012 10.41:45, Enrico Zini a écrit :
 
 since version 3.2.0, when I resume from suspend the laptop screen
 backlight turns on, but the screen contents remain all black. Other
 monitors connected to the system wake up fine.

I'm getting the same symptoms, but with a different syslog error:

[18889.928026] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... 
GPU hung
[18889.928036] [drm] capturing error event; look for more information in 
/debug/dri/0/i915_error_state
[18889.928927] [drm:i915_wait_request] *ERROR* i915_wait_request returns -11 
(awaiting 4 at 3, next 5)
[18889.929209] [drm:init_ring_common] *ERROR* render ring initialization 
failed ctl  head  tail  start 
[18889.992311] [drm] Changing LVDS panel from (+hsync, +vsync) to (-hsync, -
vsync)
[18889.992463] [ cut here ]
[18889.992490] WARNING: at 
/home/blank/debian/kernel/release/linux-2.6/linux-2.6-3.2.7/debian/build/source_amd64_none/drivers/gpu/drm/i915/intel_display.c:793
 
intel_enable_pipe+0x68/0x11f [i915]()
[18889.992493] Hardware name: Latitude D630   
[18889.992495] PLL state assertion failure (expected on, current off)
[18889.992497] Modules linked in: ipt_MASQUERADE iptable_nat nf_nat 
nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_filter ip_tables 
x_tables cn acpi_cpufreq mperf cpufreq_conservative cpufreq_stats 
cpufreq_powersave cpufreq_userspace parport_pc ppdev lp parport bnep rfcomm 
binfmt_misc kvm_intel kvm fuse ext2 loop joydev snd_hda_codec_idt 
snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss pcmcia snd_mixer_oss snd_pcm 
snd_seq_midi snd_rawmidi dell_wmi sparse_keymap yenta_socket pcmcia_rsrc 
pcmcia_core snd_seq_midi_event evdev snd_seq dell_laptop dcdbas i2c_i801 
snd_timer snd_seq_device pcspkr arc4 btusb psmouse bluetooth serio_raw 
iTCO_wdt iTCO_vendor_support snd iwl3945 iwl_legacy mac80211 cfg80211 i915 
drm_kms_helper drm i2c_algo_bit i2c_core soundcore rfkill snd_page_alloc video 
battery button wmi ac power_supply processor ext4 mbcache jbd2 crc16 
sha256_generic cryptd aes_x86_64 aes_generic cbc dm_crypt dm_mod sr_mod sd_mod 
crc_t10dif cdrom ata_generic uhci_hcd firewire_ohci
thermal thermal_sys ahci libahci firewire_core crc_itu_t ata_piix ehci_hcd tg3 
libphy libata scsi_mod usbcore usb_common [last unloaded: scsi_wait_scan]
[18889.992572] Pid: 21437, comm: kworker/u:29 Not tainted 3.2.0-1-amd64 #1
[18889.992574] Call Trace:
[18889.992580]  [81046871] ? warn_slowpath_common+0x78/0x8c
[18889.992584]  [8104691d] ? warn_slowpath_fmt+0x45/0x4a
[18889.992596]  [a02749e3] ? intel_enable_pipe+0x68/0x11f [i915]
[18889.992607]  [a0277551] ? i9xx_crtc_mode_set+0xa19/0xa89 [i915]
[18889.992618]  [a0272c67] ? intel_crtc_mode_set+0x60/0x8a [i915]
[18889.992624]  [a02534a8] ? drm_crtc_helper_set_mode+0x22b/0x38f 
[drm_kms_helper]
[18889.992628]  [811a840d] ? idr_pre_get+0x51/0x69
[18889.992635]  [a025365e] ? drm_helper_resume_force_mode+0x52/0xfe 
[drm_kms_helper]
[18889.992643]  [a0259cd2] ? i915_reset+0x420/0x43a [i915]
[18889.992652]  [a025d1a1] ? i915_driver_irq_postinstall+0x169/0x169 
[i915]
[18889.992660]  [a025d250] ? i915_error_work_func+0xaf/0xe7 [i915]
[18889.992666]  [8105ae45] ? process_one_work+0x163/0x284
[18889.992669]  [8105be0d] ? worker_thread+0xc2/0x145
[18889.992672]  [8105bd4b] ? manage_workers.isra.23+0x15b/0x15b
[18889.992675]  [8105ef49] ? kthread+0x76/0x7e
[18889.992680]  [81347934] ? kernel_thread_helper+0x4/0x10
[18889.992683]  [8105eed3] ? kthread_worker_fn+0x139/0x139
[18889.992687]  [81347930] ? gs_change+0x13/0x13
[18889.992688] ---[ end trace 7275beeccf86fa64 ]---

Is that the same issue or should I report a separate bug ?

Cheers,

OdyX


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


Mobile UXes - From the DebConf11 BoF to the stars

2011-09-08 Thread Didier Raboud
Hi all, 

This is the sumary of the discussion held at DebConf11 during the Mobile 
UXes BoF, on 2011-07-29, at 18h00 in the meeting room.

(= tl;dr version =)
(Search for Proposal down this mail.)
(Please answer to debian-de...@lists.debian.org only. )

The point of this mail is to inform people and communities of the content of 
those discussions and propose a sort-of plan of action. Note that nothing has 
been clearly decided there but the discussion was really nice and promising so 
I sort-of hope the consensus acknowledged upon there can be reflected online.

= Outline =
 0 - Commented overview of the various available stacks
 1 - Proposal for future actions and meet-together

= 0 - Commented overview of the various available stacks =

The initial idea to frame the discussion was to share experiences and opinions 
about known free software mobile stacks: are they packaged in Debian? What has 
been the experience so far? If not, why not?

The main reference to build up this list has been 
http://wiki.debian.org/Smartphone, which is still a good reference! Now to the 
list.

== Android ==

The Canonical effort [0] to port an Android execution environment is currently 
reported as a dead-end. The most free-software-friendly efforts reported are 
IcedRobot [1] and Replicant [2]. They don't seem ready enough for inclusion in 
Debian though but we should keep an eye on them.

[0] https://wiki.ubuntu.com/Specs/AndroidExecutionEnvironment
[1] http://icedrobot.org
[2] http://replicant.us/

== MeeGo ==

Back when the MeeGo project was launched, some hoped it could be Debian-based. 
Some persons from the Debian community tried to make that a reality back then 
but didn't succeed. Then the pkg-meego team [3] was formed to get software 
produced by the MeeGo project in Debian. This effort has faced a tough reality 
with regards to project management, interfaces stability, FHS respect, 
trademark policies, etc; and as a result it is currently stalled.

Nowadays, various software pieces produced by or within the MeeGo project are 
probably interesting to get in Debian:

  - Maliit [4] it is the input methods solution used in MeeGo (in particular
it's the project behind the Harmattan virtual keyboard / input method;
also used for the N900/N950 Community Edition)
  - the Tablet User Experience [5] released by Intel earlier this year.
  - Handheld UX in the MeeGo CE form [6]

As a side-note; the software released with the Nokia N9 (of which the swipe 
user interface [7] is not known to be available as free software) is available 
as a downloadable qemu image [8].

MeeGo CE [9] is a community effort both to make free MeeGo releases for a few 
smartphones, and to make MeeGo as a project more transparent by being an 
example of a contributing vendor. Since the project aims for a product level 
quality in the UIs, the packages they've put on top of MeeGo Core and 
integrate back to the Core are interesting for Debian as well. Timo Jyrinki 
wrote a very interesting blogpost on this topic [10].

[3]  http://pkg-meego.alioth.debian.org/
[4]  http://maliit.org
[5]  https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview
[6]  https://build.pub.meego.com/project/packages?project=Project%3ADE%3ATrunk
[7]  http://www.developer.nokia.com/swipe/ux/
[8]  http://harmattan-dev.nokia.com/
[9]  http://wiki.meego.com/N900
[10] http://losca.blogspot.com/2011/08/meego-ce-and-freesmartphoneorg.html

== Maemo ==

Maemo [11] is the Debian derivative that powers the Nokia N900 that was one 
branches of the MeeGo merge. Nowadays, both Maemo 6 and Harmattan (software 
basis of the Nokia N9) are reported to be dead-ends. A Debian team [12] was 
formed to work on the inclusion of the Maemo software back in Debian, but it 
decided earlier this year that Maemo is a dead end and removed Maemo related 
software from Debian [13].

It could still make sense to package some of the Maemo GTK themes to make 
running unmodified GTK applications easier on mobile devices. Openmoko also 
produced some.

[11] http://maemo.org
[12] http://wiki.debian.org/pkg-maemo
[13] http://article.gmane.org/gmane.linux.debian.alioth.maemo.maint/1013

== GNOME Mobile  Embedded Initiative ==

The GNOME Mobile  Embedded Initiative was announced in 2007 for developing 
and promoting the use of the GNOME platform in mobile devices. It is not 
packaged in Debian (although the GNOME team might be able to give more 
insightful information) and doesn't seem to have a home on the Internet. It is 
part of the Hackable1 distribution (see below).

== KDE Plasma Active ==

From their website: KDE Plasma Active [14] aims at creating a cross-device 
user experience for emerging devices such as tablet computers, media centers, 
smartphones, and more. It is currently not packaged in Debian, but some 
members of the pkg-qt-kde team could certainly be interested [15].

[14] 

Re: Bug#634916: usb-modeswitch: seems to have no effect on Huawei E169

2011-08-11 Thread Didier Raboud
reassign 634916 src:linux-2.6 3.0.0-1
retitle 634916 Linux modeswitches some 3G dongles in kernelland (duplicates 
userland functionality)
thanks

Dear linux-2.6 maintainers, 

I'm hereby re-assigning the #634916 bug to the Linux kernel, as per the
discussion held with Josua Dietze, the usb-modeswitch upstream developer.

In summary: the Linux kernel modeswitches some 3G dongles where
usb-modeswitch is supposed to be the userland tool doing this. Having this
behaviour hardcoded in Linux implies less flexibility and duplicates
a functionality already present in userland _today_.

Please ask if you need more information, cheers, 

OdyX


-- 
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/201108111057.24324.o...@debian.org



Bug#595661: Debian bug #595661: Alsa

2011-08-11 Thread Didier Raboud
forwarded 595661 alsa-de...@alsa-project.org
found 595661 3.0.0-1
thanks

Le vendredi, 29 juillet 2011 10.02:24, Jonathan Nieder a écrit :
 Interesting.  If it still happens in version 3.0, could you report it
 to alsa-de...@alsa-project.org, cc-ing this bug log?

Dear Alsa developers, 

As I reported in the Debian #595661 bug [0], I'm experiencing a weird 
behaviour of the snd-hda-intel driver on my Dell Latitude D630:

When the headphone is plugged in, I can't reach all volume levels in it: when 
playing with the Master and Headphone sliders in alsamixer (all others at 
max), sounds _stops_ being outputted before reaching zero levels (and it's not 
a matter of me not hearing: the sound is still rather loud when it stops).

What I see is that I only get sound when the sum of the levels of Master 
and Headphone is big enough:

According to my experimental analysis, the minimum combined levels where I 
can hear sound are when the sum of the attenuations of Master and 
Headphone in dB are smaller than 48 dB (see the attached graph for details).

Could this be a hardware limitation ?

Cheers,

-- 
OdyX

[0] http://bugs.debian.org/595661
snd_hda_intel_weirdness.png

Bug#607669: linux-image-2.6.37-rc5-amd64: Dell Latitude D630 backlight fails to resume to on

2010-12-20 Thread Didier Raboud
Package: linux-2.6
Version: 2.6.37~rc5-1~experimental.3
Severity: normal
Tags: experimental

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi, 

when running the 3.6.37-rc5 kernel, I noticed that my screen fails to
relight after being suspended by the desktop manager (inactivitiy timeout).
I can reliably reproduce this (and recover) by following these steps:

1) boot, up to a running X
2) $ xset dpms force off
3) move mouse

Now the screen is on, things work, but I cannot light the screen more than a
bare minimum (using the Fn-{up,down} hardware keys), while I can before step
2. I can recover from this situation by suspending-to-ram and waking up again.

This is also a regression from the Squeeze-Sid kernel (2.6.32-29), but I think
it worked with 2.6.36.

Cheers, 

OdyX

- -- Package-specific info:
** Version:
Linux version 2.6.37-rc5-amd64 (Debian 2.6.37~rc5-1~experimental.3) 
(b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.5-7) ) #1 SMP Sat Dec 11 
19:38:02 UTC 2010

** Command line:
BOOT_IMAGE=/vmlinuz-2.6.37-rc5-amd64 root=/dev/mapper/Tamino-Root ro quiet 
splash

** Not tainted

** Kernel log:
[ 9368.431655] uhci_hcd :00:1d.1: setting latency timer to 64
[ 9368.431682] usb usb6: root hub lost power or was reset
[ 9368.431694] uhci_hcd :00:1d.2: PCI INT C - GSI 22 (level, low) - IRQ 22
[ 9368.431701] uhci_hcd :00:1d.2: setting latency timer to 64
[ 9368.431728] usb usb7: root hub lost power or was reset
[ 9368.431742] ehci_hcd :00:1d.7: PCI INT A - GSI 20 (level, low) - IRQ 20
[ 9368.431748] ehci_hcd :00:1d.7: setting latency timer to 64
[ 9368.431796] pci :00:1e.0: setting latency timer to 64
[ 9368.431808] ata_piix :00:1f.1: PCI INT A - GSI 16 (level, low) - IRQ 16
[ 9368.431813] ata_piix :00:1f.1: setting latency timer to 64
[ 9368.431864] ahci :00:1f.2: setting latency timer to 64
[ 9368.431980] ata5: port disabled. ignoring.
[ 9368.431989] pci :00:1c.5: wake-up capability disabled by ACPI
[ 9368.432016] tg3 :09:00.0: PME# disabled
[ 9368.432052] i915 :00:02.0: setting latency timer to 64
[ 9368.439031] sd 0:0:0:0: [sda] Starting disk
[ 9368.472278] dell-wmi: Unknown key e043 pressed
[ 9368.484437] firewire_core: skipped bus generations, destroying all nodes
[ 9368.515466] serial 00:09: activated
[ 9368.760091] ata3: SATA link down (SStatus 0 SControl 300)
[ 9368.792078] usb 7-1: reset full speed USB device using uhci_hcd and address 2
[ 9368.984133] firewire_core: rediscovered device fw0
[ 9369.040077] usb 3-2: reset full speed USB device using uhci_hcd and address 2
[ 9369.216013] btusb 3-2:1.0: no reset_resume for driver btusb?
[ 9369.216018] btusb 3-2:1.1: no reset_resume for driver btusb?
[ 9369.216341] ata4.00: configured for UDMA/33
[ 9369.304096] usb 7-2: reset full speed USB device using uhci_hcd and address 3
[ 9369.513976] usb 7-1.2: reset full speed USB device using uhci_hcd and 
address 4
[ 9369.620975] usbfs 7-1.2:1.0: no reset_resume for driver usbfs?
[ 9371.188263] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 9371.195573] ata1.00: configured for UDMA/100
[ 9371.205301] dell-wmi: Unknown key e044 pressed
[ 9371.356279] PM: resume of devices complete after 2937.594 msecs
[ 9371.356773] PM: Finishing wakeup.
[ 9371.356775] Restarting tasks ... 
[ 9371.358520] usb 7-1.2: usbfs: process 2398 (pcscd) did not claim interface 0 
before use
[ 9371.373314] done.
[ 9371.373321] video LNXVIDEO:01: Restoring backlight state
[ 9371.422636] composite sync not supported
[ 9373.495513] cfg80211: Calling CRDA to update world regulatory domain
[ 9373.529139] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection 
driver for Linux, in-tree:s
[ 9373.529142] iwl3945: Copyright(c) 2003-2010 Intel Corporation
[ 9373.529227] iwl3945 :0c:00.0: PCI INT A - GSI 17 (level, low) - IRQ 17
[ 9373.529247] iwl3945 :0c:00.0: setting latency timer to 64
[ 9373.582914] iwl3945 :0c:00.0: Tunable channels: 13 802.11bg, 23 802.11a 
channels
[ 9373.582918] iwl3945 :0c:00.0: Detected Intel Wireless WiFi Link 3945ABG
[ 9373.583065] iwl3945 :0c:00.0: irq 44 for MSI/MSI-X
[ 9373.583423] ieee80211 phy0: Selected rate control algorithm 'iwl-3945-rs'
[ 9373.825978] btusb_intr_complete: hci0 urb 880024a65f00 failed to 
resubmit (1)
[ 9373.826961] btusb_bulk_complete: hci0 urb 880028678f00 failed to 
resubmit (1)
[ 9373.827958] btusb_bulk_complete: hci0 urb 880024a659c0 failed to 
resubmit (1)
[ 9376.485210] iwl3945 :0c:00.0: loaded firmware version 15.32.2.9
[ 9376.556528] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 9379.591638] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 9379.776553] tg3 :09:00.0: PME# enabled
[ 9379.776575] pci :00:1c.5: wake-up capability enabled by ACPI
[ 9379.801342] pci :00:1c.5: wake-up capability disabled by ACPI
[ 9379.801398] tg3 :09:00.0: PME# disabled
[ 9379.816484] tg3 :09:00.0: irq 42 for MSI/MSI-X
[ 9379.852578] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 

Bug#602444: firmware-brcm80211: Kernel Panic on iwlist scan

2010-11-04 Thread Didier Raboud
Package: firmware-brcm80211
Version: 0.27
Severity: critical
Tags: patch
Justification: breaks the whole system

Hi, 

Booting the HP Mini 5103 with the firmware-brcm80211 package installed leads
to a 100% reproducible Kernel Panic. (Squeeze's 2.6.32 and experimental
2.6.36-trunk are affected).

From the http://linuxwireless.org/en/users/Drivers/brcm80211 homepage, the fix
is to load the module with maxcpus=1.

So a simple patch would be to ship a /etc/modprobe.d/brcm80211.conf containing

options brcm80211 maxcpus=1

I tested that here and it works. So, of course having said driver run on one
CPU only is sub-optimal, but at least the Kernel Panic is avoided.

This should make it in Squeeze IMHO. 

Cheers, OdyX



-- 
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/20101104215211.10855.5591.report...@tamino



Bug#595661: linux-image-2.6.35-trunk-amd64: [Alsa] Initial offset in volume adjustment sliders (sound stops before 0)

2010-09-05 Thread Didier Raboud
Package: linux-2.6
Version: 2.6.35-1~experimental.2
Severity: normal

Hi dear Kernel maintainers, 

I noticed that I get a very weird Alsa functionality: when I reduce the volume
of various sliders under a certain level (which depends on the relative values
of the sliders, the sounds stops completely (instead of continuing to reduce).

I tried with and without pulseaudio installed and running, so it doesn't seem
to take part of the game.

The disturbing thing is that the levels are not particularilty low: e.g.
sounds stops with master=36 (/100), Headphone=66 (/100) and PCM=100 (/100).

Ah, this behaviour happens in the headphones only.

Any idea ?

Cheers, 

OdyX

-- Package-specific info:
** Version:
Linux version 2.6.35-trunk-amd64 (Debian 2.6.35-1~experimental.2) 
(m...@debian.org) (gcc version 4.4.5 20100728 (prerelease) (Debian 4.4.4-8) ) 
#1 SMP Tue Aug 17 08:22:25 UTC 2010

** Command line:
BOOT_IMAGE=/vmlinuz-2.6.35-trunk-amd64 root=/dev/mapper/Tamino-Root ro quiet

** Not tainted

** Kernel log (removed as was useless)

** Model information
sys_vendor: Dell Inc.
product_name: Latitude D630   
product_version: 
chassis_vendor: Dell Inc.
chassis_version: 
bios_vendor: Dell Inc.
bios_version: A01
board_vendor: Dell Inc.
board_name: 0KU184
board_version:

** Loaded modules:
Module  Size  Used by
iwl394555569  0 
iwlcore95515  1 iwl3945
mac80211  167373  2 iwl3945,iwlcore
cfg80211  135399  3 iwl3945,iwlcore,mac80211
ppp_deflate 3714  0 
bsd_comp4651  0 
ppp_async   6392  0 
crc_ccitt   1651  1 ppp_async
ppp_generic22115  3 ppp_deflate,bsd_comp,ppp_async
slhc4881  1 ppp_generic
option 15749  0 
usb_wwan   10841  1 option
usbserial  33726  2 option,usb_wwan
usb_storage45112  0 
tun12980  0 
nls_utf81357  1 
cifs  228177  2 
parport_pc 20766  0 
ppdev   5800  0 
lp  8959  0 
parport32010  3 parport_pc,ppdev,lp
acpi_cpufreq5893  1 
mperf   1499  1 acpi_cpufreq
rfcomm 31435  8 
sco 7932  2 
cpufreq_conservative 9744  0 
bnep   10476  2 
cpufreq_userspace   2296  0 
l2cap  30128  16 rfcomm,bnep
cpufreq_powersave   1026  0 
crc16   1659  1 l2cap
cpufreq_stats   3052  0 
binfmt_misc 7037  1 
kvm_intel  41978  0 
kvm   248733  1 kvm_intel
fuse   57953  1 
nfsd  261686  13 
exportfs3602  1 nfsd
nfs   251489  0 
lockd  64315  2 nfsd,nfs
fscache40148  1 nfs
nfs_acl 2381  2 nfsd,nfs
auth_rpcgss37433  2 nfsd,nfs
sunrpc195156  14 nfsd,nfs,lockd,nfs_acl,auth_rpcgss
coretemp5524  0 
firewire_sbp2  12277  0 
loop   13422  0 
snd_hda_codec_idt  53360  1 
joydev  9301  0 
arc41401  2 
ecb 1959  2 
snd_hda_intel  22582  5 
snd_hda_codec  84698  2 snd_hda_codec_idt,snd_hda_intel
snd_hwdep   5938  1 snd_hda_codec
snd_pcm_oss32706  0 
snd_mixer_oss  13090  1 snd_pcm_oss
snd_pcm74024  4 snd_hda_intel,snd_hda_codec,snd_pcm_oss
i915  276505  2 
pcmcia 32906  0 
snd_seq_midi4946  0 
snd_rawmidi19576  1 snd_seq_midi
snd_seq_midi_event  6337  1 snd_seq_midi
snd_seq47046  2 snd_seq_midi,snd_seq_midi_event
drm_kms_helper 26939  1 i915
snd_timer  19068  2 snd_pcm,snd_seq
btusb  10862  2 
snd_seq_device  5896  3 snd_seq_midi,snd_rawmidi,snd_seq
drm   180695  3 i915,drm_kms_helper
bluetooth  49885  9 rfcomm,sco,bnep,l2cap,btusb
psmouse51060  0 
yenta_socket   20469  0 
pcmcia_rsrc 8487  1 yenta_socket
i2c_i8018901  0 
dell_laptop 5874  0 
dell_wmi2947  0 
tpm_tis 8758  0 
snd59675  20 
snd_hda_codec_idt,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
i2c_algo_bit4914  1 i915
dcdbas  6286  1 dell_laptop
tpm14227  1 tpm_tis
pcmcia_core15629  3 pcmcia,yenta_socket,pcmcia_rsrc
tpm_bios5425  1 tpm
wmi 8103  1 dell_wmi
serio_raw   4102  0 
i2c_core   22507  5 i915,drm_kms_helper,i2c_i801,drm,i2c_algo_bit
rfkill 17395  4 cfg80211,bluetooth,dell_laptop
evdev   

Bug#464373: [linux-2.6] Not sufficient ?

2008-10-25 Thread Didier Raboud
Hi,

I'm using uswsusp for supsending and I noticed the following :

* When waking up with the wifi kill button on (to get WiFi working), the card 
is 
correctly powered on and the connection will work (modulo some other 
problems, ..)

* When waking up with the wifi kill button off (after having been in places 
where no WiFi is accessible or useful), if I power the card afterwards, it 
won't power up and I have to ifdown/ifup to get the card working.

I'm not using ifplugd or anything like this. My /etc/network/interfaces :

auto wlan0
iface wlan0 inet manual
pre-up  ip link set wlan0 up
wpa-driver  wext
wpa-roam/etc/wpa_supplicant/wpa_roaming.conf

iface default inet dhcp

Please ask for more info if needed...

Regards, 

OdyX

-- 
Didier Raboud, proud Debian user.
CH-1802 Corseaux
[EMAIL PROTECTED]


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


Bug#464373: [linux-2.6] Not sufficient ?

2008-10-25 Thread Didier Raboud
Le samedi 25 octobre 2008 12:26:45 Jonas Smedegaard, vous avez écrit :
 On Sat, Oct 25, 2008 at 12:14:12PM +0200, Didier Raboud wrote:
 I'm using uswsusp for supsending and I noticed the following :
 
 * When waking up with the wifi kill button on (to get WiFi working), the
  card is correctly powered on and the connection will work (modulo some
  other problems, ..)
 
 * When waking up with the wifi kill button off (after having been in
  places where no WiFi is accessible or useful), if I power the card
  afterwards, it won't power up and I have to ifdown/ifup to get the card
  working.
 
 I'm not using ifplugd or anything like this.

 Perhaps you are using network-manager?


   - Jonas

Hi, 

certainly not... ;) For now, it works less good than wpa_supplicant directly.

Regards, 

OdyX

-- 
Didier Raboud, proud Debian user.
CH-1802 Corseaux
[EMAIL PROTECTED]


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


Bug#495685: [#495685] firmware-iwlwifi: microcode error

2008-10-06 Thread Didier Raboud
Le mardi 19 août 2008 19:02:56 Stefano Sabatini, vous avez écrit :
 Package: firmware-iwlwifi
 Version: 0.12
 Severity: grave
 Justification: renders package unusable


 I got this when I try to load iwl3945:

 When I try the command:
 modprobe iwl3945

 it hangs for half a minute, then I get this error:

 iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection
 iwl3945: iwlwifi-3945-1.ucode firmware file req failed: Reason -2
 iwl3945: Could not read microcode: -2
 ACPI: PCI interrupt for device :10:00.0 disabled
 iwl3945: probe of :10:00.0 failed with error -2

 I'm using firmware-iwlwifi 0.12, with a linux-2.6.24 i686 debian
 custom kernel.

 Regards.

Hi, 

a new firmware-iwlwifi package is available in unstable. Please try this new 
package and update your linux-image to get the latest iwlwifi driver and 
report back if the problem is still alive.

N.B. I don't get any error with the firmware...

Regards, 

OdyX



-- 
Didier Raboud, proud Debian user.
CH-1802 Corseaux
[EMAIL PROTECTED]


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


Bug#486089: linux-image-2.6.26-rc5-amd64: ssh connections randomly hang

2008-06-13 Thread Didier Raboud
Package: linux-image-2.6.26-rc5-amd64
Version: 2.6.26~rc5-1~experimental.1~snapshot.11597
Severity: normal

Latest working kernel version: 2.6.25-2
Earliest failing kernel version: 2.6.26-rc5
Distribution: Debian (Lenny + Sid)
Hardware Environment: amd64 (Dell Latitude D630)
Software Environment: KDE
Problem Description:

With kernel version 2.6.26-rc5, the ssh connections to remote servers
randomly
hang (no error message). No amelioration despite the activation of
ServerAliveInterval on both sides.

Steps to reproduce:

Connect to a remote ssh server and do some stuff. After some time, the
connection will hang.

Please ask for details.

Regards, 
OdyX

-- Package-specific info:

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (700, 'testing'), (700, 'stable'), (600, 'unstable'), (50, 
'experimental'), (50, 'unstable'), (50, 'testing'), (50, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages linux-image-2.6.26-rc5-amd64 depends on:
ii  debconf [debconf-2.0] 1.5.22 Debian configuration management sy
ii  initramfs-tools [linux-initra 0.92b  tools for generating an initramfs
ii  module-init-tools 3.4-1  tools for managing Linux kernel mo

linux-image-2.6.26-rc5-amd64 recommends no packages.

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


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#485789: initramfs-tools: With crypted LVM, tries to start LVM before decryption

2008-06-11 Thread Didier Raboud
Package: initramfs-tools
Version: 0.92b
Severity: normal

Hi, 

I installed LennyBeta2 (under Qemu) with the graphical installer and 
chose crypted LVM. The thing is that on boot, the initramfs firstly tries 
to open (initiate ?) the LVM before it actually has access to it (because it 
is encrypted).

It results in an error (attached) which could be avoided if the encrypted 
partition is opened before the LVM is initiated.

Regards, 

Didier


-- Package-specific info:
-- /proc/cmdline
root=/dev/mapper/debian-root ro quiet

-- /proc/filesystems
ext3

-- lsmod
Module  Size  Used by
battery19976  0 
sbs20880  0 
sbshc  12032  1 sbs
dock   16032  0 
ac 11400  0 
video  25620  0 
output  8704  1 video
container   9856  0 
loop   22788  0 
parport_pc 42408  0 
parport44812  1 parport_pc
psmouse45724  0 
pcspkr  7808  0 
serio_raw  11908  0 
i2c_piix4  13708  0 
i2c_core   29824  1 i2c_piix4
button 13984  0 
evdev  17024  2 
ext3  139024  6 
jbd55976  1 ext3
mbcache13952  1 ext3
sha256_generic 13312  0 
aes_x86_64 29992  2 
aes_generic31040  0 
cbc 9088  1 
blkcipher  11780  1 cbc
dm_crypt   18568  1 
dm_mirror  27008  0 
dm_snapshot21960  0 
dm_mod 67832  18 dm_crypt,dm_mirror,dm_snapshot
ide_cd 44704  0 
cdrom  39464  1 ide_cd
ide_disk   20992  3 
8139too33024  0 
ata_generic13060  0 
libata162992  1 ata_generic
scsi_mod  170296  1 libata
floppy 4  0 
8139cp 28672  0 
mii10240  2 8139too,8139cp
uhci_hcd   30112  0 
piix   13316  0 [permanent]
generic 9732  0 [permanent]
ide_core  144920  4 ide_cd,ide_disk,piix,generic
thermal22688  0 
processor  45032  1 thermal
fan 9864  0 

-- /etc/kernel-img.conf
# Kernel image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
relative_links = yes
do_bootloader = no
do_bootfloppy = no
do_initrd = yes
link_in_boot = no
postinst_hook = update-grub
postrm_hook   = update-grub

-- /etc/initramfs-tools/initramfs.conf
MODULES=most
BUSYBOX=y
KEYMAP=n
BOOT=local
DEVICE=eth0
NFSROOT=auto

-- /etc/crypttab
hda2_crypt /dev/hda2 none luks


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

Kernel: Linux 2.6.24-1-amd64 (SMP w/1 CPU core)
Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages initramfs-tools depends on:
ii  cpio  2.9-13 GNU cpio -- a program to manage 
ar
ii  findutils 4.4.0-2utilities for finding 
files--find,
ii  klibc-utils   1.5.9-2small utilities built with klibc 
f
ii  module-init-tools 3.4-1  tools for managing Linux kernel 
mo
ii  udev  0.114-2/dev/ and hotplug management 
daemo

Versions of packages initramfs-tools recommends:
ii  busybox   1:1.9.2-3  Tiny utilities for small and 
embed

-- no debconf information
-- 
Didier Raboud, proud Debian user.
CH-1802 Corseaux
[EMAIL PROTECTED]
attachment: initramfs_ordering.png

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


Bug#469095: 469095: Wifi led does not turns on

2008-06-05 Thread Didier Raboud
# package firmware-iwlwifi
clone 469095 -1
reassign -1 linux-2.6
found -1 2.6.25-2
tag -1 + pending upstream
# Has been reported as corrected in the future 2.6.26
thanks

Le lundi 7 avril 2008 18:50:56 David L. Anselmi, vous avez écrit :
 There's a discussion of this bug and patches at:

 http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1209

 Probably this should be reassigned to the kernel.

 Dave

Hi, 

this issue has been reported to be fixed in the coming 2.6.26 which will land 
in experimental soon.

Regards, 

Didier

-- 
Didier Raboud
1802 Corseaux
[EMAIL PROTECTED]

--
* Pensez à la planète : n'imprimez ce courriel que si strictement nécessaire !
* Ce courriel est signé numériquement par OpenPGP.
ID: E9A278F0 FP: 5174 DF20 B82E 613D C14A A92B C16D 679C E9A2 78F0


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


Bug#483375: linux-image-2.6.25-2-amd64: 2.6.25-4 broke cpu frequency scaling

2008-05-28 Thread Didier Raboud
Package: linux-image-2.6.25-2-amd64
Version: 2.6.25-4
Severity: normal

Hi, 

with latest update of linux-image-2.6.25-2-amd4, I lost the folders
/sys/devices/system/cpu/cpu*/cpufreq and thus, kpowersave does not show
the frequency used and does not allow to chose between ondemand,
performance, powersave as it did before.

Regards, 

Didier

-- Package-specific info:
** Version:
Linux version 2.6.25-2-amd64 (Debian 2.6.25-4) ([EMAIL PROTECTED]) (gcc version 
4.1.3 20080420 (prerelease) (Debian 4.1.2-22)) #1 SMP Tue May 27 12:45:24 UTC 
2008

** Command line:
BOOT_IMAGE=(hd0,1)/vmlinuz-2.6.25-2-amd64 root=/dev/mapper/Tamino-Root ro quiet 
vga=792

** Not tainted

** Kernel log:
[12840.499674] usb 7-2: new full speed USB device using uhci_hcd and address 24
[12920.661435] CPU0 attaching NULL sched-domain.
[12920.661448] CPU1 attaching NULL sched-domain.
[12920.680336] CPU0 attaching sched-domain:
[12920.680348]  domain 0: span 0003
[12920.680353]   groups: 0001 0002
[12920.680364]   domain 1: span 0003
[12920.680370]groups: 0003
[12920.680378]domain 2: span 0003
[12920.680385] groups: 0003
[12920.680394] CPU1 attaching sched-domain:
[12920.680399]  domain 0: span 0003
[12920.680405]   groups: 0002 0001
[12920.680415]   domain 1: span 0003
[12920.680421]groups: 0003
[12920.680428]domain 2: span 0003
[12920.680434] groups: 0003
[12840.674052] usb 7-2: configuration #1 chosen from 1 choice
[12840.677112] usb 7-2: New USB device found, idVendor=0483, idProduct=2016
[12840.677123] usb 7-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[12840.677129] usb 7-2: Product: Biometric Coprocessor
[12840.677133] usb 7-2: Manufacturer: STMicroelectronics
[12840.912834] usb 7-1.2: new full speed USB device using uhci_hcd and address 
25
[12841.031017] usb 7-1.2: configuration #1 chosen from 1 choice
[12841.034200] usb 7-1.2: New USB device found, idVendor=0b97, idProduct=7772
[12841.034210] usb 7-1.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[12841.034216] usb 7-1.2: Product: O2Micro CCID SC Reader
[12841.034220] usb 7-1.2: Manufacturer: O2
[12844.683098] CPU0 attaching NULL sched-domain.
[12844.683111] CPU1 attaching NULL sched-domain.
[12844.703771] CPU0 attaching sched-domain:
[12844.703783]  domain 0: span 0003
[12844.703788]   groups: 0001 0002
[12844.703796]   domain 1: span 0003
[12844.703800]groups: 0003
[12844.703807] CPU1 attaching sched-domain:
[12844.703811]  domain 0: span 0003
[12844.703815]   groups: 0002 0001
[12844.703821]   domain 1: span 0003
[12844.703825]groups: 0003
[12850.444863] wlan0: no IPv6 routers present
[14131.680235] CPU0 attaching NULL sched-domain.
[14131.680250] CPU1 attaching NULL sched-domain.
[14131.703368] CPU0 attaching sched-domain:
[14131.703381]  domain 0: span 0003
[14131.703386]   groups: 0001 0002
[14131.703396]   domain 1: span 0003
[14131.703402]groups: 0003
[14131.703412] CPU1 attaching sched-domain:
[14131.703417]  domain 0: span 0003
[14131.703423]   groups: 0002 0001
[14131.703433]   domain 1: span 0003
[14131.703439]groups: 0003
[14280.205220] hub 4-0:1.0: unable to enumerate USB device on port 2
[14280.445219] usb 5-2: new low speed USB device using uhci_hcd and address 3
[14195.520990] usb 5-2: configuration #1 chosen from 1 choice
[14195.561666] input: Logitech USB Receiver as /class/input/input12
[14195.607816] input,hidraw0: USB HID v1.11 Mouse [Logitech USB Receiver] on 
usb-:00:1d.0-2
[14195.640787] input: Logitech USB Receiver as /class/input/input13
[14195.710682] input,hiddev96,hidraw1: USB HID v1.11 Device [Logitech USB 
Receiver] on usb-:00:1d.0-2
[14195.710847] usb 5-2: New USB device found, idVendor=046d, idProduct=c521
[14195.710853] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[14195.710858] usb 5-2: Product: USB Receiver
[14195.710862] usb 5-2: Manufacturer: Logitech
[14531.170340] CPU0 attaching NULL sched-domain.
[14531.170352] CPU1 attaching NULL sched-domain.
[14531.202046] CPU0 attaching sched-domain:
[14531.202057]  domain 0: span 0003
[14531.202063]   groups: 0001 0002
[14531.202074]   domain 1: span 0003
[14531.202080]groups: 0003
[14531.202089] CPU1 attaching sched-domain:
[14531.202094]  domain 0: span 0003
[14531.202100]   groups: 0002 0001
[14531.202111]   domain 1: span 0003
[14531.202117]groups: 0003
[14449.683509] CPU0 attaching NULL sched-domain.
[14449.683523] CPU1 attaching NULL sched-domain.
[14449.692406] CPU0 attaching sched-domain:
[14449.692418]  domain 0: span 0003
[14449.692423]   groups: 0001 0002
[14449.692430]   domain 1: span 0003
[14449.692434]groups: 0003
[14449.692441] CPU1 attaching sched-domain:
[14449.692445]  domain 0: span 0003
[14449.692449]   groups: 0002 0001
[14449.692455]   domain 1: span 0003

Bug#459767: linux-source-2.6.23: FTBFS with gcc-4.3

2008-05-27 Thread Didier Raboud
Le mercredi 21 mai 2008 21:14:05 maximilian attems, vous avez écrit :
 Version: 2.6.25-1

 no longer the case and it even boots fine! :)

Hi,

Just wondering (as user)...

Isn't the gcc-4.3 mandatory for all packages in Lenny (so as well for the 
kernel) ? So why not enabling it per default as soon as possible (at least on 
arches where it builds...) ?

$ apt-cache showsrc linux-image-2.6.25-2-amd64 | grep gcc
Build-Depends: debhelper (= 4.1.0), module-init-tools, dpkg-dev (= 1.10.23), 
sparc-utils [sparc], kernel-package (= 10.063), python, gcc-4.1 [alpha amd64 
arm armel hppa i386 ia64 mips mipsel powerpc s390 sparc], binutils-hppa64 
[hppa], gcc-4.1-hppa64 [hppa], gcc-3.3 [m68k]
Build-Depends: debhelper (= 4.1.0), module-init-tools, dpkg-dev (= 1.10.23), 
sparc-utils [sparc], kernel-package (= 10.063), python, gcc-4.1 [alpha amd64 
arm armel hppa i386 ia64 mips mipsel powerpc s390 sparc], binutils-hppa64 
[hppa], gcc-4.1-hppa64 [hppa], gcc-3.3 [m68k]

Visibly, it is still gcc-4.1 for most of the architectures and event gcc-3.3 
for m68k.

Thanks for your time ! Regards, 

Didier Raboud


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


Re: 2.6.25-rc8 : hibernation sometimes not resuming on Dell Latitude D630 (was: -rc7)

2008-04-10 Thread Didier Raboud
Le jeudi, 3 avril 2008 17.48:57 Rafael J. Wysocki, vous avez écrit :
 On Thursday, 3 of April 2008, Didier Raboud wrote:
  Le mercredi, 2 avril 2008 14.06:29 Didier Raboud, vous avez écrit :
   Le mardi, 1 avril 2008 23.22:35 Rafael J. Wysocki, vous avez écrit :
On Tuesday, 1 of April 2008, Didier Raboud wrote:
 Le mardi, 1 avril 2008 23.11:15 Rafael J. Wysocki, vous avez écrit :
  (...)
  Can you please test the in-kernel hibernation, then?
 
  Rafael

 Hi,

 would like to. How ?

 # echo -n disk  /sys/power/state
   
Yes, should work without the -n, too.  Of course, you have to use
the 'resume=' kernel command line argument for this to work.
   
Perhaps increase the console log level before that.
   
Thanks,
Rafael
  
   Ok. I found a better way to do it : just uninstall uswsusp and let
   kpowersave use hal to use suspend :-)
  
   Anyway, so far so good (with USB_SUSPEND not set), no hang. I will test
   with USB_SUSPEND set and the incoming 2.6.25-rc8.
  
   Regards,
  
   Didier
 
  So far so good too with stock Debian Kernel (2.7.25-rc7-amd64) with
  USB_SUSPEND set. No hang.
 
  The kernel suspend is less user-friendly than uswsusp though...
 
  So I bet there is a bug in uswsusp's kernel part ?

 It's almost the same as the in-kernel one, especially as far as the resume
 is concerned.  The simplest explanation coming to mind is that the image is
 somehow damaged in the uswsusp case.

 You can use the uswsusp's checksumming to verify that, though.

 Thanks,
 Rafael

Hi, 

I upgraded my uswsusp to 0.8 and my kernel to 2.6.25-rc8 from Debian. I 
activated the checksumming. I have hangs _again_ (I probably always had...).

Here's my /etc/uswsusp.conf :
# 
# /etc/uswsusp.conf(8) -- Configuration file for s2disk/s2both
resume device = /dev/mapper/Tamino-swap_1
compress = y
early writeout = y
image size = 967540654
shutdown method = platform
compute checksum = y
# 

I don't know how I can help further... I will try without early writeout.

Any help would be greatly appreciated !

Best regards, 

Didier

-- 
Didier Raboud
Cornalles 2
1802 Corseaux
[EMAIL PROTECTED]
079 480 67 82


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


Re: 2.6.25-rc7 : hibernation sometimes not resuming on Dell Latitude D630

2008-04-03 Thread Didier Raboud
Le mercredi, 2 avril 2008 14.06:29 Didier Raboud, vous avez écrit :
 Le mardi, 1 avril 2008 23.22:35 Rafael J. Wysocki, vous avez écrit :
  On Tuesday, 1 of April 2008, Didier Raboud wrote:
   Le mardi, 1 avril 2008 23.11:15 Rafael J. Wysocki, vous avez écrit :
(...)
Can you please test the in-kernel hibernation, then?
   
Rafael
  
   Hi,
  
   would like to. How ?
  
   # echo -n disk  /sys/power/state
 
  Yes, should work without the -n, too.  Of course, you have to use the
  'resume=' kernel command line argument for this to work.
 
  Perhaps increase the console log level before that.
 
  Thanks,
  Rafael

 Ok. I found a better way to do it : just uninstall uswsusp and let
 kpowersave use hal to use suspend :-)

 Anyway, so far so good (with USB_SUSPEND not set), no hang. I will test
 with USB_SUSPEND set and the incoming 2.6.25-rc8.

 Regards,

 Didier

So far so good too with stock Debian Kernel (2.7.25-rc7-amd64) with 
USB_SUSPEND set. No hang.

The kernel suspend is less user-friendly than uswsusp though...

So I bet there is a bug in uswsusp's kernel part ?

Regards, 

Didier


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


Re: 2.6.25-rc7 : hibernation sometimes not resuming on Dell Latitude D630

2008-04-02 Thread Didier Raboud
Le mardi, 1 avril 2008 23.22:35 Rafael J. Wysocki, vous avez écrit :
 On Tuesday, 1 of April 2008, Didier Raboud wrote:
  Le mardi, 1 avril 2008 23.11:15 Rafael J. Wysocki, vous avez écrit :
   (...)
   Can you please test the in-kernel hibernation, then?
  
   Rafael
 
  Hi,
 
  would like to. How ?
 
  # echo -n disk  /sys/power/state

 Yes, should work without the -n, too.  Of course, you have to use the
 'resume=' kernel command line argument for this to work.

 Perhaps increase the console log level before that.

 Thanks,
 Rafael

Ok. I found a better way to do it : just uninstall uswsusp and let 
kpowersave use hal to use suspend :-)

Anyway, so far so good (with USB_SUSPEND not set), no hang. I will test with 
USB_SUSPEND set and the incoming 2.6.25-rc8.

Regards, 

Didier


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


Re: 2.6.25-rc7 : hibernation sometimes not resuming on Dell Latitude D630

2008-04-01 Thread Didier Raboud
Le lundi, 31 mars 2008 23.03:16 Didier Raboud, vous avez écrit :
 Le lundi, 31 mars 2008 22.29:20 Rafael J. Wysocki, vous avez écrit :
  On Monday, 31 of March 2008, Didier Raboud wrote:
   Le lundi, 31 mars 2008 19.36:00 Didier Raboud, vous avez écrit :
Le lundi, 31 mars 2008 19.24:55 maximilian attems, vous avez écrit :
 On Mon, Mar 31, 2008 at 07:03:13PM +0200, Didier Raboud wrote:
 snipp

Attached are a 2.6.25-rc7 and a 2.6.24 dmesg's after two
successful hibernate/resume cycles.
  
   Could you please check if the problem is still present if you
   boot with acpi_new_pts_ordering kernel command line argument?
 
  By the way, I just added acp_new_pts_ordering at the end of the
  Grub line beginning by linux (hd0,1)/vmlinuz(...). Is that
  correct ?

 seems strange you should add it to the kopt line and then kick as
 root update-grub

 # kopt=root=/dev/sda1 ro
 it should land
 kernel  /boot/vmlinuz-2.6.25-rc7-amd64 root=/dev/sda1 ro
   
Well... I'm using Grub2 (grub-pc). I altered the boot option at boot
time but forgot to check /proc/cmdline. Will try again and report
back.
   
Regards,
   
Didier
  
   Hi,
  
   I tried again and ensured that /proc/cmdline 's end was
   acpi_new_pts_ordering . It did work for 2-3 hibernation, but then
   failed.
 
  Well, there were quite a lot of suspend-related changes between 2.6.24
  and now.
 
  Hmm, do you have CONFIG_USB_SUSPEND set in .config by chance?
 
  Rafael

 I do (Debian default option)... I will build a kernel without it and retry.

 Didier

Hi again. 

I compiled the same kernel with CONFIG_USB_SUSPEND not set. After 6 
hibernations, I haven't had a problem for now.

Regards,

Didier


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


Re: 2.6.25-rc7 : hibernation sometimes not resuming on Dell Latitude D630

2008-04-01 Thread Didier Raboud
Le mardi, 1 avril 2008 08.18:57 Didier Raboud, vous avez écrit :
 Le lundi, 31 mars 2008 23.03:16 Didier Raboud, vous avez écrit :
  Le lundi, 31 mars 2008 22.29:20 Rafael J. Wysocki, vous avez écrit :
   On Monday, 31 of March 2008, Didier Raboud wrote:
Le lundi, 31 mars 2008 19.36:00 Didier Raboud, vous avez écrit :
 Le lundi, 31 mars 2008 19.24:55 maximilian attems, vous avez écrit :
  On Mon, Mar 31, 2008 at 07:03:13PM +0200, Didier Raboud wrote:
  snipp
 
 Attached are a 2.6.25-rc7 and a 2.6.24 dmesg's after two
 successful hibernate/resume cycles.
   
Could you please check if the problem is still present if you
boot with acpi_new_pts_ordering kernel command line argument?
  
   By the way, I just added acp_new_pts_ordering at the end of the
   Grub line beginning by linux (hd0,1)/vmlinuz(...). Is that
   correct ?
 
  seems strange you should add it to the kopt line and then kick as
  root update-grub
 
  # kopt=root=/dev/sda1 ro
  it should land
  kernel  /boot/vmlinuz-2.6.25-rc7-amd64 root=/dev/sda1 ro

 Well... I'm using Grub2 (grub-pc). I altered the boot option at
 boot time but forgot to check /proc/cmdline. Will try again and
 report back.

 Regards,

 Didier
   
Hi,
   
I tried again and ensured that /proc/cmdline 's end was
acpi_new_pts_ordering . It did work for 2-3 hibernation, but then
failed.
  
   Well, there were quite a lot of suspend-related changes between 2.6.24
   and now.
  
   Hmm, do you have CONFIG_USB_SUSPEND set in .config by chance?
  
   Rafael
 
  I do (Debian default option)... I will build a kernel without it and
  retry.
 
  Didier

 Hi again.

 I compiled the same kernel with CONFIG_USB_SUSPEND not set. After 6
 hibernations, I haven't had a problem for now.

 Regards,

 Didier

Hi again again,

It hung after the 10th hibernation...

I wonder if the problem would not be of Debian's uswsusp binary, because tty1 
tells me that the image is successfully loaded but I just can't act on my box 
afterwards.

There is a bug open in the Debian BTS requesting a packaging of the new 
upstream version (0.8) but the maintainer is told to be too busy to handle it 
for now.

Don't know...

Regards, 

Didier


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


Re: 2.6.25-rc7 : hibernation sometimes not resuming on Dell Latitude D630

2008-03-31 Thread Didier Raboud
Le lundi, 31 mars 2008 18.33:19 Rafael J. Wysocki, vous avez écrit :
 On Monday, 31 of March 2008, Didier Raboud wrote:
  Hi,

 Hi,

  I'm using the latest Debian 2.6.25-rc7 kernel [0] and I have big troubles
  with hibernation. With this version, the hibernation (suspend on disk) is
  sometimes not resuming correctly. The only thing I get is a blinking
  cursor at the top-left of the screen. The problem is that it is not
  easily reproducible : sometimes it works, sometimes not.
 
  AFAIK, 2.6.24 is not affected, but 2.6.25-rc6 and -rc7 (at least) are.
 
  I'm using a Dell Latitude D630. (lspci attached).
 
  Attached are a 2.6.25-rc7 and a 2.6.24 dmesg's after two successful
  hibernate/resume cycles.

 Could you please check if the problem is still present if you boot with
 acpi_new_pts_ordering kernel command line argument?

 Thanks,
 Rafael

Hi. 

It did not help. I had to test 4 hibernation/resume cycles to see the resume 
fail.

By the way, I just added acp_new_pts_ordering at the end of the Grub line 
beginning by linux (hd0,1)/vmlinuz(...). Is that correct ?

Regards, 

Didier


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


Re: 2.6.25-rc7 : hibernation sometimes not resuming on Dell Latitude D630

2008-03-31 Thread Didier Raboud
Le lundi, 31 mars 2008 19.24:55 maximilian attems, vous avez écrit :
 On Mon, Mar 31, 2008 at 07:03:13PM +0200, Didier Raboud wrote:
 snipp

Attached are a 2.6.25-rc7 and a 2.6.24 dmesg's after two successful
hibernate/resume cycles.
  
   Could you please check if the problem is still present if you boot with
   acpi_new_pts_ordering kernel command line argument?
 
  By the way, I just added acp_new_pts_ordering at the end of the Grub line
  beginning by linux (hd0,1)/vmlinuz(...). Is that correct ?

 seems strange you should add it to the kopt line and then kick as root
 update-grub

 # kopt=root=/dev/sda1 ro
 it should land
 kernel  /boot/vmlinuz-2.6.25-rc7-amd64 root=/dev/sda1 ro

Well... I'm using Grub2 (grub-pc). I altered the boot option at boot time but 
forgot to check /proc/cmdline. Will try again and report back.

Regards, 

Didier


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


Re: 2.6.25-rc7 : hibernation sometimes not resuming on Dell Latitude D630

2008-03-31 Thread Didier Raboud
Le lundi, 31 mars 2008 19.36:00 Didier Raboud, vous avez écrit :
 Le lundi, 31 mars 2008 19.24:55 maximilian attems, vous avez écrit :
  On Mon, Mar 31, 2008 at 07:03:13PM +0200, Didier Raboud wrote:
  snipp
 
 Attached are a 2.6.25-rc7 and a 2.6.24 dmesg's after two successful
 hibernate/resume cycles.
   
Could you please check if the problem is still present if you boot
with acpi_new_pts_ordering kernel command line argument?
  
   By the way, I just added acp_new_pts_ordering at the end of the Grub
   line beginning by linux (hd0,1)/vmlinuz(...). Is that correct ?
 
  seems strange you should add it to the kopt line and then kick as root
  update-grub
 
  # kopt=root=/dev/sda1 ro
  it should land
  kernel  /boot/vmlinuz-2.6.25-rc7-amd64 root=/dev/sda1 ro

 Well... I'm using Grub2 (grub-pc). I altered the boot option at boot time
 but forgot to check /proc/cmdline. Will try again and report back.

 Regards,

 Didier

Hi, 

I tried again and ensured that /proc/cmdline 's end was 
acpi_new_pts_ordering . It did work for 2-3 hibernation, but then failed.

Regards, 

Didier


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


Re: 2.6.25-rc7 : hibernation sometimes not resuming on Dell Latitude D630

2008-03-31 Thread Didier Raboud
Le lundi, 31 mars 2008 22.29:20 Rafael J. Wysocki, vous avez écrit :
 On Monday, 31 of March 2008, Didier Raboud wrote:
  Le lundi, 31 mars 2008 19.36:00 Didier Raboud, vous avez écrit :
   Le lundi, 31 mars 2008 19.24:55 maximilian attems, vous avez écrit :
On Mon, Mar 31, 2008 at 07:03:13PM +0200, Didier Raboud wrote:
snipp
   
   Attached are a 2.6.25-rc7 and a 2.6.24 dmesg's after two
   successful hibernate/resume cycles.
 
  Could you please check if the problem is still present if you
  boot with acpi_new_pts_ordering kernel command line argument?

 By the way, I just added acp_new_pts_ordering at the end of the
 Grub line beginning by linux (hd0,1)/vmlinuz(...). Is that
 correct ?
   
seems strange you should add it to the kopt line and then kick as
root update-grub
   
# kopt=root=/dev/sda1 ro
it should land
kernel  /boot/vmlinuz-2.6.25-rc7-amd64 root=/dev/sda1 ro
  
   Well... I'm using Grub2 (grub-pc). I altered the boot option at boot
   time but forgot to check /proc/cmdline. Will try again and report back.
  
   Regards,
  
   Didier
 
  Hi,
 
  I tried again and ensured that /proc/cmdline 's end was
  acpi_new_pts_ordering . It did work for 2-3 hibernation, but then failed.

 Well, there were quite a lot of suspend-related changes between 2.6.24 and
 now.

 Hmm, do you have CONFIG_USB_SUSPEND set in .config by chance?

 Rafael

I do (Debian default option)... I will build a kernel without it and retry. 

Didier


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


Bug#461924: (no subject)

2008-01-30 Thread Didier Raboud
Hi, 

I confirm this behaviour with latest 2.6.24 kernel. It happens once in a 
while, but still happens.

Regards, 

Didier


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


Bug#431314: ALSA: snd_hda_intel: Intel HDA from SantaRosa platform not recognised

2007-07-01 Thread Didier Raboud
Package: linux-2.6
Version: 2.6.21-5
Severity: normal

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

Hi, 

with newer versions of the Linux kernel, it is not possible to get any sound 
from this card:

$ lspci | grep Audio
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio 
Controller (rev 02)

It is a Dell Latitude D630, running the brand new Santa Rosa platform from 
Intel. Sound works under 2.6.18, but only with two sliders in alsamixer and 
no sound from internal speakers (only headphones).

This is the error given by the kernel on boot time :

hda_intel: azx_get_response timeout, switching to polling mode...
hda_intel: azx_get_response timeout, switching to single_cmd mode...
hda_codec: No auto-config is available, default to model=ref
hda-intel: no codecs initialized

And it does not work...

I'm running 2.6.22-rc6 too and this kernel does even not solve this issue. I'm 
ready to give any necessary information.

Best regards, 

Didier Raboud

--- System information. ---
Architecture: amd64
Kernel:   Linux 2.6.21-2-amd64

Debian Release: 4.0
  700 stable  security.debian.org 
  700 stable  mirror.switch.ch 
  650 testing mirror.switch.ch 
  600 unstablemirror.switch.ch 
   50 unstablemirror.switch.ch 
   50 testing mirror.switch.ch 
   50 stable  mirror.switch.ch 
   50 stable  debian.netcologne.de 
   50 kernel-dists-trunk kernel-archive.buildserver.net 
   50 kernel-dists-sid kernel-archive.buildserver.net 
   50 kernel-dists-etch kernel-archive.buildserver.net 

--- Package information. ---
Depends   (Version) | Installed
===-+-===
| 



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#431314: ALSA: snd_hda_intel: Intel HDA from SantaRosa platform not recognised

2007-07-01 Thread Didier Raboud
Le dimanche 1 juillet 2007 23:05, maximilian attems a écrit :
 On Sun, Jul 01, 2007 at 05:59:41PM +0200, Didier Raboud wrote:
  $ lspci | grep Audio
  00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio
  Controller (rev 02)
 
  It is a Dell Latitude D630, running the brand new Santa Rosa platform
  from Intel. Sound works under 2.6.18, but only with two sliders in
  alsamixer and no sound from internal speakers (only headphones).
 
  This is the error given by the kernel on boot time :
 
  hda_intel: azx_get_response timeout, switching to polling mode...
  hda_intel: azx_get_response timeout, switching to single_cmd mode...
  hda_codec: No auto-config is available, default to model=ref
  hda-intel: no codecs initialized
 
  And it does not work...
 
  I'm running 2.6.22-rc6 too and this kernel does even not solve this
  issue. I'm ready to give any necessary information.

 hmm seems alsa bug day,
 please notify alsa upstream bug tracking system.

 we don't carry any alsa specific patch.

 regards

Hi, 

then... Similar bugs already reported upstream:

0003207: ALC883 hda-intel no sound via the speakers, only sound comes from the 
shared SPDIF/Headphone jack Aspire 9810 laptop. [0]

0003075: No soundoutput on my Speakers nor on Headphones. [1]

0003153: snd-hda-intel, 9205, Dell D830, no sound through speakers, only 
headphones, tried latest CVS, no dice. [2]

I'll check if completion on these bugs is needed.

Regards, 

Didier

[0] https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3207
[1] https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3075
[2] https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3153



Bug#430646: module missing from amd64 package too.

2007-06-27 Thread Didier Raboud
Package: ipw3945-modules-2.6.21-1-amd64

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

the module is missing from the amd64 version too.

$ dpkg -L ipw3945-modules-2.6.21-1-amd64
/.
/lib
/lib/modules
/lib/modules/2.6.21-1-amd64
/lib/modules/2.6.21-1-amd64/contrib
/lib/modules/2.6.21-1-amd64/contrib/ipw3945
/usr
/usr/share
/usr/share/doc
/usr/share/doc/ipw3945-modules-2.6.21-1-amd64
/usr/share/doc/ipw3945-modules-2.6.21-1-amd64/copyright
/usr/share/doc/ipw3945-modules-2.6.21-1-amd64/changelog.Debian.gz


regards, 

Didier

--- System information. ---
Architecture: amd64
Kernel:   Linux 2.6.18-4-amd64

Debian Release: 4.0
  700 stable  security.debian.org 
  700 stable  mirror.switch.ch 
  650 testing mirror.switch.ch 
  600 unstablemirror.switch.ch 

--- Package information. ---
Depends   (Version) | Installed
===-+-===
linux-modules-2.6.21-1-amd64| 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]