Re: Bug#702245: Thinkpad T410s cannot detect link

[Douglas Gilbert]

Seeing the same on a Lenovo X201 with a 82577LM on lk 3.8.2.

It is really strange, some switches its likes (2 out of 5),
the rest are "no shows". When I revert to lk 3.5 they are
all there.

With the "no shows" the carrier light goes on X201 RJ45
receptacle but nothing happens on the traffic LED and there
is no event sent to the logs.

This is a quite frustrating bug. If this is a Intel software/
firmware change please revert until they sort it out.

Doug Gilbert



--
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/513ca29e.50...@interlog.com

Bug#702625: marked as done (linux-source-3.2: Custom kernel built from Debian source gives a package with huge size)

[Debian Bug Tracking System]

Your message dated Sun, 10 Mar 2013 23:38:00 +
with message-id <1362958680.5951.43.ca...@deadeye.wl.decadent.org.uk>
and subject line Re: Bug#702625: linux-source-3.2: Custom kernel built from 
Debian source gives a package with huge size
has caused the Debian Bug report #702625,
regarding linux-source-3.2: Custom kernel built from Debian source gives a 
package with huge size
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


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

Dear Maintainer,

  Upgrading from Squeeze to Wheezy and using TuxOnIce hibernation system,
I installed the Wheezy's linux-source-3.2 package, and build a cusom kernel
following recommendations as in :
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-building
(I used to do this also on my Squeeze system).

I applied the TuxOnIce and RT patches, copy the config of the Debian package 
linux-image-3.2.0-rt-amd64, done a 'make oldconfig' to answer new config about 
TOI,
and run the compilation with :

time ionice -c 3 nice env KBUILD_PKG_ROOTCMD="fakeroot -u" make -j 3 
KDEB_PKGVERSION=3.2-3.2.35-2 KERNELRELEASE=3.2-rt-toi deb-pkg

After a while, I get a debian package, but with a huge size, about 500 MB,
whereas official Debian is about 20 MB !
It seems the modules are built with symbols. Looking around on the web,
I saw people telling to look at CONFIG_DEBUG_INFO config parameter, and
it's actually set :

$ grep CONFIG_DEBUG_INFO .config
CONFIG_DEBUG_INFO=y
# CONFIG_DEBUG_INFO_REDUCED is not set

But it's also set in the official Debian configs :

$ grep CONFIG_DEBUG_INFO /boot/config-3.2.0-4-*
/boot/config-3.2.0-4-amd64:CONFIG_DEBUG_INFO=y
/boot/config-3.2.0-4-amd64:# CONFIG_DEBUG_INFO_REDUCED is not set
/boot/config-3.2.0-4-rt-amd64:CONFIG_DEBUG_INFO=y
/boot/config-3.2.0-4-rt-amd64:# CONFIG_DEBUG_INFO_REDUCED is not set

What should I do to get a 'standard size' Debian package ?
Disable this parameter in the kernel config ? Or doing an action / setup
I forgot ?

  Thanks for your support,
Fred.


-- System Information:
Debian Release: 7.0
  APT prefers testing
  APT policy: (990, 'testing'), (800, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-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

Versions of packages linux-source-3.2 depends on:
ii  binutils  2.22-8
ii  bzip2 1.0.6-4

Versions of packages linux-source-3.2 recommends:
ii  gcc   4:4.7.2-1
ii  libc6-dev [libc-dev]  2.13-38
ii  make  3.81-8.2

Versions of packages linux-source-3.2 suggests:
ii  libncurses5-dev [ncurses-dev]  5.9-10
pn  libqt4-dev 
ii  pkg-config 0.26-1

-- no debconf information
--- End Message ---
--- Begin Message ---
On Sat, 2013-03-09 at 10:31 +0100, Frédéric Boiteux wrote:
[...]
> After a while, I get a debian package, but with a huge size, about 500 MB,
> whereas official Debian is about 20 MB !
> It seems the modules are built with symbols. Looking around on the web,
> I saw people telling to look at CONFIG_DEBUG_INFO config parameter, and
> it's actually set :
> 
> $ grep CONFIG_DEBUG_INFO .config
> CONFIG_DEBUG_INFO=y
> # CONFIG_DEBUG_INFO_REDUCED is not set
> 
> But it's also set in the official Debian configs :
> 
> $ grep CONFIG_DEBUG_INFO /boot/config-3.2.0-4-*
> /boot/config-3.2.0-4-amd64:CONFIG_DEBUG_INFO=y
> /boot/config-3.2.0-4-amd64:# CONFIG_DEBUG_INFO_REDUCED is not set
> /boot/config-3.2.0-4-rt-amd64:CONFIG_DEBUG_INFO=y
> /boot/config-3.2.0-4-rt-amd64:# CONFIG_DEBUG_INFO_REDUCED is not set
> 
> What should I do to get a 'standard size' Debian package ?
> Disable this parameter in the kernel config ? Or doing an action / setup
> I forgot ?

You should disable this option if you don't need debug information.

The official binary packages are built with a post-processing step that
removes the debug information into separate packages e.g.
linux-image-3.2.0-amd64-dbg.

Ben.

-- 
Ben Hutchings
Every program is either trivial or else contains at least one bug


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

Bug#692607: linux-image-3.2.0-4-686-pae: Kernel crash when coming out of screen saver

[Ben Hutchings]

On Wed, 2013-03-06 at 23:30 +0100, Steinar Bang wrote:
> > Steinar Bang :
> 
> > I then installed Bjørn's kernel with
> >  dpkg --install linux-image-3.2.0-4-686-pae_3.2.39-2a~test_i386.deb
> 
> > At the time of writing I have been running this kernel for 10 hours and
> > 40 minutes.
> 
> I have now been running a kernel with Bjørn's fix for 4 days and 2:58h,
> 
> The fix looks good to me.

Thanks all; this is now pending for the next upload.

Ben.

-- 
Ben Hutchings
Every program is either trivial or else contains at least one bug


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

Processed: tagging 692607

[Debian Bug Tracking System]

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

> tags 692607 + pending
Bug #692607 [src:linux] linux-image-3.2.0-4-686-pae: Kernel crash when coming 
out of screen saver
Bug #693501 [src:linux] lightdm-gtk-greeter: Kernel panic with 
lightdm-gtk-greeter and Intel845g
Added tag(s) pending.
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#701525: linux-image-3.2.0-4-amd64: Lenovo B575 ports doesn't work correctly

[Ben Hutchings]

On Wed, 2013-03-06 at 21:21 +0100, Adam Chyła wrote:
> Log: http://pastebin.com/macnLs01

Attaching it here.

Ben.

-- 
Ben Hutchings
Every program is either trivial or else contains at least one bug
[113488.316180] usb 2-2: new high-speed USB device number 8 using ehci_hcd
[113488.452329] usb 2-2: New USB device found, idVendor=0951, idProduct=1607
[113488.452344] usb 2-2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[113488.452355] usb 2-2: Product: DataTraveler 2.0
[113488.452386] usb 2-2: Manufacturer: Kingston
[113488.452394] usb 2-2: SerialNumber: 0014780F9951F941B5820298
[113488.454514] scsi13 : usb-storage 2-2:1.0
[113489.455218] scsi 13:0:0:0: Direct-Access Kingston DataTraveler 2.0 1.00 
PQ: 0 ANSI: 2
[113489.457111] sd 13:0:0:0: Attached scsi generic sg3 type 0
[113489.461872] sd 13:0:0:0: [sdc] 15654848 512-byte logical blocks: (8.01 
GB/7.46 GiB)
[113489.462805] sd 13:0:0:0: [sdc] Write Protect is off
[113489.462817] sd 13:0:0:0: [sdc] Mode Sense: 16 07 09 51
[113489.464468] sd 13:0:0:0: [sdc] Incomplete mode parameter data
[113489.464481] sd 13:0:0:0: [sdc] Assuming drive cache: write through
[113489.470851] sd 13:0:0:0: [sdc] Incomplete mode parameter data
[113489.470865] sd 13:0:0:0: [sdc] Assuming drive cache: write through
[113489.471668]  sdc: sdc1
[113489.474710] sd 13:0:0:0: [sdc] Incomplete mode parameter data
[113489.474724] sd 13:0:0:0: [sdc] Assuming drive cache: write through
[113489.474734] sd 13:0:0:0: [sdc] Attached SCSI removable disk
[113494.643869] sd 9:0:0:0: [sdb] 15564800 512-byte logical blocks: (7.96 
GB/7.42 GiB)
[113494.643944] sd 9:0:0:0: [sdb] Cache data unavailable
[113494.643950] sd 9:0:0:0: [sdb] Assuming drive cache: write through
[113494.646260] sd 9:0:0:0: [sdb] Cache data unavailable
[113494.646269] sd 9:0:0:0: [sdb] Assuming drive cache: write through
[113494.648997]  sdb: sdb1
[113539.435048] ehci_hcd :00:13.2: force halt; handshake c9c78424 
4000  -> -110
[113539.435061] ehci_hcd :00:13.2: HC died; cleaning up
[113539.435171] usb 2-2: USB disconnect, device number 8
[113539.520279] sd 13:0:0:0: [sdc] Unhandled error code
[113539.520290] sd 13:0:0:0: [sdc]  Result: hostbyte=DID_NO_CONNECT 
driverbyte=DRIVER_OK
[113539.520299] sd 13:0:0:0: [sdc] CDB: Write(10): 2a 00 00 00 00 00 00 00 f0 00
[113539.520316] end_request: I/O error, dev sdc, sector 0
[113539.520327] quiet_error: 67879 callbacks suppressed
[113539.520333] Buffer I/O error on device sdc, logical block 0
[113539.520338] lost page write due to I/O error on sdc
[113539.520351] Buffer I/O error on device sdc, logical block 1
[113539.520356] lost page write due to I/O error on sdc
[113539.520362] Buffer I/O error on device sdc, logical block 2
[113539.520367] lost page write due to I/O error on sdc
[113539.520373] Buffer I/O error on device sdc, logical block 3
[113539.520377] lost page write due to I/O error on sdc
[113539.520384] Buffer I/O error on device sdc, logical block 4
[113539.520388] lost page write due to I/O error on sdc
[113539.520394] Buffer I/O error on device sdc, logical block 5
[113539.520399] lost page write due to I/O error on sdc
[113539.520405] Buffer I/O error on device sdc, logical block 6
[113539.520409] lost page write due to I/O error on sdc
[113539.520415] Buffer I/O error on device sdc, logical block 7
[113539.520420] lost page write due to I/O error on sdc
[113539.520426] Buffer I/O error on device sdc, logical block 8
[113539.520430] lost page write due to I/O error on sdc
[113539.520436] Buffer I/O error on device sdc, logical block 9
[113539.520440] lost page write due to I/O error on sdc
[113539.532000] sd 13:0:0:0: [sdc] Unhandled error code
[113539.532020] sd 13:0:0:0: [sdc]  Result: hostbyte=DID_NO_CONNECT 
driverbyte=DRIVER_OK
[113539.532029] sd 13:0:0:0: [sdc] CDB: Write(10): 2a 00 00 00 00 f0 00 00 f0 00
[113539.532046] end_request: I/O error, dev sdc, sector 240
[113539.797398] usb 2-3: USB disconnect, device number 2
[113539.830053] usb 2-5: USB disconnect, device number 3

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

Bug#701525: linux-image-3.2.0-4-amd64: Lenovo B575 ports doesn't work correctly

[Ben Hutchings]

On Wed, 2013-03-06 at 21:21 +0100, Adam Chyła wrote:
> Dnia 2013-02-24, o godz. 18:50:32
> Ben Hutchings  napisał(a):
> 
> > Control: tag -1 moreinfo
> > 
> > On Sun, 2013-02-24 at 08:28 +0100, Adam Chyła wrote:
> > > Package: src:linux
> > > Version: 3.2.35-2
> > > Severity: important
> > > Tags: upstream
> > > 
> > > There is a problem with card reader rts5139 module. When I insert
> > > pendrive to port on the right side it is not visible. To solve that
> > > problem I have to blacklist rts5139 module.
> > [...]
> > 
> > Does the kernel log any messages when you insert the pen drive while
> > rts5139 is loaded?
> > 
> > Does the built-in camera work while rts5139 is loaded?
> > 
> > Ben.
> > 
> 
> No camera doesn't work. Anything connected to that doesn't wokrs
> (mouse, pendrive). 
> 
> When bug occurs I was doing:
> 
> cat Image.iso > /dev/sdb
> 
> Log: http://pastebin.com/macnLs01

I'm a bit confused.  First you said that USB devices attached to the
same controller are not visible if rts5139 is loaded.  Now you are
talking about a failure while writing to a device.  (Which device is
/dev/sdb?)  Are these two separate problems?

Ben.

-- 
Ben Hutchings
The obvious mathematical breakthrough [to break modern encryption] would be
development of an easy way to factor large prime numbers. - Bill Gates



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

Processed: tagging 644174

[Debian Bug Tracking System]

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

> tags 644174 - moreinfo
Bug #644174 [linux-2.6] linux-image-2.6.32-5-amd64: ACPI I/O resource conflicts 
with ACPI region SMBI
Removed tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#701054: verbose kernel logs for thinkcentre m78: 3.2.0-4-686-pae, 3.7-trunk-686-pae, 3.8-trunk-686-pae

[Ben Hutchings]

On Wed, 2013-03-06 at 13:51 -0500, Daniel Kahn Gillmor wrote:
[...]
> Of particular interest between the three boots is:
> 
>  * all three boots: [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored

This means: the BIOS includes a quirk for Linux, but we ignored it
because there's no way to know which versions it was intended to apply
to.  (This was changed in Linux 2.6.23, so I have no idea why there are
new machines like this.)

You can try applying the quirk by adding 'acpi_osi=Linux' to the kernel
command line.

>  * just 3.2:
> [1.676960] [Firmware Bug]: cpu 0, try to use APIC500 (LVT offset 0)
> for vector 0x10400, but the register is already in use for vector 0xf9
> on another cpu
> [1.690776] [Firmware Bug]: cpu 0, IBS interrupt offset 0 not
> available (MSRC001103A=0x0100)
> [1.700255] Failed to setup IBS, -22
> 
>  * various hda-intel weirdnesses.

Does it still crash when starting PulseAudio?

I assume it still doesn't actually produce sound output.

> please let me know if there are other diagnostics we can run with any of
> these kernels, or if you'd like me to try anything different.
[...]

The standard diagnostic script for ALSA is:
http://www.alsa-project.org/alsa-info.sh

If sound is still broken on 3.8 then please run this script there.

Ben.

-- 
Ben Hutchings
The obvious mathematical breakthrough [to break modern encryption] would be
development of an easy way to factor large prime numbers. - Bill Gates


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

Processed: tagging 701054

[Debian Bug Tracking System]

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

> tags 701054 + moreinfo
Bug #701054 [src:linux] linux-image-3.2.0-4-686-pae: NULL pointer dereference 
in azx_pcm_open on ThinkCentre M78 hardware (ATI Technologies Inc Device 9902)
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#702750: Integrate alsa-info.sh into bug script

[Ben Hutchings]

Package: src:linux
Version: 3.2.39-2
Severity: wishlist

ALSA upstream provides a diagnostic script for sound problems,
alsa-info.sh.  We should perhaps include a copy of this in linux-image
packages and offer to run it in the package-specific information we
generate for bug reports.

Ben.

-- System Information:
Debian Release: 7.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (x86_64)
Foreign Architectures: amd64

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (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/20130311003615.6593.3844.report...@deadeye.wl.decadent.org.uk

Bug#700333: Stack trace

[Ben Hutchings]

On Wed, 2013-03-06 at 15:27 +0400, vita...@yourcmc.ru wrote:
[...]
> Stack trace picture is here: 
> http://vmx.yourcmc.ru/var/pics/IMG_20130306_141045.jpg

Vitaliy reported that his system crashes when suspending to disk.  This
was a regression from 3.2 to 3.7, and remains in 3.8.  Some details of
this system are in the bug log at .

The photo shows a BUG in hrtimer_interrupt() after making the
hibernation image and while resuming the non-boot CPUs.  The HPET
interrupt handler was called immediately after it was registered for CPU
2 (?), before the corresponding clock_event_device was registered.

Seems like an obvious race condition, but then shouldn't the HPET have
been stopped while the CPU was previously offlined?  And it's strange
that this system apparently hits the race quite reliably.

Ben.

-- 
Ben Hutchings
The obvious mathematical breakthrough [to break modern encryption] would be
development of an easy way to factor large prime numbers. - Bill Gates


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

Processed: bug 700333 is forwarded to linux-ker...@vger.kernel.org

[Debian Bug Tracking System]

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

> forwarded 700333 linux-ker...@vger.kernel.org
Bug #700333 [src:linux] linux-image-3.7-trunk-amd64: Suspend to disk broken
Set Bug forwarded-to-address to 'linux-ker...@vger.kernel.org'.
> thanks
Stopping processing here.

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

Bug#701054: verbose kernel logs for thinkcentre m78: 3.2.0-4-686-pae, 3.7-trunk-686-pae, 3.8-trunk-686-pae

[Daniel Kahn Gillmor]

On 03/10/2013 08:33 PM, Ben Hutchings wrote:
> This means: the BIOS includes a quirk for Linux, but we ignored it
> because there's no way to know which versions it was intended to apply
> to.  (This was changed in Linux 2.6.23, so I have no idea why there are
> new machines like this.)
> 
> You can try applying the quirk by adding 'acpi_osi=Linux' to the kernel
> command line.

thanks, i'll give that a try when i'm in front of the machine tomorrow.

>>  * just 3.2:
>> [1.676960] [Firmware Bug]: cpu 0, try to use APIC500 (LVT offset 0)
>> for vector 0x10400, but the register is already in use for vector 0xf9
>> on another cpu
>> [1.690776] [Firmware Bug]: cpu 0, IBS interrupt offset 0 not
>> available (MSRC001103A=0x0100)
>> [1.700255] Failed to setup IBS, -22
>>
>>  * various hda-intel weirdnesses.
> 
> Does it still crash when starting PulseAudio?

kernel 3.2 (which has the above output) does have a null dereference
within pulseaudio -- you can see it at 185.6 seconds into the first of
the three boots.  neither 3.7 and 3.8 have this null dereference.

using all three kernels, there is still a hang just before "setting
preliminary keymap", which is in /etc/rcS.d/S05keyboard-setup.  So it's
presumably hanging in one of:

S01mountkernfs.sh
S02udev
S03mountdevsubfs.sh
S04bootlogd

i'm not sure what userspace process is causing that hang (that is, which
one is being terminated when i send ctrl-c through the console), but i
can try to track it down.

> I assume it still doesn't actually produce sound output.

I haven't yet been able to coax any sound out of the system.

> The standard diagnostic script for ALSA is:
> http://www.alsa-project.org/alsa-info.sh
> 
> If sound is still broken on 3.8 then please run this script there.

Will do.

Regards,

--dkg



signature.asc
Description: OpenPGP digital signature