RE: Making swapfiles and SELinux
by Dan Thurman
Miles Lane wrote:
> > On 3/8/06, Daniel B. Thurman <dant(a)cdkkt.com> wrote:
> > [snip]
> >
> Is it possible that this is related to a problem I am seeing. When my
> machine crashes (locks up after a suspend and attempted resume), I
> have to reboot twice before I get a working system. The first reboot
> always stops with the X boot UI stating something like "Enabling
> Swap." When it freezes there, I have to cold boot. After cold
> booting, everything works fine.
>
> Any suggestions?
> Miles
Booting up without a swap came up fine and ran ok. I did a
full-blown yum package installations and updates and did not
really have too much of a problem, however I was starting to
notice as I piled on applications: 'Top', GKrellM, Ximian Email
and something, the system was very noticably running very low on
available virtual memory (not sure if it was due to memory leaks
or just memory running out of heap), but eventually all mouse,
keyboard, and video updates was grinding to a halt where I could
no longer access the system, although the HD was thrashing around
SOLIDLY. I waited for 20 minutes and no change was noticed so I
was forced to hard-reboot since nothing else worked. Rebooting
restore normalcy - but I obviously wont run too many apps until
I can get swap space installed.
I wanted to add 500MB swap, but unfortunately SELinux refused
to allow me to do that, even as root. Grrrrrrr......
So - kindly please someone - tell me how I can get around this
issue so that I can continue testing... please? Pretty, pretty,
please? :-)........ :-(
Dan
18 years, 2 months
RE: Kdump from diskdumputils package
by Dan Thurman
Dawid Gajownik wrote:
> > Daniel B. Thurman wrote:
> > For the first time, I noticed this thing called: kdump because
> > when I rebooted my system after yum updated, I noticed that
> > kdump was reporting a missing dump image and left the yellow
> > [WARNING] message before the udev appears and x windows
> > startup.
>
> Known bug - this service should be disabled by default
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=183633
>
> > Question: What is kdump.
>
> http://fedoranews.org/mediawiki/index.php/Using_Kexec_and_Kdump_in_Rawhide
>
> > Question: Can I safely disable it without any adverse effects?
>
> Yes. BTW does kdump service work on your computer? I see this problem →
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=179475 :/
>
Thanks for the information. So, it is a tool for collecting crash
data from developers during panics.
The specific problem I got for kdump fail is:
No kdump kernel image found. [WARNING]
Tried to locate /boot/vmlinux-2.6.15-1.2009.4.2_FC5hypervisorkdump
And my kernel is: /boot/vmunix-2.6.15-1.2009.4.2_FC5hypervisor
So it appears that the "kdump" string was added at the end, and if
this is the case - the kernel file definitely does not exist.
The kdump service failed to start.
Thanks,
Dan
18 years, 2 months
kernel-xen0.i686 0:2.6.15-1.2032_FC5 install Warnings.
by Justin Conover
Running Transaction
Installing: kernel-xen0-devel ######################### [1/4]
Installing: kernel-xenU-devel ######################### [2/4]
Installing: kernel-xen0 ######################### [3/4]
Installing: kernel-xenU ######################### [4/4]
WARNING: /lib/modules/2.6.15-1.2032_FC5xenU/kernel/drivers/serial/8250.koneeds
unknown symbol uart_get_baud_rate
WARNING: /lib/modules/2.6.15-1.2032_FC5xenU/kernel/drivers/serial/8250.koneeds
unknown symbol uart_resume_port
WARNING: /lib/modules/2.6.15-1.2032_FC5xenU/kernel/drivers/serial/8250.koneeds
unknown symbol uart_register_driver
WARNING: /lib/modules/2.6.15-1.2032_FC5xenU/kernel/drivers/serial/8250.koneeds
unknown symbol uart_suspend_port
WARNING: /lib/modules/2.6.15-1.2032_FC5xenU/kernel/drivers/serial/8250.koneeds
unknown symbol uart_remove_one_port
WARNING: /lib/modules/2.6.15-1.2032_FC5xenU/kernel/drivers/serial/8250.koneeds
unknown symbol uart_update_timeout
WARNING: /lib/modules/2.6.15-1.2032_FC5xenU/kernel/drivers/serial/8250.koneeds
unknown symbol uart_unregister_driver
WARNING: /lib/modules/2.6.15-1.2032_FC5xenU/kernel/drivers/serial/8250.koneeds
unknown symbol uart_get_divisor
WARNING: /lib/modules/2.6.15-1.2032_FC5xenU/kernel/drivers/serial/8250.koneeds
unknown symbol uart_match_port
WARNING: /lib/modules/2.6.15-1.2032_FC5xenU/kernel/drivers/serial/8250.koneeds
unknown symbol uart_add_one_port
WARNING: /lib/modules/2.6.15-1.2032_FC5xenU/kernel/drivers/serial/8250.koneeds
unknown symbol uart_write_wakeup
Installed: kernel-xen0.i686 0:2.6.15-1.2032_FC5 kernel-xen0-devel.i686 0:
2.6.15-1.2032_FC5 kernel-xenU.i686 0:2.6.15-1.2032_FC5
kernel-xenU-devel.i686 0:2.6.15-1.2032_FC5
Complete!
18 years, 2 months
Re: FC5T3 and Radeon Mobility X700 (was: FC5T3)
by Philippe Rigault
> "shrek-m(a)gmx.de" <shrek-m(a)gmx.de> wrote:
> > but my experiences with the same boot medium was
> > "linux text" - messy menus
> > "linux text askmethod" - the menus are ok
Brilliant!
I confirm that "linux text askmethod" works with correct menus. Thanks.
> I open a bug on the messy text menus and supposedly it is fixed in rawhide
> now.
Bugzilla number ?
18 years, 2 months
Re: Help Needed: TEST FC5 KERNELS!
by Philippe Rigault
> Message: 2
> Date: Wed, 08 Mar 2006 11:44:31 -0500
> From: Warren Togami <wtogami(a)redhat.com>
> Subject: Help Needed: TEST FC5 KERNELS!
> To: fedora-devel-list(a)redhat.com, for testers of Fedora Core
> development releases <fedora-test-list(a)redhat.com>
> Message-ID: <440F09EF.10009(a)redhat.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> http://people.redhat.com/davej/kernels/Fedora/devel/
>
> If you are running rawhide FC5 on any architecture, please update to the
> latest kernel here often, reboot and test. We need your feedback very
> quickly if a new kernel here causes regressions, because we are rapidly
> approaching what will become the FC5 final kernel.
>
> If your box is SMP or dual-core, please test booting the uniprocessor
> and multi-processor kernels if your architecture has both kernel builds.
> In cases where we have separate uniprocessor and SMP kernels (x86 and
> ppc), we need both tested because the installer uses uniprocessor while
> your yum updated system might not by default.
>
> Please keep in mind that we are only interested in regressions in things
> that would break installation and booting at this point. If issue has
> always existed in past Fedora, then it would not be useful to push it
> again now. PLEASE REPORT ONLY REGRESSIONS
>
> Thank you,
> Warren Togami
> wtogami(a)redhat.com
Hi,
Tested on x86_64 (Acer Ferrari 4005WLMi)
Compared with 2.6.15-1_1955_FC5:
- No regressions.
- Critical bug 174068 seems fixed with this kernel, Great!
Cheers,
Philippe
18 years, 2 months
'quiet' option for initializing Fedora
by Luya Tshimbalanga
I have noticed that the 'quiet' option for hidden detailed informations on booting i.e
''kernel /vmlinuz-2.6.15-1.2025_FC5 ro root=/dev/VolGroup01/LogVol00 rhgb quiet
''
no longer work on Fedora . Will it be set back in the final release?
--
_______________________________________________
Get your free email from [protocol]://mail.jp.popstarmail.org
18 years, 2 months
Re: fedora-test-list Digest, Vol 25, Issue 32
by Leslie S Satenstein
Should not mount from Fedora know about LVM partitions and how to setup access?
Yes, you are right, both disks have LVM file systems.
4. Re: Silly thing like a mount command appears to not be
working correctly? (Richard Hally)
Message: 3
Date: Tue, 7 Mar 2006 21:04:13 -0800 (PST)
From: Leslie Satenstein
Subject: Silly thing like a mount command appears to not be working
correctly?
To: fedora-test-list(a)redhat.com
Message-ID: <20060308050413.78721.qmail(a)web30207.mail.mud.yahoo.com>
Content-Type: text/plain; charset="iso-8859-1"
Here is the scenario
Fedora core4 on a dedicated 80 gig drive /hdb. (All install defaults taken)
Fedora core5 on a 200 gig dedicated drive. (All defaults taken)
Using system bios, I can boot from either drive.
I can mount the boot partition from either system to the other, but I cannot mount the data partitions.
My commands were (from root)
mkdir /other (on each hard drive)
mount -t ext3 /dev/hda? /other
where I tried ? from 7 all the way to 1. On the core4 system,
The system could not find values of /dev/hda7 through 3 . Refused /dev/hda2 and showed me the boot partition for /dev/hda1
On the core5 test3 system using the default values as set up by annaconda at install time, I could see the boot partition on /dev/hdb1 but no other partition.
Is there something I am doing wrong? I tried many flavours of xxx for the mount -t xxxx (auto, ext2, ext3) , eluding -t parameter.
Your test against a vanilla corex drive would be appreciated.
Leslie
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://www.redhat.com/archives/fedora-test-list/attachments/20060307/947...
------------------------------
Message: 4
Date: Wed, 08 Mar 2006 00:16:55 -0500
From: Richard Hally
Subject: Re: Silly thing like a mount command appears to not be
working correctly?
To: For testers of Fedora Core development releases
Message-ID: <440E68C7.40605(a)mindspring.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Leslie Satenstein wrote:
> Here is the scenario
>
> Fedora core4 on a dedicated 80 gig drive /hdb. (All install defaults taken)
>
> Fedora core5 on a 200 gig dedicated drive. (All defaults taken)
>
> Using system bios, I can boot from either drive.
>
> I can mount the boot partition from either system to the other, but I
> cannot mount the data partitions.
>
> My commands were (from root)
>
> mkdir /other (on each hard drive)
>
>
> mount -t ext3 /dev/hda? /other
> where I tried ? from 7 all the way to 1. On the core4 system,
> The system could not find values of /dev/hda7 through 3 . Refused
> /dev/hda2 and showed me the boot partition for /dev/hda1
>
>
> On the core5 test3 system using the default values as set up by
> annaconda at install time, I could see the boot partition on /dev/hdb1
> but no other partition.
> Is there something I am doing wrong? I tried many flavours of xxx for
> the mount -t xxxx (auto, ext2, ext3) , eluding -t parameter.
>
> Your test against a vanilla corex drive would be appreciated.
>
> Leslie
>
Your problem may have to do with the fact that default installs use LVM
for partitions other than /boot.
18 years, 2 months
mono-beagled -- major memory leak
by Jonathan Berry
Okay, well, after using my FC5T3 +updates machine for a little while I
find that mono-beagled is using up 71.4 % of my RAM. Of my 2.0 GB of
RAM... That's about 1.4 GB... There's just something wrong about
that.
$ free
total used free shared buffers cached
Mem: 2056132 2027276 28856 0 7880 214296
-/+ buffers/cache: 1805100 251032
Swap: 2096472 1328180 768292
$ ps aux | grep mono-beagled
berryja 2723 0.7 71.4 2963828 1468308 ? Sl 21:34 0:47
mono-beagled --debug /usr/lib64/beagle/BeagleDaemon.exe --bg
Is anyone else seeing this? I'm assuming that it is not supposed to
do that. Any ideas about how to debug this?
Aha, already in bugzilla:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=183958
Jonathan
18 years, 2 months
Re: [Fwd: Help Needed: FC5 Blocker List and Rawhide Install Testing]
by Fulko.Hew@sita.aero
Rahul Sundaram <sundaram(a)fedoraproject.org> on 03/08/2006 03:51 AM wrote on
behalf of Warren:
>
https://bugzilla.redhat.com/bugzilla/showdependencytree.cgi?id=150222&hid...
>
> We are now attempting to fix some last minute problems. Your help would
> be greatly appreciated in finding solutions for the problems listed in
> the above FC5 Blocker list.
>
> Your testing of rawhide nightly tree installs (while not guaranteed to
> work) is very valuable at this point. We need to know if there are any
> critical installation issues that would effect FC5 install, like the
> nasty Bug #159026. Please also test upgrades of FC3 or FC4 systems to
> the nightly rawhide tree and report any problems that you see to
Bugzilla.
>
> Bugzilla is the official and best way to get reports to the developers.
> Complaints posted only to a mailing list are very likely to be lost in
> the bulk. Bug reports have status, comments and resolution states so at
> least there is a chance of tracking your issue.
I (and others) would like to see the problem with 'no longer being able to
install'
resolved. Apparently something between FC5 Test 1 and Test2 _changed_ the
way
the CD and DVDs are made, preventing some people from installing off of
the media, whereas older version of Core work fine.
This is reported in Bugzilla #s: 178143, 182147, 178632
This bug will prevent (some) people from being able to install Fedora
Core altogether. And it will give any newcomer, a bad taste...
well actually _no_ taste, since they won't know how to get past
the boot prompt!
> Thank you for using Fedora.
>
> Warren Togami
> wtogami(a)redhat.com
18 years, 2 months
Re: fedora-test-list Digest, Vol 25, Issue 31
by William John Murray
> Message: 13
> Date: Tue, 7 Mar 2006 18:15:33 -0800
> From: "Tom London" <selinux(a)gmail.com>
> Subject: Re: NetworkManager help?
> To: "For testers of Fedora Core development releases"
> <fedora-test-list(a)redhat.com>
> Message-ID:
> <4c4ba1530603071815t58d75e28l8a5cb5136ffefad6(a)mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Sorry for the wrong answer, I misread.....
>
> nm-applet is meant to be run in the background. Are you saying that
> if you do this, you don't get the applet in the panel?
>
> Have you started the NetworkManager and NetworkManagerDispatcher
> services? (From a root terminal window, do 'ps agx | grep Network';
> are they both running?)
>
> tom
>
Of course....NetworkManager wasn't running.I thought I checked, but
obviously not.
Sorry,
Bill
18 years, 2 months