unifdef is where?
by Tom Horsley
Anyone know what rpm I need to install to get unifdef?
I'm trying to get the kernel source prep'ed in my FC6t3
system, and it says I'm missing the unifdef dependency
when I do the rpmbuild command (sigh...).
17 years, 8 months
problems with most recent fc5 maint.?
by Anne & Lynn Wheeler
FC5 2187 kernel, dump, misc. other stuff ... after reboot, non-root file
systems weren't automatically mounted (needed "mount -a" as root) and
there was some problem with automatic start of eth0 (had to deactivate
and re-activate to get internet working).
17 years, 8 months
FC6t3 - LVM space calculations in anaconda, off by 1?
by Wojtek.Pilorz
I have recently installed FC6t3 over previous FC6t2 install
(no upgrade did not work at all,
is it supposed to work? If so I will report details)
I had several filesystems on LVM in FC6t2 (root was on 'native'
partition) and all space in volume group was allocated to logical volumes.
With the same setup anaconda claimed that too much space is allocated to
LVs (over 100%, one 32MB block too much)
After I redefined LVs to satisfy anaconda in FC6t3 install (so that it
reported 100% of space in VG allocated to LVs) install went smoothly.
After FC6t3 system was started, LVM reported that 32MB (1 block) of space
in VG in unallocated.
Seems to me like a bug introduced in anaconda LVM handling between FC6t2
and FC6t3.
Best regards,
Wojtek
17 years, 8 months
sytem-config-printer
by Craig Thomas
Hi there,
I'm using rawhide and the system is yum updated, and I get this when
trying to configure a printer, any thoughts?
[root@jane ~]# system-config-printer
(system-config-printer.py:2730): libgnomevfs-WARNING **: Failed to open
session DBUS connection: Unable to determine the address of the message
bus (try 'man dbus-launch' and 'man dbus-daemon' for help)
Volume monitoring will not work.
2730: arguments to dbus_connection_send_with_reply_and_block() were
incorrect, assertion "connection != NULL" failed in file
dbus-connection.c line 2785.
This is normally a bug in some application using the D-Bus library.
2730: arguments to dbus_connection_send_with_reply_and_block() were
incorrect, assertion "connection != NULL" failed in file
dbus-connection.c line 2785.
This is normally a bug in some application using the D-Bus library.
Traceback (most recent call last):
File "/usr/share/system-config-printer/system-config-printer.py",
line 2411, in ?
main()
File "/usr/share/system-config-printer/system-config-printer.py",
line 2402, in main
mainwindow = GUI()
File "/usr/share/system-config-printer/system-config-printer.py",
line 308, in __init__
self.populateList()
File "/usr/share/system-config-printer/system-config-printer.py",
line 380, in populateList
self.printers = cupshelpers.getPrinters(self.cups)
File "/usr/share/system-config-printer/cupshelpers.py", line 213, in
getPrinters
printers_conf = PrintersConf(connection)
File "/usr/share/system-config-printer/cupshelpers.py", line 293, in
__init__
self.parse(self.fetch('/admin/conf/printers.conf'), 'Printer')
File "/usr/share/system-config-printer/cupshelpers.py", line 321, in
parse
self.device_uris[current_printer] = words[1]
IndexError: list index out of range
[root@jane ~]#
17 years, 8 months
Rawhide hangs on reboot
by Paul Michael Reilly
I could use some help here in figuring where to file this bug/issue:
While rebooting my Thinkpad A31P (model 2653-R9U) the most recent
kernel (kernel-2.6.17-1.2647.fc6) was selected by default. The boot
process gets as far as displaying the fat X (but does not display the
rotating blue swirl) before it appears to be "hung". I gave up after
15 minutes, forced a manual shutdown and then cold-booted successfully
using the original kernel (kernel-2.6.16-1.2122_FC5). This is two
kernels in a row that show this behavior so I figure it is time to log
the issue/bug but I must confess I have not a clue which module to
file this issue against. Suggestions?
Thanks,
-pmr
17 years, 8 months
Test3 doesn't boot
by Steve Grubb
Hi,
I was using the tree from last weekend so that I would not have to do another
DVD download and installed to software raid 5...all went smooth until reboot:
md: Autodetecting raid arrays
md: autorun ...
md: ... autorun done
VFS: Cannot open root device "md1" or unknown-block(0,0)
Please append a correct "root=" boot option
kernel panic - not syncing: VFS: Unable to mount root fs or unknown block(0,0)
So which is it - unable to mount or unknown block? How do you fix either?
I decided to do the full download of the Test3 final. It identified the
filesystem correctly so I told it to do an upgrade. After the replace bootloader
screen, I get a python traceback:
File "/usr/lib/python2.4/site-packages/yum/packages.py" line 612 in tagByName
raise Errors.MiscErrors "unknown header tag %s" %tag
File "/usr/lib/python2.4/site-packages/yum/packages.py" line 629 in return Simple
return Self.tagByName(thing)
File "/usr/lib/anaconda/sortedtransaction.py" line 17 in __getMedia
uri=po.returnSimple('basepath')
Hmm...the dialog offers to scp the file to a host. After typing in the
information, it says there was a problem sending the file. I ran tcpdump
on the destination machine and not a single packet arrived. Was there more
information that it should have collected or maybe some information it
should have output so that I could tell you what it did wrong? "There was a
problem" is not exactly debugable.
So...will there be a Test3.1 to fix people's installation issues or do we just
not want people testing FC6?
-Steve
17 years, 8 months
yum upgrade leaves locks in rpmdb
by Zoltan Boszormenyi
Hi,
after upgrading to glibc-2.4.90-30 today,
I experienced this:
# yum upgrade "k*"
...
Complete!
rpmdb: Locker still has locks
error: db4 error(22) from db->close: Érvénytelen paraméter
#
Best regards,
Zoltán Böszörményi
17 years, 8 months
2.6.17-1.2630.fc6 -- INFO: trying to register non-static key.
by Miles Lane
INFO: trying to register non-static key.
the code is fine but needs lockdep annotation.
turning off the locking correctness validator.
[<c04051ee>] show_trace_log_lvl+0x58/0x171
[<c0405802>] show_trace+0xd/0x10
[<c040591b>] dump_stack+0x19/0x1b
[<c043b29a>] __lock_acquire+0xfd/0x99c
[<c043c0aa>] lock_acquire+0x4b/0x6d
[<c0614364>] _spin_lock_irq+0x1f/0x2e
[<c06124c6>] wait_for_completion_timeout+0x2c/0xba
[<f9003c4a>] scsi_send_eh_cmnd+0x201/0x35b [scsi_mod]
[<f9003e0a>] scsi_eh_tur+0x25/0x71 [scsi_mod]
[<f90046b5>] scsi_error_handler+0x39f/0x95a [scsi_mod]
[<c04364a9>] kthread+0xc3/0xf2
[<c0402005>] kernel_thread_helper+0x5/0xb
DWARF2 unwinder stuck at kernel_thread_helper+0x5/0xb
Leftover inexact backtrace:
[<c0405802>] show_trace+0xd/0x10
[<c040591b>] dump_stack+0x19/0x1b
[<c043b29a>] __lock_acquire+0xfd/0x99c
[<c043c0aa>] lock_acquire+0x4b/0x6d
[<c0614364>] _spin_lock_irq+0x1f/0x2e
[<c06124c6>] wait_for_completion_timeout+0x2c/0xba
[<f9003c4a>] scsi_send_eh_cmnd+0x201/0x35b [scsi_mod]
[<f9003e0a>] scsi_eh_tur+0x25/0x71 [scsi_mod]
[<f90046b5>] scsi_error_handler+0x39f/0x95a [scsi_mod]
[<c04364a9>] kthread+0xc3/0xf2
[<c0402005>] kernel_thread_helper+0x5/0xb
pccard: card ejected from slot 0
ieee1394: Node removed: ID:BUS[1-00:1023] GUID[0080880002103eae]
PM: Removing info for ieee1394:0080880002103eae-0
PM: Removing info for ieee1394:0080880002103eae
ieee1394: Node removed: ID:BUS[1-01:1023] GUID[0090a950000b2255]
PM: Removing info for scsi:2:0:0:0
PM: Removing info for No Bus:target2:0:0
PM: Removing info for No Bus:host2
PM: Removing info for ieee1394:0090a950000b2255-0
PM: Removing info for ieee1394:0090a950000b2255
ieee1394: Node removed: ID:BUS[1-02:1023] GUID[0090a94000007475]
PM: Removing info for ieee1394:0090a94000007475-0
PM: Removing info for ieee1394:0090a94000007475
BUG: unable to handle kernel NULL pointer dereference at virtual
address 00000000
printing eip:
f93c23f7
*pde = 00000000
Oops: 0000 [#1]
SMP
last sysfs file: /class/pcmcia_socket/pcmcia_socket0/card_eject
Modules linked in: i915 drm autofs4 hidp l2cap bluetooth
cpufreq_ondemand ipv6 vfat fat dm_mirror dm_mod video sbs i2c_ec
button battery asus_acpi ac parport_pc lp parport dv1394 raw1394 sbp2
joydev snd_intel8x0 snd_seq_dummy snd_seq_oss snd_seq_midi_event
snd_seq snd_seq_device snd_pcm_oss i2c_i801 i2c_core sd_mod
snd_intel8x0m snd_ac97_codec ipw2200 snd_ac97_bus ieee80211
ieee80211_crypt pcspkr snd_mixer_oss sg snd_pcm sdhci snd_timer snd
mmc_core soundcore snd_page_alloc 8139too 8139cp mii serio_raw
ohci1394 ieee1394 ide_cd cdrom usb_storage scsi_mod ext3 jbd ehci_hcd
ohci_hcd uhci_hcd
CPU: 0
EIP: 0060:[<f93c23f7>] Not tainted VLI
EFLAGS: 00010286 (2.6.17-1.2630.fc6 #1)
EIP is at dv1394_remove_host+0x1a/0xb8 [dv1394]
eax: f9199140 ebx: 00000001 ecx: 00000000 edx: f93c23dd
esi: 00000000 edi: f93c39c8 ebp: ed410e0c esp: ed410e00
ds: 007b es: 007b ss: 0068
Process pccardctl (pid: 17878, ti=ed410000 task=dff1cab0 task.ti=ed410000)
Stack: f93c5ba0 f7688000 f93c5ba0 ed410e28 f9161410 00000000 00000206 f93c5ba0
f7688000 f911662c ed410e38 f91616b8 f7688000 f768ae28 ed410e44 f91610c4
dfe0c02c ed410e5c f910febe f768ab48 dfe0c02c dfe0c074 f911662c ed410e68
Call Trace:
[<f9161410>] __unregister_host+0x1b/0x95 [ieee1394]
[<f91616b8>] highlevel_remove_host+0x24/0x47 [ieee1394]
[<f91610c4>] hpsb_remove_host+0x3b/0x5b [ieee1394]
[<f910febe>] ohci1394_pci_remove+0x48/0x1d5 [ohci1394]
[<c04f3ed3>] pci_device_remove+0x19/0x2c
[<c0554fcf>] __device_release_driver+0x63/0x79
[<c0555224>] device_release_driver+0x2e/0x3e
[<c055490d>] bus_remove_device+0x81/0x91
[<c05538c2>] device_del+0x115/0x149
[<c0553901>] device_unregister+0xb/0x15
[<c04f1c21>] pci_remove_bus_device+0x3c/0xc6
[<c04f1cc8>] pci_remove_behind_bridge+0x1d/0x31
[<c057872e>] cb_free+0x1a/0x1d
[<c0575757>] socket_shutdown+0x70/0xd7
[<c05757db>] socket_remove+0x1d/0x24
[<c0575824>] pcmcia_eject_card+0x42/0x50
[<c0578172>] pccard_store_eject+0x1c/0x24
[<c0556230>] class_device_attr_store+0x1d/0x22
[<c04aa408>] sysfs_write_file+0xab/0xd1
[<c04735a8>] vfs_write+0xab/0x157
[<c0473bed>] sys_write+0x3b/0x60
[<c0403faf>] syscall_call+0x7/0xb
DWARF2 unwinder stuck at syscall_call+0x7/0xb
Leftover inexact backtrace:
[<c0405391>] show_stack_log_lvl+0x8a/0x95
[<c04054c9>] show_registers+0x12d/0x19a
[<c04056c6>] die+0x190/0x293
[<c06156c5>] do_page_fault+0x3dc/0x4a4
[<c0404be1>] error_code+0x39/0x40
[<f9161410>] __unregister_host+0x1b/0x95 [ieee1394]
[<f91616b8>] highlevel_remove_host+0x24/0x47 [ieee1394]
[<f91610c4>] hpsb_remove_host+0x3b/0x5b [ieee1394]
[<f910febe>] ohci1394_pci_remove+0x48/0x1d5 [ohci1394]
[<c04f3ed3>] pci_device_remove+0x19/0x2c
[<c0554fcf>] __device_release_driver+0x63/0x79
[<c0555224>] device_release_driver+0x2e/0x3e
[<c055490d>] bus_remove_device+0x81/0x91
[<c05538c2>] device_del+0x115/0x149
[<c0553901>] device_unregister+0xb/0x15
[<c04f1c21>] pci_remove_bus_device+0x3c/0xc6
[<c04f1cc8>] pci_remove_behind_bridge+0x1d/0x31
[<c057872e>] cb_free+0x1a/0x1d
[<c0575757>] socket_shutdown+0x70/0xd7
[<c05757db>] socket_remove+0x1d/0x24
[<c0575824>] pcmcia_eject_card+0x42/0x50
[<c0578172>] pccard_store_eject+0x1c/0x24
[<c0556230>] class_device_attr_store+0x1d/0x22
[<c04aa408>] sysfs_write_file+0xab/0xd1
[<c04735a8>] vfs_write+0xab/0x157
[<c0473bed>] sys_write+0x3b/0x60
[<c0403faf>] syscall_call+0x7/0xb
Code: 20 25 c7 89 da 89 9e 90 00 00 00 eb d8 5b 5e 5d c3 55 89 e5 57
bf c8 39 3c f9 56 53 8b 98 44 2b 00 00 8b 80 3c 2b 00 00 8b 70 04 <ac>
ae 75 08 84 c0 75 f8 31 c0 eb 04 19 c0 0c 01 85 c0 0f 85 81
EIP: [<f93c23f7>] dv1394_remove_host+0x1a/0xb8 [dv1394] SS:ESP 0068:ed410e00
17 years, 8 months
Why does rpmq chew CPU time forever after yum update?
by Miles Lane
Hi,
After I run yum update, I see rpmq running and running and gobbling
CPU cycles all the while. What's up with that? Should I just reboot,
or should I let rpmq complete whatever it is doing first?
32559 root 39 19 13280 2488 2000 R 96.2 0.2 79:16.11 rpmq
Thanks,
Miles
17 years, 8 months
