|
Bugzilla – Full Text Bug Listing |
| Summary: | OpenSuse 11.0 Beta 3 doesn't boot | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.0 | Reporter: | Simon Schneider <schneida.simon> |
| Component: | Kernel | Assignee: | Marcus Schaefer <ms> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Blocker | ||
| Priority: | P5 - None | CC: | eriksorenson, forgotten_LHylH34xWO, forgotten_WYqD73zI_T, hulleyrob, jreidinger, martin, public, rastislav.krupansky |
| Version: | Beta 3 | Flags: | coolo:
SHIP_STOPPER-
|
| Target Milestone: | --- | ||
| Hardware: | 64bit | ||
| OS: | openSUSE 11.0 | ||
| Whiteboard: | |||
| Found By: | System Test | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
Error log on ALT F3 and F4
boot.msg as requested dmesg.out as requested interupts.out as requested Consolidated boot, dmesg, hwinfo & interrupts file output Output of hwinfo --all (Schneider) boot.kiwi and boot.msg files in tar.gz format /var/log from simon test-ready.c |
||
|
Description
Simon Schneider
2008-05-15 18:04:46 UTC
the md5sum is ok? What do you see with kiwidebug=1 The md5sum is ok. I will try kiwidebug=1 in the evening and report back. I forgot to post my hardware: Asus P5NE-SLI Intel E6750 @ 3.00 Ghz MSI Nvidia Gforce 8800 GTS When reproducing, please, change the video mode to text mode and report what the last of the messages is so that we can figure out at which stage boot freezes. So now I changed the video mode to text and the last messeges are: --> Probing module: ohci-hcd Drive not ready Drive not ready Drive not ready Drive not ready Couldn't find CD image configuration file reboot Exception: Errologs on Alt + F2,F3 reboot Exception: reboot in 120 sec After that I tried turning on kiwidebug. Instead of the last two lines I get into a shell, but I can't type anything into it. I tried the same image on a virtual machine and it worked without any problem, so I don't think, that it's a problem of the CD I use. Problem with accesing your CD drive? What's reported on 2nd and 3rd consoles (as the error report you wrote above suggests)? It's not possible to acess the 2nd and the 3rd console. I think the keyboard doesn't work properly at that moment. It isn't possible to restart the computer with ALT+ S-Abf + B either. I just downloaded th 32 bit Version and I will try it later and report back if this version works. So i burned the i386 version to a CD now and tried booting again. These time I used a different burning program and lowered the speed (18 instead of 36). Same probleme as described above. Could it be, that it is a problem with my SATA Disc-Drive? It is a HL-DT-ST DVDRAM GSA-H62N from LG. Should I install one of my old drives and try it again or do you thing that this doesn't matter? So, I'm writing this message from OpenSuse 11.0 Beta 3, but not on my Tower, but on my Laptop. So it is definitively not a problem with the CD itself. I'm going to setup one of my old drives now and try it again. Hope it will work. Is there any possibility to edit old comments? This is my third post after each other and in forums that would be quite bad. I have never used Bugzilla before so I don't know if this is ok here. Sorry, no way to edit old comments. Can you summarize the problem now? Is it still a hardware issue, or have you ruled that out by installing with the same drive on different cpu? see #375836 - try booting with pnpacpi=off So i tried with pnpacpi=off same thing, no changes. To sum it up: It is still a hardware problem. Not with my Sata Drive from LG (i tested it with an old Pata drive too). The same CD's work fine on other machines. Another problem is, that the keyboard doesn't work, so I can't go to Errorscreen 2 and 3 with Alt + F2 or Alt + F3. I tried the Beta 2 now and this version doesn't work either. Still same problem. It's interesting because the OpenSuse 10.3 worked fine on this machine, also Fedora, Gentoo, Ubuntu do. Created attachment 216157 [details]
Error log on ALT F3 and F4
So I pluged in an old PS/2 Keyboard now with which I'm now able to type in commands in the shell if i use kiwidebug on. I made an attachment with the errorr logs on both other screens. I also tried to unplugged my USB devices but still same erorr. FWIW. This also happens (same probe/error messages as in #4 thread) on my PC. Using 32-bit LiveCD of 11b3 (KDE). PC is homebrew, Asus M2NPV-VM, AMD 3600x2 processor, IGP disabled, PCIe NV 8600GT, WD 250 gig SATA, Pioneer 107D (booting from) and 112D ATA DVD/CD drives. PS/2 KB & MS mouse. Samsung 213T LCD using difital connection. This is my main system and contains openSuse 10.1, 10.3 (desktop production) as well as W2K, XP, a couple of Fat16 partitions, a couple more NTFS data partitions, etc. Hitting 16 partition limit? Tried pnpacpi=off and hwprobe=-parallel,-misc.par workarounds (for slightly different problem) found in Bugzilla threads with both enabled and disabled parallel port. No difference in error message on main console. Live 11b2 worked fine. *** Bug 391824 has been marked as a duplicate of this bug. *** Can you please do the followings after boot fails in the emergency shell? 1. Plug in a USB stick (if a harddisk or any other writable storage device is already detected, you can just that too) 2. mount the device under /mnt. e.g. mount /dev/sda1 /mnt. You can find out the device name by looking at the output of dmesg or /var/log/boot.msg 3. Run the following: cp /var/log/boot.msg /mnt; dmesg > /mnt/dmesg.out; lspci -nn > /mnt/lspci.out; cat /proc/interrupts > interrupts.out 4. unmount /mnt and post the result files here. Thanks. I've met the same issue on my system (notebook Benq p51e with AMD 64-bit cpu). The only way I've managed to install openSuse 11 beta 3 X86 is to use folder located on hdd. I booted from DVD and than type path to folder which contains installation files from DVD. Created attachment 217333 [details]
boot.msg as requested
Created attachment 217334 [details]
dmesg.out as requested
Created attachment 217335 [details]
interupts.out as requested
I added the interupts.out, the dmesg.out and the boot.msg lspci didn't work (not a valid command). according to Michl support for specific hardware is not a shipment blocker. So while this is clearly desirable to fix, we won't delay 11.0 if not. Stephan: Perhaps I don't understand your comment re: "specific hardware". Looking at Schneider's configuration: (Intel CPU/Board, both 32 & 64 bit tried, German language, LG SATA DVD, USB & PS/2 K/B, etc). versus mine (Comment 14: AMD CPU and MB, 32 bit tried, English language, Pioneer ATA DVDs, PS/2 KB & Mouse, etc.), this seems to be happening on different MBs, CPU manuafacturers, both SATA and ATA DVD devices, PS/2 and USB K/B & Mice, etc. What "specific hardware" are you referencing? In my case, the 11b2 worked fine, so it seems to be a regression? Hmmm... Simon, from the command shell, if you run "mount /dev/sr0 /mnt", does it succeed and can you access the media content if you cd under /mnt? You might have to retry a few times before the media gets ready. Erik, the symptom can be caused by a lot of different things. Can you please post the information requested in comment #16? Please run "hwinfo --all" instead of lspci. Tejun: Would like to, but all I have to dump to is a regular floppy and a camera card ... the latter I'm not going near. Took me a bit of searching to find that Alt-F2 was the Emergency Console. After that, tried: mount /dev/fd0 /mnt, but got a must supply file type. modified to mount -t msdos /dev/fd0 /mnt, but got invalid file type. modified to mount -t vfat /dev/fd0, but got "not a block device". Any suggestions? I guess it's possible the floppy isn't enumerated by that point? Is the floppy drive detected and the floppy formatted? You can determine by looking at /var/log/boot.msg and the output of dmesg. *** Bug 392219 has been marked as a duplicate of this bug. *** Created attachment 217513 [details]
Consolidated boot, dmesg, hwinfo & interrupts file output
Tejun: Was able to dump to floppy after formatting another one as ext2, rather than using a fat12 (DOS/Windows) formatted floppy. Attaching boot.msg, dmesg.out, hwinfo.out and interrupts.out, consolidated into sorenson_info.txt. Was also able to mount CD (mount /dev/sr0 /mnt) and traverse folder structure (went down to /mnt/boot/i386/loader before I stopped). So I tried mounting /dev/sr0 instantly after getting into the emergency shell and it work perfectly without any problems (went down to /mnt/boot/i386/loader/animations). I also used hwinfo --all and will attache the output now. Created attachment 217552 [details]
Output of hwinfo --all (Schneider)
Erik, Simon, thanks for the logs. This doesn't seem to be a kernel problem. Could be related to bug #390204. cc'ing Josef. Can you guys please run save_y2logs from the emergency shell and post the result here? What seems to happen here is that the boot script is too quick to determine that there's no media in the drive. Can someone point me to where this logic is implemented? Tejun: Are you asking Simon and me to "run save_y2logs from the emergency shell"? I don't know about Simon, but that command doesn't seem to exist on my system, nor is there a file by that name. More detail/location, etc would be appreciated. Thnx. Aiee.. Sorry about that. Can you please just copy whole /var/log and tar them and upload here? Created attachment 217594 [details]
boot.kiwi and boot.msg files in tar.gz format
OK, that was easier. Only two files exist at stoppage point in /var/log:
- boot.kiwi
- boot.msg
These have been compressed in tar.gz format in "sorenson_info2" attachment.
Ok, and here are mine. simon.tar - boot.kiwi - boot.msg Another (maybe important or not important) thing I noticed now (when I was playing around a litle bit in the shell) was, that when I type: modprobe ehci-hcd modprobe pata-amd that works without any output, but if i write: modprobe ohci-hcd it says: ohci-hcd not found. As I said, that maybe interesting for your experts, but maybe clear to you also. Created attachment 217608 [details]
/var/log from simon
Okay, the problem is that the boot script is too impatient and times out before the drive becomes ready. It currently does 7 times spaced by 1 sec of 5 consecutive tries, which apparently is too short. We'll need to try for something like 30 seconds and it will definitely help to issue TEST UNIT READY and determine the device state. ie. if TUR indicates CHECK_SENSE w/ SK:ASC:ASCQ=02:04:01, it means LOGICAL UNIT IS IN PROCESS OF BECOMING READY which means that the drive has media in it and trying to recognize it in which case we can wait for it longer. Possible sense codes for TUR are described in section F.3.3 of t10 MMC-6 standard and as follows. For 04:01, we can wait longer knowing that the drive is doing something. for 02:04:02 and 02:03, we know that it's not gonna get ready by itself. The same goes for 02:30:01-03 or 02:3A:*. ATAPI devices often being cheesy, depending 100% on the sense data result isn't advisable. There probably needs to be some retry anyway but TUR can definitely help determining what's going on. SK ASC ASCQ Description 2 04 00 LOGICAL UNIT NOT READY, CAUSE NOT REPORTABLE 2 04 01 LOGICAL UNIT IS IN PROCESS OF BECOMING READY 2 04 02 LOGICAL UNIT NOT READY, INITIALIZING CMD. REQUIRED 2 04 03 LOGICAL UNIT NOT READY, MANUAL INTERVENTION REQUIRED 2 04 04 LOGICAL UNIT NOT READY, FORMAT IN PROGRESS 2 04 07 LOGICAL UNIT NOT READY, OPERATION IN PROGRESS 2 04 08 LOGICAL UNIT NOT READY, LONG WRITE IN PROGRESS 2 0C 07 WRITE ERROR RECOVERY NEEDED 2 0C 0F DEFECTS IN ERROR WINDOW 2 30 00 INCOMPATIBLE MEDIUM INSTALLED 2 30 01 CANNOT READ MEDIUM – UNKNOWN FORMAT 2 or 5 30 02 CANNOT READ MEDIUM – INCOMPATIBLE FORMAT 2 30 03 CLEANING CARTRIDGE INSTALLED 2 or 5 30 04 CANNOT WRITE MEDIUM – UNKNOWN FORMAT 2 or 5 30 05 CANNOT WRITE MEDIUM – INCOMPATIBLE FORMAT 2 or 5 30 06 CANNOT FORMAT MEDIUM – INCOMPATIBLE MEDIUM 2 30 07 CLEANING FAILURE 2 or 5 30 11 CANNOT WRITE MEDIUM – UNSUPPORTED MEDIUM VERSION 2 3A 00 MEDIUM NOT PRESENT 2 3A 01 MEDIUM NOT PRESENT – TRAY CLOSED 2 3A 02 MEDIUM NOT PRESENT – TRAY OPEN 2 3E 00 LOGICAL UNIT HAS NOT SELF-CONFIGURED YET Created attachment 217654 [details]
test-ready.c
Program source which issues TUR and prints sense code.
Scrap that. You can probably just use CDROM_DRIVE_STATUS ioctl which returns one of.. #define CDS_NO_INFO 0 /* if not implemented */ #define CDS_NO_DISC 1 #define CDS_TRAY_OPEN 2 #define CDS_DRIVE_NOT_READY 3 #define CDS_DISC_OK 4 Cc'ing Anna Bernathova as she was tackling related problem on bug #374526. Cc'ing Josef Reidinger who's working on bug #390204 where yast doesn't wait long enough for drive readiness. Similar problem here I have a SATA DVD Writer and a PATA CD-ROM The install fails in the SATA DVD RW but swapping the disk to the CD-ROM it works fine. It seems to load some modules then complain about not being able to see the image. Interesting! I tried it on 3 different Drives, but none of them worked properly. But on your machine one works and the other doesn't. Rob, can you please report logs as described in comment #16? Hi, have tried the install disk again same thing if i use the SATA drive.
I attach two of the files you requested, lspci was an unrecognised command so it didnt work.
I only get 120 seconds to do this as the install forces a reboot !
Hope this helps.
Rob
-----
Boot logging started on /dev/tty1(/dev/console) at Mon May 26 09:18:41 2008
-----> Starting boot shell on tty2
-----> Boot-Logging enabled on /dev/tty3
-----> Kernel logging enabled on: /dev/tty4
-----> Including required kernel modules...
-----> Probing module: sata_nv
-----> Probing module: pata_amd
-----> Probing module: ehci-hcd
-----> Probing module: ohci-hcd
Drive not ready yet... waiting
Drive not ready yet... waiting
Drive not ready yet... waiting
Drive not ready yet... waiting
Drive not ready yet... waiting
Drive not ready yet... waiting
-----> Couldn't find CD image configuration file
-----> rebootException: error consoles at Alt-F3/F4
-----> rebootException: reboot in 120 sec...
Linux version 2.6.25.3-2-default (geeko@buildhost) (gcc version 4.3.1 20080507 (prerelease) [gcc-4_3-branch revision 135036] (SUSE Linux) ) #1 SMP 2008-05-10 07:46:36 +0200
Command line: BOOT_IMAGE=linux initrd=initrd,12801024.spl ramdisk_size=512000 ramdisk_blocksize=4096 splash=silent vga=0x31a
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000003fff0000 (usable)
BIOS-e820: 000000003fff0000 - 000000003fff3000 (ACPI NVS)
BIOS-e820: 000000003fff3000 - 0000000040000000 (ACPI data)
BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fef00000 (reserved)
BIOS-e820: 00000000fefffc00 - 00000000ff000000 (reserved)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
Entering add_active_range(0, 0, 159) 0 entries of 3200 used
Entering add_active_range(0, 256, 262128) 1 entries of 3200 used
end_pfn_map = 1048576
DMI 2.3 present.
ACPI: RSDP 000F7230, 0014 (r0 Nvidia)
ACPI: RSDT 3FFF3040, 0030 (r1 Nvidia AWRDACPI 42302E31 AWRD 0)
ACPI: FACP 3FFF30C0, 0074 (r1 Nvidia AWRDACPI 42302E31 AWRD 0)
ACPI: DSDT 3FFF3180, 66D0 (r1 NVIDIA AWRDACPI 1000 MSFT 100000E)
ACPI: FACS 3FFF0000, 0040
ACPI: MCFG 3FFF9980, 003C (r1 Nvidia AWRDACPI 42302E31 AWRD 0)
ACPI: APIC 3FFF98C0, 006E (r1 Nvidia AWRDACPI 42302E31 AWRD 0)
Scanning NUMA topology in Northbridge 24
No NUMA configuration found
Faking a node at 0000000000000000-000000003fff0000
Entering add_active_range(0, 0, 159) 0 entries of 3200 used
Entering add_active_range(0, 256, 262128) 1 entries of 3200 used
Bootmem setup node 0 0000000000000000-000000003fff0000
NODE_DATA [000000000000b000 - 0000000000012fff]
bootmap [0000000000013000 - 000000000001afff] pages 8
early res: 0 [0-fff] BIOS data page
early res: 1 [6000-7fff] SMP_TRAMPOLINE
early res: 2 [200000-8b8bd7] TEXT DATA BSS
early res: 3 [3e3e9000-3ffbffbd] RAMDISK
early res: 4 [9f800-a07ff] EBDA
early res: 5 [8000-afff] PGTABLE
[ffffe20000000000-ffffe200001fffff] PMD ->ffff810001200000 on node 0
[ffffe20000200000-ffffe200003fffff] PMD ->ffff810001600000 on node 0
[ffffe20000400000-ffffe200005fffff] PMD ->ffff810001a00000 on node 0
[ffffe20000600000-ffffe200007fffff] PMD ->ffff810001e00000 on node 0
[ffffe20000800000-ffffe200009fffff] PMD ->ffff810002200000 on node 0
[ffffe20000a00000-ffffe20000bfffff] PMD ->ffff810002600000 on node 0
[ffffe20000c00000-ffffe20000dfffff] PMD ->ffff810002a00000 on node 0
Zone PFN ranges:
DMA 0 -> 4096
DMA32 4096 -> 1048576
Normal 1048576 -> 1048576
Movable zone start PFN for each node
early_node_map[2] active PFN ranges
0: 0 -> 159
0: 256 -> 262128
On node 0 totalpages: 262031
DMA zone: 56 pages used for memmap
DMA zone: 1729 pages reserved
DMA zone: 2214 pages, LIFO batch:0
DMA32 zone: 3527 pages used for memmap
DMA32 zone: 254505 pages, LIFO batch:31
Normal zone: 0 pages used for memmap
Movable zone: 0 pages used for memmap
Nvidia board detected. Ignoring ACPI timer override.
If you got timer trouble try acpi_use_timer_override
ACPI: PM-Timer IO Port: 0x4008
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 (Bootup-CPU)
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: BIOS IRQ0 pin2 override ignored.
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge)
ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge)
ACPI: IRQ9 used by override.
ACPI: IRQ14 used by override.
ACPI: IRQ15 used by override.
Setting APIC routing to flat
Using ACPI (MADT) for SMP configuration information
PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
PM: Registered nosave memory: 00000000000a0000 - 00000000000f0000
PM: Registered nosave memory: 00000000000f0000 - 0000000000100000
Allocating PCI resources starting at 50000000 (gap: 40000000:a0000000)
SMP: Allowing 1 CPUs, 0 hotplug CPUs
PERCPU: Allocating 50608 bytes of per cpu data
Built 1 zonelists in Node order, mobility grouping on. Total pages: 256719
Policy zone: DMA32
Kernel command line: BOOT_IMAGE=linux initrd=initrd,12801024.spl ramdisk_size=512000 ramdisk_blocksize=4096 splash=silent vga=0x31a
bootsplash: silent mode.
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
TSC calibrated against PM_TIMER
time.c: Detected 2211.327 MHz processor.
spurious 8259A interrupt: IRQ7.
Console: colour dummy device 80x25
console [tty0] enabled
Checking aperture...
Node 0: aperture @ c000000 size 32 MB
Aperture pointing to e820 RAM. Ignoring.
No AGP bridge found
Memory: 998164k/1048512k available (2368k kernel code, 49960k reserved, 1930k data, 404k init)
CPA: page pool initialized 1 of 1 pages preallocated
Calibrating delay using timer specific routine.. 4425.52 BogoMIPS (lpj=8851046)
Security Framework initialized
AppArmor: AppArmor initialized <NULL>
AppArmor: Registered secondary security module capability
Capability LSM initialized as secondary
Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
Mount-cache hash table entries: 256
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU 0/0 -> Node 0
SMP alternatives: switching to UP code
Freeing SMP alternatives: 25k freed
ACPI: Core revision 20070126
Parsing all Control Methods:
Table [DSDT](id 0001) - 990 Objects with 86 Devices 317 Methods 37 Regions
tbxface-0598 [00] tb_load_namespace : ACPI Tables successfully acquired
evxfevnt-0091 [00] enable : Transition to ACPI mode successful
Using local APIC timer interrupts.
APIC timer calibration result 12564426
Detected 12.564 MHz APIC timer.
Brought up 1 CPUs
CPU0 attaching sched-domain:
domain 0: span 00000000,00000000,00000000,00000001
groups: 00000000,00000000,00000000,00000001
net_namespace: 1016 bytes
Booting paravirtualized kernel on bare hardware
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: Using MMCONFIG at e0000000 - efffffff
PCI: Using configuration type 1
evgpeblk-0956 [00] ev_create_gpe_block : GPE 00 to 1F [_GPE] 4 regs on int 0x9
evgpeblk-0956 [00] ev_create_gpe_block : GPE 20 to 5F [_GPE] 8 regs on int 0x9
evgpeblk-1052 [00] ev_initialize_gpe_bloc: Found 8 Wake, Enabled 0 Runtime GPEs in this block
evgpeblk-1052 [00] ev_initialize_gpe_bloc: Found 0 Wake, Enabled 0 Runtime GPEs in this block
ACPI: EC: Look up EC in DSDT
Completing Region/Field/Buffer/Package initialization:........................................................................................................................................
Initialized 33/37 Regions 9/9 Fields 35/35 Buffers 59/79 Packages (999 nodes)
Initializing Device/Processor/Thermal objects by executing _INI methods:...
Executed 3 _INI methods requiring 1 _STA executions (examined 90 objects)
ACPI: Interpreter enabled
ACPI: (supports S0 S1 S3 S4 S5)
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Transparent bridge - 0000:00:09.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 *5 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNK2] (IRQs 3 4 *5 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNK3] (IRQs 3 4 5 *7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNK4] (IRQs 3 4 5 *7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNK5] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LUBA] (IRQs 3 4 5 7 9 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LUBB] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LMAC] (IRQs 3 *4 5 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LACI] (IRQs *3 4 5 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LMCI] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LSMB] (IRQs *3 4 5 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LUB2] (IRQs 3 4 5 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LIDE] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LSID] (IRQs 3 4 *5 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LFID] (IRQs 3 4 5 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LPCA] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [APC1] (IRQs 16) *0
ACPI: PCI Interrupt Link [APC2] (IRQs 17) *0
ACPI: PCI Interrupt Link [APC3] (IRQs 18) *0
ACPI: PCI Interrupt Link [APC4] (IRQs 19) *0
ACPI: PCI Interrupt Link [APC5] (IRQs *16), disabled.
ACPI: PCI Interrupt Link [APCF] (IRQs 20 21 22 23) *0
ACPI: PCI Interrupt Link [APCG] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [APCH] (IRQs 20 21 22 23) *0
ACPI: PCI Interrupt Link [APCJ] (IRQs 20 21 22 23) *0
ACPI: PCI Interrupt Link [APCK] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [APCS] (IRQs 20 21 22 23) *0
ACPI: PCI Interrupt Link [APCL] (IRQs 20 21 22 23) *0
ACPI: PCI Interrupt Link [APCZ] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [APSI] (IRQs 20 21 22 23) *0
ACPI: PCI Interrupt Link [APSJ] (IRQs 20 21 22 23) *0
ACPI: PCI Interrupt Link [APCP] (IRQs 20 21 22 23) *0, disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp: PnP ACPI: found 12 devices
ACPI: ACPI bus type pnp unregistered
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
AppArmor: AppArmor Filesystem Enabled
ACPI: RTC can wake from S4
system 00:01: ioport range 0x4000-0x407f has been reserved
system 00:01: ioport range 0x4080-0x40ff has been reserved
system 00:01: ioport range 0x4400-0x447f has been reserved
system 00:01: ioport range 0x4480-0x44ff has been reserved
system 00:01: ioport range 0x4800-0x487f has been reserved
system 00:01: ioport range 0x4880-0x48ff has been reserved
system 00:02: ioport range 0x4d0-0x4d1 has been reserved
system 00:02: ioport range 0x800-0x87f has been reserved
system 00:02: ioport range 0x290-0x297 has been reserved
system 00:0a: iomem range 0xe0000000-0xefffffff could not be reserved
system 00:0b: iomem range 0xf0000-0xf3fff could not be reserved
system 00:0b: iomem range 0xf4000-0xf7fff could not be reserved
system 00:0b: iomem range 0xf8000-0xfbfff could not be reserved
system 00:0b: iomem range 0xfc000-0xfffff could not be reserved
system 00:0b: iomem range 0x3fff0000-0x3fffffff could not be reserved
system 00:0b: iomem range 0xffff0000-0xffffffff could not be reserved
system 00:0b: iomem range 0x0-0x9ffff could not be reserved
system 00:0b: iomem range 0x100000-0x3ffeffff could not be reserved
system 00:0b: iomem range 0xfec00000-0xfec00fff could not be reserved
system 00:0b: iomem range 0xfee00000-0xfeefffff could not be reserved
system 00:0b: iomem range 0xfefff000-0xfeffffff could not be reserved
system 00:0b: iomem range 0xfff80000-0xfff80fff has been reserved
system 00:0b: iomem range 0xfff90000-0xfffbffff has been reserved
system 00:0b: iomem range 0xfffed000-0xfffeffff has been reserved
PCI: Bridge: 0000:00:09.0
IO window: a000-afff
MEM window: 0xda000000-0xda0fffff
PREFETCH window: disabled.
PCI: Bridge: 0000:00:0b.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Bridge: 0000:00:0c.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Bridge: 0000:00:0d.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Bridge: 0000:00:0e.0
IO window: 9000-9fff
MEM window: 0xd8000000-0xd9ffffff
PREFETCH window: 0x00000000d0000000-0x00000000d7ffffff
PCI: Setting latency timer of device 0000:00:09.0 to 64
PCI: Setting latency timer of device 0000:00:0b.0 to 64
PCI: Setting latency timer of device 0000:00:0c.0 to 64
PCI: Setting latency timer of device 0000:00:0d.0 to 64
PCI: Setting latency timer of device 0000:00:0e.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 6, 262144 bytes)
TCP established hash table entries: 131072 (order: 9, 2097152 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
Unpacking initramfs...<7>Switched to high resolution mode on CPU 0
done
Freeing initrd memory: 28507k freed
audit: initializing netlink socket (disabled)
type=2000 audit(1211793520.384:1): initialized
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci 0000:00:00.0: Enabling HT MSI Mapping
pci 0000:00:0b.0: Enabling HT MSI Mapping
pci 0000:00:0b.0: Found enabled HT MSI Mapping
pci 0000:00:0b.0: Linking AER extended capability
pci 0000:00:0c.0: Enabling HT MSI Mapping
pci 0000:00:0c.0: Found enabled HT MSI Mapping
pci 0000:00:0c.0: Linking AER extended capability
pci 0000:00:0d.0: Enabling HT MSI Mapping
pci 0000:00:0d.0: Found enabled HT MSI Mapping
pci 0000:00:0d.0: Linking AER extended capability
pci 0000:00:0e.0: Enabling HT MSI Mapping
pci 0000:00:0e.0: Found enabled HT MSI Mapping
pci 0000:00:0e.0: Linking AER extended capability
pci 0000:01:00.0: Boot video device
PCI: Setting latency timer of device 0000:00:0b.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:0b.0:pcie00]
Allocate Port Service[0000:00:0b.0:pcie03]
PCI: Setting latency timer of device 0000:00:0c.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:0c.0:pcie00]
Allocate Port Service[0000:00:0c.0:pcie03]
PCI: Setting latency timer of device 0000:00:0d.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:0d.0:pcie00]
Allocate Port Service[0000:00:0d.0:pcie03]
PCI: Setting latency timer of device 0000:00:0e.0 to 64
assign_interrupt_mode Found MSI capability
Allocate Port Service[0000:00:0e.0:pcie00]
Allocate Port Service[0000:00:0e.0:pcie03]
vesafb: framebuffer at 0xd0000000, mapped to 0xffffc20010580000, using 10240k, total 16384k
vesafb: mode is 1280x1024x16, linelength=2560, pages=5
vesafb: scrolling: redraw
vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
bootsplash 3.1.6-2004/03/31: looking for picture...
bootsplash: silentjpeg size 208945 bytes
bootsplash: ...found (1280x1024, 286424 bytes, v3).
Console: switching to colour frame buffer device 156x60
fb0: VESA VGA frame buffer device
Non-volatile memory driver v1.2
Linux agpgart interface v0.103
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13: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
input: PC Speaker as /devices/platform/pcspkr/input/input0
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
cpuidle: using governor ladder
cpuidle: using governor menu
NET: Registered protocol family 1
registered taskstats version 1
Freeing unused kernel memory: 404k freed
Write protecting the kernel read-only data: 1688k
input: PS2++ Logitech MX Mouse as /devices/platform/i8042/serio1/input/input2
IT8712 SuperIO detected.
No dock devices found.
SCSI subsystem initialized
libata version 3.00 loaded.
sata_nv 0000:00:07.0: version 3.5
ACPI: PCI Interrupt Link [APSI] enabled at IRQ 23
ACPI: PCI Interrupt 0000:00:07.0[A] -> Link [APSI] -> GSI 23 (level, low) -> IRQ 23
PCI: Setting latency timer of device 0000:00:07.0 to 64
scsi0 : sata_nv
scsi1 : sata_nv
ata1: SATA max UDMA/133 cmd 0x9f0 ctl 0xbf0 bmdma 0xd800 irq 23
ata2: SATA max UDMA/133 cmd 0x970 ctl 0xb70 bmdma 0xd808 irq 23
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: ATAPI: TSSTcorpCD/DVDW SH-S183A, SB02, max UDMA/33
ata1.00: applying bridge limits
ata1.00: configured for UDMA/33
ata2: SATA link down (SStatus 0 SControl 300)
scsi 0:0:0:0: CD-ROM TSSTcorp CD/DVDW SH-S183A SB02 PQ: 0 ANSI: 5
ACPI: PCI Interrupt Link [APSJ] enabled at IRQ 22
ACPI: PCI Interrupt 0000:00:08.0[A] -> Link [APSJ] -> GSI 22 (level, low) -> IRQ 22
PCI: Setting latency timer of device 0000:00:08.0 to 64
scsi2 : sata_nv
scsi3 : sata_nv
ata3: SATA max UDMA/133 cmd 0x9e0 ctl 0xbe0 bmdma 0xc400 irq 22
ata4: SATA max UDMA/133 cmd 0x960 ctl 0xb60 bmdma 0xc408 irq 22
ata3: SATA link down (SStatus 0 SControl 300)
ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata4.00: ATA-7: SAMSUNG SP1614C, SW100-34, max UDMA7
ata4.00: 312581808 sectors, multi 1: LBA48
ata4.00: configured for UDMA/133
scsi 3:0:0:0: Direct-Access ATA SAMSUNG SP1614C SW10 PQ: 0 ANSI: 5
pata_amd 0000:00:06.0: version 0.3.10
PCI: Setting latency timer of device 0000:00:06.0 to 64
scsi4 : pata_amd
scsi5 : pata_amd
ata5: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xf000 irq 14
ata6: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xf008 irq 15
ata6.01: ATAPI: ATAPI-CD ROM-DRIVE-56MAX, VER 56HA, max UDMA/33
ata6: nv_mode_filter: 0x739f&0x701f->0x701f, BIOS=0x7000 (0xc0) ACPI=0x701f (600:60:0x1c)
ata6.01: configured for UDMA/33
scsi 5:0:1:0: CD-ROM ATAPI-CD ROM-DRIVE-56MAX 56HA PQ: 0 ANSI: 5
Uniform Multi-Platform E-IDE driver
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Driver 'sr' needs updating - please use bus_type methods
sr0: scsi3-mmc drive: 40x/40x writer dvd-ram cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 0:0:0:0: Attached scsi CD-ROM sr0
sr1: scsi3-mmc drive: 0x/56x cd/rw xa/form2 cdda tray
sr 5:0:1:0: Attached scsi CD-ROM sr1
Driver 'sd' needs updating - please use bus_type methods
sd 3:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB)
sd 3:0:0:0: [sda] Write Protect is off
sd 3:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 3:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 3:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB)
sd 3:0:0:0: [sda] Write Protect is off
sd 3:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 3:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sda: sda1 sda2
sd 3:0:0:0: [sda] Attached SCSI disk
st: Version 20080221, fixed bufsize 32768, s/g segs 256
Driver 'st' needs updating - please use bus_type methods
sr 0:0:0:0: Attached scsi generic sg0 type 5
sd 3:0:0:0: Attached scsi generic sg1 type 0
sr 5:0:1:0: Attached scsi generic sg2 type 5
brd: module loaded
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
ACPI: PCI Interrupt Link [APCL] enabled at IRQ 21
ACPI: PCI Interrupt 0000:00:02.1[B] -> Link [APCL] -> GSI 21 (level, low) -> IRQ 21
PCI: Setting latency timer of device 0000:00:02.1 to 64
ehci_hcd 0000:00:02.1: EHCI Host Controller
ehci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:02.1: debug port 1
PCI: cache line size of 64 is not supported by device 0000:00:02.1
ehci_hcd 0000:00:02.1: irq 21, io mem 0xda105000
ehci_hcd 0000:00:02.1: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 10 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.25.3-2-default ehci_hcd
usb usb1: SerialNumber: 0000:00:02.1
ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
ACPI: PCI Interrupt 0000:05:08.2[C] -> Link [APC1] -> GSI 16 (level, low) -> IRQ 16
ehci_hcd 0000:05:08.2: EHCI Host Controller
ehci_hcd 0000:05:08.2: new USB bus registered, assigned bus number 2
ehci_hcd 0000:05:08.2: irq 16, io mem 0xda003000
ehci_hcd 0000:05:08.2: USB 2.0 started, EHCI 0.95, driver 10 Dec 2004
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 5 ports detected
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: EHCI Host Controller
usb usb2: Manufacturer: Linux 2.6.25.3-2-default ehci_hcd
usb usb2: SerialNumber: 0000:05:08.2
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usb 1-8: new high speed USB device using ehci_hcd and address 2
usb 1-8: configuration #1 chosen from 1 choice
scsi6 : SCSI emulation for USB Mass Storage devices
usb 1-8: New USB device found, idVendor=0781, idProduct=5204
usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-8: Product: Cruzer Crossfire
usb 1-8: Manufacturer: SanDisk Corporation
usb 1-8: SerialNumber: 000018741B628156
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
scsi 6:0:0:0: Direct-Access SanDisk Cruzer Crossfire 2.01 PQ: 0 ANSI: 2
sd 6:0:0:0: [sdb] 2005432 512-byte hardware sectors (1027 MB)
sd 6:0:0:0: [sdb] Write Protect is off
sd 6:0:0:0: [sdb] Mode Sense: 03 00 00 00
sd 6:0:0:0: [sdb] Assuming drive cache: write through
sd 6:0:0:0: [sdb] 2005432 512-byte hardware sectors (1027 MB)
sd 6:0:0:0: [sdb] Write Protect is off
sd 6:0:0:0: [sdb] Mode Sense: 03 00 00 00
sd 6:0:0:0: [sdb] Assuming drive cache: write through
sdb: sdb1
sd 6:0:0:0: [sdb] Attached SCSI removable disk
sd 6:0:0:0: Attached scsi generic sg3 type 0
usb-storage: device scan complete
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda2, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
if you boot the CD with kiwidebug=1 as kernel parameter you will get a shell instead of a reboot exception I'm currently in the loop to add the sense checking code provided in this report. Stay tuned :) Ok have now rebooted and tried again. cat /proc/interrupts > interrupts.out gives me nothing either when using the install disk or the installed system. From the installed system I can use lspci but not from the shell when the install fails, hope this will be of some use anyway. Here it is: 00:00.0 Memory controller [0580]: nVidia Corporation CK804 Memory Controller [10de:005e] (rev a3) 00:01.0 ISA bridge [0601]: nVidia Corporation CK804 ISA Bridge [10de:0050] (rev a3) 00:01.1 SMBus [0c05]: nVidia Corporation CK804 SMBus [10de:0052] (rev a2) 00:02.0 USB Controller [0c03]: nVidia Corporation CK804 USB Controller [10de:005a] (rev a2) 00:02.1 USB Controller [0c03]: nVidia Corporation CK804 USB Controller [10de:005b] (rev a3) 00:04.0 Multimedia audio controller [0401]: nVidia Corporation CK804 AC'97 Audio Controller [10de:0059] (rev a2) 00:06.0 IDE interface [0101]: nVidia Corporation CK804 IDE [10de:0053] (rev f2) 00:07.0 IDE interface [0101]: nVidia Corporation CK804 Serial ATA Controller [10de:0054] (rev f3) 00:08.0 IDE interface [0101]: nVidia Corporation CK804 Serial ATA Controller [10de:0055] (rev f3) 00:09.0 PCI bridge [0604]: nVidia Corporation CK804 PCI Bridge [10de:005c] (rev a2) 00:0a.0 Bridge [0680]: nVidia Corporation CK804 Ethernet Controller [10de:0057] (rev a3) 00:0b.0 PCI bridge [0604]: nVidia Corporation CK804 PCIE Bridge [10de:005d] (rev a3) 00:0c.0 PCI bridge [0604]: nVidia Corporation CK804 PCIE Bridge [10de:005d] (rev a3) 00:0d.0 PCI bridge [0604]: nVidia Corporation CK804 PCIE Bridge [10de:005d] (rev a3) 00:0e.0 PCI bridge [0604]: nVidia Corporation CK804 PCIE Bridge [10de:005d] (rev a3) 00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration [1022:1100] 00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map [1022:1101] 00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller [1022:1102] 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control [1022:1103] 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)] [1002:5b60] 01:00.1 Display controller [0380]: ATI Technologies Inc RV370 [Radeon X300SE] [1002:5b70] 05:07.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ [10ec:8139] (rev 10) 05:08.0 USB Controller [0c03]: NEC Corporation USB [1033:0035] (rev 41) 05:08.1 USB Controller [0c03]: NEC Corporation USB [1033:0035] (rev 41) 05:08.2 USB Controller [0c03]: NEC Corporation USB 2.0 [1033:00e0] (rev 02) Steffen can you read comment #46 and tell me if the following modules are correctly and in the right order ? -----> Probing module: sata_nv -----> Probing module: pata_amd -----> Probing module: ehci-hcd -----> Probing module: ohci-hcd thanks Well, at least I don't see anything wrong with it. sorry for the delay. I finally got this problem fixed after I setup a test machine with two drives. - fixed CDDevice and CDMount functions - added sense code checking when mounting the detected devices This is done by the code provided in comment #40. Thanks a lot. I called it "driveready" and added it to the kiwi-tools package my test machines with one or two drives works now as expected. If the problem remains feel free to re-open the bug. If this is required what I don't hope :-) the following process should be used to provide more log information: 1) boot with kiwidebug=1 2) plug in a USB stick and copy the following log file on the device /var/log/boot.kiwi Thanks *** Bug 381671 has been marked as a duplicate of this bug. *** *** Bug 392666 has been marked as a duplicate of this bug. *** |