Bug#721005: linux: sierra Gobi 3000 WWAN no longer works
Source: linux Version: 3.10.7-1 Severity: normal Hi. I got a little bit stuck with this... I'm having a Fujitsu Lifebook E782 which has some Sierra Gobi 3000 UMTS modem in it. For many years it simply used to work perfectly, but a year ago or so it already stopped working (i.e. wasn't detected anymore by the kernel)... but it came back surprisingly around March that year and worked at least until May. Unfortunately I don't know when exactly it stopped worked since I use it only rarley when I'm on train. # lsusb Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 009: ID 04f2:b2fc Chicony Electronics Co., Ltd Bus 001 Device 011: ID 0489:e052 Foxconn / Hon Hai Bus 001 Device 010: ID 0b97:7772 O2 Micro, Inc. OZ776 CCID Smartcard Reader Bus 001 Device 003: ID 0b97:7761 O2 Micro, Inc. Oz776 1.1 Hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Manually loading sierra or sierra_net doens't help either, but the device is enabled in the BIOS. Any ideas? Cheers, Chris. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.10-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.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/20130827022933.3584.69451.report...@heisenberg.scientia.net
Bug#701744: Xen netback regression
Hi all, Are there any updates on the final resolution of this bug? It's been a while, and it's still marked as pending... Thanks, Ward. -- Ward Vandewege | CTO, Free Software Foundation GPG Key: 25F774AB | http://status.fsf.org/ward http://fsf.org/blogs/RSS | http://identi.ca/cure Do you use free software? Donate to join the FSF and support freedom at http://www.fsf.org/register_form?referrer=859 -- 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/20130827004827.ga30...@countzero.vandewege.net
Bug#720743: closed by Ben Hutchings (Re: Bug#720743: [firmware-brcm80211] the firmware crashes kernel-3.10.9)
So, you are not going to enable gpio on bcma, isn't it? Il giorno 26/ago/2013 12:21, "Debian Bug Tracking System" < ow...@bugs.debian.org> ha scritto: > This is an automatic notification regarding your Bug report > which was filed against the firmware-brcm80211 package: > > #720743: [firmware-brcm80211] the firmware crashes kernel-3.10.9 > > It has been closed by Ben Hutchings . > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Ben Hutchings < > b...@decadent.org.uk> by > replying to this email. > > > -- > 720743: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720743 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > > > -- Messaggio inoltrato -- > From: Ben Hutchings > To: 720743-d...@bugs.debian.org > Cc: > Date: Mon, 26 Aug 2013 11:18:55 +0100 > Subject: Re: Bug#720743: [firmware-brcm80211] the firmware crashes > kernel-3.10.9 > On Sun, 2013-08-25 at 02:56 +0200, Valerio Passini wrote: > > Package: firmware-brcm80211 > > Version: 0.39~bpo70+1 > > Severity: normal > > > > --- Please enter the report below this line. --- > > The last firmware provided in unstable (should be 0.40) doesn't work > with my > > 3.8.13 custom kernel, and what is worse, causes kernel opses in my custom > > 3.10.9 kernel locking it totally. Reverting to any previous version down > to > > the one present in wheezy at least allows to connect with kernel 3.8.13, > but > > all of them crashes the kernel 3.10.9. > > This is a driver bug, and you aren't using a Debian kernel so this isn't > our bug. > > Ben. > > -- > Ben Hutchings > This sentence contradicts itself - no actually it doesn't. > > > -- Messaggio inoltrato -- > From: Valerio Passini > To: sub...@bugs.debian.org > Cc: > Date: Sun, 25 Aug 2013 02:56:33 +0200 > Subject: [firmware-brcm80211] the firmware crashes kernel-3.10.9 > Package: firmware-brcm80211 > Version: 0.39~bpo70+1 > Severity: normal > > --- Please enter the report below this line. --- > The last firmware provided in unstable (should be 0.40) doesn't work with > my > 3.8.13 custom kernel, and what is worse, causes kernel opses in my custom > 3.10.9 kernel locking it totally. Reverting to any previous version down to > the one present in wheezy at least allows to connect with kernel 3.8.13, > but > all of them crashes the kernel 3.10.9. > Best regards > > Valerio > > > > --- System information. --- > Architecture: amd64 > Kernel: Linux 3.8.13 > > Debian Release: jessie/sid > 990 unstablemi.mirror.garr.it > 990 unstableftp.uk.debian.org > 990 unstableftp.it.debian.org > 500 wheezy activsoftware.co.uk > 500 testing mi.mirror.garr.it > 500 testing ftp.uk.debian.org > 500 stable deb.opera.com > 1 experimentalmi.mirror.garr.it > 1 experimentalftp.uk.debian.org > > --- Package information. --- > Package's Depends field is empty. > > Package's Recommends field is empty. > > Suggests (Version) | Installed > ==-+-=== > initramfs-tools| 0.113 > linux-image| > > > > > Valerio > >
Bug#721002: Please set CONFIG_HID_HUION=m
Package: src:linux Version: 3.11~rc4-1~exp1 Severity: minor Please set CONFIG_HID_HUION=m; this driver handles a series of cheap tablet input devices which was recently added to the kernel. -- Don Armstrong http://www.donarmstrong.com DIE! -- Maritza Campos http://www.crfh.net/d/20020601.html -- 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/20130826223626.gs27...@rzlab.ucr.edu
Bug#720998: linux-image-3.2.0-4-amd64: in pid_nr_ns: unable to handle kernel NULL pointer dereference at 0000000000000013 Package: src:linux Version: 3.2.46-1 Severity: normal
Package: src:linux Version: 3.2.46-1 Severity: normal During a scheduled shutdown, the kernel crashed and locked up. the monitor showed several more failures after the one that got recorded below (i can attach a screenshot if that would be useful), but i believe this is the first visible symptom (the timestamps on the backtraces visible on the monitor are all 51010.*, about 10 minutes later than the first NULL pointer dereference). After a reboot, the machine comes up fine. the RAM has been tested via memtest86+, no errors shown. note that this is a 64-bit kernel with a 32-bit userland. Aug 21 07:00:45 hobbes kernel: [ 24.415401] sha1_ssse3: Using AVX optimized SHA-1 implementation Aug 21 07:00:47 hobbes kernel: [ 26.512023] eth0: no IPv6 routers present Aug 21 21:00:34 hobbes kernel: [50413.229680] BUG: unable to handle kernel NULL pointer dereference at 0013 Aug 21 21:00:34 hobbes kernel: [50413.229772] IP: [] pid_nr_ns+0xd/0x24 Aug 21 21:00:34 hobbes kernel: [50413.229837] PGD 1297e6067 PUD 12863a067 PMD 0 Aug 21 21:00:34 hobbes kernel: [50413.229894] Oops: [#1] SMP Aug 21 21:00:34 hobbes kernel: [50413.229936] CPU 3 Aug 21 21:00:34 hobbes kernel: [50413.229958] Modules linked in: sha1_ssse3 sha1_generic hmac cbc cts bnep rfcomm bluetooth rfkill crc16 uinput rpcsec_gss_krb5 nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc loop snd_hda_codec_realtek snd_hda_codec_hdmi powernow_k8 mperf snd_hda_intel crc32c_intel ghash_clmulni_intel aesni_intel snd_hda_codec i2c_piix4 snd_hwdep snd_pcm snd_page_alloc aes_x86_64 snd_seq snd_seq_device snd_timer snd soundcore processor psmouse tpm_tis tpm tpm_bios thermal_sys serio_raw pcspkr aes_generic cryptd evdev ext3 mbcache jbd dm_mod microcode usbhid hid sg sr_mod sd_mod cdrom crc_t10dif usb_storage ohci_hcd radeon xhci_hcd ahci libahci ehci_hcd power_supply i2c_algo_bit r8169 mii libata button usbcore scsi_mod usb_common ttm drm_kms_helper drm wmi i2c_core [last unloaded: scsi_wait_scan] Aug 21 21:00:34 hobbes kernel: [50413.230916] Aug 21 21:00:34 hobbes kernel: [50413.230936] Pid: 6813, comm: killall5 Not tainted 3.2.0-4-amd64 #1 Debian 3.2.46-1 LENOVO 4865A14/Annapurna CRB Aug 21 21:00:34 hobbes kernel: [50413.231045] RIP: 0010:[] [] pid_nr_ns+0xd/0x24 Aug 21 21:00:34 hobbes kernel: [50413.231126] RSP: :88012908bea8 EFLAGS: 00010206 Aug 21 21:00:34 hobbes kernel: [50413.231179] RAX: RBX: RCX: 0012 Aug 21 21:00:34 hobbes kernel: [50413.231249] RDX: RSI: 8161c060 RDI: 000f Aug 21 21:00:34 hobbes kernel: [50413.231317] RBP: 88012646c1c0 R08: R09: 00013780 Aug 21 21:00:34 hobbes kernel: [50413.231386] R10: 00013780 R11: 880126972300 R12: 0013 Aug 21 21:00:34 hobbes kernel: [50413.231458] R13: 0038 R14: 88012646c330 R15: 880126a7d1a0 Aug 21 21:00:34 hobbes kernel: [50413.231528] FS: () GS:88012fd8(0063) knlGS:f77378d0 Aug 21 21:00:34 hobbes kernel: [50413.231606] CS: 0010 DS: 002b ES: 002b CR0: 8005003b Aug 21 21:00:34 hobbes kernel: [50413.231663] CR2: 0013 CR3: 000129e86000 CR4: 000406e0 Aug 21 21:00:34 hobbes kernel: [50413.231732] DR0: DR1: DR2: Aug 21 21:00:34 hobbes kernel: [50413.231801] DR3: DR6: 0ff0 DR7: 0400 Aug 21 21:00:34 hobbes kernel: [50413.231870] Process killall5 (pid: 6813, threadinfo 88012908a000, task 880126a7d1a0) Aug 21 21:00:34 hobbes kernel: [50413.231950] Stack: Aug 21 21:00:34 hobbes kernel: [50413.231973] 8105cedc 81056538 e000 0013 Aug 21 21:00:34 hobbes kernel: [50413.232067] 1a9d 0001 810d292e Aug 21 21:00:34 hobbes kernel: [50413.232153] 88012908bf24 810d2a3d Aug 21 21:00:34 hobbes kernel: [50413.232239] Call Trace: Aug 21 21:00:34 hobbes kernel: [50413.232269] [] ? __task_pid_nr_ns+0x46/0x47 Aug 21 21:00:34 hobbes kernel: [50413.232331] [] ? sys_kill+0xc8/0x14c Aug 21 21:00:34 hobbes kernel: [50413.232387] [] ? __mlock_vma_pages_range+0x5e/0x65 Aug 21 21:00:34 hobbes kernel: [50413.232452] [] ? do_mlock_pages+0x108/0x11a Aug 21 21:00:34 hobbes kernel: [50413.232513] [] ? ia32_do_call+0x13/0x13 Aug 21 21:00:34 hobbes kernel: [50413.232567] Code: e9 a1 f9 ff ff 65 48 8b 04 25 00 c7 00 00 48 8b 80 88 04 00 00 48 8b 70 20 e9 d8 ff ff ff 31 c0 48 85 ff 74 1c 8b 96 20 08 00 00 <3b> 57 04 77 11 48 c1 e2 05 48 8d 54 17 30 48 39 72 08 75 02 8b Aug 21 21:00:34 hobbes kernel: [50413.232985] RIP [] pid_nr_ns+0xd/0x24 Aug 21 21:00:34 hobbes kernel: [50413.233043] RSP Aug 21 21:00:34 hobbes kernel: [50413.233079] CR2: 0013 Aug 21 21:00:34 hobbes kernel: [50413.233138] ---[ end trace 8c52e8a6600
Bug#622325: additional problems
As per Roman's advice, a full power off and unplug allowed me to boot and run pwmconfig, this set up my /etc/fancontrol properly... on reboot, hwmon0 and hwmon1 switched and fancontrol started at boot but was unable to do anything with my hardware due to the switched sym link... when i re-ran pwmconfig I once again got the "i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0" message repeat about 10 times and had to do a full power off / unplug to run pwmconfig again and setup my config file again. I don't know how to keep hwmon0 and hwmon1 from switching places each boot, the soultions ive found involving editing lm_sensors config file or modules.conf dont seem to apply to debian... other than that the problem seems to occur again if anything involving the fan or temperature sensor is queried more than once per cold boot
Bug#717765: linux-image-3.2.0-4-amd64: panic in ccm crypto module
Gerald Turner writes: > I'll will be changing IPsec configurations to the more classic AES-CBC > modes and report back whether the panics stopped. It's been a month since switching from CCM to CBC, still using the aes-aesni module, no panics. I studied the logs of Herbert Xu's crypto tree¹ and couldn't find any activity in the CCM module, or anything related to SG. Like I said I'm probably the only user of this exotic configuration, so should probably close this report. ¹ https://git.kernel.org/cgit/linux/kernel/git/herbert/crypto-2.6.git/log/ -- Gerald Turner Email: gtur...@unzane.com JID: gtur...@unzane.com GPG: 0xFA8CD6D5 21D9 B2E8 7FE7 F19E 5F7D 4D0C 3FA0 810F FA8C D6D5 pgp2AJjBDv2HA.pgp Description: PGP signature
Bug#582975: marked as done (drm/i915: Hangcheck timer elapsed... GPU hung)
Your message dated Mon, 26 Aug 2013 17:01:12 +0200 with message-id <20130826150112.ga25...@inutil.org> and subject line Re: drm/i915: Hangcheck timer elapsed... GPU hung has caused the Debian Bug report #582975, regarding drm/i915: Hangcheck timer elapsed... GPU hung to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 582975: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582975 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.32-13 Severity: important X session appears to hang. Switching to VT still works fine. Switching back to X shows same screen contents from VT. X cursor is drawn and changes depending on window with focus (eg. text cursor over rxvt). Am able to switch between virtual desktops and close apps and WM (awesome) via keyboard shortcuts (deduced by mouse cursor changing and by ps output on VT). KMS is enabled. lspci output below: 00:00.0 Host bridge: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02) 00:00.1 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02) 00:00.3 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02) 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) 00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) 00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01) 00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01) 00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01) 00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 01) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 81) 00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge (rev 01) 00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller (rev 01) 00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 01) 00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01) 00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 01) 02:00.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev 8d) 02:00.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 13) 02:01.0 Ethernet controller: Intel Corporation 82541GI Gigabit Ethernet Controller 02:02.0 Network controller: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05) Let me know if I can provide any more details. -- Package-specific info: ** Version: Linux version 2.6.32-5-686 (Debian 2.6.32-13) (m...@debian.org) (gcc version 4.3.4 (Debian 4.3.4-10) ) #1 SMP Wed May 19 19:51:54 UTC 2010 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 root=UUID=43c39ab8-a297-45d5-a2f6-4fd419c58689 ro quiet ** Not tainted ** Kernel log: [1.617358] hub 3-0:1.0: USB hub found [1.617367] hub 3-0:1.0: 2 ports detected [1.617417] uhci_hcd :00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18 [1.617426] uhci_hcd :00:1d.2: setting latency timer to 64 [1.617430] uhci_hcd :00:1d.2: UHCI Host Controller [1.617439] uhci_hcd :00:1d.2: new USB bus registered, assigned bus number 4 [1.617468] uhci_hcd :00:1d.2: irq 18, io base 0x1860 [1.617505] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001 [1.617509] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [1.617513] usb usb4: Product: UHCI Host Controller [1.617516] usb usb4: Manufacturer: Linux 2.6.32-5-686 uhci_hcd [1.617519] usb usb4: SerialNumber: :00:1d.2 [1.617604] usb usb4: configuration #1 chosen from 1 choice [1.617641] hub 4-0:1.0: USB hub found [1.617649] hub 4-0:1.0: 2 ports detected [1.780378] ata1.00: ATA-5: HITACHI_DK13FA-40B, 00MCA0B4, max UDMA/100 [1.780383] ata1.00: 78140160 sectors, multi 16: LBA [1.790157] ata1.00: configured for UDMA/100 [1.790304] scsi 0:0:0:0: Direct-Access ATA HITACHI_DK13FA-4 00MC PQ: 0 ANSI: 5 [1.799296] e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection [1.801110] sdhci-pci :02:00.1: SDHCI controller found [1180:0822] (rev 13) [1.801130] sdhci-pci :02:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17 [
Bug#587763: marked as done (linux-image-2.6.32-5-amd64: scary messages from JBD when manipulating quotas on ext4)
Your message dated Mon, 26 Aug 2013 17:01:28 +0200 with message-id <20130826150128.gc25...@inutil.org> and subject line Re: linux-image-2.6.32-5-amd64: scary messages from JBD when manipulating quotas on ext4 has caused the Debian Bug report #587763, regarding linux-image-2.6.32-5-amd64: scary messages from JBD when manipulating quotas on ext4 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 587763: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587763 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.32-15 Severity: important Hi, here is how to reproduce this bug: 1. set up quotas on an ext4 filesystem 2. use edquota to change the quotas of some user Actual result: the kernel outputs this scary message: [ 399.792052] JBD: Spotted dirty metadata buffer (dev = sdb1, blocknr = 34816). There's a risk of filesystem corruption in case of system crash. Expected result: - no scary message - no filesystem corruption - changed quotas A patch has been proposed here: http://www.spinics.net/lists/linux-ext4/msg19302.html This bug has also been reported here: https://bugzilla.redhat.com/show_bug.cgi?id=578674 -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-15) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-1) ) #1 SMP Tue Jun 1 04:34:03 UTC 2010 -- System Information: Debian Release: squeeze/sid APT prefers testing-proposed-updates APT policy: (500, 'testing-proposed-updates'), (500, 'testing') Architecture: amd64 (x86_64) -- Laurent Bonnaud. http://www.lis.inpg.fr/pages_perso/bonnaud/ --- End Message --- --- Begin Message --- On Sat, Nov 26, 2011 at 10:29:35PM -0600, Jonathan Nieder wrote: > > Laurent Bonnaud wrote: > > > 1. set up quotas on an ext4 filesystem > > 2. use edquota to change the quotas of some user > > > > Actual result: the kernel outputs this scary message: > [...] > > Expected result: > > - no scary message > > - no filesystem corruption > > - changed quotas > > Robert L Mathews wrote: > > > This bug still exists in squeeze kernel 2.6.32-35squeeze2 (I'm using > > "linux-image-2.6.32-5-amd64 2.6.32-35squeeze2"). > > > > The patch wasn't committed to the upstream kernel until 2.6.35 on July 27, > > 2010: > > > > http://git.strongswan.org/?p=linux-dumm.git;a=commitdiff;h=62d2b5f2dcd3707b070efb16bbfdf6947c38c194 > > Thanks. > > Robert, Laurent, please confirm that this fix works against a squeeze > kernel. Instructions for building and testing a patched kernel are > at [1]. If it works well, we can consider applying it and propose it > for inclusion in the next upstream 2.6.32.y kernel. Closing. This is fixed in Wheezy and we won't backport it to oldstable any more. Cheers, Moritz--- End Message ---
Bug#622325: bus lock still a problem
3.10.8-orion5x root@a110755:~# pwmconfig # pwmconfig revision 5857 (2010-08-22) This program will search your sensors for pulse width modulation (pwm) controls, and test each one to see if it controls a fan on your motherboard. Note that many motherboards do not have pwm circuitry installed, even if your sensor chip supports pwm. We will attempt to briefly stop each fan using the pwm controls. The program will attempt to restore each fan to full speed after testing. However, it is ** very important ** that you physically verify that the fans have been to full speed after the program has completed. Found the following devices: hwmon0/device is g760a hwmon1/device is lm75 Found the following PWM controls: hwmon0/device/pwm1 Giving the fans some time to reach full speed... Found the following fan sensors: hwmon0/device/fan1_input current speed: 6383 RPM Warning!!! This program will stop your fans, one at a time, for approximately 5 seconds each!!! This may cause your processor temperature to rise!!! If you do not want to do this hit control-C now!!! Hit return to continue: Testing pwm control hwmon0/device/pwm1 ... hwmon0/device/fan1_input ... speed was 6383 now 0 It appears that fan hwmon0/device/fan1_input is controlled by pwm hwmon0/device/pwm1 Would you like to generate a detailed correlation (y)? y PWM 255 FAN 6383 PWM 240 FAN 6383 PWM 225 FAN 6383 PWM 210 FAN 6383 PWM 195 FAN 6383 PWM 180 FAN 6383 PWM 165 FAN 6301 PWM 150 FAN 4636 PWM 135 FAN 4096 PWM 120 FAN 3614 PWM 105 FAN 3298 PWM 90 FAN 2978 PWM 75 FAN 2715 PWM 60 FAN 2520 PWM 45 FAN 2329 PWM 30 FAN 2194 PWM 28 FAN 2155 PWM 26 FAN 2137 PWM 24 FAN 2118 PWM 22 FAN 2118 PWM 20 FAN 2100 PWM 18 FAN 2073 PWM 16 FAN 2056 PWM 14 FAN 2048 PWM 12 FAN 2014 PWM 10 FAN 2014 PWM 8 FAN 1981 PWM 6 FAN 1966 PWM 4 FAN 1950 PWM 2 FAN 1935 PWM 0 FAN 0 Fan Stopped at PWM = 0 Testing is complete. On Mon, Aug 26, 2013 at 11:13 AM, Roman Mamedov wrote: > On Mon, 26 Aug 2013 11:06:52 -0400 > Russ H wrote: > > > I compiled a vanilla 3.10.8 kernel on my DNS-323 arm box... still getting > > this bug: > > Hello, > > Did you do a full power-off of your device after running a previous > unpatched > version on it? Because as I found out, booting a bugged kernel even once > locks-up the bus "for good" and merely rebooting the DNS-323 doesn't > restore > access. Try doing a full power-off including disconnecting the power cord > before trying the new kernel. > > (Of course the problem could be something else entirely). > > > > > root@a110755:~# uname -r > > 3.10.8-orion5x > > root@a110755:~# pwmconfig > > # pwmconfig revision 5857 (2010-08-22) > > This program will search your sensors for pulse width modulation (pwm) > > controls, and test each one to see if it controls a fan on > > your motherboard. Note that many motherboards do not have pwm > > circuitry installed, even if your sensor chip supports pwm. > > We will attempt to briefly stop each fan using the pwm controls. > > The program will attempt to restore each fan to full speed > > after testing. However, it is ** very important ** that you > > physically verify that the fans have been to full speed > > after the program has completed. > > Found the following devices: > >hwmon0/device is g760a > > Found the following PWM controls: > >hwmon0/device/pwm1 > > [ 382.279864] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0 > > [ 384.279860] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0 > > [ 386.279861] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0 > > [ 388.279859] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0 > > Giving the fans some time to reach full speed... > > Found the following fan sensors: > > [ 395.349854] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0 > > [ 397.349861] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0 > > [ 399.349853] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0 > >hwmon0/device/fan1_input current speed: 0 ... skipping! > > There are no working fan sensors, all readings are 0. > > Make sure you have a 3-wire fan connected. > > You may also need to increase the fan divisors. > > See doc/fan-divisors for more information. > > > -- > With respect, > Roman >
Bug#622325: bus lock still a problem
On Mon, 26 Aug 2013 11:06:52 -0400 Russ H wrote: > I compiled a vanilla 3.10.8 kernel on my DNS-323 arm box... still getting > this bug: Hello, Did you do a full power-off of your device after running a previous unpatched version on it? Because as I found out, booting a bugged kernel even once locks-up the bus "for good" and merely rebooting the DNS-323 doesn't restore access. Try doing a full power-off including disconnecting the power cord before trying the new kernel. (Of course the problem could be something else entirely). > > root@a110755:~# uname -r > 3.10.8-orion5x > root@a110755:~# pwmconfig > # pwmconfig revision 5857 (2010-08-22) > This program will search your sensors for pulse width modulation (pwm) > controls, and test each one to see if it controls a fan on > your motherboard. Note that many motherboards do not have pwm > circuitry installed, even if your sensor chip supports pwm. > We will attempt to briefly stop each fan using the pwm controls. > The program will attempt to restore each fan to full speed > after testing. However, it is ** very important ** that you > physically verify that the fans have been to full speed > after the program has completed. > Found the following devices: >hwmon0/device is g760a > Found the following PWM controls: >hwmon0/device/pwm1 > [ 382.279864] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0 > [ 384.279860] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0 > [ 386.279861] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0 > [ 388.279859] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0 > Giving the fans some time to reach full speed... > Found the following fan sensors: > [ 395.349854] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0 > [ 397.349861] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0 > [ 399.349853] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0 >hwmon0/device/fan1_input current speed: 0 ... skipping! > There are no working fan sensors, all readings are 0. > Make sure you have a 3-wire fan connected. > You may also need to increase the fan divisors. > See doc/fan-divisors for more information. -- With respect, Roman signature.asc Description: PGP signature
Bug#641906: marked as done (firmware-brcm80211: freezing of system after loading)
Your message dated Mon, 26 Aug 2013 17:01:33 +0200 with message-id <20130826150133.gd25...@inutil.org> and subject line Re: freeze when loading brcm80211 module has caused the Debian Bug report #641906, regarding firmware-brcm80211: freezing of system after loading to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 641906: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641906 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: firmware-brcm80211 Severity: critical Justification: breaks the whole system After installing the firmware packet for BCM4313 (firmware-brcm80211) and reloading the brcm80211 module the system freezes and refuses to boot. On booting, the system freezes somewhere in the init prosess supposably at loading the module or shortly afterwards. Uninstalling the package from recovering mode fixes the problem again, system starts up again. I am using a Eee PC 1215N(BLK041M). -- System Information: Debian Release: 6.0.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-openvz-686 (SMP w/4 CPU cores) Locale: LANG=en_ZW.utf8, LC_CTYPE=en_ZW.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash firmware-brcm80211 depends on no packages. firmware-brcm80211 recommends no packages. Versions of packages firmware-brcm80211 suggests: ii initramfs-tools0.98.8tools for generating an initramfs ii linux-image-2.6.32-5-6 2.6.32-35squeeze2 Linux 2.6.32 for modern PCs ii linux-image-2.6.32-5-o 2.6.32-35squeeze2 Linux 2.6.32 for modern PCs, OpenV --- End Message --- --- Begin Message --- On Thu, Nov 24, 2011 at 06:41:32PM -0600, Jonathan Nieder wrote: > Hi, > > seb wrote: > > > After installing the firmware packet for BCM4313 > > (firmware-brcm80211) and reloading the brcm80211 module the system > > freezes and refuses to boot. > > > > On booting, the system freezes somewhere in the init prosess > > supposably at loading the module or shortly afterwards. > > > > Uninstalling the package from recovering mode fixes the problem > > again, system starts up again. > > Thanks. Please attach output from "reportbug --template > linux-image-$(uname -r)", so we can get to know your hardware better. > Please also attach console messages from loading the module in > recovery mode, as obtained with netconsole[1], serial console[2], or a > digital camera. > > Is this a regression, or is this the first time you've tried this? > > Hope that helps, > Jonathan > > [1] http://www.kernel.org/doc/Documentation/networking/netconsole.txt > [2] http://www.kernel.org/doc/Documentation/serial-console.txt No further feedback, closing the bug. Cheers, Moritz--- End Message ---
Bug#648310: marked as done (pegasus: Pegasus driver in kernel 3.0.0-1-amd64 fails when using USB network adapter.)
Your message dated Mon, 26 Aug 2013 17:01:19 +0200 with message-id <20130826150119.gb25...@inutil.org> and subject line Re: linux-image-2.6.32-5-486: Driver pegasus freeze networking very often so one must reboot to get it to work again has caused the Debian Bug report #586289, regarding pegasus: Pegasus driver in kernel 3.0.0-1-amd64 fails when using USB network adapter. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 586289: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586289 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 3.0.0-3 Severity: grave File: pegasus Justification: renders package unusable Please see fault in dmesg: pegasus 4-1:1.0: eth3: update_eth_regs_async, status -22 Utilizing USB network adapter listed as follows: 07a6:0986 ADMtek, Inc. AN986 Pegasus Ethernet ifconfig, ethtool, etc allow configuration of the device but no data will actually pass through it. I turned down the other ethernet adapters on the machine and was unable to ping past the first directly connected host to the Pegasus adapter. -- Package-specific info: ** Version: Linux version 3.0.0-1-amd64 (Debian 3.0.0-3) (b...@decadent.org.uk) (gcc version 4.5.3 (Debian 4.5.3-8) ) #1 SMP Sat Aug 27 16:21:11 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.0.0-1-amd64 root=UUID=58ebd269-072a-4ff9-91e5-590efa23f4db ro quiet ** Not tainted ** Kernel log: [4.241765] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [4.241767] [drm] Driver supports precise vblank timestamp query. [4.241778] [drm] radeon: irq initialized. [4.241784] mtrr: type mismatch for f000,800 old: write-back new: write-combining [4.241787] [drm] Detected VRAM RAM=128M, BAR=128M [4.241789] [drm] RAM width 128bits DDR [4.241851] [TTM] Zone kernel: Available graphics memory: 4034950 kiB. [4.241853] [TTM] Zone dma32: Available graphics memory: 2097152 kiB. [4.241855] [TTM] Initializing pool allocator. [4.241883] [drm] radeon: 128M of VRAM memory ready [4.241886] [drm] radeon: 512M of GTT memory ready. [4.241904] [drm] GART: num cpu pages 131072, num gpu pages 131072 [4.245780] [drm] radeon: 1 quad pipes, 1 z pipes initialized. [4.252865] radeon :01:05.0: WB enabled [4.253252] [drm] Loading RS690/RS740 Microcode [4.341491] [drm] radeon: ring at 0xA0001000 [4.341510] [drm] ring test succeeded in 1 usecs [4.341662] [drm] radeon: ib pool ready. [4.341736] [drm] ib test succeeded in 0 usecs [4.341783] failed to evaluate ATIF got AE_BAD_PARAMETER [4.342045] [drm] Radeon Display Connectors [4.342047] [drm] Connector 0: [4.342048] [drm] VGA [4.342051] [drm] DDC: 0x7e50 0x7e40 0x7e54 0x7e44 0x7e58 0x7e48 0x7e5c 0x7e4c [4.342053] [drm] Encoders: [4.342055] [drm] CRT1: INTERNAL_KLDSCP_DAC1 [4.342057] [drm] Connector 1: [4.342058] [drm] S-video [4.342059] [drm] Encoders: [4.342061] [drm] TV1: INTERNAL_KLDSCP_DAC1 [4.342063] [drm] Connector 2: [4.342064] [drm] HDMI-A [4.342067] [drm] DDC: 0x7e40 0x7e50 0x7e44 0x7e54 0x7e48 0x7e58 0x7e4c 0x7e5c [4.342069] [drm] Encoders: [4.342070] [drm] DFP3: INTERNAL_LVTM1 [4.393126] [drm] Radeon display connector VGA-1: Found valid EDID [4.402631] [drm] Radeon display connector HDMI-A-1: No monitor connected or invalid EDID [4.555138] [drm] fb mappable at 0xF004 [4.555141] [drm] vram apper at 0xF000 [4.555143] [drm] size 5242880 [4.555145] [drm] fb depth is 24 [4.555146] [drm]pitch is 5120 [4.555232] fbcon: radeondrmfb (fb0) is primary device [4.582047] Console: switching to colour frame buffer device 160x64 [4.591920] fb0: radeondrmfb frame buffer device [4.591922] drm: registered panic notifier [4.591928] [drm] Initialized radeon 2.10.0 20080528 for :01:05.0 on minor 0 [4.592732] HDA Intel :01:05.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19 [4.592799] HDA Intel :01:05.2: irq 42 for MSI/MSI-X [7.620009] hda-intel: azx_get_response timeout, switching to polling mode: last cmd=0x000f [8.624010] hda-intel: No response from codec, disabling MSI: last cmd=0x000f [9.628012] hda-intel: Codec #0 probe error; disabling it... [ 11.772009] hda_intel: azx_get_response timeout, switching to single_cmd mode: last cmd=0x00070503 [ 12.219260] Adding 4882428k swap on /dev/sda2. Priority:-1 extents:1 across:4882428k [ 12.224843] EXT4-fs (sda1): re-mounted. Opts: (null) [ 12.5
Bug#586289: marked as done (linux-image-2.6.32-5-486: Driver pegasus freeze networking very often so one must reboot to get it to work again)
Your message dated Mon, 26 Aug 2013 17:01:19 +0200 with message-id <20130826150119.gb25...@inutil.org> and subject line Re: linux-image-2.6.32-5-486: Driver pegasus freeze networking very often so one must reboot to get it to work again has caused the Debian Bug report #586289, regarding linux-image-2.6.32-5-486: Driver pegasus freeze networking very often so one must reboot to get it to work again to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 586289: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586289 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.32-15 Severity: grave Tags: squeeze Justification: renders package unusable Hi, the driver pegasus freeze networking very often so one must to reboot to get networking work again. At reboot the system hang and one can see a message like: [5952.880465] pegasus 1-1:1.0: update_eth_regs_async, status -22 At this point one must press the Reset button of the PC Box because the system hangs forever. -- Package-specific info: ** Version: Linux version 2.6.32-5-486 (Debian 2.6.32-15) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-1) ) #1 Tue Jun 1 04:27:25 UTC 2010 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-486 root=UUID=127a8e72-b9d4-4a28-8aa9-e6cdcb3985c9 ro all_generic_ide quiet ** Not tainted ** Kernel log: [7.386866] ohci_hcd :00:0b.0: power state changed by ACPI to D0 [7.391599] ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11 [7.391636] ohci_hcd :00:0b.0: PCI INT A -> Link[LNKD] -> GSI 11 (level, low) -> IRQ 11 [7.391792] ohci_hcd :00:0b.0: OHCI Host Controller [7.391994] ohci_hcd :00:0b.0: new USB bus registered, assigned bus number 1 [7.392242] ohci_hcd :00:0b.0: irq 11, io mem 0xf7fff000 [7.957294] usb usb1: New USB device found, idVendor=1d6b, idProduct=0001 [7.957323] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [7.957344] usb usb1: Product: OHCI Host Controller [7.957362] usb usb1: Manufacturer: Linux 2.6.32-5-486 ohci_hcd [7.957380] usb usb1: SerialNumber: :00:0b.0 [7.958819] usb usb1: configuration #1 chosen from 1 choice [7.959658] hub 1-0:1.0: USB hub found [7.959803] hub 1-0:1.0: 2 ports detected [9.469598] PM: Starting manual resume from disk [9.469635] PM: Resume from partition 8:8 [9.469648] PM: Checking hibernation image. [9.495441] PM: Error -22 checking image file [9.495458] PM: Resume from disk failed. [9.683653] EXT3-fs: INFO: recovery required on readonly filesystem. [9.683682] EXT3-fs: write access will be enabled during recovery. [ 10.019741] kjournald starting. Commit interval 5 seconds [ 10.019839] EXT3-fs: recovery complete. [ 10.038103] EXT3-fs: mounted filesystem with ordered data mode. [ 14.275485] udev: starting version 157 [ 16.300368] Marking TSC unstable due to TSC halts in idle [ 16.301500] processor LNXCPU:00: registered as cooling_device1 [ 16.344132] Switching to clocksource acpi_pm [ 16.682421] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1 [ 16.682917] ACPI: Lid Switch [LID] [ 16.683650] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 [ 16.683697] ACPI: Power Button [PWRF] [ 16.735214] input: PC Speaker as /devices/platform/pcspkr/input/input3 [ 16.854916] psmouse serio1: ID: 12 02 3c [ 16.916017] ACPI: Battery Slot [MBAT] (battery absent) [ 17.086489] ACPI: AC Adapter [ADP1] (on-line) [ 17.582986] input: PS/2 Generic Mouse as /devices/platform/i8042/serio1/input/input4 [ 17.912789] NET: Registered protocol family 23 [ 17.941369] yenta_cardbus :00:13.0: CardBus bridge found [1179:0001] [ 17.950140] toshiba_acpi: Toshiba Laptop ACPI Extras version 0.19 [ 17.950167] toshiba_acpi: HCI method: \_SB_.VALD.GHCI [ 18.071396] yenta_cardbus :00:13.0: ISA IRQ mask 0x06b8, PCI irq 11 [ 18.071425] yenta_cardbus :00:13.0: Socket status: 3007 [ 18.083845] parport_pc 00:0b: reported by Plug and Play ACPI [ 18.083954] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE] [ 18.085976] yenta_cardbus :00:13.1: CardBus bridge found [1179:0001] [ 18.213173] yenta_cardbus :00:13.1: ISA IRQ mask 0x0638, PCI irq 11 [ 18.213203] yenta_cardbus :00:13.1: Socket status: 3007 [ 18.569373] donauboe :00:11.0: power state changed by ACPI to D0 [ 18.570090] donauboe :00:11.0: power state changed by ACPI to D0 [ 18.586984] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11 [
Bug#622325: bus lock still a problem
I compiled a vanilla 3.10.8 kernel on my DNS-323 arm box... still getting this bug: root@a110755:~# uname -r 3.10.8-orion5x root@a110755:~# pwmconfig # pwmconfig revision 5857 (2010-08-22) This program will search your sensors for pulse width modulation (pwm) controls, and test each one to see if it controls a fan on your motherboard. Note that many motherboards do not have pwm circuitry installed, even if your sensor chip supports pwm. We will attempt to briefly stop each fan using the pwm controls. The program will attempt to restore each fan to full speed after testing. However, it is ** very important ** that you physically verify that the fans have been to full speed after the program has completed. Found the following devices: hwmon0/device is g760a Found the following PWM controls: hwmon0/device/pwm1 [ 382.279864] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0 [ 384.279860] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0 [ 386.279861] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0 [ 388.279859] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0 Giving the fans some time to reach full speed... Found the following fan sensors: [ 395.349854] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0 [ 397.349861] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0 [ 399.349853] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0 hwmon0/device/fan1_input current speed: 0 ... skipping! There are no working fan sensors, all readings are 0. Make sure you have a 3-wire fan connected. You may also need to increase the fan divisors. See doc/fan-divisors for more information.
Bug#720926: i915: task Xorg blocked for more than 120 seconds.
Package: src:linux Version: 3.10.7-1 Severity: normal Dear Maintainer, I have a relatively reproducible (~60% probability) freeze problem, which happens when the system is loaded. I can reproduce it as follow: - Boot and log into a e17 session with OpenGL compositing enabled. - Do a parallel compilation of several large C++ programs while doing other work. The system becomes frozen; mouse and keyboard (including leds) do not respond. I have booted the machine with kernel logging on serial enabled and eventually saw a kernel stacktrace about Xorg being stuck in a lock. While researching the problem, the system apparently self-recovered and become usable again. xserver-xorg-video-intel's version is 2:2.21.14-4 and xserver-xorg-core's version is 2:1.12.4-6.1. Detail about this specific boot: - VirtualBox was not used. - I Issued SysRq S and SysRq T (dump state), but T is apparently disabled by default. - I Unplugged the network cable during the crash (this is not a driver bug). - Xorg.log shows no error. i915_error_state says "no error state collected". -- Package-specific info: ** Version: Linux version 3.10-2-amd64 (debian-kernel@lists.debian.org) (gcc version 4.7.3 (Debian 4.7.3-6) ) #1 SMP Debian 3.10.7-1 (2013-08-17) ** Command line: BOOT_IMAGE=/vmlinuz-3.10-2-amd64 root=/dev/mapper/evilbit-root ro console=ttyS0,115200 ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [ 205.097386] SysRq : Emergency Sync [ 205.698053] SysRq : Emergency Sync [ 206.030619] SysRq : Emergency Sync [ 206.292625] SysRq : Emergency Sync [ 207.024009] SysRq : This sysrq operation is disabled. [ 256.309865] Emergency Sync complete [ 256.313368] Emergency Sync complete [ 256.318152] Emergency Sync complete [ 256.321830] Emergency Sync complete [ 361.647572] INFO: task Xorg:2911 blocked for more than 120 seconds. [ 361.653860] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 361.661710] XorgD 880212499880 0 2911 2903 0x0044 [ 361.668804] 880212499880 3082 880214a04100 00013f40 [ 361.676272] 880213cfffd8 880213cfffd8 880212499880 88021e213f40 [ 361.683737] 880212499880 880213cffb30 810c03e7 0002 [ 361.691201] Call Trace: [ 361.693661] [] ? __lock_page+0x61/0x61 [ 361.699080] [] ? io_schedule+0x54/0x69 [ 361.704507] [] ? sleep_on_page+0x5/0x8 [ 361.709920] [] ? __wait_on_bit+0x3b/0x6e [ 361.715506] [] ? wait_on_page_bit+0x69/0x6e [ 361.721357] [] ? autoremove_wake_function+0x2a/0x2a [ 361.727904] [] ? shmem_getpage_gfp+0x20d/0x5c5 [ 361.734016] [] ? shmem_read_mapping_page_gfp+0x26/0x41 [ 361.740836] [] ? i915_gem_object_get_pages_gtt+0xdf/0x2d1 [i915] [ 361.748512] [] ? kmem_cache_free+0x3f/0x7c [ 361.754280] [] ? i915_gem_object_get_pages+0x53/0x87 [i915] [ 361.761528] [] ? i915_gem_object_pin+0x19c/0x4f9 [i915] [ 361.768424] [] ? i915_gem_wait_for_error+0x17/0x147 [i915] [ 361.775582] [] ? i915_gem_fault+0xc6/0x1fa [i915] [ 361.781953] [] ? __do_fault+0xcb/0x3aa [ 361.787366] [] ? i915_gem_set_domain_ioctl+0x190/0x1b3 [i915] [ 361.794782] [] ? handle_pte_fault+0x2c5/0x7a7 [ 361.800800] [] ? handle_mm_fault+0x1f1/0x238 [ 361.806733] [] ? __do_page_fault+0x383/0x3cb [ 361.812666] [] ? vfs_ioctl+0x1b/0x25 [ 361.817901] [] ? do_vfs_ioctl+0x3e8/0x42a [ 361.823571] [] ? vfs_read+0xa9/0xef [ 361.828720] [] ? SyS_read+0x74/0x8b [ 361.833867] [] ? page_fault+0x28/0x30 [ 481.889334] INFO: task Xorg:2911 blocked for more than 120 seconds. [ 481.895616] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 481.903458] XorgD 880212499880 0 2911 2903 0x0044 [ 481.910544] 880212499880 3082 880214a04100 00013f40 [ 481.918006] 880213cfffd8 880213cfffd8 880212499880 88021e213f40 [ 481.925464] 880212499880 880213cffb30 810c03e7 0002 [ 481.932915] Call Trace: [ 481.935374] [] ? __lock_page+0x61/0x61 [ 481.940782] [] ? io_schedule+0x54/0x69 [ 481.946199] [] ? sleep_on_page+0x5/0x8 [ 481.951603] [] ? __wait_on_bit+0x3b/0x6e [ 481.957183] [] ? wait_on_page_bit+0x69/0x6e [ 481.963026] [] ? autoremove_wake_function+0x2a/0x2a [ 481.969565] [] ? shmem_getpage_gfp+0x20d/0x5c5 [ 481.975668] [] ? shmem_read_mapping_page_gfp+0x26/0x41 [ 481.982478] [] ? i915_gem_object_get_pages_gtt+0xdf/0x2d1 [i915] [ 481.990147] [] ? kmem_cache_free+0x3f/0x7c [ 481.995906] [] ? i915_gem_object_get_pages+0x53/0x87 [i915] [ 482.003142] [] ? i915_gem_object_pin+0x19c/0x4f9 [i915] [ 482.010030] [] ? i915_gem_wait_for_error+0x17/0x147 [i915] [ 482.017181] [] ? i915_gem_fault+0xc6/0x1fa [i915] [ 482.023542] [] ? __do_fault+0xcb/0x3aa [ 482.028952] [] ? i915_gem_set_domain_ioctl+0x190/0x1b3 [i915] [ 482.036357] [] ? handle_pte_fault+0x2c5/0x7a7 [ 482.042370] [] ? handl
[PATCH] udebs for armmp flavour
I think this is fairly uncontroversial but I'll give people some time to object/comment. I've built a netboot installer image and run through it on a Calxeda system. There are some other d-i things needed (bootloader support, kernel selection) before that is really useful out of the box. commit cb01ae767eb63c196318635003e8516265ed30b5 Author: Ian Campbell Date: Mon Aug 26 11:11:15 2013 +0100 Add udebs for armmp flavour Based on the mx5 and vexpress lists, plus some manual tweaking. diff --git a/linux/debian/changelog b/linux/debian/changelog index c58006f..9b104a3 100644 --- a/linux/debian/changelog +++ b/linux/debian/changelog @@ -24,6 +24,9 @@ linux (3.11~rc5-1~exp1) UNRELEASED; urgency=low * Update Brazilian Portugese debconf template translations (Fernando Ike de Oliveira) (Closes: #719725) + [ Ian Campbell ] + * armhf: Add udebs for armmp flavour + -- Ben Hutchings Sun, 11 Aug 2013 19:34:47 +0200 linux (3.11~rc4-1~exp1) experimental; urgency=low diff --git a/linux/debian/installer/armhf/kernel-versions b/linux/debian/installer/armhf/kernel-versions index cf3465a..55b5ade 100644 --- a/linux/debian/installer/armhf/kernel-versions +++ b/linux/debian/installer/armhf/kernel-versions @@ -1,3 +1,4 @@ # arch version flavour installedname suffix build-depends +armhf - armmp- y - armhf - mx5 - y - armhf - vexpress - y - diff --git a/linux/debian/installer/armhf/modules/armhf-armmp/ata-modules b/linux/debian/installer/armhf/modules/armhf-armmp/ata-modules new file mode 100644 index 000..04d9c88 --- /dev/null +++ b/linux/debian/installer/armhf/modules/armhf-armmp/ata-modules @@ -0,0 +1 @@ +libata diff --git a/linux/debian/installer/armhf/modules/armhf-armmp/btrfs-modules b/linux/debian/installer/armhf/modules/armhf-armmp/btrfs-modules new file mode 100644 index 000..e261e13 --- /dev/null +++ b/linux/debian/installer/armhf/modules/armhf-armmp/btrfs-modules @@ -0,0 +1 @@ +#include diff --git a/linux/debian/installer/armhf/modules/armhf-armmp/core-modules b/linux/debian/installer/armhf/modules/armhf-armmp/core-modules new file mode 100644 index 000..f05d062 --- /dev/null +++ b/linux/debian/installer/armhf/modules/armhf-armmp/core-modules @@ -0,0 +1 @@ +#include diff --git a/linux/debian/installer/armhf/modules/armhf-armmp/crc-modules b/linux/debian/installer/armhf/modules/armhf-armmp/crc-modules new file mode 100644 index 000..7e00de7 --- /dev/null +++ b/linux/debian/installer/armhf/modules/armhf-armmp/crc-modules @@ -0,0 +1 @@ +#include diff --git a/linux/debian/installer/armhf/modules/armhf-armmp/crypto-dm-modules b/linux/debian/installer/armhf/modules/armhf-armmp/crypto-dm-modules new file mode 100644 index 000..4c8f235 --- /dev/null +++ b/linux/debian/installer/armhf/modules/armhf-armmp/crypto-dm-modules @@ -0,0 +1 @@ +#include diff --git a/linux/debian/installer/armhf/modules/armhf-armmp/crypto-modules b/linux/debian/installer/armhf/modules/armhf-armmp/crypto-modules new file mode 100644 index 000..3a1e862 --- /dev/null +++ b/linux/debian/installer/armhf/modules/armhf-armmp/crypto-modules @@ -0,0 +1 @@ +#include diff --git a/linux/debian/installer/armhf/modules/armhf-armmp/event-modules b/linux/debian/installer/armhf/modules/armhf-armmp/event-modules new file mode 100644 index 000..f8819af --- /dev/null +++ b/linux/debian/installer/armhf/modules/armhf-armmp/event-modules @@ -0,0 +1 @@ +#include diff --git a/linux/debian/installer/armhf/modules/armhf-armmp/ext2-modules b/linux/debian/installer/armhf/modules/armhf-armmp/ext2-modules new file mode 100644 index 000..c407140 --- /dev/null +++ b/linux/debian/installer/armhf/modules/armhf-armmp/ext2-modules @@ -0,0 +1 @@ +#include diff --git a/linux/debian/installer/armhf/modules/armhf-armmp/ext3-modules b/linux/debian/installer/armhf/modules/armhf-armmp/ext3-modules new file mode 100644 index 000..bbdd7f4 --- /dev/null +++ b/linux/debian/installer/armhf/modules/armhf-armmp/ext3-modules @@ -0,0 +1 @@ +#include diff --git a/linux/debian/installer/armhf/modules/armhf-armmp/ext4-modules b/linux/debian/installer/armhf/modules/armhf-armmp/ext4-modules new file mode 100644 index 000..394c577 --- /dev/null +++ b/linux/debian/installer/armhf/modules/armhf-armmp/ext4-modules @@ -0,0 +1 @@ +#include diff --git a/linux/debian/installer/armhf/modules/armhf-armmp/fat-modules b/linux/debian/installer/armhf/modules/armhf-armmp/fat-modules new file mode 100644 index 000..274584e --- /dev/null +++ b/linux/debian/installer/armhf/modules/armhf-armmp/fat-modules @@ -0,0 +1 @@ +#include diff --git a/linux/debian/installer/armhf/modules/armhf-armmp/fuse-modules b/linux/debian/installer/armhf/modules/armhf-armmp/fuse-modules new file mode 100644 index 000..0b6ba0c --- /dev/null +++ b/linux/debian/installer/armhf/modules/armhf-armmp/fuse-modules @@ -0,0 +1 @@ +#include diff --git a/linux/debian/ins
Bug#720743: marked as done ([firmware-brcm80211] the firmware crashes kernel-3.10.9)
Your message dated Mon, 26 Aug 2013 11:18:55 +0100 with message-id <1377512335.16071.16.ca...@deadeye.wl.decadent.org.uk> and subject line Re: Bug#720743: [firmware-brcm80211] the firmware crashes kernel-3.10.9 has caused the Debian Bug report #720743, regarding [firmware-brcm80211] the firmware crashes kernel-3.10.9 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 720743: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720743 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: firmware-brcm80211 Version: 0.39~bpo70+1 Severity: normal --- Please enter the report below this line. --- The last firmware provided in unstable (should be 0.40) doesn't work with my 3.8.13 custom kernel, and what is worse, causes kernel opses in my custom 3.10.9 kernel locking it totally. Reverting to any previous version down to the one present in wheezy at least allows to connect with kernel 3.8.13, but all of them crashes the kernel 3.10.9. Best regards Valerio --- System information. --- Architecture: amd64 Kernel: Linux 3.8.13 Debian Release: jessie/sid 990 unstablemi.mirror.garr.it 990 unstableftp.uk.debian.org 990 unstableftp.it.debian.org 500 wheezy activsoftware.co.uk 500 testing mi.mirror.garr.it 500 testing ftp.uk.debian.org 500 stable deb.opera.com 1 experimentalmi.mirror.garr.it 1 experimentalftp.uk.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Suggests (Version) | Installed ==-+-=== initramfs-tools| 0.113 linux-image| Valerio --- End Message --- --- Begin Message --- On Sun, 2013-08-25 at 02:56 +0200, Valerio Passini wrote: > Package: firmware-brcm80211 > Version: 0.39~bpo70+1 > Severity: normal > > --- Please enter the report below this line. --- > The last firmware provided in unstable (should be 0.40) doesn't work with my > 3.8.13 custom kernel, and what is worse, causes kernel opses in my custom > 3.10.9 kernel locking it totally. Reverting to any previous version down to > the one present in wheezy at least allows to connect with kernel 3.8.13, but > all of them crashes the kernel 3.10.9. This is a driver bug, and you aren't using a Debian kernel so this isn't our bug. Ben. -- Ben Hutchings This sentence contradicts itself - no actually it doesn't. signature.asc Description: This is a digitally signed message part --- End Message ---
