4:55 p.m.
Currently running Fedora 9 Release to date. Doesn't happen very
often, maybe once every 3-4 days. Twice I've caught it at idle with
the screen saver (picture viewer) frozen and twice while browsing in
Gnome.
Not really noticing anything weird in the logs?
--
projecthuh.com
All of my bits are free, are yours? Fedoraproject.org
5:21 p.m.
Currently running Fedora 9 Release to date. Doesn't happen very
often, maybe once every 3-4 days. Twice I've caught it at idle with
the screen saver (picture viewer) frozen and twice while browsing in
Gnome.
Not really noticing anything weird in the logs?
I have had this happen with Fedora 8 on my x86_64 machine. Nothing
recorded in the logs. I have not had the time to debug it.
What kind of motherboard, video card and processor? Maybe there is
something in common with my system.
5:26 p.m.
Abit 35 Pro , Intel E8400 etc.
Attached is lscpi -vvv
On Tue, May 6, 2008 at 6:21 PM, Alan <alan(a)clueserver.org> wrote:
> Currently running Fedora 9 Release to date. Doesn't happen
very
> often, maybe once every 3-4 days. Twice I've caught it at idle with
> the screen saver (picture viewer) frozen and twice while browsing in
> Gnome.
>
> Not really noticing anything weird in the logs?
I have had this happen with Fedora 8 on my x86_64 machine. Nothing
recorded in the logs. I have not had the time to debug it.
What kind of motherboard, video card and processor? Maybe there is
something in common with my system.
--
fedora-devel-list mailing list
fedora-devel-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
--
projecthuh.com
All of my bits are free, are yours? Fedoraproject.org
5:28 p.m.
On Tue, 2008-05-06 at 18:26 -0400, Dr. Diesel wrote:
Abit 35 Pro , Intel E8400 etc.
Attached is lscpi -vvv
Oh wierd an nvidia card... are you running the binary driver? or just
the normal nv one?
Dave.
On Tue, May 6, 2008 at 6:21 PM, Alan <alan(a)clueserver.org> wrote:
> > Currently running Fedora 9 Release to date. Doesn't happen very
> > often, maybe once every 3-4 days. Twice I've caught it at idle with
> > the screen saver (picture viewer) frozen and twice while browsing in
> > Gnome.
> >
> > Not really noticing anything weird in the logs?
>
> I have had this happen with Fedora 8 on my x86_64 machine. Nothing
> recorded in the logs. I have not had the time to debug it.
>
> What kind of motherboard, video card and processor? Maybe there is
> something in common with my system.
>
> --
> fedora-devel-list mailing list
> fedora-devel-list(a)redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-devel-list
>
--
fedora-devel-list mailing list
fedora-devel-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
5:30 p.m.
Just nv since Nvidia's drivers don't yet support xorg 1.5. The only
kernel module I have loaded is VirtualBox 1.6's.
Filing a bug now..
On Tue, May 6, 2008 at 6:28 PM, Dave Airlie <airlied(a)redhat.com> wrote:
On Tue, 2008-05-06 at 18:26 -0400, Dr. Diesel wrote:
> Abit 35 Pro , Intel E8400 etc.
>
> Attached is lscpi -vvv
Oh wierd an nvidia card... are you running the binary driver? or just
the normal nv one?
Dave.
>
>
>
> On Tue, May 6, 2008 at 6:21 PM, Alan <alan(a)clueserver.org> wrote:
> > > Currently running Fedora 9 Release to date. Doesn't happen very
> > > often, maybe once every 3-4 days. Twice I've caught it at idle
with
> > > the screen saver (picture viewer) frozen and twice while browsing in
> > > Gnome.
> > >
> > > Not really noticing anything weird in the logs?
> >
> > I have had this happen with Fedora 8 on my x86_64 machine. Nothing
> > recorded in the logs. I have not had the time to debug it.
> >
> > What kind of motherboard, video card and processor? Maybe there is
> > something in common with my system.
> >
> > --
> > fedora-devel-list mailing list
> > fedora-devel-list(a)redhat.com
> > https://www.redhat.com/mailman/listinfo/fedora-devel-list
> >
>
>
>
> --
> fedora-devel-list mailing list
> fedora-devel-list(a)redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-devel-list
--
fedora-devel-list mailing list
fedora-devel-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
--
projecthuh.com
All of my bits are free, are yours? Fedoraproject.org
6:21 p.m.
On Tue, 2008-05-06 at 18:30 -0400, Dr. Diesel wrote:
Just nv since Nvidia's drivers don't yet support xorg 1.5.
The only
kernel module I have loaded is VirtualBox 1.6's.
Filing a bug now..
can you try without virtualbox?
I've seen oops reports from it around the place.
Dave.
On Tue, May 6, 2008 at 6:28 PM, Dave Airlie <airlied(a)redhat.com> wrote:
> On Tue, 2008-05-06 at 18:26 -0400, Dr. Diesel wrote:
> > Abit 35 Pro , Intel E8400 etc.
> >
> > Attached is lscpi -vvv
>
> Oh wierd an nvidia card... are you running the binary driver? or just
> the normal nv one?
>
> Dave.
>
>
>
> >
> >
> >
> > On Tue, May 6, 2008 at 6:21 PM, Alan <alan(a)clueserver.org> wrote:
> > > > Currently running Fedora 9 Release to date. Doesn't happen
very
> > > > often, maybe once every 3-4 days. Twice I've caught it at idle
with
> > > > the screen saver (picture viewer) frozen and twice while browsing
in
> > > > Gnome.
> > > >
> > > > Not really noticing anything weird in the logs?
> > >
> > > I have had this happen with Fedora 8 on my x86_64 machine. Nothing
> > > recorded in the logs. I have not had the time to debug it.
> > >
> > > What kind of motherboard, video card and processor? Maybe there is
> > > something in common with my system.
> > >
> > > --
> > > fedora-devel-list mailing list
> > > fedora-devel-list(a)redhat.com
> > > https://www.redhat.com/mailman/listinfo/fedora-devel-list
> > >
> >
> >
> >
> > --
> > fedora-devel-list mailing list
> > fedora-devel-list(a)redhat.com
> > https://www.redhat.com/mailman/listinfo/fedora-devel-list
>
> --
> fedora-devel-list mailing list
> fedora-devel-list(a)redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-devel-list
>
--
projecthuh.com
All of my bits are free, are yours? Fedoraproject.org
6:25 p.m.
On Tue, May 6, 2008 at 7:21 PM, Dave Airlie <airlied(a)redhat.com> wrote:
On Tue, 2008-05-06 at 18:30 -0400, Dr. Diesel wrote:
> Just nv since Nvidia's drivers don't yet support xorg 1.5. The only
> kernel module I have loaded is VirtualBox 1.6's.
>
> Filing a bug now..
can you try without virtualbox?
I've seen oops reports from it around the place.
Dave.
Yup, sure can, removed!
6:31 p.m.
On Tue, May 6, 2008 at 7:25 PM, Dr. Diesel <dr.diesel(a)gmail.com> wrote:
On Tue, May 6, 2008 at 7:21 PM, Dave Airlie
<airlied(a)redhat.com> wrote:
> On Tue, 2008-05-06 at 18:30 -0400, Dr. Diesel wrote:
> > Just nv since Nvidia's drivers don't yet support xorg 1.5. The only
> > kernel module I have loaded is VirtualBox 1.6's.
> >
> > Filing a bug now..
>
> can you try without virtualbox?
>
> I've seen oops reports from it around the place.
>
>
>
> Dave.
>
Yup, sure can, removed!
BTW, the module was loaded, but Virtualbox was not running on any of the cases..
--
projecthuh.com
All of my bits are free, are yours? Fedoraproject.org
6:31 p.m.
I've had a lot of freeze problems on my F7 machines. A lot of times it
turns out to be X. If I log in from another machine and run 'top' I can
see X taking 99% cpu. So I kill X and then the system recovers.
Regards,
Gerry
5:58 p.m.
Still happens without the vboxdrv kernel module....
On Tue, May 6, 2008 at 7:21 PM, Dave Airlie <airlied(a)redhat.com> wrote:
On Tue, 2008-05-06 at 18:30 -0400, Dr. Diesel wrote:
> Just nv since Nvidia's drivers don't yet support xorg 1.5. The only
> kernel module I have loaded is VirtualBox 1.6's.
>
> Filing a bug now..
can you try without virtualbox?
I've seen oops reports from it around the place.
Dave.
>
> On Tue, May 6, 2008 at 6:28 PM, Dave Airlie <airlied(a)redhat.com> wrote:
> > On Tue, 2008-05-06 at 18:26 -0400, Dr. Diesel wrote:
> > > Abit 35 Pro , Intel E8400 etc.
> > >
> > > Attached is lscpi -vvv
> >
> > Oh wierd an nvidia card... are you running the binary driver? or just
> > the normal nv one?
> >
> > Dave.
> >
> >
> >
> > >
> > >
> > >
> > > On Tue, May 6, 2008 at 6:21 PM, Alan <alan(a)clueserver.org> wrote:
> > > > > Currently running Fedora 9 Release to date. Doesn't happen
very
> > > > > often, maybe once every 3-4 days. Twice I've caught it at
idle with
> > > > > the screen saver (picture viewer) frozen and twice while
browsing in
> > > > > Gnome.
> > > > >
> > > > > Not really noticing anything weird in the logs?
> > > >
> > > > I have had this happen with Fedora 8 on my x86_64 machine. Nothing
> > > > recorded in the logs. I have not had the time to debug it.
> > > >
> > > > What kind of motherboard, video card and processor? Maybe there is
> > > > something in common with my system.
> > > >
> > > > --
> > > > fedora-devel-list mailing list
> > > > fedora-devel-list(a)redhat.com
> > > > https://www.redhat.com/mailman/listinfo/fedora-devel-list
> > > >
> > >
> > >
> > >
> > > --
> > > fedora-devel-list mailing list
> > > fedora-devel-list(a)redhat.com
> > > https://www.redhat.com/mailman/listinfo/fedora-devel-list
> >
> > --
> > fedora-devel-list mailing list
> > fedora-devel-list(a)redhat.com
> > https://www.redhat.com/mailman/listinfo/fedora-devel-list
> >
>
>
>
> --
> projecthuh.com
> All of my bits are free, are yours? Fedoraproject.org
>
--
fedora-devel-list mailing list
fedora-devel-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
--
projecthuh.com
All of my bits are free, are yours? Fedoraproject.org
6:25 p.m.
On Thu, May 8, 2008 at 4:58 PM, Dr. Diesel <dr.diesel(a)gmail.com> wrote:
Still happens without the vboxdrv kernel module....
was it a rmmod or a reboot of the system without the module? Sometimes
loading a module will much with the kernel enough that removing it is
not enough to make a problem not occur. You might also want to run sar
at 1 minute intervals and see if something like 100% CPU usage etc is
occuring?
--
Stephen J Smoogen. --
How far that little candle throws his beams! So shines a good deed
in a naughty world. = Shakespeare. "The Merchant of Venice"
7:23 p.m.
On Thu, May 8, 2008 at 7:25 PM, Stephen John Smoogen <smooge(a)gmail.com> wrote:
On Thu, May 8, 2008 at 4:58 PM, Dr. Diesel
<dr.diesel(a)gmail.com> wrote:
> Still happens without the vboxdrv kernel module....
>
was it a rmmod or a reboot of the system without the module? Sometimes
loading a module will much with the kernel enough that removing it is
not enough to make a problem not occur. You might also want to run sar
at 1 minute intervals and see if something like 100% CPU usage etc is
occuring?
Ok, vboxdrv now disabled at boot, not just rmmod.
I don't think it was a 100% CPU issue, I was not able to loggin via
SSH either. The number lock and caps lock keys were also
non-responsive also.
--
projecthuh.com
All of my bits are free, are yours? Fedoraproject.org
5:36 a.m.
Ok, that wasn't it either!
Log files don't seem to be showing me anything! Here is messages
about that time:
May 8 21:13:06 localhost dhclient: bound to 192.168.2.37 -- renewal
in 1670 seconds.
May 8 21:40:56 localhost dhclient: DHCPREQUEST on eth1 to 192.168.2.10 port 67
May 8 21:40:56 localhost dhclient: DHCPACK from 192.168.2.10
May 8 21:40:56 localhost dhclient: bound to 192.168.2.37 -- renewal
in 1577 seconds.
May 8 22:07:13 localhost dhclient: DHCPREQUEST on eth1 to 192.168.2.10 port 67
May 8 22:07:13 localhost dhclient: DHCPACK from 192.168.2.10
May 8 22:07:13 localhost dhclient: bound to 192.168.2.37 -- renewal
in 1684 seconds.
May 8 22:35:17 localhost dhclient: DHCPREQUEST on eth1 to 192.168.2.10 port 67
May 8 22:35:17 localhost dhclient: DHCPACK from 192.168.2.10
May 8 22:35:17 localhost dhclient: bound to 192.168.2.37 -- renewal
in 1547 seconds.
May 8 23:01:04 localhost dhclient: DHCPREQUEST on eth1 to 192.168.2.10 port 67
May 8 23:01:04 localhost dhclient: DHCPACK from 192.168.2.10
May 8 23:01:04 localhost dhclient: bound to 192.168.2.37 -- renewal
in 1541 seconds.
May 8 23:08:28 localhost ntpd[1889]: synchronized to 209.193.103.214, stratum 2
May 8 23:26:45 localhost dhclient: DHCPREQUEST on eth1 to 192.168.2.10 port 67
May 8 23:26:45 localhost dhclient: DHCPACK from 192.168.2.10
May 8 23:26:45 localhost dhclient: bound to 192.168.2.37 -- renewal
in 1398 seconds.
May 9 06:26:29 localhost kernel: imklog 3.14.1, log source =
/proc/kmsg started.
On Thu, May 8, 2008 at 7:23 PM, Dr. Diesel <dr.diesel(a)gmail.com> wrote:
On Thu, May 8, 2008 at 7:25 PM, Stephen John Smoogen
<smooge(a)gmail.com> wrote:
> On Thu, May 8, 2008 at 4:58 PM, Dr. Diesel <dr.diesel(a)gmail.com> wrote:
>> Still happens without the vboxdrv kernel module....
>>
>
> was it a rmmod or a reboot of the system without the module? Sometimes
> loading a module will much with the kernel enough that removing it is
> not enough to make a problem not occur. You might also want to run sar
> at 1 minute intervals and see if something like 100% CPU usage etc is
> occuring?
>
Ok, vboxdrv now disabled at boot, not just rmmod.
I don't think it was a 100% CPU issue, I was not able to loggin via
SSH either. The number lock and caps lock keys were also
non-responsive also.
--
projecthuh.com
All of my bits are free, are yours? Fedoraproject.org
--
projecthuh.com
All of my bits are free, are yours? Fedoraproject.org
10:56 a.m.
On one of my machines that was experiencing hard freezes I would notice
that the last thing in the log before the hang was a ntpd time synch.
Don't know why a time synch would cause a hang but every time it was the
last thing before it would hang.
Regards,
Gerry
6:48 a.m.
I'm on my longest run without a crash, the only thing different is I
disabled ntpd and avahi-daemon.
Andy
On Sat, May 10, 2008 at 12:47 AM, Dave Airlie <airlied(a)redhat.com> wrote:
On Fri, 2008-05-09 at 05:36 -0500, Dr. Diesel wrote:
> Ok, that wasn't it either!
try booting with nohz maybe.
crazy but worth a go.
Dave.
--
fedora-devel-list mailing list
fedora-devel-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
--
projecthuh.com
All of my bits are free, are yours? Fedoraproject.org
3:41 p.m.
Finally caught something useful!!! Happened again earlier today!
May 13 11:50:44 localhost dhclient: bound to 192.168.2.37 -- renewal
in 1574 seconds.
May 13 12:11:50 localhost kernel: slideshow[16311]: segfault at 14 ip
3c69238d5f sp 7fff73f4f31f error 6 in
libX11.so.6.2.0[3c69200000+106000]
May 13 12:15:07 localhost kernel: slideshow[16576]: segfault at 14 ip
3c69238d5f sp 7fff680a647f error 6 in
libX11.so.6.2.0[3c69200000+106000]
May 13 12:16:58 localhost dhclient: DHCPREQUEST on eth1 to 192.168.2.10 port 67
May 13 12:16:58 localhost dhclient: DHCPACK from 192.168.2.10
May 13 12:16:58 localhost dhclient: bound to 192.168.2.37 -- renewal
in 1544 seconds.
May 13 12:25:07 localhost kernel: slideshow[16842]: segfault at 14 ip
3c69238d5f sp 7fff52abbe8f error 6 in
libX11.so.6.2.0[3c69200000+106000]
May 13 12:35:07 localhost kernel: slideshow[17107]: segfault at 14 ip
3c69238d5f sp 7fff907edbcf error 6 in
libX11.so.6.2.0[3c69200000+106000]
May 13 14:11:42 localhost kernel: imklog 3.14.1, log source =
/proc/kmsg started.
Andy
On Tue, May 13, 2008 at 7:48 AM, Dr. Diesel <dr.diesel(a)gmail.com> wrote:
I'm on my longest run without a crash, the only thing different
is I
disabled ntpd and avahi-daemon.
Andy
On Sat, May 10, 2008 at 12:47 AM, Dave Airlie <airlied(a)redhat.com> wrote:
>
>
> On Fri, 2008-05-09 at 05:36 -0500, Dr. Diesel wrote:
> > Ok, that wasn't it either!
>
> try booting with nohz maybe.
>
> crazy but worth a go.
>
> Dave.
>
>
>
> --
> fedora-devel-list mailing list
> fedora-devel-list(a)redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-devel-list
>
--
projecthuh.com
All of my bits are free, are yours? Fedoraproject.org
--
projecthuh.com
All of my bits are free, are yours? Fedoraproject.org
9:13 a.m.
All, it is possible that all of these freezes are caused by a failing
hard drive? Perhaps failed during the upgrade from F8 to F9 and its
only 3 months old!! Mmmmm, just my luck!
Last night I suddenly began to receive Kerneloops after Kerneloops,
4-5 total then it hard locked. When I went to reboot I got the error
couldn't find /sys /root etc, couldn't find any of the logical
volumes. I tried rebooting it several times and finally it made it to
doing an automatic fsck that fails at about 4%. SMART says the HD is
fine. I'll have to pull the drive to retrieve and log files, assuming
I'm able to read anything!
I don't think its a CPU/memory issues as it will run
memtest86/folding@home for 12+ hours without errors. This is not an
overclocked system.
Anyhow, failing HD sound possible?
Thanks
Andy
On Tue, May 13, 2008 at 3:41 PM, Dr. Diesel <dr.diesel(a)gmail.com> wrote:
Finally caught something useful!!! Happened again earlier today!
May 13 11:50:44 localhost dhclient: bound to 192.168.2.37 -- renewal
in 1574 seconds.
May 13 12:11:50 localhost kernel: slideshow[16311]: segfault at 14 ip
3c69238d5f sp 7fff73f4f31f error 6 in
libX11.so.6.2.0[3c69200000+106000]
May 13 12:15:07 localhost kernel: slideshow[16576]: segfault at 14 ip
3c69238d5f sp 7fff680a647f error 6 in
libX11.so.6.2.0[3c69200000+106000]
May 13 12:16:58 localhost dhclient: DHCPREQUEST on eth1 to 192.168.2.10 port 67
May 13 12:16:58 localhost dhclient: DHCPACK from 192.168.2.10
May 13 12:16:58 localhost dhclient: bound to 192.168.2.37 -- renewal
in 1544 seconds.
May 13 12:25:07 localhost kernel: slideshow[16842]: segfault at 14 ip
3c69238d5f sp 7fff52abbe8f error 6 in
libX11.so.6.2.0[3c69200000+106000]
May 13 12:35:07 localhost kernel: slideshow[17107]: segfault at 14 ip
3c69238d5f sp 7fff907edbcf error 6 in
libX11.so.6.2.0[3c69200000+106000]
May 13 14:11:42 localhost kernel: imklog 3.14.1, log source =
/proc/kmsg started.
Andy
On Tue, May 13, 2008 at 7:48 AM, Dr. Diesel <dr.diesel(a)gmail.com> wrote:
> I'm on my longest run without a crash, the only thing different is I
> disabled ntpd and avahi-daemon.
>
> Andy
>
>
>
> On Sat, May 10, 2008 at 12:47 AM, Dave Airlie <airlied(a)redhat.com> wrote:
> >
> >
> > On Fri, 2008-05-09 at 05:36 -0500, Dr. Diesel wrote:
> > > Ok, that wasn't it either!
> >
> > try booting with nohz maybe.
> >
> > crazy but worth a go.
> >
> > Dave.
> >
> >
> >
> > --
> > fedora-devel-list mailing list
> > fedora-devel-list(a)redhat.com
> > https://www.redhat.com/mailman/listinfo/fedora-devel-list
> >
>
>
>
> --
>
>
> projecthuh.com
> All of my bits are free, are yours? Fedoraproject.org
>
--
projecthuh.com
All of my bits are free, are yours? Fedoraproject.org
--
projecthuh.com
All of my bits are free, are yours? Fedoraproject.org
9:20 a.m.
Dr. Diesel wrote:
All, it is possible that all of these freezes are caused by a
failing
hard drive? Perhaps failed during the upgrade from F8 to F9 and its
only 3 months old!! Mmmmm, just my luck!
Last night I suddenly began to receive Kerneloops after Kerneloops,
4-5 total then it hard locked. When I went to reboot I got the error
couldn't find /sys /root etc, couldn't find any of the logical
volumes. I tried rebooting it several times and finally it made it to
doing an automatic fsck that fails at about 4%. SMART says the HD is
fine.
Note that the overall SMART health status is near useless. What you
should do is look at the disk error log :
# smartctl -l error /dev/sda
and run a short and/or long self test (short is couple of mins, long is
typically 1 to 2 hours):
# smartctl -t long /dev/sda
# smartctl -t short /dev/sda
Results of the self test after completion:
# smartctl -l selftest /dev/sda
You may want to do this from a live CD if your system is really unstable.
4:59 p.m.
Thanks for the input!
I ran smartctl -t long and found no errors, did it several times!
fsck found a zillion errors, is it possible this is still a bug issue?
Thanks
Andy
On Wed, May 14, 2008 at 10:20 AM, Denis Leroy <denis(a)poolshark.org> wrote:
Dr. Diesel wrote:
>
> All, it is possible that all of these freezes are caused by a failing
> hard drive? Perhaps failed during the upgrade from F8 to F9 and its
> only 3 months old!! Mmmmm, just my luck!
>
> Last night I suddenly began to receive Kerneloops after Kerneloops,
> 4-5 total then it hard locked. When I went to reboot I got the error
> couldn't find /sys /root etc, couldn't find any of the logical
> volumes. I tried rebooting it several times and finally it made it to
> doing an automatic fsck that fails at about 4%. SMART says the HD is
> fine.
Note that the overall SMART health status is near useless. What you should
do is look at the disk error log :
# smartctl -l error /dev/sda
and run a short and/or long self test (short is couple of mins, long is
typically 1 to 2 hours):
# smartctl -t long /dev/sda
# smartctl -t short /dev/sda
Results of the self test after completion:
# smartctl -l selftest /dev/sda
You may want to do this from a live CD if your system is really unstable.
--
fedora-devel-list mailing list
fedora-devel-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
--
projecthuh.com
All of my bits are free, are yours? Fedoraproject.org
4:33 p.m.
And more!
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A
mtrr: no MTRR for d0000000,ff00000 found
console-kit-dae[2420]: segfault at 8 ip 3c67e2a699 sp 4100fff0 error 4
in libglib-2.0.so.0.1600.3[3c67e00000+de000]
mtrr: base(0xd0000000) is not aligned on a size(0xff00000) boundary
Andy
On Wed, May 14, 2008 at 5:59 PM, Dr. Diesel <dr.diesel(a)gmail.com> wrote:
Thanks for the input!
I ran smartctl -t long and found no errors, did it several times!
fsck found a zillion errors, is it possible this is still a bug issue?
Thanks
Andy
On Wed, May 14, 2008 at 10:20 AM, Denis Leroy <denis(a)poolshark.org> wrote:
> Dr. Diesel wrote:
>>
>> All, it is possible that all of these freezes are caused by a failing
>> hard drive? Perhaps failed during the upgrade from F8 to F9 and its
>> only 3 months old!! Mmmmm, just my luck!
>>
>> Last night I suddenly began to receive Kerneloops after Kerneloops,
>> 4-5 total then it hard locked. When I went to reboot I got the error
>> couldn't find /sys /root etc, couldn't find any of the logical
>> volumes. I tried rebooting it several times and finally it made it to
>> doing an automatic fsck that fails at about 4%. SMART says the HD is
>> fine.
>
> Note that the overall SMART health status is near useless. What you should
> do is look at the disk error log :
>
> # smartctl -l error /dev/sda
>
> and run a short and/or long self test (short is couple of mins, long is
> typically 1 to 2 hours):
>
> # smartctl -t long /dev/sda
> # smartctl -t short /dev/sda
>
> Results of the self test after completion:
>
> # smartctl -l selftest /dev/sda
>
> You may want to do this from a live CD if your system is really unstable.
>
> --
> fedora-devel-list mailing list
> fedora-devel-list(a)redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-devel-list
>
--
projecthuh.com
All of my bits are free, are yours? Fedoraproject.org
--
projecthuh.com
All of my bits are free, are yours? Fedoraproject.org
5:01 p.m.
On Thu, May 15, 2008 at 05:33:02PM -0400, Dr. Diesel wrote:
And more!
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A
mtrr: no MTRR for d0000000,ff00000 found
console-kit-dae[2420]: segfault at 8 ip 3c67e2a699 sp 4100fff0 error 4
in libglib-2.0.so.0.1600.3[3c67e00000+de000]
mtrr: base(0xd0000000) is not aligned on a size(0xff00000) boundary
Out of curiosity what does memtest86 think of the box. A mix of random memory
and disk corruptions is a good candidate for suspecting RAM (although it's
certainly not conclusive and it could be an FC9 triggered bug)
8:47 p.m.
Alan Cox escreveu:
On Thu, May 15, 2008 at 05:33:02PM -0400, Dr. Diesel wrote:
> And more!
>
> ISO 9660 Extensions: Microsoft Joliet Level 3
> ISO 9660 Extensions: RRIP_1991A
> mtrr: no MTRR for d0000000,ff00000 found
> console-kit-dae[2420]: segfault at 8 ip 3c67e2a699 sp 4100fff0 error 4
> in libglib-2.0.so.0.1600.3[3c67e00000+de000]
> mtrr: base(0xd0000000) is not aligned on a size(0xff00000) boundary
>
Out of curiosity what does memtest86 think of the box. A mix of random memory
and disk corruptions is a good candidate for suspecting RAM (although it's
certainly not conclusive and it could be an FC9 triggered bug)
I installed OK (upgraded over a Fedora Rel 8 using DVD).
Kernel XEN boots to the point that the message "Releasing VGA" appears.
Then it freezes (a poweroff is necessary because system don't catch
keyboard IRQs).
System is: ASUS PS800-MX SE with 2 160GBytes SATA, two 80GBytes ATA and
a RTL8139 additional network board. RAM is 2GBytes.
11:50 p.m.
I am having the same issue here. Booting the xen kernel just freezes
there with that VGA message.
2008/5/16 Casimiro de Almeida Barreto <casimiro.barreto(a)gmail.com>:
Alan Cox escreveu:
On Thu, May 15, 2008 at 05:33:02PM -0400, Dr. Diesel wrote:
And more!
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A
mtrr: no MTRR for d0000000,ff00000 found
console-kit-dae[2420]: segfault at 8 ip 3c67e2a699 sp 4100fff0 error 4
in libglib-2.0.so.0.1600.3[3c67e00000+de000]
mtrr: base(0xd0000000) is not aligned on a size(0xff00000) boundary
Out of curiosity what does memtest86 think of the box. A mix of random
memory
and disk corruptions is a good candidate for suspecting RAM (although it's
certainly not conclusive and it could be an FC9 triggered bug)
I installed OK (upgraded over a Fedora Rel 8 using DVD).
Kernel XEN boots to the point that the message "Releasing VGA" appears. Then
it freezes (a poweroff is necessary because system don't catch keyboard
IRQs).
System is: ASUS PS800-MX SE with 2 160GBytes SATA, two 80GBytes ATA and a
RTL8139 additional network board. RAM is 2GBytes.
--
fedora-devel-list mailing list
fedora-devel-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
--
Enjoy Life !
7:03 a.m.
On Thu, May 15, 2008 at 5:01 PM, Alan Cox <alan(a)redhat.com> wrote:
On Thu, May 15, 2008 at 05:33:02PM -0400, Dr. Diesel wrote:
> And more!
>
> ISO 9660 Extensions: Microsoft Joliet Level 3
> ISO 9660 Extensions: RRIP_1991A
> mtrr: no MTRR for d0000000,ff00000 found
> console-kit-dae[2420]: segfault at 8 ip 3c67e2a699 sp 4100fff0 error 4
> in libglib-2.0.so.0.1600.3[3c67e00000+de000]
> mtrr: base(0xd0000000) is not aligned on a size(0xff00000) boundary
Out of curiosity what does memtest86 think of the box. A mix of random memory
and disk corruptions is a good candidate for suspecting RAM (although it's
certainly not conclusive and it could be an FC9 triggered bug)
That figures! I ran memtest86 and folding for 12+ hours when the
freezing first started, no errors. I re-run it last night at your
request and get an error! Only one, at the top, 2049meg, ran it
several times, all that the same place.
Probably why I only see the freezes after a few days. I'll report
back if it makes a week or so with no issues.
Thanks to all.
--
projecthuh.com
All of my bits are free, are yours? Fedoraproject.org
5:22 p.m.
Well, 24 hours of memtest86 show no errors (27 passes), system is
still hosed! Is there any other tests to prove this isn't a hardware
failure? I do see amarok in messages but i don't think its been
running on all lockup occasion.
Please Help!
messages:
May 21 17:53:47 localhost kernel: BUG: unable to handle kernel paging
request at 00000000001200d2
May 21 17:53:47 localhost kernel: IP: [__d_lookup+246/285] __d_lookup+0xf6/0x11d
May 21 17:53:47 localhost kernel: PGD 2e08c067 PUD 10e6b067 PMD 2b4b5067 PTE 0
May 21 17:53:47 localhost kernel: Oops: 0000 [21] SMP
May 21 17:53:47 localhost kernel: CPU 0
May 21 17:53:47 localhost kernel: Modules linked in: nfs lockd nfs_acl
coretemp w83627ehf hwmon_vid hwmon fuse sunrpc ipt_REJECT xt_tcpudp
nf_conntrack_ipv4 xt_state nf_conntrack iptable_filter ip_tables
x_tables loop dm_multipath ipv6 snd_hda_intel snd_seq_dummy
snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss
snd_mixer_oss snd_pcm snd_timer firewire_ohci snd_page_alloc snd_hwdep
firewire_core r8169 snd pata_jmicron crc_itu_t pl2303 pata_acpi
i2c_i801 usb_storage iTCO_wdt pcspkr usbserial bay button i2c_core
ata_generic soundcore iTCO_vendor_support sg floppy dm_snapshot
dm_zero dm_mirror dm_mod ahci libata sd_mod scsi_mod ext3 jbd mbcache
uhci_hcd ohci_hcd ehci_hcd [last unloaded: microcode]
May 21 17:53:47 localhost kernel: Pid: 12207, comm: amarokcollectio
Tainted: G D 2.6.25.3-18.fc9.x86_64 #1
May 21 17:53:47 localhost kernel: RIP: 0010:[__d_lookup+246/285]
[__d_lookup+246/285] __d_lookup+0xf6/0x11d
May 21 17:53:47 localhost kernel: RSP: 0018:ffff810010e4bb08 EFLAGS: 00010206
May 21 17:53:47 localhost kernel: RAX: 00000000001200d2 RBX:
ffff810013db0ea0 RCX: 0000000000000011
May 21 17:53:47 localhost kernel: RDX: 000000000001c256 RSI:
ffff810010e4bbf8 RDI: ffff81003f443ea0
May 21 17:53:47 localhost kernel: RBP: ffff810010e4bb58 R08:
0000000000000000 R09: 0000000000000000
May 21 17:53:47 localhost kernel: R10: 0000000000000003 R11:
ffff81002508f390 R12: 00000000001200d2
May 21 17:53:47 localhost kernel: R13: ffff81003f443ea0 R14:
ffff810010e4bbf8 R15: 0000000099fa0098
May 21 17:53:47 localhost kernel: FS: 0000000000000000(0000)
GS:ffffffff813f6000(0000) knlGS:0000000000000000
May 21 17:53:47 localhost kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
0000000080050033
May 21 17:53:47 localhost kernel: CR2: 00000000001200d2 CR3:
0000000010e69000 CR4: 00000000000006e0
May 21 17:53:47 localhost kernel: DR0: 0000000000000000 DR1:
0000000000000000 DR2: 0000000000000000
May 21 17:53:47 localhost kernel: DR3: 0000000000000000 DR6:
00000000ffff0ff0 DR7: 0000000000000400
May 21 17:53:47 localhost kernel: Process amarokcollectio (pid: 12207,
threadinfo ffff810010e4a000, task ffff81000f34a000)
May 21 17:53:47 localhost kernel: Stack: 000000000000000f
0000000f3f5441ed ffff810026d50900 ffffffff8104184a
May 21 17:53:47 localhost kernel: 00000000001200d2 0000000000000000
ffff810010e4be88 ffff81003f54e3c8
May 21 17:53:47 localhost kernel: ffff810026d50900 ffff810010e4be88
ffff810010e4bba8 ffffffff810ac3fc
May 21 17:53:47 localhost kernel: Call Trace:
May 21 17:53:47 localhost kernel: [in_group_p+42/44] ? in_group_p+0x2a/0x2c
May 21 17:53:47 localhost kernel: [do_lookup+44/424] do_lookup+0x2c/0x1a8
May 21 17:53:47 localhost kernel: [__link_path_walk+2481/3731]
__link_path_walk+0x9b1/0xe93
May 21 17:53:47 localhost kernel: [touch_atime+131/274] ?
touch_atime+0x83/0x112
May 21 17:53:47 localhost kernel: [__link_path_walk+3133/3731]
__link_path_walk+0xc3d/0xe93
May 21 17:53:47 localhost kernel: [path_walk+97/195] path_walk+0x61/0xc3
May 21 17:53:47 localhost kernel: [do_path_lookup+470/561]
do_path_lookup+0x1d6/0x231
May 21 17:53:47 localhost kernel: [__path_lookup_intent_open+92/159]
__path_lookup_intent_open+0x5c/0x9f
May 21 17:53:47 localhost kernel: [path_lookup_open+12/14]
path_lookup_open+0xc/0xe
May 21 17:53:47 localhost kernel: [open_namei+118/1696] open_namei+0x76/0x6a0
May 21 17:53:47 localhost kernel: [do_filp_open+40/75] do_filp_open+0x28/0x4b
May 21 17:53:47 localhost kernel: [__strncpy_from_user+44/83] ?
__strncpy_from_user+0x2c/0x53
May 21 17:53:47 localhost kernel: [get_unused_fd_flags+139/287] ?
get_unused_fd_flags+0x8b/0x11f
May 21 17:53:47 localhost kernel: [do_sys_open+81/210] do_sys_open+0x51/0xd2
May 21 17:53:47 localhost kernel: [sys_open+27/29] sys_open+0x1b/0x1d
May 21 17:53:47 localhost kernel: [tracesys+213/218] tracesys+0xd5/0xda
May 21 17:53:47 localhost kernel:
May 21 17:53:47 localhost kernel:
May 21 17:53:47 localhost kernel: Code: 04 10 75 06 f0 ff 03 48 89 d8
fe 43 08 eb 34 41 fe 44 24 f0 48 8b 45 d0 48 8b 00 48 89 45 d0 48 8b
45 d0 48 85 c0 74 19 49 89 c4 <48> 8b 00 49 8d 5c 24 e8 44 39 7b 30 0f
18 08 75 d8 e9 65 ff ff
May 21 17:53:47 localhost kernel: RIP [__d_lookup+246/285]
__d_lookup+0xf6/0x11d
May 21 17:53:47 localhost kernel: RSP <ffff810010e4bb08>
May 21 17:53:47 localhost kernel: CR2: 00000000001200d2
May 21 17:53:47 localhost kernel: ---[ end trace c2ff9cce82980cc9 ]---
May 21 17:53:49 localhost kerneloops: Submitted 1 kernel oopses to
www.kerneloops.org
Dmesg:
BUG: unable to handle kernel paging request at 00000000001200d2
IP: [<ffffffff810b6273>] __d_lookup+0xf6/0x11d
PGD 2e088067 PUD 10f70067 PMD 2dd90067 PTE 0
Oops: 0000 [18] SMP
CPU 0
Modules linked in: nfs lockd nfs_acl coretemp w83627ehf hwmon_vid
hwmon fuse sunrpc ipt_REJECT xt_tcpudp nf_conntrack_ipv4 xt_state
nf_conntrack iptable_filter ip_tables x_tables loop dm_multipath ipv6
snd_hda_intel snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq
snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm snd_timer
firewire_ohci snd_page_alloc snd_hwdep firewire_core r8169 snd
pata_jmicron crc_itu_t pl2303 pata_acpi i2c_i801 usb_storage iTCO_wdt
pcspkr usbserial bay button i2c_core ata_generic soundcore
iTCO_vendor_support sg floppy dm_snapshot dm_zero dm_mirror dm_mod
ahci libata sd_mod scsi_mod ext3 jbd mbcache uhci_hcd ohci_hcd
ehci_hcd [last unloaded: microcode]
Pid: 12190, comm: amarokcollectio Tainted: G D 2.6.25.3-18.fc9.x86_64 #1
RIP: 0010:[<ffffffff810b6273>] [<ffffffff810b6273>] __d_lookup+0xf6/0x11d
RSP: 0018:ffff810010f5fb08 EFLAGS: 00010206
RAX: 00000000001200d2 RBX: ffff810013db0ea0 RCX: 0000000000000011
RDX: 000000000001c256 RSI: ffff810010f5fbf8 RDI: ffff81003f443ea0
RBP: ffff810010f5fb58 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000003 R11: ffff81002508f390 R12: 00000000001200d2
R13: ffff81003f443ea0 R14: ffff810010f5fbf8 R15: 0000000099fa0098
FS: 0000000000000000(0000) GS:ffffffff813f6000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000001200d2 CR3: 0000000010e45000 CR4: 00000000000006e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process amarokcollectio (pid: 12190, threadinfo ffff810010f5e000, task
ffff810010e26000)
Stack: 000000000000000f 0000000f3f5441ed ffff810026d50900 ffffffff8104184a
00000000001200d2 0000000000000000 ffff810010f5fe88 ffff81003f54e3c8
ffff810026d50900 ffff810010f5fe88 ffff810010f5fba8 ffffffff810ac3fc
Call Trace:
[<ffffffff8104184a>] ? in_group_p+0x2a/0x2c
[<ffffffff810ac3fc>] do_lookup+0x2c/0x1a8
[<ffffffff810ae699>] __link_path_walk+0x9b1/0xe93
[<ffffffff810b76f8>] ? touch_atime+0x83/0x112
[<ffffffff810ae925>] __link_path_walk+0xc3d/0xe93
[<ffffffff810aebdc>] path_walk+0x61/0xc3
[<ffffffff810aefda>] do_path_lookup+0x1d6/0x231
[<ffffffff810af2e9>] __path_lookup_intent_open+0x5c/0x9f
[<ffffffff810af338>] path_lookup_open+0xc/0xe
[<ffffffff810afe06>] open_namei+0x76/0x6a0
[<ffffffff810a3787>] do_filp_open+0x28/0x4b
[<ffffffff81132b05>] ? __strncpy_from_user+0x2c/0x53
[<ffffffff810a3430>] ? get_unused_fd_flags+0x8b/0x11f
[<ffffffff810a37fb>] do_sys_open+0x51/0xd2
[<ffffffff810a38a5>] sys_open+0x1b/0x1d
[<ffffffff8100c052>] tracesys+0xd5/0xda
Code: 04 10 75 06 f0 ff 03 48 89 d8 fe 43 08 eb 34 41 fe 44 24 f0 48
8b 45 d0 48 8b 00 48 89 45 d0 48 8b 45 d0 48 85 c0 74 19 49 89 c4 <48>
8b 00 49 8d 5c 24 e8 44 39 7b 30 0f 18 08 75 d8 e9 65 ff ff
RIP [<ffffffff810b6273>] __d_lookup+0xf6/0x11d
RSP <ffff810010f5fb08>
CR2: 00000000001200d2
---[ end trace c2ff9cce82980cc9 ]---
On Fri, May 16, 2008 at 8:03 AM, Dr. Diesel <dr.diesel(a)gmail.com> wrote:
On Thu, May 15, 2008 at 5:01 PM, Alan Cox <alan(a)redhat.com>
wrote:
> On Thu, May 15, 2008 at 05:33:02PM -0400, Dr. Diesel wrote:
>> And more!
>>
>> ISO 9660 Extensions: Microsoft Joliet Level 3
>> ISO 9660 Extensions: RRIP_1991A
>> mtrr: no MTRR for d0000000,ff00000 found
>> console-kit-dae[2420]: segfault at 8 ip 3c67e2a699 sp 4100fff0 error 4
>> in libglib-2.0.so.0.1600.3[3c67e00000+de000]
>> mtrr: base(0xd0000000) is not aligned on a size(0xff00000) boundary
>
> Out of curiosity what does memtest86 think of the box. A mix of random memory
> and disk corruptions is a good candidate for suspecting RAM (although it's
> certainly not conclusive and it could be an FC9 triggered bug)
That figures! I ran memtest86 and folding for 12+ hours when the
freezing first started, no errors. I re-run it last night at your
request and get an error! Only one, at the top, 2049meg, ran it
several times, all that the same place.
Probably why I only see the freezes after a few days. I'll report
back if it makes a week or so with no issues.
Thanks to all.
--
projecthuh.com
All of my bits are free, are yours? Fedoraproject.org
--
projecthuh.com
All of my bits are free, are yours? Fedoraproject.org
12:37 p.m.
All,
Even though memtest86 would run fine for > 24 hours without error I up
and decided to swap on the memory. Since I've no lockups or
weirdness, I'm fairly confidant the memory was the issue.
Thanks
Andy
On Wed, May 21, 2008 at 6:22 PM, Dr. Diesel <dr.diesel(a)gmail.com> wrote:
Well, 24 hours of memtest86 show no errors (27 passes), system is
still hosed! Is there any other tests to prove this isn't a hardware
failure? I do see amarok in messages but i don't think its been
running on all lockup occasion.
Please Help!
messages:
May 21 17:53:47 localhost kernel: BUG: unable to handle kernel paging
request at 00000000001200d2
May 21 17:53:47 localhost kernel: IP: [__d_lookup+246/285] __d_lookup+0xf6/0x11d
May 21 17:53:47 localhost kernel: PGD 2e08c067 PUD 10e6b067 PMD 2b4b5067 PTE 0
May 21 17:53:47 localhost kernel: Oops: 0000 [21] SMP
May 21 17:53:47 localhost kernel: CPU 0
May 21 17:53:47 localhost kernel: Modules linked in: nfs lockd nfs_acl
coretemp w83627ehf hwmon_vid hwmon fuse sunrpc ipt_REJECT xt_tcpudp
nf_conntrack_ipv4 xt_state nf_conntrack iptable_filter ip_tables
x_tables loop dm_multipath ipv6 snd_hda_intel snd_seq_dummy
snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss
snd_mixer_oss snd_pcm snd_timer firewire_ohci snd_page_alloc snd_hwdep
firewire_core r8169 snd pata_jmicron crc_itu_t pl2303 pata_acpi
i2c_i801 usb_storage iTCO_wdt pcspkr usbserial bay button i2c_core
ata_generic soundcore iTCO_vendor_support sg floppy dm_snapshot
dm_zero dm_mirror dm_mod ahci libata sd_mod scsi_mod ext3 jbd mbcache
uhci_hcd ohci_hcd ehci_hcd [last unloaded: microcode]
May 21 17:53:47 localhost kernel: Pid: 12207, comm: amarokcollectio
Tainted: G D 2.6.25.3-18.fc9.x86_64 #1
May 21 17:53:47 localhost kernel: RIP: 0010:[__d_lookup+246/285]
[__d_lookup+246/285] __d_lookup+0xf6/0x11d
May 21 17:53:47 localhost kernel: RSP: 0018:ffff810010e4bb08 EFLAGS: 00010206
May 21 17:53:47 localhost kernel: RAX: 00000000001200d2 RBX:
ffff810013db0ea0 RCX: 0000000000000011
May 21 17:53:47 localhost kernel: RDX: 000000000001c256 RSI:
ffff810010e4bbf8 RDI: ffff81003f443ea0
May 21 17:53:47 localhost kernel: RBP: ffff810010e4bb58 R08:
0000000000000000 R09: 0000000000000000
May 21 17:53:47 localhost kernel: R10: 0000000000000003 R11:
ffff81002508f390 R12: 00000000001200d2
May 21 17:53:47 localhost kernel: R13: ffff81003f443ea0 R14:
ffff810010e4bbf8 R15: 0000000099fa0098
May 21 17:53:47 localhost kernel: FS: 0000000000000000(0000)
GS:ffffffff813f6000(0000) knlGS:0000000000000000
May 21 17:53:47 localhost kernel: CS: 0010 DS: 0000 ES: 0000 CR0:
0000000080050033
May 21 17:53:47 localhost kernel: CR2: 00000000001200d2 CR3:
0000000010e69000 CR4: 00000000000006e0
May 21 17:53:47 localhost kernel: DR0: 0000000000000000 DR1:
0000000000000000 DR2: 0000000000000000
May 21 17:53:47 localhost kernel: DR3: 0000000000000000 DR6:
00000000ffff0ff0 DR7: 0000000000000400
May 21 17:53:47 localhost kernel: Process amarokcollectio (pid: 12207,
threadinfo ffff810010e4a000, task ffff81000f34a000)
May 21 17:53:47 localhost kernel: Stack: 000000000000000f
0000000f3f5441ed ffff810026d50900 ffffffff8104184a
May 21 17:53:47 localhost kernel: 00000000001200d2 0000000000000000
ffff810010e4be88 ffff81003f54e3c8
May 21 17:53:47 localhost kernel: ffff810026d50900 ffff810010e4be88
ffff810010e4bba8 ffffffff810ac3fc
May 21 17:53:47 localhost kernel: Call Trace:
May 21 17:53:47 localhost kernel: [in_group_p+42/44] ? in_group_p+0x2a/0x2c
May 21 17:53:47 localhost kernel: [do_lookup+44/424] do_lookup+0x2c/0x1a8
May 21 17:53:47 localhost kernel: [__link_path_walk+2481/3731]
__link_path_walk+0x9b1/0xe93
May 21 17:53:47 localhost kernel: [touch_atime+131/274] ?
touch_atime+0x83/0x112
May 21 17:53:47 localhost kernel: [__link_path_walk+3133/3731]
__link_path_walk+0xc3d/0xe93
May 21 17:53:47 localhost kernel: [path_walk+97/195] path_walk+0x61/0xc3
May 21 17:53:47 localhost kernel: [do_path_lookup+470/561]
do_path_lookup+0x1d6/0x231
May 21 17:53:47 localhost kernel: [__path_lookup_intent_open+92/159]
__path_lookup_intent_open+0x5c/0x9f
May 21 17:53:47 localhost kernel: [path_lookup_open+12/14]
path_lookup_open+0xc/0xe
May 21 17:53:47 localhost kernel: [open_namei+118/1696] open_namei+0x76/0x6a0
May 21 17:53:47 localhost kernel: [do_filp_open+40/75] do_filp_open+0x28/0x4b
May 21 17:53:47 localhost kernel: [__strncpy_from_user+44/83] ?
__strncpy_from_user+0x2c/0x53
May 21 17:53:47 localhost kernel: [get_unused_fd_flags+139/287] ?
get_unused_fd_flags+0x8b/0x11f
May 21 17:53:47 localhost kernel: [do_sys_open+81/210] do_sys_open+0x51/0xd2
May 21 17:53:47 localhost kernel: [sys_open+27/29] sys_open+0x1b/0x1d
May 21 17:53:47 localhost kernel: [tracesys+213/218] tracesys+0xd5/0xda
May 21 17:53:47 localhost kernel:
May 21 17:53:47 localhost kernel:
May 21 17:53:47 localhost kernel: Code: 04 10 75 06 f0 ff 03 48 89 d8
fe 43 08 eb 34 41 fe 44 24 f0 48 8b 45 d0 48 8b 00 48 89 45 d0 48 8b
45 d0 48 85 c0 74 19 49 89 c4 <48> 8b 00 49 8d 5c 24 e8 44 39 7b 30 0f
18 08 75 d8 e9 65 ff ff
May 21 17:53:47 localhost kernel: RIP [__d_lookup+246/285]
__d_lookup+0xf6/0x11d
May 21 17:53:47 localhost kernel: RSP <ffff810010e4bb08>
May 21 17:53:47 localhost kernel: CR2: 00000000001200d2
May 21 17:53:47 localhost kernel: ---[ end trace c2ff9cce82980cc9 ]---
May 21 17:53:49 localhost kerneloops: Submitted 1 kernel oopses to
www.kerneloops.org
Dmesg:
BUG: unable to handle kernel paging request at 00000000001200d2
IP: [<ffffffff810b6273>] __d_lookup+0xf6/0x11d
PGD 2e088067 PUD 10f70067 PMD 2dd90067 PTE 0
Oops: 0000 [18] SMP
CPU 0
Modules linked in: nfs lockd nfs_acl coretemp w83627ehf hwmon_vid
hwmon fuse sunrpc ipt_REJECT xt_tcpudp nf_conntrack_ipv4 xt_state
nf_conntrack iptable_filter ip_tables x_tables loop dm_multipath ipv6
snd_hda_intel snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq
snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm snd_timer
firewire_ohci snd_page_alloc snd_hwdep firewire_core r8169 snd
pata_jmicron crc_itu_t pl2303 pata_acpi i2c_i801 usb_storage iTCO_wdt
pcspkr usbserial bay button i2c_core ata_generic soundcore
iTCO_vendor_support sg floppy dm_snapshot dm_zero dm_mirror dm_mod
ahci libata sd_mod scsi_mod ext3 jbd mbcache uhci_hcd ohci_hcd
ehci_hcd [last unloaded: microcode]
Pid: 12190, comm: amarokcollectio Tainted: G D 2.6.25.3-18.fc9.x86_64 #1
RIP: 0010:[<ffffffff810b6273>] [<ffffffff810b6273>] __d_lookup+0xf6/0x11d
RSP: 0018:ffff810010f5fb08 EFLAGS: 00010206
RAX: 00000000001200d2 RBX: ffff810013db0ea0 RCX: 0000000000000011
RDX: 000000000001c256 RSI: ffff810010f5fbf8 RDI: ffff81003f443ea0
RBP: ffff810010f5fb58 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000003 R11: ffff81002508f390 R12: 00000000001200d2
R13: ffff81003f443ea0 R14: ffff810010f5fbf8 R15: 0000000099fa0098
FS: 0000000000000000(0000) GS:ffffffff813f6000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000001200d2 CR3: 0000000010e45000 CR4: 00000000000006e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process amarokcollectio (pid: 12190, threadinfo ffff810010f5e000, task
ffff810010e26000)
Stack: 000000000000000f 0000000f3f5441ed ffff810026d50900 ffffffff8104184a
00000000001200d2 0000000000000000 ffff810010f5fe88 ffff81003f54e3c8
ffff810026d50900 ffff810010f5fe88 ffff810010f5fba8 ffffffff810ac3fc
Call Trace:
[<ffffffff8104184a>] ? in_group_p+0x2a/0x2c
[<ffffffff810ac3fc>] do_lookup+0x2c/0x1a8
[<ffffffff810ae699>] __link_path_walk+0x9b1/0xe93
[<ffffffff810b76f8>] ? touch_atime+0x83/0x112
[<ffffffff810ae925>] __link_path_walk+0xc3d/0xe93
[<ffffffff810aebdc>] path_walk+0x61/0xc3
[<ffffffff810aefda>] do_path_lookup+0x1d6/0x231
[<ffffffff810af2e9>] __path_lookup_intent_open+0x5c/0x9f
[<ffffffff810af338>] path_lookup_open+0xc/0xe
[<ffffffff810afe06>] open_namei+0x76/0x6a0
[<ffffffff810a3787>] do_filp_open+0x28/0x4b
[<ffffffff81132b05>] ? __strncpy_from_user+0x2c/0x53
[<ffffffff810a3430>] ? get_unused_fd_flags+0x8b/0x11f
[<ffffffff810a37fb>] do_sys_open+0x51/0xd2
[<ffffffff810a38a5>] sys_open+0x1b/0x1d
[<ffffffff8100c052>] tracesys+0xd5/0xda
Code: 04 10 75 06 f0 ff 03 48 89 d8 fe 43 08 eb 34 41 fe 44 24 f0 48
8b 45 d0 48 8b 00 48 89 45 d0 48 8b 45 d0 48 85 c0 74 19 49 89 c4 <48>
8b 00 49 8d 5c 24 e8 44 39 7b 30 0f 18 08 75 d8 e9 65 ff ff
RIP [<ffffffff810b6273>] __d_lookup+0xf6/0x11d
RSP <ffff810010f5fb08>
CR2: 00000000001200d2
---[ end trace c2ff9cce82980cc9 ]---
On Fri, May 16, 2008 at 8:03 AM, Dr. Diesel <dr.diesel(a)gmail.com> wrote:
> On Thu, May 15, 2008 at 5:01 PM, Alan Cox <alan(a)redhat.com> wrote:
>> On Thu, May 15, 2008 at 05:33:02PM -0400, Dr. Diesel wrote:
>>> And more!
>>>
>>> ISO 9660 Extensions: Microsoft Joliet Level 3
>>> ISO 9660 Extensions: RRIP_1991A
>>> mtrr: no MTRR for d0000000,ff00000 found
>>> console-kit-dae[2420]: segfault at 8 ip 3c67e2a699 sp 4100fff0 error 4
>>> in libglib-2.0.so.0.1600.3[3c67e00000+de000]
>>> mtrr: base(0xd0000000) is not aligned on a size(0xff00000) boundary
>>
>> Out of curiosity what does memtest86 think of the box. A mix of random memory
>> and disk corruptions is a good candidate for suspecting RAM (although it's
>> certainly not conclusive and it could be an FC9 triggered bug)
>
> That figures! I ran memtest86 and folding for 12+ hours when the
> freezing first started, no errors. I re-run it last night at your
> request and get an error! Only one, at the top, 2049meg, ran it
> several times, all that the same place.
>
> Probably why I only see the freezes after a few days. I'll report
> back if it makes a week or so with no issues.
>
> Thanks to all.
>
> --
> projecthuh.com
> All of my bits are free, are yours? Fedoraproject.org
>
--
projecthuh.com
All of my bits are free, are yours? Fedoraproject.org
--
projecthuh.com
All of my bits are free, are yours? Fedoraproject.org
1 p.m.
2008/5/27 Dr. Diesel <dr.diesel(a)gmail.com>:
All,
Even though memtest86 would run fine for > 24 hours without error I up
and decided to swap on the memory. Since I've no lockups or
weirdness, I'm fairly confidant the memory was the issue.
That would suggest, perhaps, that when memtest is running, very little
else in the system is active (e.g. disks aren't doing anything,
graphics card is not drawing much power for acceleration blocks etc)
... which might indicate that your power supply isn't quite up to the
job. Glad it's working now though.
5:24 p.m.
Dr. Diesel wrote:
Currently running Fedora 9 Release to date. Doesn't happen very
often, maybe once every 3-4 days. Twice I've caught it at idle with
the screen saver (picture viewer) frozen and twice while browsing in
Gnome.
Not really noticing anything weird in the logs?
Haven't had a freeze yet but I have seen a couple weird things with X.
Twice now my cursor just went to either the upper right corner or the
lower right corner. If you try to move it somewhere it just goes back
to the corner in a jerky motion. Very strange.
Regards,
Gerry
11:43 p.m.
Gerry Reno wrote:
Dr. Diesel wrote:
> Currently running Fedora 9 Release to date. Doesn't happen very
> often, maybe once every 3-4 days. Twice I've caught it at idle with
> the screen saver (picture viewer) frozen and twice while browsing in
> Gnome.
>
> Not really noticing anything weird in the logs?
>
>
Haven't had a freeze yet but I have seen a couple weird things with X.
Twice now my cursor just went to either the upper right corner or the
lower right corner. If you try to move it somewhere it just goes back
to the corner in a jerky motion. Very strange.
I think that could be several mouse or input devices sending core events,
fighting each other for where the cursor should go. Do you have more than one
mouse attached? Do you have more input devices (maybe pseudo devices) showing
up in the Xorg.0.log? Maybe that issue is an auto-configured input problem.
--
Andrew Farris <lordmorgul(a)gmail.com> www.lordmorgul.net
gpg 0x8300BF29 fingerprint 071D FFE0 4CBC 13FC 7DEB 5BD5 5F89 8E1B 8300 BF29
5:25 p.m.
On Tue, 2008-05-06 at 17:55 -0400, Dr. Diesel wrote:
Currently running Fedora 9 Release to date. Doesn't happen very
often, maybe once every 3-4 days. Twice I've caught it at idle with
the screen saver (picture viewer) frozen and twice while browsing in
Gnome.
Not really noticing anything weird in the logs?
AMD 64-bit + ATI AGP card?
please open a bug and attach some lspci and /var/log/Xorg.0.log stuff as
my mind reading abilities suck this morning.
Dave.
5:29 p.m.
[stalwart@delta ~]$ uptime
01:27:18 up 19 days, 1:06, 14 users, load average: 0.32, 0.29, 0.26
[stalwart@delta ~]$ cat /etc/fedora-release
Fedora release 9 (Sulphur)
[stalwart@delta ~]$ uname -a
Linux delta 2.6.25-0.218.rc8.git7.fc9.x86_64 #1 SMP Wed Apr 9 19:55:19
EDT 2008 x86_64 x86_64 x86_64 GNU/Linux
19 days of web development, movies, music, web browsing, packaging,
patching, hacking and what not. System is rock stable.
CPU: Intel Core2Quad Q6600
Video: NVIDIA GeForce 8600GT, driver - nouveau
On 5/7/08, Dave Airlie <airlied(a)redhat.com> wrote:
On Tue, 2008-05-06 at 17:55 -0400, Dr. Diesel wrote:
> Currently running Fedora 9 Release to date. Doesn't happen very
> often, maybe once every 3-4 days. Twice I've caught it at idle with
> the screen saver (picture viewer) frozen and twice while browsing in
> Gnome.
>
> Not really noticing anything weird in the logs?
AMD 64-bit + ATI AGP card?
please open a bug and attach some lspci and /var/log/Xorg.0.log stuff as
my mind reading abilities suck this morning.
Dave.
--
fedora-devel-list mailing list
fedora-devel-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
--
http://scwlab.com
5:32 p.m.
Ah yes, my mobo is P35. Dr., is yours too?
On 5/7/08, Pavel Shevchuk <stlwrt(a)gmail.com> wrote:
[stalwart@delta ~]$ uptime
01:27:18 up 19 days, 1:06, 14 users, load average: 0.32, 0.29, 0.26
[stalwart@delta ~]$ cat /etc/fedora-release
Fedora release 9 (Sulphur)
[stalwart@delta ~]$ uname -a
Linux delta 2.6.25-0.218.rc8.git7.fc9.x86_64 #1 SMP Wed Apr 9 19:55:19
EDT 2008 x86_64 x86_64 x86_64 GNU/Linux
19 days of web development, movies, music, web browsing, packaging,
patching, hacking and what not. System is rock stable.
CPU: Intel Core2Quad Q6600
Video: NVIDIA GeForce 8600GT, driver - nouveau
On 5/7/08, Dave Airlie <airlied(a)redhat.com> wrote:
> On Tue, 2008-05-06 at 17:55 -0400, Dr. Diesel wrote:
> > Currently running Fedora 9 Release to date. Doesn't happen very
> > often, maybe once every 3-4 days. Twice I've caught it at idle with
> > the screen saver (picture viewer) frozen and twice while browsing in
> > Gnome.
> >
> > Not really noticing anything weird in the logs?
>
>
> AMD 64-bit + ATI AGP card?
>
> please open a bug and attach some lspci and /var/log/Xorg.0.log stuff as
> my mind reading abilities suck this morning.
>
>
>
> Dave.
>
>
> --
> fedora-devel-list mailing list
> fedora-devel-list(a)redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-devel-list
>
--
http://scwlab.com
--
http://scwlab.com
5:34 p.m.
I also have VBox 1.6 installed for few days already (didn't reboot
since installation), run linux and windows in it, no problems at all
On 5/7/08, Pavel Shevchuk <stlwrt(a)gmail.com> wrote:
Ah yes, my mobo is P35. Dr., is yours too?
On 5/7/08, Pavel Shevchuk <stlwrt(a)gmail.com> wrote:
> [stalwart@delta ~]$ uptime
> 01:27:18 up 19 days, 1:06, 14 users, load average: 0.32, 0.29, 0.26
> [stalwart@delta ~]$ cat /etc/fedora-release
> Fedora release 9 (Sulphur)
> [stalwart@delta ~]$ uname -a
> Linux delta 2.6.25-0.218.rc8.git7.fc9.x86_64 #1 SMP Wed Apr 9 19:55:19
> EDT 2008 x86_64 x86_64 x86_64 GNU/Linux
>
> 19 days of web development, movies, music, web browsing, packaging,
> patching, hacking and what not. System is rock stable.
>
> CPU: Intel Core2Quad Q6600
> Video: NVIDIA GeForce 8600GT, driver - nouveau
>
>
> On 5/7/08, Dave Airlie <airlied(a)redhat.com> wrote:
> > On Tue, 2008-05-06 at 17:55 -0400, Dr. Diesel wrote:
> > > Currently running Fedora 9 Release to date. Doesn't happen very
> > > often, maybe once every 3-4 days. Twice I've caught it at idle
with
> > > the screen saver (picture viewer) frozen and twice while browsing in
> > > Gnome.
> > >
> > > Not really noticing anything weird in the logs?
> >
> >
> > AMD 64-bit + ATI AGP card?
> >
> > please open a bug and attach some lspci and /var/log/Xorg.0.log stuff as
> > my mind reading abilities suck this morning.
> >
> >
> >
> > Dave.
> >
> >
> > --
> > fedora-devel-list mailing list
> > fedora-devel-list(a)redhat.com
> > https://www.redhat.com/mailman/listinfo/fedora-devel-list
> >
>
>
>
> --
> http://scwlab.com
>
--
http://scwlab.com
--
http://scwlab.com
5:35 p.m.
Yea, Abit IP35 Pro,
https://bugzilla.redhat.com/show_bug.cgi?id=445458
On Tue, May 6, 2008 at 6:32 PM, Pavel Shevchuk <stlwrt(a)gmail.com> wrote:
Ah yes, my mobo is P35. Dr., is yours too?
On 5/7/08, Pavel Shevchuk <stlwrt(a)gmail.com> wrote:
> [stalwart@delta ~]$ uptime
> 01:27:18 up 19 days, 1:06, 14 users, load average: 0.32, 0.29, 0.26
> [stalwart@delta ~]$ cat /etc/fedora-release
> Fedora release 9 (Sulphur)
> [stalwart@delta ~]$ uname -a
> Linux delta 2.6.25-0.218.rc8.git7.fc9.x86_64 #1 SMP Wed Apr 9 19:55:19
> EDT 2008 x86_64 x86_64 x86_64 GNU/Linux
>
> 19 days of web development, movies, music, web browsing, packaging,
> patching, hacking and what not. System is rock stable.
>
> CPU: Intel Core2Quad Q6600
> Video: NVIDIA GeForce 8600GT, driver - nouveau
>
>
> On 5/7/08, Dave Airlie <airlied(a)redhat.com> wrote:
> > On Tue, 2008-05-06 at 17:55 -0400, Dr. Diesel wrote:
> > > Currently running Fedora 9 Release to date. Doesn't happen very
> > > often, maybe once every 3-4 days. Twice I've caught it at idle
with
> > > the screen saver (picture viewer) frozen and twice while browsing in
> > > Gnome.
> > >
> > > Not really noticing anything weird in the logs?
> >
> >
> > AMD 64-bit + ATI AGP card?
> >
> > please open a bug and attach some lspci and /var/log/Xorg.0.log stuff as
> > my mind reading abilities suck this morning.
> >
> >
> >
> > Dave.
> >
> >
> > --
7:56 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dr. Diesel wrote:
Currently running Fedora 9 Release to date. Doesn't happen very
often, maybe once every 3-4 days. Twice I've caught it at idle with
the screen saver (picture viewer) frozen and twice while browsing in
Gnome.
Not really noticing anything weird in the logs?
I had one last night, running jaaa (spectrum analyzer) on the input from a USB sound
device, so lots of 2d graphics activity. System just locked, power button time.
Lenovo T60
Core2 Duo T7200 2.00GHz
3GB Ram
$ uname -a
Linux torg 2.6.25-14.fc9.x86_64 #1 SMP Thu May 1 06:06:21 EDT 2008 x86_64 x86_64
x86_64 GNU/Linux
I'd suspended to RAM and resumed a number of times before this happened. Nothing
readily apparent in my logs. I'll try and get some better info if it happens again.
Clark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iEYEARECAAYFAkghpxsACgkQHyuj/+TTEp0RQgCdHmy2ufkvaDCxwhcJUr/T6grc
VUEAnjZ/XLovWwZlQb8a+eWKh+cYPzpg
=9eYg
-----END PGP SIGNATURE-----
9:09 a.m.
On Tue, May 06, 2008 at 05:55:38PM -0400, Dr. Diesel wrote:
Currently running Fedora 9 Release to date. Doesn't happen very
often, maybe once every 3-4 days. Twice I've caught it at idle with
the screen saver (picture viewer) frozen and twice while browsing in
Gnome.
Not really noticing anything weird in the logs?
I've been running into hangs
for a long time on my laptop.
Seems to be related to something in the utrace patchset (not totally proven
though). nohz=off makes the problem go away (25 days uptime with
2.6.25-0.218.rc8.git7.fc9 :-) )
Would be nice to see SOMEONE being able to reproduce the same issue,
it's only this one laptop I've seen it on, nearly identical X31
didn't show any issues.
https://bugzilla.redhat.com/show_bug.cgi?id=283161 for the details.
--
Pekka Pietikainen
9:25 a.m.
On Thursday 08 May 2008 10:09:10 am Pekka Pietikainen wrote:
On Tue, May 06, 2008 at 05:55:38PM -0400, Dr. Diesel wrote:
> Currently running Fedora 9 Release to date. Doesn't happen very
> often, maybe once every 3-4 days. Twice I've caught it at idle with
> the screen saver (picture viewer) frozen and twice while browsing in
> Gnome.
>
> Not really noticing anything weird in the logs?
I've been running into hangs for a long time on my laptop.
Seems to be related to something in the utrace patchset (not totally proven
though). nohz=off makes the problem go away (25 days uptime with
2.6.25-0.218.rc8.git7.fc9 :-) )
Would be nice to see SOMEONE being able to reproduce the same issue,
it's only this one laptop I've seen it on, nearly identical X31
didn't show any issues.
https://bugzilla.redhat.com/show_bug.cgi?id=283161 for the details.
Might be worth trying out a 2.6.25.2 build, there are a number of scheduler
fixes that went in post-2.6.25. There's a 2.6.25.2 (plus what's in the queue
for 2.6.25.3) build that was done in dist-f10 last night. Right now, dist-f10
is still mostly the same thing as dist-f9, so there shouldn't be any issues
running this kernel on an F9 system -- I'm running it on my own otherwise f9
laptop w/o a problem (but then again, I didn't have any problems with prior
kernels either).
http://koji.fedoraproject.org/packages/kernel/2.6.25.2/5.fc10/
--
Jarod Wilson
jwilson(a)redhat.com
5824
days inactive
5845
days old
37 comments
15 participants
participants (15)
-
Alan -
Alan Cox -
Andrew Farris -
Andy Lawrence -
Bill Crawford -
casimiro barreto -
Clark Williams -
David Airlie -
Deependra Singh Shekhawat -
Denis Leroy -
Gerry Reno -
Jarod Wilson -
Pavel Shevchuk -
Pekka Pietikäinen -
Stephen John Smoogen