Bug 806547 - [abrt] kernel: WARNING: at block/genhd.c:1570 disk_clear_events+0xe0/0xf0()
Summary: [abrt] kernel: WARNING: at block/genhd.c:1570 disk_clear_events+0xe0/0xf0()
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 17
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:490baf7d89680f6b4606970771b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-24 16:13 UTC by Bruno Wolff III
Modified: 2012-06-28 02:28 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-28 02:28:22 UTC
Type: ---


Attachments (Terms of Use)

Description Bruno Wolff III 2012-03-24 16:13:40 UTC
libreport version: 2.0.8
abrt_version:   2.0.7
cmdline:        initrd=initrd0.img root=live:UUID=cc429e5a-0c22-4cee-96ad-dbe1468a7c17 rootfstype=ext4 ro liveimg quiet  rhgb rd.luks=0 rd.md=0 rd.dm=0  BOOT_IMAGE=vmlinuz0 
comment:        I put the f17 live desktop RC1 live image on a usb flash drive booted an old laptop using the usb drive. I ran live install from icon on the left and I got the abort message.
kernel:         3.3.0-1.fc17.i686
reason:         WARNING: at block/genhd.c:1570 disk_clear_events+0xe0/0xf0()
smolt_data:     Unable to save UUID to /etc/smolt/hw-uuid.  Please run once as root.
time:           Sat 24 Mar 2012 11:14:42 AM EDT

backtrace:
:WARNING: at block/genhd.c:1570 disk_clear_events+0xe0/0xf0()
:Hardware name: Inspiron 2200                   
:Modules linked in: iscsi_ibft iscsi_boot_sysfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi xts lrw gf128mul sha256_generic dm_crypt vfat fat dm_round_robin dm_multipath raid10 raid456 async_raid6_recov async_memcpy async_pq raid6_pq async_xor xor async_tx raid1 raid0 fuse ipt_MASQUERADE nf_conntrack_netbios_ns nf_conntrack_broadcast ip6table_mangle ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables iptable_nat nf_nat iptable_mangle nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack bnep bluetooth arc4 b43 bcma mac80211 cfg80211 microcode dell_laptop rfkill dcdbas snd_intel8x0 ssb snd_intel8x0m snd_ac97_codec ac97_bus mmc_core snd_pcm iTCO_wdt snd_page_alloc iTCO_vendor_support snd_timer i2c_i801 snd e100 soundcore mii yenta_socket uinput squashfs i915 video i2c_algo_bit drm_kms_helper drm i2c_core usb_storage [last unloaded: scsi_wait_scan]
:Pid: 1463, comm: udevd Not tainted 3.3.0-1.fc17.i686 #1
:Call Trace:
: [<c0437232>] warn_slowpath_common+0x72/0xa0
: [<c063ddf0>] ? disk_clear_events+0xe0/0xf0
: [<c063ddf0>] ? disk_clear_events+0xe0/0xf0
: [<c0437282>] warn_slowpath_null+0x22/0x30
: [<c063ddf0>] disk_clear_events+0xe0/0xf0
: [<c05630d6>] check_disk_change+0x26/0x70
: [<c07386ef>] sd_open+0x8f/0x1a0
: [<c0450180>] ? cancel_delayed_work_sync+0x10/0x20
: [<c063d979>] ? disk_block_events+0x59/0x80
: [<c0738660>] ? sd_rescan+0x30/0x30
: [<c0563fe9>] __blkdev_get+0x2e9/0x400
: [<c0564254>] blkdev_get+0x154/0x270
: [<c05643c2>] blkdev_open+0x52/0x70
: [<c0532c52>] __dentry_open+0x212/0x2e0
: [<c0533c66>] nameidata_to_filp+0x66/0x80
: [<c0564370>] ? blkdev_get+0x270/0x270
: [<c0541dbf>] do_last+0x3bf/0x7b0
: [<c0542295>] path_openat+0xa5/0x350
: [<c0542651>] do_filp_open+0x31/0x80
: [<c054cdbc>] ? alloc_fd+0x3c/0xe0
: [<c053e263>] ? getname_flags+0xb3/0x160
: [<c0533d5d>] do_sys_open+0xdd/0x1a0
: [<c04a7066>] ? __audit_syscall_exit+0x356/0x3b0
: [<c0533e52>] sys_open+0x32/0x40
: [<c09277c4>] syscall_call+0x7/0xb
: [<c0920000>] ? remove_waiter+0x9f/0x135

Comment 1 Dave Jones 2012-06-28 00:49:29 UTC
Can you reproduce this on 3.4 ?

Comment 2 Bruno Wolff III 2012-06-28 02:28:22 UTC
I haven't been testing installs on that machine recently. But I am currently running 3.4.4-1.fc17 on it and am not seeing issues other than maybe an increase in the frequency of a wireless problem I have been seeing for a long time.
I think it's safe to close this now, and I can open another bug if it shows up with a later kernel. I'll eventually do some test installs of F18 on that machine, and if the problem is still there, I'll likely see it again.


Note You need to log in before you can comment on or make changes to this bug.