date:20120404

Bug#667446: linux-image-3.2.0-2-orion5x: leds-gpio fails on MV2120

2012-04-04 Thread Henry von Tresckow

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

During Bootup, the leds-gpio initalization fails with the following error 
message:

leds-gpio: probe of leds-gpio failed with error -22

Only the power led stays lit. The /sys/class/leds directory is also empty.






-- Package-specific info:
** Version:
Linux version 3.2.0-2-orion5x (Debian 3.2.12-1) 
(debian-kernel@lists.debian.org) (gcc version 4.6.2 (Debian 4.6.2-12) ) #1 Thu 
Mar 22 03:54:01 UTC 2012

** Command line:
console=ttyS0,115200 root=/dev/md0 ro BOOT_MODE=normal runintime=13000 
serialNo=CN68110K3H

** Not tainted

** Kernel log:
[   12.680997] rtc-pcf8563 0-0051: chip found, driver version 0.4.3
[   12.688480] rtc-pcf8563 0-0051: low voltage detected, date/time is not 
reliable.
[   12.695918] rtc-pcf8563 0-0051: retrieved date/time is not valid.
[   12.702508] rtc-pcf8563 0-0051: rtc core: registered rtc-pcf8563 as rtc0
[   12.709626] Registered led device: mv2120:blue:health
[   12.709882] Registered led device: mv2120:red:health
[   12.710120] Registered led device: mv2120:led:bright
[   12.710357] Registered led device: mv2120:led:dimmed
[   12.710627] Registered led device: mv2120:red:sata0
[   12.711476] leds-gpio: probe of leds-gpio failed with error -22
[   12.719263] TCP cubic registered
[   12.722558] NET: Registered protocol family 17
[   12.727025] Registering the dns_resolver key type
[   12.731875] VFP support v0.3: not present
[   12.736937] registered taskstats version 1
[   12.742752] rtc-pcf8563 0-0051: low voltage detected, date/time is not 
reliable.
[   12.750141] rtc-pcf8563 0-0051: retrieved date/time is not valid.
[   12.756267] rtc-pcf8563 0-0051: hctosys: invalid date/time
[   12.761913] Initializing network drop monitor service
[   12.768620] Freeing init memory: 140K
[   12.985733] udevd[48]: starting version 175
[   13.539871] SCSI subsystem initialized
[   13.721327] libata version 3.00 loaded.
[   13.726336] sata_mv sata_mv.0: version 1.28
[   13.727399] sata_mv sata_mv.0: slots 32 ports 2
[   13.789925] scsi0 : sata_mv
[   13.799135] scsi1 : sata_mv
[   13.806608] ata1: SATA max UDMA/133 irq 29
[   13.810714] ata2: SATA max UDMA/133 irq 29
[   14.321015] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   14.361032] ata1.00: ATA-8: ST3500418AS, CC38, max UDMA/133
[   14.366604] ata1.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[   14.431043] ata1.00: configured for UDMA/133
[   14.436116] scsi 0:0:0:0: Direct-Access ATA  ST3500418AS  CC38 
PQ: 0 ANSI: 5
[   14.790967] ata2: SATA link down (SStatus 0 SControl 300)
[   14.856637] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 
GiB)
[   14.867542] sd 0:0:0:0: [sda] Write Protect is off
[   14.872401] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[   14.872733] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[   14.919769]  sda: sda1 sda2  sda5 
[   14.928971] sd 0:0:0:0: [sda] Attached SCSI disk
[   15.475178] device-mapper: uevent: version 1.0.3
[   15.484779] device-mapper: ioctl: 4.22.0-ioctl (2011-10-19) initialised: 
dm-de...@redhat.com
[   16.608932] kjournald starting.  Commit interval 5 seconds
[   16.614579] EXT3-fs (dm-0): mounted filesystem with ordered data mode
[   18.521715] udevd[194]: starting version 175
[   19.241204] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[   19.342251] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[   19.349269] mv643xx_eth smi: probed
[   19.514333] mv643xx_eth_port mv643xx_eth_port.0: eth0: port 0 with MAC 
address 00:0a:e4:87:6e:27
[   19.614814] usbcore: registered new interface driver usbfs
[   19.620510] usbcore: registered new interface driver hub
[   19.729908] usbcore: registered new device driver usb
[   19.737956] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[   19.990610] alg: hash: Test 6 failed for mv-hmac-sha1
[   19.995751] : 9a 5e 0d 81 ff f1 0b 69 3b 73 88 c8 d6 c9 13 d9
[   20.002231] 0010: 06 e3 53 3e
[   20.054468] orion-ehci orion-ehci.0: Marvell Orion EHCI
[   20.059848] orion-ehci orion-ehci.0: new USB bus registered, assigned bus 
number 1
[   20.141104] orion-ehci orion-ehci.0: irq 17, io mem 0xf105
[   20.165456] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
[   20.189432] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[   20.196295] usb usb1: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
[   20.203549] usb usb1: Product: Marvell Orion EHCI
[   20.208251] usb usb1: Manufacturer: Linux 3.2.0-2-orion5x ehci_hcd
[   20.214460] usb usb1: SerialNumber: orion-ehci.0
[   20.371115] hub 1-0:1.0: USB hub found
[   20.406404] hub 1-0:1.0: 1 port detected
[   20.421073] orion-ehci orion-ehci.1: Marvell Orion EHCI
[   20.426391] orion-ehci orion-ehci.1: new USB bus registered, assigned bus 
number 2
[   20.521091] orion-ehci orion-ehci.1: irq 12, io mem 0xf10a
[   20.571057] orion-ehci orion-ehci.1: USB 2.0 started,

Bug#666386: igb + bnx2 + ifenslave + brctl + vconfig = largely broken

2012-04-04 Thread Josip Rodin

On Mon, Apr 02, 2012 at 05:22:37AM +0100, Ben Hutchings wrote:
 On Sun, 2012-04-01 at 12:40 +0200, Josip Rodin wrote:
  On Sun, Apr 01, 2012 at 03:09:56AM +0100, Ben Hutchings wrote:
   I bet this is due to the combination of LRO plus bridging.  We try to
   turn off LRO in devices under a bridge, but that won't work if there's
   an intermediate bonding device.
   
   If you run:
   
   # ethtool -K eth0 lro off
   # ethtool -K eth2 lro off
   
   does the bridge start working?
  
  Err...
  
  % sudo ethtool -K eth0 lro off
  Cannot set large receive offload settings: Operation not supported
  % sudo ethtool -K eth2 lro off
  Cannot set large receive offload settings: Operation not supported
 
 Hmm.  Well it shouldn't be a problem but you could try also turning off
 GRO (similar commands).

Ah, there we go. Once I ran sudo ethtool -K eth0 gro off,
sudo ifenslave bond54 eth0 produced a still-working bond54.

  That's with eth0 removed from bonding, and eth2 inside.
 
 So the bonding device has only one slave now?

Yes, it was like that.

 What if you take the bonding device out completely and add eth2 directly
 to the bridge?

I think I had already tested that and everything was fine, too.
Do you want me to test that or is the GRO removal conclusive?

-- 
 2. That which causes joy or happiness.



-- 
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/20120404075557.ga3...@entuzijast.net

Bug#654799: Cranking sound coming out of speakers with the new 3.1 kernel

2012-04-04 Thread Jan Prunk

Hello !

I can confirm that I have NO further sound errors in the following kernels:
ii linux-image-3.2.0-2-686-pae 3.2.9-1
ii linux-image-3.2.0-1-686-pae 3.2.6-1

The rest is still to be tested.

Kind regards,
Jan

On Thu, Mar 1, 2012 at 8:56 AM, Takashi Iwai ti...@suse.de wrote:
At Thu, 1 Mar 2012 08:44:33 +0100,
Jan Prunk wrote:

Hello !

The sound has been stable for the last days without noises,
after applying % amixer -c0 set Auto-Mute Mode Disabled

OK, another question is whether the auto-mute feature works in hardware,
i.e. even when this mixer is set off, the hardware switches the
speaker upon plugging the headphone? If yes, we can simply remove
this switch and software feature from the driver.

thanks,

Takashi

It seems this has solved it, until further notice.
You might want to keep the bug open for a while,
so I can check with all the kernels (it works with latest).

Kind regards,
Jan

On Tue, Feb 28, 2012 at 4:38 PM, Takashi Iwai ti...@suse.de wrote:
At Tue, 28 Feb 2012 16:16:48 +0100,
Jan Prunk wrote:

Hello !

On Sat, Jan 14, 2012 at 12:04 AM, Jonathan Nieder jrnie...@gmail.com
wrote:
Hi again,

Jan Prunk wrote:

I tried booting into 3.2.0-rc7-686-pae, but the crunching sound
is still present, I am able to play music file properly, and
crunching is in the background, and also while not processing
any sounds, the crunching appears out of the speakers.

Ok, thanks for testing. Please send a summary of this regression to
alsa-de...@alsa-project.org, cc-ing Takashi Iwai ti...@suse.de and
either me or this bug log so we can track it.

Be sure to mention:

- steps to reproduce, what you expect versus what actually happens,
and how that indicates a bug

The sound is ok in kernel version 3.0.0-1-686-pae but on all newer
versions there are sparkling/farting noises coming out of the speaker.
The noise is not very loud, its barely noticeable, but its repetative
and doesn't go away. And I think it happens while typing on the
keyboard and a bit later, then it dissapears for a few seconds,
or by the time that I type again.

- which kernel versions you tried, and what happens with each
I tried running alsa-info.sh as a user.

I tried 3.0.0-1-686-pae here is the debug:
http://www.alsa-project.org/db/?f=c1149b6466b2068d79c7517a8b0808d8b5c26e6b
---
Linux vaio 3.2.0-1-686-pae #1 SMP Fri Feb 17 06:27:21 UTC 2012 i686
GNU/Linux
ii linux-image-3.2.0-1-686-pae 3.2.6-1
http://www.alsa-project.org/db/?f=fddbfbdc4fc44555a6dc851ecdc70760da6dd840
---
Linux vaio 3.2.0-rc7-686-pae #1 SMP Wed Dec 28 21:26:25 UTC 2011 i686
GNU/Linux
ii linux-image-3.2.0-rc7-686-pae 3.2~rc7-1~experimental.1
http://www.alsa-project.org/db/?f=78c8919e87dd03294484f83b5f7ae44331b5edfe
Being booted into this version for 15 minutes, it seems to not make any
noises,
but I will resubmit the info later if the noises will start to appear.

3.2.0-rc7 alsa-info shows that the headphone jack is plugged, thus the
speaker is muted. It's natural that the noise goes away in this
state.

Apart from that, I see no obvious problem in 3.2.0 output.

Does the problem still happen when you disable Auto-Mute Mode mixer
enum?
% amixer -c0 set Auto-Mute Mode Disabled

Also, try to pass algin_buffer_size=0 option to snd-hda-intel.
I don't expect much that this will influence, but at least, it's a
difference between 3.0 and 3.2.

Takashi

- alsa-info.sh output, as an attachment

- if you can make a recording of the strange sound available
somewhere online, that would be ideal

Because the noise is barely heard, I would need to find a good mic.
to be able to record it, but I could do that in the next bug submission.

- whether you are able to bisect or test patches if needed

I might try that, if there are any manuals around how to do it,
but my response might take some time.

[1] may have more hints.

Thanks and good luck,
Jonathan

[1] http://alsa-project.org/main/index.php/Help_To_Debug_Intel_HDA

Kind regards,
Jan Prunk
--
Jan Prunk http://www.prunk.si
0x00E80E86 http://pgp.prunk.si
http://AS50763.peeringdb.com

--
Jan Prunk http://www.prunk.si
0x00E80E86 http://pgp.prunk.si
http://AS50763.peeringdb.com

--
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/calnopx7hdaedx+wnuzrz0njst1jun1rl21hw5s+wzexvrs5...@mail.gmail.com

Bug#667434: lvcreate / lvremove snapshot under Xen causes Kernel OOPs

2012-04-04 Thread Ian Campbell

Hi Quintin,

Thanks for your report.

On Wed, 2012-04-04 at 13:54 +1200, Quintin Russ wrote:
 Package: linux-image-2.6.32-5-xen-amd64
 Version: 2.6.32-39
 Severity: important
 
 We have observed an issue when a Xen dom0 is removing a snapshot for a
 logical volume and another process comes along to create a snapshot
 for that same device (different names) causing the server to Kernel
 Ooops. According to my logs sometimes removing of the snapshot can
 pause or take a while contributing to the issue. Attempts to add
 locking code (using dotlockfile) have not so far been successful in
 mitigating this bug, but we are still exploring this option.
 
 The nodes that are affected intermittently  we have been unable to
 reproduce this issue in the lab (on either the same model of hardware
 or hardware that has crashed in production). From our logs we can see
 that every time this issue occurs one process has been removing the
 snapshot while another has been creating a snapshot shortly after
 (seconds normally). We are currently seeing about a 5% chance of a
 crash per month (assuming our nodes are equal).
 
 This bug looks similar to a number of bugs that have already been
 filed related to this
 issue:http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614400  A quick
 Google search shows many more (which have mostly been merged):
 https://www.google.co.nz/webhp?q=site%3Abugs.debian.org%20xen%
 20snapshot%20kernel%20oops%20squeeze

Those issues were believed to be fixed in 2.6.32-34 and you are running
2.6.32-39 so either this is a different issue (perhaps with similar
symptoms) or the issue isn't really fixed. Either way I think we need to
see your kernel logs containing the actual oops in order to make any
progress.

Thanks,
Ian.

-- 
Ian Campbell
Current Noise: Cathedral - Carnival Bizarre

HOORAY, Ronald!!  Now YOU can marry LINDA RONSTADT too!!




-- 
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/133354.20582.13.ca...@zakaz.uk.xensource.com

Bug#667501: linux-image-3.2.0-0.bpo.2-686-pae: crash when trying to read a floppy disk with Nautilus

2012-04-04 Thread rpnpif

Package: linux-2.6
Version: 3.2.12-1~bpo60+1
Severity: normal

In Nautilus when I click on floppy disk icon, an error is emitted.
Floppy drive is unusable under Debian.

-- Package-specific info:
** Version:
Linux version 3.2.0-0.bpo.2-686-pae (Debian 3.2.12-1~bpo60+1) 
(debian-kernel@lists.debian.org) (gcc version 4.4.5 (Debian 4.4.5-8) ) #1 SMP 
Sun Mar 25 11:12:58 UTC 2012

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.2.0-0.bpo.2-686-pae 
root=UUID=c9ea41b4-f399-48c8-87a5-b254689124b1 ro quiet

** Tainted: WO (4608)
 * Taint on warning.
 * Out-of-tree module has been loaded.

** Kernel log:
[17563.596056] [ cut here ]
[17563.596129] WARNING: at 
/build/buildd-linux-2.6_3.2.12-1~bpo60+1-i386-EZ37JT/linux-2.6-3.2.12/debian/build/source_i386_none/drivers/block/floppy.c:1041
 setup_rw_floppy+0x1e8/0x2a1 [floppy]()
[17563.596137] Hardware name: MS-6380 
[17563.596140] floppy_disable_hlt() scheduled for removal in 2012
[17563.596144] Modules linked in: vboxnetadp(O) vboxnetflt(O) vboxdrv(O) mperf 
cpufreq_stats cpufreq_powersave cpufreq_conservative cpufreq_userspace ppdev lp 
snd_hrtimer binfmt_misc fuse ipt_REJECT xt_comment ipt_LOG xt_limit xt_tcpudp 
xt_addrtype xt_state ip6table_filter ip6_tables nf_nat_irc nf_conntrack_irc 
nf_nat_ftp nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack_ftp 
nf_conntrack iptable_filter ip_tables x_tables nls_utf8 nls_cp437 vfat fat ext4 
jbd2 crc16 hwmon_vid sg loop firewire_sbp2 saa7134_alsa mt20xx tea5767 
ir_lirc_codec tda9887 lirc_dev tda8290 ir_mce_kbd_decoder ir_sony_decoder 
snd_via82xx snd_ac97_codec ac97_bus ir_jvc_decoder tuner ir_rc6_decoder 
ir_rc5_decoder snd_pcm_oss snd_mixer_oss ir_nec_decoder snd_pcm saa7134 rc_core 
videobuf_dma_sg snd_page_alloc videobuf_core snd_mpu401_uart v4l2_common usbhid 
snd_seq_midi videodev snd_rawmidi hid snd_seq_midi_event snd_seq media ohci_hcd 
tveeprom radeon i2c_viapro ttm via_ircc drm_kms_helper drm irda uhci_hcd
  ehci_hcd usbcore sr_mod via_rhine crc_ccitt snd_timer snd_seq_device snd 
soundcore usb_common cdrom evdev i2c_algo_bit i2c_core firewire_ohci 
power_supply pcspkr 8139too firewire_core 8139cp crc_itu_t mii shpchp floppy 
ns558 gameport parport_pc parport processor thermal_sys button ext3 jbd mbcache 
sd_mod crc_t10dif ata_generic pata_via libata scsi_mod
[17563.596288] Pid: 0, comm: swapper/0 Tainted: G   O 
3.2.0-0.bpo.2-686-pae #1
[17563.596292] Call Trace:
[17563.596312]  [c103b945] ? warn_slowpath_common+0x6a/0x7b
[17563.596327]  [f84583ae] ? setup_rw_floppy+0x1e8/0x2a1 [floppy]
[17563.596333]  [c103b9bc] ? warn_slowpath_fmt+0x28/0x2c
[17563.596350]  [f84583ae] ? setup_rw_floppy+0x1e8/0x2a1 [floppy]
[17563.596369]  [c104080d] ? irq_enter+0x49/0x49
[17563.596378]  [c10465d5] ? run_timer_softirq+0x167/0x20b
[17563.596391]  [f84581c6] ? fd_watchdog+0x84/0x84 [floppy]
[17563.596397]  [c104080d] ? irq_enter+0x49/0x49
[17563.596403]  [c10408a8] ? __do_softirq+0x9b/0x14e
[17563.596409]  [c104080d] ? irq_enter+0x49/0x49
[17563.596412]  IRQ  [c10406f0] ? irq_exit+0x2f/0x91
[17563.596425]  [c10203eb] ? smp_apic_timer_interrupt+0x69/0x73
[17563.596434]  [c12d62e9] ? apic_timer_interrupt+0x31/0x38
[17563.596443]  [c1026554] ? native_safe_halt+0x2/0x3
[17563.596452]  [c1011ee2] ? default_idle+0x50/0x87
[17563.596463]  [c100bf09] ? cpu_idle+0xa3/0xbe
[17563.596474]  [c142c7d5] ? start_kernel+0x33d/0x342
[17563.596479] ---[ end trace 3810d95a8a9539d4 ]---

** Model information
not available

** Loaded modules:
vboxnetadp(O)
vboxnetflt(O)
vboxdrv(O)
mperf
cpufreq_stats
cpufreq_powersave
cpufreq_conservative
cpufreq_userspace
ppdev
lp
snd_hrtimer
binfmt_misc
fuse
ipt_REJECT
xt_comment
ipt_LOG
xt_limit
xt_tcpudp
xt_addrtype
xt_state
ip6table_filter
ip6_tables
nf_nat_irc
nf_conntrack_irc
nf_nat_ftp
nf_nat
nf_conntrack_ipv4
nf_defrag_ipv4
nf_conntrack_ftp
nf_conntrack
iptable_filter
ip_tables
x_tables
nls_utf8
nls_cp437
vfat
fat
ext4
jbd2
crc16
hwmon_vid
sg
loop
firewire_sbp2
saa7134_alsa
mt20xx
tea5767
ir_lirc_codec
tda9887
lirc_dev
tda8290
ir_mce_kbd_decoder
ir_sony_decoder
snd_via82xx
snd_ac97_codec
ac97_bus
ir_jvc_decoder
tuner
ir_rc6_decoder
ir_rc5_decoder
snd_pcm_oss
snd_mixer_oss
ir_nec_decoder
snd_pcm
saa7134
rc_core
videobuf_dma_sg
snd_page_alloc
videobuf_core
snd_mpu401_uart
v4l2_common
usbhid
snd_seq_midi
videodev
snd_rawmidi
hid
snd_seq_midi_event
snd_seq
media
ohci_hcd
tveeprom
radeon
i2c_viapro
ttm
via_ircc
drm_kms_helper
drm
irda
uhci_hcd
ehci_hcd
usbcore
sr_mod
via_rhine
crc_ccitt
snd_timer
snd_seq_device
snd
soundcore
usb_common
cdrom
evdev
i2c_algo_bit
i2c_core
firewire_ohci
power_supply
pcspkr
8139too
firewire_core
8139cp
crc_itu_t
mii
shpchp
floppy
ns558
gameport
parport_pc
parport
processor
thermal_sys
button
ext3
jbd
mbcache
sd_mod
crc_t10dif
ata_generic
pata_via
libata
scsi_mod

** PCI devices:
00:00.0 Host bridge [0600]: VIA Technologies, Inc. VT8366/A/7 [Apollo 
KT266/A/333] [1106:3099]
Subsystem: VIA Technologies, Inc. Device

40 matches

Mail list logo