Opened 10 years ago

Last modified 3 years ago

#11258 new bug

HP xw9400 KDL on CD install

Reported by: vidrep Owned by: nobody
Priority: normal Milestone: R1
Component: Drivers/Disk Version: R1/Development
Keywords: boot-failure Cc:
Blocked By: Blocking:
Platform: All

Description

Burned a pair of CD installation disc's, and created a pair of USB boot drives. Each pair had both the nightly cd iso and the anyboot image. The HP xw9400 KDL's on every attempt to boot and install to a hard drive partition from a CD. Booting and installing from a USB drive works without any problem. Attached is a photo of the KDL and listdev for this PC.

Attachments (11)

listdev_xw9400 (3.9 KB ) - added by vidrep 10 years ago.
IMG_0182.JPG (1.4 MB ) - added by vidrep 10 years ago.
syslog (150.0 KB ) - added by vidrep 10 years ago.
listusb (9.1 KB ) - added by vidrep 10 years ago.
IMG_0276.JPG (738.4 KB ) - added by vidrep 4 years ago.
IMG_0278.JPG (894.8 KB ) - added by vidrep 4 years ago.
IMG_0279.JPG (891.6 KB ) - added by vidrep 4 years ago.
IMG_0281.JPG (931.1 KB ) - added by vidrep 4 years ago.
serial.txt (51.2 KB ) - added by vidrep 4 years ago.
serial2.txt (69.8 KB ) - added by vidrep 4 years ago.
serial3.txt (67.4 KB ) - added by vidrep 4 years ago.

Change History (28)

by vidrep, 10 years ago

Attachment: listdev_xw9400 added

by vidrep, 10 years ago

Attachment: IMG_0182.JPG added

comment:1 by diver, 10 years ago

Component: - GeneralDrivers/Disk

comment:2 by korli, 10 years ago

A syslog on the failed boot would be interesting. The interesting part is the disk discovery by the usb_disk driver.

EDIT: you didn't describe what your optical drive was. USB or SATA?

Last edited 10 years ago by korli (previous) (diff)

comment:3 by vidrep, 10 years ago

Drive Info: HP TSSTcorp CDDVDW TS-H653N HB02 (SATA)

If it will help, I'll try to rig up a Windows PC to capture serial debug output during boot attempts.

My other HP PC (model dc5750) that I also test Haiku on, has the opposite problem. It will KDL on USB/anyboot, but installs fine from CD/ISO.

comment:4 by vidrep, 10 years ago

This issue is still present in hrev49143. I have not tested with this PC since December. I did a fresh install to a hard drive partition from USB anyboot, then tried to do a CD iso install. The CD iso image will KDL when attempting to boot into the installer. The same message is displayed as in the earlier photo (IMG_0182.JPG). Attached is a syslog, in case it may be of use.

by vidrep, 10 years ago

Attachment: syslog added

by vidrep, 10 years ago

Attachment: listusb added

comment:5 by vidrep, 9 years ago

I attempted a fresh install of hrev49852 x86_gcc2 and x86_64 on this same PC in preparation for testing for another ticket. It invoked KDL on two occasions, but eventually I was able to do an install from CD. So, apparently not fixed yet.

comment:6 by mmlr, 4 years ago

The syslog in this ticket shows two SATA controllers with a possibly mangled PCI BAR. It is unclear wheter or not there would be another BAR at index 5 at all, but if so it would have been erroneously overwritten before and is fixed in hrev54417.

comment:7 by vidrep, 4 years ago

Tried again today with hrev54503 x86_64 and it still KDL's when attempting to boot from a CD. USB boot, drive setup and installation went without any issues.

comment:8 by vidrep, 4 years ago

I have attached a photo of the most recent KDL.

by vidrep, 4 years ago

Attachment: IMG_0276.JPG added

in reply to:  7 comment:9 by mmlr, 4 years ago

Replying to vidrep:

Tried again today with hrev54503 x86_64 and it still KDL's when attempting to boot from a CD. USB boot, drive setup and installation went without any issues.

It was worth a try, thanks for testing!

The syslog of the successful boot shows the ATAPI CD drive to be identified properly, so it doesn't look completely broken. Maybe you can enable on-screen debug output in the bootloader and attach photos of the last few screens of output? The problem should show somewhere before the disk/partition dump starts.

Additionally you could try inserting the CD after successfully booting via another method and attach a syslog from that. If there is a general problem with access to the device it should also show there.

comment:10 by vidrep, 4 years ago

I took a series of photos, but some were too blurry to be of any use. Maybe we'll get lucky with one of the good ones as attached.

by vidrep, 4 years ago

Attachment: IMG_0278.JPG added

by vidrep, 4 years ago

Attachment: IMG_0279.JPG added

by vidrep, 4 years ago

Attachment: IMG_0281.JPG added

comment:11 by mmlr, 4 years ago

Those are from the PCI dump in early init. The problem would probably show in the next one or two screens.

comment:12 by vidrep, 4 years ago

Can we capture that debug output somehow, rather than taking photos? Capture output on a second PC with SerialConnect?

comment:13 by vidrep, 4 years ago

I setup the PC for serial debug output and captured a log (attached).

by vidrep, 4 years ago

Attachment: serial.txt added

comment:14 by vidrep, 4 years ago

Here's a second log which appears to have additional data from when I switched between PC's with a KVM switch (attached).

by vidrep, 4 years ago

Attachment: serial2.txt added

comment:15 by mmlr, 4 years ago

The first report shows a timeout on spinlock acquisition, apparently due to serial debug output that can't be sent quickly enough. This should be continueable KDL by using the co KDL command (either by keyboard or over the serial line).

The second report is more complete and shows that the CD is identified properly. It also shows the boot method to be 0 for BOOT_METHOD_HARD_DISK instead of BOOT_METHOD_CD. This makes it appear similar or the same as what's happening in #16358, i.e. the CD being ignored as a boot candidate due to the boot method saying it wasn't booted from CD.

In this case though, there appears to be a Haiku install on one of the partitions. Is it possible, that the bootloader in use is coming from the disk instead of the CD? Can you unplug the disk just to make sure that it indeed boots from CD?

comment:16 by vidrep, 4 years ago

I wiped the hard drive that I had Haiku installed on and initiated another CD boot with debugging enabled (see attached serial log).

by vidrep, 4 years ago

Attachment: serial3.txt added

comment:17 by waddlesplash, 3 years ago

Keywords: boot-failure added
Note: See TracTickets for help on using tickets.