Re: [proaudio] 2.6.17-r3 problems

["Mark Knecht" <markknecht@xxxxxxxxx>]

Karstan,
  Hello again and sorry for the continuing problems.

  Possibly the way to approach this here is to do a lot of the ground
work that you would need to do for the LKML anyway. That way you would
have the information they are going to require as well as the
possibility that we will get the problems worked out.

  I think the first thing would be to get a simple listing of the
hardware in the machine using lspci. Post back the output of that
command.

  Second, since this is an NForce chipset, and is reasonably new,
does the machine use SATA disk drives? If so please make sure that
CONFIG_SCSI_SATA_NV=y is set in your .config file. Possibly you have
the right drivers built in but not the right chipset support.

  Lastly for now I had one machine that had almost exactly the same
problem you are having. In that case it turned out that the two
kernels were booting the on-board and off-board disk controllers out
of order.With one kernel my drive was /dev/hda and with the other it
was /dev/hde. It took me at least a week to figure that out, but the
answer eventually came by very carefully watching the boot process.
There is a point very early on where the system says some things about
the drive hardware. I finally noticed that this had changed and was
able to work things out from there. Maybe you'll discover something
similar if you look carefully.

  Notice all the crazy stuff going on here on my NForce-4 MB:

NFORCE-CK804: IDE controller at PCI slot 0000:00:06.0
NFORCE-CK804: chipset revision 242
NFORCE-CK804: not 100% native mode: will probe irqs later
NFORCE-CK804: 0000:00:06.0 (rev f2) UDMA133 controller
   ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
   ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
Probing IDE interface ide0...
hda: LITE-ON DVDRW LDW-411S, ATAPI CD/DVD-ROM drive
hdb: LITE-ON LTR-48246S, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
Probing IDE interface ide1...
hda: ATAPI 40X DVD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
hdb: ATAPI 48X CD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
megaraid cmm: 2.20.2.6 (Release Date: Mon Mar 7 00:01:03 EST 2005)
megaraid: 2.20.4.8 (Release Date: Mon Apr 11 12:27:22 EST 2006)
megasas: 00.00.02.04 Fri Feb 03 14:31:44 PST 2006
libata version 1.20 loaded.
sata_nv 0000:00:07.0: version 0.8
ACPI: PCI Interrupt Link [APSI] enabled at IRQ 22
GSI 17 sharing vector 0xE1 and IRQ 17
ACPI: PCI Interrupt 0000:00:07.0[A] -> Link [APSI] -> GSI 22 (level,
low) -> IRQ  225
PCI: Setting latency timer of device 0000:00:07.0 to 64
ata1: SATA max UDMA/133 cmd 0x9F0 ctl 0xBF2 bmdma 0xD800 irq 225
ata2: SATA max UDMA/133 cmd 0x970 ctl 0xB72 bmdma 0xD808 irq 225
ata1: SATA link down (SStatus 0)
scsi0 : sata_nv
ata2: SATA link down (SStatus 0)
scsi1 : sata_nv
ACPI: PCI Interrupt Link [APSJ] enabled at IRQ 21
GSI 18 sharing vector 0xE9 and IRQ 18
ACPI: PCI Interrupt 0000:00:08.0[A] -> Link [APSJ] -> GSI 21 (level,
low) -> IRQ  233
PCI: Setting latency timer of device 0000:00:08.0 to 64
ata3: SATA max UDMA/133 cmd 0x9E0 ctl 0xBE2 bmdma 0xC400 irq 233
ata4: SATA max UDMA/133 cmd 0x960 ctl 0xB62 bmdma 0xC408 irq 233
ata3: SATA link up 1.5 Gbps (SStatus 113)
ata3: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4023 85:3468 86:3c01 87:4023 88:407f
ata3: dev 0 ATA-7, max UDMA/133, 488397168 sectors: LBA48
nv_sata: Primary device added
nv_sata: Primary device removed
nv_sata: Secondary device added
nv_sata: Secondary device removed
ata3: dev 0 configured for UDMA/133
scsi2 : sata_nv
ata4: SATA link down (SStatus 0)
scsi3 : sata_nv
 Vendor: ATA       Model: ST3250823AS       Rev: 3.03
 Type:   Direct-Access                      ANSI SCSI revision: 05
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
sda: sda1 sda2 sda3 < sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda12 >
sd 2:0:0:0: Attached scsi disk sda

  Even though the drives end up being hda drives I still have to load
the SCSI stuff to get them to work due to the way SATA is supported.

  Lastly, you might look at dmesg VERY carefully when the machine
boots under 2.6.16 to look for other stuff, then watch what you can
under 2.6.17 for any differences.

Best of luck,
Mark



On 6/28/06, krgn <k.gebbert@xxxxxxxxx> wrote:
>  Ok, just to double check, I have tried to compile the last 2.6.16.22 with
> more or less exactly the same config as before, and it worked immediately.
>  I am unsure how to proceed, whether to tak this issue to gentoo-user or
> even maybe to the kernel people? It seems that the problem clearly is
> loading the ext3/////ext2 driver on startup so the disk can be mounted. For
> this try, I compiled everything into the kernel (which, yeah, I tryed with
> 2.6.17-rt1 too ;)).
>  Could someone maybe give adivce on how to proceed with this, since I think
> I have circled it so far, that one can say it must have to do with the new
> kernel version.
>  I also found this, looking for changes in the ext3/2 driver:
>         http://www.linuxdevices.com/news/NS2182308099.html
>  This does not seem to be a good/detailed source for info, yet it might be a
> hint towards the problem.
>  any clues?
>
>  Karsten
>
>
>  Mark Knecht wrote:
> On 6/27/06, krgn <k.gebbert@xxxxxxxxx> wrote:
>
> hi Mark,
>
>  thanks, that was already very helpful, I saw now actually how different
>  things are from .16 to .17 so luckily I ended up with a newer, different
>  error which is now more complicated to show, since I don't reach a stage
>  anymore, where I can grab a log or so.
>  Bascially, when reaching something like this stage here,
>
>                     VFS: Disk quotas dquot_6.5.1
>                     Dquot-cache hash table entries: 1024 (order 0, 4096
>  bytes)
>                                    ..........
>                     VFS: Mounted root (ext2 filesystem) readonly.
>                      Time: tsc clocksource has been installed.
>
>  the newer kernel tells me something like it can't mount my root
>  partition and that 'block(0,0)' is unknown. I double checked against my
>  old config, changed the new one to the old settings and recompiled, but
>  no joy. I appended the new config so maybe someone who might have a clue
>  what this might be, can have a look.
>  normally, my root partition is mounted like this:
>                  /dev/hda5 on / type ext3 (rw,noatime,user_xattr)
>  and I also checked again grub settings and the fstab file, but there was
>  nothing strange, so must assume its something about the configuration,
>  or the kernel again (since my old one boots fine with the same grub
>  settings)
>  any idea about VFS?
>
>  thanks,
>
>  KArsten
>
>
>  Hi Karsten,
>  (Or is it actually KArsten with two capitals? Please excuse my
>  confusion there. I'd very much like to address you properly. Thanks.)
>
>  I don't really have a clue exactly what this problem is but I took a
>  look around on web using Google. A few things came up:
>
>  1) Did you remember to build ext3 support into the kernel? Note how
>  mine below says it's mounting ext3.
>
>  2) It seems that someone might have had an issue like this caused by
>  ACPI. You could try acpi=off on your boot command line edited in by
>  hand or added in grub.
>
>  When my AMD64 machine boots I see this:
>
>  <SNIP>
>  ACPI wakeup devices:
>  HUB0 XVR0 XVR1 XVR2 XVR3 USB0 USB2 MMAC MMCI UAR1
>  ACPI: (supports S0 S1 S3 S4 S5)
>  Time: tsc clocksource has been installed.
>  kjournald starting.  Commit interval 5 seconds
>  EXT3-fs: mounted filesystem with ordered data mode.
>  VFS: Mounted root (ext3 filesystem) readonly.
> *****************************************************************************
>  *
>                  *
>  *  REMINDER, the following debugging options are turned on in your .config:
> *
>  *
>                  *
>  *        CONFIG_DEBUG_RT_MUTEXES
>                   *
>  *        CONFIG_DEBUG_PREEMPT
>                  *
>  *
>                  *
>  *  they may increase runtime overhead and latencies.
>     *
>  *
>                  *
> *****************************************************************************
>  Freeing unused kernel memory: 188k freed
>  input: AT Translated Set 2 keyboard as /class/input/input0
>  input: ImExPS/2 Generic Explorer Mouse as /class/input/input1
>  Adding 2008084k swap on /dev/sda10.  Priority:-1 extents:1 across:2008084k
>  EXT3 FS on sda2, internal journal
>  [drm] Initialized drm 1.0.1 20051102
>  <SNIP>
>
>    Since there is ACPI stuff immediately before and after it seems
>  worth looking at.
>
>    I suppose you don't have a second Linux box to do the null modem
>  cable trick where you can capture the boot stuff on a different
>  machine? Helpful during times like these.
>
>    Write back with more info and we can keep trying. At least that's
>  two ideas for now.
>
>  Cheers,
>  Mark