Is it just me, or is kernel-2.6.5-1.332 bust? On an SMP i686 box it hangs as init starts, on x86_64 it goes into an oops loop at initrd load time.
On Tue, 2004-04-20 at 15:47, Alex Kiernan wrote:
Is it just me, or is kernel-2.6.5-1.332 bust?
Working fine here, though I've only tried it on UP Athlon so far.
On an SMP i686 box it hangs as init starts
Does it work if you boot with vdso=0 ? If it does, then your glibc is too old.
on x86_64 it goes into an oops loop at initrd load time.
That's an unknown one. Please bugzilla.
Thanks,
Dave
Dave Jones davej@redhat.com writes:
On Tue, 2004-04-20 at 15:47, Alex Kiernan wrote:
On an SMP i686 box it hangs as init starts
Does it work if you boot with vdso=0 ? If it does, then your glibc is too old.
Can't check right now, but I'll give it a go later - I've got glibc-2.3.3-22 according to rpm -q.
on x86_64 it goes into an oops loop at initrd load time.
That's an unknown one. Please bugzilla.
Will do. I don't have the box on a serial console at the moment - any ideas on ways I can usefully grab any detail?
On Tue, 2004-04-20 at 16:18, Alex Kiernan wrote:
Does it work if you boot with vdso=0 ? If it does, then your glibc is too old
Can't check right now, but I'll give it a go later - I've got glibc-2.3.3-22 according to rpm -q.
Hmm, same here, so that probably isn't it. Puzzling.
That's an unknown one. Please bugzilla.
Will do. I don't have the box on a serial console at the moment - any ideas on ways I can usefully grab any detail?
Worse case you could always take a picture of it if you've a digital camera handy. I don't usually encourage this, but it's better than nothing as a last resort.
Dave
Dave Jones davej@redhat.com writes:
On Tue, 2004-04-20 at 16:18, Alex Kiernan wrote:
Does it work if you boot with vdso=0 ? If it does, then your glibc is too old
Can't check right now, but I'll give it a go later - I've got glibc-2.3.3-22 according to rpm -q.
Hmm, same here, so that probably isn't it. Puzzling.
Booting w/ vdso=0 fixes it
That's an unknown one. Please bugzilla.
Will do. I don't have the box on a serial console at the moment - any ideas on ways I can usefully grab any detail?
Worse case you could always take a picture of it if you've a digital camera handy. I don't usually encourage this, but it's better than nothing as a last resort.
Thats bad :)
I'll get a serial console on it - its local, I just need to find the right cables for my laptop.
On Tue, 2004-04-20 at 17:06, Alex Kiernan wrote:
Dave Jones davej@redhat.com writes:
On Tue, 2004-04-20 at 16:18, Alex Kiernan wrote:
Does it work if you boot with vdso=0 ? If it does, then your glibc is too old
Can't check right now, but I'll give it a go later - I've got glibc-2.3.3-22 according to rpm -q.
Hmm, same here, so that probably isn't it. Puzzling.
Booting w/ vdso=0 fixes it
Wow, that is freaky. Another one for you to bugzilla please 8-)
Worse case you could always take a picture of it if you've a digital camera handy. I don't usually encourage this, but it's better than nothing as a last resort.
Thats bad :) I'll get a serial console on it - its local, I just need to find the right cables for my laptop.
Thanks for the effort.
Dave
Dave Jones davej@redhat.com writes:
On Tue, 2004-04-20 at 17:06, Alex Kiernan wrote:
Dave Jones davej@redhat.com writes:
On Tue, 2004-04-20 at 16:18, Alex Kiernan wrote:
Does it work if you boot with vdso=0 ? If it does, then your glibc is too old
Can't check right now, but I'll give it a go later - I've got glibc-2.3.3-22 according to rpm -q.
Hmm, same here, so that probably isn't it. Puzzling.
Booting w/ vdso=0 fixes it
Wow, that is freaky. Another one for you to bugzilla please 8-)
OK - I'll check first it wasn't a fluke.
Worse case you could always take a picture of it if you've a digital camera handy. I don't usually encourage this, but it's better than nothing as a last resort.
Thats bad :) I'll get a serial console on it - its local, I just need to find the right cables for my laptop.
Thanks for the effort.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=121350
On Tue, Apr 20, 2004 at 05:06:39PM +0100, Alex Kiernan wrote:
Will do. I don't have the box on a serial console at the moment - any ideas on ways I can usefully grab any detail?
Worse case you could always take a picture of it if you've a digital camera handy. I don't usually encourage this, but it's better than nothing as a last resort.
Thats bad :)
I'll get a serial console on it - its local, I just need to find the right cables for my laptop.
Got serial console on a few of my boxes, the oops is below. Do we have a bug # for this one yet? If not, let me know and I will bugzilla it.
Thanks, Justin
I installed the kernel update today on four different machines. I haven't seen the kernel oops on the i686 boxes, but I am experiencing huge problems.
1. On an SMP system(Dell PE 2650, Dual P4 2.6Ghz), the network connectivity to two of them(tg3) is extrememly slow and is dropping packets left and right. I could barely get into the machines to change the grub.conf back to the previous release and reboot.
2. On one of the SMP systems, NIS stopped working(maybe due to the network problems?.
3. On a PIII 850Mhz, there are no problems with the intel 10/100 adaptors and the system seems to be running fine.
Can I provide any other feedback, or should I tag these problems onto bugzilla #121350?
On Tue, 2004-04-20 at 10:56, Justin M. Forbes wrote:
On Tue, Apr 20, 2004 at 05:06:39PM +0100, Alex Kiernan wrote:
Will do. I don't have the box on a serial console at the moment - any ideas on ways I can usefully grab any detail?
Worse case you could always take a picture of it if you've a digital camera handy. I don't usually encourage this, but it's better than nothing as a last resort.
Thats bad :)
I'll get a serial console on it - its local, I just need to find the right cables for my laptop.
Got serial console on a few of my boxes, the oops is below. Do we have a bug # for this one yet? If not, let me know and I will bugzilla it.
Thanks, Justin
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-test-list
Alex Kiernan alex.kiernan@thus.net writes:
Dave Jones davej@redhat.com writes:
On Tue, 2004-04-20 at 17:06, Alex Kiernan wrote:
Dave Jones davej@redhat.com writes:
On Tue, 2004-04-20 at 16:18, Alex Kiernan wrote:
Does it work if you boot with vdso=0 ? If it does, then your glibc is too old
Can't check right now, but I'll give it a go later - I've got glibc-2.3.3-22 according to rpm -q.
Hmm, same here, so that probably isn't it. Puzzling.
Booting w/ vdso=0 fixes it
Wow, that is freaky. Another one for you to bugzilla please 8-)
OK - I'll check first it wasn't a fluke.
It was a fluke - rebooting this morning, w/ -332 and w/o vdso=0 its fine; looks like a strange one off which just chose to happen that time.
On Apr 20, 2004, Sean Bruno sean.bruno@dsl-only.net wrote:
I installed the kernel update today on four different machines. I haven't seen the kernel oops on the i686 boxes, but I am experiencing huge problems.
- On an SMP system(Dell PE 2650, Dual P4 2.6Ghz), the network
connectivity to two of them(tg3) is extrememly slow and is dropping packets left and right. I could barely get into the machines to change the grub.conf back to the previous release and reboot.
- On one of the SMP systems, NIS stopped working(maybe due to the
network problems?.
- On a PIII 850Mhz, there are no problems with the intel 10/100
adaptors and the system seems to be running fine.
Can I provide any other feedback, or should I tag these problems onto bugzilla #121350?
The problem I've had on 5 different boxes was filesystem I/O.
strace showed lstat64 system calls would take forever to complete (quite often 5-10 seconds); then a burst of progress was made and then it came to a halt again. Hard disk leds confirmed this access pattern, except for one of the boxes that had two disks in RAID 1 resyncing, whose disk access was constant. Very odd.
Alex Kiernan alex.kiernan@thus.net writes:
Dave Jones davej@redhat.com writes:
On Tue, 2004-04-20 at 17:06, Alex Kiernan wrote:
Dave Jones davej@redhat.com writes:
Worse case you could always take a picture of it if you've a digital camera handy. I don't usually encourage this, but it's better than nothing as a last resort.
Thats bad :) I'll get a serial console on it - its local, I just need to find the right cables for my laptop.
Thanks for the effort.
Just tried the current bk tree - it boots/runs fine, so whatever the problem was looks like its fixed upstream or its some problem the Fedora patches introduce.
On Mon, 2004-04-26 at 15:13, Alex Kiernan wrote:
Worse case you could always take a picture of it if you've a digital camera handy. I don't usually encourage this, but it's better than nothing as a last resort.
Thats bad :) I'll get a serial console on it - its local, I just need to find the right cables for my laptop.
Thanks for the effort.
Just tried the current bk tree - it boots/runs fine, so whatever the problem was looks like its fixed upstream or its some problem the Fedora patches introduce.
Hmm, more head scratching. We're going to do one final rebase to 2.6.6 when that's out later this week, and that's what we're rolling with for FC2 GA, (Additional patches from upstream will be cherry-picked).
Will be interesting to see if the next kernel that we push out fixes it for you too. If it doesn't, then it is something we added which is bogus.
Dave
Dave Jones davej@redhat.com writes:
On Mon, 2004-04-26 at 15:13, Alex Kiernan wrote:
Worse case you could always take a picture of it if you've a digital camera handy. I don't usually encourage this, but it's better than nothing as a last resort.
Thats bad :) I'll get a serial console on it - its local, I just need to find the right cables for my laptop.
Thanks for the effort.
Just tried the current bk tree - it boots/runs fine, so whatever the problem was looks like its fixed upstream or its some problem the Fedora patches introduce.
Hmm, more head scratching. We're going to do one final rebase to 2.6.6 when that's out later this week, and that's what we're rolling with for FC2 GA, (Additional patches from upstream will be cherry-picked).
Will be interesting to see if the next kernel that we push out fixes it for you too. If it doesn't, then it is something we added which is bogus.
2.6.5-1.349 is working fine, so whatever it was it looks like its fixed.
I saw a strange one with FC2T3 while rebuilding a kernel on a Armada M700 laptop.
* use ssh to login with two separate sessions (normal user acct). * use "su -" to become root on both sessions.
In one case the first 'su -' worked fine, but the second session would abort the 'su -' command after the first char of the root password was entered. I was unable to 'su -' a second session over ssh and had to use the laptop keyboard/display instead.
ron
I have tried this message _three_ times and still have not received a reply.
In FC2, will ESD only support ALSA or will it support ALSA and OSS? I insist on using the OSS drivers because the ALSA snd-intel8x0 driver _sucks_ on my laptop (ACPI conflicts, poor sound quality, etc).
Someone please let me know whats up with ESD.
Brian Smith
On Wed, 2004-05-05 at 15:01 -0400, Brian R Smith wrote:
I have tried this message _three_ times and still have not received a reply.
In FC2, will ESD only support ALSA or will it support ALSA and OSS? I insist on using the OSS drivers because the ALSA snd-intel8x0 driver _sucks_ on my laptop (ACPI conflicts, poor sound quality, etc).
Someone please let me know whats up with ESD.
Can't give a direct answer as I don't know, and sympathize with your frustration, but can only offer some suggestions to increase the probability of getting an answer:
1. Read http://www.catb.org/~esr/faqs/smart-questions.html
2. Don't SHOUT.
3. Fix your clock (or mail transport?) so your message is not showing it's from several days in the past.
Phil
-
Alex Kiernan -
Alexandre Oliva -
Brian R Smith -
Dave Jones -
Justin M. Forbes -
Phil Schaffner -
ron flory -
Sean Bruno