No kernel 2.6.29.x is able to start any of my 3 F11 boxes.Starting procedures idles after awhile Any suggestion how to debug it??? No clue even if I remove rhgb and quiet option. No clue also from dmesg.
Antonio M antonio.montagnani@gmail.com wrote:
No kernel 2.6.29.x is able to start any of my 3 F11 boxes.Starting procedures idles after awhile Any suggestion how to debug it??? No clue even if I remove rhgb and quiet option. No clue also from dmesg.
For me kernel-2.6.29-0.31.rc1.git2.fc11.x86_64 and 0.35 do work (kernels before that did hang on boot, crash X, ...).
It could be a broken initrd, a new mkinitrd showed up in updates today. Perhaps updating (and then reinstalling the kernel so it picks up a new initrd) cures your ailments?
DANGEROUS. Sharp knife included. We are not responsible for lost fingers.
On Thu, Jan 15, 2009 at 03:27:14PM -0300, Horst H. von Brand wrote:
Antonio M antonio.montagnani@gmail.com wrote:
No kernel 2.6.29.x is able to start any of my 3 F11 boxes.
For me kernel-2.6.29-0.31.rc1.git2.fc11.x86_64 and 0.35 do work (kernels before that did hang on boot, crash X, ...).
It could be a broken initrd, a new mkinitrd showed up in updates today.
Antonio is not saying very much what really happens so no wonder that nobody is rushing with an advice. OTOH from what he eventually posted on https://bugzilla.redhat.com/show_bug.cgi?id=479525#c4 it appears that this is way before initrd comes into play. What is supposed to come on his machine(s) after
ata2.00: configured for UDM/33 ata2.01: configured for MWDMA2
is his own sweet secret.
I thought initially that he possibly gets "crc error", which happened to me at the same time, but apparently this is not that and starting with 2.6.29-0.28.rc1.fc11 on my hardware current kernels boot again.
Michal
2009/1/15 Michal Jaegermann michal@harddata.com:
On Thu, Jan 15, 2009 at 03:27:14PM -0300, Horst H. von Brand wrote:
Antonio M antonio.montagnani@gmail.com wrote:
No kernel 2.6.29.x is able to start any of my 3 F11 boxes.
For me kernel-2.6.29-0.31.rc1.git2.fc11.x86_64 and 0.35 do work (kernels before that did hang on boot, crash X, ...).
It could be a broken initrd, a new mkinitrd showed up in updates today.
Antonio is not saying very much what really happens so no wonder that nobody is rushing with an advice. OTOH from what he eventually posted on https://bugzilla.redhat.com/show_bug.cgi?id=479525#c4 it appears that this is way before initrd comes into play. What is supposed to come on his machine(s) after
ata2.00: configured for UDM/33 ata2.01: configured for MWDMA2
is his own sweet secret.
I thought initially that he possibly gets "crc error", which happened to me at the same time, but apparently this is not that and starting with 2.6.29-0.28.rc1.fc11 on my hardware current kernels boot again.
Michal
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
Tnx to both of you.
Michael there is no my secret, as after those lines system idles and I have to do an hard reboot (unless someone suggests how to proceed in digging) And my system is fully updated (as rawhide, I mean).
I wonder why kernel 28 boot fine and 2'9's no... If you have any suggestion, I will proceed to further tests: and for sure at least two out of three boxes don't boot (or complete booting..:) Any option to include???
Tnx again
Antonio M wrote:
2009/1/15 Michal Jaegermann michal@harddata.com:
ata2.00: configured for UDM/33 ata2.01: configured for MWDMA2
is his own sweet secret.
I thought initially that he possibly gets "crc error", which happened to me at the same time, but apparently this is not that and starting with 2.6.29-0.28.rc1.fc11 on my hardware current kernels boot again.
Tnx to both of you.
Michael there is no my secret, as after those lines system idles and I have to do an hard reboot (unless someone suggests how to proceed in digging) And my system is fully updated (as rawhide, I mean).
I think what Michael is getting at is what *would* you see immediately following these two lines on the last kernel that does work? (assuming of course that you do have two such lines!).
That would give people some idea of what the kernel might be doing at the point that it goes off into the weeds.
If you have a dmesg from 28 or whatever is the latest working for you, it might be useful to put it in pastebin or something and post a link to this thread.
Regards, Bryn.
2009/1/16 Bryn M. Reeves bmr@redhat.com:
Antonio M wrote:
2009/1/15 Michal Jaegermann michal@harddata.com:
ata2.00: configured for UDM/33 ata2.01: configured for MWDMA2
is his own sweet secret.
I thought initially that he possibly gets "crc error", which happened to me at the same time, but apparently this is not that and starting with 2.6.29-0.28.rc1.fc11 on my hardware current kernels boot again.
Tnx to both of you.
Michael there is no my secret, as after those lines system idles and I have to do an hard reboot (unless someone suggests how to proceed in digging) And my system is fully updated (as rawhide, I mean).
I think what Michael is getting at is what *would* you see immediately following these two lines on the last kernel that does work? (assuming of course that you do have two such lines!).
That would give people some idea of what the kernel might be doing at the point that it goes off into the weeds.
If you have a dmesg from 28 or whatever is the latest working for you, it might be useful to put it in pastebin or something and post a link to this thread.
Regards, Bryn.
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
Please read all thread and to bug #479525 Tnx for yr. attention
Rgds
2009/1/15 Michal Jaegermann michal@harddata.com:
On Thu, Jan 15, 2009 at 03:27:14PM -0300, Horst H. von Brand wrote:
Antonio M antonio.montagnani@gmail.com wrote:
No kernel 2.6.29.x is able to start any of my 3 F11 boxes.
For me kernel-2.6.29-0.31.rc1.git2.fc11.x86_64 and 0.35 do work (kernels before that did hang on boot, crash X, ...).
It could be a broken initrd, a new mkinitrd showed up in updates today.
Antonio is not saying very much what really happens so no wonder that nobody is rushing with an advice. OTOH from what he eventually posted on https://bugzilla.redhat.com/show_bug.cgi?id=479525#c4 it appears that this is way before initrd comes into play. What is supposed to come on his machine(s) after
ata2.00: configured for UDM/33 ata2.01: configured for MWDMA2
is his own sweet secret.
I thought initially that he possibly gets "crc error", which happened to me at the same time, but apparently this is not that and starting with 2.6.29-0.28.rc1.fc11 on my hardware current kernels boot again.
Michal
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
these are the lines in dmesg in a regular boot: any comment???
scsi 0:0:0:0: Direct-Access ATA Maxtor 6L200P0 BAH4 PQ: 0 ANSI: 5 sd 0:0:0:0: [sda] 398297088 512-byte hardware sectors: (203 GB/189 GiB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 0:0:0:0: [sda] 398297088 512-byte hardware sectors: (203 GB/189 GiB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sda: sda1 sda2 sd 0:0:0:0: [sda] Attached SCSI disk sd 0:0:0:0: Attached scsi generic sg0 type 0 scsi 1:0:0:0: CD-ROM HL-DT-ST DVDRAM GSA-4163B A103 PQ: 0 ANSI: 5 sr0: scsi3-mmc drive: 40x/40x writer dvd-ram cd/rw xa/form2 cdda tray Uniform CD-ROM driver Revision: 3.20 sr 1:0:0:0: Attached scsi CD-ROM sr0 sr 1:0:0:0: Attached scsi generic sg1 type 5 scsi 1:0:1:0: CD-ROM HP CD-Writer+ 7500 1.0a PQ: 0 ANSI: 5 sr1: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda tray sr 1:0:1:0: Attached scsi CD-ROM sr1 sr 1:0:1:0: Attached scsi generic sg2 type 5 ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver ehci_hcd 0000:00:1d.7: PCI INT D -> GSI 23 (level, low) -> IRQ 23 ehci_hcd 0000:00:1d.7: setting latency timer to 64 ehci_hcd 0000:00:1d.7: EHCI Host Controller ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1 ehci_hcd 0000:00:1d.7: debug port 1 ehci_hcd 0000:00:1d.7: cache line size of 128 is not supported ehci_hcd 0000:00:1d.7: irq 23, io mem 0xf9fffc00 ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 8 ports detected usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb1: Product: EHCI Host Controller usb usb1: Manufacturer: Linux 2.6.28-3.fc11.i686 ehci_hcd usb usb1: SerialNumber: 0000:00:1d.7 ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver uhci_hcd: USB Universal Host Controller Interface driver uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 uhci_hcd 0000:00:1d.0: setting latency timer to 64 uhci_hcd 0000:00:1d.0: UHCI Host Controller uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2 uhci_hcd 0000:00:1d.0: irq 16, io base 0x0000c480 usb usb2: configuration #1 chosen from 1 choice hub 2-0:1.0: USB hub found hub 2-0:1.0: 2 ports detected usb usb2: New USB device found, idVendor=1d6b, idProduct=0001 usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb2: Product: UHCI Host Controller usb usb2: Manufacturer: Linux 2.6.28-3.fc11.i686 uhci_hcd usb usb2: SerialNumber: 0000:00:1d.0 uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19 uhci_hcd 0000:00:1d.1: setting latency timer to 64 uhci_hcd 0000:00:1d.1: UHCI Host Controller uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3 uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000c800 usb usb3: configuration #1 chosen from 1 choice hub 3-0:1.0: USB hub found hub 3-0:1.0: 2 ports detected usb usb3: New USB device found, idVendor=1d6b, idProduct=0001 usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb3: Product: UHCI Host Controller usb usb3: Manufacturer: Linux 2.6.28-3.fc11.i686 uhci_hcd usb usb3: SerialNumber: 0000:00:1d.1 uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18 uhci_hcd 0000:00:1d.2: setting latency timer to 64 uhci_hcd 0000:00:1d.2: UHCI Host Controller uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4 uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000c880 usb usb4: configuration #1 chosen from 1 choice hub 4-0:1.0: USB hub found hub 4-0:1.0: 2 ports detected usb usb4: New USB device found, idVendor=1d6b, idProduct=0001 usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb4: Product: UHCI Host Controller usb usb4: Manufacturer: Linux 2.6.28-3.fc11.i686 uhci_hcd usb usb4: SerialNumber: 0000:00:1d.2 uhci_hcd 0000:00:1d.3: PCI INT A -> GSI 16 (level, low) -> IRQ 16 uhci_hcd 0000:00:1d.3: setting latency timer to 64 uhci_hcd 0000:00:1d.3: UHCI Host Controller uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5 uhci_hcd 0000:00:1d.3: irq 16, io base 0x0000cc00 usb usb5: configuration #1 chosen from 1 choice hub 5-0:1.0: USB hub found hub 5-0:1.0: 2 ports detected usb usb5: New USB device found, idVendor=1d6b, idProduct=0001 usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb5: Product: UHCI Host Controller usb usb5: Manufacturer: Linux 2.6.28-3.fc11.i686 uhci_hcd usb usb5: SerialNumber: 0000:00:1d.3 PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12 serio: i8042 KBD port at 0x60,0x64 irq 1 serio: i8042 AUX port at 0x60,0x64 irq 12 mice: PS/2 mouse device common for all mice rtc_cmos 00:02: RTC can wake from S4 rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0 rtc0: alarms up to one month, 114 bytes nvram, hpet irqs device-mapper: uevent: version 1.0.3 device-mapper: ioctl: 4.14.0-ioctl (2008-04-23) initialised: dm-devel@redhat.com cpuidle: using governor ladder cpuidle: using governor menu usbcore: registered new interface driver hiddev usbcore: registered new interface driver usbhid usbhid: v2.6:USB HID core driver nf_conntrack version 0.5.0 (16379 buckets, 65516 max) CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use nf_conntrack.acct=1 kernel paramater, acct=1 nf_conntrack module option or sysctl net.netfilter.nf_conntrack_acct=1 to enable it. ip_tables: (C) 2000-2006 Netfilter Core Team TCP cubic registered Initializing XFRM netlink socket NET: Registered protocol family 17 Using IPI No-Shortcut mode registered taskstats version 1 Magic number: 9:138:696 debug: unmapping init memory c089d000..c0a1e000 Write protecting the kernel text: 2916k Write protecting the kernel read-only data: 1324k input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3 console_init used greatest stack depth: 2680 bytes left modprobe used greatest stack depth: 2456 bytes left psmouse serio1: ID: 10 00 64<6>usb 2-2: new full speed USB device using uhci_hcd and address 2 lvm used greatest stack depth: 2352 bytes left usb 2-2: configuration #1 chosen from 1 choice usb 2-2: New USB device found, idVendor=04b8, idProduct=010b usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 2-2: Product: Perfection1240 usb 2-2: Manufacturer: EPSON input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input4 kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. SELinux: Disabled at runtime. SELinux: Unregistering netfilter hooks type=1404 audit(1232044753.492:2): selinux=0 auid=4294967295 ses=4294967295 runlevel used greatest stack depth: 2304 bytes left hostname used greatest stack depth: 1848 bytes left mount used greatest stack depth: 1504 bytes left udev: starting version 135 intel_rng: FWH not detected parport_pc 00:0a: reported by Plug and Play ACPI parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE,EPP] iTCO_vendor_support: vendor-support=0 iTCO_wdt: Intel TCO WatchDog Timer Driver v1.04 iTCO_wdt: Found a ICH5 or ICH5R TCO device (Version=1, TCOBASE=0x0860) iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) skge 0000:02:05.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22 skge 1.13 addr 0xfbffc000 irq 22 chip Yukon-Lite rev 9 skge eth0: addr 00:11:d8:bf:9f:05 ne2k-pci.c:v1.03 9/22/2003 D. Becker/P. Gortmaker ne2k-pci 0000:02:0b.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23 eth1: RealTek RTL-8029 found at 0xec00, IRQ 23, 52:54:05:e5:82:46. i801_smbus 0000:00:1f.3: PCI INT B -> GSI 17 (level, low) -> IRQ 17 ACPI: I/O resource 0000:00:1f.3 [0x400-0x41f] conflicts with ACPI region SMRG [0x400-0x40f] ACPI: Device needs an ACPI driver input: PC Speaker as /devices/platform/pcspkr/input/input5 Intel ICH 0000:00:1f.5: PCI INT B -> GSI 17 (level, low) -> IRQ 17 Intel ICH 0000:00:1f.5: setting latency timer to 64 ALSA sound/pci/ac97/ac97_codec.c:2127: AC'97 0 analog subsections not ready ppdev: user-space parallel port driver modprobe used greatest stack depth: 1008 bytes left udev: renamed network interface eth1 to eth0 udev: renamed network interface eth0_rename to eth1 device-mapper: multipath: version 1.0.5 loaded EXT3 FS on dm-0, internal journal kjournald starting. Commit interval 5 seconds EXT3 FS on sda1, internal journal EXT3-fs: mounted filesystem with ordered data mode. Adding 2031608k swap on /dev/mapper/VolGroup00-LogVol01. Priority:-1 extents:1 across:2031608k
2009/1/15 Antonio M antonio.montagnani@gmail.com:
2009/1/15 Michal Jaegermann michal@harddata.com:
On Thu, Jan 15, 2009 at 03:27:14PM -0300, Horst H. von Brand wrote:
Antonio M antonio.montagnani@gmail.com wrote:
No kernel 2.6.29.x is able to start any of my 3 F11 boxes.
For me kernel-2.6.29-0.31.rc1.git2.fc11.x86_64 and 0.35 do work (kernels before that did hang on boot, crash X, ...).
It could be a broken initrd, a new mkinitrd showed up in updates today.
Antonio is not saying very much what really happens so no wonder that nobody is rushing with an advice. OTOH from what he eventually posted on https://bugzilla.redhat.com/show_bug.cgi?id=479525#c4 it appears that this is way before initrd comes into play. What is supposed to come on his machine(s) after
ata2.00: configured for UDM/33 ata2.01: configured for MWDMA2
is his own sweet secret.
I thought initially that he possibly gets "crc error", which happened to me at the same time, but apparently this is not that and starting with 2.6.29-0.28.rc1.fc11 on my hardware current kernels boot again.
Michal
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
these are the lines in dmesg in a regular boot: any comment???
scsi 0:0:0:0: Direct-Access ATA Maxtor 6L200P0 BAH4 PQ: 0 ANSI: 5 sd 0:0:0:0: [sda] 398297088 512-byte hardware sectors: (203 GB/189 GiB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 0:0:0:0: [sda] 398297088 512-byte hardware sectors: (203 GB/189 GiB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sda: sda1 sda2 sd 0:0:0:0: [sda] Attached SCSI disk sd 0:0:0:0: Attached scsi generic sg0 type 0 scsi 1:0:0:0: CD-ROM HL-DT-ST DVDRAM GSA-4163B A103 PQ: 0 ANSI: 5 sr0: scsi3-mmc drive: 40x/40x writer dvd-ram cd/rw xa/form2 cdda tray Uniform CD-ROM driver Revision: 3.20 sr 1:0:0:0: Attached scsi CD-ROM sr0 sr 1:0:0:0: Attached scsi generic sg1 type 5 scsi 1:0:1:0: CD-ROM HP CD-Writer+ 7500 1.0a PQ: 0 ANSI: 5 sr1: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda tray sr 1:0:1:0: Attached scsi CD-ROM sr1 sr 1:0:1:0: Attached scsi generic sg2 type 5 ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver ehci_hcd 0000:00:1d.7: PCI INT D -> GSI 23 (level, low) -> IRQ 23 ehci_hcd 0000:00:1d.7: setting latency timer to 64 ehci_hcd 0000:00:1d.7: EHCI Host Controller ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1 ehci_hcd 0000:00:1d.7: debug port 1 ehci_hcd 0000:00:1d.7: cache line size of 128 is not supported ehci_hcd 0000:00:1d.7: irq 23, io mem 0xf9fffc00 ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 8 ports detected usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb1: Product: EHCI Host Controller usb usb1: Manufacturer: Linux 2.6.28-3.fc11.i686 ehci_hcd usb usb1: SerialNumber: 0000:00:1d.7 ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver uhci_hcd: USB Universal Host Controller Interface driver uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 uhci_hcd 0000:00:1d.0: setting latency timer to 64 uhci_hcd 0000:00:1d.0: UHCI Host Controller uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2 uhci_hcd 0000:00:1d.0: irq 16, io base 0x0000c480 usb usb2: configuration #1 chosen from 1 choice hub 2-0:1.0: USB hub found hub 2-0:1.0: 2 ports detected usb usb2: New USB device found, idVendor=1d6b, idProduct=0001 usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb2: Product: UHCI Host Controller usb usb2: Manufacturer: Linux 2.6.28-3.fc11.i686 uhci_hcd usb usb2: SerialNumber: 0000:00:1d.0 uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19 uhci_hcd 0000:00:1d.1: setting latency timer to 64 uhci_hcd 0000:00:1d.1: UHCI Host Controller uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3 uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000c800 usb usb3: configuration #1 chosen from 1 choice hub 3-0:1.0: USB hub found hub 3-0:1.0: 2 ports detected usb usb3: New USB device found, idVendor=1d6b, idProduct=0001 usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb3: Product: UHCI Host Controller usb usb3: Manufacturer: Linux 2.6.28-3.fc11.i686 uhci_hcd usb usb3: SerialNumber: 0000:00:1d.1 uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18 uhci_hcd 0000:00:1d.2: setting latency timer to 64 uhci_hcd 0000:00:1d.2: UHCI Host Controller uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4 uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000c880 usb usb4: configuration #1 chosen from 1 choice hub 4-0:1.0: USB hub found hub 4-0:1.0: 2 ports detected usb usb4: New USB device found, idVendor=1d6b, idProduct=0001 usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb4: Product: UHCI Host Controller usb usb4: Manufacturer: Linux 2.6.28-3.fc11.i686 uhci_hcd usb usb4: SerialNumber: 0000:00:1d.2 uhci_hcd 0000:00:1d.3: PCI INT A -> GSI 16 (level, low) -> IRQ 16 uhci_hcd 0000:00:1d.3: setting latency timer to 64 uhci_hcd 0000:00:1d.3: UHCI Host Controller uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5 uhci_hcd 0000:00:1d.3: irq 16, io base 0x0000cc00 usb usb5: configuration #1 chosen from 1 choice hub 5-0:1.0: USB hub found hub 5-0:1.0: 2 ports detected usb usb5: New USB device found, idVendor=1d6b, idProduct=0001 usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb5: Product: UHCI Host Controller usb usb5: Manufacturer: Linux 2.6.28-3.fc11.i686 uhci_hcd usb usb5: SerialNumber: 0000:00:1d.3 PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12 serio: i8042 KBD port at 0x60,0x64 irq 1 serio: i8042 AUX port at 0x60,0x64 irq 12 mice: PS/2 mouse device common for all mice rtc_cmos 00:02: RTC can wake from S4 rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0 rtc0: alarms up to one month, 114 bytes nvram, hpet irqs device-mapper: uevent: version 1.0.3 device-mapper: ioctl: 4.14.0-ioctl (2008-04-23) initialised: dm-devel@redhat.com cpuidle: using governor ladder cpuidle: using governor menu usbcore: registered new interface driver hiddev usbcore: registered new interface driver usbhid usbhid: v2.6:USB HID core driver nf_conntrack version 0.5.0 (16379 buckets, 65516 max) CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use nf_conntrack.acct=1 kernel paramater, acct=1 nf_conntrack module option or sysctl net.netfilter.nf_conntrack_acct=1 to enable it. ip_tables: (C) 2000-2006 Netfilter Core Team TCP cubic registered Initializing XFRM netlink socket NET: Registered protocol family 17 Using IPI No-Shortcut mode registered taskstats version 1 Magic number: 9:138:696 debug: unmapping init memory c089d000..c0a1e000 Write protecting the kernel text: 2916k Write protecting the kernel read-only data: 1324k input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3 console_init used greatest stack depth: 2680 bytes left modprobe used greatest stack depth: 2456 bytes left psmouse serio1: ID: 10 00 64<6>usb 2-2: new full speed USB device using uhci_hcd and address 2 lvm used greatest stack depth: 2352 bytes left usb 2-2: configuration #1 chosen from 1 choice usb 2-2: New USB device found, idVendor=04b8, idProduct=010b usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 2-2: Product: Perfection1240 usb 2-2: Manufacturer: EPSON input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input4 kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. SELinux: Disabled at runtime. SELinux: Unregistering netfilter hooks type=1404 audit(1232044753.492:2): selinux=0 auid=4294967295 ses=4294967295 runlevel used greatest stack depth: 2304 bytes left hostname used greatest stack depth: 1848 bytes left mount used greatest stack depth: 1504 bytes left udev: starting version 135 intel_rng: FWH not detected parport_pc 00:0a: reported by Plug and Play ACPI parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE,EPP] iTCO_vendor_support: vendor-support=0 iTCO_wdt: Intel TCO WatchDog Timer Driver v1.04 iTCO_wdt: Found a ICH5 or ICH5R TCO device (Version=1, TCOBASE=0x0860) iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) skge 0000:02:05.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22 skge 1.13 addr 0xfbffc000 irq 22 chip Yukon-Lite rev 9 skge eth0: addr 00:11:d8:bf:9f:05 ne2k-pci.c:v1.03 9/22/2003 D. Becker/P. Gortmaker ne2k-pci 0000:02:0b.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23 eth1: RealTek RTL-8029 found at 0xec00, IRQ 23, 52:54:05:e5:82:46. i801_smbus 0000:00:1f.3: PCI INT B -> GSI 17 (level, low) -> IRQ 17 ACPI: I/O resource 0000:00:1f.3 [0x400-0x41f] conflicts with ACPI region SMRG [0x400-0x40f] ACPI: Device needs an ACPI driver input: PC Speaker as /devices/platform/pcspkr/input/input5 Intel ICH 0000:00:1f.5: PCI INT B -> GSI 17 (level, low) -> IRQ 17 Intel ICH 0000:00:1f.5: setting latency timer to 64 ALSA sound/pci/ac97/ac97_codec.c:2127: AC'97 0 analog subsections not ready ppdev: user-space parallel port driver modprobe used greatest stack depth: 1008 bytes left udev: renamed network interface eth1 to eth0 udev: renamed network interface eth0_rename to eth1 device-mapper: multipath: version 1.0.5 loaded EXT3 FS on dm-0, internal journal kjournald starting. Commit interval 5 seconds EXT3 FS on sda1, internal journal EXT3-fs: mounted filesystem with ordered data mode. Adding 2031608k swap on /dev/mapper/VolGroup00-LogVol01. Priority:-1 extents:1 across:2031608k
-- Antonio Montagnani Skype : antoniomontag
I mean the missing lines, where system idles...
On Thu, Jan 15, 2009 at 09:07:11PM +0100, Antonio M wrote:
2009/1/15 Michal Jaegermann michal@harddata.com:
Antonio is not saying very much what really happens so no wonder that nobody is rushing with an advice. OTOH from what he eventually posted on https://bugzilla.redhat.com/show_bug.cgi?id=479525#c4 it appears that this is way before initrd comes into play. What is supposed to come on his machine(s) after
ata2.00: configured for UDM/33 ata2.01: configured for MWDMA2
is his own sweet secret.
these are the lines in dmesg in a regular boot: any comment???
scsi 0:0:0:0: Direct-Access ATA Maxtor 6L200P0 BAH4 PQ: 0 ANSI: 5 sd 0:0:0:0: [sda] 398297088 512-byte hardware sectors: (203 GB/189 GiB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
.....
Well, attachment to https://bugzilla.redhat.com/show_bug.cgi?id=479525 is not of an application/octet-stream type, as left there, but your regular text. Few lines is usually more than enough here.
Here and there you mean that this is what you expect to see in a normal boot but it not coming. Right? You are not perfectly clear.
If this happens then, if you installed kernel-doc package, in /usr/share/doc/kernel-doc-2.6.29/Documentation/kernel-parameters.txt there are described various 'libata....' parameters which you may want to try. It is also possible that in that part of dmesg you are not showing, and from a failing boot, there are some errors and/or hints which can give you an information. If you will find some options which allow you to boot then this is a valuable information for developers.
If you want the whole story then in subdirectory DocBook/libata you will find the whole big reference.
Michal
2009/1/16 Michal Jaegermann michal@harddata.com:
On Thu, Jan 15, 2009 at 09:07:11PM +0100, Antonio M wrote:
2009/1/15 Michal Jaegermann michal@harddata.com:
Antonio is not saying very much what really happens so no wonder that nobody is rushing with an advice. OTOH from what he eventually posted on https://bugzilla.redhat.com/show_bug.cgi?id=479525#c4 it appears that this is way before initrd comes into play. What is supposed to come on his machine(s) after
ata2.00: configured for UDM/33 ata2.01: configured for MWDMA2
is his own sweet secret.
these are the lines in dmesg in a regular boot: any comment???
scsi 0:0:0:0: Direct-Access ATA Maxtor 6L200P0 BAH4 PQ: 0 ANSI: 5 sd 0:0:0:0: [sda] 398297088 512-byte hardware sectors: (203 GB/189 GiB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
.....
Well, attachment to https://bugzilla.redhat.com/show_bug.cgi?id=479525 is not of an application/octet-stream type, as left there, but your regular text. Few lines is usually more than enough here.
Here and there you mean that this is what you expect to see in a normal boot but it not coming. Right? You are not perfectly clear.
If this happens then, if you installed kernel-doc package, in /usr/share/doc/kernel-doc-2.6.29/Documentation/kernel-parameters.txt there are described various 'libata....' parameters which you may want to try. It is also possible that in that part of dmesg you are not showing, and from a failing boot, there are some errors and/or hints which can give you an information. If you will find some options which allow you to boot then this is a valuable information for developers.
If you want the whole story then in subdirectory DocBook/libata you will find the whole big reference.
Michal
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
1) your understanding is correct, I pasted only the lines I think I should see and that are not coming out. 2) I will download what you suggest but I think that a standard kernel should boot with no options (3 machines with different hardware are not booting with 29 - see also Antonio Olivares message not far from this...about different problems with F11.
tnx for help
On Fri, Jan 16, 2009 at 06:56:08AM +0100, Antonio M wrote:
.... but I think that a standard kernel should boot with no options
Your understanding is correct but this is rawhide. If you are running that then you should expect things to break and if you are able to contribute to a search for solutions then even better. Plain "does not work" is not going that far but if you do not have anything more informative then so be it. Even if you say "I tried this and that and still no go" that brings something too.
3 machines with different hardware are not booting with 29
And some other are booting and may show different problems. Say this: https://bugzilla.redhat.com/show_bug.cgi?id=479778
Michal
-
Antonio M -
Bryn M. Reeves -
Horst H. von Brand -
Michal Jaegermann