« Return to Thread: [Bug 53443] NEW: SATA renumbering prevents boot

[Bug 53443] NEW: SATA renumbering prevents boot

by Bugzilla from bugzilla@qa.mandrivalinux.com :: Rate this Message:

Reply to Author | View in Thread

https://qa.mandriva.com/show_bug.cgi?id=53443

  Summary    : SATA renumbering prevents boot
  Product    : Mandriva Linux
  Component  : Core Packages
  Version    : Cooker
  Keywords   : Triaged
  Status     : NEW
  Severity   : critical
  Priority   : release_critical
  Assigned To: kernel@...
  Reported By: t.blackwell@...





--- Comment #5 from Tony Blackwell <t.blackwell@...>  2009-09-10 21:50:38 CEST ---
For comparison, the following is the output of dmesg on the same hardware but
_from 2009 x86_64_.  I'll put in the 2010 dmesg in a subsequent post.

2009 dmesg (down to the point where shorewall starts flooding)

sd 3:0:0:0: Attached scsi generic sg5 type 0
sd 4:0:0:0: Attached scsi generic sg6 type 0
scsi 6:0:1:0: Attached scsi generic sg7 type 5
input: PC Speaker as /class/input/input3
Driver 'sr' needs updating - please use bus_type methods
sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 6:0:1:0: Attached scsi CD-ROM sr0
ACPI: SSDT BF6980C0, 0403 (r1 DpgPmm  P001Ist       11 INTL 20060113)
processor ACPI0007:00: registered as cooling_device0
ACPI: SSDT BF6984D0, 0403 (r1 DpgPmm  P002Ist       12 INTL 20060113)
processor ACPI0007:01: registered as cooling_device1
ACPI: SSDT BF6988E0, 0403 (r1 DpgPmm  P003Ist       12 INTL 20060113)
processor ACPI0007:02: registered as cooling_device2
ACPI: SSDT BF698CF0, 0403 (r1 DpgPmm  P004Ist       12 INTL 20060113)
processor ACPI0007:03: registered as cooling_device3
ACPI: SSDT BF699100, 0403 (r1 DpgPmm  P005Ist       12 INTL 20060113)
processor ACPI0007:04: registered as cooling_device4
ACPI: SSDT BF699510, 0403 (r1 DpgPmm  P006Ist       12 INTL 20060113)
processor ACPI0007:05: registered as cooling_device5
ACPI: SSDT BF699920, 0403 (r1 DpgPmm  P007Ist       12 INTL 20060113)
processor ACPI0007:06: registered as cooling_device6
ACPI: SSDT BF699D30, 0403 (r1 DpgPmm  P008Ist       12 INTL 20060113)
processor ACPI0007:07: registered as cooling_device7
r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
r8169 0000:06:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
r8169 0000:06:00.0: setting latency timer to 64
r8169 0000:06:00.0: no MSI. Back to INTx.
eth0: RTL8168c/8111c at 0xffffc20000c52000, 00:26:18:54:a0:a9, XID 3c4000c0 IRQ
18
udev: renamed network interface eth0 to eth1
ACPI: WMI: Mapper loaded
input: Power Button (FF) as /class/input/input4
ACPI: Power Button (FF) [PWRF]
input: Power Button (CM) as /class/input/input5
rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
rtc0: alarms up to one month, y3k, hpet irqs
HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
HDA Intel 0000:00:1b.0: setting latency timer to 64
hda_codec: Unknown model for ALC883, trying auto-probe from BIOS...
ACPI: Power Button (CM) [PWRB]
i801_smbus 0000:00:1f.3: PCI INT C -> GSI 18 (level, low) -> IRQ 18
ACPI: I/O resource 0000:00:1f.3 [0x400-0x41f] conflicts with ACPI region SMRG
[0x400-0x40f]
ACPI: Device needs an ACPI driver
Linux video capture interface: v2.00
cx2388x alsa driver version 0.0.6 loaded
cx88_audio 0000:08:01.1: PCI INT A -> GSI 17 (level, low) -> IRQ 17
cx88[0]: subsystem: 18ac:db40, board: DViCO FusionHDTV DVB-T Hybrid
[card=46,autodetected]
cx88[0]: TV tuner type 72, Radio tuner type -1
cx88/2: cx2388x MPEG-TS Driver Manager version 0.0.6 loaded
cx88/0: cx2388x v4l2 driver version 0.0.6 loaded
tuner' 1-0061: chip found @ 0xc2 (cx88[0])
tuner-simple 1-0061: creating new instance
tuner-simple 1-0061: type set to 72 (Thomson FE6600)
cx88[0]/1: CX88x/0: ALSA support for cx2388x boards
cx8800 0000:08:01.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
cx88[0]/0: found at 0000:08:01.0, rev: 5, irq: 17, latency: 64, mmio:
0xf8000000
cx88[0]/0: registered device video0 [v4l2]
cx88[0]/0: registered device vbi0
cx88[0]/2: cx2388x 8802 Driver Manager
cx88-mpeg driver manager 0000:08:01.2: PCI INT A -> GSI 17 (level, low) -> IRQ
17
cx88[0]/2: found at 0000:08:01.2, rev: 5, irq: 17, latency: 64, mmio:
0xfa000000
cx88/2: cx2388x dvb driver version 0.0.6 loaded
cx88/2: registering cx8802 driver, type: dvb access: shared
cx88[0]/2: subsystem: 18ac:db40, board: DViCO FusionHDTV DVB-T Hybrid [card=46]
cx88[0]/2: cx2388x based DVB/ATSC card
tuner-simple 1-0061: attaching existing instance
tuner-simple 1-0061: type set to 72 (Thomson FE6600)
DVB: registering new adapter (cx88[0])
DVB: registering frontend 0 (Zarlink ZL10353 DVB-T)...
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.14.0-ioctl (2008-04-23) initialised:
dm-devel@...
EXT3 FS on sda3, internal journal
scsi 8:0:0:0: Direct-Access     Multi    Flash Reader     1.00 PQ: 0 ANSI: 0
sd 8:0:0:0: [sdh] Attached SCSI removable disk
sd 8:0:0:0: Attached scsi generic sg8 type 0
usb-storage: device scan complete
scsi 9:0:0:0: Direct-Access     Generic  Flash HS-CF      4.44 PQ: 0 ANSI: 0
sd 9:0:0:0: [sdi] Attached SCSI removable disk
sd 9:0:0:0: Attached scsi generic sg9 type 0
scsi 9:0:0:1: Direct-Access     Generic  Flash HS-COMBO   4.44 PQ: 0 ANSI: 0
sd 9:0:0:1: [sdj] Attached SCSI removable disk
sd 9:0:0:1: Attached scsi generic sg10 type 0
usb-storage: device scan complete
loop: module loaded
Adding 6843648k swap on /dev/sda6.  Priority:-1 extents:1 across:6843648k
ip_tables: (C) 2000-2006 Netfilter Core Team
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Plase use
nf_conntrack.acct=1 kernel paramater, acct=1 nf_conntrack module option or
sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
ctnetlink v0.93: registering with nfnetlink.
ClusterIP Version 0.8 loaded successfully
netfilter PSD loaded - (c) astaro AG
IFWLOG: register target
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
Bluetooth: Core ver 2.13
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP ver 2.11
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.10
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bridge firewalling registered
r8169: eth1: link up
r8169: eth1: link up
NET: Registered protocol family 17
/dev/vmmon[5749]: Module vmmon: registered with major=10 minor=165
/dev/vmmon[5749]: Initial HV check: anyNotCapable=0 anyUnlocked=0 anyEnabled=1
anyDisabled=0
/dev/vmmon[5749]: HV check: anyNotCapable=0 anyUnlocked=0 anyEnabled=1
anyDisabled=0
/dev/vmmon[5749]: Module vmmon: initialized
/dev/vmci[5812]: VMCI: Driver initialized.
/dev/vmci[5812]: Module vmci: registered with major=10 minor=58
/dev/vmci[5812]: Module vmci: initialized
ppdev: user-space parallel port driver
eth1: no IPv6 routers present
Shorewall:net2fw:DROP:IN=eth1 OUT=
MAC=00:26:18:54:a0:a9:00:13:46:5e:23:9d:08:00 SRC=192.168.0.1 DST=192.168.0.166
LEN=257 TOS=0x00 PREC=0x00 TTL=64 ID=29 PROTO=UDP SPT=1900 DPT=51056 LEN=237



----------------------------------------------------------------------------
Original Bug Text:


Description of problem:
hardware:
ASUS P6T motherboard, i7 920 CPU, several SATA drives of which first 2 are 1.5Gb each.  1st SATA drive has a 35gb windows partition then 2 ext3 each of about 25 Gb, then extended partition containing mostly a large encrypted partition as well as swap.  The next 1.5Gb HD is all a single encrypted partition.
windows on sda1, cooker on sda2, 2009 on sda3.  All has been working well, using lilo from the 2020beta1 on root of sda to boot cooker on sda2 or the older 2009 on sda3.

Last night loaded all the updates offered - around 500 files.

Today boot failed.  Eventually found that now cooker thinks it is on sdb.  Lilo still points at sda, which cooker now thinks is the second HD with only the encrypted data partition on it.  Curiously lilo can still start the 2009 partition on sda3, which still corectly knows it is on sda and works fine.

Work-Around:
Edited lilo.conf, changed everyting to sdb, ran lilo and cooker boots and runs OK now.


Summary:
Last night's updates have somehow changed SATA enumeration to prevent boot without manually fixing lilo.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.



--
Configure bugmail: https://qa.mandriva.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

 « Return to Thread: [Bug 53443] NEW: SATA renumbering prevents boot