FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora User

 
 
LinkBack Thread Tools
 
Old 08-18-2010, 02:41 PM
Steve Blackwell
 
Default kernel crash

On Wed, 18 Aug 2010 08:44:16 +0300
Gilboa Davara <gilboad@gmail.com> wrote:

> On Tue, 2010-08-17 at 13:08 -0400, Steve Blackwell wrote:
> > On Wed, 18 Aug 2010 02:12:16 +0930
> > Tim <ignored_mailbox@yahoo.com.au> wrote:
> >
> > > On Tue, 2010-08-17 at 12:05 -0400, Steve Blackwell wrote:
> > > > I've been looking at my logs some more. I don't understand these
> > > > messages:
> > > >
> > > > Aug 17 10:30:50 steve kernel: CPU0: Temperature above
> > > > threshold, cpu clock throttled (total events = 455)
> > > > Aug 17 10:30:50 steve kernel: CPU1: Temperature above
> > > > threshold, cpu clock throttled (total events = 455)
> > > > Aug 17 10:30:50 steve kernel: CPU1: Temperature/speed normal
> > > > Aug 17 10:30:50 steve kernel: CPU0: Temperature/speed normal
> > >
> > > And the CPU overheating as well as your hard drive?
> > >
> > > Is the computer in a hot room? Are the fans working? Is the
> > > ventilation blocked? Is the computer wedged in between things
> > > that restrict airflow? Are things full of fluff and dust?
> > >
> > >
> > Well it would seems so but I don't trust the messages. It doesn't
> > seem reasonable that the CPUs go overtemp and then immediately cool
> > down enough to be OK.
>
> Actually it is possible.
> Your CPU has auto-throttle support. Read: When the CPU passes a
> certain temperature threshold, it automatically clocks down (or
> inserts NOPs) in-order to prevent is from burning out. Never the
> less, if your machine's cooling is sufficient you shouldn't see this
> message.
>
> If you CPU's high and low water mark are the same (E.g. 90C), the CPU
> will reach 90C, throttle, and drop to 89C - all in one second.
> I'd suggest you configure lm_sensros and monitor the CPU and board
> temperature.
> $ sensors-detect
> $ /etc/init.d/lm_sensors restart
> $ sensors -s
> $ sensors
>
> - Gilboa
> P.S. can you post your hardware configuration?
>

Running sensors-detect produced the same /etc/sysconfig/lm_sensors
file that I already had. Running sensors shows this:

# sensors
atk0110-acpi-0
Adapter: ACPI interface
Vcore Voltage: +1.42 V (min = +1.45 V, max = +1.75 V)
+3.3 Voltage: +1.68 V (min = +3.00 V, max = +3.60 V)
+5.0 Voltage: +1.62 V (min = +4.50 V, max = +5.50 V)
+12.0 Voltage: +11.98 V (min = +11.20 V, max = +13.20 V)
CPU FAN Speed: 56250 RPM (min = 0 RPM)
CHASSIS FAN Speed: 0 RPM (min = 0 RPM)
POWER FAN Speed: 0 RPM (min = 0 RPM)
CPU Temperature: +62.0C (high = +90.0C, crit = +125.0C)
MB Temperature: +49.0C (high = +70.0C, crit = +125.0C)
Power Temperature: +24.0C (high = +80.0C, crit = +125.0C)

The first thing that jumps out at me is that I think I need a new PSU!
How is this machine even running if 3 of the 4 voltages are low?

The second thing is that the temps are just fine. So why do I keep
getting these messages in the logs? Perhaps because the power rails are
low?

The chassis and power fans are 2 wire so no data.

lshw dumps a lot of information. Anything in particular you are looking
for?

I think I have solved my lockup problem. I'll write a separate post
about that.

Thanks,
Steve
--
Changing lives one card at a time

http://www.send1cardnow.com
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 08-18-2010, 04:01 PM
Gilboa Davara
 
Default kernel crash

On Wed, 2010-08-18 at 10:41 -0400, Steve Blackwell wrote:
> On Wed, 18 Aug 2010 08:44:16 +0300
> Gilboa Davara <gilboad@gmail.com> wrote:
>
> > On Tue, 2010-08-17 at 13:08 -0400, Steve Blackwell wrote:
> > > On Wed, 18 Aug 2010 02:12:16 +0930
> > > Tim <ignored_mailbox@yahoo.com.au> wrote:
> > >
> > > > On Tue, 2010-08-17 at 12:05 -0400, Steve Blackwell wrote:
> > > > > I've been looking at my logs some more. I don't understand these
> > > > > messages:
> > > > >
> > > > > Aug 17 10:30:50 steve kernel: CPU0: Temperature above
> > > > > threshold, cpu clock throttled (total events = 455)
> > > > > Aug 17 10:30:50 steve kernel: CPU1: Temperature above
> > > > > threshold, cpu clock throttled (total events = 455)
> > > > > Aug 17 10:30:50 steve kernel: CPU1: Temperature/speed normal
> > > > > Aug 17 10:30:50 steve kernel: CPU0: Temperature/speed normal
> > > >
> > > > And the CPU overheating as well as your hard drive?
> > > >
> > > > Is the computer in a hot room? Are the fans working? Is the
> > > > ventilation blocked? Is the computer wedged in between things
> > > > that restrict airflow? Are things full of fluff and dust?
> > > >
> > > >
> > > Well it would seems so but I don't trust the messages. It doesn't
> > > seem reasonable that the CPUs go overtemp and then immediately cool
> > > down enough to be OK.
> >
> > Actually it is possible.
> > Your CPU has auto-throttle support. Read: When the CPU passes a
> > certain temperature threshold, it automatically clocks down (or
> > inserts NOPs) in-order to prevent is from burning out. Never the
> > less, if your machine's cooling is sufficient you shouldn't see this
> > message.
> >
> > If you CPU's high and low water mark are the same (E.g. 90C), the CPU
> > will reach 90C, throttle, and drop to 89C - all in one second.
> > I'd suggest you configure lm_sensros and monitor the CPU and board
> > temperature.
> > $ sensors-detect
> > $ /etc/init.d/lm_sensors restart
> > $ sensors -s
> > $ sensors
> >
> > - Gilboa
> > P.S. can you post your hardware configuration?
> >
>
> Running sensors-detect produced the same /etc/sysconfig/lm_sensors
> file that I already had. Running sensors shows this:
>
> # sensors
> atk0110-acpi-0
> Adapter: ACPI interface
> Vcore Voltage: +1.42 V (min = +1.45 V, max = +1.75 V)
> +3.3 Voltage: +1.68 V (min = +3.00 V, max = +3.60 V)
> +5.0 Voltage: +1.62 V (min = +4.50 V, max = +5.50 V)
> +12.0 Voltage: +11.98 V (min = +11.20 V, max = +13.20 V)
> CPU FAN Speed: 56250 RPM (min = 0 RPM)
> CHASSIS FAN Speed: 0 RPM (min = 0 RPM)
> POWER FAN Speed: 0 RPM (min = 0 RPM)
> CPU Temperature: +62.0C (high = +90.0C, crit = +125.0C)
> MB Temperature: +49.0C (high = +70.0C, crit = +125.0C)
> Power Temperature: +24.0C (high = +80.0C, crit = +125.0C)
>
> The first thing that jumps out at me is that I think I need a new PSU!
> How is this machine even running if 3 of the 4 voltages are low?

Doubt it. Look at the CPU fan speed. Most likely lm_sensors fails to
convert the raw sensor readings to real values.
I'd suggest to reboot the machine, and check if your machine's BIOS has
sensors/monitor tab / menu. If it has, you may be able to view the
actual PSU voltage and fan speeds from within your BIOS.

>
> The second thing is that the temps are just fine. So why do I keep
> getting these messages in the logs? Perhaps because the power rails are
> low?

Doubt it.
Temperatures looks OK.

>
> The chassis and power fans are 2 wire so no data.

OK.

>
> lshw dumps a lot of information. Anything in particular you are looking
> for?

CPU, motherboard make / model, PSU information, memory configuration,
etc.

>
> I think I have solved my lockup problem. I'll write a separate post
> about that.

Good to hear.

- Gilboa

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 08-18-2010, 04:03 PM
Steve Blackwell
 
Default kernel crash

On Wed, 18 Aug 2010 11:44:53 +1000
David <bouncingcats@gmail.com> wrote:

> On 18 August 2010 09:22, Bill Davidsen <davidsen@tmr.com> wrote:
> >>
> > If this line is for real:
> > *194 Temperature_Celsius * * 0x0022 * 116 * 253 * 000 * *Old_age
> > Always
> > *- * * * 34
> >
> > Then your drive is running hotter than boiling water and has been
> > close to melting point of solder. In spite of that the error count
> > is fine, but holding your hand an inch or so from the drive should
> > tell you if this is that hot.
>
> Having rtfm, I think the values reported there are normalised values,
> not degrees Celsius.
>
> See
> http://sourceforge.net/apps/trac/smartmontools/wiki/FAQ#Whyismydisktemperaturesreportedbysmartdas150Ce lsius
>
> and read 'man smartctl' under option -A

David, thanks for the link and yes, you are correct.

I have now modified my /etc/smartd.conf file and added -r 194 which
should make the temps get reported in raw format. ie degC.

/dev/sdb -a -d sat -H -r 194 -m root

sensors indicated the the CPU fan and the power supply rails are
monitored. Does anyone know if I can put something in smartd.conf to
get reports on them and if so what?

Thanks,
Steve
--
Changing lives one card at a time

http://www.send1cardnow.com
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 08-18-2010, 04:20 PM
David
 
Default kernel crash

On 19 August 2010 00:41, Steve Blackwell <zephod@cfl.rr.com> wrote:
>
> Running sensors-detect produced the same /etc/sysconfig/lm_sensors
> file that I already had. Running sensors shows this:
>
> +3.3 Voltage: +1.68 V (min = +3.00 V, max = +3.60 V)
> +5.0 Voltage: +1.62 V (min = +4.50 V, max = +5.50 V)
> CPU FAN Speed: * *56250 RPM *(min = * *0 RPM)

Fan rpm value looks much higher than typical.
The motherboard can not possibly be running with the above reported voltages.
More likely the sensors raw-to-reported scaling is incorrectly
calibrated for your system.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 08-18-2010, 04:28 PM
Steve Blackwell
 
Default kernel crash

On Tue, 17 Aug 2010 18:07:18 +0300
Gilboa Davara <gilboad@gmail.com> wrote:

> On Tue, 2010-08-17 at 09:44 -0400, Steve Blackwell wrote:
> > I leave my computer on 24/7 so that my backups can run at night.
> > Lately, it has been crashing during the night usually leaving no
> > trace of what happened. Last night it crashed but left this
> > in /var/log/messages:
> >
> > Aug 17 01:04:56 steve kernel: INFO: task kjournald:1960 blocked for
> > more than 120 seconds. Aug 17 01:04:56 steve kernel: "echo 0
> > > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> > > Could a hard drive get shut down because it was getting too hot?
> > > What would be a normal temp for a hard drive that has just
> > > completed a backup? 124C seems really hot. The HD cooling fan had
> > > been broken so I replaced it this past weekend but it doesn't
> > > seem to have helped. Too late? Permanent HD damage already done?
> > Any other comments or suggestions?
>
> Hello Steve,
>
> This is not a crash.
> The kjournald kernel process (which handles various file-system task).
> You assumption that the HD went into some type of sleep/suspend mode
> during write sounds reasonable to me.

My machine locked up again yesterday evening and my inner Grissom had
been nagging me all day. Something just didn't make sense. If it was a
temperature problem, then why did it always happen after long periods
of inactivity and usually at night when the temperatures should be at
their coolest?

I went back and looked at the logs from yesterday. This time I found
that the last log written was pm-suspend.log. (Ah-ha!) At the bottom of
this log are these lines:
...
/usr/lib/pm-utils/sleep.d/98smart-kernel-video suspend suspend: success.
/usr/lib/pm-utils/sleep.d/99hd-apm-restore.hook suspend suspend:
Advanced Power Management not supported by device sdc. Advanced Power
Management not supported by device sda. Advanced Power Management not
supported by device sdb. success.
/usr/lib/pm-utils/sleep.d/99video suspend suspend:
kernel.acpi_video_flags = 0 success.
Tue Aug 17 21:42:23 EDT 2010: performing suspend

I found that I have 2 screensavers enabled, an X screensaver and a
GNOME screensaver. One of them had power management enabled and set to
suspend after 2 hrs of inactivity. I disabled the X screensaver and
disabled power management. Last night the machine ran all night with no problems.

It looks like the power management was able to put the disks to sleep
but not wake them up because power management is not supported by the
disks. This problems started a few weeks ago so I suspect an update of
screensaver on Aug 6 started the problem.

So nothing to do with overheating but I am learning more about smartd.

Steve.
--
Changing lives one card at a time

http://www.send1cardnow.com
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 08-19-2010, 06:16 AM
Tim
 
Default kernel crash

On Wed, 2010-08-18 at 12:03 -0400, Steve Blackwell wrote:
> sensors indicated the the CPU fan and the power supply rails are
> monitored. Does anyone know if I can put something in smartd.conf to
> get reports on them and if so what?

SMART is for hard drives. If you want to monitor other things, you need
to use another tool.

--
[tim@localhost ~]$ uname -r
2.6.27.25-78.2.56.fc9.i686

Don't send private replies to my address, the mailbox is ignored. I
read messages from the public lists.



--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 
Old 03-08-2011, 01:18 AM
Antonio Olivares
 
Default kernel crash

--- On Mon, 3/7/11, Adam Williamson <awilliam@redhat.com> wrote:

> From: Adam Williamson <awilliam@redhat.com>
> Subject: Re: kernel crash
> To: "For testers of Fedora development releases" <test@lists.fedoraproject.org>
> Date: Monday, March 7, 2011, 6:02 PM
> On Mon, 2011-03-07 at 17:44 -0800,
> Antonio Olivares wrote:
>
> > This was sent to oops page, but not to fedora
> bugzilla.* Is that what the reporting tool should do?
>
> Yes. It's also not a crash, but a warning.
> --

Then why the damn thing says that it is a kernel crash?
If it is just a warning, then the tool should just report an oops right?

BTW, the following sealert keeps popping up and a bug has already been filed

It is sadly becoming annoying

SELinux is preventing /usr/lib/xulrunner-2/plugin-container from name_connect access on the tcp_socket port 5050.

***** Plugin catchall (100. confidence) suggests ***************************

If you believe that plugin-container should be allowed name_connect access on the port 5050 tcp_socket by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# grep plugin-containe /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context unconfined_u:unconfined_r:mozilla_plugin_t:s0-s0:c
0.c1023
Target Context system_ubject_r:mmcc_port_t:s0
Target Objects port 5050 [ tcp_socket ]
Source plugin-containe
Source Path /usr/lib/xulrunner-2/plugin-container
Port 5050
Host toshiba-satellite
Source RPM Packages xulrunner-2.0-0.25.b12.fc15
Target RPM Packages
Policy RPM selinux-policy-3.9.15-2.fc15
Selinux Enabled True
Policy Type targeted
Enforcing Mode Enforcing
Host Name toshiba-satellite
Platform Linux toshiba-satellite
2.6.38-0.rc6.git6.1.fc15.i686 #1 SMP Sat Feb 26
02:03:01 UTC 2011 i686 i686
Alert Count 6
First Seen Thu 03 Mar 2011 08:50:35 PM CST
Last Seen Mon 07 Mar 2011 07:55:31 PM CST
Local ID afb8cabc-0526-4409-8185-8412c24eceba

Raw Audit Messages
type=AVC msg=audit(1299549331.536:133): avc: denied { name_connect } for pid=3337 comm="plugin-containe" dest=5050 scontext=unconfined_u:unconfined_r:mozilla_plugin_ t:s0-s0:c0.c1023 tcontext=system_ubject_r:mmcc_port_t:s0 tclass=tcp_socket


type=SYSCALL msg=audit(1299549331.536:133): arch=i386 syscall=socketcall success=yes exit=0 a0=3 a1=af4fd080 a2=3729614 a3=0 items=0 ppid=2323 pid=3337 auid=500 uid=500 gid=500 euid=500 suid=500 fsuid=500 egid=500 sgid=500 fsgid=500 tty=(none) ses=1 comm=plugin-containe exe=/usr/lib/xulrunner-2/plugin-container subj=unconfined_u:unconfined_r:mozilla_plugin_t:s0-s0:c0.c1023 key=(null)

Hash: plugin-containe,mozilla_plugin_t,mmcc_port_t,tcp_socket,n ame_connect

audit2allow

#============= mozilla_plugin_t ==============
allow mozilla_plugin_t mmcc_port_t:tcp_socket name_connect;

audit2allow -R

#============= mozilla_plugin_t ==============
allow mozilla_plugin_t mmcc_port_t:tcp_socket name_connect;



https://bugzilla.redhat.com/show_bug.cgi?id=682078

Thanks,

Antonio



--
selinux mailing list
selinux@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/selinux
 
Old 03-08-2011, 01:30 PM
Miroslav Grepl
 
Default kernel crash

On 03/08/2011 02:18 AM, Antonio Olivares wrote:
>
> --- On Mon, 3/7/11, Adam Williamson<awilliam@redhat.com> wrote:
>
>> From: Adam Williamson<awilliam@redhat.com>
>> Subject: Re: kernel crash
>> To: "For testers of Fedora development releases"<test@lists.fedoraproject.org>
>> Date: Monday, March 7, 2011, 6:02 PM
>> On Mon, 2011-03-07 at 17:44 -0800,
>> Antonio Olivares wrote:
>>
>>> This was sent to oops page, but not to fedora
>> bugzilla. Is that what the reporting tool should do?
>>
>> Yes. It's also not a crash, but a warning.
>> --
> Then why the damn thing says that it is a kernel crash?
> If it is just a warning, then the tool should just report an oops right?
>
> BTW, the following sealert keeps popping up and a bug has already been filed
>
> It is sadly becoming annoying
>
> SELinux is preventing /usr/lib/xulrunner-2/plugin-container from name_connect access on the tcp_socket port 5050.
>
> ***** Plugin catchall (100. confidence) suggests ***************************
>
> If you believe that plugin-container should be allowed name_connect access on the port 5050 tcp_socket by default.
> Then you should report this as a bug.
> You can generate a local policy module to allow this access.
> Do
> allow this access for now by executing:
> # grep plugin-containe /var/log/audit/audit.log | audit2allow -M mypol
> # semodule -i mypol.pp
>
> Additional Information:
> Source Context unconfined_u:unconfined_r:mozilla_plugin_t:s0-s0:c
> 0.c1023
> Target Context system_ubject_r:mmcc_port_t:s0
> Target Objects port 5050 [ tcp_socket ]
> Source plugin-containe
> Source Path /usr/lib/xulrunner-2/plugin-container
> Port 5050
> Host toshiba-satellite
> Source RPM Packages xulrunner-2.0-0.25.b12.fc15
> Target RPM Packages
> Policy RPM selinux-policy-3.9.15-2.fc15
> Selinux Enabled True
> Policy Type targeted
> Enforcing Mode Enforcing
> Host Name toshiba-satellite
> Platform Linux toshiba-satellite
> 2.6.38-0.rc6.git6.1.fc15.i686 #1 SMP Sat Feb 26
> 02:03:01 UTC 2011 i686 i686
> Alert Count 6
> First Seen Thu 03 Mar 2011 08:50:35 PM CST
> Last Seen Mon 07 Mar 2011 07:55:31 PM CST
> Local ID afb8cabc-0526-4409-8185-8412c24eceba
>
> Raw Audit Messages
> type=AVC msg=audit(1299549331.536:133): avc: denied { name_connect } for pid=3337 comm="plugin-containe" dest=5050 scontext=unconfined_u:unconfined_r:mozilla_plugin_ t:s0-s0:c0.c1023 tcontext=system_ubject_r:mmcc_port_t:s0 tclass=tcp_socket
>
>
> type=SYSCALL msg=audit(1299549331.536:133): arch=i386 syscall=socketcall success=yes exit=0 a0=3 a1=af4fd080 a2=3729614 a3=0 items=0 ppid=2323 pid=3337 auid=500 uid=500 gid=500 euid=500 suid=500 fsuid=500 egid=500 sgid=500 fsgid=500 tty=(none) ses=1 comm=plugin-containe exe=/usr/lib/xulrunner-2/plugin-container subj=unconfined_u:unconfined_r:mozilla_plugin_t:s0-s0:c0.c1023 key=(null)
>
> Hash: plugin-containe,mozilla_plugin_t,mmcc_port_t,tcp_socket,n ame_connect
>
> audit2allow
>
> #============= mozilla_plugin_t ==============
> allow mozilla_plugin_t mmcc_port_t:tcp_socket name_connect;
>
> audit2allow -R
>
> #============= mozilla_plugin_t ==============
> allow mozilla_plugin_t mmcc_port_t:tcp_socket name_connect;
>
>
>
> https://bugzilla.redhat.com/show_bug.cgi?id=682078
>
> Thanks,
>
> Antonio
I am going to submit a new F15 policy update today. So you can test it
then and increase the karma ;-).
>
>
> --
> selinux mailing list
> selinux@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/selinux

--
selinux mailing list
selinux@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/selinux
 
Old 03-08-2011, 02:55 PM
Antonio Olivares
 
Default kernel crash

> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=682078
> >
> > Thanks,
> >
> > Antonio
> I am going to submit a new F15 policy update today. So you
> can test it
> then and increase the karma ;-).
> >
> >
> > --

I downloaded the selinux policy and yum localinstalled it to see if it could pull in deps:

[root@toshiba-satellite ~]# yum localinstall /home/olivares/Downloads/selinux-policy-3.9.16-1.fc15.noarch.rpm
Loaded plugins: langpacks, presto, refresh-packagekit
Adding en_US to language list
Setting up Local Package Process
Examining /home/olivares/Downloads/selinux-policy-3.9.16-1.fc15.noarch.rpm: selinux-policy-3.9.16-1.fc15.noarch
Marking /home/olivares/Downloads/selinux-policy-3.9.16-1.fc15.noarch.rpm as an update to selinux-policy-3.9.15-2.fc15.noarch
Resolving Dependencies
--> Running transaction check
---> Package selinux-policy.noarch 0:3.9.15-2.fc15 will be updated
--> Processing Dependency: selinux-policy = 3.9.15-2.fc15 for package: selinux-policy-targeted-3.9.15-2.fc15.noarch
--> Processing Dependency: selinux-policy = 3.9.15-2.fc15 for package: selinux-policy-targeted-3.9.15-2.fc15.noarch
---> Package selinux-policy.noarch 0:3.9.16-1.fc15 will be an update
--> Finished Dependency Resolution
Error: Package: selinux-policy-targeted-3.9.15-2.fc15.noarch (@updates-testing)
Requires: selinux-policy = 3.9.15-2.fc15
Removing: selinux-policy-3.9.15-2.fc15.noarch (@updates-testing)
selinux-policy = 3.9.15-2.fc15
Updated By: selinux-policy-3.9.16-1.fc15.noarch (/selinux-policy-3.9.16-1.fc15.noarch)
selinux-policy = 3.9.16-1.fc15
Available: selinux-policy-3.9.14-2.fc15.noarch (fedora)
selinux-policy = 3.9.14-2.fc15
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest


Should I install one by one, and in which order?


If not, would waiting for tomorrow these would be pushed to updates testing?

Thanks,

Antonio



--
selinux mailing list
selinux@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/selinux
 
Old 03-09-2011, 03:27 PM
Miroslav Grepl
 
Default kernel crash

On 03/08/2011 03:55 PM, Antonio Olivares wrote:
>>> https://bugzilla.redhat.com/show_bug.cgi?id=682078
>>>
>>> Thanks,
>>>
>>> Antonio
>> I am going to submit a new F15 policy update today. So you
>> can test it
>> then and increase the karma ;-).
>>>
>>> --
> I downloaded the selinux policy and yum localinstalled it to see if it could pull in deps:
>
> [root@toshiba-satellite ~]# yum localinstall /home/olivares/Downloads/selinux-policy-3.9.16-1.fc15.noarch.rpm
> Loaded plugins: langpacks, presto, refresh-packagekit
> Adding en_US to language list
> Setting up Local Package Process
> Examining /home/olivares/Downloads/selinux-policy-3.9.16-1.fc15.noarch.rpm: selinux-policy-3.9.16-1.fc15.noarch
> Marking /home/olivares/Downloads/selinux-policy-3.9.16-1.fc15.noarch.rpm as an update to selinux-policy-3.9.15-2.fc15.noarch
> Resolving Dependencies
> --> Running transaction check
> ---> Package selinux-policy.noarch 0:3.9.15-2.fc15 will be updated
> --> Processing Dependency: selinux-policy = 3.9.15-2.fc15 for package: selinux-policy-targeted-3.9.15-2.fc15.noarch
> --> Processing Dependency: selinux-policy = 3.9.15-2.fc15 for package: selinux-policy-targeted-3.9.15-2.fc15.noarch
> ---> Package selinux-policy.noarch 0:3.9.16-1.fc15 will be an update
> --> Finished Dependency Resolution
> Error: Package: selinux-policy-targeted-3.9.15-2.fc15.noarch (@updates-testing)
> Requires: selinux-policy = 3.9.15-2.fc15
> Removing: selinux-policy-3.9.15-2.fc15.noarch (@updates-testing)
> selinux-policy = 3.9.15-2.fc15
> Updated By: selinux-policy-3.9.16-1.fc15.noarch (/selinux-policy-3.9.16-1.fc15.noarch)
> selinux-policy = 3.9.16-1.fc15
> Available: selinux-policy-3.9.14-2.fc15.noarch (fedora)
> selinux-policy = 3.9.14-2.fc15
> You could try using --skip-broken to work around the problem
> You could try running: rpm -Va --nofiles --nodigest
>
>
> Should I install one by one, and in which order?
>
>
> If not, would waiting for tomorrow these would be pushed to updates testing?
>
> Thanks,
My bad. You need to download/install

selinux-policy-3.9.16-1.fc15.noarch.rpm
selinux-policy-targeted-3.9.16-1.fc15.noarch.rpm

packages.

Regards,
Miroslav
> Antonio
>
>
>

--
selinux mailing list
selinux@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/selinux
 

Thread Tools




All times are GMT. The time now is 08:43 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org