I've completed a 2.6.13 kernel rebase, and pushed out a test kernel to fc4-updates-testing. (FC3 probably won't get another rebase before EOL).
Please give this a try on your systems, and file any bugs that you happen upon in bugzilla.
You can also find interim 'snapshot' builds at http://people.redhat.com/davej/kernels/Fedora/FC4/ which may fix additional problems since the last updates-testing release.
I'm hoping to get this pushed out fairly soon depending upon the feedback I get from how well this kernel works out.
Thanks,
Dave
On Fri, 2005-09-23 at 21:49 -0400, Dave Jones wrote:
I've completed a 2.6.13 kernel rebase, and pushed out a test kernel to fc4-updates-testing. (FC3 probably won't get another rebase before EOL).
Cool. Does this include the new not-so-nice-yet PCMCIA stuff? I ask this because yum doesn't want to install pcmciautils or the like when I enable the updates-testing repo and run `yum update kernel`.
I'm downloading the RPM now. Thanks for all your hard work. :)
On Fri, Sep 23, 2005 at 07:33:01PM -0700, Peter Gordon wrote:
On Fri, 2005-09-23 at 21:49 -0400, Dave Jones wrote:
I've completed a 2.6.13 kernel rebase, and pushed out a test kernel to fc4-updates-testing. (FC3 probably won't get another rebase before EOL).
Cool. Does this include the new not-so-nice-yet PCMCIA stuff? I ask this because yum doesn't want to install pcmciautils or the like when I enable the updates-testing repo and run `yum update kernel`.
No, I'm playing it safe for FC4 and going with 'minimal change'. For the shiny new toys, either jump into rawhide, or wait until FC5.
The problem with the new stuff is the pain of updating userspace. It's guaranteed to break some configurations, and FC4 is supposedly our 'stable' release right now.
Dave
On Fri, 2005-09-23 at 22:47 -0400, Dave Jones wrote:
No, I'm playing it safe for FC4 and going with 'minimal change'. For the shiny new toys, either jump into rawhide, or wait until FC5.
I appreciate that very much. I could never get the new PCMCIA subsystem to play nice with my old Prism2 wireless ethernet card. 2.6.13-1.1524_FC4 seems to work just lovely for me though.
The problem with the new stuff is the pain of updating userspace. It's guaranteed to break some configurations, and FC4 is supposedly our 'stable' release right now.
I agree. I hope this small issue is fixed in the later kernels and in FC5. In either case, thanks for your hard work on this, Dave.
Dave Jones wrote:
I've completed a 2.6.13 kernel rebase, and pushed out a test kernel to fc4-updates-testing. (FC3 probably won't get another rebase before EOL).
Please give this a try on your systems, and file any bugs that you happen upon in bugzilla.
You can also find interim 'snapshot' builds at http://people.redhat.com/davej/kernels/Fedora/FC4/ which may fix additional problems since the last updates-testing release.
I'm hoping to get this pushed out fairly soon depending upon the feedback I get from how well this kernel works out.
Thanks,
Dave
What is the best way to narrow down bug reports for particular kernel versions and distribution versions?
Jim
This list is too long for Bugzilla's little mind; the Next/Prev/First/Last buttons won't appear on individual bugs.
2172 bugs found.
On Fri, Sep 23, 2005 at 10:34:29PM -0400, Jim Cornette wrote:
What is the best way to narrow down bug reports for particular kernel versions and distribution versions?
This list is too long for Bugzilla's little mind; the Next/Prev/First/Last buttons won't appear on individual bugs.
2172 bugs found.
Heh, that must be every kernel bug across every release we have open. If you click the advanced tab in the search page, you can narrow it down to a specific release.
For the curious, here's how the kernel bugcount across fedora releases has looked the last few weeks..
| FC3 | FC4 |devel| ------+-----+-----+-----+ Jul29 | 616 | 256 | 170 | Aug06 | 585 | 261 | 165 | Aug14 | 580 | 275 | 171 | Aug26 | 559 | 294 | 177 | Aug29 | 555 | 278 | 174 | <- FC3/FC4 kernel minor update. Sep 5 | 552 | 303 | 173 | Sep10 | 550 | 311 | 178 | Sep16 | 547 | 323 | 182 | Sep23 | 543 | 322 | 182 | <- FC3/FC4 kernel minor update.
The obvious trend here is that FC3 bugs are dropping off, whilst FC4 is increasing.
Given that they're both pretty much the same kernel, my guess is that more people are starting to migrate over from FC3 as it nears its end of life.
Dave
| FC3 | FC4 |devel|
------+-----+-----+-----+ Jul29 | 616 | 256 | 170 | Aug06 | 585 | 261 | 165 | Aug14 | 580 | 275 | 171 | Aug26 | 559 | 294 | 177 | Aug29 | 555 | 278 | 174 | <- FC3/FC4 kernel minor update. Sep 5 | 552 | 303 | 173 | Sep10 | 550 | 311 | 178 | Sep16 | 547 | 323 | 182 | Sep23 | 543 | 322 | 182 | <- FC3/FC4 kernel minor update.
i couldn't help but chartify this. attached.
On Fri, 23 Sep 2005, Dave Jones wrote:
I've completed a 2.6.13 kernel rebase, and pushed out a test kernel to fc4-updates-testing. (FC3 probably won't get another rebase before EOL).
Please give this a try on your systems, and file any bugs that you happen upon in bugzilla.
You can also find interim 'snapshot' builds at http://people.redhat.com/davej/kernels/Fedora/FC4/ which may fix additional problems since the last updates-testing release.
I'm hoping to get this pushed out fairly soon depending upon the feedback I get from how well this kernel works out.
Thanks,
Dave
Does this purport to fix the ibm_acpi module bug?
On Sat, 24 Sep 2005 07:48:37 +0300, Matthew Saltzman mjs@ces.clemson.edu wrote:
Hi
On Fri, 23 Sep 2005, Dave Jones wrote:
I've completed a 2.6.13 kernel rebase, and pushed out a test kernel to fc4-updates-testing. (FC3 probably won't get another rebase before EOL).
Please give this a try on your systems, and file any bugs that you happen upon in bugzilla.
You can also find interim 'snapshot' builds at http://people.redhat.com/davej/kernels/Fedora/FC4/ which may fix additional problems since the last updates-testing release.
I'm hoping to get this pushed out fairly soon depending upon the feedback I get from how well this kernel works out.
Thanks,
Dave
Does this purport to fix the ibm_acpi module bug?
Just installed on a T21. ibm_acpi seems to be fixed, loads fine (v0.8). Also v0.11 works :) [root@purgatory acpi]# tail -3 /var/log/messages Sep 24 14:03:10 purgatory kernel: ibm_acpi: IBM ThinkPad ACPI Extras v0.11 Sep 24 14:03:10 purgatory kernel: ibm_acpi: http://ibm-acpi.sf.net/ Sep 24 14:03:10 purgatory kernel: ibm_acpi: dock device not present [root@purgatory acpi]# ls /proc/acpi/ibm/ bay bluetooth cmos driver fan led thermal volume beep brightness dock ecdump hotkey light video [root@purgatory acpi]#
Also ACPI seems to be fixed since the machine reboot AND shuts down properly. Maybe add to https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=165819 ???
But ... [root@purgatory acx]# modprobe e100 FATAL: Error inserting e100 (/lib/modules/2.6.13-1.1524_FC4/kernel/drivers/net/e100.ko): Unknown symbol in module, or unknown parameter (see dmesg) [root@purgatory acx]# dmesg |tail JoinBSSID MAC:00:13:10:02:6D:04 acx_set_status(4):ASSOCIATED ASSOCIATED! acx_i_timer: priv->status=4 (ASSOCIATED) get_mask 0x00000000, set_mask 0x00000040 setting RXconfig to 2010:0FDD get_mask 0x00000000, set_mask 0x00000000 - after update spurious 8259A interrupt: IRQ7. wlan0: rx: 6 DUPs in 60 packets received in 10 secs e100: Unknown parameter `irq' [root@purgatory acx]# lsmod |grep e100 [root@purgatory acx]#
There was another error about cardmgr but I didnt write it down and cant find anything in the logs now. I'll try and get it somehow. PCMCIA works fine though.
Hope all this helps. Regards
Efthym
On Sat, Sep 24, 2005 at 02:07:48PM +0300, Efthym wrote:
e100: Unknown parameter `irq'
Your /etc/modprobe.conf probably has an irq line in it for this module. Which is odd, as this module has never supported that parameter as far as I can tell.
What has changed though is that we're now failing on unknown params instead of ignoring them. I should probably fix that up for the FC4 kernel.
Dave
On Sat, 24 Sep 2005 21:09:24 +0300, Dave Jones davej@redhat.com wrote:
On Sat, Sep 24, 2005 at 02:07:48PM +0300, Efthym wrote:
e100: Unknown parameter `irq'
Your /etc/modprobe.conf probably has an irq line in it for this module. Which is odd, as this module has never supported that parameter as far as I can tell.
What has changed though is that we're now failing on unknown params instead of ignoring them. I should probably fix that up for the FC4 kernel.
Dave
You're right. there was an "options e100 irq=11" in my modprobe.conf. Don't know how it got there, but I know that it's gone now :). This was disregarded by previous kernels.
Thanks for the tip
Efthym
Hi Dave!
Am Freitag, den 23.09.2005, 21:49 -0400 schrieb Dave Jones:
You can also find interim 'snapshot' builds at http://people.redhat.com/davej/kernels/Fedora/FC4/ which may fix additional problems since the last updates-testing release.
AFAICS there is still no support for yum from FC4 in your repo :-(
Without it is nearly useless IMHO...
CU thl
Quoting Thorsten Leemhuis fedora@leemhuis.info:
AFAICS there is still no support for yum from FC4 in your repo :-(
Without it is nearly useless IMHO...
Kernels deserve special attention, so as long as the new kernel doesn't involve a long list of dependencies yum doesn't add much. In any case, it is very simple to create your own local repos, using createrepo (8) (Create repomd (xml-rpm-metadata) repository).
Am Samstag, den 24.09.2005, 11:22 -0300 schrieb George White:
Quoting Thorsten Leemhuis fedora@leemhuis.info:
AFAICS there is still no support for yum from FC4 in your repo :-(
Without it is nearly useless IMHO...
Kernels deserve special attention, so as long as the new kernel doesn't involve a long list of dependencies yum doesn't add much.
I disagree.
In any case, it is very simple to create your own local repos, using createrepo (8) (Create repomd (xml-rpm-metadata) repository).
Consider me as a person that always wants to test the latest kernel that davej releases at the above place. What works better for me: The current scheme:
scheme 1: - think "hey, maybe davej released a new kernel" - fire up you browser - go to the repo from davej - check manually if there is a new kernel - download it. wait for download - fire up a shell - rpm -ivh new-kernel.rpm (and don#t type rpm -Uvh here accidentally)
or scheme 2:
- put a repo file below /etc/yum.repo once - always get the new kernel from davej-repo when I do a yum update, If something breaks I can easily go back to an older kernel.
or scheme 3, for users that don't always want to install kernels from that repo
- put a repo file below /etc/yum.repo once, that is disabled by default - think "hey, maybe davej released a new kernel" - run something like "yum --enablerepo=davej-test-kernels update kernel"
Scheme 2 is best for me. I'd like to run it to help testing this kernels. But even scheme 3 is a lot easier for most people than scheme 1. And easier here means IMHO: Kernel gets more testing.
And yes, surely I can mirror that repo and add a createrepo as part of the mirroring. <sarcasm>Sounds like a really really good idea to me. Why don't we do that for updates and rawhide, too? </sarcasm>^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W But that is unneeded overhead IMHO. I complicates things without need.
-thorsten "insert a jef-spaleta-like-sentence here" leemhuis
On Sat, Sep 24, 2005 at 11:55:39AM +0200, Thorsten Leemhuis wrote:
Hi Dave!
Am Freitag, den 23.09.2005, 21:49 -0400 schrieb Dave Jones:
You can also find interim 'snapshot' builds at http://people.redhat.com/davej/kernels/Fedora/FC4/ which may fix additional problems since the last updates-testing release.
AFAICS there is still no support for yum from FC4 in your repo :-(
Yeah, the box that creates the repodata has an ancient version of yum, which doesn't know how to create the newer metadata.
Dave
On Fri, 2005-09-23 at 21:49 -0400, Dave Jones wrote:
I've completed a 2.6.13 kernel rebase, and pushed out a test kernel to fc4-updates-testing. (FC3 probably won't get another rebase before EOL).
Please give this a try on your systems, and file any bugs that you happen upon in bugzilla.
You can also find interim 'snapshot' builds at http://people.redhat.com/davej/kernels/Fedora/FC4/ which may fix additional problems since the last updates-testing release.
I'm hoping to get this pushed out fairly soon depending upon the feedback I get from how well this kernel works out.
I've been having trouble with kernel version 2.6.12-1.1456_FC4, so I downloaded 2.6.13-1.1525_FC4 and tried it. It seems to be broken in the same way, namely:
Hardware: CPU: AMD Athlon(tm) 64 Processor 3000+ running at 3 GHz Video Card: Sapphire Card running ATI RV280 [Radeon 9200] Motherboard: Asus K8N-E Deluxe with NVIDIA chipset
Software: Various Linux Kernels X.Org version 6.8.2
Problems: The system won't boot properly. It starts normally, and gets as far as displaying "Initializing hardware... ", and then, when the screen is reinitialized the display disappears, and is replaced by a small square of colored vertical lines in the middle of the monitor. I don't think the keyboard works either, though it's hard to tell without a display.
The system will boot properly if given a "linux single" command, and the X-Windows subsystem can then be started OK using a "telinit 5" command.
The above comments apply to kernel versions: 2.6.12-1.1456_FC4 and 2.6.13-1.1525_FC4 when starting from a cold (turned off) system.
They apply sometimes to kernel versions 2.6.12-1.1398_FC4 and 2.6.12-1.1447_FC4 I think only on an attempt to reboot.
Once the system is started, it seems to run fine.
More info available on request.
jon
On Mon, Sep 26, 2005 at 01:08:57PM -0700, Jonathan Ryshpan wrote:
Hardware: CPU: AMD Athlon(tm) 64 Processor 3000+ running at 3 GHz Video Card: Sapphire Card running ATI RV280 [Radeon 9200] Motherboard: Asus K8N-E Deluxe with NVIDIA chipset
Software: Various Linux Kernels X.Org version 6.8.2
Problems: The system won't boot properly. It starts normally, and gets as far as displaying "Initializing hardware... ", and then, when the screen is reinitialized the display disappears, and is replaced by a small square of colored vertical lines in the middle of the monitor. I don't think the keyboard works either, though it's hard to tell without a display.
The system will boot properly if given a "linux single" command, and the X-Windows subsystem can then be started OK using a "telinit 5" command. The above comments apply to kernel versions: 2.6.12-1.1456_FC4 and 2.6.13-1.1525_FC4 when starting from a cold (turned off) system. They apply sometimes to kernel versions 2.6.12-1.1398_FC4 and 2.6.12-1.1447_FC4 I think only on an attempt to reboot.
Is this using the stock xorg ati driver, or ATI's firegl driver ? Does it still happen if you set your /etc/X11/xorg.conf to use the vesa driver instead ? It sounds more like an X driver issue than a kernel issue at first impression.
If you have this box networked, can you log into it when the display is garbled ? If so, grabbing the X logs from /var/log/ may yield some clues.
You have all the Xorg errata installed I assume ?
Dave
On Mon, 26 Sep 2005, Jonathan Ryshpan wrote:
I've been having trouble with kernel version 2.6.12-1.1456_FC4, so I downloaded 2.6.13-1.1525_FC4 and tried it. It seems to be broken in the same way, namely:
[...]
More info available on request.
File a bug. I don't think the maintainers will follow up with you based on your report here. As Red Hatters have repeated often on these lists: If it's not in Bugzilla, it's not a bug.
jon
On Mon, 2005-09-26 at 16:36 -0400, Matthew Saltzman wrote:
On Mon, 26 Sep 2005, Jonathan Ryshpan wrote:
I've been having trouble with kernel version 2.6.12-1.1456_FC4, so I downloaded 2.6.13-1.1525_FC4 and tried it. It seems to be broken in the same way, namely:
[...]
More info available on request.
File a bug. I don't think the maintainers will follow up with you based on your report here. As Red Hatters have repeated often on these lists: If it's not in Bugzilla, it's not a bug.
That may be true Matt, but as Dave said just before you sent this, Jon's problem is likely an issue with X and not with the kernel. I would say the same considering the timing of the problem. More tests and information are needed to narrow it down though.
Sometimes things do get resolved without a bugzilla, especially cases where it is a configuration or user issue.
In all cases you have to look at the actual problem, not the perception. If it is X the bug would go against X. If it is a kernel issue the bug goes against the kernel. If it is a driver problem the bug goes against the driver. Identifying the actual problem is better than just a blanket statement something like "My PC won't boot since I did an update".
The more the user can do to narrow down the problem source the quicker it can be identified and fixed. Often the best help is to assist in ways to identify the actual location of the problem. Then, if appropriate, file a bug against the proper package.
-- Matthew Saltzman
Clemson University Math Sciences mjs AT clemson DOT edu http://www.math.clemson.edu/~mjs
On Mon, 26 Sep 2005, Jeff Vian wrote:
On Mon, 2005-09-26 at 16:36 -0400, Matthew Saltzman wrote:
On Mon, 26 Sep 2005, Jonathan Ryshpan wrote:
I've been having trouble with kernel version 2.6.12-1.1456_FC4, so I downloaded 2.6.13-1.1525_FC4 and tried it. It seems to be broken in the same way, namely:
[...]
More info available on request.
File a bug. I don't think the maintainers will follow up with you based on your report here. As Red Hatters have repeated often on these lists: If it's not in Bugzilla, it's not a bug.
That may be true Matt, but as Dave said just before you sent this, Jon's problem is likely an issue with X and not with the kernel. I would say the same considering the timing of the problem. More tests and information are needed to narrow it down though.
Sometimes things do get resolved without a bugzilla, especially cases where it is a configuration or user issue.
In all cases you have to look at the actual problem, not the perception. If it is X the bug would go against X. If it is a kernel issue the bug goes against the kernel. If it is a driver problem the bug goes against the driver. Identifying the actual problem is better than just a blanket statement something like "My PC won't boot since I did an update".
The more the user can do to narrow down the problem source the quicker it can be identified and fixed. Often the best help is to assist in ways to identify the actual location of the problem. Then, if appropriate, file a bug against the proper package.
Fair enough--in fact I agree 100%. I read the OP's "more information on request" as being addressed to potential fixers of a bug he believed he had isolated. Maybe it just caught me in a momentary bout of impatience.
Jonathan Ryshpan wrote:
I've been having trouble with kernel version 2.6.12-1.1456_FC4, so I downloaded 2.6.13-1.1525_FC4 and tried it. It seems to be broken in the same way, namely:
Hardware: CPU: AMD Athlon(tm) 64 Processor 3000+ running at 3 GHz Video Card: Sapphire Card running ATI RV280 [Radeon 9200] Motherboard: Asus K8N-E Deluxe with NVIDIA chipset
Is this 32 bit or 64 bit?
I hope you mean "running at 2 GHz". A 3000 at 3 GHz would be seriously over-clocked: you'd need to reproduce your results on a non-overclocked system.
I can report that I have a 3200 Athlon 64 running (at 2 GHz) on an Asus A8N-SLI with a PCI ATI Radeon 9250, and have no troubles with either kernel-2.6.12-1.1456_FC4.x86_64 or kernel-2.6.13-1.1524_FC4.x86_64.
That is, once I'd got the Radeon working stably...
Software: Various Linux Kernels X.Org version 6.8.2
Problems: The system won't boot properly. It starts normally, and gets as far as displaying "Initializing hardware... ", and then, when the screen is reinitialized the display disappears, and is replaced by a small square of colored vertical lines in the middle of the monitor. I don't think the keyboard works either, though it's hard to tell without a display.
Does the Caps Lock LED work? (The Logitech keyboard I'm typing on seems to handle the Num Lock LED itself, and the Scroll Lock key actually has a purpose under Linux, so pressing Scroll Lock won't necessarily light the Scroll Lock key). But the Caps Lock key is a fairly good indication of whether there's anything listening to the keyboard...
Again, which X driver are you using? I've found that I've had to switch to the "ati" driver to get stability (it seems to be the "turning off dri" that does it). Does that work for you? (Although I just get hard lock-ups with DRI enabled).
Hope this helps,
James.
--- Dave Jones davej@redhat.com wrote:
I've completed a 2.6.13 kernel rebase, and pushed out a test kernel to fc4-updates-testing. (FC3 probably won't get another rebase before EOL).
Please give this a try on your systems, and file any bugs that you happen upon in bugzilla.
You can also find interim 'snapshot' builds at http://people.redhat.com/davej/kernels/Fedora/FC4/ which may fix additional problems since the last updates-testing release.
I'm hoping to get this pushed out fairly soon depending upon the feedback I get from how well this kernel works out.
Thanks,
Dave
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Dear Dave & list, The latest kernel 2.6.13-1.1526_FC4 is already in http://download.fedora.redhat.com/pub/fedora/linux/core/updates/4/i386/ and can be updated via yum. I installed it with rpm -ivh and everyting is working great.
[olivares@localhost ~]$ uname -r 2.6.13-1.1526_FC4 [olivares@localhost ~]$
Best Regards,
Antonio
__________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com
On Fri, 2005-09-30 at 15:00 -0700, Antonio Olivares wrote:
Dear Dave & list, The latest kernel 2.6.13-1.1526_FC4 is already in http://download.fedora.redhat.com/pub/fedora/linux/core/updates/4/i386/ and can be updated via yum. I installed it with rpm -ivh and everyting is working great.
1526 gives a kernel panic for me during boot on this Dell Inspiron 5160.
On 9/30/05, Brian Gaynor briang@pmccorp.com wrote:
On Fri, 2005-09-30 at 15:00 -0700, Antonio Olivares wrote:
Dear Dave & list, The latest kernel 2.6.13-1.1526_FC4 is already in http://download.fedora.redhat.com/pub/fedora/linux/core/updates/4/i386/ and can be updated via yum. I installed it with rpm -ivh and everyting is working great.
1526 gives a kernel panic for me during boot on this Dell Inspiron 5160.
-- Brian Gaynor www.pmccorp.com http://www.pmccorp.com FC4/Linux on DELL Inspiron 5160 3.0Ghz canis 15:15:18 up 3:35, 1 user, load average: 0.55, 0.34, 0.17
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
1526 no problems here using Dell Inspiron 600m
-- Terry Snyder Jr Computer Support Specialist http://www.personal.psu.edu/tes215 Linux (Red Hat 5.2, 6.0, 6.1, 7.1, 8.0, 9.0,Fedora Core 3, 4) Windows (3.x, 95, 98, ME, 2k, XP, 2k3) Mac (7, 8, X) I have used them all.
On Fri, Sep 30, 2005 at 03:16:49PM -0700, Brian Gaynor wrote:
On Fri, 2005-09-30 at 15:00 -0700, Antonio Olivares wrote:
Dear Dave & list, The latest kernel 2.6.13-1.1526_FC4 is already in http://download.fedora.redhat.com/pub/fedora/linux/core/updates/4/i386/ and can be updated via yum. I installed it with rpm -ivh and everyting is working great.
1526 gives a kernel panic for me during boot on this Dell Inspiron 5160.
bugzilla it please, with the full output of the panic.
Dave
On Fri, 2005-09-30 at 18:27 -0400, Dave Jones wrote:
On Fri, Sep 30, 2005 at 03:16:49PM -0700, Brian Gaynor wrote:
On Fri, 2005-09-30 at 15:00 -0700, Antonio Olivares wrote:
Dear Dave & list, The latest kernel 2.6.13-1.1526_FC4 is already in http://download.fedora.redhat.com/pub/fedora/linux/core/updates/4/i386/ and can be updated via yum. I installed it with rpm -ivh and everyting is working great.
1526 gives a kernel panic for me during boot on this Dell Inspiron 5160.
bugzilla it please, with the full output of the panic.
This is happening early during boot, insmod is failing to load several modules. Last to fail is ext3.ko and the panic sets in immediately after. No file system yet, so I have no logs.
I have no serial port on this machine to redirect the console output to, is there any other way to capture any more than a screen full of output for bugzilla?
Have not had a problem on this machine with any of the earlier FC4 release kernels.
Brian
On Fri, Sep 30, 2005 at 04:18:10PM -0700, Brian Gaynor wrote:
On Fri, 2005-09-30 at 18:27 -0400, Dave Jones wrote:
On Fri, Sep 30, 2005 at 03:16:49PM -0700, Brian Gaynor wrote:
On Fri, 2005-09-30 at 15:00 -0700, Antonio Olivares wrote:
Dear Dave & list, The latest kernel 2.6.13-1.1526_FC4 is already in http://download.fedora.redhat.com/pub/fedora/linux/core/updates/4/i386/ and can be updated via yum. I installed it with rpm -ivh and everyting is working great.
1526 gives a kernel panic for me during boot on this Dell Inspiron 5160.
bugzilla it please, with the full output of the panic.
This is happening early during boot, insmod is failing to load several modules. Last to fail is ext3.ko and the panic sets in immediately after. No file system yet, so I have no logs.
I have no serial port on this machine to redirect the console output to, is there any other way to capture any more than a screen full of output for bugzilla?
boot with vga=791, and take a pic with digital camera :)
Have not had a problem on this machine with any of the earlier FC4 release kernels.
9 times out of 10 this is a broken initrd. Your /etc/modprobe.conf may yield some clues.
Dave
Hmmm...
Already deleted the original so I guess I'll have to hijack this subthread...
On Fri, 2005-09-30 at 18:27 -0400, Dave Jones wrote:
On Fri, Sep 30, 2005 at 03:16:49PM -0700, Brian Gaynor wrote:
On Fri, 2005-09-30 at 15:00 -0700, Antonio Olivares wrote:
Dear Dave & list, The latest kernel 2.6.13-1.1526_FC4 is already in http://download.fedora.redhat.com/pub/fedora/linux/core/updates/4/i386/ and can be updated via yum. I installed it with rpm -ivh and everyting is working great.
1526 gives a kernel panic for me during boot on this Dell Inspiron 5160.
bugzilla it please, with the full output of the panic.
On a different problem. 524 and 526 have worked fine for me both UP and SMP. However, both had the same problem with Xen. I go to boot Xen on the system and it quickly gives me an error complaining that Domain 0 is too big to load and then reboots. I've tried adding a memory specification to the xen line in grub with no effect. The version immediately prior to these two would load for a while and then hang. It's predecessor would load and run. Non-xen seems fine.
Dave
Mike
Michael H. Warfield wrote:
Hmmm...
Already deleted the original so I guess I'll have to hijack this subthread...
On Fri, 2005-09-30 at 18:27 -0400, Dave Jones wrote:
On Fri, Sep 30, 2005 at 03:16:49PM -0700, Brian Gaynor wrote:
On Fri, 2005-09-30 at 15:00 -0700, Antonio Olivares wrote:
Dear Dave & list, The latest kernel 2.6.13-1.1526_FC4 is already in http://download.fedora.redhat.com/pub/fedora/linux/core/updates/4/i386/ and can be updated via yum. I installed it with rpm -ivh and everyting is working great.
1526 gives a kernel panic for me during boot on this Dell Inspiron 5160.
bugzilla it please, with the full output of the panic.
On a different problem. 524 and 526 have worked fine for me both UP and SMP. However, both had the same problem with Xen. I go to boot Xen on the system and it quickly gives me an error complaining that Domain 0 is too big to load and then reboots. I've tried adding a memory specification to the xen line in grub with no effect. The version immediately prior to these two would load for a while and then hang. It's predecessor would load and run. Non-xen seems fine.
Dave
Mike
Just a "me too" when I tried to boot the xen kernel. My trouble was awhile back. The symptom is the same. I have an HP ze4315 where the behavior took place with 512 MB and a 256MB memory module installed (768MB). Free reports the below though.
free total used free shared buffers cached Mem: 644480 534888 109592 0 41616 340224 -/+ buffers/cache: 153048 491432 Swap: 819272 0 819272
Have you searched through bugzilla for this problem yet?