Re: Increasing minimum 'i386' processor

[Raphael Hertzog]

On Sat, 19 Nov 2011, Ben Hutchings wrote:
> Also possibly:
> 6. DM&P/SiS Vortex86 and Vortex86SX.  These supposedly have all
>586-class features except an FPU, and we could probably keep FPU
>emulation for them.

FWIW, I do run Debian on such systems albeit with a custom kernel.
Given those CPU tend to be used in an "embedded" context I guess
it's ok if the official kernel does not support them. But it would be
nice if Debian's userspace could be kept compatible. Not sure what this
requires though...

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Pre-order a copy of the Debian Administrator's Handbook and help
liberate it: http://debian-handbook.info/go/ulule-rh/


-- 
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/2020074047.gi3...@rivendell.home.ouaza.com

Re: Increasing minimum 'i386' processor

[Guillem Jover]

Hi!

On Sat, 2011-11-19 at 22:42:11 +, Ben Hutchings wrote:
> The i386 architecture was the first in Linux and in Debian, but we have
> long since dropped support for the original i386-compatible processors
> and now require a minimum of a 486-class processor.
> 
> I think it is time to increase the minimum requirement to 586-class, if
> not for wheezy then immediately after.  (Later it should be increased
> further, and eventually i386 should be reduced to a partial architecture
> that may be installed on amd64 systems.)  This would allow the use of
> optimisations and new instructions throughout userland that improve
> performance for the vast majority of users.

It seems gcc has been targetting i586 instruction set by default since
gcc 4.4.0-1~exp1, although the triplet was not changed to match. On the
discussion regarding multiarch tuples I proposed we should switch the
triplet back to i386-linux-gnu to avoid this kind of confusion, fix the
internal inconsistency and the one with other architectures (which do
not track the base instruction set in the triplet) and so that we can
use them directly as the multiarch tuples.

For more details please see:

  
  

regards,
guillem


-- 
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/202810.ga20...@gaara.hadrons.org

Increasing minimum 'i386' processor

[Ben Hutchings]

The i386 architecture was the first in Linux and in Debian, but we have
long since dropped support for the original i386-compatible processors
and now require a minimum of a 486-class processor.

I think it is time to increase the minimum requirement to 586-class, if
not for wheezy then immediately after.  (Later it should be increased
further, and eventually i386 should be reduced to a partial architecture
that may be installed on amd64 systems.)  This would allow the use of
optimisations and new instructions throughout userland that improve
performance for the vast majority of users.

The 486-class processors that would no longer be supported are:
1. All x86 processors with names including '486'
2. AMD Am5x86
3. Cyrix/IBM/ST 5x86, 6x86 and MediaGX
4. UMC U5D and U5S
5. AMD/NSC Geode GX1, Geode SC1100, Elan SC4xx and SC5xx
Also possibly:
6. DM&P/SiS Vortex86 and Vortex86SX.  These supposedly have all
   586-class features except an FPU, and we could probably keep FPU
   emulation for them.

So far as I know, all processors in groups 1-5 have been out of
production for several years.  Soekris still advertises boards using the
Geode SC1100 and Elan SC520, but they seem quite uncompetitive with
ARM-based systems and at least the SC1100-based products are being
EOL'd.

Starting from version 2.6.24 or earlier (early 2008), Debian '486'
kernel packages had a bug that caused them to crash on boot on 486-class
processors, but this was not reported until early 2009 (#511703),
suggesting that there were few users with such systems.  Debian 7.0
'wheezy' should be released in late 2012 or early 2013 and in the
intervening 4 years the numbers of running systems with such a processor
will have declined still further.

Ben.

-- 
Ben Hutchings
The world is coming to an end.  Please log off.


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

Bug#645308: tg3 broken for NetXtreme 5714S in squeeze 6.0.3 installer

[Marc Haber]

On Sat, Nov 19, 2011 at 07:37:16PM +, Ben Hutchings wrote:
> But I can provide you with a rebuilt tg3.ko so you can test just that
> change in the installer like you did previously.

Already forgot about that. Yes, of course, that would be a way to go.
No need to hurry, I won't be on site before tuesday.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany  |  lose things."Winona Ryder | Fon: *49 621 31958061
Nordisch by Nature |  How to make an American Quilt | Fax: *49 621 31958062



-- 
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/2019201315.gg4...@torres.zugschlus.de

Bug#649304: needed for 686-pae kernels

[Will Set]

 Saturday, November 19, 2011 2:32 PM Jonathan Nieder : wrote
>forcemerge 627019 649304
>quit
>
>Hi Will,
>
>Will Set wrote:
>
>> [Subject:  needed for 686-pae kernels]
>
>You haven't described the actual symptoms here.  I assume that they
>are segfaults and hangs, as before?

Yes, the kernel still hangs early in boot.  The difference being 
the kernel hang without   looks to me to be more 
consistent now, than when I originally reported
the problem with the 2.6.39-rc7-686 kernel.

>
>> I first noticed this issue using 2.6.38-rc5-686 and 2.6.38-rc6-686. 
>> Although, 2.6.38-1-686 worked out of the box, the regession showed again 
>> using 2.6.39-rcX kernels,
>> and continues to show using all 686-pae kernels.
>> Adding  to the kernel commandline works around the issue.
>>
>> Using 486 kernels is another workaround to this issue.
>
>Please send full "dmesg" output from booting up and reproducing the
>bug.  Attaching "acpidump" output would be useful, too.

I'll also be away from my desk for a few days, and will followup, 
with dmesg and acpidump, as soon as I return.

Best Regards,
Will


>
>> see: #627019  linux-image-2.6.39-rc7-686-pae: several kernel hangs ... 
>
>Thanks for filing a separate bug so we can keep track of the
>information about each machine separately.  I'm marking the two
>reports as related for easy reference.
>
>Thanks and hope that helps,
>Jonathan

Bug#645308: tg3 broken for NetXtreme 5714S in squeeze 6.0.3 installer

[Ben Hutchings]

On Sat, 2011-11-19 at 19:45 +0100, Marc Haber wrote:
> On Fri, Nov 18, 2011 at 11:54:35AM -0800, Matt Carlson wrote:
> > I think I misspoke earlier.  The commit I mentioned above fixes a problem
> > introduced in an earlier patch.  (commit ID
> > d2394e6bb1aa636f3bd142cb6f7845a4332514b5, entitled
> > "tg3: Always turn on APE features in mac_mode reg")  So the fact that
> > 2.6.32-35 works and 2.6.32-36 doesn't means you applied the problematic
> > patch that had the bug, but you didn't apply the above fix to correct it.
> 
> I can try a fixed kernel, but I don't understand the way Debian builds
> its kernels. I can
> 
> (a) download a Debian kernel source package, apply
> d2394e6bb1aa636f3bd142cb6f7845a4332514b5 and go the make; make install
> way or
> (b) wait for a kernel deb from Ben.
> 
> If (a) is expected to give reasonable results, I can do that.

I'm not going to build a complete new package myself, as you can easily
do that with the debian/bin/test-patches script in the source package.
But I can provide you with a rebuilt tg3.ko so you can test just that
change in the installer like you did previously.

Ben.

-- 
Ben Hutchings
The world is coming to an end.  Please log off.


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

Processed: Re: needed for 686-pae kernels

[Debian Bug Tracking System]

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

> forcemerge 627019 649304
Bug#627019: linux-image-2.6.39-rc7-686-pae: several kernel hangs before geting 
to login
Bug#649304: linux-image-3.1.0-1-686-pae:  needed for 686-pae 
kernels
Forcibly Merged 627019 649304.

> quit
Stopping processing here.

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

Bug#649304: needed for 686-pae kernels

[Jonathan Nieder]

forcemerge 627019 649304
quit

Hi Will,

Will Set wrote:

> [Subject:  needed for 686-pae kernels]

You haven't described the actual symptoms here.  I assume that they
are segfaults and hangs, as before?

> I first noticed this issue using 2.6.38-rc5-686 and 2.6.38-rc6-686. 
> Although, 2.6.38-1-686 worked out of the box, the regession showed again 
> using 2.6.39-rcX kernels,
> and continues to show using all 686-pae kernels.
> Adding  to the kernel commandline works around the issue.
>
> Using 486 kernels is another workaround to this issue.

Please send full "dmesg" output from booting up and reproducing the
bug.  Attaching "acpidump" output would be useful, too.

> see: #627019  linux-image-2.6.39-rc7-686-pae: several kernel hangs ... 

Thanks for filing a separate bug so we can keep track of the
information about each machine separately.  I'm marking the two
reports as related for easy reference.

Thanks and hope that helps,
Jonathan



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/2019193213.gc31...@elie.hsd1.il.comcast.net

Bug#649304: linux-image-3.1.0-1-686-pae: needed for 686-pae kernels

[Will Set]

Package: linux-2.6

Version: 3.1.1-1
Severity: normal
Tags: d-i

I first noticed this issue using 2.6.38-rc5-686 and 2.6.38-rc6-686. 
Although, 2.6.38-1-686 worked out of the box, the regession showed again 
using 2.6.39-rcX kernels,
and continues to show using all 686-pae kernels.
Adding  to the kernel commandline works around the issue.

Using 486 kernels is another workaround to this issue.

see: #627019  linux-image-2.6.39-rc7-686-pae: several kernel hangs ... 


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

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.1.0-1-686-pae root=/dev/sdb8 ro processor.nocst=1

** Not tainted

** Kernel log:
[5.702701] [drm] nouveau :01:00.0: Detected an NV40 generation card 
(0x04a100a1)
[5.704709] IR RC5(x) protocol handler initialized
[5.706708] [drm] nouveau :01:00.0: Attempting to load BIOS image from 
PRAMIN
[5.798468] [drm] nouveau :01:00.0: ... appears to be valid
[5.798533] [drm] nouveau :01:00.0: BIT BIOS found
[5.798591] [drm] nouveau :01:00.0: Bios version 05.44.a2.07
[5.798650] [drm] nouveau :01:00.0: TMDS table version 1.1
[5.798707] [drm] nouveau :01:00.0: BIT table 'd' not found
[5.798765] [drm] nouveau :01:00.0: Found Display Configuration Block 
version 3.0
[5.798836] [drm] nouveau :01:00.0: Raw DCB entry 0: 01000300 0028
[5.798895] [drm] nouveau :01:00.0: Raw DCB entry 1: 02011310 0028
[5.798953] [drm] nouveau :01:00.0: Raw DCB entry 2: 01011312 
[5.799012] [drm] nouveau :01:00.0: Raw DCB entry 3: 020223f1 0084c030
[5.799071] [drm] nouveau :01:00.0: DCB connector table: VHER 0x30 5 7 2
[5.799131] [drm] nouveau :01:00.0:   0: 0x: type 0x00 idx 0 tag 
0xff
[5.799202] [drm] nouveau :01:00.0:   1: 0x2230: type 0x30 idx 1 tag 
0x08
[5.799272] [drm] nouveau :01:00.0:   2: 0x0110: type 0x10 idx 2 tag 
0xff
[5.799341] [drm] nouveau :01:00.0:   3: 0x0111: type 0x11 idx 3 tag 
0xff
[5.799410] [drm] nouveau :01:00.0:   4: 0x0113: type 0x13 idx 4 tag 
0xff
[5.799484] [drm] nouveau :01:00.0: Parsing VBIOS init table 0 at offset 
0xDD1E
[5.802028] [drm] nouveau :01:00.0: Parsing VBIOS init table 1 at offset 
0xE00C
[5.807894] IR RC6 protocol handler initialized
[5.815248] [drm] nouveau :01:00.0: Parsing VBIOS init table 2 at offset 
0xE546
[5.815342] [drm] nouveau :01:00.0: Parsing VBIOS init table 3 at offset 
0xE6A3
[5.816531] [drm] nouveau :01:00.0: Parsing VBIOS init table 4 at offset 
0xE82C
[5.816604] [drm] nouveau :01:00.0: mem timing table length unknown: 14
[5.816664] [drm] nouveau :01:00.0: timingset 255 does not exist
[5.833530] i2c-core: driver [msp3400] using legacy suspend method
[5.833597] i2c-core: driver [msp3400] using legacy resume method
[5.836820] [drm] nouveau :01:00.0: 1 available performance level(s)
[5.836885] [drm] nouveau :01:00.0: 0: memory 532MHz core 350MHz 
fanspeed 100%
[5.836963] [drm] nouveau :01:00.0: c: memory 401MHz core 200MHz
[5.837330] [TTM] Zone  kernel: Available graphics memory: 448398 kiB.
[5.837449] [TTM] Zone highmem: Available graphics memory: 516082 kiB.
[5.837514] [TTM] Initializing pool allocator.
[5.837601] [drm] nouveau :01:00.0: Detected 256MiB VRAM
[5.837895] agpgart-intel :00:00.0: AGP 3.0 bridge
[5.837974] agpgart: modprobe tried to set rate=x12. Setting to AGP3 x8 mode.
[5.838116] IR JVC protocol handler initialized
[5.838325] agpgart-intel :00:00.0: putting AGP V3 device into 8x mode
[5.838540] nouveau :01:00.0: putting AGP V3 device into 8x mode
[5.838634] [drm] nouveau :01:00.0: 256 MiB GART (aperture)
[5.838876] [drm] nouveau :01:00.0: Saving VGA fonts
[5.914955] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[5.915027] [drm] No driver support for vblank timestamp query.
[5.917941] [drm] nouveau :01:00.0: Setting dpms mode 3 on vga encoder 
(output 0)
[5.918021] [drm] nouveau :01:00.0: Setting dpms mode 3 on vga encoder 
(output 1)
[5.918097] [drm] nouveau :01:00.0: Setting dpms mode 3 on tmds encoder 
(output 2)
[5.918179] [drm] nouveau :01:00.0: Setting dpms mode 3 on TV encoder 
(output 3)
[5.948032] intel8x0_measure_ac97_clock: measured 55898 usecs (2693 samples)
[5.948101] intel8x0: clocking to 48000
[5.962545] IR Sony protocol handler initialized
[5.971068] IR MCE Keyboard/mouse protocol handler initialized
[5.979526] bttv0: audio absent, no audio device found!
[6.057390] i2c-core: driver [tuner] using legacy suspend method
[6.057461] i2c-core: driver [tuner] using legacy resume method
[6.058546] lirc_dev: IR Remote Control driver registered, major

Bug#645308: tg3 broken for NetXtreme 5714S in squeeze 6.0.3 installer

[Marc Haber]

On Fri, Nov 18, 2011 at 11:54:35AM -0800, Matt Carlson wrote:
> I think I misspoke earlier.  The commit I mentioned above fixes a problem
> introduced in an earlier patch.  (commit ID
> d2394e6bb1aa636f3bd142cb6f7845a4332514b5, entitled
> "tg3: Always turn on APE features in mac_mode reg")  So the fact that
> 2.6.32-35 works and 2.6.32-36 doesn't means you applied the problematic
> patch that had the bug, but you didn't apply the above fix to correct it.

I can try a fixed kernel, but I don't understand the way Debian builds
its kernels. I can

(a) download a Debian kernel source package, apply
d2394e6bb1aa636f3bd142cb6f7845a4332514b5 and go the make; make install
way or
(b) wait for a kernel deb from Ben.

If (a) is expected to give reasonable results, I can do that.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany  |  lose things."Winona Ryder | Fon: *49 621 31958061
Nordisch by Nature |  How to make an American Quilt | Fax: *49 621 31958062



-- 
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/2019184536.ge4...@torres.zugschlus.de

Bug#649198: linux-image-2.6.32-5-amd64: Kernel Oops on try to use an USB CD drive that was powered off

[Thomas Schmitt]

Hi,

> cat /proc/version

Says:
  Linux version 2.6.32-5-amd64 (Debian 2.6.32-38) (b...@decadent.org.uk) (gcc 
version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Mon Oct 3 03:59:20 UTC 2011

I was confused by the similarity of "2.6.32-5-amd64" and "2.6.32-38"
which made me think that "-38" should replace "-5".


> This shows a crash in close() not ioctl(). 

This is plausible, now that you stated it.

The xorriso command -toc causes ioctl(SG_IO) on the open filedescriptor.
If the ioctl() fails, then the file descriptor gets closed, indeed.

The original Oopses, which made me dig by xorriso, were with qemu which
uses SG_IO, and with blkid, which probably does not.
The Oops with qemu happened when i shut down client and qemu. At that
time qemu had reported I/O errors as reply to my attempts to talk to
the powerless drive. blkid was started by udevd.


> But anyway, definitely another bug to be fixed.

It was always a cool feature of Linux and USB drives that i could
revive a stuck drive without rebooting the system. Very helpful when
doing MMC experiments.
This still works with squeeze, but it is quite ugly when all terminals
scream "Kernel Oops" and a black window pops up urging me to report it.

The machine is dedicated to testing. Just give me instructions if you
want me to make experiments.


Have a nice day :)

Thomas




-- 
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/97955114524715@192.168.2.69

Bug#649294: linux-2.6: Duplicate battery after suspend/resume

[Bertrand Marc]

Package: linux-2.6
Severity: normal

Dear Maintainer,

After suspend/resume, the kernel seems to think I have 2 batteries, one empty 
and my real battery. Of course I have only one battery on this laptop (DELL 
Latitude E6400). It works fine after a reboot: acpi reports only one battery.

Here is the output of acpi -i -s before suspend:
Battery 0: Full, 100%
Battery 0: design capacity 5200 mAh, last full capacity 4464 mAh = 85%

Here is the output of acpi -i -s after suspend/resume:
Battery 0: slot empty
Battery 1: Full, 100%
Battery 1: design capacity 5200 mAh, last full capacity 4464 mAh = 85%

Do not hesitate to ask for more logs or output, I'll be happy to provide any 
information necessary.

Regards,
Bertrand


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

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



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/2019164930.9732.63154.reportbug@localhost.localdomain

Bug#649198: linux-image-2.6.32-5-amd64: Kernel Oops on try to use an USB CD drive that was powered off

[Ben Hutchings]

On Sat, 2011-11-19 at 12:40 +0100, Thomas Schmitt wrote:
> Hi,
> 
> Ben Hutchings wrote:
> > Please
> > update to the current stable point release (Debian 6.0.3) and let us
> > know whether the bug is fixed.
> 
> I am not a skilled Debian admin. So i need instructions for any Debian
> specific action you want me to perform.
> 
> Following the advise of the maintainer of my upstream packages in Debian
> i checked /etc/apt/sources.list and performed apt-get update,
> apt-get upgrade.

That's right.

> But after reboot uname -a still says 2.6.32-5.
> The date has changed, though:
>   Linux debian2 2.6.32-5-amd64 #1 SMP Mon Oct 3 03:59:20 UTC 2011 x86_64
> The previous one was
>   Linux debian2 2.6.32-5-amd64 #1 SMP Tue Jun 14 09:42:28 UTC 2011 x86_64

The version string that uname shows is kept unchanged as long as
possible, so that third-party kernel modules do not need to be rebuilt
after an upgrade.  You can use 'cat /proc/version' to get the package
version.

> Some messages from that upgrade attempt are listed below.
> 
> 
> I can still reproduce the kernel Oops by having a file descriptor open,
> switching off the USB drive, and then trying to use the file descriptor
> with ioctl(SG_IO).
> 
> Nov 19 11:32:21 debian2 kernel: [ 5287.380722] usb 1-3: USB disconnect, 
> address 3
> Nov 19 11:32:29 debian2 kernel: [ 5295.341307] PGD 77fb9067 PUD 0
> Nov 19 11:32:29 debian2 kernel: [ 5295.341328] CPU 3
> Nov 19 11:32:29 debian2 kernel: [ 5295.341332] Modules linked in: ppdev lp 
> sco bridge stp bnep rfcomm l2cap crc16 bluetooth rfkill powernow_k8 
> cpufreq_powersave cpufreq_stats cpufreq_conservative cpufreq_userspace 
> kvm_amd kvm binfmt_misc fuse loop snd_hda_codec_atihdmi snd_hda_codec_realtek 
> snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_seq snd_timer 
> snd_seq_device snd radeon ttm soundcore snd_page_alloc drm_kms_helper drm 
> i2c_algo_bit shpchp pci_hotplug i2c_piix4 i2c_core edac_core edac_mce_amd 
> k10temp pcspkr parport_pc parport button evdev processor ext3 jbd mbcache 
> usbhid hid sg sd_mod sr_mod crc_t10dif cdrom ata_generic usb_storage 
> pata_atiixp ahci libata ohci_hcd ehci_hcd thermal r8169 thermal_sys mii 
> scsi_mod usbcore nls_base [last unloaded: scsi_wait_scan]
> Nov 19 11:32:29 debian2 kernel: [ 5295.341436] Pid: 2636, comm: xorriso Not 
> tainted 2.6.32-5-amd64 #1 GA-MA74GM-S2H
> Nov 19 11:32:29 debian2 kernel: [ 5295.341442] RIP: 0010:[<00010153>] 
>  [<00010153>] 0x10153
> Nov 19 11:32:29 debian2 kernel: [ 5295.341453] RSP: 0018:880109643be0  
> EFLAGS: 00010206
> Nov 19 11:32:29 debian2 kernel: [ 5295.341458] RAX: 00010153 RBX: 
>  RCX: 880123e91198
> Nov 19 11:32:29 debian2 kernel: [ 5295.341463] RDX: 0010 RSI: 
> 880123e91110 RDI: 880124cf8000
> Nov 19 11:32:29 debian2 kernel: [ 5295.341442] RIP: 0010:[<00010153>] 
>  [<00010153>] 0x10153
> Nov 19 11:32:29 debian2 kernel: [ 5295.341453] RSP: 0018:880109643be0  
> EFLAGS: 00010206
> Nov 19 11:32:29 debian2 kernel: [ 5295.341458] RAX: 00010153 RBX: 
>  RCX: 880123e91198
> Nov 19 11:32:29 debian2 kernel: [ 5295.341463] RDX: 0010 RSI: 
> 880123e91110 RDI: 880124cf8000
> Nov 19 11:32:29 debian2 kernel: [ 5295.341469] RBP: 880124cf8000 R08: 
> 880124cf8000 R09: 880126aaae40
> Nov 19 11:32:29 debian2 kernel: [ 5295.341474] R10:  R11: 
> 00010153 R12: 880123e91110
> Nov 19 11:32:29 debian2 kernel: [ 5295.341479] R13: 0100 R14: 
> 0001 R15: 0001
> Nov 19 11:32:29 debian2 kernel: [ 5295.341486] FS:  7faa824d8700() 
> GS:88000538() knlGS:
> Nov 19 11:32:29 debian2 kernel: [ 5295.341492] CS:  0010 DS:  ES:  
> CR0: 80050033
> Nov 19 11:32:29 debian2 kernel: [ 5295.341497] CR2: 00010153 CR3: 
> 7b72e000 CR4: 06e0
> Nov 19 11:32:29 debian2 kernel: [ 5295.341503] DR0:  DR1: 
>  DR2: 
> Nov 19 11:32:29 debian2 kernel: [ 5295.341508] DR3:  DR6: 
> 0ff0 DR7: 0400
> Nov 19 11:32:29 debian2 kernel: [ 5295.341515] Process xorriso (pid: 2636, 
> threadinfo 880109642000, task 880124442a60)
> Nov 19 11:32:29 debian2 kernel: [ 5295.341522]  8117f52f 
> 0010810c78a0  0801
> Nov 19 11:32:29 debian2 kernel: [ 5295.341531] <0> 8800c680 
> 0041 880126aaae40 880124cf8000
> Nov 19 11:32:29 debian2 kernel: [ 5295.341540] <0>  
>   880126aaae40
> Nov 19 11:32:29 debian2 kernel: [ 5295.341562]  [] ? 
> get_request+0x1f0/0x2ba
> Nov 19 11:32:29 debian2 kernel: [ 5295.341572]  [] ? 
> get_request_wait+0x21/0x188
> Nov 19 11:32:29 debian2 kernel: [ 5295.341583]  [] ? 
> get_page_from_freelist+0x56b/0x760
> Nov 19 11:32:29 debian2 kernel: [ 5295.3416

Bug#649288: initramfs-tools: missing new ELF interpreter /lib/arm-linux-gnueabihf/ld-linux.so.3 in initramfs on armhf

[Dmitri Gribenko]

Package: initramfs-tools
Followup-For: Bug #649288

Version: 0.99

Dear Maintainer,

Here is a workaround:

# cat > /etc/initramfs-tools/hooks/elf_interp
#!/bin/sh

set -e

PREREQ=""

prereqs () {
echo "${PREREQ}"
}

case "${1}" in
prereqs)
prereqs
exit 0
;;
esac

.. /usr/share/initramfs-tools/hook-functions

copy_exec /lib/arm-linux-gnueabihf/ld-linux.so.3 /lib/arm-linux-gnueabihf

exit 0

^D
# dpkg-reconfigure initramfs-tools

Dmitri Gribenko

-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 1.7M Aug 13 05:02 /boot/initrd.img-2.6.38-ac1-ac100
-rw-r--r-- 1 root root 1.9M Nov 19 17:58 /boot/initrd.img-2.6.38-ac2-ac100
-- /proc/cmdline
root=/dev/mmcblk1p1 rootflags=noatime mem=448M@0M nvmem=64M@448M vmalloc=320M 
video=tegrafb console=tty0 usbcore.old_scheme_first=1 tegraboot=sdmmc 
tegrapart=recovery:700:a00:800,boot:1100:1000:800,mbr:2100:200:800,system:2300:25800:800,cache:27b00:32000:800,misc:59b00:400:800,userdata:5a000:9a600:800

-- /proc/filesystems
ext4
fuseblk

-- lsmod
Module  Size  Used by
aes_generic26768  2 
ipv6  275379  16 
cpufreq_conservative 5231  0 
cpufreq_userspace   1918  0 
cpufreq_ondemand6011  2 
cpufreq_powersave748  0 
fuse   60328  1 
arc41076  2 
rt2800usb  11495  0 
rt2800lib  39791  1 rt2800usb
crc_ccitt   1133  1 rt2800lib
rt2x00usb   8203  1 rt2800usb
rt2x00lib  30452  3 rt2800usb,rt2800lib,rt2x00usb
snd_soc_alc563218328  1 
snd_soc_tegra_i2s   3936  1 
snd_soc_tegra_das   2524  1 snd_soc_tegra_i2s
mac80211  195632  3 rt2800lib,rt2x00usb,rt2x00lib
snd_soc_tegra_paz00 3149  0 
snd_soc_tegra_pcm   3228  1 
snd_soc_core   75287  5 
snd_soc_tegra_i2s,snd_soc_alc5632,snd_soc_tegra_das,snd_soc_tegra_paz00,snd_soc_tegra_pcm
uvcvideo   54470  0 
cfg80211  145261  2 rt2x00lib,mac80211
psmouse46862  0 
snd_pcm59970  2 snd_soc_tegra_pcm,snd_soc_core
libps2  3665  1 psmouse
snd_soc_tegra_utils 1649  1 snd_soc_tegra_paz00
videodev   56188  1 uvcvideo
snd_timer  16667  1 snd_pcm
rfkill 15008  1 cfg80211
snd40444  3 snd_soc_core,snd_pcm,snd_timer
soundcore   5107  1 snd
snd_page_alloc  3528  1 snd_pcm
evdev   7237  0 
ext4  324828  1 
mbcache 5056  1 ext4
jbd2   77306  1 ext4
crc16   1121  1 ext4

-- /etc/initramfs-tools/modules

-- /etc/initramfs-tools/initramfs.conf
MODULES=dep
BUSYBOX=y
KEYMAP=n
COMPRESS=gzip
BOOT=local
DEVICE=
NFSROOT=auto

-- /etc/initramfs-tools/update-initramfs.conf
update_initramfs=yes
backup_initramfs=no

-- /sys/block
mmcblk0
mmcblk1

-- mkinitramfs hooks
/etc/initramfs-tools/hooks/:
elf_interp

/usr/share/initramfs-tools/hooks:
busybox
flash_kernel_set_root
fuse
keymap
klibc
ntfs_3g
thermal
udev


-- System Information:
Debian Release: wheezy/sid
Architecture: armhf (armv7l)

Kernel: Linux 2.6.38-ac2-ac100 (SMP w/2 CPU cores)
Locale: LANG=ru_UA.UTF-8, LC_CTYPE=ru_UA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages initramfs-tools depends on:
ii  cpio   2.11-7  
ii  findutils  4.4.2-1 
ii  klibc-utils1.5.25-1
ii  module-init-tools  3.16-1  
ii  udev   175-2   

Versions of packages initramfs-tools recommends:
ii  busybox  1:1.19.3-1

Versions of packages initramfs-tools suggests:
ii  bash-completion  1:1.3-3

-- Configuration Files:
/etc/initramfs-tools/initramfs.conf changed [not included]

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/2019160355.1205.83260.reportbug@delta

Bug#649288: initramfs-tools: missing new ELF interpreter /lib/arm-linux-gnueabihf/ld-linux.so.3 in initramfs on armhf

[Dmitri Gribenko]

Package: initramfs-tools

Version: 0.99
Severity: important

Dear Maintainer,

Seems like armhf ELF interpreter path was changed from
/lib/ld-linux.so.3 to /lib/arm-linux-gnueabihf/ld-linux.so.3

For example, coreutils was compiled a while ago and it uses old
interpreter path:

$ readelf -l /bin/ls | grep interpreter
  [Requesting program interpreter: /lib/ld-linux.so.3]

While udev was recently updated to 175-2 and it uses new interpreter
path:

$ readelf -l /sbin/udevadm | grep interpreter
  [Requesting program interpreter: /lib/arm-linux-gnueabihf/ld-linux.so.3]

See also:
http://www.mail-archive.com/cross-distro@lists.linaro.org/msg00103.html

The problem is that copy_exec() in
/usr/share/initramfs-tools/hook-functions copies the interpreter only to
the old path.  It basically does the following:

$ cat copy_exec_udevadm.sh
#!/bin/sh -e

src=/sbin/udevadm

for x in $(ldd ${src} 2>/dev/null | sed -e '
/\//!d;
/linux-gate/d;
/=>/ {s/.*=>[[:blank:]]*\([^[:blank:]]*\).*/\1/};
s/[[:blank:]]*\([^[:blank:]]*\) (.*)/\1/' 2>/dev/null); do

# copy ${x}
echo ${x}

done

$ ./copy_exec_udevadm.sh
/lib/arm-linux-gnueabihf/libselinux.so.1
/lib/arm-linux-gnueabihf/librt.so.1
/lib/arm-linux-gnueabihf/libgcc_s.so.1
/lib/arm-linux-gnueabihf/libc.so.6
/lib/ld-linux.so.3
/lib/arm-linux-gnueabihf/libdl.so.2
/lib/arm-linux-gnueabihf/libpthread.so.0

Here's some additional info:

$ ldd /bin/ls
libselinux.so.1 => /lib/arm-linux-gnueabihf/libselinux.so.1 (0x4009d000)
librt.so.1 => /lib/arm-linux-gnueabihf/librt.so.1 (0x400d)
libacl.so.1 => /lib/arm-linux-gnueabihf/libacl.so.1 (0x4005a000)
libgcc_s.so.1 => /lib/arm-linux-gnueabihf/libgcc_s.so.1 (0x400b9000)
libc.so.6 => /lib/arm-linux-gnueabihf/libc.so.6 (0x400de000)
libdl.so.2 => /lib/arm-linux-gnueabihf/libdl.so.2 (0x4008b000)
/lib/ld-linux.so.3 (0x4002e000)
libpthread.so.0 => /lib/arm-linux-gnueabihf/libpthread.so.0 (0x401bd000)
libattr.so.1 => /lib/arm-linux-gnueabihf/libattr.so.1 (0x4004d000)
$ ldd /sbin/udevadm
libselinux.so.1 => /lib/arm-linux-gnueabihf/libselinux.so.1 (0x401cd000)
librt.so.1 => /lib/arm-linux-gnueabihf/librt.so.1 (0x40075000)
libgcc_s.so.1 => /lib/arm-linux-gnueabihf/libgcc_s.so.1 (0x400e8000)
libc.so.6 => /lib/arm-linux-gnueabihf/libc.so.6 (0x401e9000)
/lib/arm-linux-gnueabihf/ld-linux.so.3 => /lib/ld-linux.so.3 
(0x40056000)
libdl.so.2 => /lib/arm-linux-gnueabihf/libdl.so.2 (0x400b3000)
libpthread.so.0 => /lib/arm-linux-gnueabihf/libpthread.so.0 (0x402c8000)

I don't know how to fix this properly (apart from treating ELF
interpreter as a special case).

Currently this bug breaks only udev inside initramfs, but in future will
break all newly compiled binaries that need to be in initramfs.

Tell me if you need any additional information.

Best regards,
Dmitri Gribenko

-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 1.7M Aug 13 05:02 /boot/initrd.img-2.6.38-ac1-ac100
-rw-r--r-- 1 root root 1.8M Nov 19 16:54 /boot/initrd.img-2.6.38-ac2-ac100
-- /proc/cmdline
root=/dev/mmcblk1p1 rootflags=noatime mem=448M@0M nvmem=64M@448M vmalloc=320M 
video=tegrafb console=tty0 usbcore.old_scheme_first=1 tegraboot=sdmmc 
tegrapart=recovery:700:a00:800,boot:1100:1000:800,mbr:2100:200:800,system:2300:25800:800,cache:27b00:32000:800,misc:59b00:400:800,userdata:5a000:9a600:800

-- /proc/filesystems
ext4
fuseblk

-- lsmod
Module  Size  Used by
aes_generic26768  3 
arc41076  2 
rt2800usb  11495  0 
rt2800lib  39791  1 rt2800usb
crc_ccitt   1133  1 rt2800lib
rt2x00usb   8203  1 rt2800usb
snd_soc_tegra_i2s   3936  1 
snd_soc_tegra_paz00 3149  0 
rt2x00lib  30452  3 rt2800usb,rt2800lib,rt2x00usb
snd_soc_alc563218328  1 
snd_soc_tegra_das   2524  1 snd_soc_tegra_i2s
snd_soc_tegra_pcm   3228  1 
mac80211  195632  3 rt2800lib,rt2x00usb,rt2x00lib
snd_soc_core   75287  5 
snd_soc_tegra_i2s,snd_soc_tegra_paz00,snd_soc_tegra_das,snd_soc_alc5632,snd_soc_tegra_pcm
psmouse46862  0 
snd_pcm59970  2 snd_soc_tegra_pcm,snd_soc_core
cfg80211  145261  2 rt2x00lib,mac80211
uvcvideo   54470  0 
libps2  3665  1 psmouse
snd_timer  16667  1 snd_pcm
snd_soc_tegra_utils 1649  1 snd_soc_tegra_paz00
videodev   56188  1 uvcvideo
rfkill 15008  1 cfg80211
snd40444  3 snd_soc_core,snd_pcm,snd_timer
soundcore   5107  1 snd
snd_page_alloc  3528  1 snd_pcm
evdev   7237  0 
ipv6  275379  18 
cpufreq_conservative 5231  0 
cpufreq_userspace   1918  0 
cpufreq_ondemand6011  2 
cpufreq_powersave748  0 
fuse   60328  1 
ext4  324828

Processed: Re: Kernel Oops on try to use an USB CD drive that was powered off

[Debian Bug Tracking System]

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

> found 649198 linux-2.6/2.6.32-38
Bug #649198 [linux-2.6] linux-image-2.6.32-5-amd64: Kernel Oops on try to use 
an USB CD drive that was powered off
The source linux-2.6 and version 2.6.32-38 do not appear to match any binary 
packages
Bug Marked as found in versions linux-2.6/2.6.32-38.
>
End of message, stopping processing here.

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

Bug#649198: linux-image-2.6.32-5-amd64: Kernel Oops on try to use an USB CD drive that was powered off

[Thomas Schmitt]

Hi,

Ben Hutchings wrote:
> Please
> update to the current stable point release (Debian 6.0.3) and let us
> know whether the bug is fixed.

I am not a skilled Debian admin. So i need instructions for any Debian
specific action you want me to perform.

Following the advise of the maintainer of my upstream packages in Debian
i checked /etc/apt/sources.list and performed apt-get update,
apt-get upgrade.

But after reboot uname -a still says 2.6.32-5.
The date has changed, though:
  Linux debian2 2.6.32-5-amd64 #1 SMP Mon Oct 3 03:59:20 UTC 2011 x86_64
The previous one was
  Linux debian2 2.6.32-5-amd64 #1 SMP Tue Jun 14 09:42:28 UTC 2011 x86_64

Some messages from that upgrade attempt are listed below.


I can still reproduce the kernel Oops by having a file descriptor open,
switching off the USB drive, and then trying to use the file descriptor
with ioctl(SG_IO).

Nov 19 11:32:21 debian2 kernel: [ 5287.380722] usb 1-3: USB disconnect, address 
3
Nov 19 11:32:29 debian2 kernel: [ 5295.341307] PGD 77fb9067 PUD 0
Nov 19 11:32:29 debian2 kernel: [ 5295.341328] CPU 3
Nov 19 11:32:29 debian2 kernel: [ 5295.341332] Modules linked in: ppdev lp sco 
bridge stp bnep rfcomm l2cap crc16 bluetooth rfkill powernow_k8 
cpufreq_powersave cpufreq_stats cpufreq_conservative cpufreq_userspace kvm_amd 
kvm binfmt_misc fuse loop snd_hda_codec_atihdmi snd_hda_codec_realtek 
snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_seq snd_timer snd_seq_device 
snd radeon ttm soundcore snd_page_alloc drm_kms_helper drm i2c_algo_bit shpchp 
pci_hotplug i2c_piix4 i2c_core edac_core edac_mce_amd k10temp pcspkr parport_pc 
parport button evdev processor ext3 jbd mbcache usbhid hid sg sd_mod sr_mod 
crc_t10dif cdrom ata_generic usb_storage pata_atiixp ahci libata ohci_hcd 
ehci_hcd thermal r8169 thermal_sys mii scsi_mod usbcore nls_base [last 
unloaded: scsi_wait_scan]
Nov 19 11:32:29 debian2 kernel: [ 5295.341436] Pid: 2636, comm: xorriso Not 
tainted 2.6.32-5-amd64 #1 GA-MA74GM-S2H
Nov 19 11:32:29 debian2 kernel: [ 5295.341442] RIP: 0010:[<00010153>]  
[<00010153>] 0x10153
Nov 19 11:32:29 debian2 kernel: [ 5295.341453] RSP: 0018:880109643be0  
EFLAGS: 00010206
Nov 19 11:32:29 debian2 kernel: [ 5295.341458] RAX: 00010153 RBX: 
 RCX: 880123e91198
Nov 19 11:32:29 debian2 kernel: [ 5295.341463] RDX: 0010 RSI: 
880123e91110 RDI: 880124cf8000
Nov 19 11:32:29 debian2 kernel: [ 5295.341442] RIP: 0010:[<00010153>]  
[<00010153>] 0x10153
Nov 19 11:32:29 debian2 kernel: [ 5295.341453] RSP: 0018:880109643be0  
EFLAGS: 00010206
Nov 19 11:32:29 debian2 kernel: [ 5295.341458] RAX: 00010153 RBX: 
 RCX: 880123e91198
Nov 19 11:32:29 debian2 kernel: [ 5295.341463] RDX: 0010 RSI: 
880123e91110 RDI: 880124cf8000
Nov 19 11:32:29 debian2 kernel: [ 5295.341469] RBP: 880124cf8000 R08: 
880124cf8000 R09: 880126aaae40
Nov 19 11:32:29 debian2 kernel: [ 5295.341474] R10:  R11: 
00010153 R12: 880123e91110
Nov 19 11:32:29 debian2 kernel: [ 5295.341479] R13: 0100 R14: 
0001 R15: 0001
Nov 19 11:32:29 debian2 kernel: [ 5295.341486] FS:  7faa824d8700() 
GS:88000538() knlGS:
Nov 19 11:32:29 debian2 kernel: [ 5295.341492] CS:  0010 DS:  ES:  CR0: 
80050033
Nov 19 11:32:29 debian2 kernel: [ 5295.341497] CR2: 00010153 CR3: 
7b72e000 CR4: 06e0
Nov 19 11:32:29 debian2 kernel: [ 5295.341503] DR0:  DR1: 
 DR2: 
Nov 19 11:32:29 debian2 kernel: [ 5295.341508] DR3:  DR6: 
0ff0 DR7: 0400
Nov 19 11:32:29 debian2 kernel: [ 5295.341515] Process xorriso (pid: 2636, 
threadinfo 880109642000, task 880124442a60)
Nov 19 11:32:29 debian2 kernel: [ 5295.341522]  8117f52f 
0010810c78a0  0801
Nov 19 11:32:29 debian2 kernel: [ 5295.341531] <0> 8800c680 
0041 880126aaae40 880124cf8000
Nov 19 11:32:29 debian2 kernel: [ 5295.341540] <0>  
  880126aaae40
Nov 19 11:32:29 debian2 kernel: [ 5295.341562]  [] ? 
get_request+0x1f0/0x2ba
Nov 19 11:32:29 debian2 kernel: [ 5295.341572]  [] ? 
get_request_wait+0x21/0x188
Nov 19 11:32:29 debian2 kernel: [ 5295.341583]  [] ? 
get_page_from_freelist+0x56b/0x760
Nov 19 11:32:29 debian2 kernel: [ 5295.341607]  [] ? 
scsi_execute+0x3b/0x12f [scsi_mod]
Nov 19 11:32:29 debian2 kernel: [ 5295.341626]  [] ? 
scsi_execute_req+0x40/0xb9 [scsi_mod]
Nov 19 11:32:29 debian2 kernel: [ 5295.341644]  [] ? 
scsi_execute_req+0x87/0xb9 [scsi_mod]
Nov 19 11:32:29 debian2 kernel: [ 5295.341662]  [] ? 
ioctl_internal_command+0x64/0x16a [scsi_mod]
Nov 19 11:32:29 debian2 kernel: [ 5295.341681]  [] ? 
scsi_set_medium_removal+0x5a/0x98 [scsi_mod]
Nov 19 11:32:29 debian2 kernel: [ 5295

Bug#649252: ([linux-2.6] linux-image-3.1.0-1-amd64 - blank screen during boot with i915)

[dpdt1]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256


if i boot with kernel option "nomodeset" as stated here :
http://wiki.debian.org/KernelModesetting#Disabling_KMS
bug doesnt appear and screen is back to normal.


dpdt1

- -- 
New gpg key :

pub   4096R/41778EBB 2010-10-06 [expires: 2013-10-05]
Key fingerprint = 6BF7 3AED 0FD9 518E 4C71  AAF7 42CB 4773 4177 8EBB
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCAAGBQJOx4jaAAoJEELLR3NBd467/7wQAJfZdv91/EpBEhh+JdsWlOjg
Qj/YkaYhGIpsTTljjGntuCEgpHxdWdFnb3ZsSXx00PdQeF08J7UjGX+vHzXxrsMT
KllMcttMMWJ65eBQ+jGynChfnYI0+532LuLBwNuiBkrLevWY2YwBT7K4xJj9IG8g
r8AwFYro8/kRFlYhxGbAhxjEzvTu2aD6FAyBN9n8UlCnlADLKKTFZuOKS0aABaju
vd2UtmCDMe00W/5Y5aD5DIQCE+yC70FR7mI275/oZW+/1kuA7QaPUqbdZQoYSsY1
7nPBQX3Rl943cUqGBi6rPMo3cyyisu8XSKJkuqOMzH927gUeTKmKT8TIkzPQgYNo
VoNH01k9Cn2rNfSDRWs8Sg3jPzttGVJn8Zk4iq5Mls/Mby19nZsq+2r6GGgbAF2k
mzgKPsEbwmqrJbvDOoUfYqPMD0xauN6SpNYGbExcirXaBVeQMu+lnE45dCB/Oio7
E8HmlcK9l2kfziidQNRwjwbkqrofhb6RbOlHazZNDQQMBOuhTfjrp9XgKNPGqeBX
jx/WXQyLsAaCdLpV23iBslpP/FxSbHBq6JNgpLmJ3IfPWBHddQN6nWATAygYkeY4
kbUXm9GScdMrr4o2EdAVsyA9OMgyISEoT/7nUaXxTXnCxxXXIeUHZB+I8qiuQYvA
j2sEFCWk5QwnHvVzqTEB
=c77E
-END PGP SIGNATURE-




-- 
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/4ec788df.40...@espiv.net

Bug#649252: [linux-2.6] linux-image-3.1.0-1-amd64 - blank screen during boot with i915

[dpdt1]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Package: linux-2.6
Version: linux-image-3.1.0-1-amd64
Severity: normal

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

Hi,

since latest kernel 3.1 i can't see any boot messages. screen is blank
after the first "waiting for dev" message.
i use cryptsetup so i just wait a minute, type the luks password in
the blind and wait till gdm3 is started and then i get the screen back
normally.

problem doesnt appear if booting with previous
linux-image-3.0.0-2-amd64 .

laptop is a dell inspiron 1525 (
http://wiki.debian.org/InstallingDebianOn/Dell/Inspiron1525 )

# lspci -v | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Mobile
GM965/GL960 Integrated Graphics Controller (primary) (rev 0c) (prog-if
00 [VGA controller])

# dmesg | grep Intel
[0.620445] agpgart-intel :00:00.0: Intel 965GM Chipset


/var/log/boot (during those messages screen is blank) :

Sat Nov 19 10:55:50 2011: Setting parameters of disc: (none).
Sat Nov 19 10:55:50 2011: Checking root file system...fsck from
util-linux 2.19.1
Sat Nov 19 10:55:50 2011: /dev/sda1: clean, 242206/1986768 files,
2142311/7936102 blocks
Sat Nov 19 10:55:50 2011: done.
Sat Nov 19 10:55:50 2011: Starting early crypto disks...swap (starting)...
Sat Nov 19 10:55:50 2011: modprobe: FATAL: Error inserting padlock_sha
(/lib/modules/3.1.0-1-amd64/kernel/drivers/crypto/padlock-sha.ko): No
such device
Sat Nov 19 10:55:50 2011:
Sat Nov 19 10:55:50 2011: crypt-home (starting)...
Sat Nov 19 10:55:50 2011: Unlocking the disk /dev/sda3 (crypt-home)
Sat Nov 19 10:55:50 2011: Enter passphrase:
Sat Nov 19 10:56:06 2011: done.
Sat Nov 19 10:56:07 2011: Loading kernel modules...done.
Sat Nov 19 10:56:07 2011: Setting up LVM Volume Groups  Reading all
physical volumes.  This may take a while...
+ some more startup messages.

let me know if you need any other info.

thanks,

dpdt1


- --- System information. ---
Architecture: amd64
Kernel: Linux 3.1.0-1-amd64

Debian Release: wheezy/sid
500 unstable ftp.de.debian.org
500 unstable debian.tu-bs.de
500 testing ftp.gr.debian.org
1 experimental ftp.de.debian.org

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

Package's Recommends field is empty.

Package's Suggests field is empty.




- -- 
New gpg key :

pub   4096R/41778EBB 2010-10-06 [expires: 2013-10-05]
Key fingerprint = 6BF7 3AED 0FD9 518E 4C71  AAF7 42CB 4773 4177 8EBB
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCAAGBQJOx4L2AAoJEELLR3NBd467XG8P/1JoByYI4GJRGePXBs6wyadd
J+RpRM+kpkoBenRQ98mJ+aZDVvavW3qcNkUwugHOc8XXgVfZxZGvMuGvQBwmfSpd
CT9oL4dQGcoHhZekHyAsBh/NV86KCViDpvZVGn9pFBhqSemFgzE9O9YZsKMa+ZTX
1AnImig2glzofD22ttB2PSnT+B1Qqa1V+4tiBNcTgBZkxFRZVWHGdcCXbl/iyHWq
vwEdBK+8+x3+Rnn6J4v/s9FUiX0aPmve7KM3mZeELcKEqN830OxkmxawPDUyXZD3
sV6xhG2vti1Hmtw1sM5cihCRTQq/l9s6jCuQvJn4jhitiYWErlkoijyJTYUDi3Rv
4lBhOljlRAaIa8qCjjZdZOVXtIsPDyqGteTllbfrO35PAj9ycsVifJoSLoV9xlNy
c/mccGhW3TuxNqfPcl6t9jxGMogf9OYcB2zMoNm750qkXV+xANEKkSGJoenOiVBk
cwL1QRr0PVzZsEwk/UXoswkYknp5JgMAaBQkSxzobTsLbIHgeUJzwY2+izVoVK9n
b24+bHZEC8KNohjrqb/d3UkwvKWTtpIvohQ5vwTaMItmcnywcd32CglviciX6Him
cPYrUCZo0LePzZy/EPljWij2DdRF42sDvf6N/IroXr0Np1SCxwvQrBTOn+BHWsHz
lb5JQZW0wZiurC5Q5CCe
=8UEk
-END PGP SIGNATURE-




-- 
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/4ec782f9.5000...@espiv.net