Bug 819561
Summary: | [abrt]: WARNING: at drivers/net/wireless/brcm80211/brcmsmac/main.c:8006 brcms_c_wait_for_tx_completion+0x99/0xb0 [brcmsmac]() | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | kopano.fedora | ||||
Component: | kernel | Assignee: | John W. Linville <linville> | ||||
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 17 | CC: | allinux4, arend, atef.live, balamahendran, battleman2004, gansalmon, gremaud.benoit, itamar, jeverhart, johannbg, jonathan, kernel-maint, klic, madhu.chinakonda, marcosmds, matthew.hooper, pahan, pi_raph, sanjay.ankur, thuforuk | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2012-07-09 20:33:11 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
kopano.fedora
2012-05-07 14:27:51 UTC
Balancing after removing a device Package: kernel Architecture: i686 OS Release: Fedora release 17 (Beefy Miracle) (In reply to comment #1) > Balancing after removing a device > > Package: kernel > Architecture: i686 > OS Release: Fedora release 17 (Beefy Miracle) To clarify, as this isn't a btrfs related bug, I was balancing a btrfs file system after removing a missing device and abrt posted to this bug. I'll attach my abrt data just in case it proves useful. Kernel: 3.4.0-0.rc5.git5.1.fc18.i686 Created attachment 583949 [details]
abrt data
Booting up Package: kernel OS Release: Fedora release 17 (Beefy Miracle) Resumed from sleep. Package: kernel OS Release: Fedora release 17 (Beefy Miracle) Happens a few times a day in F17. It seems to be graphics driver issue for me - I'm using an opensource driver. Everything worked fine in F16 and 12.04 with Catalyst. My graphics card is HD 6550D on A8-3870K. Package: kernel OS Release: Fedora release 17 (Beefy Miracle) Installed a plain Fedora 16 installation. Upgraded to Fedora 17 beta using preupgrade. The upgrade went smoothly but this message was waiting in abrt upon the first boot of F17. Package: kernel Architecture: i686 OS Release: Fedora release 17 (Beefy Miracle) Fresh install on virtualbox, first time boot Package: kernel Architecture: i686 OS Release: Fedora release 17 (Beefy Miracle) I do not know what caused the problem, everything seems fine with my wireless connection (I am using it to make this report). However, bluetoth is not working. Checking system configuration applet shows no adapter. But lsusb | grep -i blue Bus 002 Device 004: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) Package: kernel OS Release: Fedora release 17 (Beefy Miracle) Just installed Fedora 17 and don't understand anything. Package: kernel OS Release: Fedora release 17 (Beefy Miracle) Error happens Everytime at boot Package: kernel OS Release: Fedora release 17 (Beefy Miracle) Turned on the laptop, when gnome shell came up - the ABRT was there waiting. No user impact at all - everything works, but this report comes up. Sorry I don't have more information. Package: kernel OS Release: Fedora release 17 (Beefy Miracle) I believe this problem happens when my external hard disk is connected to my computer. It is a usb3.0 connector and has a btrfs partition in it. Package: kernel OS Release: Fedora release 17 (Beefy Miracle) 点击左上角活动时,几秒钟未响应 Package: kernel OS Release: Fedora release 17 (Beefy Miracle) Updating Fedora 17 on June 2nd and the error report came up in the middle of the update process. Package: kernel OS Release: Fedora release 17 (Beefy Miracle) Appeared as soon as the KDE GUI started. Obviously occurred during the boot process. Package: kernel OS Release: Fedora release 17 (Beefy Miracle) system crashes soon after login to gnome Package: kernel OS Release: Fedora release 17 (Beefy Miracle) This incidence occured while I was doing nothing but waiting for the first "software update" to finish. Package: kernel OS Release: Fedora release 17 (Beefy Miracle) About comment 9 Bluetooth is ok now. I have to install the other bluez*.rpm. I do not know the reason but Anaconda installed just a part of the bluez*.rpm. After installing the other packages, bluetooth turned alive. It follows the packages I installed to fix the problem. bluez-gstreamer-4.99-1.fc17.x86_64 bluez-hid2hci-4.99-1.fc17.x86_64 bluez-alsa-4.99-1.fc17.x86_64 bluez-compat-4.99-1.fc17.x86_64 bluez-hcidump-2.2-2.fc17.x86_64 I guess bluez-hid2hci and bluez-hcidump did the magic. i was running an update in the backround and viewing a website i have just recently installed this system on an old acer aspire netbook and i tryed to update this computer in live mode because it wouldnt start after i ran an update it ran out of memory and then the anaconda installer started working Package: kernel OS Release: Fedora release 17 (Beefy Miracle) When fetching a signature from a "signotec sigma" signature table. Somewhat reproducible by doing this 30-50 times in a row. Package: kernel Architecture: i686 OS Release: Fedora release 17 (Beefy Miracle) (In reply to comment #21) > When fetching a signature from a "signotec sigma" signature table. Somewhat > reproducible by doing this 30-50 times in a row. > > Package: kernel > Architecture: i686 > OS Release: Fedora release 17 (Beefy Miracle) No idea why abrt appended to this bug GDM login screen came up; I selected user, pressed enter, and X locked up partway into the 'expose the password box' animation. Package: kernel OS Release: Fedora release 17 (Beefy Miracle) fresh installed f 17 after yum update i got this Package: kernel OS Release: Fedora release 17 (Beefy Miracle) was starting the system Package: kernel Architecture: i686 OS Release: Fedora release 17 (Beefy Miracle) This is a new install fresh with a new format/partition, the crash happened at some point during the bootup process. At the point of logging into the desktop, ABRT was ready to report this. All packages are up to date as of this morning. Package: kernel Architecture: i686 OS Release: Fedora release 17 (Beefy Miracle) After the last hibernation? I don't know Package: kernel OS Release: Fedora release 17 (Beefy Miracle) This error occurs during boot on F17 for both Desktop and KDE Spins on the below hardware, does not occur at all on my laptop with an AMD A8-3520 APU chipset. System will boot into GNOME with a highly degraded boot time, however will not boot at all in KDE. Hardware of error: Acer Aspire 6930 w/Intel G45M chipset How to reproduce: Occurs on every boot, displayed on boot messages Expected Result: To boot without CPU getting stuck to decrease boot time in GNOME, make system bootable in KDE. I am providing all info ABRT is prompting, however if any further details are needed, please let me know. Package: kernel OS Release: Fedora release 17 (Beefy Miracle) I was attempting a reboot and this well known bug reared it's head. Sometimes I still get bugchecks, but it is not related to this issue. I am submitting this to make sure that I am assuming correctly. -l0ft1369 Package: kernel Architecture: i686 OS Release: Fedora release 17 (Beefy Miracle) I was trying to connect to an other wireless network (one with different conficuration and more secure). Package: kernel OS Release: Fedora release 17 (Beefy Miracle) I sometimes also get a "ieee80211 phy16: brcms_c_ampdu_dotxstatus_complete: Pkt tx suppressed, illegal channel possibly " counting channel(?) numbers. Only way to get the network running again is unloading and reloading the brcmsmac module again. Is this related, or should I add another BZ? (F17 up to date) started a skype call Package: kernel OS Release: Fedora release 17 (Beefy Miracle) When system booting. Package: kernel OS Release: Fedora release 17 (Beefy Miracle) Occur at boot of system Package: kernel OS Release: Fedora release 17 (Beefy Miracle) No idea. Just found this in the reports. Package: kernel OS Release: Fedora release 17 (Beefy Miracle) The error appears after loggin in Package: kernel Architecture: i686 OS Release: Fedora release 17 (Beefy Miracle) was starting fedora Package: kernel Architecture: i686 OS Release: Fedora release 17 (Beefy Miracle) What happened before: This happened after I closed firefox running in selinux sandbox. The sandbox was created with vpnc session active, while it was closed when vpnc was already disconnected. Reproducibility: Knock, knock, knock, it is not reproducible (so far.) Package: kernel OS Release: Fedora release 17 (Beefy Miracle) (In reply to comment #38) > What happened before: > This happened after I closed firefox running in selinux sandbox. > The sandbox was created with vpnc session active, while it was closed when > vpnc was already disconnected. > > Reproducibility: > Knock, knock, knock, it is not reproducible (so far.) > > > Package: kernel > OS Release: Fedora release 17 (Beefy Miracle) Ignore this comment. It is not a duplicate but unrelated issue: Bug 831194. Likely a bug in abrt: Bug 831197. Package: kernel OS Release: Fedora release 17 (Beefy Miracle) This happened (and has happened before) when the system would either be going into 'suspend' mode due to inactivity, to into 'suspend' with the closing of the cover of this netbook. Package: kernel OS Release: Fedora release 17 (Beefy Miracle) Just boot. Package: kernel OS Release: Fedora release 17 (Beefy Miracle) Ao iniciar o sistema, na tela de carregamento onde aparece o logotipo sendo preenchido foi informado esse erro. Package: kernel OS Release: Fedora release 17 (Beefy Miracle) I was using Fedora 17 64-bit with KDE 4.8.3. I logged out and logged in again. Abrt brought up this ooops. This *may* be the first time I actually managed to capture soemthing that I have been observing for the week since I built this new computer: every few hours the machine freezes without any warning and without any logs in anywhwere I can find. What happens is that on two monitor setup, the primary monitor blanks to black, mouse pointer freezes, secondary monitor keeps displaying last image and the machine is just dead, not responding to anything (keyboard -- caps/num lock don't light the LED, network is cut off -- external ssh sessions die). The only way out is reset button. This time I got this ooops during login and no freeze so I hope this report may help fixing the crashes. Package: kernel OS Release: Fedora release 17 (Beefy Miracle) This seems to be related to Ivy Bridge GPU (i7-3770K): WARNING: at drivers/gpu/drm/i915/i915_irq.c:535 ivybridge_irq_handler+0x362/0x370 [i915]() Hardware name: System Product Name Missed a PM interrupt Modules linked in: xts gf128mul dm_crypt hidp fuse lockd sunrpc rfcomm bnep ebtable_nat ebtables ipt_MASQUERADE iptable_nat nf_nat xt_CHECKSUM iptable_mangle bridge stp llc nf_conntrack_ipv4 nf_defrag_ipv4 ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 xt_state nf_conntrack ip6table_filter be2iscsi iscsi_boot_sysfs ip6_tables bnx2i cnic uio cxgb4i cxgb4 cxgb3i cxgb3 mdio libcxgbi ib_iser rdma_cm ib_addr iw_cm ib_cm ib_sa ib_mad ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek eeepc_wmi asus_wmi sparse_keymap coretemp microcode btusb bluetooth rfkill vhost_net tun macvtap macvlan i2c_i801 kvm iTCO_wdt iTCO_vendor_support uinput snd_hda_intel r8169 snd_hda_codec mii snd_hwdep snd_pcm snd_page_alloc snd_timer snd soundcore crc32c_intel ghash_clmulni_intel wmi usb_storage i915 video i2c_algo_bit drm_kms_helper drm i2c_core [last unloaded: scsi_wait_scan] Pid: 0, comm: swapper/6 Not tainted 3.4.0-1.fc17.x86_64 #1 Call Trace: <IRQ> [<ffffffff8105681f>] warn_slowpath_common+0x7f/0xc0 [<ffffffff81056916>] warn_slowpath_fmt+0x46/0x50 [<ffffffffa0071c62>] ivybridge_irq_handler+0x362/0x370 [i915] [<ffffffff810df8a4>] handle_irq_event_percpu+0x54/0x200 [<ffffffff810dfa91>] handle_irq_event+0x41/0x70 [<ffffffff810e234f>] handle_edge_irq+0x6f/0x110 [<ffffffff810150ef>] handle_irq+0xbf/0x150 [<ffffffff815f48d2>] ? __atomic_notifier_call_chain+0x12/0x20 [<ffffffff815f48f6>] ? atomic_notifier_call_chain+0x16/0x20 [<ffffffff815fa72a>] do_IRQ+0x5a/0xe0 [<ffffffff815f0e2a>] common_interrupt+0x6a/0x6a <EOI> [<ffffffff8101bad2>] ? mwait_idle+0x92/0x1e0 [<ffffffff8101c50e>] cpu_idle+0xfe/0x120 [<ffffffff815df98c>] start_secondary+0x248/0x24a kernel: 3.4.0-1.fc17.x86_64 During spelscheck Thunderbird got hungup, and while it was hung, I made it the highest priority in CPU and Hard Disk, a little after that I got the kernel crash Package: kernel Architecture: i686 OS Release: Fedora release 17 (Beefy Miracle) Fiz update do sistema e ao reiniciar, após o logon, reproduziu este erro. Package: kernel Architecture: i686 OS Release: Fedora release 17 (Beefy Miracle) Apos atualizar o fedora. Package: kernel Architecture: i686 OS Release: Fedora release 17 (Beefy Miracle) "yum -y install sed curl wget sudo dif sudo" Package: kernel OS Release: Fedora release 17 (Beefy Miracle) just booted up no btrfs file system on this particular machine Package: kernel OS Release: Fedora release 17 (Beefy Miracle) comment 13 above: ==== efreeti 2012-05-31 19:55:30 EDT I believe this problem happens when my external hard disk is connected to my computer. It is a usb3.0 connector and has a btrfs partition in it. Package: kernel OS Release: Fedora release 17 (Beefy Miracle) ==== Noticed this, remembered the external usb3 drive that I unpluged just as the grub was trying to start couldn't remember if it had a btrfs.... no it doesn't (parted) print all Model: ATA WDC WD10EARS-00M (scsi) Disk /dev/sda: 1000GB Sector size (logical/physical): 512B/512B Partition Table: msdos Disk Flags: Number Start End Size Type File system Flags 1 1049kB 1050MB 1049MB primary ext4 boot 2 1050MB 36.9GB 35.9GB primary linux-swap(v1) 3 36.9GB 144GB 107GB primary ext4 4 144GB 1000GB 856GB primary ext4 Model: WD My Passport 0740 (scsi) Disk /dev/sdc: 1000GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 1049kB 2097kB 1049kB bios_grub 2 2097kB 526MB 524MB ext4 ext4 boot 3 526MB 54.2GB 53.7GB ext4 4 54.2GB 64.3GB 10.1GB linux-swap(v1) 5 64.3GB 1000GB 936GB (parted) yet the "reason" WARNING: at fs/btrfs/super.c:219__brtfs_abort_transaction+0xad/0xc0 [btrfs]() on the crash report was fs/btrfs..... sorry for the excess crap if it is no help adios, @ rebooted after a microcode update and it happens again this time no pluging , un-plugging, and complete power-off before re-boot adios, @ Package: kernel OS Release: Fedora release 17 (Beefy Miracle) fresh install of fedora 17 64 bit in virtualbox with gnome and kde both selected during install. Afterwards updated kernel and installed kernel-devel, kernel-headers, dkms, gcc. Rebooted Package: kernel OS Release: Fedora release 17 (Beefy Miracle) running Yumex, Firefox 13.0, System Settings>Mouse & Touchpad when I noticed the Abrt-applet icon on the bottom of the screen. Package: kernel Architecture: i686 OS Release: Fedora release 17 (Beefy Miracle) at normal boot Package: kernel OS Release: Fedora release 17 (Beefy Miracle) Arend, is there any way to silence this WARNING? Is it important? If not, can we silence it? abrt points me here. Happens at boot-up. I don't have Ivy Bridge GPU. WARNING: at net/sched/sch_generic.c:256 dev_watchdog+0x250/0x260() kernel-3.4.2-4.fc17.x86_64 Occurred during system boot. System appears to be operating fine Package: kernel Architecture: i686 OS Release: Fedora release 17 (Beefy Miracle) (In reply to comment #56) > Arend, is there any way to silence this WARNING? Is it important? If not, > can we silence it? Hi John, I understand from a couple comments that they got no or degraded wireless connectivity afterwards so it seem important enough. I fixed a couple of scenarios which are already in stable 3.4.2 (listed below), but given comment 57 that does not cover all. brcm80211: smac: resume transmit fifo upon receiving frames brcm80211: smac: fix endless retry of A-MPDU transmissions I am looking into it on and off, but I have not got a solid lead yet. I know what is happening, but not why and how we got there. Tough nut to crack. Hopefully I find the silver bullet soon. Ho inserito una scheda SD HC da 8 Gb. È stata rilevata correttamente, ma all'apertura con Nautilus il sistema è crashato. Package: kernel OS Release: Fedora release 17 (Beefy Miracle) The issue happened on my desktop that had been locked with xscreensaver for about 4.5 hours. Xscreensaver is using its default configuration so I guess it was using several GL plugins. Package: kernel OS Release: Fedora release 17 (Beefy Miracle) *** Bug 833237 has been marked as a duplicate of this bug. *** John, to your comment #56, with my netbook on F17 I regularly get also a "ieee80211 phy52: brcms_c_ampdu_dotxstatus_complete: Pkt tx suppressed, illegal channel possibly xx". This effectively drops my wireless and I have to rmmod/modprobe the brcmsmac module, so it's not only a harmless warning... Occurs during the boot-up process Package: kernel Architecture: i686 OS Release: Fedora release 17 (Beefy Miracle) I tried to write something on btrfs formated USB drive and it was doing weird things, like unable to unmount, unable to show output of #df command and then it crashed. Package: kernel OS Release: Fedora release 17 (Beefy Miracle) touch pad Package: kernel OS Release: Fedora release 17 (Beefy Miracle) Just completed installing from Live CD/DVD; First boot up after establishing a user; was asked to select desktop: "Default Configuration" or "One Blank Panel" -- I selected Default Config. When desktop was opened, there was this AutoBugRpt waiting for me ... I have no clue. <sigh> Package: kernel Architecture: i686 OS Release: Fedora release 17 (Beefy Miracle) No idea. Happens since I upgraded to F17 using pre-upgrade. Package: kernel OS Release: Fedora release 17 (Beefy Miracle) Applying reccommended updates via yumex when this error popped up Package: kernel Architecture: i686 OS Release: Fedora release 17 (Beefy Miracle) I am hoping someone can firm that all of these are related to the same bug. I get a different error message, so I'm not sure they are related. However, abrt keeps pointing me here. abrt_version: 2.0.10 cmdline: BOOT_IMAGE=/vmlinuz-3.4.2-4.fc17.x86_64 root=/dev/mapper/secured-root ro rd.md=0 rd.luks.uuid=WITHHELD rd.dm=0 SYSFONT=True rd.lvm.lv=secured/root rd.luks.uuid=WITHHELD KEYTABLE=us rd.lvm.lv=secured/swap LANG=en_US.UTF-8 rhgb quiet kernel: 3.4.0-1.fc17.x86_64 time: Wed 20 Jun 2012 04:23:40 PM PDT backtrace: :WARNING: at net/sched/sch_generic.c:256 dev_watchdog+0x250/0x260() :Hardware name: MS-7388 :NETDEV WATCHDOG: p6p1 (r8169): transmit queue 0 timed out :Modules linked in: xt_LOG nf_conntrack_ipv4 nf_defrag_ipv4 lockd bnep sunrpc bluetooth rfkill ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 xt_state ip6table_filter ip6_tables xt_connlimit xt_conntrack nf_conntrack snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_timer fuse sp5100_tco snd k8temp r8169 edac_core edac_mce_amd mii soundcore i2c_piix4 serio_raw uinput xts gf128mul dm_crypt ata_generic pata_acpi pata_atiixp wmi radeon i2c_algo_bit drm_kms_helper ttm drm i2c_core [last unloaded: scsi_wait_scan] :Pid: 4189, comm: firefox Not tainted 3.4.0-1.fc17.x86_64 #1 :Call Trace: : <IRQ> [<ffffffff8105681f>] warn_slowpath_common+0x7f/0xc0 : [<ffffffff8101a8e9>] ? sched_clock+0x9/0x10 : [<ffffffff81056916>] warn_slowpath_fmt+0x46/0x50 : [<ffffffff810919f1>] ? trigger_load_balance+0x61/0x2e0 : [<ffffffff815019c0>] dev_watchdog+0x250/0x260 : [<ffffffff81501770>] ? dev_deactivate_queue.constprop.30+0x80/0x80 : [<ffffffff810659c1>] run_timer_softirq+0x141/0x340 : [<ffffffff8107bc69>] ? enqueue_hrtimer+0x29/0x90 : [<ffffffff8105dbc0>] __do_softirq+0xc0/0x1e0 : [<ffffffff815f9edc>] call_softirq+0x1c/0x30 : [<ffffffff810151f5>] do_softirq+0x75/0xb0 : [<ffffffff8105df95>] irq_exit+0xb5/0xc0 : [<ffffffff815fa81e>] smp_apic_timer_interrupt+0x6e/0x99 : [<ffffffff815f958a>] apic_timer_interrupt+0x6a/0x70 : <EOI> [<ffffffff815f8c10>] ? sysret_audit+0x17/0x21 smolt_data: : : :General :================================= :UUID: 8c00c362-11f8-4291-80b0-4f4b13a39a8a :OS: Fedora release 17 (Beefy Miracle) :Default run level: Unknown :Language: en_US.UTF-8 :Platform: x86_64 :BogoMIPS: 4999.73 :CPU Vendor: AuthenticAMD :CPU Model: AMD Athlon(tm) Dual Core Processor 4850e :CPU Stepping: 2 :CPU Family: 15 :CPU Model Num: 107 :Number of CPUs: 2 :CPU Speed: 2500 :System Memory: 3955 :System Swap: 8191 :Vendor: MICRO-STAR INTERNATIONAL CO.,LTD :System: MS-7388 1.0 :Form factor: Desktop :Kernel: 3.4.2-4.fc17.x86_64 :SELinux Enabled: 1 :SELinux Policy: targeted :SELinux Enforce: Enforcing :MythTV Remote: Unknown :MythTV Role: Unknown :MythTV Theme: Unknown :MythTV Plugin: :MythTV Tuner: -1 : : :Devices :================================= :(4098:22908:4098:22872) pci, pcieport, PCI/PCI, RD790 PCI to PCI bridge (PCI express gpp port C) :(4098:43552:5218:43552) pci, snd_hda_intel, MULTIMEDIA, RV635 Audio device [Radeon HD 3600 Series] :(4098:17290:5218:29576) pci, ohci_hcd, USB, SB600 USB (OHCI3) :(4098:22872:4098:22872) pci, None, HOST/PCI, RD780 Northbridge only dual slot PCI-e_GFX and HT1 K8 part :(4098:17292:5218:29576) pci, pata_atiixp, STORAGE, SB600 IDE :(4332:33128:5218:14476) pci, r8169, ETHERNET, RTL8111/8168B PCI Express Gigabit Ethernet controller :(4130:4352:0:0) pci, None, HOST/PCI, K8 [Athlon64/Opteron] HyperTransport Technology Configuration :(4130:4355:0:0) pci, k8temp, HOST/PCI, K8 [Athlon64/Opteron] Miscellaneous Control :(4130:4354:0:0) pci, None, HOST/PCI, K8 [Athlon64/Opteron] DRAM Controller :(4130:4353:0:0) pci, None, HOST/PCI, K8 [Athlon64/Opteron] Address Map :(4098:17280:5218:29576) pci, ahci, STORAGE, SB600 Non-Raid-5 SATA :(4098:22904:4098:22872) pci, pcieport, PCI/PCI, RD790 PCI to PCI bridge (external gfx0 port A) :(4098:17285:5218:29576) pci, None, SERIAL, SBx00 SMBus Controller :(4098:17293:5218:29576) pci, None, PCI/ISA, SB600 PCI to LPC Bridge :(4098:17283:5218:29576) pci, snd_hda_intel, MULTIMEDIA, SBx00 Azalia (Intel HDA) :(4098:17284:0:0) pci, None, PCI/PCI, SBx00 PCI to PCI Bridge :(4098:17289:5218:29576) pci, ohci_hcd, USB, SB600 USB (OHCI2) :(4098:38296:5218:4496) pci, radeon, VIDEO, Mobility Radeon HD 3600 Series :(4098:17287:5218:29576) pci, ohci_hcd, USB, SB600 USB (OHCI0) :(4098:17288:5218:29576) pci, ohci_hcd, USB, SB600 USB (OHCI1) :(4098:17291:5218:29576) pci, ohci_hcd, USB, SB600 USB (OHCI4) :(4098:17286:5218:29576) pci, ehci_hcd, USB, SB600 USB Controller (EHCI) : : :Filesystem Information :================================= :device mtpt type bsize frsize blocks bfree bavail file ffree favail :------------------------------------------------------------------- :/dev/mapper/secured-root / ext4 4096 4096 67031890 62801733 59446290 16777216 16636609 16636609 :/dev/sda2 WITHHELD fuseblk 16384 16384 22135483 18887047 18887047 302323824 302322569 302322569 :/dev/sdb2 /boot ext4 1024 1024 496449 437167 412182 124928 124589 124589 :/dev/mapper/secured-home /home ext4 4096 4096 418632878 230269312 209317453 104759296 104730357 104730357 : END: The issue appeares on system startup only. Waking up from hibernation is passed correctly. Package: kernel Architecture: i686 OS Release: Fedora release 17 (Beefy Miracle) The latest nouveau from git and the latest Fedora Kernel keeps failing at KDM. Package: kernel OS Release: Fedora release 17 (Beefy Miracle) (In reply to comment #70) > I am hoping someone can firm that all of these are related to the same bug. > I get a different error message, so I'm not sure they are related. However, > abrt keeps pointing me here. Sigh. Thanks for including the backtrace. When abrt directs people here, it doesn't attach the backtrace so we can't tell whether it's really the same problem or not. In your case, it isn't. I suspect the reporter in comment #72 also isn't seeing the brcmsmac problem this bug is for. I'm removing the hash from the whiteboard so abrt will stop doing that. I actually suspect that more comments fall into that category. The problem flagged by this WARN is not causing a system crash (worst case is loss of wireless connectivity) and there are quite a number of comments saying their system crashed. My case appears to be related to this bug: https://bugzilla.redhat.com/show_bug.cgi?id=715137 This seems odd because this bug was originally reported 2011-06-21 but it didn't impact me until the update on 2012-06-17 (kernel-3.4.2-4.fc17.x86_64). In my case, there is no noticeable loss in functionality. Thank you for all your help. I will raise future concerns on that bug. *** This bug has been marked as a duplicate of bug 799168 *** |