Re: Bug#992790: Severity: High / Bug on Debian 11 Bullseye - Boot problem - Failed to start Load/Save RF Kill Switch Status

[Andrei POPESCU]

Control: reassign -1 src:linux 5.10.46-4

On Lu, 23 aug 21, 15:38:42, pham...@bluewin.ch wrote:
> Package: Kernel
> Version: Linux station 5.10.0-8-amd64 #1 SMP Debian 5.10.46-4 (2021-08-03) 
> x86_64 GNU/Linux
> Bug Description:
> 
> After a new install I can't boot normally.
> I have to start in recovery mode to be able to get to the login window.
> Attachement :
> Config : inxi -Fxxxz
> - Two print screen of boot
> - Boot logs : dmesg, journalctl, journalctl -p err
> Best regards.
> 
> Philippe

Reassigning to correct package.

Kind regards,
Andrei
-- 
Looking after bugs assigned to unknown or inexistent packages


signature.asc
Description: PGP signature

Re: Bug#992131: R8169 CRASH! (rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100))

[Andrei POPESCU]

Control: reassign -1 src:linux 5.10.46+4

On Jo, 12 aug 21, 16:37:47, Vincenzo Gianfelice wrote:
> Package: r8169

There is no such package, you probably meant the kernel (guessing the 
version from your output below).

Full quote follows for convenience of kernel maintainers.

Kind regards,
Andrei

> Kernel: 5.10.0-8 (amd64)
> 
> System: Debian 11 (bullseye)
> 
> libc: 2.31
> 
> Hi. I state that this problem is present from kernel 5.4 and still has
> not been fixed ... suddenly, the ethernet stops working and this error
> appears (in dmesg):
> 
> 
> [   12.063469] NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
> [   12.063509] WARNING: CPU: 3 PID: 0 at net/sched/sch_generic.c:467
> dev_watchdog+0x24d/0x260
> [   12.063520] Modules linked in: joydev hid_logitech_hidpp uvcvideo
> videobuf2_vmalloc hid_gener
> ic videobuf2_memops videobuf2_v4l2 videobuf2_common snd_usb_audio
> videodev snd_usbmidi_lib snd_r
> awmidi usbhid snd_seq_device mc hid intel_rapl_msr intel_rapl_common
> rfkill snd_hda_codec_realte
> k snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel
> snd_intel_dspcfg x86_pkg_
> temp_thermal soundwire_intel intel_powerclamp
> soundwire_generic_allocation snd_soc_core coretemp
> snd_compress soundwire_cadence kvm_intel snd_hda_codec snd_hda_core
> nvidia_drm(POE) mei_hdcp kvm
> snd_hwdep soundwire_bus irqbypass drm_kms_helper snd_pcm rapl
> intel_cstate snd_timer iTCO_wdt m
> ei_me snd intel_pmc_bxt iTCO_vendor_support intel_uncore mei watchdog
> soundcore ee1004 sg intel_
> wmi_thunderbolt pcspkr cec nvidia_modeset(POE) evdev acpi_pad
> intel_pmc_core nvidia(POE) corefre
> qk(OE) parport_pc ppdev drm lp parport fuse configfs ip_tables
> x_tables autofs4 ext4 crc16 mbcac
> he jbd2 crc32c_generic uas usb_storage sd_mod
> [   12.063805]  t10_pi crc_t10dif crct10dif_generic crct10dif_pclmul
> crct10dif_common crc32_pclm
> ul crc32c_intel ahci libahci ghash_clmulni_intel libata xhci_pci
> scsi_mod xhci_hcd aesni_intel i
> 2c_i801 i2c_smbus usbcore r8169 libaes crypto_simd realtek mdio_devres
> cryptd libphy glue_helper
> usb_common wmi fan video button
> [   12.063917] CPU: 3 PID: 0 Comm: swapper/3 Tainted: P   OE
>   5.10.0-8-amd64 #1 Debia
> n 5.10.46-4
> [   12.063922] Hardware name: Gigabyte Technology Co., Ltd.
> H110M-S2H/H110M-S2H-CF, BIOS F24 12/
> 14/2017
> [   12.063933] RIP: 0010:dev_watchdog+0x24d/0x260
> [   12.063941] Code: 29 cb fd ff eb a9 4c 89 f7 c6 05 72 b7 10 01 01
> e8 b8 a0 fa ff 44 89 e9 4c
> 89 f6 48 c7 c7 40 8d d6 93 48 89 c2 e8 d6 24 14 00 <0f> 0b eb 8a 66 66
> 2e 0f 1f 84 00 00 00 00 0
> 0 0f 1f 40 00 0f 1f 44
> [   12.063947] RSP: 0018:a1590018ceb8 EFLAGS: 00010286
> [   12.063957] RAX:  RBX: 8eea4c5ba800 RCX: 
> 083f
> [   12.063963] RDX:  RSI: 00f6 RDI: 
> 083f
> [   12.063972] RBP: 8eea4b5043dc R08:  R09: 
> a1590018ccd8
> [   12.063978] R10: a1590018ccd0 R11: 942cb3e8 R12: 
> 8eea4b504480
> [   12.063983] R13:  R14: 8eea4b504000 R15: 
> 8eea4c5ba880
> [   12.063990] FS:  () GS:8eecaecc()
> knlGS:
> [   12.063995] CS:  0010 DS:  ES:  CR0: 80050033
> [   12.064001] CR2: 5624fe890068 CR3: 000103f06006 CR4: 
> 003706e0
> [   12.064006] DR0:  DR1:  DR2: 
> 
> [   12.064011] DR3:  DR6: fffe0ff0 DR7: 
> 0400
> [   12.064016] Call Trace:
> [   12.064024]  
> [   12.064038]  ? pfifo_fast_enqueue+0x150/0x150
> [   12.064056]  call_timer_fn+0x29/0xf0
> [   12.064063]  __run_timers.part.0+0x1d3/0x240
> [   12.064071]  ? ktime_get+0x38/0xa0
> [   12.064079]  ? lapic_next_deadline+0x28/0x30
> [   12.064087]  ? clockevents_program_event+0x8d/0xf0
> [   12.064094]  run_timer_softirq+0x26/0x50
> [   12.064103]  __do_softirq+0xc5/0x275
> [   12.064111]  asm_call_irq_on_stack+0xf/0x20
> [   12.064117]  
> [   12.064126]  do_softirq_own_stack+0x37/0x40
> [   12.064136]  irq_exit_rcu+0x8e/0xc0
> [   12.064146]  sysvec_apic_timer_interrupt+0x36/0x80
> [   12.064156]  asm_sysvec_apic_timer_interrupt+0x12/0x20
> [   12.064167] RIP: 0010:cpuidle_enter_state+0xc7/0x350
> [   12.064174] Code: 8b 3d 2d 34 d7 6c e8 a8 2a a2 ff 49 89 c5 0f 1f
> 44 00 00 31 ff e8 39 35 a2
> ff 45 84 ff 0f 85 fa 00 00 00 fb 66 0f 1f 44 00 00 <45> 85 f6 0f 88 06
> 01 00 00 49 63 c6 4c 2b 2
> c 24 48 8d 14 40 48 8d
> [   12.064180] RSP: 0018:a159000dfea8 EFLAGS: 0246
> [   12.064188] RAX: 8eecaecebc00 RBX: 0001 RCX: 
> 001f
> [   12.064193] RDX:  RSI: 1fefa71c RDI: 
> 
> [   12.064198] RBP: 8eecaecf5b00 R08: 0002cf095853 R09: 
> 0018
> [   12.064204] R10: 0001fc29 R11: 7786 R12: 
> 943ae6c0
> [   12.064208] R13: 0002cf095853 R14: 0001 R15: 
> 

Re: Bug#991342: general protection fault in linux kernel 4.9.0-16-amd64

[Andrei POPESCU]

Control: reassign -1 src:linux 4.9.272-2

On Mi, 21 iul 21, 11:00:18, Святослав wrote:
> 
> Package: linux-image-4.9.0-16-amd64
> Version: 4.9.272-2
>  
> I am using Debian GNU/Linux 9 (stretch) on ASUSTeK COMPUTER INC. ZenBook 13. 
> I’v upgraded kernel from 4.9.0.14 to 4.9.0-16. Just after booting and 
> enabling WiFi, I got kernel general protection fault warning (see log in 
> attachment). I tried to reboot, but my computer stuck with blinking cursor on 
> it’s terminal, so, the good old SysRq^R, SysRq^E, etc. only helped to reboot 
> it.
>  
> Best regards, S.

This package appears to be unknown to the BTS, possibly because stretch 
is already out of security support.

I'm reassigning your report to the source package, so the Kernel 
Maintainers will actually see it, but you should consider upgrading to 
Debian 10 (buster), or at the very least the kernel.

Kind regards,
Andrei
-- 
Looking after bugs assigned to unknown or inexistent packages


signature.asc
Description: PGP signature

Re: Bug#990868: lenovo T460 Shutdown Problem

[Andrei POPESCU]

Control: reassign -1 src:linux

On Sb, 10 iul 21, 00:56:28, Brian Falco wrote:
> Package: not sure, shutdown, poweroff, halt, kernel bug 
> Version: 0.0-0
> 
> When I shutdown my Lenovo Thinkpad T460 the laptop powers off
> but the screen stays on, I have to hold the power button for 5 seconds or so 
> till it turns off the screen.
> I can confirm this happens on all flavours, Gnome,Kde,Xfce and Mate. I have 
> installed
> and tested each version from the rc2 net installer. This problem also exists
> on the Debian Live Cd's all flavors mentioned. I cant run the report tool as
> I have removed all versions from my laptop. I can however run from the live 
> cd,
> the only problem is I have to use Ethernet as the firmware live non-free disk 
> does
> not see my wifi either.
> 
> I do not have any problems with Debian 10, Ubuntu 20.04.2 on the same laptop.
> They run as expected, no similar issues.
> 
> More info:
> 
> I will add a video and picture to display the issue.
> If there is something else I can do please let me know so
> I can help resolve this issue.
> 
> [T460.jpg]I am using Debian GNU/Linux 11, debian-live-blsy-DI-rc2-amd64/ all 
> variants.
> 
> Sent with [ProtonMail](https://protonmail.com/) Secure Email.

Reassigning to the kernel, especially since it worked correctly in 
previous Debian versions.

Kind regards,
Andrei
-- 
Looking after bugs assigned to unknown or inexistent packages


signature.asc
Description: PGP signature

Re: Bug#990732: iwlwifi fails to work after hibernation with linux-4.19.0-17-amd64

[Andrei POPESCU]

Control: reassign -1 src:linux 4.19.0-17

Reassigning to correct source package, full quote below for Maintainers' 
convenience.

Kind regards,
Andrei

On Lu, 05 iul 21, 20:44:58, Robert Scott wrote:
> Package: li1nux
> Version: 4.19.0-17
> 
> tl;dr: I have a feeling this is https://bugzilla.redhat.com/show_bug.cgi?
> id=1656233
> 
> After resuming a buster system with linux-4.19.0-17 on a thinkpad x220 the 
> intel 6205 wifi fails to work, with the below dmesg warnings.
> 
> Hopefully this _is_ just the same bug as linked, which would suggest the 
> solution is https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/
> linux.git/commit/drivers/pci/probe.c?
> id=10ecc818ea7319b5d0d2b4e1aa6a77323e776f76
> 
> [11218.145442] iwlwifi :03:00.0: Error, can not clear persistence bit
> [11218.145448] iwlwifi :03:00.0: Failed to start HW: -1
> [11218.145454] iwlwifi :03:00.0: Unable to initialize device.
> [11218.148066] iwlwifi :03:00.0: Error, can not clear persistence bit
> [11218.148072] iwlwifi :03:00.0: Failed to start HW: -1
> [11218.148079] iwlwifi :03:00.0: Unable to initialize device.
> [11315.009011] [ cut here ]
> [11315.009014] Timeout waiting for hardware access (CSR_GP_CNTRL 0x)
> [11315.009051] WARNING: CPU: 0 PID: 8807 at drivers/net/wireless/intel/
> iwlwifi/pcie/trans.c:2033 iwl_trans_pcie_grab_nic_access+0x1e8/0x220 [iwlwifi]
> [11315.009052] Modules linked in: rfcomm bnep btusb btrtl btbcm btintel 
> bluetooth drbg ansi_cprng ecdh_generic hid_generic usbhid hid nls_ascii 
> nls_cp437 vfat fat uas usb_storage ctr ccm tun intel_rapl arc4 
> x86_pkg_temp_thermal intel_powerclamp iwldvm(-) coretemp snd_hda_codec_hdmi 
> mei_wdt kvm_intel mac80211 uvcvideo snd_hda_codec_conexant videobuf2_vmalloc 
> videobuf2_memops snd_hda_codec_generic videobuf2_v4l2 joydev kvm 
> videobuf2_common irqbypass snd_hda_intel intel_cstate iwlwifi snd_hda_codec 
> sg 
> intel_uncore videodev wmi_bmof intel_rapl_perf serio_raw snd_hda_core media 
> pcspkr snd_hwdep cfg80211 snd_pcm thinkpad_acpi snd_timer mei_me nvram 
> iTCO_wdt iTCO_vendor_support mei snd soundcore pcc_cpufreq rfkill ac battery 
> evdev nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 xt_hl ip6_tables ip6t_rt 
> nf_log_ipv4
> [11315.009080]  nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG nft_limit 
> xt_limit xt_addrtype xt_tcpudp xt_conntrack nft_compat nft_counter 
> nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat 
> nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c 
> nf_tables nfnetlink parport_pc ppdev sunrpc lp parport ip_tables x_tables 
> autofs4 ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb twofish_generic 
> twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 twofish_common xts 
> algif_skcipher af_alg dm_crypt dm_mod sd_mod crct10dif_pclmul crc32_pclmul 
> crc32c_intel ghash_clmulni_intel pcbc i915 ahci aesni_intel libahci libata 
> sdhci_pci aes_x86_64 crypto_simd cryptd cqhci glue_helper scsi_mod psmouse 
> i2c_algo_bit sdhci drm_kms_helper mmc_core ehci_pci ehci_hcd i2c_i801 lpc_ich 
> drm mfd_core
> [11315.009108]  usbcore e1000e usb_common thermal wmi video button
> [11315.009114] CPU: 0 PID: 8807 Comm: rmmod Tainted: GW 
> 4.19.0-17-amd64 #1 Debian 4.19.194-1
> [11315.009115] Hardware name: LENOVO 4290A48/4290A48, BIOS 8DET49WW (1.19 ) 
> 07/01/2011
> [11315.009123] RIP: 0010:iwl_trans_pcie_grab_nic_access+0x1e8/0x220 [iwlwifi]
> [11315.009126] Code: e6 c3 49 8d 56 08 bf 00 02 00 00 e8 e2 36 dd c2 e9 33 ff 
> ff ff 89 c6 48 c7 c7 b0 b5 ed c0 c6 05 e1 45 02 00 01 e8 01 0d 44 c3 <0f> 0b 
> e9 ee fe ff ff 48 8b 7b 30 48 c7 c1 18 b6 ed c0 31 d2 31 f6
> [11315.009127] RSP: 0018:a81cc394fdc8 EFLAGS: 00010082
> [11315.009129] RAX:  RBX: 9a9e13830018 RCX: 
> 0006
> [11315.009130] RDX: 0007 RSI: 0092 RDI: 
> 9a9e160166b0
> [11315.009131] RBP:  R08: 05d9 R09: 
> 0004
> [11315.009132] R10:  R11: 0001 R12: 
> 9a9e1383a258
> [11315.009133] R13: a81cc394fdf8 R14:  R15: 
> 
> [11315.009135] FS:  7f3ddc3ab480() GS:9a9e1600() knlGS:
> 
> [11315.009136] CS:  0010 DS:  ES:  CR0: 80050033
> [11315.009137] CR2: 5573c3c42750 CR3: 00011e5f4003 CR4: 
> 000606f0
> [11315.009138] Call Trace:
> [11315.009149]  iwl_write_prph+0x37/0x90 [iwlwifi]
> [11315.009156]  iwl_pcie_apm_init+0x1b2/0x210 [iwlwifi]
> [11315.009164]  iwl_pcie_apm_stop+0x324/0x360 [iwlwifi]
> [11315.009171]  iwl_trans_pcie_op_mode_leave+0x86/0x150 [iwlwifi]
> [11315.009177]  iwl_op_mode_dvm_stop+0x8b/0xb0 [iwldvm]
> [11315.009184]  _iwl_op_mode_stop.isra.8+0x27/0x40 [iwlwifi]
> [11315.009190]  iwl_opmode_deregister+0x5e/0xb0 [iwlwifi]
> [11315.009196]  iwl_exit+0xc/0x486 [iwldvm]
> [11315.009200]  __x64_sys_delete_module+0x190/0x2e0
> [11315.009204]  

Re: Bug#990423: stretch kernel 4.9.0-16-amd64 crashes randomly

[Andrei POPESCU]

Control: reassign -1 src:linux

On Lu, 28 iun 21, 19:36:45, boobarkee wrote:
> Package: linux-image-4.9.0-16-amd64
> I recently installed the 4.9.0-16 kernel via apt-get dist-upgrade without any 
> problem.Since then my system crashed randomly 3 times. 2-times prior to 
> graphical login, 1 time shortly after login. Each time I got a stack trace on 
> the console, I believe they were differnt each time.
> Then I switched back to 4.9.0-15, which runs perfectly stable.
> My system is a HP 635 laptop.
> /proc/cpu (just for one kernel):processor   : 1
> vendor_id   : AuthenticAMD
> cpu family  : 20
> model   : 2
> model name  : AMD E-450 APU with Radeon(tm) HD Graphics
> stepping    : 0
> microcode   : 0x5000119
> cpu MHz : 825.000
> cache size  : 512 KB
> physical id : 0
> siblings    : 2
> core id : 1
> cpu cores   : 2
> apicid  : 1
> initial apicid  : 1
> fpu : yes
> fpu_exception   : yes
> cpuid level : 6
> wp  : yes
> flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
> cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt 
> pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid 
> aperfmperf pni monitor ssse3 cx16 popcnt lahf_lm cmp_legacy svm extapic 
> cr8_legacy abm sse4a misalignsse 3dnowprefetch ibs skinit wdt hw_pstate 
> vmmcall arat npt lbrv svm_lock nrip_save pausefilter
> bugs    : fxsave_leak sysret_ss_attrs null_seg spectre_v1 spectre_v2 
> spec_store_bypass
> bogomips    : 3292.81
> TLB size    : 1024 4K pages
> clflush size    : 64
> cache_alignment : 64
> address sizes   : 36 bits physical, 48 bits virtual
> power management: ts ttp tm stc 100mhzsteps hwpstate
> 
> Best regardsCarl 

Reassigning to source package as this particular binary package is not 
known to the BTS anymore.

Kind regards,
Andrei
-- 
Looking after bugs assigned to unknown or inexistent packages


signature.asc
Description: PGP signature

Re: Bug#990404: 5.10.0-7-rt-amd64 gives IRQ 29 HANDLER ERROR

[Andrei POPESCU]

Control: reassign -1 src:linux 5.10.40-1

On Lu, 28 iun 21, 09:55:31, CG Netlink wrote:
> Package: 5.10.0-7-rt-amd64
> Version: 5.10.0-7-rt
> Debian: Linux hostname 5.10.0-7-rt-amd64 #1 SMP PREEMPT_RT Debian 5.10.40-1 
> (2021-05-28) x86_64 GNU/Linux
> 
> On booting with this kernel i receive the following error. The error exists 
> but everything else is fine. No crash, no hiccups.
> 
> 
> [1.355493] [ cut here ]
> [1.355494] irq 29 handler irq_default_primary_handler+0x0/0x10 enabled 
> interrupts
> [1.355501] WARNING: CPU: 5 PID: 112 at kernel/irq/handle.c:159 
> __handle_irq_event_percpu+0x1e9/0x1f0
> [1.355504] Modules linked in: libaes(+) crypto_simd ahci(+) cryptd 
> xhci_pci(+) glue_helper nvme libahci drm_kms_helper xhci_hcd libata nvme_core 
> cec t10_pi scsi_mod crc_t10dif usbcore drm i2c_piix4 crct10dif_generic 
> usb_common crct10dif_pclmul crct10dif_common i2c_hid wmi battery video hid 
> button
> [1.355515] CPU: 5 PID: 112 Comm: irq/7-pinctrl_a Not tainted 
> 5.10.0-7-rt-amd64 #1 Debian 5.10.40-1
> [1.355517] Hardware name: LENOVO 81YQ/LNVNB161216, BIOS E7CN41WW 
> 05/14/2021
> [1.355518] RIP: 0010:__handle_irq_event_percpu+0x1e9/0x1f0
> [1.355521] Code: cb fe ff ff e9 da 34 7a 00 45 31 e4 e9 ca fe ff ff 48 8b 
> 13 44 89 ee 48 c7 c7 b8 a2 cd 8f c6 05 cc 91 7a 01 01 e8 17 d2 79 00 <0f> 0b 
> eb bd 0f 1f 00 0f 1f 44 00 00 55 48 89 fd 48 c7 c7 7c 55 d6
> [1.355522] RSP: 0018:bb2c0035fd98 EFLAGS: 00010282
> [1.355523] RAX:  RBX: 9f3140aa1780 RCX: 
> 
> [1.355524] RDX: 0001 RSI: 8fd0e6d4 RDI: 
> 
> [1.355525] RBP: bb2c0035fde4 R08: 90263b80 R09: 
> 0001
> [1.355525] R10: 000f R11: bb2c0035facd R12: 
> 
> [1.355526] R13: 001d R14: 9f3140a75e00 R15: 
> 0002
> [1.355527] FS:  () GS:9f343f74() 
> knlGS:
> [1.355528] CS:  0010 DS:  ES:  CR0: 80050033
> [1.355528] CR2: 562b1b1f75e0 CR3: 000150082000 CR4: 
> 00350ee0
> [1.355529] Call Trace:
> [1.355533]  handle_irq_event_percpu+0x53/0xa0
> [1.355535]  handle_irq_event+0x52/0x90
> [1.355536]  handle_level_irq+0xa8/0x1c0
> [1.355538]  generic_handle_irq+0x47/0x50
> [1.355540]  amd_gpio_irq_handler+0x15f/0x1b0
> [1.355543]  ? irq_thread_fn+0x60/0x60
> [1.355544]  irq_forced_thread_fn+0x31/0x80
> [1.355545]  irq_thread+0xe2/0x1c0
> [1.355546]  ? irq_finalize_oneshot.part.0+0xd0/0xd0
> [1.355548]  ? irq_thread_check_affinity+0xe0/0xe0
> [1.355548]  kthread+0x186/0x1a0
> [1.31]  ? __kthread_parkme+0xa0/0xa0
> [1.32]  ret_from_fork+0x22/0x30
> [1.35] ---[ end trace 0002 ]---
> 
> 
> 
> inxi -F:
> 
> System:Host: hostname Kernel: 5.10.0-7-rt-amd64 x86_64 bits: 64 Console: 
> tty 0 Distro: Debian GNU/Linux 11 (bullseye)
> Machine:   Type: Laptop System: LENOVO product: 81YQ v: IdeaPad 5 15ARE05 
> serial: PF2LEZ5D
>Mobo: LENOVO model: LNVNB161216 v: SDK0J40709WIN serial: PF2LEZ5D 
> UEFI: LENOVO v: E7CN41WW date: 05/14/2021
> Battery:   ID-1: BAT0 charge: 69.1 Wh condition: 70.7/70.0 Wh (101%)
> CPU:   Info: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics bits: 
> 64 type: MCP L2 cache: 4 MiB
>Speed: 1397 MHz min/max: 1400/2000 MHz Core speeds (MHz): 1: 1397 
> 2: 1397 3: 1397 4: 1397 5: 1397 6: 1397 7: 1397
>8: 1397
> Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Renoir driver: amdgpu 
> v: kernel
>Device-2: IMC Networks Integrated Camera type: USB driver: uvcvideo
>Display: server: X.org 1.20.11 driver: loaded: amdgpu,ati 
> unloaded: fbdev,modesetting,vesa tty: 157x79
>Message: Advanced graphics data unavailable in console for root.
> Audio: Device-1: Advanced Micro Devices [AMD/ATI] driver: snd_hda_intel
>Device-2: Advanced Micro Devices [AMD] 
> Raven/Raven2/FireFlight/Renoir Audio Processor driver: N/A
>Device-3: Advanced Micro Devices [AMD] Family 17h HD Audio driver: 
> snd_hda_intel
>Device-4: JMTek LLC. USB PnP Audio Device type: USB driver: 
> hid-generic,snd-usb-audio,usbhid
>Sound Server: ALSA v: k5.10.0-7-rt-amd64
> Network:   Message: No Device data found.
>Device-1: Realtek RTL8153 Gigabit Ethernet Adapter type: USB 
> driver: r8152
>IF: enx00e04c680469 state: up speed: 100 Mbps duplex: full mac: 
> 00:e0:4c:68:04:69
> Bluetooth: Device-1: Intel AX200 Bluetooth type: USB driver: N/A
>Message: Required tool hciconfig not installed. Check --recommends
> Drives:Local Storage: total: 476.94 GiB used: 54.98 GiB (11.5%)
>ID-1: /dev/nvme0n1 vendor: SK Hynix model: HFM512GDHTNI-87A0B 
> size: 476.94 GiB
> Partition: ID-1: / size: 449.95 GiB used: 

Re: Bug#989777: Severity: High / Debian 10 & 11 with Kernel 5.10.x-amd64 => Intel AX210 Wifi & Bluetooth not work

[Andrei POPESCU]

On Lu, 14 iun 21, 17:51:35, pham...@bluewin.ch wrote:
> Hello Vincent,
> And thank you for your message.
> I just tested the two new live images:
> - debian-live-blsy-DI-rc2-amd64-cinnamon+nonfree.iso  2021-06-11 
> 18:133.2G
> - debian-live-testing-amd64-cinnamon+nonfree.iso  2021-06-14 
> 07:553.2G
> Both work with firmware iwlwifi_20210315-2 so they don't work on my system.
> I don't know where to find a version of Debian 11 live including the old 
> firmware_iwlwifi 20210208-4 you are telling me about.
> I would like to do a test for you if you provide me with a download URL of a 
> live version of Debian 11 equipped with this firmware_iwlwifi 20210208-4. 
> Also note that I can't seem to find a download link for 
> firmware_iwlwifi_20210208-4.deb alone.
> Meilleures salutations / Best regards.
> Philippe

Hello Philippe,

(not the maintainer, but maybe I can still assist)

The link to the .deb package was provided in Vincent's message, I'll 
include it again here:

https://snapshot.debian.org/archive/debian/20210313T203823Z/pool/non-free/f/firmware-nonfree/firmware-iwlwifi_20210208-4_all.deb

This is a direct download link, your browser should offer to save the 
file. Copy it to a USB stick and insert it during the installation.

In case the installer doesn't ask at all (because it already found a 
firmware) it is possible to install it manually via the console, or just 
use a regular image (without firmware included).

If you need any help with this feel free to contact one of Debian's 
support channels:

https://www.debian.org/support

Hope this helps,
Andrei
-- 
Looking after bugs assigned to unknown or inexistent packages


signature.asc
Description: PGP signature

Re: Bug#989777: Debian 10 & 11 with Kernel 5.10.x-amd64 => Intel AX210 Wifi & Bluetooth not work

[Andrei POPESCU]

Reassign -1 src:linux 5.10.40-1

On Sb, 12 iun 21, 21:11:02, pham...@bluewin.ch wrote:
> Package: kernel 
> Version: 5.10.x-amd64
> Bug Description: My Intel AX210 Wifi and Bluetooth card not work
> Intel indicates on its website that this AX210 card is compatible from kernel 
> 5.10 !?!
> https://www.intel.com/content/www/us/en/support/articles/05511/wireless.html

Please try installing using an image from here:


https://cdimage.debian.org/images/unofficial/non-free/images-including-firmware/

> My laptop does not have an RJ-45 port, I do not have access to the internet, 
> nor to my Bluetooth devices such as my mouse, my keyboard, my headphones ;-(
> Best regards.
> Philippe

Reassigning to correct package.

Kind regards,
Andrei
-- 
Looking after bugs assigned to unknown or inexistent packages


signature.asc
Description: PGP signature

Re: Bug#989718: Linux RT kernel not working for compile using SID branch

[Andrei POPESCU]

Control: reassign -1 src:linux 5.10.42-1

On Vi, 11 iun 21, 08:19:06, ionut n wrote:
> Package: linuxVersion: 5.10.42-1ABINAME='5.10.0-8'
> SOURCEVERSION='5.10.42-1'
 
Hello,

Please note your mailer is mangling line breaks (and the binary package 
'linux' doesn't exist anyway).

Reassigning to correct (source) package.

> Hi Debian Team,
> I try to compile Linux kernel, but not working.One patch for RT flavor is not 
> compatible.
> debian/patches-rt/series:0001-z3fold-remove-preempt-disabled-sections-for-RT.patch#0002-stop_machine-Add-function-and-caller-debug-info.patch0003-sched-Fix-balance_callback.patch
> I comment line and compile started. But i view other issue now with bfd_close 
> / libbfd.
> util/symbol-elf.c:555:46: error: request for member 'build_id' in something 
> not a structure or union  555 |  memcpy(bid->data, abfd->build_id->data, 
> abfd->build_id->size);      |                                              
> ^~util/symbol-elf.c:556:25: error: request for member 'build_id' in something 
> not a structure or union  556 |  memset(bid->data + abfd->build_id->size, 0, 
> size - abfd->build_id->size);      |                         ^~
> OS Release:PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"NAME="Debian 
> GNU/Linux"VERSION_ID="11"VERSION="11 
> (bullseye)"VERSION_CODENAME=bullseyeID=debianHOME_URL="https://www.debian.org/"SUPPORT_URL="https://www.debian.org/support"BUG_REPORT_URL="https://bugs.debian.org/;
> OS GCC:gcc (Debian 10.2.1-6) 10.2.1 20210110Copyright (C) 2020 Free Software 
> Foundation, Inc.This is free software; see the source for copying conditions. 
>  There is NOwarranty; not even for MERCHANTABILITY or FITNESS FOR A 
> PARTICULAR PURPOSE.
> OS GLIBC:ldd (Debian GLIBC 2.31-12) 2.31Copyright (C) 2020 Free Software 
> Foundation, Inc.This is free software; see the source for copying conditions. 
>  There is NOwarranty; not even for MERCHANTABILITY or FITNESS FOR A 
> PARTICULAR PURPOSE.Written by Roland McGrath and Ulrich Drepper.
> Debian Linux Branch: sidDebian Linux URL Git: 
> https://salsa.debian.org/kernel-team/linux.gitCommand for starting compiling: 
> CPUCNT=142time DEBIAN_KERNEL_USE_CCACHE=true DEBIAN_KERNEL_JOBS=$CPUCNT     
> fakeroot make -j$CPUCNT -f debian/rules.gen binary-arch_amd64_real
> Can you help me with this problem?
> 
> Thanks.Ionut NechitaRomaniaSoftware Enginner

Kind regards,
Andrei
-- 
Looking after bugs assigned to unknown or inexistent packages


signature.asc
Description: PGP signature

Re: Bug#985369: Banana Pi Call Trace in sound/core/init.c:207 snd_card_new+0x430/0x480 [snd]

[Andrei POPESCU]

Control: reassign -1 src:linux 5.10.19-1

On Ma, 16 mar 21, 19:26:43, Tuxo wrote:
> Package: 5.10.0-4-armmp-lpae
> Version: Debian 5.10.19-1: armhf
> 
> Call Trace coming up:
> 
> [  +0.303626] [ cut here ]
> [  +0.008081] WARNING: CPU: 0 PID: 248 at sound/core/init.c:207
> snd_card_new+0x430/0x480 [snd]
> [  +0.007999] Modules linked in: sun4i_codec(E+) snd_soc_core(E)
> snd_pcm_dmaengine(E) snd_pcm(E) nvmem_sunxi_sid(E) sun4i_ts(E) sg(E)
> snd_timer(E) snd(E) sunxi_cir(E) soundcore(E) rc_core(E) sun4i_ss(E+)
> libdes(E) sunxi_wdt(E) sunxi_cedrus(CE) videobuf2_dma_contig(E)
> v4l2_mem2mem(E) videobuf2_memops(E) videobuf2_v4l2(E) videobuf2_common(E)
> leds_gpio(E) cpufreq_dt(E) fuse(E) configfs(E) sunrpc(E) ip_tables(E)
> x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) btrfs(E)
> blake2b_generic(E) xor(E) xor_neon(E) raid6_pq(E) libcrc32c(E)
> crc32c_generic(E) f2fs(E) crc32_generic(E) sd_mod(E) t10_pi(E) crc_t10dif(E)
> crct10dif_generic(E) crct10dif_common(E) axp20x_usb_power(E) industrialio(E)
> pinctrl_axp209(E) axp20x_regulator(E) realtek(E) sun4i_backend(E)
> dwmac_sunxi(E) stmmac_platform(E) stmmac(E) ohci_platform(E) pcs_xpcs(E)
> phylink(E) ahci_sunxi(E) ehci_platform(E) ohci_hcd(E) libahci_platform(E)
> ptp(E) libahci(E) sunxi(E) phy_generic(E) lima(E) libata(E) gpu_sched(E)
> musb_hdrc(E)
> [  +0.000354]  pps_core(E) ehci_hcd(E) udc_core(E) i2c_mv64xxx(E)
> scsi_mod(E) sun4i_drm_hdmi(E) usbcore(E) cec(E) spi_sun4i(E) sunxi_mmc(E)
> phy_sun4i_usb(E) sun4i_drm(E) sun4i_frontend(E) sun4i_tcon(E)
> sun8i_tcon_top(E) drm_kms_helper(E) display_connector(E) drm(E)
> [  +0.064237] CPU: 0 PID: 248 Comm: systemd-udevd Tainted: G C E
> 5.10.0-4-armmp-lpae #1 Debian 5.10.19-1
> [  +0.010143] Hardware name: Allwinner sun7i (A20) Family
> [  +0.010019] Backtrace:
> [  +0.009907] [] (dump_backtrace) from []
> (show_stack+0x20/0x24)
> [  +0.010172]  r7:00cf r6:600f0113 r5: r4:c16d04d0
> [  +0.010253] [] (show_stack) from []
> (dump_stack+0xc8/0xdc)
> [  +0.010012] [] (dump_stack) from []
> (__warn+0xfc/0x158)
> [  +0.010183]  r7:00cf r6:0009 r5:bf6e1604 r4:bf6eb01c
> [  +0.010016] [] (__warn) from []
> (warn_slowpath_fmt+0x70/0xe4)
> [  +0.010317]  r7:bf6e1604 r6:00cf r5:bf6eb01c r4:
> [  +0.010074] [] (warn_slowpath_fmt) from []
> (snd_card_new+0x430/0x480 [snd])
> [  +0.010305]  r8:c2e0f8c4 r7:c1a3ec10 r6: r5:c2ca3000 r4:
> [  +0.010210] [] (snd_card_new [snd]) from []
> (snd_soc_bind_card+0x3a8/0xa30 [snd_soc_core])
> [  +0.010262]  r10: r9:bf759d8c r8:c1a26e80 r7:0001 r6:0050
> r5:c2e0f840
> [  +0.010202]  r4:c2bc2d00
> [  +0.010557] [] (snd_soc_bind_card [snd_soc_core]) from
> [] (snd_soc_register_card+0xf8/0x108 [snd_soc_core])
> [  +0.010486]  r10:0024 r9:bf733170 r8:c1a26e80 r7:bf72e6f4 r6:c1a3ec10
> r5:c2bd4a00
> [  +0.010532]  r4:c2e0f840
> [  +0.010512] [] (snd_soc_register_card [snd_soc_core]) from
> [] (sun4i_codec_probe+0x230/0x468 [sun4i_codec])
> [  +0.011003]  r5:c2bd4a00 r4:0002
> [  +0.010799] [] (sun4i_codec_probe [sun4i_codec]) from
> [] (platform_drv_probe+0x58/0xa8)
> [  +0.011063]  r8: r7:c17f1de0 r6:bf733170 r5:c1a3ec10 r4:
> [  +0.011147] [] (platform_drv_probe) from []
> (really_probe+0x108/0x514)
> [  +0.011228]  r7:c17f1de0 r6: r5:c17f1dd8 r4:c1a3ec10
> [  +0.011134] [] (really_probe) from []
> (driver_probe_device+0x100/0x1d4)
> [  +0.16]  r10:bf733940 r9:c1604e00 r8:c2f15f30 r7:bf733170 r6:c1a3ec54
> r5:bf733170
> [  +0.06]  r4:c1a3ec10
> [  +0.15] [] (driver_probe_device) from []
> (device_driver_attach+0xb8/0xc0)
> [  +0.10]  r9:c1604e00 r8:c2f15f30 r7:bf733170 r6:c1a3ec54 r5:
> r4:c1a3ec10
> [  +0.12] [] (device_driver_attach) from []
> (__driver_attach+0x9c/0x150)
> [  +0.18]  r7:c17579a8 r6:c1a3ec10 r5:bf733170 r4:
> [  +0.079177] [] (__driver_attach) from []
> (bus_for_each_dev+0x84/0xd0)
> [  +0.16]  r7:c17579a8 r6:c0aac58c r5:bf733170 r4:
> [  +0.13] [] (bus_for_each_dev) from []
> (driver_attach+0x2c/0x30)
> [  +0.08]  r6: r5:c2f71780 r4:bf733170
> [  +0.11] [] (driver_attach) from []
> (bus_add_driver+0x120/0x20c)
> [  +0.13] [] (bus_add_driver) from []
> (driver_register+0x98/0x128)
> [  +0.08]  r7: r6:bf733a70 r5: r4:bf733170
> [  +0.13] [] (driver_register) from []
> (__platform_driver_register+0x50/0x58)
> [  +0.07]  r5:c2fbe300 r4:c17579a8
> [  +0.53] [] (__platform_driver_register) from []
> (sun4i_codec_driver_init+0x24/0x1000 [sun4i_codec])
> [  +0.06]  r5:c2fbe300 r4:bf704000
> [  +0.24] [] (sun4i_codec_driver_init [sun4i_codec]) from
> [] (do_one_initcall+0x50/0x27c)
> [  +0.14] [] (do_one_initcall) from []
> (do_init_module+0x70/0x2a4)
> [  +0.09]  r7:c2f15ea8 r6:bf733a70 r5:c2fbe300 r4:bf733940
> [  +0.10] [] (do_init_module) from []
> (load_module+0x2260/0x264c)
> [  +0.08]  r6:bf733a70 

Re: Bug#980284: linux-image-5.10.0-1-amd64: InfraRed receiving timeout, remote control button pushes duplicated

[Andrei POPESCU]

Control: reassign -1 src:linx 5.10.4-1

On Du, 17 ian 21, 10:35:07, Martin King wrote:
> Package: src:linuxX-Debbugs-Cc: mar...@mjking.org
> Version: 5.10.4-1
> Severity: important
> 
> Dear Maintainer,
> 
> Intel NUC7i5BNH using internal CIR (Consumer InfraRed)
> 
> Device setup;
> ~$ ir-keytable
> Found /sys/class/rc/rc0/ with:
> Name: ITE8708 CIR transceiver
> Driver: ite-cir
> Default keymap: rc-rc6-mce
> Input device: /dev/input/event7
> LIRC device: /dev/lirc0
> Attached BPF protocols: Operation not permitted
> Supported kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo 
> mce_kbd rc-6 sharp xmp imon 
> Enabled kernel protocols: lirc sony 
> bus: 25, vendor/product: 1283:, version: 0x
> Repeat delay = 500 ms, repeat period = 125 ms
> 
> With current bullseye kernel, 5.10.0-1-amd64, all button pushes on IR handset 
> (sony protocol) are duplicated.
> 
> Output from ~$ evemu-record /dev/input/event7
> 
> (EV_KEY "1" indicates key down, "0" key up. Repeated key down shown after 
> approx. 1 second is not a physical key press, output shown is one click of 
> "OK" key)
> 
> E: 0.01 0004 0004 65637 # EV_MSC / MSC_SCAN 65637
> E: 0.01 0001 0160 0001  # EV_KEY / KEY_OK   1
> E: 0.01     #  SYN_REPORT (0) -- +0ms
> E: 0.045144 0004 0004 65637 # EV_MSC / MSC_SCAN 65637
> E: 0.045144     #  SYN_REPORT (0) -- +45ms
> E: 0.089035 0004 0004 65637 # EV_MSC / MSC_SCAN 65637
> E: 0.089035     #  SYN_REPORT (0) -- +44ms
> E: 0.191682 0001 0160   # EV_KEY / KEY_OK   0
> E: 0.191682     #  SYN_REPORT (0) -- 
> +102ms
> E: 1.297171 0004 0004 65637 # EV_MSC / MSC_SCAN 65637
> E: 1.297171 0001 0160 0001  # EV_KEY / KEY_OK   1
> E: 1.297171     #  SYN_REPORT (0) -- 
> +1106ms
> E: 1.399612 0001 0160   # EV_KEY / KEY_OK   0
> E: 1.399612     #  SYN_REPORT (0) -- 
> +102ms
> 
> With previous kernel, 5.9.0-5-amd64, behaviour was as expected, no 
> duplication. The obvious difference between kernels is much longer receiving 
> timeout.
> 
> Previous kernel;
> ~$ ir-ctl -f
> Receive features /dev/lirc0:
>  - Device can receive raw IR
>  - Can report decoded scancodes and protocol
>  - Resolution 8 microseconds
>  - Set receive carrier
>  - Receiving timeout 16000 microseconds
>  - Can set receiving timeout min 1181 microseconds, max 125 microseconds
> Send features /dev/lirc0:
>  - Device can send raw IR
>  - IR scancode encoder
>  - Set carrier
>  - Set duty cycle
> 
> Current kernel;
> ~ir-ctl -f
> Receive features /dev/lirc0:
>  - Device can receive raw IR
>  - Can report decoded scancodes and protocol
>  - Resolution 8 microseconds
>  - Set receive carrier
>  - Receiving timeout 1180480 microseconds
>  - Can set receiving timeout min 1180480 microseconds, max 125 
> microseconds
> Send features /dev/lirc0:
>  - Device can send raw IR
>  - IR scancode encoder
>  - Set carrier
>  - Set duty cycle
> 
> Timeout is already at minimum allowed value.
> 
> I am not certain that this is the cause but can report that IR remote control 
> has failed on this model of Intel NUC with 5.10.0-1-amd64 kernel.
> 
> 
> -- Package-specific info:
> ** Version:
> Linux version 5.10.0-1-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 
> 10.2.1-3) 10.2.1 20201224, GNU ld (GNU Binutils for Debian) 2.35.1) #1 SMP 
> Debian 5.10.4-1 (2020-12-31)
> 
> ** Command line:
> BOOT_IMAGE=/boot/vmlinuz-5.10.0-1-amd64 
> root=UUID=72a8f6e8-b30b-4c51-b902-f83f15c52cfa ro quiet
> 
> ** Not tainted
> 
> ** Kernel log:
> Unable to read kernel log; any relevant messages should be attached
> 
> ** Model information
> sys_vendor: Intel Corporation
> product_name: NUC7i5BNH
> product_version: J31169-307
> chassis_vendor: Intel Corporation
> chassis_version: 2
> bios_vendor: Intel Corp.
> bios_version: BNKBL357.86A.0083.2020.0714.1344
> board_vendor: Intel Corporation
> board_name: NUC7i5BNB
> board_version: J31144-306
> 
> ** Loaded modules:
> snd_hrtimer
> snd_seq
> snd_seq_device
> nf_tables
> libcrc32c
> nfnetlink
> bridge
> stp
> llc
> intel_rapl_msr
> intel_rapl_common
> cmac
> algif_hash
> algif_skcipher
> af_alg
> snd_hda_codec_hdmi
> bnep
> snd_hda_codec_realtek
> btusb
> btrtl
> x86_pkg_temp_thermal
> btbcm
> intel_powerclamp
> snd_hda_codec_generic
> btintel
> coretemp
> ledtrig_audio
> bluetooth
> kvm_intel
> snd_soc_skl
> snd_soc_hdac_hda
> snd_hda_ext_core
> snd_soc_sst_ipc
> snd_soc_sst_dsp
> snd_soc_acpi_intel_match
> jitterentropy_rng
> snd_soc_acpi
> kvm
> snd_hda_intel
> drbg
> irqbypass
> snd_intel_dspcfg
> soundwire_intel
> ir_sony_decoder
> iwlmvm
> soundwire_generic_allocation
> 

Bug#979187: 5.9.15 Debian kernel stopped booting on raspi 4 with Elecom USB MSD 056e:6a13

[Andrei POPESCU]

On Lu, 04 ian 21, 18:40:44, Ryutaroh Matsumoto wrote:
> Hi,
> 
> > reportbug linux-image-5.9.0-5-arm64
> > while booted with this kernel and select the option to Follow-Up to this 
> > bug (you might want to have the bug number handy), so that reportbug can 
> > collect more information about your system.
> 
> I wanted to do that, but as the kernel does not boot with the
> problematic USB MSD, I cannot use reportbug on it.
> Did you mean that I should boot linux-image-5.9.0-5-arm64
> on an sdcard or another usb msd, and run reportbug on it?

If possible that might be very helpful.

You could also try asking on one of Debian's support channels, in case 
there is some workaround.

https://www.debian.org/support

Kind regards,
Andrei
-- 
Looking after bugs assigned to unknown or inexistent packages


signature.asc
Description: PGP signature

Re: Bug#979187: 5.9.15 Debian kernel stopped booting on raspi 4 with Elecom USB MSD 056e:6a13

[Andrei POPESCU]

Control: reassign -1 src:linux 5.9.15-1

On Lu, 04 ian 21, 11:03:09, Ryutaroh Matsumoto wrote:
> Package: llinux-image-5.9.0-5-arm64
> Version: 5.9.15-1
> Severity: normal

Hello,

There is a typo in the package name, so the bug was assigned to an 
inexistent package, fixing it with this message.


Please use

reportbug linux-image-5.9.0-5-arm64

while booted with this kernel and select the option to Follow-Up to this 
bug (you might want to have the bug number handy), so that reportbug can 
collect more information about your system.

Kind regards,
Andrei
 
> Dear Debian kernel maintainers,
> 
> This is a report different from
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977694
> 
> Debian kernel earlier than 5.9.14 booted with the
> following Elecom USB MSD.
> But Debian kernel 5.9.15 stopped working, while
> it boots with another USB MSD from Elecom...
> 
> Best regards, Ryutaroh Matsumoto
> V
> # lsusb -v
> 
> Bus 002 Device 005: ID 056e:6a13 Elecom Co., Ltd ESD-EMN
> Device Descriptor:
>   bLength18
>   bDescriptorType 1
>   bcdUSB   3.20
>   bDeviceClass0 
>   bDeviceSubClass 0 
>   bDeviceProtocol 0 
>   bMaxPacketSize0 9
>   idVendor   0x056e Elecom Co., Ltd
>   idProduct  0x6a13 
>   bcdDevice   11.00
>   iManufacturer   1 ELECOM
>   iProduct2 ESD-EMN
>   iSerial 3 20B10164305600A9
>   bNumConfigurations  1
>   Configuration Descriptor:
> bLength 9
> bDescriptorType 2
> wTotalLength   0x0079
> bNumInterfaces  1
> bConfigurationValue 1
> iConfiguration  0 
> bmAttributes 0x80
>   (Bus Powered)
> MaxPower  504mA
> Interface Descriptor:
>   bLength 9
>   bDescriptorType 4
>   bInterfaceNumber0
>   bAlternateSetting   0
>   bNumEndpoints   2
>   bInterfaceClass 8 Mass Storage
>   bInterfaceSubClass  6 SCSI
>   bInterfaceProtocol 80 Bulk-Only
>   iInterface  0 
>   Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x01  EP 1 OUT
> bmAttributes2
>   Transfer TypeBulk
>   Synch Type   None
>   Usage Type   Data
> wMaxPacketSize 0x0400  1x 1024 bytes
> bInterval   0
> bMaxBurst   8
>   Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x82  EP 2 IN
> bmAttributes2
>   Transfer TypeBulk
>   Synch Type   None
>   Usage Type   Data
> wMaxPacketSize 0x0400  1x 1024 bytes
> bInterval   0
> bMaxBurst   8
> Interface Descriptor:
>   bLength 9
>   bDescriptorType 4
>   bInterfaceNumber0
>   bAlternateSetting   1
>   bNumEndpoints   4
>   bInterfaceClass 8 Mass Storage
>   bInterfaceSubClass  6 SCSI
>   bInterfaceProtocol 98 
>   iInterface  0 
>   Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x01  EP 1 OUT
> bmAttributes2
>   Transfer TypeBulk
>   Synch Type   None
>   Usage Type   Data
> wMaxPacketSize 0x0400  1x 1024 bytes
> bInterval   0
> bMaxBurst   8
> MaxStreams  4
> Data-out pipe (0x04)
>   Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x82  EP 2 IN
> bmAttributes2
>   Transfer TypeBulk
>   Synch Type   None
>   Usage Type   Data
> wMaxPacketSize 0x0400  1x 1024 bytes
> bInterval   0
> bMaxBurst   8
> MaxStreams  4
> Data-in pipe (0x03)
>   Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x03  EP 3 OUT
> bmAttributes2
>   Transfer TypeBulk
>   Synch Type   None
>   Usage Type   Data
> wMaxPacketSize 0x0400  1x 1024 bytes
> bInterval   0
> bMaxBurst   0
> Command pipe (0x01)
>   Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x84  EP 4 IN
> 

Re: Bug#978753: usercopy: Kernel memory exposure attempt

[Andrei POPESCU]

Control: reassign -1 src:linux 4.19.160-2

On Jo, 31 dec 20, 12:45:47, Markus Bäcklund wrote:
> Package: src:linux-image-4.19.0-13-amd64
> Version: 4.19.160-2
> Severity: critical
> Justification: breaks the whole system
> 
> 
> 
> -- Package-specific info:
> ** Kernel log: boot messages should be attached
> 
> 
> -- System Information:
> Debian Release: 10.7
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.4.86 (SMP w/4 CPU cores)
> Kernel taint flags: TAINT_UNSIGNED_MODULE
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_US:en (charmap=UTF-8)
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages linux-image-4.19.0-13-amd64 depends on:
> ii  initramfs-tools [linux-initramfs-tool]  0.133+deb10u1
> ii  kmod26-1
> ii  linux-base  4.6
> 
> Versions of packages linux-image-4.19.0-13-amd64 recommends:
> ii  apparmor 2.13.2-10
> ii  firmware-linux-free  3.4
> 
> Versions of packages linux-image-4.19.0-13-amd64 suggests:
> pn  debian-kernel-handbook  
> ii  grub-pc 2.02+dfsg1-20+deb10u2
> pn  linux-doc-4.19  
> 
> Versions of packages linux-image-4.19.0-13-amd64 is related to:
> pn  firmware-amd-graphics 
> pn  firmware-atheros  
> pn  firmware-bnx2 
> pn  firmware-bnx2x
> pn  firmware-brcm80211
> pn  firmware-cavium   
> pn  firmware-intel-sound  
> pn  firmware-intelwimax   
> pn  firmware-ipw2x00  
> pn  firmware-ivtv 
> pn  firmware-iwlwifi  
> pn  firmware-libertas 
> pn  firmware-linux-nonfree
> pn  firmware-misc-nonfree 
> pn  firmware-myricom  
> pn  firmware-netxen   
> pn  firmware-qlogic   
> pn  firmware-realtek  
> pn  firmware-samsung  
> pn  firmware-siano
> pn  firmware-ti-connectivity  
> pn  xen-hypervisor
> 
> -- no debconf information
> 
> 
> Caused system halt with message:
> 
> usercopy: Kernel memory exposure attempt detected from SLUB object 
> 'mm_struct(770:pm2-root.service)' (offset 272, size 320)!

-- 
Looking after bugs assigned to unknown or inexistent packages


signature.asc
Description: PGP signature

Bug#974528: Regression: built-in ethernet on PINE A64+ stopped working (dwmac-sun8i)

[Andrei POPESCU]

Control: fixed -1 5.9.11-1

On Mi, 11 nov 20, 20:42:52, Andrei POPESCU wrote:
> Package: src:linux
> Version: 5.9.1-1
> Severity: important
> X-Debbugs-Cc: andreimpope...@gmail.com
> 
> Dear Maintainers,
> 
> Everything appears to be fine (link is up, address assigned, etc.) yet 
> ping, wget, etc. all time out.
> 
> Same issue also with 5.9.6-1 while 5.8.14-1 and previous versions work 
> fine.
> 
> Kind regards,
> Andrei
> 
> 
> -- Package-specific info:
> ** Version:
> Linux version 5.9.0-1-arm64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 
> 10.2.0-15) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35.1) #1 SMP Debian 
> 5.9.1-1 (2020-10-17)
> 
> ** Command line:
> root=LABEL=pb64p rootwait rw rootflags=noatime
> 
> ** Tainted: C (1024)
>  * staging driver was loaded
> 
> ** Kernel log:
> [   11.264769] systemd[1]: Listening on Journal Socket.
> [   11.293028] systemd[1]: Listening on Network Service Netlink Socket.
> [   11.324904] systemd[1]: Listening on udev Control Socket.
> [   11.356578] systemd[1]: Listening on udev Kernel Socket.
> [   11.390069] systemd[1]: Mounting Huge Pages File System...
> [   11.426027] systemd[1]: Mounting POSIX Message Queue File System...
> [   11.461564] systemd[1]: Mounting NFSD configuration filesystem...
> [   11.501742] systemd[1]: Mounting RPC Pipe File System...
> [   11.543167] systemd[1]: Mounting Kernel Debug File System...
> [   11.578157] systemd[1]: Mounting Kernel Trace File System...
> [   11.608230] systemd[1]: Condition check resulted in Kernel Module 
> supporting RPCSEC_GSS being skipped.
> [   11.638763] systemd[1]: Starting Set the console keyboard layout...
> [   11.678568] systemd[1]: Starting Create list of static device nodes for 
> the current kernel...
> [   11.695407] RPC: Registered named UNIX socket transport module.
> [   11.717285] RPC: Registered udp transport module.
> [   11.717289] RPC: Registered tcp transport module.
> [   11.717291] RPC: Registered tcp NFSv4.1 backchannel transport module.
> [   11.794544] systemd[1]: Starting Load Kernel Module drm...
> [   11.827394] systemd[1]: Condition check resulted in Set Up Additional 
> Binary Formats being skipped.
> [   11.858512] systemd[1]: Starting Journal Service...
> [   11.972471] systemd[1]: Starting Load Kernel Modules...
> [   12.017036] systemd[1]: Starting Remount Root and Kernel File Systems...
> [   12.050318] Installing knfsd (copyright (C) 1996 o...@monad.swb.de).
> [   12.089900] systemd[1]: Starting Coldplug All udev Devices...
> [   12.134653] systemd[1]: Mounted Huge Pages File System.
> [   12.165035] systemd[1]: Mounted POSIX Message Queue File System.
> [   12.197041] systemd[1]: Mounted NFSD configuration filesystem.
> [   12.229460] systemd[1]: Mounted RPC Pipe File System.
> [   12.260981] systemd[1]: Started Journal Service.
> [   13.029351] random: crng init done
> [   13.043435] random: 7 urandom warning(s) missed due to ratelimiting
> [   13.423065] fuse: init (API version 7.31)
> [   13.455286] EXT4-fs (sdb1): mounted filesystem with ordered data mode. 
> Opts: (null)
> [   13.550228] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data 
> mode. Opts: (null)
> [   13.576018] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data 
> mode. Opts: (null)
> [   14.072349] audit: type=1400 audit(1605103249.756:2): apparmor="STATUS" 
> operation="profile_load" profile="unconfined" name="lsb_release" pid=261 
> comm="apparmor_parser"
> [   14.113776] audit: type=1400 audit(1605103249.756:3): apparmor="STATUS" 
> operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=262 
> comm="apparmor_parser"
> [   14.142128] audit: type=1400 audit(1605103249.756:4): apparmor="STATUS" 
> operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" 
> pid=262 comm="apparmor_parser"
> [   14.180524] audit: type=1400 audit(1605103249.756:5): apparmor="STATUS" 
> operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=263 
> comm="apparmor_parser"
> [   14.214473] audit: type=1400 audit(1605103249.756:6): apparmor="STATUS" 
> operation="profile_load" profile="unconfined" name="man_filter" pid=263 
> comm="apparmor_parser"
> [   14.240863] audit: type=1400 audit(1605103249.756:7): apparmor="STATUS" 
> operation="profile_load" profile="unconfined" name="man_groff" pid=263 
> comm="apparmor_parser"
> [   14.745315] sunxi-wdt 1c20ca0.watchdog: Watchdog enabled (timeo

Re: Bug#975489: Add Aqtion USB to 5Gbe driver (aqc111.ko) to linux-image

[Andrei POPESCU]

Control: reassign -1 src:linux
Control: severity -1 wishlist

On Du, 22 nov 20, 20:13:40, Nicolas Richeton wrote:
> Package: linux-image
> Version: 5.8.0-1amd64
> 
> Hello, 
> 
> Driver for Marvel/Aquantia AQtion USB to 5GbE Controller (aqc111) is not 
> included in Debian kernel package. 
> 
> It is included in linux kernel since nov. 2018 
> (https://github.com/torvalds/linux/blob/v5.9/drivers/net/usb/aqc111.c)
> 
> Could you please add it to the Debian kernel package (as module aqc111.ko) ? 
> 
> Thanks, 
> 
> Best Regards

Reassigning to correct package.

Kind regards,
Andrei
-- 
Looking after bugs assigned to unknown or inexistent packages


signature.asc
Description: PGP signature

Bug#974528: Regression: built-in ethernet on PINE A64+ stopped working (dwmac-sun8i)

[Andrei POPESCU]

Package: src:linux
Version: 5.9.1-1
Severity: important
X-Debbugs-Cc: andreimpope...@gmail.com

Dear Maintainers,

Everything appears to be fine (link is up, address assigned, etc.) yet 
ping, wget, etc. all time out.

Same issue also with 5.9.6-1 while 5.8.14-1 and previous versions work 
fine.

Kind regards,
Andrei


-- Package-specific info:
** Version:
Linux version 5.9.0-1-arm64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 
10.2.0-15) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35.1) #1 SMP Debian 
5.9.1-1 (2020-10-17)

** Command line:
root=LABEL=pb64p rootwait rw rootflags=noatime

** Tainted: C (1024)
 * staging driver was loaded

** Kernel log:
[   11.264769] systemd[1]: Listening on Journal Socket.
[   11.293028] systemd[1]: Listening on Network Service Netlink Socket.
[   11.324904] systemd[1]: Listening on udev Control Socket.
[   11.356578] systemd[1]: Listening on udev Kernel Socket.
[   11.390069] systemd[1]: Mounting Huge Pages File System...
[   11.426027] systemd[1]: Mounting POSIX Message Queue File System...
[   11.461564] systemd[1]: Mounting NFSD configuration filesystem...
[   11.501742] systemd[1]: Mounting RPC Pipe File System...
[   11.543167] systemd[1]: Mounting Kernel Debug File System...
[   11.578157] systemd[1]: Mounting Kernel Trace File System...
[   11.608230] systemd[1]: Condition check resulted in Kernel Module supporting 
RPCSEC_GSS being skipped.
[   11.638763] systemd[1]: Starting Set the console keyboard layout...
[   11.678568] systemd[1]: Starting Create list of static device nodes for the 
current kernel...
[   11.695407] RPC: Registered named UNIX socket transport module.
[   11.717285] RPC: Registered udp transport module.
[   11.717289] RPC: Registered tcp transport module.
[   11.717291] RPC: Registered tcp NFSv4.1 backchannel transport module.
[   11.794544] systemd[1]: Starting Load Kernel Module drm...
[   11.827394] systemd[1]: Condition check resulted in Set Up Additional Binary 
Formats being skipped.
[   11.858512] systemd[1]: Starting Journal Service...
[   11.972471] systemd[1]: Starting Load Kernel Modules...
[   12.017036] systemd[1]: Starting Remount Root and Kernel File Systems...
[   12.050318] Installing knfsd (copyright (C) 1996 o...@monad.swb.de).
[   12.089900] systemd[1]: Starting Coldplug All udev Devices...
[   12.134653] systemd[1]: Mounted Huge Pages File System.
[   12.165035] systemd[1]: Mounted POSIX Message Queue File System.
[   12.197041] systemd[1]: Mounted NFSD configuration filesystem.
[   12.229460] systemd[1]: Mounted RPC Pipe File System.
[   12.260981] systemd[1]: Started Journal Service.
[   13.029351] random: crng init done
[   13.043435] random: 7 urandom warning(s) missed due to ratelimiting
[   13.423065] fuse: init (API version 7.31)
[   13.455286] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: 
(null)
[   13.550228] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. 
Opts: (null)
[   13.576018] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. 
Opts: (null)
[   14.072349] audit: type=1400 audit(1605103249.756:2): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="lsb_release" pid=261 
comm="apparmor_parser"
[   14.113776] audit: type=1400 audit(1605103249.756:3): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=262 
comm="apparmor_parser"
[   14.142128] audit: type=1400 audit(1605103249.756:4): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" 
pid=262 comm="apparmor_parser"
[   14.180524] audit: type=1400 audit(1605103249.756:5): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=263 
comm="apparmor_parser"
[   14.214473] audit: type=1400 audit(1605103249.756:6): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="man_filter" pid=263 
comm="apparmor_parser"
[   14.240863] audit: type=1400 audit(1605103249.756:7): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="man_groff" pid=263 
comm="apparmor_parser"
[   14.745315] sunxi-wdt 1c20ca0.watchdog: Watchdog enabled (timeout=16 sec, 
nowayout=0)
[   14.780462] mc: Linux media interface: v0.10
[   14.781214] sun8i-ce 1c15000.crypto: Set mod clock to 3 (300 Mhz) 
from 2400 (24 Mhz)
[   14.824192] sun8i-ce 1c15000.crypto: will run requests pump with realtime 
priority
[   14.842889] sun8i-ce 1c15000.crypto: will run requests pump with realtime 
priority
[   14.871585] sun8i-ce 1c15000.crypto: will run requests pump with realtime 
priority
[   14.888372] sun8i-ce 1c15000.crypto: will run requests pump with realtime 
priority
[   14.909217] sun8i-ce 1c15000.crypto: Register cbc(aes)
[   14.966708] videodev: Linux video capture interface: v2.00
[   15.098064] lima 1c4.gpu: gp - mali400 version major 1 minor 1
[   15.110923] lima 1c4.gpu: pp0 - mali400 version major 1 minor 1
[   15.123213] lima 1c4.gpu: pp1 - mali400 

Re: Bug#972927: Kernel 5.9.1-1 - NIC problem

[Andrei POPESCU]

Control: reassign -1 src:linux 5.9.1-1

On Lu, 26 oct 20, 11:35:05, Jan VECEK wrote:
> Package: linux 5.9.1-1
>   Version: 5.9.1-1
> 
> After upgrade to Kernel 5.9.0-1-amd64 I have only one NIC eno1 ( eno2,
> eno3 and eno4 are gone) on my Super Micro A2SDi-4C-HLN4F.
> 
> = eno2, eno3 and eno4 are missing
> 
> Thanks
> 
> Jan Vecek

> Oct 26 03:15:43vecinoap rsyslogd: imuxsock: Acquired UNIX socket 
> '/run/systemd/journal/syslog' (fd 3) from systemd.  [v8.2008.0]
> Oct 26 03:15:43 vecinoap rsyslogd: [origin software="rsyslogd" 
> swVersion="8.2008.0" x-pid="577" x-info="https://www.rsyslog.com;] start
> Oct 26 03:15:43 vecinoap rsyslogd: action 'action-0-builtin:omfwd' suspended 
> (module 'builtin:omfwd'), retry 0. There should be messages before this one 
> giving the reason for suspension. [v8.2008.0 try 
> https://www.rsyslog.com/e/2007 ]
> Oct 26 03:15:43 vecinoap rsyslogd: action 'action-0-builtin:omfwd' resumed 
> (module 'builtin:omfwd') [v8.2008.0 try https://www.rsyslog.com/e/2359 ]
> Oct 26 03:15:43 vecinoap kernel: [0.00] Linux version 5.9.0-1-amd64 
> (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.0-15) 10.2.0, GNU ld 
> (GNU Binutils for Debian) 2.35.1) #1 SMP Debian 5.9.1-1 (2020-10-17)
> Oct 26 03:15:43 vecinoap kernel: [0.00] Command line: 
> BOOT_IMAGE=/boot/vmlinuz-5.9.0-1-amd64 
> root=UUID=f21aabf7-bd6d-4e92-b7f5-1a36a05c2db7 ro quiet
> Oct 26 03:15:43 vecinoap kernel: [0.00] x86/fpu: Supporting XSAVE 
> feature 0x001: 'x87 floating point registers'
> Oct 26 03:15:43 vecinoap kernel: [0.00] x86/fpu: Supporting XSAVE 
> feature 0x002: 'SSE registers'
> Oct 26 03:15:43 vecinoap kernel: [0.00] x86/fpu: Supporting XSAVE 
> feature 0x008: 'MPX bounds registers'
> Oct 26 03:15:43 vecinoap kernel: [0.00] x86/fpu: Supporting XSAVE 
> feature 0x010: 'MPX CSR'
> Oct 26 03:15:43 vecinoap kernel: [0.00] x86/fpu: xstate_offset[3]:  
> 576, xstate_sizes[3]:   64
> Oct 26 03:15:43 vecinoap kernel: [0.00] x86/fpu: xstate_offset[4]:  
> 640, xstate_sizes[4]:   64
> Oct 26 03:15:43 vecinoap kernel: [0.00] x86/fpu: Enabled xstate 
> features 0x1b, context size is 704 bytes, using 'compacted' format.
> Oct 26 03:15:43 vecinoap kernel: [0.00] BIOS-provided physical RAM 
> map:
> Oct 26 03:15:43 vecinoap kernel: [0.00] BIOS-e820: [mem 
> 0x-0x000997ff] usable
> Oct 26 03:15:43 vecinoap kernel: [0.00] BIOS-e820: [mem 
> 0x00099800-0x0009] reserved
> Oct 26 03:15:43 vecinoap kernel: [0.00] BIOS-e820: [mem 
> 0x000e-0x000f] reserved
> Oct 26 03:15:43 vecinoap kernel: [0.00] BIOS-e820: [mem 
> 0x0010-0x76fa2fff] usable
> Oct 26 03:15:43 vecinoap kernel: [0.00] BIOS-e820: [mem 
> 0x76fa3000-0x76fb2fff] reserved
> Oct 26 03:15:43 vecinoap kernel: [0.00] BIOS-e820: [mem 
> 0x76fb3000-0x7d2dcfff] usable
> Oct 26 03:15:43 vecinoap kernel: [0.00] BIOS-e820: [mem 
> 0x7d2dd000-0x7ddb9fff] reserved
> Oct 26 03:15:43 vecinoap kernel: [0.00] BIOS-e820: [mem 
> 0x7ddba000-0x7de95fff] usable
> Oct 26 03:15:43 vecinoap kernel: [0.00] BIOS-e820: [mem 
> 0x7de96000-0x7e1defff] ACPI NVS
> Oct 26 03:15:43 vecinoap kernel: [0.00] BIOS-e820: [mem 
> 0x7e1df000-0x7f23] reserved
> Oct 26 03:15:43 vecinoap kernel: [0.00] BIOS-e820: [mem 
> 0x7f24-0x7f7f] usable
> Oct 26 03:15:43 vecinoap kernel: [0.00] BIOS-e820: [mem 
> 0x7f80-0x7fff] reserved
> Oct 26 03:15:43 vecinoap kernel: [0.00] BIOS-e820: [mem 
> 0xe000-0xefff] reserved
> Oct 26 03:15:43 vecinoap kernel: [0.00] BIOS-e820: [mem 
> 0xfd00-0xfe7f] reserved
> Oct 26 03:15:43 vecinoap kernel: [0.00] BIOS-e820: [mem 
> 0xff00-0x] reserved
> Oct 26 03:15:43 vecinoap kernel: [0.00] BIOS-e820: [mem 
> 0x0001-0x00027fff] usable
> Oct 26 03:15:43 vecinoap kernel: [0.00] NX (Execute Disable) 
> protection: active
> Oct 26 03:15:43 vecinoap kernel: [0.00] SMBIOS 3.0.0 present.
> Oct 26 03:15:43 vecinoap kernel: [0.00] DMI: Supermicro Super 
> Server/A2SDi-4C-HLN4F, BIOS 1.2 11/05/2019
> Oct 26 03:15:43 vecinoap kernel: [0.00] tsc: Detected 2200.000 MHz 
> processor
> Oct 26 03:15:43 vecinoap kernel: [0.000575] last_pfn = 0x28 
> max_arch_pfn = 0x4
> Oct 26 03:15:43 vecinoap kernel: [0.000687] x86/PAT: Configuration [0-7]: 
> WB  WC  UC- UC  WB  WP  UC- WT  
> Oct 26 03:15:43 vecinoap kernel: [0.000763] last_pfn = 0x7f800 
> max_arch_pfn = 0x4
> Oct 26 03:15:43 vecinoap kernel: [0.005158] found SMP MP-table at [mem 
> 0x000fcdc0-0x000fcdcf]
> Oct 26 03:15:43 vecinoap kernel: [

Re: Bug#960605: Idle temperatures too high when using maxcpus kernel parameter

[Andrei POPESCU]

Control: reassign -1 src:linux 4.19.98-1

On Jo, 14 mai 20, 15:34:05, Vaddina Kameswar Rao wrote:
> Package: kernel
> Version: 4.19
> 
> Hello,
> 
> We have Dell PowerEdge R630 server, 2 sockets, air cooled. It has Intel
> Xeon E5-2630L v4 (Broadwell, 1.80GHz, 2 CPUs/node, 10 cores/CPU). I am
> noticing that the idle temperatures are too high when I use the 'maxcpus'
> kernel level parameter. The temperature in the server room is controlled
> and I notice that without 'maxcpus' parameter the sensors command usually
> reports an average of under 27 degree C. With 'maxcpus' the temperature
> starts with 35 degree C on boot and slowly climbs to 42 degree C after 20
> min of idling. This means that, there is very little headroom for the
> application to not trigger active cooling (happens at 60degree C). We
> reproduced the problem on other clusters with the same hardware, with
> debian testing, debian 10, debian 9 and ubuntu 18.04. With and without
> intel_pstate driver activated, the result is still the same.
> 
> According to my rudimentary understanding (I might be wrong), the issue
> boils down to "Offline cpu prevents sibling core to go to deep idle state
> when the system is idling". This increases the temperatures of the cores.
> 
> 1) The attached Screenshot1.png depicts the output of 'turbostat' command.
> We can see that the operating system is requesting C6 deep idle state (C6%
> column), but was only getting C1 state (CPU%c1 column) from the hardware
> all of the time.
> 
> 2) In the attached Screenshot2.png, I made the sibling CPU for Core0
> online. That means, I made Core20 online. See the attached image
> architecture.png to know which are the sibling cores. You can see that the
> Core0 immediately went to the C6 deep idle state (CPU%c6).
> 
> 3) In the attached Screenshot3.png, I made the sibling core for Core0
> offline again. That means, I made Core20 offline. This time, the Core0 did
> not go back to the C1 idle state. But, remained in the C6 deep idle state.
> 
> 4) In the attached Screenshot4.png, I made all the sibling cores online and
> then offline again. This time, all the cores now are in the C6 deep idle
> state (CPU%c6). We can also notice that the PkgWatt power consumption has
> dropped by half. The temperatures are slowly going back to under 27 degree
> C. I also ran some stress tests and saw, that after the stress tests the
> CPU's are going back to the deep idle states. Temperatures are also
> returning to under 27 degree C.
> 
> This leads me to conclude that it might be possible, that the kernel 4.19
> might have some regression with intel_idle driver. I am not sure though.
> What do you think?
> 
> Best regards,
> Kamesh

> root@server-9:~# uname -a
> Linux server-27.paris.fr 4.19.0-8-amd64 #1 SMP Debian 4.19.98-1 (2020-01-26) 
> x86_64 GNU/Linux
> 
> root@server-9:~# cpupower frequency-info
> analyzing CPU 0:
>   driver: intel_pstate
>   CPUs which run at the same hardware frequency: 0
>   CPUs which need to have their frequency coordinated by software: 0
>   maximum transition latency:  Cannot determine or is not supported.
>   hardware limits: 1.20 GHz - 2.90 GHz
>   available cpufreq governors: performance powersave
>   current policy: frequency should be within 1.20 GHz and 2.90 GHz.
>   The governor "powersave" may decide which speed to use
>   within this range.
>   current CPU frequency: Unable to call hardware
>   current CPU frequency: 1.20 GHz (asserted by call to kernel)
>   boost state support:
> Supported: yes
> Active: yes
> 
> 
> root@server-9:~# grep . /sys/devices/system/cpu/cpu*/cpufreq/* > grep.out
> /sys/devices/system/cpu/cpu0/cpufreq/affected_cpus:0
> /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq:290
> /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq:120
> /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_transition_latency:0
> /sys/devices/system/cpu/cpu0/cpufreq/related_cpus:0
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors:performance 
> powersave
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq:1200504
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver:intel_pstate
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor:powersave
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq:290
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq:120
> /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed:
> /sys/devices/system/cpu/cpu10/cpufreq/affected_cpus:10
> /sys/devices/system/cpu/cpu10/cpufreq/cpuinfo_max_freq:290
> /sys/devices/system/cpu/cpu10/cpufreq/cpuinfo_min_freq:120
> /sys/devices/system/cpu/cpu10/cpufreq/cpuinfo_transition_latency:0
> /sys/devices/system/cpu/cpu10/cpufreq/related_cpus:10
> /sys/devices/system/cpu/cpu10/cpufreq/scaling_available_governors:performance 
> powersave
> /sys/devices/system/cpu/cpu10/cpufreq/scaling_cur_freq:129
> /sys/devices/system/cpu/cpu10/cpufreq/scaling_driver:intel_pstate
> 

Re: Bug#422675: Possible fix by reverting a patch that entered mainline between 3.11 and 3.12

[Andrei POPESCU]

Control: reassign -1 src:linux

On Lu, 11 mai 20, 18:03:00, Jim Knopf wrote:
> ­In case anyone stumbles upon this thread looking for a solution,
> there has been success here reverting a particular kernel patch
> to sis900.c that occured between linux versions 3.11 and 3.12.
> 
> The machine tested has been a Gericom Webboy (laptop from
> year ~2000), it was connected to a tplink router.
> 
> Systems with kernel versions 2.6.21.7, 2.6.27.27, 3.8.2 and 3.11
> had acceptable network performance, while a regression was
> observed after booting 4.4.0 vanilla.  With this version the net-
> work adapter delivered a mere 100 kb/s, while in the megabyte
> range with aforementioned versions.
> 
> Backtracking the issue down to kernel 3.12.6 reliably exhibited
> the same degradation for each kernel tested - flooding dmesg
> log with the log patterns described earlier in this bug thread.
> 
> Visiting the kernel changelogs between versions 3.11 and 3.12.6
> the following candidate patch could be identified as a possible
> cause:
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/net/ethernet/sis/sis900.c?h=v3.12=78f1ccc4f82cd7bbb65b0e938ed0dfd81e902fe0
> 
> The patch title is
> sis900: don't restart auto-negotiation each time after link resume.
> 
> .. applied to linux mainline on
> 2013-08-20
> 
> Once this patch is reverted and 3.12.6 kernel recompiled, the
> sis900 network card's performance was restored.  This observation
> has then been confirmed and reproduced by reverse applying the
> patch to kernel 4.4.0.
> 
> This patch may or may not be the cause for other setups employing
> sis900 as a network chip, but has been reproducibly identified as
> cause for performance degradation for the issue above.
> 
> 
> The mii-tool workaround described earlier has worked as well, i.e.
> without patching the sis900.c driver, setting 10baseT-FD only for
> auto-negotiation events.  (100baseTx-HD showed no improvement).
> 10baseT-FD limits the network card's speed to about one mbyte/s,
> which is inferior to proper patching of sis900 kernel driver.
> 
> 
> Regards,
> Jim

-- 
Looking after bugs filled against unknown packages


signature.asc
Description: PGP signature

Re: Bug#956090: linux-image-5.5.0-1-amd65-unsigned: TUN/TAP not working with openvpn

[Andrei POPESCU]

Control: reassign -1 linux-image-5.5.0-1-amd64-unsigned 5.5.13-2

On Ma, 07 apr 20, 08:03:16, Arndt Heuvel wrote:
> Package: linux-image-5.5.0-1-amd65-unsigned
> Version: 5.5.13-2
> Severity: normal
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>* What led up to the situation?
> 
> installing linux-image-5.5.0-1-amd64-unsigned
> 
>* What was the outcome of this action?
> 
> openvpn conections break with this Error:
> ERROR: Cannot ioctl TUNSETIFF tun: Invalid argument (errno=22)
> 
> After instaling linux-image-5.4.0-4 openvpn works again.
> 
> 
> 
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE= 
> (charmap=UTF-8)
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled

-- 
Looking after bugs filled against unknown packages


signature.asc
Description: PGP signature

Bug#946510: Please enable CONFIG_DRM_SUN8I_MIXER for Allwinner A64 support

[Andrei POPESCU]

Package: src:linux
Version: 5.3.9-3
Severity: wishlist

Dear Maintainer,

Please enable CONFIG_DRM_SUN8I_MIXER in order to enable the lima driver 
on Allwinner A64 based devices (e.g. the PINE A64+).

This was tested by rebuilding the official kernel with this option. 

Support is still buggy (e.g. invisible mouse cursor), but hopping it 
will improve and be usable when bullseye is released.

Many thanks,
Andrei

-- Package-specific info:
** Version:
Linux version 5.3.0-2-arm64 (debian-kernel@lists.debian.org) (gcc version 9.2.1 
20191130 (Debian 9.2.1-21)) #1 SMP Debian 5.3.9-3 (2019-11-19)

** Command line:
root=LABEL=bullseye rootwait

** Tainted: E (8192)
 * Unsigned module has been loaded.

** Kernel log:
[   10.532360] systemd[1]: Starting Create list of static device nodes for the 
current kernel...
[   10.575310] systemd[1]: Condition check resulted in Set Up Additional Binary 
Formats being skipped.
[   10.596881] systemd[1]: Condition check resulted in File System Check on 
Root Device being skipped.
[   10.626384] systemd[1]: Starting Journal Service...
[   10.668499] systemd[1]: Starting Load Kernel Modules...
[   10.707843] systemd[1]: Starting Remount Root and Kernel File Systems...
[   10.748382] systemd[1]: Starting udev Coldplug all Devices...
[   10.760548] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[   10.807043] systemd[1]: Mounted Huge Pages File System.
[   10.839485] systemd[1]: Mounted POSIX Message Queue File System.
[   10.871570] systemd[1]: Mounted Kernel Debug File System.
[   10.910077] systemd[1]: Started Create list of static device nodes for the 
current kernel.
[   10.950212] systemd[1]: Started Load Kernel Modules.
[   10.981772] systemd[1]: Started Remount Root and Kernel File Systems.
[   11.018435] systemd[1]: Started Set the console keyboard layout.
[   11.056623] systemd[1]: Condition check resulted in FUSE Control File System 
being skipped.
[   11.077900] systemd[1]: Condition check resulted in Kernel Configuration 
File System being skipped.
[   11.103332] systemd[1]: Condition check resulted in Rebuild Hardware 
Database being skipped.
[   11.131100] systemd[1]: Starting Load/Save Random Seed...
[   11.168741] systemd[1]: Starting Apply Kernel Variables...
[   11.204179] systemd[1]: Starting Create System Users...
[   11.232141] systemd[1]: Started Apply Kernel Variables.
[   11.266366] systemd[1]: Started udev Coldplug all Devices.
[   11.302821] systemd[1]: Started Create System Users.
[   11.340862] systemd[1]: Starting Helper to synchronize boot up for 
ifupdown...
[   11.380523] systemd[1]: Starting Create Static Device Nodes in /dev...
[   11.413924] systemd[1]: Started Helper to synchronize boot up for ifupdown.
[   11.453874] systemd[1]: Started Create Static Device Nodes in /dev.
[   11.483441] systemd[1]: Reached target Local File Systems (Pre).
[   11.520142] systemd[1]: Starting udev Kernel Device Manager...
[   11.806045] systemd[1]: Started udev Kernel Device Manager.
[   11.852757] systemd[1]: Starting Show Plymouth Boot Screen...
[   11.893597] systemd[1]: Starting Network Service...
[   11.949726] systemd[1]: Received SIGRTMIN+20 from PID 260 (plymouthd).
[   12.042533] systemd[1]: Started Show Plymouth Boot Screen.
[   12.077646] systemd[1]: Started Journal Service.
[   12.226217] systemd-journald[231]: Received client request to flush runtime 
journal.
[   12.557295] sunxi-wdt 1c20ca0.watchdog: Watchdog enabled (timeout=16 sec, 
nowayout=0)
[   12.669951] axp20x-ac-power-supply axp20x-ac-power-supply: DMA mask not set
[   12.685646] axp20x-battery-power-supply axp20x-battery-power-supply: DMA 
mask not set
[   12.701296] sun4i-drm display-engine: bound 110.mixer (ops 
sun8i_mixer_platform_driver_exit [sun8i_mixer])
[   12.719700] lima 1c4.gpu: bus rate = 2
[   12.732543] lima 1c4.gpu: mod rate = 29700
[   12.759897] lima 1c4.gpu: gp - mali400 version major 1 minor 1
[   12.776438] sun4i-drm display-engine: bound 120.mixer (ops 
sun8i_mixer_platform_driver_exit [sun8i_mixer])
[   12.779901] lima 1c4.gpu: pp0 - mali400 version major 1 minor 1
[   12.815030] sun4i-drm display-engine: No panel or bridge found... RGB output 
disabled
[   12.831338] sun4i-drm display-engine: bound 1c0c000.lcd-controller (ops 
sun4i_tcon_platform_driver_exit [sun4i_tcon])
[   12.851591] axp20x-adc axp813-adc: DMA mask not set
[   12.855337] lima 1c4.gpu: pp1 - mali400 version major 1 minor 1
[   12.885878] lima 1c4.gpu: l2 cache 64K, 4-way, 64byte cache line, 64bit 
external bus
[   12.886703] sun4i-drm display-engine: bound 1c0d000.lcd-controller (ops 
sun4i_tcon_platform_driver_exit [sun4i_tcon])
[   12.910790] [drm] Initialized lima 1.0.0 20190217 for 1c4.gpu on minor 1
[   12.958697] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   12.959400] input: axp20x-pek as 
/devices/platform/soc/1f03400.rsb/sunxi-rsb-3a3/axp221-pek/input/input12
[   13.004815] sd 0:0:0:1: Attached scsi generic sg1 type 0
[   13.022394] 

Bug#928457: arm64: please apply workaround for A64 timer instability

[Andrei POPESCU]

Source: linux
Version: 4.19.28-2
Severity: wishlist
X-Debbugs-CC: debian-...@lists.debian.org

Hello,

The Allwinner A64 is affected by a bug that makes the clock jump, 
usually 95 years into the future.

The mainline kernel contains a workaround merged for 5.1:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=c950ca8c35eeb32224a63adc47e12f9e226da241

Please kindly apply this and the corresponding needed DT change for the 
buster kernel.

Thanks,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Bug#921019: arm64: Please provide sound modules for Allwinner A64 based systems

[Andrei POPESCU]

On Jo, 31 ian 19, 17:21:54, Harald Geyer wrote:
 
> Please enable the following Kconfig symbols as modules:
> 
> CONFIG_SND_SUN50I_CODEC_ANALOG
> CONFIG_SND_SUN8I_CODEC
> CONFIG_SND_SUN4I_I2S
> CONFIG_SND_SOC_SIMPLE_AMPLIFIER
> CONFIG_SND_SIMPLE_CARD
> 
> These are necessary for sound support on pinebook, Olimex TERES-I, etc.
> The drivers are available upstream since 4.20.
> Pinebook has sound enabled in devicetree starting with 5.0

Would this enable also the S/PDIF or is something else needed 
(CONFIG_SND_SUN4I_SPDIF maybe?)?

According to 
https://linux-sunxi.org/Linux_mainlining_effort#Status_Matrix
the S/PDIF is available already in 4.17, so it would be nice to activate 
it also for the stable kernel.

Thanks for considering,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

Re: Bug#807670: Can't build linux-tools-4.2 package

[Andrei POPESCU]

Control: reassign -1 src:linux-tools

On Vi, 11 dec 15, 17:07:29, Alexey wrote:
> Package: linux-perf
> Version: 4.2
> Source: linux-tools-4.2-2
> 
> 
> Hello!
> When I try to build source package I got error.
> 
> Command: dpkg-buildpackage -uc -us -nc -d -S -i -I
> --source-option=--unapply-patches
> Result:
> dpkg-buildpackage: source package linux-tools
> dpkg-buildpackage: source version 4.2-2
> dpkg-buildpackage: source distribution unstable
> dpkg-buildpackage: source changed by Ben Hutchings 
>  dpkg-source -i -I --unapply-patches --before-build linux-tools-4.2
> dpkg-source: info: using options from linux-tools-4.2/debian/source/options:
> --compression=xz
> dpkg-source: info: applying gitignore.patch
> dpkg-source: info: applying modpost-symbol-prefix.patch
> can't find file to patch at input line 15
> Perhaps you used the wrong -p or --strip option?
> The text leading up to this was:
> --
> |From: Chris Boot 
> |Date: Mon, 01 Jul 2013 23:10:02 +0100
> |Subject: modpost symbol prefix setting
> |Forwarded: not-needed
> |
> |[bwh: The original version of this was added by Bastian Blank.  The
> |upstream code includes  so that 
> |can tell whether C symbols have an underscore prefix.  Since we build
> |modpost separately from the kernel,  won't exist.
> |However, no Debian Linux architecture uses the symbol prefix, so we
> |can simply omit it.]
> |
> |--- a/scripts/mod/modpost.c
> |+++ b/scripts/mod/modpost.c
> --
> No file to patch.  Skipping patch.
> 1 out of 1 hunk ignored
> dpkg-source: info: the patch has fuzz which is not allowed, or is malformed
> dpkg-source: info: if patch 'modpost-symbol-prefix.patch' is correctly
> applied by quilt, use 'quilt refresh' to update it
> dpkg-source: error: LC_ALL=C patch -t -F 0 -N -p1 -u -V never -g0 -E -b -B
> .pc/modpost-symbol-prefix.patch/ --reject-file=- <
> linux-tools-4.2/debian/patches/modpost-symbol-prefix.patch gave error exit
> status 1
> dpkg-buildpackage: error: dpkg-source -i -I --unapply-patches --before-build
> linux-tools-4.2 gave error exit status 2
> 
> 
> 
> If I execute build command again without cleaning catalog source package
> will be build successfully.
> I make my build with git-buildpackage software. And I have separated debian
> and upstream branches, which specified in debian/gbp.conf.
> If I manually create .gitignore file like this doing patch gitignore.path
> that build will be successful too. I have many other packages which do not
> behave strangely.
> 
> Whats wrong with tis repo?

-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Re: Bug#776638: [linux-image] acerhdf does not turn off fan

[Andrei POPESCU]

Control: reassign -1 src:linux

On Vi, 30 ian 15, 12:32:48, Tar Qui wrote:
 Package: linux-image
 Version: 3.16.7-ckt4-2
 Severity: normal
 
 --- Please enter the report below this line. ---
 apologize for my terrible english.
 acerhdf built in the kernel does not stop the fan below the fanoff value.
 the problem and the solution (working for me) at this address
 http://ubuntuforums.org/archive/index.php/t-2203796.html
 
 in source file acerhdf.c (
 http://www.piie.net/files/acerhdf_kmod-0.5.30b-linux-3.8.tar.gz)
 - static unsigned int fanstate = ACERHDF_FAN_AUTO;
 + static unsigned int fanstate = ACERHDF_FAN_OFF;
 
 make
 
 i hope this fix will merged in the kernel.
 thanks.
 
 --- System information. ---
 Architecture: i386
 Kernel:   Linux 3.16.0-4-686-pae
 
 Debian Release: 8.0
   500 unstablemi.mirror.garr.it
 
 --- Package information. ---
 Package's Depends field is empty.
 
 Package's Recommends field is empty.
 
 Package's Suggests field is empty.

-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Re: Bug#763868: usb-modules-3.16-2-amd64-di: gspca_ov519 module fails to initiate webcam

[Andrei POPESCU]

Control: reassign -1 src:linux

On Vi, 03 oct 14, 12:15:32, Morten Bo Johansen wrote:
 Source: usb-modules-3.16-2-amd64-di
 Severity: important
 
 Dear Maintainer,
 
 My webcam does not work with this module. I am attaching the relevant lines 
 from
 dmesg with some debugging info enabled:
 
   Thanks,
   Morten
 
 PS: I hope I reported this in the right place.
 
   [ debugging info follows ]
 
 [ 5742.199055] usb 1-2.4: new full-speed USB device number 7 using xhci_hcd
 [ 5742.288767] usb 1-2.4: New USB device found, idVendor=05a9, idProduct=8519
 [ 5742.288771] usb 1-2.4: New USB device strings: Mfr=1, Product=2, 
 SerialNumber=0
 [ 5742.288773] usb 1-2.4: Product: USB Camera
 [ 5742.288775] usb 1-2.4: Manufacturer: OmniVision Technologies, Inc.
 [ 5742.289392] gspca_main: ov519-2.14.0 probing 05a9:8519
 [ 5742.289402] ov519 1-2.4:1.0: SET 01  005a 6d
 [ 5742.289568] ov519 1-2.4:1.0: SET 01  0053 9bov519 1-2.4:1.0: SET 01 
  0054 ff
 [ 5742.289763] ov519 1-2.4:1.0: SET 01  005d 03ov519 1-2.4:1.0: SET 01 
  0049 01
 [ 5742.289960] ov519 1-2.4:1.0: SET 01  0048 00ov519 1-2.4:1.0: SET 01 
  0072 ee
 [ 5742.290150] ov519 1-2.4:1.0: SET 01  0051 0fov519 1-2.4:1.0: SET 01 
  0051 00
 [ 5742.290337] ov519 1-2.4:1.0: SET 01  0022 00ov519 1-2.4:1.0: SET 01 
  0041 42
 [ 5742.290549] ov519 1-2.4:1.0: SET 01  0044 43ov519 1-2.4:1.0: 
 ov518_i2c_w 12 80
 [ 5742.290644] ov519 1-2.4:1.0: SET 01  0042 12ov519 1-2.4:1.0: SET 01 
  0045 80
 [ 5742.290832] ov519 1-2.4:1.0: SET 01  0047 01ov519 1-2.4:1.0: SET 01 
  0043 1c
 [ 5742.455030] ov519 1-2.4:1.0: SET 01  0047 03ov519 1-2.4:1.0: SET 01 
  0047 05
 [ 5742.455755] ov519 1-2.4:1.0: GET 01  0045 7fov519 1-2.4:1.0: 
 ov518_i2c_r 1c 7f
 [ 5742.455759] ov519 1-2.4:1.0: SET 01  0043 1dov519 1-2.4:1.0: SET 01 
  0047 03
 [ 5742.456159] ov519 1-2.4:1.0: SET 01  0047 05ov519 1-2.4:1.0: GET 01 
  0045 a2
 [ 5742.456509] ov519 1-2.4:1.0: ov518_i2c_r 1d a2ov519 1-2.4:1.0: I2C synced 
 in 0 attempt(s)
 [ 5742.456511] ov519 1-2.4:1.0: starting OV7xx0 configurationov519 1-2.4:1.0: 
 SET 01  0043 29
 [ 5742.456599] ov519 1-2.4:1.0: SET 01  0047 03ov519 1-2.4:1.0: SET 01 
  0047 05
 [ 5742.457031] ov519 1-2.4:1.0: GET 01  0045 a2ov519 1-2.4:1.0: 
 ov518_i2c_r 29 a2
 [ 5742.457033] ov519 1-2.4:1.0: Unknown image sensor version: 2
 [ 5742.457035] ov519 1-2.4:1.0: OV519 Config failed
 [ 5742.457042] ov519: probe of 1-2.4:1.0 failed with error -22
 [ 7054.719846] usb 1-2: USB disconnect, device number 5
 [ 7054.719855] usb 1-2.4: USB disconnect, device number 7
 [ 7638.249762] usb 1-2: new high-speed USB device number 8 using xhci_hcd
 [ 7638.378431] usb 1-2: New USB device found, idVendor=152d, idProduct=2329
 [ 7638.378434] usb 1-2: New USB device strings: Mfr=1, Product=2, 
 SerialNumber=5
 [ 7638.378436] usb 1-2: Product: USB to ATA/ATAPI bridge
 [ 7638.378438] usb 1-2: Manufacturer: JMicron
 [ 7638.378439] usb 1-2: SerialNumber: 801130168383
 [ 7638.430451] usb-storage 1-2:1.0: USB Mass Storage device detected
 [ 7638.430667] usb-storage 1-2:1.0: Quirks match for vid 152d pid 2329: 8020
 [ 7638.430704] scsi5 : usb-storage 1-2:1.0
 [ 7638.430817] usbcore: registered new interface driver usb-storage
 [ 7645.520200] scsi 5:0:0:0: Direct-Access ST1000DM 003-9YN162
 PQ: 0 ANSI: 2 CCS
 [ 7645.520513] sd 5:0:0:0: Attached scsi generic sg1 type 0
 [ 7645.520697] sd 5:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 
 TB/931 GiB)
 [ 7645.520975] sd 5:0:0:0: [sdb] Write Protect is off
 [ 7645.520978] sd 5:0:0:0: [sdb] Mode Sense: 28 00 00 00
 [ 7645.521236] sd 5:0:0:0: [sdb] No Caching mode page found
 [ 7645.521238] sd 5:0:0:0: [sdb] Assuming drive cache: write through
 [ 7645.579731]  sdb: sdb1 sdb2  sdb5 sdb6 sdb7 
 [ 7645.581330] sd 5:0:0:0: [sdb] Attached SCSI disk
 [ 7649.427653] EXT4-fs (sdb6): mounted filesystem with ordered data mode. 
 Opts: (null)
 [ 8231.207817] usb 1-2: USB disconnect, device number 8
 [ 8549.156486] usb 1-2: new full-speed USB device number 9 using xhci_hcd
 [ 8549.285472] usb 1-2: New USB device found, idVendor=05a9, idProduct=8519
 [ 8549.285480] usb 1-2: New USB device strings: Mfr=1, Product=2, 
 SerialNumber=0
 [ 8549.285485] usb 1-2: Product: USB Camera
 [ 8549.285489] usb 1-2: Manufacturer: OmniVision Technologies, Inc.
 [ 8549.286222] gspca_main: ov519-2.14.0 probing 05a9:8519
 [ 8549.286241] ov519 1-2:1.0: SET 01  005a 6d
 [ 8549.286313] ov519 1-2:1.0: SET 01  0053 9bov519 1-2:1.0: SET 01  
 0054 ff
 [ 8549.286441] ov519 1-2:1.0: SET 01  005d 03ov519 1-2:1.0: SET 01  
 0049 01
 [ 8549.286564] ov519 1-2:1.0: SET 01  0048 00ov519 1-2:1.0: SET 01  
 0072 ee
 [ 8549.286685] ov519 1-2:1.0: SET 01  0051 0fov519 1-2:1.0: SET 01  
 0051 00
 [ 8549.286805] ov519 1-2:1.0: SET 01  0022 00ov519 1-2:1.0: SET 01  
 0041 42
 [ 8549.286921] ov519 1-2:1.0: SET 01  0044 

Re: Bug#763606: linux-image-3.16-2-powerpc: Bridge configuration stopped working with kernel 3.16 (was working with previous kernel 3.14)

[Andrei POPESCU]

Control: reassign -1 src:linux

On Mi, 01 oct 14, 11:22:20, Rubin Simons wrote:
 Source: linux-image-3.16-2-powerpc
 Severity: important
 Tags: upstream
 
 Dear Maintainer,
 
 I'm running Debian sid on PowerPC (Mac Mini) with a Sun GEM ethernet adapter. 
 The system is running a bridge configuration (brctl and friends) as an 
 OpenVPN server.
 
 Last monday I upgraded to version 3.16 of the kernel (I was at 3.14). After a 
 reboot, everything seemed fine, no error messages, no strangeness.
 
 That same day I connected to the OpenVPN service on the box and noticed that 
 stuff didn't work as it did before the upgrade; specifically, I could only 
 reach the server itself and other connected clients (read: everything on the 
 tap0 part of the bridge) and nothing on the network (read: everything behing 
 the eth0 part of the bridge).
 
 Initially I thought it might be a setup bug. Last two days I've rechecked 
 everything, routing rules, firewalling stuff, etc; I verified the bridge 
 worked within the host, but nothing traversed to/from the eth0 part of the 
 bridge.
 
 Today, I downgraded the kernel to 3.2.60 (package from stable) as the 
 previous 3.14 kernel was not avalable anymore (and of course, I deinstalled 
 it..). After installation of the 3.2.60 kernel, my bridge setup works 
 normally again.
 
 I'm pretty sure this is a bug in either the kernel bridge (tun) or ethernet 
 (sungem) driver, or otherwise a bug in openvpn related to bridging on 3.16.
 
 -- System Information:
 Debian Release: jessie/sid
   APT prefers testing-updates
   APT policy: (500, 'testing-updates'), (500, 'testing')
 Architecture: powerpc (ppc)
 
 Kernel: Linux 3.2.0-4-powerpc
 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/dash

-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Re: Bug#762824: [linux-image] Backlight control through /sys/class/backlight/acpi_video0 no more working on Lenovo IdeaPad

[Andrei POPESCU]

Control: reassign -1 src:linux 3.16.3-2

On Jo, 25 sep 14, 15:08:35, onetmt wrote:
 Package: linux-image
 Version: 3.16-2-amd64
 Severity: important
 
 --- Please enter the report below this line. ---
 With 3.16 debian kernels, backlight controller is always at its max
 value (255); entry in /sys/class/backlight/acpi_video0, formerly used to
 control backlighting, isn't created anymore (only switchable graphic
 card controller /sys/class/backlight/radeon_bl is created).
 
 --- System information. ---
 Architecture: amd64
 Kernel:   Linux 3.16-2-amd64
 
 Debian Release: jessie/sid
   500 unstableftp.it.debian.org
   500 stable  dl.google.com
 
 --- Package information. ---
 Package's Depends field is empty.
 
 Package's Recommends field is empty.
 
 Package's Suggests field is empty.
 
 -- 
 Hofstadter's Law:
 It always takes longer than you expect, even when you take into account
 Hofstadter's Law.

-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Re: Bug#759291: linux-image-armmp: Please enable support for exynos devices

[Andrei POPESCU]

Control: reassign -1 linux-image-armmp 3.14.15-2

On Lu, 25 aug 14, 14:21:03, Neil Williams wrote:
 Source: linux-image-armmp
 Version: 3.14.15-2
 Severity: wishlist
 
 Please add support for exynos devices (like arndale) - config ARCH_EXYNOS.
 
 
 -- System Information:
 Debian Release: jessie/sid
   APT prefers unstable
   APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
 Architecture: amd64 (x86_64)
 Foreign Architectures: i386
 armhf
 
 Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores)
 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: 
 LC_ALL set to en_GB.UTF-8)
 Shell: /bin/sh linked to /bin/dash

-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Re: Bug#759317: linux-image-3.14-2-686-pae: Cannot upgrade kernel due to via-velocity.ko error

[Andrei POPESCU]

Control: reassign -1 src:linux

On Ma, 26 aug 14, 10:58:01, Demetris Demetriou wrote:
 Source: linux-image-3.14-2-686-pae
 Version: via-velocity.ko unexpected end of file or stream
 Severity: important
 
 Hello,
 The problem does not affect the system listed by Reportbug, but the system
 listed below:
 
 System: Asus EEE PC 701SD
 Debian Jessie (testing) 32Bit
 
 When running sudo apt-get update  sudo apt-get upgrade the following comes 
 up
 and the upgrade stops:
 
 ---
 Preparing to unpack .../linux-image-3.14-2-686-pae_3.14.15-2_i386.deb ...
 Unpacking linux-image-3.14-2-686-pae (3.14.15-2) over (3.14.13-2) ...
 dpkg: error processing archive /var/cache/apt/archives/linux-
 image-3.14-2-686-pae_3.14.15-2_i386.deb (--unpack):
  cannot copy extracted data for
 './lib/modules/3.14-2-686-pae/kernel/drivers/net/ethernet/via/via-velocity.ko'
 to 
 '/lib/modules/3.14-2-686-pae/kernel/drivers/net/ethernet/via/via-velocity.ko
 ..dpkg-new': unexpected end of file or stream
 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
 E: Sub-process /usr/bin/dpkg returned an error code (1)
 
 
 Thank you,
 Demetris Demetriou
 deZillium LTD
 
 
 
 -- System Information:
 Debian Release: jessie/sid
   APT prefers testing-updates
   APT policy: (500, 'testing-updates'), (500, 'testing')
 Architecture: amd64 (x86_64)
 Foreign Architectures: i386
 
 Kernel: Linux 3.14-2-amd64 (SMP w/2 CPU cores)
 Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/dash

-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Re: Bug#753656: linux-image-3.14-1-rt-amd64: Kernel panic caused by ohci_hcd

[Andrei POPESCU]

Control: reassign -1 src:linux

On Jo, 03 iul 14, 18:35:01, The GZeus wrote:
 Source: linux-image-3.14-1-rt-amd64
 Severity: important
 
 Dear Maintainer,
 
 
 Twice I have had a kernel panic with nearly identical messages while playing 
 a game (Dust: An Elysian Tail, obtained via native Linux Steam, which I 
 installed from non-free) with an official MS XBox 360 wired controller with 
 the standard xpad driver.
 
 I took a photo of the most recent one, and I'm willing to type out whatever 
 lines contain the necessary information.
 Would you like the output of lspci/lsusb?
 
 Odd that I've never had this happen in any other situation, but that's what 
 happened.
 
 My system uses an AMD A10 APU.
 
 *** Reporter, please consider answering these questions, where appropriate ***
 
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
  ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
 
 *** End of the template - remove these template lines ***
 
 
 -- System Information:
 Debian Release: jessie/sid
   APT prefers testing
   APT policy: (900, 'testing')
 Architecture: amd64 (x86_64)
 Foreign Architectures: i386
 
 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
 Locale: LANG=en_GB.UTF-8, LC_CTYPE=ja_JP.utf8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/dash

-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Re: Bug#750661: uninstallable

[Andrei POPESCU]

On Sb, 28 iun 14, 09:08:48, Vincent Bernat wrote:
  ❦  8 juin 2014 11:06 +0300, Andrei POPESCU andreimpope...@gmail.com :
 
  Version: 3.15~rc7-1~exp1
  Severity: grave
  
  seems to depend on absent linux-kbuild-3.15 
 
  As far as I understand, at this point you are expected to build your own 
  linux-kbuild package. Closing this bug, but CC -kernel in case they want 
  to comment.
 
 Why would a user be expected to build its own packages to satisfy a
 dependency? Why not provide the appropriate package in experimental?

This is a question for the Kernel Team actually (CCd).

Kind regards,
Andrei (looking after bugs filed against unknown packages)
-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Re: Bug#751911: is Marvell USB wireless LAN adapter: id 1286:1fab supported?

[Andrei POPESCU]

Control: reassign -1 firmware-libertas
Control: severity -1 wishlist

On Ma, 17 iun 14, 18:49:42, Adrian Venditti wrote:
 Package:  libertas-firmwareVersion:  9.70.7.p0.0-1
 
 
 
 hi,
 To write this email I'm using Suse linux 11.4 with the ndiswrapper package 
 for a windows driver for my wireless adapter. The rest of this email refers 
 to the latest version of Debian linux.
 I've downloaded and installed the latest version of Debian linux - on a 
 separate partition with dual-boot - and am trying to get a Debian driver for 
 my wireless LAN adapter to work. It's based on the Marvell chipset 88w8338. 
 Here's the output from lsusb:
 
 Bus 001 Device 004: ID 1286:1fab Marvell Semiconductor, Inc. 88W8338 
 [Libertas] 802.11g
 output from dmesg:
 adrian@home:~ cat debian-dmesg.txt | grep usb 1-7 [   17.653166] usb 1-7: 
 new high-speed USB device number 4 using ehci_hcd[   17.855860] usb 1-7: New 
 USB device found, idVendor=1286, idProduct=1fab[   17.871647] usb 1-7: New 
 USB device strings: Mfr=1, Product=2, SerialNumber=0[   17.887432] usb 1-7: 
 Product: MARVELL Wireless Device V1.0.1.2[   17.903208] usb 1-7: 
 Manufacturer: MARVELL 
 What's missing from the package contents 
 page:https://packages.debian.org/squeeze-backports/firmware-libertas
 is a reference to 8338 as a driver code.
 Can this be fixed please?
 thanks,
 Adrian  

-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Re: Bug#751461: usb ports inaccessible after boot up

[Andrei POPESCU]

Control: reassign -1 src:linux 3.2.0-4-686-pae

On Vi, 13 iun 14, 10:03:42, A.Verheul wrote:
 Package:   vmlinuz
 Version:   3.2.0-4-686-pae
 
 Debian Version:Debian wheezy 7.4.0, i386
  
 Bug summary:   USB ports inaccessible after boot up
  
 Related bugreport: #500552 - involves exactly the same problem (year 2008) - 
then solved through CPU replacement - issue archived by now
 
 Possibly related : #750445 - describes similar problem with different error 
 code 
  
 Reporter:  Arie Verheul
 Personal status:   new to Linux
  
 --
 Summary of what has been found so far
 --
  
 a. The system may work properly and hence the hardware seems OK.
  
 b. The issue seems not specific for Debian but rather a general kernel issue.
  
 c. Puppy Linux seems less sensitive for the issue.
  
 d. The Intel BIOS version affects the issue.
  
 e. There are indications that the problem might involve a timing issue.
  
 --
  
 Dear sir or madam,
  
 I do experience a persistent problem with usb port setup on boot up.
 The system boots up OK but ends up with non-functioning usb-ports.
 This renders the system useless. The hardware used is new and recent (see 
 specs below). 
   
 Initially it was attempted to install Scientific Linux, which uses the 
 Anaconda installer. 
 However, Anaconda boots up OK but with non-functioning usb-ports. No solution 
 was found.
 Installation was done from an usb stick (no optical drive present).
 Therefore the issue seems to be a kernel issue which is not specific for 
 Debian.
  
 Next it was attempted to install Debian. Just like Anaconda the Debian 
 installer boots up 
 with inaccessible usb ports. This could be solved by repeatedly hotplugging 
 the usb mouse. 
 After the usb ports had become accessible Debian could be installed properly.
  
 However, once installed Debian normally always boots up with non functioning 
 usb-ports.
 Error message as below:
  
 [   20.405006] usb 1-1: device not accepting address 2, error -110
 [   20.516591] usb 1-1: new high-speed USB device number 3 using ehci_hcd
 [   36.040241] usb 1-1: device not accepting address 3, error -110
 [   36.152034] usb 1-1: new high-speed USB device number 4 using ehci_hcd
 [   46.562305] usb 1-1: device not accepting address 4, error -110
 [   46.674088] usb 1-1: new high-speed USB device number 5 using ehci_hcd
 [   57.084282] usb 1-1: device not accepting address 5, error -110
 [   57.084425] hub 1-0:1.0: unable to enumerate USB device on port 1
  
 Instead of usb 1-1 the system may complain about usb 3-1 with exactly the 
 same result.
  
 To inspect the hard disk Puppy Linux 5.7.1 was installed on a usb stick.
 Surprisingly Puppy always booted properly, and did not seem to suffer from 
 the usb issue.
 However, when the system BIOS was updated in an attempt to solve the issue 
 (see below for version), Puppy randomly failed in about half of the cases.
 Returning to the previous BIOS version solved this. This was reported to 
 Intel.
  
 From experiments it was found that Debian could be made to work with properly 
 functioning
 usb-ports by simply deleting some log files from the /var/log directory 
 (using Puppy).
 Deleted were kernel.log and the various dmesg files. Although the effect of 
 this remains
 unclear it gives gives a 70% chance for a working system. Strange enough the 
 reported errors 
 remain exactly the same, even if the system ends up in a properly working 
 state.
 The system has been used this way for over 2 month now with consistently the 
 same results. 
  
 The impression is that the solution found for bug #500552 was rather a 
 workaround than a solution.
 The random behaviour of both Debian and Puppy (the latter with updated BIOS) 
 could indicate
 a timing issue. In this respect it might be relevant that the system uses an 
 SSD which is faster 
 than most HDD's. The effect of deleting log files could be just a slight 
 delay in OS loading. 
  
 I therefore took notes of the time of the first reported usb error, both in 
 cases that ended up
 with functioning usb ports as in cases with non functioning usb ports.
  
 --
 Boot up ending with non-functioning usb-ports
  
 20.178
 20.178
 20.178
 20.184
 20.200
 20.405
  
 Boot up ending with properly functioning usb-ports
  
 20.465
 20.477
 20.508
 20.544
 --
  
 These data support the timing issue hypothesis. 
 A first error at 20.405 or earlier would result in non-functioning usb-ports, 
 a first error at 20.465 or later would result in 

Re: Bug#750959: linux-image-3.15-rc8-amd64: Add support for VGA VFIO (CONFIG_VFIO_PCI_VGA)

[Andrei POPESCU]

Control: reassign -1 src:linux

On Lu, 09 iun 14, 02:55:32, fld wrote:
 Source: linux-image-3.15-rc8-amd64
 Severity: wishlist
 
 Dear Maintainer,
 
 In the past few years with the increased availability of IOMMU/Vt-d supporting
 hardware, there has been an increase in the popularity of experimenting with
 VGA passtrough to virtual machines via IOMMU. Currently the most bleeding edge
 way of doing this is with the combination of kvm, qemu and vfio. However,
 most graphics cards don't play nice with just the plain vfio and need special
 considerations that need to be enabled in the kernel.
 
 I propose that we enable these special features called CONFIG_VFIO_PCI_VGA
 in the kernel so that people can more easily experiment with these new cool
 features. I asked the leading developer of VFIO VGA support (Alex Williamson)
 if he could think of any reason why not to enable this feature by default, and
 he could not think of any. The option should simply add the capability to use
 the x-vga feature in Qemu.
 
 Here some basic information about VFIO:
 https://www.kernel.org/doc/Documentation/vfio.txt
 
 Interesting presentations about VGA Passtroughs with VFIO:
 http://www.linux-kvm.org/wiki/images/b/b4/2012-forum-VFIO.pdf
 http://www.linux-kvm.org/wiki/images/e/ed/Kvm-forum-2013-VFIO-VGA.pdf
 
 There is also quite a bit of mainstream interest about this stuff:
 https://bbs.archlinux.org/viewtopic.php?id=162768
 
 Thank you.
 
 -- System Information:
 Debian Release: jessie/sid
   APT prefers unstable
   APT policy: (500, 'unstable'), (1, 'experimental')
 Architecture: amd64 (x86_64)
 
 Kernel: Linux 3.15.0-rc7 (SMP w/8 CPU cores)
 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/dash

-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Re: Bug#750661: uninstallable

[Andrei POPESCU]

On Jo, 05 iun 14, 09:31:06, Yaroslav Halchenko wrote:
 Source: linux-headers-3.15-rc7-amd64

Such (source) package does not exist, see #690169.

 Version: 3.15~rc7-1~exp1
 Severity: grave
 
 seems to depend on absent linux-kbuild-3.15 

As far as I understand, at this point you are expected to build your own 
linux-kbuild package. Closing this bug, but CC -kernel in case they want 
to comment.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Re: Bug#746800: linux-image-3.13-1-armmp: Please enable CONFIG_TI_EDMA for Beaglebone support

[Andrei POPESCU]

Control: reassign -1 src:linux

On Sb, 03 mai 14, 14:18:38, James Valleroy wrote:
 Source: linux-image-3.13-1-armmp
 Severity: wishlist
 
 Dear Maintainer,
 
 Please set CONFIG_TI_EDMA=y which is required to boot on the Beaglebone.

-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Re: Bug#745331: linux-image-3.14-trunk-amd64: Please enable CONFIG_X86_INTEL_LPS

[Andrei POPESCU]

Control: reassign -1 src:linux

On Du, 20 apr 14, 16:57:38, Guido Günther wrote:
 Source: linux-image-3.14-trunk-amd64
 Severity: wishlist
 
 Please enable the above config setting. It's necessary to power up some
 of the i2c devices on the vaio duo 13 as Thomas (cc:) found out.
 Cheers,
  -- Guido
 
 -- System Information:
 Debian Release: jessie/sid
   APT prefers testing
   APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'), 
 (1, 'experimental')
 Architecture: amd64 (x86_64)
 
 Kernel: Linux 3.14.0-rc1+ (SMP w/4 CPU cores)
 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
  Shell: /bin/sh linked to /bin/dash

-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Re: Bug#743214: nouveau driver completely breaks nVidia 6150 system

[Andrei POPESCU]

Control: reassign -1 src:linux 3.2.51-1

On Lu, 31 mar 14, 10:39:03, Adam Majer wrote:
 Source: linux-image-3.2.0-4-amd64
 Version: 3.2.51-1
 Severity: normal
 
 The severity of this should be grave/critical, as it makes the system
 unbootable. I've left it as normal as it seems to affect only specific
 hardware configuration.
 
 Nouveau driver should be blacklisted for this chipset,
 
 https://bugzilla.kernel.org/show_bug.cgi?id=68701
 
 There are other reports for crashing in X
https://bugzilla.kernel.org/show_bug.cgi?id=50091
 
 
 00:05.0 VGA compatible controller [0300]: NVIDIA Corporation C51PV
 [GeForce 6150] [10de:0240] (rev a2)
 
 
 00:05.0 VGA compatible controller [0300]: NVIDIA Corporation C51PV
 [GeForce 6150] [10de:0240] (rev a2) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. A8N-VM CSM [1043:81cd]
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
 Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- 
 TAbort- MAbort- SERR- PERR- INTx-
 Latency: 0
 Interrupt: pin A routed to IRQ 5
 Region 0: Memory at fc00 (32-bit, non-prefetchable) [size=16M]
 Region 1: Memory at d000 (64-bit, prefetchable) [size=256M]
 Region 3: Memory at fb00 (64-bit, non-prefetchable) [size=16M]
 [virtual] Expansion ROM at cef0 [disabled] [size=128K]
 Capabilities: [48] Power Management version 2
 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
 PME(D0-,D1-,D2-,D3hot-,D3cold-)
 Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
 Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
 Address:   Data: 
 
 
 -- System Information:
 Debian Release: jessie/sid
   APT prefers unstable
   APT policy: (500, 'unstable'), (50, 'experimental')
 Architecture: amd64 (x86_64)
 Foreign Architectures: i386
 
 Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores)
 Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/dash

-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Re: Bug#742499: rts5139.ko: need to unload and reload rts5139 module to have the sdcard reader to work

[Andrei POPESCU]

Control: reassign -1 src:linux

On Lu, 24 mar 14, 15:09:17, tchetche wrote:
 Package: rts5139.ko
 Severity: normal
 
 Dear Maintainer,
 
 *** Reporter, please consider answering these questions, where appropriate ***
 
* What led up to the situation?
 When inserting a sd card in the reader, nothing happens (nothing in dmesg)
* What exactly did you do (or not do) that was effective (or
  ineffective)?
 booting with an sdcard inserted make it visible to the system, but then
 changing sdcard is not visible unless I type rmmod rts5139  modprobe
 RTS5139.
* What was the outcome of this action?
* What outcome did you expect instead?
 
 *** End of the template - remove these template lines ***
 
 
 
 -- System Information:
 Debian Release: jessie/sid
   APT prefers testing-updates
   APT policy: (500, 'testing-updates'), (500, 'testing')
 Architecture: amd64 (x86_64)
 Foreign Architectures: i386
 
 Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores)
 Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/dash

-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Re: Bug#741663: linux-image-3.13-1-powerpc-smp: therm_windtunnel does not load correctly

[Andrei POPESCU]

Control: reassign -1 src:linux

On Sb, 15 mar 14, 20:25:23, Bryan Christianson wrote:
 Source: linux-image-3.13-1-powerpc-smp
 Severity: normal
 
 Dear Maintainer,
 
 
* What led up to the situation?
 After upgrade from linux-image-3.12-1-powerpc-smp I noticed the fan in my 
 G4 PowerPC was making different noises than it had previously. I rmmod'ed the 
 therm_windtunnel module and reloaded with modprobe. There were the usual 
 i2c i2c-7: therm_windtunnel: attach_adapter method is deprecated message 
 but 
 no initialisation messages from the driver. Also, there are no temperature 
 and 
 fan speed statistics being shown in the kernel log.
 
* What exactly did you do (or not do) that was effective (or
  ineffective)?
 
 I rebooted on linux-image-3.12-1-powerpc-smp
 
* What was the outcome of this action?
 Fan and Temperature behaving normally
* What outcome did you expect instead?
 
 
 
 -- System Information:
 Debian Release: jessie/sid
   APT prefers testing
   APT policy: (900, 'testing')
 Architecture: i386 (i686)
 
 Kernel: Linux 3.12-1-powerpc-smp 
 Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/bash

-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Re: Bug#741372: linux-image-3.13-1-686-pae: Unable properly to capture video from devices

[Andrei POPESCU]

Control: reassign -1 src:linux 3.15.5-1

On Ma, 11 mar 14, 16:45:29, Marco wrote:
 Source: linux-image-3.13-1-686-pae
 Version: 3.15.5-1
 Severity: normal
 
 Dear Maintainer,
 
 After upgrading from kernel 3.2 to 3.10 or 3.13, I wasn't able properly to 
 capture video with my webcam nor my capture card. It happens that video is 
 captured as if it's been fast-forwarded, while the audio captures at normal 
 speed.
 
 I'm using Mencoder to capture the video. What's interesting is that when 
 using Mplayer to reproduce the video directly from the device (webcam or 
 capture card), it does it at normal speed. So, I can't capture video using 
 kernel 3.10 or 3.13, but if I boot kernel 3.2, I can capture with no 
 inconvenience.
 
 I don't know if the bug is in the kernel itself, or in v4l, or in mencoder. 
 But I think that this is more kernel-related.
 
 Thank you.
 
 -- System Information:
 Debian Release: jessie/sid
   APT prefers unstable
   APT policy: (500, 'unstable')
 Architecture: i386 (i686)
 
 Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores)
 Locale: LANG=es_AR.utf8, LC_CTYPE=es_AR.utf8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/dash

-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Re: Bug#740041: xen-netfront: reduce gso_max_size to account for max TCP header

[Andrei POPESCU]

Control: reassign -1 src:linux 3.2.41-2+deb7u2
Control: fixed -1 3.2.51-1

On Ma, 25 feb 14, 16:25:48, Kris Shannon wrote:
 Source: linux-2.6
 Version: 2.6.32-48
 Control: found -1 linux/3.2.41-2+deb7u2
 Control: fixed -1 linux/3.2.51-1
 
 Separate bug for domU (xen-netfront) side of Bug #701744 as requested in
 https://lists.debian.org/debian-kernel/2014/02/msg00297.html 
 1393274681.6823.101.ca...@deadeye.wl.decadent.org.uk
 
 Summary:
 
 The security fix for XSA-39 revealed a GSO size calculation bug.
 
 Patches for both xen-netback and xen-netfront were created and fixed upstream.
 
 Either patch was enough to fix the regression and a work-around (turning off 
 GSO) was found.
 
 Bug #701744 was closed with the backporting of the xen-netback patch to both 
 the Squeeze and Wheezy kernels.
 
 The xen-netfront patch was backported to the 3.2.47 kernel and included in 
 the Debian Wheezy kernel 3.2.51-1

-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Re: Bug#739972: missing kernel config options for support of mirabox

[Andrei POPESCU]

Control: reassign -1 src:linux 3.13-1~exp1

On Lu, 24 feb 14, 14:22:03, Jasmin Schnatterbeck wrote:
 Source: linux-image-3.13-trunk-armmp
 Version: 3.13-1~exp1
 Severity: important
 
 the mentioned multiplatform kernel ist intended to run on armada 370
 SOCs. A system using this SOC is the Mirabox.
 
 I noticed, that the following modules are missing in the armmp kernel to
 support the device properly:
 
 xhci controller:
 CONFIG_USB_XHCI_HCD=m
 
 mwifiex wifi:
 CONFIG_MWIFIEX=m
 CONFIG_MWIFIEX_SDIO=m
 
 Futhermore hctosys-on-boot does not work. As the /etc/init.d/hwlock.sh
 script does not run in rcS, because udev is already active, the system
 time relies on the kernel, that needs to set it from rtc on boot time.
 In order to make this work, the rtc driver must be compiled-in (as far
 as I investigated the situation):
 
 RTC_DRV_MV=y
 
 Furthermore the PCI-Controller of the device needs the following kernel
 option to make it work:
 
 CONFIG_PCI_MVEBU=y
 
 The mentioned modifications are tested locally and work.
 
 If the options for RTC and PCI (non-module) conflict with other options
 (related to another device), a separated flavour would still be
 necessary.
 
 Cheers
 Jasmin



-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Re: Bug#661861: PC Engines Alix 3C2: Boot hang waiting for /dev to be fully populated

[Andrei POPESCU]

Control: reassign -1 src:linux

On Du, 16 feb 14, 20:38:14, Daniel Bayer wrote:
 Hi!
 
 I just had the same problem on Alix 2d3 with BIOS v0.99 while
 updating to wheezy. It turned out that the system hangs when 
 loading the cs5535-mfgpt module:
 
 | Waiting for /dev to be fully populated...
 | [8.547274] cfg80211: Calling CRDA to update world regulatory domain
 | [8.554139] input: PC Speaker as /devices/platform/pcspkr/input/input0
 | [9.071321] geode-aes: GEODE AES engine enabled.
 | [9.073504] ath5k :00:0c.0: registered as 'phy0'
 | [9.802039] Error: Driver 'pcspkr' is already registered, aborting...
 | [9.885425] cs5535-mfgpt cs5535-mfgpt: reserved resource region [io 
 0x6200-0x623f]
 
 The module should output a second line reporting the number of free
 timers. This did not happen. So I assume the system crashed somewhere
 in the scan_times() function of cs5535-mfgpt. I played a little bit
 with the mfgptfix boot command line option, but the system always
 crashed. But simply removing the cs5535-mfgpt fixed the problem.
 
 In the end I found the MFGPT workaround option in the BIOS, which was 
 enabled:
 
 | BIOS setup:
 | 
 | (9) 9600 baud (2) 19200 baud *3* 38400 baud (5) 57600 baud (1) 115200 baud
 | (C) CHS mode *L* LBA mode *W* HDD wait *V* HDD slave *U* UDMA enable
 | *M* MFGPT workaround
 | (P) late PCI init
 | *R* Serial console enable
 | (E) PXE boot enable
 | (X) Xmodem upload
 | (Q) Quit
 
 After disabling it the system booted fine with cs5535-mfgpt enabled and
 mfgptfix not set. Now everything works as expected.
 
 
 Daniel

-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Re: Bug#737245: Wheezy kernel fails to browse NFS export with 64 bits inode

[Andrei POPESCU]

Control: reassign src:linux

On Vi, 31 ian 14, 19:58:18, Emmanuel Florac wrote:
 Package: linux-image
 
 
 Mounting an NFS export from a large XFS filesystem, either using
 NFS3 or NFS4, on a freshly installed wheezy :
 
 # uname -a
 Linux violon 3.2.0-4-amd64 #1 SMP Debian 3.2.51-1 x86_64 GNU/Linux
 # mount 10.1.2.3:/mnt/export /mnt/nfs
 # ls /mnt/nfs
 Stale NFS handle.
 # umount /mnt/nfs
 # mount -o vers=3 10.1.2.3:/mnt/export /mnt/nfs
 # ls /mnt/nfs
 Stale NFS handle.
 
 This is if the inode number on the /mnt/export XFS fs on the server is
 64 bits. If the inode is smaller and fits in 32 bits, it works perfectly
 fine. This is a very annoying bug.
 
 There are no errors in dmesg or /var/log/messages.
 
 Running on the file server Wheezy with a custom kernel (plain vanilla
 source from kernel.org).
 
 
 -- 
 
 Emmanuel Florac |   Direction technique
 |   Intellique
 | eflo...@intellique.com
 |   +33 1 78 94 84 02
 

-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Re: Bug#735839: /init: exec: line 331: switch_root: not found

[Andrei POPESCU]

Control: reassign -1 src:linux

On Vi, 17 ian 14, 21:39:09, Bertrand GRONDIN wrote:
 
 Package: linux-image-3.12.0.131108-gdn
 Version: 3.12
 Severity: critical
 Tags: d-i
 Justification: breaks the whole system
 
 After installing new linux kernel, I have the following message :
 
 I have to load preinstalled kernel. If you reinstall it, by example, you
 have
 this message.
 
 /init: exec: line 331: switch_root: not found
 kernel panic - not syncing: attempted to kill init!
 exit code: 0x0200
 
 
 
 -- System Information:
 Debian Release: jessie/sid
 APT prefers testing-proposed-updates
 APT policy: (500, 'testing-proposed-updates'), (500, 'oldstable-updates'),
 (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental')
 Architecture: amd64 (x86_64)
 
 Kernel: Linux 3.12.0.131108-gdn (SMP w/4 CPU cores)
 Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/dash
 
 Versions of packages linux-image-3.12.0.131108-gdn depends on:
 ii coreutils 8.21-1
 ii debconf [debconf-2.0] 1.5.52
 
 linux-image-3.12.0.131108-gdn recommends no packages.
 
 Versions of packages linux-image-3.12.0.131108-gdn suggests:
 pn fdutils none
 pn ksymoops none
 pn linux-doc-3.12.0.131108-gdn | linux-source-3.12.0.131108-gdn none
 pn linux-image-3.12.0.131108-gdn-dbg none
 
 --===5649671868940448812==
 MIME-Version: 1.0
 Content-Transfer-Encoding: 8bit
 Content-Type: text/plain; charset=utf-8
 Content-Disposition: attachment; filename=grub.cfg
 
 #
 # DO NOT EDIT THIS FILE
 #
 # It is automatically generated by grub-mkconfig using templates
 # from /etc/grub.d and settings from /etc/default/grub
 #
 
 ### BEGIN /etc/grub.d/00_header ###
 if [ -s $prefix/grubenv ]; then
 set have_grubenv=true
 load_env
 fi
 set default=0
 
 if [ x${feature_menuentry_id} = xy ]; then
 menuentry_id_option=--id
 else
 menuentry_id_option=
 fi
 
 export menuentry_id_option
 
 if [ ${prev_saved_entry} ]; then
 set saved_entry=${prev_saved_entry}
 save_env saved_entry
 set prev_saved_entry=
 save_env prev_saved_entry
 set boot_once=true
 fi
 
 function savedefault {
 if [ -z ${boot_once} ]; then
 saved_entry=${chosen}
 save_env saved_entry
 fi
 }
 function load_video {
 if [ x$feature_all_video_module = xy ]; then
 insmod all_video
 else
 insmod efi_gop
 insmod efi_uga
 insmod ieee1275_fb
 insmod vbe
 insmod vga
 insmod video_bochs
 insmod video_cirrus
 fi
 }
 
 if [ x$feature_default_font_path = xy ] ; then
 font=unicode
 else
 insmod part_msdos
 insmod ext2
 set root='hd0,msdos8'
 if [ x$feature_platform_search_hint = xy ]; then
 search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos8
 --hint-efi=hd0,msdos8 --hint-baremetal=ahci0,msdos8 --hint='hd0,msdos8'
 740e0848-bcc5-411a-b0ea-64ef31a954d0
 else
 search --no-floppy --fs-uuid --set=root 740e0848-bcc5-411a-b0ea-64ef31a954d0
 fi
 font=/share/grub/unicode.pf2
 fi
 
 if loadfont $font ; then
 set gfxmode=auto
 load_video
 insmod gfxterm
 set locale_dir=$prefix/locale
 set lang=fr_FR
 insmod gettext
 fi
 terminal_output gfxterm
 if [ ${recordfail} = 1 ] ; then
 set timeout=-1
 else
 set timeout=5
 fi
 ### END /etc/grub.d/00_header ###
 
 ### BEGIN /etc/grub.d/05_debian_theme ###
 insmod part_msdos
 insmod ext2
 set root='hd0,msdos8'
 if [ x$feature_platform_search_hint = xy ]; then
 search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos8
 --hint-efi=hd0,msdos8 --hint-baremetal=ahci0,msdos8 --hint='hd0,msdos8'
 740e0848-bcc5-411a-b0ea-64ef31a954d0
 else
 search --no-floppy --fs-uuid --set=root 740e0848-bcc5-411a-b0ea-64ef31a954d0
 fi
 insmod png
 if background_image /share/images/desktop-base/joy-grub.png; then
 set color_normal=white/black
 set color_highlight=black/white
 else
 set menu_color_normal=cyan/blue
 set menu_color_highlight=white/blue
 fi
 ### END /etc/grub.d/05_debian_theme ###
 
 ### BEGIN /etc/grub.d/10_linux ###
 function gfxmode {
 set gfxpayload=${1}
 }
 set linux_gfx_mode=
 export linux_gfx_mode
 menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class
 gnu --class os $menuentry_id_option
 'gnulinux-simple-6b7438e1-b248-490c-8019-9af66aa7e176' {
 load_video
 insmod gzio
 insmod part_msdos
 insmod ext2
 set root='hd0,msdos5'
 if [ x$feature_platform_search_hint = xy ]; then
 search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5
 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 --hint='hd0,msdos5'
 6b7438e1-b248-490c-8019-9af66aa7e176
 else
 search --no-floppy --fs-uuid --set=root 6b7438e1-b248-490c-8019-9af66aa7e176
 fi
 echo 'Chargement de Linux 3.12.6.131226-gdn…'
 linux /boot/vmlinuz-3.12.6.131226-gdn
 root=UUID=6b7438e1-b248-490c-8019-9af66aa7e176 ro quiet
 echo 'Chargement du disque mémoire initial…'
 initrd /boot/initrd.img-3.12.6.131226-gdn
 }
 submenu 'Options avancées pour Debian GNU/Linux' $menuentry_id_option
 'gnulinux-advanced-6b7438e1-b248-490c-8019-9af66aa7e176' {
 menuentry 'Debian GNU/Linux, avec Linux 3.12.6.131226-gdn' --class
 debian --class gnu-linux --class 

Bug#735462: firmware-non-free: Drop reference to obsolete linux-image virtual package

[Andrei POPESCU]

Control: reassign -1 src:firmware-nonfree

On Mi, 15 ian 14, 16:37:34, hert...@debian.org wrote:
 Source: firmware-non-free
 Version: 0.40
 Severity: normal
 Usertags: obsolete-linux-image
 
 Hello,
 
 one (or more) binary package(s) generated by the firmware-non-free
 source package still mentions the “linux-image” virtual package
 in Recommends or Suggests. That virtual package is obsolete since the
 latest linux-image-* packages no longer provide this virtual package.
 
 See https://lists.debian.org/debian-devel/2013/09/msg00539.html for
 the rationale and some details.
 
 The presence of this virtual package in Recommends has the rather
 annoying side effect that when you try to install the package with
 APT, and that you have say wheezy and jessie repositories, APT will
 install the wheezy kernel that still provides linux-image and this
 even though you already have a jessie kernel installed...
 
 Please get rid of those linux-image dependencies.
 
 Cheers, 
 -- 
 Raphaël Hertzog ◈ Debian Developer
 
 Discover the Debian Administrator's Handbook:
 → http://debian-handbook.info/get/

-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Re: Bug#731016: Can't mount external USB HD Asus AN300

[Andrei POPESCU]

Control: reassign -1 src:linux

On Ma, 07 ian 14, 10:01:50, Ido Halperin wrote:
 
 I have just upgraded into kernel 3.12-1-amd64 but the problem persists.
 
 Until this issue will be solved I am trying to find some way to manually
 create the block device for this HDD but I don't know where I should
 look. 
 I found some pages about adding scsi device and following that I typed:
 
 
 **$ dmesg | tail -n 100
 
 [...]
 
 [24690.748752] usb 2-4: new SuperSpeed USB device number 7 using
 xhci_hcd
 [24690.765189] usb 2-4: New USB device found, idVendor=0b05,
 idProduct=17b6
 [24690.765196] usb 2-4: New USB device strings: Mfr=2, Product=3,
 SerialNumber=1
 [24690.765200] usb 2-4: Product: Super Speed Mass Storage
 [24690.765203] usb 2-4: Manufacturer: USB3.0 Device
 [24690.765205] usb 2-4: SerialNumber: 40201208020A
 [24690.765975] usb-storage 2-4:1.0: USB Mass Storage device detected
 [24690.766258] scsi17 : usb-storage 2-4:1.0
 [24691.768698] scsi 17:0:0:0: Direct-Access USB3.0 D Super Speed
 Mass 0PQ: 1 ANSI: 0
 [24691.768878] scsi 17:0:0:1: CD-ROMASMT VirtualCDROM
 PQ: 0 ANSI: 0
 [24691.769160] scsi 17:0:0:0: Attached scsi generic sg2 type 0
 [24691.769681] sr1: scsi-1 drive
 [24691.769834] sr 17:0:0:1: Attached scsi CD-ROM sr1
 [24691.769920] sr 17:0:0:1: Attached scsi generic sg3 type 5
 [24691.820241] xhci_hcd :00:14.0: WARN Event TRB for slot 14 ep 2
 with no TDs queued?
 [24691.960100] ISO 9660 Extensions: Microsoft Joliet Level 3
 [24691.960231] ISOFS: changing to secondary root
 
 
 
 I understand from that output that 17:0:0:0 is my hdd.
 I tried:
 
 **$ echo 0 0 0  /sys/class/scsi_host/host17/scan
 
 but no progress was achieved.
 Do you know if  there is  some scsi administration tool that may help
 me tom manually create the block device file?
  
 Ido.
 

-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Re: Bug#730482: linux-image-3.9.6: PCI/USB reset not being done on Geode LX800 / CS5536

[Andrei POPESCU]

Hi Kernel Maintainers,

Since the package doesn't exist this landed in the wrong place. Could 
you please have a look and take over the bug if useful?

Thanks,
Andrei

On Lu, 25 nov 13, 14:59:32, lkcl wrote:
 Package: linux-image-3.9.6
 Version: 3.9.6
 Severity: normal
 
 
 the normal reporting information is being removed because the report
 is being generated from an alternative non-SMTP-networked system
 
 here's what has to be done to solve the problem:
 
 write_sys(/sys/bus/usb/devices/usb1/remove, 1)
 write_sys(/sys/bus/usb/devices/usb2/remove, 1)
 
 write_sys(/sys/devices/pci:00/:00:0f.5/remove, 1)
 write_sys(/sys/devices/pci:00/:00:0f.4/remove, 1)
 time.sleep(5)
 write_sys(/sys/devices/pci:00/pci_bus/:00/rescan, 1)
 time.sleep(5)
 
 the two devices are listed from lspci, here:
 00:0f.4 USB controller: Advanced Micro Devices [AMD] CS5536 [Geode companion] 
 OHC (rev 02)
 00:0f.5 USB controller: Advanced Micro Devices [AMD] CS5536 [Geode companion] 
 EHC (rev 02)
 
 which correspond to the two removes above.
 
 this is basically an incredibly drastic PCI USB host controller reset
 which has to be done in between mountkernfs and udev.  it's therefore
 set up on an /etc/rc.S/S03 level script which carries out the resets
 that *should* be being done by the kernel modules themselves in the
 first place.
 
 symptoms are as follows:
 
 * put a USB 3G MiniPCIe modem into an alix6f2 LX800 board
 * ls /dev/ttyACM0
 * reboot (do NOT powercycle)
 * log in again
 * ls /dev/ttyACM0 - FAILS.
 
 however if instead of a reboot a halt and power-cycle is carried out instead,
 the 2nd ls /dev/ttyACM0 SUCCEEDS.
 
 it *also* succeeds even without a powercycle if the above drastic PCI device
 reset is carried out.
 
 if however this is carried out *after* udev is allowed to pick things up
 then we have a bit of a problem, which is that e.g. other USB devices
 (such as USB memory sticks or USB-to-serial converters) suddenly find that
 in the middle of loading the kernel module the device just... disappears
 (because the USB hub it's connected to just got a kick in the nuts).
 
 this has probably been a long-standing bug in the CS5536 PCI host controller
 code.  the reset should be being carried out at startup when the module
 is loaded.

-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Re: Bug#729542: firmware-ipw2200: instability with firmware 3.1

[Andrei POPESCU]

Control: reassign -1 firmware-ipw2x00 0.36+wheezy.1

On Mi, 13 nov 13, 18:44:36, Andres Salomon wrote:
 Package: firmware-ipw2200
 Version: 0.36+wheezy.1
 
 On my thinkpad x40, after a full day of use the wireless stops
 functioning.  This is with the ipw2200 3.1 firmware, which is currently
 in wheezy (and sid, I believe).  Reloading the ipw2200 module allows it
 to start working again.  I've tried this with multiple kernels (3.2 in
 wheezy, 3.10 in wheezy-backports) and get the same result.
 
 I found a thread that looks like a similar problem, which suggested
 downgrading the firmware.  I will give that a try with 3.0 firmware.
 
 Here's the thread:
 http://forums.gentoo.org/viewtopic-t-819782-start-0.html
 
 Here's dmesg output:
 [8.613489] libipw: 802.11 data/management/control stack, git-1.1.13
 [8.613552] libipw: Copyright (C) 2004-2005 Intel Corporation 
 jketr...@linux.intel.com
 [8.876998] snd_intel8x0 :00:1f.5: setting latency timer to 64
 [9.398883] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 
 1.2.2kmprq
 [9.398962] ipw2200: Copyright(c) 2003-2006 Intel Corporation
 [9.399455] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
 [9.442738] ipw2200 :02:02.0: firmware: agent loaded ipw2200-bss.fw 
 into memory
 [9.570550] ipw2200: Detected geography ZZR (14 802.11bg channels, 0 
 802.11a channels)
 [9.800073] intel8x0_measure_ac97_clock: measured 55167 usecs (2658 
 samples)
 [9.800137] intel8x0: clocking to 48000
 [9.803211] [drm] Memory usable by graphics device = 128M
 [9.803279] i915 :00:02.0: setting latency timer to 64
 [9.804832] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
 [9.804891] [drm] Driver supports precise vblank timestamp query.
 [9.813730] vgaarb: device changed decodes: 
 PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
 [9.824340] [drm] initialized overlay support
 [9.926898] fbcon: inteldrmfb (fb0) is primary device
 [   10.570137] Console: switching to colour frame buffer device 128x48
 [   10.589161] i915 :00:02.0: fb0: inteldrmfb frame buffer device
 [   10.589385] i915 :00:02.0: registered panic notifier
 [   10.589610] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on 
 minor 0
 [   12.271843] Adding 498008k swap on /dev/sda2.  Priority:-1 extents:1 
 across:498008k 
 [   12.903779] EXT3-fs (sda3): using internal journal
 [   13.146486] loop: module loaded
 [   15.235663] kjournald starting.  Commit interval 5 seconds
 [   15.236284] EXT3-fs (sda1): using internal journal
 [   15.245055] EXT3-fs (sda1): mounted filesystem with ordered data mode
 [   28.637793] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
 [ 1770.320059] ipw2200: Firmware error detected.  Restarting.
 [ 2444.719565] ipw2200: Firmware error detected.  Restarting.
 [ 2582.956118] ipw2200: Failed to send SYSTEM_CONFIG: Already sending a 
 command.
 [ 3993.115919] ipw2200: Failed to send SYSTEM_CONFIG: Already sending a 
 command.
 [ 4224.987218] ipw2200: Failed to send SYSTEM_CONFIG: Already sending a 
 command.
 [ 4674.398093] ipw2200: Failed to send SYSTEM_CONFIG: Already sending a 
 command.
 [ 5091.795353] ipw2200: Failed to send SYSTEM_CONFIG: Already sending a 
 command.
 [ 5624.415277] ipw2200: Failed to send SYSTEM_CONFIG: Already sending a 
 command.
 [ 5658.786056] ipw2200: Failed to send SYSTEM_CONFIG: Already sending a 
 command.
 [ 7039.317926] ipw2200: Failed to send SYSTEM_CONFIG: Already sending a 
 command.
 [ 7547.025554] ipw2200: Failed to send ASSOCIATE: Already sending a command.
 [16192.912553] e1000: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: 
 RX/TX
 [16192.912630] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Re: Bug#714345: Subject: Re: Bug#714345: alsa-base: No sound on PowerPC with Jessie upgrade

[Andrei POPESCU]

Control: reassign -1 src:linux

On Vi, 01 nov 13, 04:28:49, elsner@googlemail.com wrote:
 Hello,
 
 i had the same problem on a PowerBook g4, kernel 3.10.
 
 Found a hint in another bug-report on google:
 It turns out that module i2c_powermac simply wasn't loaded.
 This module is the driver for the i2c bus, on which the snd_aoa-modules 
 depend.
 Makes sense, huh?
 
 For whatever reason the module isn't autoloaded anymore.
 
 A simple modprobe i2c_powermac made my soundcard work again.
 Next step: enter the module in /etc/modules and be happy.
 
 Hope this helps
 
 Regards
 
 Karl Elsner
 
 
 
 
 
 Von meinem iPad gesendet

-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Re: Bug#726821: linux: shutdown -h now reboots instead shutting down the system

[Andrei POPESCU]

Control: reassign -1 linux-image-3.2.0-4-amd64

On Sb, 19 oct 13, 17:20:44, Camaleón wrote:
 Package: linux-image-3.2.0-3-amd64
 Version: 3.2.51-1
 Severity: normal
 
Based on the version I'm guessing you meant -4, reassigning accordingly. 

BTW, classic debugging question: did you try a newer kernel (e.g. from 
backports, which has 3.10)?

 I'm experiencing the same problem as reported at BTS #691902¹ but given the 
 difference in hardware I open a new report.
 
 Running Debian Wheezy, XFCE and nouveau driver, whether I try to shutdown
 the system by either:
 
 - using XFCE's menu entry;
 - issuing on xfce4-terminal shutdown -h now;
 - stopping lightdm service and then issuing on tty1 shutdown -h now;
 
 I get the same random behaviour: system restarts instead shtting down. 
 But this happens sometimes, other times it shutdowns fine (error ratio 
 is about 50%).
 
 Note 1: I have several computers running the same configuration 
 (wheezy+xfce) but this issue is only reproducible under one system that 
 uses nouveau driver (the others run nvidia closed source driver). The 
 other difference is the hardware itself which is different on every 
 computer.
 
 Note 2: this is a production system so cannot perform any hard test 
 (e.g., installing a new kernel or compile it from scratch).
 
 Attaching dmesg.
 
 ¹http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691902

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Re: Bug#712855: Better!

[Andrei POPESCU]

Control: reassign -1 src:linux
Control: fixed -1 3.10.7-1
Control: close -1

On Jo, 29 aug 13, 02:05:19, Yohann Ferreira wrote:
 Hi!
 
 It's the same old me again.
 
 I've tried a bit more the latest kernel 3.10 in debian unstable and the wifi 
 problems are mostly gone! :D (Hurray!!)
 
 My kernel:
 Linux Valyria 3.10-2-amd64 #1 SMP Debian 3.10.7-1 (2013-08-17) x86_64 
 GNU/Linux
 
 When unplugging the cable (laptop on battery), I sometimes have the 
 connection 
 dying  but after a few minutes everything is back to normal.
 
 The signal is a bit weaker than before all that (in linux 3.2.0) but internet 
 browsing, downloading and the connection stability is overall fine.
 
 Thanks for all the hard work on this!!
 
 Best regards,
 
 Yohann

Hi Yohann,

Thanks for following up with this, especially since your report has 
fallen through the cracks (due to package renaming).

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Bug#711526: mmc0: Timeout waiting for hardware interrupt.

[Andrei POPESCU]

Control: reassign -1 linux-image-3.2.0-4-amd64
Control: found -1 3.2.41-2+deb7u2

On Vi, 07 iun 13, 14:57:49, pepelopez wrote:
 Package: 3.2.41-2+deb7u2
 Version: linux-image-3.2.0-4-amd64

Dear pepelopez,

You mixed up the package name with the version, which is why:

1. your report was filled against 'unknown-package'
2. it misses information that may be very useful for the Maintainers

I'm taking care of 1., but kindly run

reportbug linux-image-3.2.0-4-amd64

and send the generated information as a follow-up for this bug (number 
711526).

Kind regards,
Andrei
-- 
Looking after bugs filled against unknown packages


signature.asc
Description: Digital signature

Bug#688132: firmware-nonfree: Romanian translation of the debconf template

[Andrei POPESCU]

Source: firmware-nonfree
Severity: wishlist
Tags: patch l10n

Dear Maintainer,

See attached the Romanian translation of the debconf template.

Kind regards,
Andrei

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

Kernel: Linux 3.2.0-3-rt-686-pae (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=ro_RO.UTF-8, LC_CTYPE=ro_RO.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
# Romanian translation of firmware-nonfree.
# Copyright (C) 2012
# This file is distributed under the same license as the firmware-nonfree package.
# Andrei POPESCU andreimpope...@gmail.com, 2012.
#
msgid 
msgstr 
Project-Id-Version: firmware-nonfree\n
Report-Msgid-Bugs-To: firmware-nonf...@packages.debian.org\n
POT-Creation-Date: 2012-09-03 12:15+0200\n
PO-Revision-Date: 2012-09-19 19:56+0300\n
Last-Translator: Andrei POPESCU andreimpope...@gmail.com\n
Language-Team: Romanian Team debian-l10n-roman...@lists.debian.org\n
Language: ro\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit\n

#. Type: boolean
#. Description
#: ../templates/templates.license.in:2001
msgid Do you agree to the \@license-title@\?
msgstr Sunteți de acord cu „@license-title@”?

#. Type: boolean
#. Description
#: ../templates/templates.license.in:2001
msgid 
In order to install this package, you must agree to the following terms, the 
\@license-title@\. If you do not agree, the installation will be canceled.
msgstr 
Pentru a instala acest pachet trebuie să acceptați termenii licenței 
„@license-title@”. Dacă nu sunteți de acord instalarea va fi anulată.

#. Type: error
#. Description
#: ../templates/templates.license.in:3001
msgid Declined @license-title@
msgstr @license-title@ refuzată

#. Type: error
#. Description
#: ../templates/templates.license.in:3001
msgid 
If you do not agree to the \@license-title@\  license terms you cannot 
install this software.
msgstr 
Dacă nu acceptați termenii licenței „@license-title@” nu puteți instala 
acest software.

#. Type: error
#. Description
#: ../templates/templates.license.in:3001
msgid The installation of this package has been canceled.
msgstr Instalarea acestui pachet a fost anulată.

Re: new hardware support: calling for testing

[Andrei Popescu]

On Sb, 17 sep 11, 17:01:15, Ben Hutchings wrote:
 On Sat, 2011-09-17 at 15:00 +0200, Francesca Ciceri wrote:
 [...]
  The Debian project invites interested users to pre-release test these
  packages, especially on systems that use the updated drivers, possibly
  within September 24th: so that if there will not be regressions, the new
  drivers will be added to the upcoming point release.
 [...]
 
 If there are regressions, we want to fix them, not revert all the
 changes.

How about this:

~~~
The Debian project invites interested users to pre-release test these 
packages, especially on systems that use the updated drivers.
The drivers [...]

Any problems found in testing should be reported to the Debian bug 
tracking system using the 'reportbug' tool. Reports should preferably be 
sent until September 24th, but later reports of serious issues will 
still be taken into consideration. In case of regressions in the updated 
drivers, please follow up to the bug number listed above.
~~~

Kind regards,
Andrei
-- 
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic


signature.asc
Description: Digital signature

Bug#613534: Seems to be rather a bug in nvidia, not the kernel

[Andrei Popescu]

reassign 613536
retitle 613536 Some special keys don't work with nvidia + newer kernel
thanks

On Ma, 15 feb 11, 16:13:31, Andrei POPESCU wrote:
 
 The ThinkVantage button is not producing any reaction at all in xev. 
 This worked fine until now, including on 2.6.36-trunk-amd64. Any other 
 things to try that might help you?

Further experiments show that this bug happens only with nvidia and 
kernel 2.6.37 or newer, it does not happen with nouveau.

I tried to test on squeeze (older Xorg), but the kernel module won't 
compile on 2.6.38 from unstable.

acpi_listen is silent as long as I'm in X, but will react to key presses 
even if I only switch to the console with Ctrl+Alt+F1.

Please ask if you need more info, this bug is very annoying for me.

Regards,
Andrei
-- 
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic


signature.asc
Description: Digital signature

Bug#613534: regression: ThinkVantage button doesn't work on ThinkPad R61i since 2.6.37

[Andrei POPESCU]

Package: linux-2.6
Version: 2.6.37-1~experimental.1
Severity: normal

Hi,

The ThinkVantage button is not producing any reaction at all in xev. 
This worked fine until now, including on 2.6.36-trunk-amd64. Any other 
things to try that might help you?

Regards,
Andrei

-- Package-specific info:
** Version:
Linux version 2.6.37-trunk-amd64 (Debian 2.6.37-1~experimental.1) 
(b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.5-10) ) #1 SMP Thu Jan 6 
14:13:28 UTC 2011

** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.37-trunk-amd64 
root=UUID=dff9280e-3948-4edd-a64d-e33aa0384ccf ro quiet 4

** Tainted: P (1)
 * Proprietary module has been loaded.

** Kernel log:
[6.107537] usb 2-5: Product: Integrated Camera
[6.107540] usb 2-5: Manufacturer: Chicony Electronics Co., Ltd.
[6.107543] usb 2-5: SerialNumber: SN0001
[6.244228] firewire_core: created device fw0: GUID 00061b032a1dae65, S400
[6.313784] usbcore: registered new interface driver usbserial
[6.313813] USB Serial support registered for generic
[6.344818] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 
in-tree:
[6.344822] iwlagn: Copyright(c) 2003-2010 Intel Corporation
[6.344956] iwlagn :03:00.0: PCI INT A - GSI 17 (level, low) - IRQ 17
[6.344996] iwlagn :03:00.0: setting latency timer to 64
[6.345126] iwlagn :03:00.0: Detected Intel(R) Wireless WiFi Link 
4965AGN, REV=0x4
[6.345441] HDA Intel :00:1b.0: PCI INT B - GSI 17 (level, low) - IRQ 
17
[6.345447] hda_intel: probe_mask set to 0x1 for device 17aa:20ac
[6.345660] HDA Intel :00:1b.0: irq 48 for MSI/MSI-X
[6.345759] HDA Intel :00:1b.0: setting latency timer to 64
[6.348071] usb 3-1: new full speed USB device using uhci_hcd and address 2
[6.388315] iwlagn :03:00.0: device EEPROM VER=0x36, CALIB=0x5
[6.388370] iwlagn :03:00.0: Tunable channels: 13 802.11bg, 19 802.11a 
channels
[6.388560] iwlagn :03:00.0: irq 49 for MSI/MSI-X
[6.454834] iwlagn :03:00.0: loaded firmware version 228.61.2.24
[6.512839] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'
[6.515204] usb 3-1: New USB device found, idVendor=0a5c, idProduct=2110
[6.515209] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[6.515213] usb 3-1: Product: BCM2045B
[6.515215] usb 3-1: Manufacturer: Broadcom Corp
[6.760069] usb 3-2: new full speed USB device using uhci_hcd and address 3
[6.917099] input: HDA Digital PCBeep as 
/devices/pci:00/:00:1b.0/input/input8
[6.918874] ata_piix :00:1f.1: version 2.13
[6.918900] ata_piix :00:1f.1: PCI INT C - GSI 16 (level, low) - IRQ 16
[6.918984] ata_piix :00:1f.1: setting latency timer to 64
[6.919696] scsi3 : ata_piix
[6.919827] scsi4 : ata_piix
[6.920545] ata4: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0x18c0 irq 14
[6.920550] ata5: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x18c8 irq 15
[6.920995] ata5: port disabled. ignoring.
[6.939191] usb 3-2: New USB device found, idVendor=147e, idProduct=2016
[6.939196] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[6.939199] usb 3-2: Product: Fingerprint Sensor   
[6.939202] usb 3-2: Manufacturer: TouchStrip
[6.941481] usbcore: registered new interface driver usbserial_generic
[6.941485] usbserial: USB Serial Driver core
[7.088739] ata4.00: ATAPI: HL-DT-ST DVDRAM GMA-4082N, EX01, max UDMA/33
[7.104327] ata4.00: configured for UDMA/33
[7.109811] scsi 3:0:0:0: CD-ROMHL-DT-ST DVDRAM GMA-4082N EX01 
PQ: 0 ANSI: 5
[7.299549] Bluetooth: Core ver 2.15
[7.299586] NET: Registered protocol family 31
[7.299589] Bluetooth: HCI device and connection manager initialized
[7.299592] Bluetooth: HCI socket layer initialized
[7.345425] Bluetooth: Generic Bluetooth USB driver ver 0.6
[7.350556] usbcore: registered new interface driver btusb
[7.559574] USB Serial support registered for GSM modem (1-port)
[7.559698] usbcore: registered new interface driver option
[7.559700] option: v0.7.2:USB Driver for GSM modems
[7.620817] nvidia: module license 'NVIDIA' taints kernel.
[7.620822] Disabling lock debugging due to kernel taint
[7.639000] pcmcia_socket pcmcia_socket0: cs: memory probe 
0x0c-0x0f: excluding 0xc-0xd3fff 0xe-0xf
[7.639100] pcmcia_socket pcmcia_socket0: cs: memory probe 
0xa000-0xa0ff: clean.
[7.639198] pcmcia_socket pcmcia_socket0: cs: memory probe 
0x6000-0x60ff: excluding 0x6000-0x60ff
[7.770481] sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda 
tray
[7.770486] cdrom: Uniform CD-ROM driver Revision: 3.20
[7.770992] sr 3:0:0:0: Attached scsi CD-ROM sr0
[7.849439] Linux video capture interface: v2.00
[7.873953] uvcvideo: Found UVC 1.00 device Integrated Camera (17ef:1004)
[7.879001] input: Integrated Camera as 

Bug#581876: Please apply upstream patch to fix the beep for some Thinkpad machines

[Andrei Popescu]

On Vi, 04 iun 10, 00:46:16, Moritz Muehlenhoff wrote:
 Version: 2.6.34-1
 
 Andrei Popescu wrote:
  On Mon,17.May.10, 02:48:28, Ben Hutchings wrote:
   
   Sorry, this patch cannot be applied on its own.  It depends on other
   changes to registration of 'beep' devices, and I'm not yet convinced
   that it's worth the risk to backport those changes.
  
  Thanks for considering. If there's anything I can do to help please let 
  me know.
 
 The patch was merged in 2.6.34, marking that version as fixed.

Do you mean the version in experimental? I'll test as soon as I have 
time.

Regards,
Andrei
-- 
http://nuvreauspam.ro/2010/05/4-neticheta-pe-mail/


signature.asc
Description: Digital signature

Bug#581876: Please apply upstream patch to fix the beep for some Thinkpad machines

[Andrei Popescu]

On Mon,17.May.10, 02:48:28, Ben Hutchings wrote:
 
 Sorry, this patch cannot be applied on its own.  It depends on other
 changes to registration of 'beep' devices, and I'm not yet convinced
 that it's worth the risk to backport those changes.

Thanks for considering. If there's anything I can do to help please let 
me know.

Regards,
Andrei
-- 
http://nuvreauspam.ro/2010/05/4-neticheta-pe-mail/


signature.asc
Description: Digital signature

Bug#581876: Please apply upstream patch to fix the beep for some Thinkpad machines

[Andrei Popescu]

Package: linux-2.6
Severity: wishlist

Hello,

2.6.30 introduced a regression where some Thinkpads would not beep 
anymore on plugging/unplugging the power chord. See this thread
http://sourceforge.net/mailarchive/message.php?msg_id=m31vgd2v3h.fsf%40fox.lamasti.net
for more info.

The alsa developers came up with a patch[1], but I haven't been able to 
test it myself as it won't apply against 2.6.32 from sid or even 2.6.33 
from experimental.

If it isn't too much work to backport the patch it would be nice to have 
it in squeeze. I could test if needed (assuming I get the rebuild[2] 
right), but I lack the skills to do it myself.

[1] 
http://sourceforge.net/mailarchive/message.php?msg_name=alpine.LNX.2.00.1003261047210.3925%40eeebox2.perex-int.cz

[2] http://wiki.debian.org/HowToRebuildAnOfficialDebianKernelPackage
BTW, there's a minor addition I wanted to do for this page, but it's set 
immutable...

Regards,
Andrei

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=ro_RO.UTF-8, LC_CTYPE=ro_RO.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/20100516202621.10814.56037.report...@think.homelan

Bug#532005: this seems related to my issue

[Andrei Popescu]

On Du,14.feb.10, 23:02:11, Moritz Muehlenhoff wrote:

  Until 2.6.29-2-amd64 my laptop was making a special sound (two 
  system beeps in rapid succession) when plugging/unplugging the power 
  cord. This sound would work whether the pcspkr module was loaded or 
  not (which would stop any other system beeps), but can be disabled 
  by muting the Beep control in alsamixer. It also works during POST 
  or at the grub menu.
  
  With 2.6.30-1-amd64 this works only a few seconds into the boot sequence 
  when it stops completely and no loading/unloading of modules or 
  mutin/unmuting of channels will bring it back. This seems to be related 
  to this
  
  $ dmesg | grep Beep
  [6.234499] input: HDA Digital PCBeep as 
  /devices/pci:00/:00:1b.0/input/input10
  
  (I see the submitter has the same thing in his dmesg)
 
 Hi,
 The next release of Debian (6.0, code name Squeeze) will be based
 on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell
 us whether the problem persists. If so, we should report it upstream
 to the kernel.org developers.

Hello,

The high pitch has been solved already in 2.6.32-trunk-amd64, but I 
can't test the other issue (no beeps when removing the power cord) 
because my battery is dead and removing the cord will kill the system.

Buying a new battery is on my TODO list and I will report back ASAP.  
Thank you for looking into this issue.

Regards,
Andrei
-- 
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic


signature.asc
Description: Digital signature

Bug#435560: linux-image-2.6.22-1-686: initrd creation fails with yaird

[Andrei Popescu]

Package: linux-image-2.6.22-1-686
Version: 2.6.22-3
Severity: normal


Here is a paste from aptitude's output:

Setting up linux-image-2.6.22-1-686 (2.6.22-3) ...
Running depmod.
Finding valid ramdisk creators.
Using mkinitrd.yaird to build the ramdisk.
yaird error: unrecognised line in /proc/bus/input/devices: U: Uniq= (fatal)
mkinitrd.yaird failed to create initrd image.
Failed to create initrd image.
dpkg: error processing linux-image-2.6.22-1-686 (--configure):
 subprocess post-installation script returned error exit status 9

I will reboot with a different kernel and try a to reinstall. I will 
post back if it works.

Contact me if you need more info.

Regards,
Andrei

-- Package-specific info:
** Version:
Linux version 2.6.22-1-686 (Debian 2.6.22-2) ([EMAIL PROTECTED]) (gcc version 
4.1.3 20070718 (prerelease) (Debian 4.1.2-14)) #1 SMP Mon Jul 23 13:23:02 UTC 
2007

** Not tainted

** Kernel log:
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda8, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
ip_tables: (C) 2000-2006 Netfilter Core Team
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (4023 buckets, 32184 max)
ip6_tables: (C) 2000-2006 Netfilter Core Team
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
ctnetlink v0.93: registering with nfnetlink.
ClusterIP Version 0.8 loaded successfully
ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
ACPI: Processor [CPU] (supports 8 throttling states)
Marking TSC unstable due to: possible TSC halt in C2.
Time: acpi_pm clocksource has been installed.
ACPI: Battery Slot [BAT0] (battery present)
ACPI: AC Adapter [AC] (on-line)
input: Power Button (FF) as /class/input/input3
ACPI: Power Button (FF) [PWRF]
input: Lid Switch as /class/input/input4
ACPI: Lid Switch [LID]
input: Sleep Button (CM) as /class/input/input5
ACPI: Sleep Button (CM) [SLPB]
ACPI: Thermal Zone [THM0] (56 C)
Non-volatile memory driver v1.2
input: /usr/sbin/thinkpad-keys as /class/input/input6
Clocksource tsc unstable (delta = -217462088 ns)
eth0: no IPv6 routers present
[drm] Initialized drm 1.1.0 20060810
ACPI: PCI Interrupt :00:02.0[A] - Link [LNKA] - GSI 11 (level, low) - 
IRQ 11
[drm] Initialized i915 1.6.0 20060119 on minor 0
[drm] Initialized i915 1.6.0 20060119 on minor 1
QEMU Accelerator Module version 1.3.0, Copyright (c) 2005-2007 Fabrice Bellard
KQEMU installed, max_locked_mem=253696kB.
hdc: tray open
end_request: I/O error, dev hdc, sector 0
Buffer I/O error on device hdc, logical block 0
Buffer I/O error on device hdc, logical block 1
Buffer I/O error on device hdc, logical block 2
Buffer I/O error on device hdc, logical block 3
Buffer I/O error on device hdc, logical block 4
Buffer I/O error on device hdc, logical block 5
Buffer I/O error on device hdc, logical block 6
Buffer I/O error on device hdc, logical block 7
hdc: tray open
end_request: I/O error, dev hdc, sector 0
Buffer I/O error on device hdc, logical block 0
hdc: tray open
end_request: I/O error, dev hdc, sector 4
Buffer I/O error on device hdc, logical block 1
hdc: tray open
end_request: I/O error, dev hdc, sector 0
Buffer I/O error on device hdc, logical block 0
Buffer I/O error on device hdc, logical block 1
Buffer I/O error on device hdc, logical block 2
Buffer I/O error on device hdc, logical block 3
Buffer I/O error on device hdc, logical block 4
Buffer I/O error on device hdc, logical block 5
Buffer I/O error on device hdc, logical block 6
Buffer I/O error on device hdc, logical block 7
hdc: tray open
end_request: I/O error, dev hdc, sector 0
Buffer I/O error on device hdc, logical block 0
hdc: tray open
end_request: I/O error, dev hdc, sector 4
Buffer I/O error on device hdc, logical block 1
hdc: tray open
end_request: I/O error, dev hdc, sector 0
Buffer I/O error on device hdc, logical block 0
Buffer I/O error on device hdc, logical block 1
Buffer I/O error on device hdc, logical block 2
Buffer I/O error on device hdc, logical block 3
Buffer I/O error on device hdc, logical block 4
Buffer I/O error on device hdc, logical block 5
Buffer I/O error on device hdc, logical block 6
Buffer I/O error on device hdc, logical block 7
hdc: tray open
end_request: I/O error, dev hdc, sector 0
Buffer I/O error on device hdc, logical block 0
hdc: tray open
end_request: I/O error, dev hdc, sector 4
Buffer I/O error on device hdc, logical block 1
hdc: tray open
end_request: I/O error, dev hdc, sector 0
Buffer I/O error on device hdc, logical block 0
Buffer I/O error on device hdc, logical block 1
Buffer I/O error on device hdc, logical block 2
Buffer I/O error on device hdc, logical block 3
Buffer I/O error on device hdc, logical block 4
Buffer I/O error on device hdc, logical block 5
Buffer I/O error on device hdc, logical block 6
Buffer I/O error on device hdc, logical block 7
hdc: tray open
end_request: I/O error, dev hdc, sector 0
Buffer I/O error 

Bug#435560: Reboot sucessful

[Andrei Popescu]

I booted with the new kernel and the old initrd and it worked. 'aptitude 
reinstall' generated the same error so I rebooted with an older kernel 
(2.6.21) and the reinstall worked. I am now running the 2.6.22 without 
apparent problems.

Regards,
Andrei
-- 
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)


signature.asc
Description: Digital signature