Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Gentoo: User

gentoo-sources-2.6.35-r12 causes kernel panic

 

 

Gentoo user RSS feed   Index | Next | Previous | View Threaded


michaelkintzios at gmail

Nov 27, 2010, 6:59 AM

Post #1 of 19 (4780 views)
Permalink
gentoo-sources-2.6.35-r12 causes kernel panic

I haven't had much luck with the 2.6.35 version of kernels - they have
cause panics on two different x86 boxen.

Now that 2.6.35 has gone stable so I tried it again and I'm getting a
kernel panic complaining about VFS unable to mount root fs:
==================================
VFS: Cannot open root device "sda3" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
Pid: 1, comm: swapper Not tainted 2.6.35-gentoo-r12 #2
Call Trace:
[<c14b3530>] ? panic+0x5f/0xc6
[<c1693c68>] ? mount_block_root+0x1c2/0x245
[<c1002930>] ? do_signal+0x766/0x7f2
[<c1693d31>] ? mount_root+0x46/0x5a
[<c1693e8b>] ? prepare_namespace+0x146/0x182
[<c1093203>] ? sys_access+0x1f/0x23
[<c16933f1>] ? kernel_init+0x1a9/0x1b7
[<c1693248>] ? kernel_init+0x0/0x1b7
[<c10030b6>] ? kernel_thread_helper+0x6/0x10
panic occurred, switching back to text console
==================================

This is my chipset:
=======================
*-pci
description: Host bridge
product: 82915G/P/GV/GL/PL/910GL Memory Controller Hub
vendor: Intel Corporation
physical id: 100
bus info: pci [at] 000:00:00.0
version: 04
width: 32 bits
clock: 33MHz
*-pci:0
description: PCI bridge
product: 82915G/P/GV/GL/PL/910GL PCI Express Root Port
vendor: Intel Corporation
physical id: 1
bus info: pci [at] 000:00:01.0
version: 04
width: 32 bits
clock: 33MHz
capabilities: pci pm msi pciexpress normal_decode
bus_master cap_list
configuration: driver=pcieport
resources: irq:40 ioport:b000(size=4096)
memory:cfe00000-cfefffff memory:d0000000-dfffffff
[snip ...]
*-pci:1
description: PCI bridge
product: 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1
vendor: Intel Corporation
physical id: 1c
bus info: pci [at] 000:00:1c.0
version: 03
width: 32 bits
clock: 33MHz
capabilities: pci pciexpress msi pm normal_decode
bus_master cap_list
configuration: driver=pcieport
resources: irq:41 ioport:c000(size=4096)
memory:c0000000-c01fffff ioport:c0200000(size=2097152)
[snip ...]
*-ide:1
description: IDE interface
product: 82801FB/FW (ICH6/ICH6W) SATA Controller
vendor: Intel Corporation
physical id: 1f.2
bus info: pci [at] 000:00:1f.2
logical name: scsi2
version: 03
width: 32 bits
clock: 66MHz
capabilities: ide pm bus_master cap_list emulated
configuration: driver=ata_piix latency=0
resources: irq:19 ioport:9400(size=8) ioport:9000(size=4)
ioport:8800(size=8) ioport:8400(size=4) ioport:8000(size=16)
*-disk
description: ATA Disk
product: WDC WD2500JD-22H
vendor: Western Digital
physical id: 0.0.0
bus info: scsi@2:0.0.0
logical name: /dev/sda
version: 08.0
serial: WD-WMAL71304147
size: 232GiB (250GB)
capabilities: partitioned partitioned:dos
configuration: ansiversion=5 signature=08640863
=======================

and these are the kernel options (which work fine with 2.6.34-r12):
=======================
# Bus options (PCI etc.)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
# CONFIG_PCI_GOOLPC is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCI_DOMAINS=y
# CONFIG_PCI_CNB20LE_QUIRK is not set
CONFIG_PCIEPORTBUS=y
CONFIG_PCIEAER=y
# CONFIG_PCIE_ECRC is not set
# CONFIG_PCIEAER_INJECT is not set
# CONFIG_PCIEASPM is not set
CONFIG_PCIE_PME=y
CONFIG_ARCH_SUPPORTS_MSI=y
# CONFIG_PCI_MSI is not set
# CONFIG_PCI_STUB is not set
CONFIG_HT_IRQ=y
# CONFIG_PCI_IOV is not set
CONFIG_PCI_IOAPIC=y
CONFIG_ISA_DMA_API=y
CONFIG_ISA=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
# CONFIG_OLPC is not set
CONFIG_K8_NB=y
# CONFIG_PCCARD is not set
# CONFIG_HOTPLUG_PCI is not set
[snip ...]

# Protocols
#
# CONFIG_ISAPNP is not set
# CONFIG_PNPBIOS is not set
CONFIG_PNPACPI=y
CONFIG_BLK_DEV=y
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_DEV_XD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_DRBD is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_UB is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=4096
# CONFIG_BLK_DEV_XIP is not set
CONFIG_CDROM_PKTCDVD=y
CONFIG_CDROM_PKTCDVD_BUFFERS=8
# CONFIG_CDROM_PKTCDVD_WCACHE is not set
# CONFIG_ATA_OVER_ETH is not set
# CONFIG_BLK_DEV_HD is not set
# CONFIG_MISC_DEVICES is not set
CONFIG_HAVE_IDE=y
# CONFIG_IDE is not set

#
# SCSI device support
#
CONFIG_SCSI_MOD=y
# CONFIG_RAID_ATTRS is not set
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
# CONFIG_SCSI_TGT is not set
# CONFIG_SCSI_NETLINK is not set
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=y
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=y
# CONFIG_BLK_DEV_SR_VENDOR is not set
CONFIG_CHR_DEV_SG=y
# CONFIG_CHR_DEV_SCH is not set
CONFIG_SCSI_MULTI_LUN=y
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
# CONFIG_SCSI_SCAN_ASYNC is not set
CONFIG_SCSI_WAIT_SCAN=m

# SCSI Transports
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set
# CONFIG_SCSI_SAS_ATTRS is not set
# CONFIG_SCSI_SAS_LIBSAS is not set
# CONFIG_SCSI_SRP_ATTRS is not set
# CONFIG_SCSI_LOWLEVEL is not set
CONFIG_SCSI_DH=y
# CONFIG_SCSI_DH_RDAC is not set
# CONFIG_SCSI_DH_HP_SW is not set
# CONFIG_SCSI_DH_EMC is not set
# CONFIG_SCSI_DH_ALUA is not set
# CONFIG_SCSI_OSD_INITIATOR is not set
CONFIG_ATA=y
# CONFIG_ATA_NONSTANDARD is not set
# CONFIG_ATA_VERBOSE_ERROR is not set
CONFIG_ATA_ACPI=y
# CONFIG_SATA_PMP is not set

#
# Controllers with non-SFF native interface
#
# CONFIG_SATA_AHCI is not set
# CONFIG_SATA_AHCI_PLATFORM is not set
# CONFIG_SATA_INIC162X is not set
# CONFIG_SATA_SIL24 is not set
# CONFIG_ATA_SFF is not set
# CONFIG_MD is not set
# CONFIG_FUSION is not set
=======================

Am I missing something obvious to make the 2.6.35 series work with my boxen?

Please ask if you need more info.
--
Regards,
Mick


markknecht at gmail

Nov 27, 2010, 7:17 AM

Post #2 of 19 (4607 views)
Permalink
Re: gentoo-sources-2.6.35-r12 causes kernel panic [In reply to]

On Sat, Nov 27, 2010 at 6:59 AM, Mick <michaelkintzios [at] gmail> wrote:
> I haven't had much luck with the 2.6.35 version of kernels - they have
> cause panics on two different x86 boxen.
>
> Now that 2.6.35 has gone stable so I tried it again and I'm getting a
> kernel panic complaining about VFS unable to mount root fs:
> ==================================
> VFS:  Cannot open root device "sda3" or unknown-block(0,0)
> Please append a correct "root=" boot option; here are the available partitions:
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
> Pid: 1, comm: swapper Not tainted 2.6.35-gentoo-r12 #2
> Call Trace:
>  [<c14b3530>] ? panic+0x5f/0xc6
>  [<c1693c68>] ? mount_block_root+0x1c2/0x245
>  [<c1002930>] ? do_signal+0x766/0x7f2
>  [<c1693d31>] ? mount_root+0x46/0x5a
>  [<c1693e8b>] ? prepare_namespace+0x146/0x182
>  [<c1093203>] ? sys_access+0x1f/0x23
>  [<c16933f1>] ? kernel_init+0x1a9/0x1b7
>  [<c1693248>] ? kernel_init+0x0/0x1b7
>  [<c10030b6>] ? kernel_thread_helper+0x6/0x10
> panic occurred, switching back to text console
> ==================================
<SNIP>
>
> Am I missing something obvious to make the 2.6.35 series work with my boxen?
>
> Please ask if you need more info.
> --
> Regards,
> Mick
>
>

Hi Mick,
OK, there's so many possibilities for what causes this. Basic
confusion ensues...

1) When booting, if you look carefully, is the initial kernel seeing
_any_ disks? Sometimes they fly bye and are hard to catch. If it is
then is it showing sda3?

2) What sort of file system did you put on sda3? I assume this is
built into the kernel if this is an upgrade?

3) Post the appropriate part of grub.conf to show how you are booting.

4) Post fstab

- Mark


michaelkintzios at gmail

Nov 27, 2010, 9:17 AM

Post #3 of 19 (4677 views)
Permalink
Re: gentoo-sources-2.6.35-r12 causes kernel panic [In reply to]

On Saturday 27 November 2010 15:17:43 Mark Knecht wrote:
> On Sat, Nov 27, 2010 at 6:59 AM, Mick <michaelkintzios [at] gmail> wrote:
> > I haven't had much luck with the 2.6.35 version of kernels - they have
> > cause panics on two different x86 boxen.
> >
> > Now that 2.6.35 has gone stable so I tried it again and I'm getting a
> > kernel panic complaining about VFS unable to mount root fs:
> > ==================================
> > VFS: Cannot open root device "sda3" or unknown-block(0,0)
> > Please append a correct "root=" boot option; here are the available
> > partitions: Kernel panic - not syncing: VFS: Unable to mount root fs on
> > unknown-block(0,0) Pid: 1, comm: swapper Not tainted 2.6.35-gentoo-r12
> > #2
> > Call Trace:
> > [<c14b3530>] ? panic+0x5f/0xc6
> > [<c1693c68>] ? mount_block_root+0x1c2/0x245
> > [<c1002930>] ? do_signal+0x766/0x7f2
> > [<c1693d31>] ? mount_root+0x46/0x5a
> > [<c1693e8b>] ? prepare_namespace+0x146/0x182
> > [<c1093203>] ? sys_access+0x1f/0x23
> > [<c16933f1>] ? kernel_init+0x1a9/0x1b7
> > [<c1693248>] ? kernel_init+0x0/0x1b7
> > [<c10030b6>] ? kernel_thread_helper+0x6/0x10
> > panic occurred, switching back to text console
> > ==================================
>
> <SNIP>
>
> > Am I missing something obvious to make the 2.6.35 series work with my
> > boxen?

> OK, there's so many possibilities for what causes this. Basic
> confusion ensues...
>
> 1) When booting, if you look carefully, is the initial kernel seeing
> _any_ disks? Sometimes they fly bye and are hard to catch. If it is
> then is it showing sda3?

The moment the monitor comes on it's already crashed - the first line under
the penguins shows:

Initializing USB Mass Storage driver...

so I assume that any probing of drives has already happened.

> 2) What sort of file system did you put on sda3? I assume this is
> built into the kernel if this is an upgrade?

reiserfs built into the kernel and unchanged for the last umpteen kernel
series.

> 3) Post the appropriate part of grub.conf to show how you are booting.

title=Gentoo Linux 2.6.35-r12
root (hd0,5)
kernel /kernel-2.6.35-gentoo-r12 root=/dev/sda3

The 2.6.34-r12 uses the same stanza except for *.35 being replaced with *.34

> 4) Post fstab

/dev/sda6 /boot ext2 noauto,noatime 1 1
/dev/sda3 / reiserfs noatime 0 1
/dev/sda2 none swap sw 0 0
[snip]

I'll now build the kernel on the second x86 box and see what happens there.
--
Regards,
Mick
Attachments: signature.asc (0.19 KB)


markknecht at gmail

Nov 27, 2010, 9:53 AM

Post #4 of 19 (4684 views)
Permalink
Re: gentoo-sources-2.6.35-r12 causes kernel panic [In reply to]

On Sat, Nov 27, 2010 at 9:17 AM, Mick <michaelkintzios [at] gmail> wrote:
> On Saturday 27 November 2010 15:17:43 Mark Knecht wrote:
>> On Sat, Nov 27, 2010 at 6:59 AM, Mick <michaelkintzios [at] gmail> wrote:
>> > I haven't had much luck with the 2.6.35 version of kernels - they have
>> > cause panics on two different x86 boxen.
>> >
>> > Now that 2.6.35 has gone stable so I tried it again and I'm getting a
>> > kernel panic complaining about VFS unable to mount root fs:
>> > ==================================
>> > VFS:  Cannot open root device "sda3" or unknown-block(0,0)
>> > Please append a correct "root=" boot option; here are the available
>> > partitions: Kernel panic - not syncing: VFS: Unable to mount root fs on
>> > unknown-block(0,0) Pid: 1, comm: swapper Not tainted 2.6.35-gentoo-r12
>> > #2
>> > Call Trace:
>> >  [<c14b3530>] ? panic+0x5f/0xc6
>> >  [<c1693c68>] ? mount_block_root+0x1c2/0x245
>> >  [<c1002930>] ? do_signal+0x766/0x7f2
>> >  [<c1693d31>] ? mount_root+0x46/0x5a
>> >  [<c1693e8b>] ? prepare_namespace+0x146/0x182
>> >  [<c1093203>] ? sys_access+0x1f/0x23
>> >  [<c16933f1>] ? kernel_init+0x1a9/0x1b7
>> >  [<c1693248>] ? kernel_init+0x0/0x1b7
>> >  [<c10030b6>] ? kernel_thread_helper+0x6/0x10
>> > panic occurred, switching back to text console
>> > ==================================
>>
>> <SNIP>
>>
>> > Am I missing something obvious to make the 2.6.35 series work with my
>> > boxen?
>
>>    OK, there's so many possibilities for what causes this. Basic
>> confusion ensues...
>>
>> 1) When booting, if you look carefully, is the initial kernel seeing
>> _any_ disks? Sometimes they fly bye and are hard to catch. If it is
>> then is it showing sda3?
>
> The moment the monitor comes on it's already crashed - the first line under
> the penguins shows:
>
> Initializing USB Mass Storage driver...
>
> so I assume that any probing of drives has already happened.
>
>> 2) What sort of file system did you put on sda3? I assume this is
>> built into the kernel if this is an upgrade?
>
> reiserfs built into the kernel and unchanged for the last umpteen kernel
> series.
>
>> 3) Post the appropriate part of grub.conf to show how you are booting.
>
> title=Gentoo Linux 2.6.35-r12
> root (hd0,5)
> kernel /kernel-2.6.35-gentoo-r12 root=/dev/sda3
>
> The 2.6.34-r12 uses the same stanza except for *.35 being replaced with *.34
>
>> 4) Post fstab
>
> /dev/sda6     /boot      ext2            noauto,noatime          1 1
> /dev/sda3     /          reiserfs        noatime                 0 1
> /dev/sda2     none       swap            sw                      0 0
> [snip]
>
> I'll now build the kernel on the second x86 box and see what happens there.
> --
> Regards,
> Mick
>

Yeah, all makes sense what you've done and I can only offer one more
thing for you to look at.

I skipped from 2.6.33 to 2.6.36 so I cannot say anything specific
about the *.35 series, but one thing I've suffered with on my 2.6.36
build is that if I have a specific USB hub hooked up my machine won't
complete a boot. I have to disconnect this USB hub prior to boot and
then hook it back up after the boot completes.

I've not had time to look for the cause so I only hook it up to use
it. After boot there are no other problems I've seen.

I was assuming that maybe there's some difference in the USB stuff
that I hadn't discovered yet, and since you see a crash at a USB step
possibly it's similar and I never saw it at *.35 because I never used
that series?

Good luck and I wish I could be of more help.

Cheers,
Mark


michaelkintzios at gmail

Nov 27, 2010, 10:29 AM

Post #5 of 19 (4590 views)
Permalink
Re: gentoo-sources-2.6.35-r12 causes kernel panic [In reply to]

On Saturday 27 November 2010 17:53:21 Mark Knecht wrote:
> On Sat, Nov 27, 2010 at 9:17 AM, Mick <michaelkintzios [at] gmail> wrote:
> > On Saturday 27 November 2010 15:17:43 Mark Knecht wrote:
> >> On Sat, Nov 27, 2010 at 6:59 AM, Mick <michaelkintzios [at] gmail> wrote:
> >> > I haven't had much luck with the 2.6.35 version of kernels - they have
> >> > cause panics on two different x86 boxen.
> >> >
> >> > Now that 2.6.35 has gone stable so I tried it again and I'm getting a
> >> > kernel panic complaining about VFS unable to mount root fs:
> >> > ==================================
> >> > VFS: Cannot open root device "sda3" or unknown-block(0,0)
> >> > Please append a correct "root=" boot option; here are the available
> >> > partitions: Kernel panic - not syncing: VFS: Unable to mount root fs
> >> > on unknown-block(0,0) Pid: 1, comm: swapper Not tainted
> >> > 2.6.35-gentoo-r12 #2
> >> > Call Trace:
> >> > [<c14b3530>] ? panic+0x5f/0xc6
> >> > [<c1693c68>] ? mount_block_root+0x1c2/0x245
> >> > [<c1002930>] ? do_signal+0x766/0x7f2
> >> > [<c1693d31>] ? mount_root+0x46/0x5a
> >> > [<c1693e8b>] ? prepare_namespace+0x146/0x182
> >> > [<c1093203>] ? sys_access+0x1f/0x23
> >> > [<c16933f1>] ? kernel_init+0x1a9/0x1b7
> >> > [<c1693248>] ? kernel_init+0x0/0x1b7
> >> > [<c10030b6>] ? kernel_thread_helper+0x6/0x10
> >> > panic occurred, switching back to text console
> >> > ==================================
> >>
> >> <SNIP>
> >>
> >> > Am I missing something obvious to make the 2.6.35 series work with my
> >> > boxen?
> >>
> >> OK, there's so many possibilities for what causes this. Basic
> >> confusion ensues...
> >>
> >> 1) When booting, if you look carefully, is the initial kernel seeing
> >> _any_ disks? Sometimes they fly bye and are hard to catch. If it is
> >> then is it showing sda3?
> >
> > The moment the monitor comes on it's already crashed - the first line
> > under the penguins shows:
> >
> > Initializing USB Mass Storage driver...
> >
> > so I assume that any probing of drives has already happened.
> >
> >> 2) What sort of file system did you put on sda3? I assume this is
> >> built into the kernel if this is an upgrade?
> >
> > reiserfs built into the kernel and unchanged for the last umpteen kernel
> > series.
> >
> >> 3) Post the appropriate part of grub.conf to show how you are booting.
> >
> > title=Gentoo Linux 2.6.35-r12
> > root (hd0,5)
> > kernel /kernel-2.6.35-gentoo-r12 root=/dev/sda3
> >
> > The 2.6.34-r12 uses the same stanza except for *.35 being replaced with
> > *.34
> >
> >> 4) Post fstab
> >
> > /dev/sda6 /boot ext2 noauto,noatime 1 1
> > /dev/sda3 / reiserfs noatime 0 1
> > /dev/sda2 none swap sw 0 0
> > [snip]
> >
> > I'll now build the kernel on the second x86 box and see what happens
> > there. --
> > Regards,
> > Mick
>
> Yeah, all makes sense what you've done and I can only offer one more
> thing for you to look at.
>
> I skipped from 2.6.33 to 2.6.36 so I cannot say anything specific
> about the *.35 series, but one thing I've suffered with on my 2.6.36
> build is that if I have a specific USB hub hooked up my machine won't
> complete a boot. I have to disconnect this USB hub prior to boot and
> then hook it back up after the boot completes.
>
> I've not had time to look for the cause so I only hook it up to use
> it. After boot there are no other problems I've seen.
>
> I was assuming that maybe there's some difference in the USB stuff
> that I hadn't discovered yet, and since you see a crash at a USB step
> possibly it's similar and I never saw it at *.35 because I never used
> that series?
>
> Good luck and I wish I could be of more help.

Thanks for trying to help me Mark, I'm surprised this problem is not more
widespread.

My second x86 machine also fails with the same kernel panic. :-(

Because this is a slower machine I had a moment to see the initial messages
before the penguin showed up.

It said:

ERROR: Unable to locate IOAPIC for GSI4

This is repeated a number of times and then the penguin pops up before the
kernel crashes a dozen lines further down. It seems that this is a regression
error, which I hope has been taken care of in later kernels:

http://kerneltrap.org/mailarchive/linux-kernel/2010/7/8/4591800
--
Regards,
Mick
Attachments: signature.asc (0.19 KB)


markknecht at gmail

Nov 27, 2010, 10:50 AM

Post #6 of 19 (4591 views)
Permalink
Re: gentoo-sources-2.6.35-r12 causes kernel panic [In reply to]

On Sat, Nov 27, 2010 at 10:29 AM, Mick <michaelkintzios [at] gmail> wrote:
> On Saturday 27 November 2010 17:53:21 Mark Knecht wrote:
>> On Sat, Nov 27, 2010 at 9:17 AM, Mick <michaelkintzios [at] gmail> wrote:
>> > On Saturday 27 November 2010 15:17:43 Mark Knecht wrote:
>> >> On Sat, Nov 27, 2010 at 6:59 AM, Mick <michaelkintzios [at] gmail> wrote:
>> >> > I haven't had much luck with the 2.6.35 version of kernels - they have
>> >> > cause panics on two different x86 boxen.
>> >> >
>> >> > Now that 2.6.35 has gone stable so I tried it again and I'm getting a
>> >> > kernel panic complaining about VFS unable to mount root fs:
>> >> > ==================================
>> >> > VFS:  Cannot open root device "sda3" or unknown-block(0,0)
>> >> > Please append a correct "root=" boot option; here are the available
>> >> > partitions: Kernel panic - not syncing: VFS: Unable to mount root fs
>> >> > on unknown-block(0,0) Pid: 1, comm: swapper Not tainted
>> >> > 2.6.35-gentoo-r12 #2
>> >> > Call Trace:
>> >> >  [<c14b3530>] ? panic+0x5f/0xc6
>> >> >  [<c1693c68>] ? mount_block_root+0x1c2/0x245
>> >> >  [<c1002930>] ? do_signal+0x766/0x7f2
>> >> >  [<c1693d31>] ? mount_root+0x46/0x5a
>> >> >  [<c1693e8b>] ? prepare_namespace+0x146/0x182
>> >> >  [<c1093203>] ? sys_access+0x1f/0x23
>> >> >  [<c16933f1>] ? kernel_init+0x1a9/0x1b7
>> >> >  [<c1693248>] ? kernel_init+0x0/0x1b7
>> >> >  [<c10030b6>] ? kernel_thread_helper+0x6/0x10
>> >> > panic occurred, switching back to text console
>> >> > ==================================
>> >>
>> >> <SNIP>
>> >>
>> >> > Am I missing something obvious to make the 2.6.35 series work with my
>> >> > boxen?
>> >>
>> >>    OK, there's so many possibilities for what causes this. Basic
>> >> confusion ensues...
>> >>
>> >> 1) When booting, if you look carefully, is the initial kernel seeing
>> >> _any_ disks? Sometimes they fly bye and are hard to catch. If it is
>> >> then is it showing sda3?
>> >
>> > The moment the monitor comes on it's already crashed - the first line
>> > under the penguins shows:
>> >
>> > Initializing USB Mass Storage driver...
>> >
>> > so I assume that any probing of drives has already happened.
>> >
>> >> 2) What sort of file system did you put on sda3? I assume this is
>> >> built into the kernel if this is an upgrade?
>> >
>> > reiserfs built into the kernel and unchanged for the last umpteen kernel
>> > series.
>> >
>> >> 3) Post the appropriate part of grub.conf to show how you are booting.
>> >
>> > title=Gentoo Linux 2.6.35-r12
>> > root (hd0,5)
>> > kernel /kernel-2.6.35-gentoo-r12 root=/dev/sda3
>> >
>> > The 2.6.34-r12 uses the same stanza except for *.35 being replaced with
>> > *.34
>> >
>> >> 4) Post fstab
>> >
>> > /dev/sda6     /boot      ext2            noauto,noatime          1 1
>> > /dev/sda3     /          reiserfs        noatime                 0 1
>> > /dev/sda2     none       swap            sw                      0 0
>> > [snip]
>> >
>> > I'll now build the kernel on the second x86 box and see what happens
>> > there. --
>> > Regards,
>> > Mick
>>
>> Yeah, all makes sense what you've done and I can only offer one more
>> thing for you to look at.
>>
>> I skipped from 2.6.33 to 2.6.36 so I cannot say anything specific
>> about the *.35 series, but one thing I've suffered with on my 2.6.36
>> build is that if I have a specific USB hub hooked up my machine won't
>> complete a boot. I have to disconnect this USB hub prior to boot and
>> then hook it back up after the boot completes.
>>
>> I've not had time to look for the cause so I only hook it up to use
>> it. After boot there are no other problems I've seen.
>>
>> I was assuming that maybe there's some difference in the USB stuff
>> that I hadn't discovered yet, and since you see a crash at a USB step
>> possibly it's similar and I never saw it at *.35 because I never used
>> that series?
>>
>> Good luck and I wish I could be of more help.
>
> Thanks for trying to help me Mark, I'm surprised this problem is not more
> widespread.
>
> My second x86 machine also fails with the same kernel panic.  :-(
>
> Because this is a slower machine I had a moment to see the initial messages
> before the penguin showed up.
>
> It said:
>
> ERROR:  Unable to locate IOAPIC for GSI4
>
> This is repeated a number of times and then the penguin pops up before the
> kernel crashes a dozen lines further down.  It seems that this is a regression
> error, which I hope has been taken care of in later kernels:
>
> http://kerneltrap.org/mailarchive/linux-kernel/2010/7/8/4591800
> --
> Regards,
> Mick
>

If you can then give 2.6.36 a try. Possibly it's in by now? That
thread ends without (by my reading anyway) any particular conclusion
about a fix.

- Mark


petri.rosenstrom at gmail

Nov 28, 2010, 10:42 PM

Post #7 of 19 (4564 views)
Permalink
Re: gentoo-sources-2.6.35-r12 causes kernel panic [In reply to]

On Sat, Nov 27, 2010 at 8:50 PM, Mark Knecht <markknecht [at] gmail> wrote:
> On Sat, Nov 27, 2010 at 10:29 AM, Mick <michaelkintzios [at] gmail> wrote:
>> On Saturday 27 November 2010 17:53:21 Mark Knecht wrote:
>>> On Sat, Nov 27, 2010 at 9:17 AM, Mick <michaelkintzios [at] gmail> wrote:
>>> > On Saturday 27 November 2010 15:17:43 Mark Knecht wrote:
>>> >> On Sat, Nov 27, 2010 at 6:59 AM, Mick <michaelkintzios [at] gmail> wrote:
>>> >> > I haven't had much luck with the 2.6.35 version of kernels - they have
>>> >> > cause panics on two different x86 boxen.
>>> >> >
>>> >> > Now that 2.6.35 has gone stable so I tried it again and I'm getting a
>>> >> > kernel panic complaining about VFS unable to mount root fs:
>>> >> > ==================================
>>> >> > VFS:  Cannot open root device "sda3" or unknown-block(0,0)
>>> >> > Please append a correct "root=" boot option; here are the available
>>> >> > partitions: Kernel panic - not syncing: VFS: Unable to mount root fs
>>> >> > on unknown-block(0,0) Pid: 1, comm: swapper Not tainted
>>> >> > 2.6.35-gentoo-r12 #2
>>> >> > Call Trace:
>>> >> >  [<c14b3530>] ? panic+0x5f/0xc6
>>> >> >  [<c1693c68>] ? mount_block_root+0x1c2/0x245
>>> >> >  [<c1002930>] ? do_signal+0x766/0x7f2
>>> >> >  [<c1693d31>] ? mount_root+0x46/0x5a
>>> >> >  [<c1693e8b>] ? prepare_namespace+0x146/0x182
>>> >> >  [<c1093203>] ? sys_access+0x1f/0x23
>>> >> >  [<c16933f1>] ? kernel_init+0x1a9/0x1b7
>>> >> >  [<c1693248>] ? kernel_init+0x0/0x1b7
>>> >> >  [<c10030b6>] ? kernel_thread_helper+0x6/0x10
>>> >> > panic occurred, switching back to text console
>>> >> > ==================================
>>> >>
>>> >> <SNIP>
>>> >>
>>> >> > Am I missing something obvious to make the 2.6.35 series work with my
>>> >> > boxen?
>>> >>
>>> >>    OK, there's so many possibilities for what causes this. Basic
>>> >> confusion ensues...
>>> >>
>>> >> 1) When booting, if you look carefully, is the initial kernel seeing
>>> >> _any_ disks? Sometimes they fly bye and are hard to catch. If it is
>>> >> then is it showing sda3?
>>> >
>>> > The moment the monitor comes on it's already crashed - the first line
>>> > under the penguins shows:
>>> >
>>> > Initializing USB Mass Storage driver...
>>> >
>>> > so I assume that any probing of drives has already happened.
>>> >
>>> >> 2) What sort of file system did you put on sda3? I assume this is
>>> >> built into the kernel if this is an upgrade?
>>> >
>>> > reiserfs built into the kernel and unchanged for the last umpteen kernel
>>> > series.
>>> >
>>> >> 3) Post the appropriate part of grub.conf to show how you are booting.
>>> >
>>> > title=Gentoo Linux 2.6.35-r12
>>> > root (hd0,5)
>>> > kernel /kernel-2.6.35-gentoo-r12 root=/dev/sda3
>>> >
>>> > The 2.6.34-r12 uses the same stanza except for *.35 being replaced with
>>> > *.34
>>> >
>>> >> 4) Post fstab
>>> >
>>> > /dev/sda6     /boot      ext2            noauto,noatime          1 1
>>> > /dev/sda3     /          reiserfs        noatime                 0 1
>>> > /dev/sda2     none       swap            sw                      0 0
>>> > [snip]
>>> >
>>> > I'll now build the kernel on the second x86 box and see what happens
>>> > there. --
>>> > Regards,
>>> > Mick
>>>
>>> Yeah, all makes sense what you've done and I can only offer one more
>>> thing for you to look at.
>>>
>>> I skipped from 2.6.33 to 2.6.36 so I cannot say anything specific
>>> about the *.35 series, but one thing I've suffered with on my 2.6.36
>>> build is that if I have a specific USB hub hooked up my machine won't
>>> complete a boot. I have to disconnect this USB hub prior to boot and
>>> then hook it back up after the boot completes.
>>>
>>> I've not had time to look for the cause so I only hook it up to use
>>> it. After boot there are no other problems I've seen.
>>>
>>> I was assuming that maybe there's some difference in the USB stuff
>>> that I hadn't discovered yet, and since you see a crash at a USB step
>>> possibly it's similar and I never saw it at *.35 because I never used
>>> that series?
>>>
>>> Good luck and I wish I could be of more help.
>>
>> Thanks for trying to help me Mark, I'm surprised this problem is not more
>> widespread.
>>
>> My second x86 machine also fails with the same kernel panic.  :-(
>>
>> Because this is a slower machine I had a moment to see the initial messages
>> before the penguin showed up.
>>
>> It said:
>>
>> ERROR:  Unable to locate IOAPIC for GSI4
>>
>> This is repeated a number of times and then the penguin pops up before the
>> kernel crashes a dozen lines further down.  It seems that this is a regression
>> error, which I hope has been taken care of in later kernels:
>>
>> http://kerneltrap.org/mailarchive/linux-kernel/2010/7/8/4591800
>> --
>> Regards,
>> Mick
>>
>
> If you can then give 2.6.36 a try. Possibly it's in by now? That
> thread ends without (by my reading anyway) any particular conclusion
> about a fix.
>
> - Mark
>
>

Hi Mick,

You didn't show CONFIG_ATA_PIIX in your kernel config... Or atleast I
didn't find it.

CONFIG_ATA_PIIX=y
Device Drivers --->Serial ATA and Parallel ATA drivers --->Intel
ESB, ICH, PIIX3, PIIX4 PATA/SATA support

Best regards
Petri


michaelkintzios at gmail

Nov 29, 2010, 12:30 AM

Post #8 of 19 (4561 views)
Permalink
Re: gentoo-sources-2.6.35-r12 causes kernel panic [In reply to]

On Monday 29 November 2010 06:42:26 Petri Rosenstrm wrote:
> On Sat, Nov 27, 2010 at 8:50 PM, Mark Knecht <markknecht [at] gmail> wrote:
> > On Sat, Nov 27, 2010 at 10:29 AM, Mick <michaelkintzios [at] gmail> wrote:
> >> On Saturday 27 November 2010 17:53:21 Mark Knecht wrote:
> >>> On Sat, Nov 27, 2010 at 9:17 AM, Mick <michaelkintzios [at] gmail> wrote:
> >>> > On Saturday 27 November 2010 15:17:43 Mark Knecht wrote:
> >>> >> On Sat, Nov 27, 2010 at 6:59 AM, Mick <michaelkintzios [at] gmail>
wrote:
> >>> >> > I haven't had much luck with the 2.6.35 version of kernels - they
> >>> >> > have cause panics on two different x86 boxen.
> >>> >> >
> >>> >> > Now that 2.6.35 has gone stable so I tried it again and I'm
> >>> >> > getting a kernel panic complaining about VFS unable to mount root
> >>> >> > fs: ==================================
> >>> >> > VFS: Cannot open root device "sda3" or unknown-block(0,0)
> >>> >> > Please append a correct "root=" boot option; here are the
> >>> >> > available partitions: Kernel panic - not syncing: VFS: Unable to
> >>> >> > mount root fs on unknown-block(0,0) Pid: 1, comm: swapper Not
> >>> >> > tainted
> >>> >> > 2.6.35-gentoo-r12 #2
> >>> >> > Call Trace:
> >>> >> > [<c14b3530>] ? panic+0x5f/0xc6
> >>> >> > [<c1693c68>] ? mount_block_root+0x1c2/0x245
> >>> >> > [<c1002930>] ? do_signal+0x766/0x7f2
> >>> >> > [<c1693d31>] ? mount_root+0x46/0x5a
> >>> >> > [<c1693e8b>] ? prepare_namespace+0x146/0x182
> >>> >> > [<c1093203>] ? sys_access+0x1f/0x23
> >>> >> > [<c16933f1>] ? kernel_init+0x1a9/0x1b7
> >>> >> > [<c1693248>] ? kernel_init+0x0/0x1b7
> >>> >> > [<c10030b6>] ? kernel_thread_helper+0x6/0x10
> >>> >> > panic occurred, switching back to text console
> >>> >> > ==================================
> >>> >>
> >>> >> <SNIP>
> >>> >>
> >>> >> > Am I missing something obvious to make the 2.6.35 series work with
> >>> >> > my boxen?
> >>> >>
> >>> >> OK, there's so many possibilities for what causes this. Basic
> >>> >> confusion ensues...
> >>> >>
> >>> >> 1) When booting, if you look carefully, is the initial kernel seeing
> >>> >> _any_ disks? Sometimes they fly bye and are hard to catch. If it is
> >>> >> then is it showing sda3?
> >>> >
> >>> > The moment the monitor comes on it's already crashed - the first line
> >>> > under the penguins shows:
> >>> >
> >>> > Initializing USB Mass Storage driver...
> >>> >
> >>> > so I assume that any probing of drives has already happened.
> >>> >
> >>> >> 2) What sort of file system did you put on sda3? I assume this is
> >>> >> built into the kernel if this is an upgrade?
> >>> >
> >>> > reiserfs built into the kernel and unchanged for the last umpteen
> >>> > kernel series.
> >>> >
> >>> >> 3) Post the appropriate part of grub.conf to show how you are
> >>> >> booting.
> >>> >
> >>> > title=Gentoo Linux 2.6.35-r12
> >>> > root (hd0,5)
> >>> > kernel /kernel-2.6.35-gentoo-r12 root=/dev/sda3
> >>> >
> >>> > The 2.6.34-r12 uses the same stanza except for *.35 being replaced
> >>> > with *.34
> >>> >
> >>> >> 4) Post fstab
> >>> >
> >>> > /dev/sda6 /boot ext2 noauto,noatime 1 1
> >>> > /dev/sda3 / reiserfs noatime 0 1
> >>> > /dev/sda2 none swap sw 0 0
> >>> > [snip]
> >>> >
> >>> > I'll now build the kernel on the second x86 box and see what happens
> >>> > there. --
> >>> > Regards,
> >>> > Mick
> >>>
> >>> Yeah, all makes sense what you've done and I can only offer one more
> >>> thing for you to look at.
> >>>
> >>> I skipped from 2.6.33 to 2.6.36 so I cannot say anything specific
> >>> about the *.35 series, but one thing I've suffered with on my 2.6.36
> >>> build is that if I have a specific USB hub hooked up my machine won't
> >>> complete a boot. I have to disconnect this USB hub prior to boot and
> >>> then hook it back up after the boot completes.
> >>>
> >>> I've not had time to look for the cause so I only hook it up to use
> >>> it. After boot there are no other problems I've seen.
> >>>
> >>> I was assuming that maybe there's some difference in the USB stuff
> >>> that I hadn't discovered yet, and since you see a crash at a USB step
> >>> possibly it's similar and I never saw it at *.35 because I never used
> >>> that series?
> >>>
> >>> Good luck and I wish I could be of more help.
> >>
> >> Thanks for trying to help me Mark, I'm surprised this problem is not
> >> more widespread.
> >>
> >> My second x86 machine also fails with the same kernel panic. :-(
> >>
> >> Because this is a slower machine I had a moment to see the initial
> >> messages before the penguin showed up.
> >>
> >> It said:
> >>
> >> ERROR: Unable to locate IOAPIC for GSI4
> >>
> >> This is repeated a number of times and then the penguin pops up before
> >> the kernel crashes a dozen lines further down. It seems that this is a
> >> regression error, which I hope has been taken care of in later kernels:
> >>
> >> http://kerneltrap.org/mailarchive/linux-kernel/2010/7/8/4591800
> >> --
> >> Regards,
> >> Mick
> >
> > If you can then give 2.6.36 a try. Possibly it's in by now? That
> > thread ends without (by my reading anyway) any particular conclusion
> > about a fix.
> >
> > - Mark
>
> Hi Mick,
>
> You didn't show CONFIG_ATA_PIIX in your kernel config... Or atleast I
> didn't find it.
>
> CONFIG_ATA_PIIX=y
> Device Drivers --->Serial ATA and Parallel ATA drivers --->Intel
> ESB, ICH, PIIX3, PIIX4 PATA/SATA support

That's because it's not longer there:

$ cat /usr/src/linux/.config | grep -i CONFIG_ATA
# CONFIG_ATALK is not set
# CONFIG_ATA_OVER_ETH is not set
CONFIG_ATA=y
# CONFIG_ATA_NONSTANDARD is not set
# CONFIG_ATA_VERBOSE_ERROR is not set
CONFIG_ATA_ACPI=y
# CONFIG_ATA_SFF is not set
# CONFIG_ATARI_PARTITION is not set
--
Regards,
Mick
Attachments: signature.asc (0.19 KB)


petri.rosenstrom at gmail

Nov 29, 2010, 12:43 AM

Post #9 of 19 (4600 views)
Permalink
Re: gentoo-sources-2.6.35-r12 causes kernel panic [In reply to]

On Mon, Nov 29, 2010 at 10:30 AM, Mick <michaelkintzios [at] gmail> wrote:
> On Monday 29 November 2010 06:42:26 Petri Rosenström wrote:
>> On Sat, Nov 27, 2010 at 8:50 PM, Mark Knecht <markknecht [at] gmail> wrote:
>> > On Sat, Nov 27, 2010 at 10:29 AM, Mick <michaelkintzios [at] gmail> wrote:
>> >> On Saturday 27 November 2010 17:53:21 Mark Knecht wrote:
>> >>> On Sat, Nov 27, 2010 at 9:17 AM, Mick <michaelkintzios [at] gmail> wrote:
>> >>> > On Saturday 27 November 2010 15:17:43 Mark Knecht wrote:
>> >>> >> On Sat, Nov 27, 2010 at 6:59 AM, Mick <michaelkintzios [at] gmail>
> wrote:
>> >>> >> > I haven't had much luck with the 2.6.35 version of kernels - they
>> >>> >> > have cause panics on two different x86 boxen.
>> >>> >> >
>> >>> >> > Now that 2.6.35 has gone stable so I tried it again and I'm
>> >>> >> > getting a kernel panic complaining about VFS unable to mount root
>> >>> >> > fs: ==================================
>> >>> >> > VFS:  Cannot open root device "sda3" or unknown-block(0,0)
>> >>> >> > Please append a correct "root=" boot option; here are the
>> >>> >> > available partitions: Kernel panic - not syncing: VFS: Unable to
>> >>> >> > mount root fs on unknown-block(0,0) Pid: 1, comm: swapper Not
>> >>> >> > tainted
>> >>> >> > 2.6.35-gentoo-r12 #2
>> >>> >> > Call Trace:
>> >>> >> >  [<c14b3530>] ? panic+0x5f/0xc6
>> >>> >> >  [<c1693c68>] ? mount_block_root+0x1c2/0x245
>> >>> >> >  [<c1002930>] ? do_signal+0x766/0x7f2
>> >>> >> >  [<c1693d31>] ? mount_root+0x46/0x5a
>> >>> >> >  [<c1693e8b>] ? prepare_namespace+0x146/0x182
>> >>> >> >  [<c1093203>] ? sys_access+0x1f/0x23
>> >>> >> >  [<c16933f1>] ? kernel_init+0x1a9/0x1b7
>> >>> >> >  [<c1693248>] ? kernel_init+0x0/0x1b7
>> >>> >> >  [<c10030b6>] ? kernel_thread_helper+0x6/0x10
>> >>> >> > panic occurred, switching back to text console
>> >>> >> > ==================================
>> >>> >>
>> >>> >> <SNIP>
>> >>> >>
>> >>> >> > Am I missing something obvious to make the 2.6.35 series work with
>> >>> >> > my boxen?
>> >>> >>
>> >>> >>    OK, there's so many possibilities for what causes this. Basic
>> >>> >> confusion ensues...
>> >>> >>
>> >>> >> 1) When booting, if you look carefully, is the initial kernel seeing
>> >>> >> _any_ disks? Sometimes they fly bye and are hard to catch. If it is
>> >>> >> then is it showing sda3?
>> >>> >
>> >>> > The moment the monitor comes on it's already crashed - the first line
>> >>> > under the penguins shows:
>> >>> >
>> >>> > Initializing USB Mass Storage driver...
>> >>> >
>> >>> > so I assume that any probing of drives has already happened.
>> >>> >
>> >>> >> 2) What sort of file system did you put on sda3? I assume this is
>> >>> >> built into the kernel if this is an upgrade?
>> >>> >
>> >>> > reiserfs built into the kernel and unchanged for the last umpteen
>> >>> > kernel series.
>> >>> >
>> >>> >> 3) Post the appropriate part of grub.conf to show how you are
>> >>> >> booting.
>> >>> >
>> >>> > title=Gentoo Linux 2.6.35-r12
>> >>> > root (hd0,5)
>> >>> > kernel /kernel-2.6.35-gentoo-r12 root=/dev/sda3
>> >>> >
>> >>> > The 2.6.34-r12 uses the same stanza except for *.35 being replaced
>> >>> > with *.34
>> >>> >
>> >>> >> 4) Post fstab
>> >>> >
>> >>> > /dev/sda6     /boot      ext2            noauto,noatime          1 1
>> >>> > /dev/sda3     /          reiserfs        noatime                 0 1
>> >>> > /dev/sda2     none       swap            sw                      0 0
>> >>> > [snip]
>> >>> >
>> >>> > I'll now build the kernel on the second x86 box and see what happens
>> >>> > there. --
>> >>> > Regards,
>> >>> > Mick
>> >>>
>> >>> Yeah, all makes sense what you've done and I can only offer one more
>> >>> thing for you to look at.
>> >>>
>> >>> I skipped from 2.6.33 to 2.6.36 so I cannot say anything specific
>> >>> about the *.35 series, but one thing I've suffered with on my 2.6.36
>> >>> build is that if I have a specific USB hub hooked up my machine won't
>> >>> complete a boot. I have to disconnect this USB hub prior to boot and
>> >>> then hook it back up after the boot completes.
>> >>>
>> >>> I've not had time to look for the cause so I only hook it up to use
>> >>> it. After boot there are no other problems I've seen.
>> >>>
>> >>> I was assuming that maybe there's some difference in the USB stuff
>> >>> that I hadn't discovered yet, and since you see a crash at a USB step
>> >>> possibly it's similar and I never saw it at *.35 because I never used
>> >>> that series?
>> >>>
>> >>> Good luck and I wish I could be of more help.
>> >>
>> >> Thanks for trying to help me Mark, I'm surprised this problem is not
>> >> more widespread.
>> >>
>> >> My second x86 machine also fails with the same kernel panic.  :-(
>> >>
>> >> Because this is a slower machine I had a moment to see the initial
>> >> messages before the penguin showed up.
>> >>
>> >> It said:
>> >>
>> >> ERROR:  Unable to locate IOAPIC for GSI4
>> >>
>> >> This is repeated a number of times and then the penguin pops up before
>> >> the kernel crashes a dozen lines further down.  It seems that this is a
>> >> regression error, which I hope has been taken care of in later kernels:
>> >>
>> >> http://kerneltrap.org/mailarchive/linux-kernel/2010/7/8/4591800
>> >> --
>> >> Regards,
>> >> Mick
>> >
>> > If you can then give 2.6.36 a try. Possibly it's in by now? That
>> > thread ends without (by my reading anyway) any particular conclusion
>> > about a fix.
>> >
>> > - Mark
>>
>> Hi Mick,
>>
>> You didn't show CONFIG_ATA_PIIX in your kernel config... Or atleast I
>> didn't find it.
>>
>> CONFIG_ATA_PIIX=y
>> Device Drivers  --->Serial ATA and Parallel ATA drivers  --->Intel
>> ESB, ICH, PIIX3, PIIX4 PATA/SATA support
>
> That's because it's not longer there:
>
> $ cat /usr/src/linux/.config | grep -i CONFIG_ATA
> # CONFIG_ATALK is not set
> # CONFIG_ATA_OVER_ETH is not set
> CONFIG_ATA=y
> # CONFIG_ATA_NONSTANDARD is not set
> # CONFIG_ATA_VERBOSE_ERROR is not set
> CONFIG_ATA_ACPI=y
> # CONFIG_ATA_SFF is not set
> # CONFIG_ATARI_PARTITION is not set
> --
> Regards,
> Mick
>

Try setting that from make menuconfig, and do the normal stuff and try
to boot. My best guess at this moment is that you need it and you are
missing it.

Best regards
Petri


neil at digimed

Nov 29, 2010, 1:01 AM

Post #10 of 19 (4604 views)
Permalink
Re: gentoo-sources-2.6.35-r12 causes kernel panic [In reply to]

On Mon, 29 Nov 2010 08:30:46 +0000, Mick wrote:

> $ cat /usr/src/linux/.config | grep -i CONFIG_ATA
> # CONFIG_ATALK is not set
> # CONFIG_ATA_OVER_ETH is not set
> CONFIG_ATA=y
> # CONFIG_ATA_NONSTANDARD is not set
> # CONFIG_ATA_VERBOSE_ERROR is not set
> CONFIG_ATA_ACPI=y
> # CONFIG_ATA_SFF is not set

This one may be the cause, I've needed to set it on several machines to
avoid just what you're seeing.


--
Neil Bothwick

Nothing is foolproof to a sufficiently talented fool.
Attachments: signature.asc (0.19 KB)


michaelkintzios at gmail

Nov 29, 2010, 2:30 AM

Post #11 of 19 (4567 views)
Permalink
Re: gentoo-sources-2.6.35-r12 causes kernel panic [In reply to]

On Monday 29 November 2010 09:01:37 Neil Bothwick wrote:
> On Mon, 29 Nov 2010 08:30:46 +0000, Mick wrote:
> > $ cat /usr/src/linux/.config | grep -i CONFIG_ATA
> > # CONFIG_ATALK is not set
> > # CONFIG_ATA_OVER_ETH is not set
> > CONFIG_ATA=y
> > # CONFIG_ATA_NONSTANDARD is not set
> > # CONFIG_ATA_VERBOSE_ERROR is not set
> > CONFIG_ATA_ACPI=y
> > # CONFIG_ATA_SFF is not set
>
> This one may be the cause, I've needed to set it on several machines to
> avoid just what you're seeing.

Aha!! I couldn't see it because I had not enabled "ATA BMDMA support" - it's
compiling now.

Thank you all for your help!
--
Regards,
Mick
Attachments: signature.asc (0.19 KB)


michaelkintzios at gmail

Nov 29, 2010, 4:52 AM

Post #12 of 19 (4594 views)
Permalink
Re: gentoo-sources-2.6.35-r12 causes kernel panic [In reply to]

On 29 November 2010 10:30, Mick <michaelkintzios [at] gmail> wrote:
> On Monday 29 November 2010 09:01:37 Neil Bothwick wrote:
>> On Mon, 29 Nov 2010 08:30:46 +0000, Mick wrote:
>> > $ cat /usr/src/linux/.config | grep -i CONFIG_ATA
>> > # CONFIG_ATALK is not set
>> > # CONFIG_ATA_OVER_ETH is not set
>> > CONFIG_ATA=y
>> > # CONFIG_ATA_NONSTANDARD is not set
>> > # CONFIG_ATA_VERBOSE_ERROR is not set
>> > CONFIG_ATA_ACPI=y
>> > # CONFIG_ATA_SFF is not set
>>
>> This one may be the cause, I've needed to set it on several machines to
>> avoid just what you're seeing.
>
> Aha!! I couldn't see it because I had not enabled "ATA BMDMA support" - it's
> compiling now.
>
> Thank you all for your help!

Ughh! Spoke too soon. :-(

The older PIII machine still crashes in the same manner. This is what
I have configured:

$ cat /usr/src/linux/.config | grep -i CONFIG_ATA
# CONFIG_ATALK is not set
# CONFIG_ATA_OVER_ETH is not set
CONFIG_ATA=y
# CONFIG_ATA_NONSTANDARD is not set
# CONFIG_ATA_VERBOSE_ERROR is not set
CONFIG_ATA_ACPI=y
CONFIG_ATA_SFF=y
CONFIG_ATA_BMDMA=y
CONFIG_ATA_PIIX=y
CONFIG_ATA_GENERIC=y

Also,

CONFIG_SATA_PMP=y

CONFIG_PATA_ISAPNP=y

CONFIG_PATA_ACPI=y
CONFIG_PATA_LEGACY=y

This is what this old machine contains:

# lspci
00:00.0 Host bridge: Intel Corporation 82830 830 Chipset Host Bridge (rev 04)
00:01.0 PCI bridge: Intel Corporation 82830 830 Chipset AGP Bridge (rev 04)
...
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 42)
00:1f.0 ISA bridge: Intel Corporation 82801CAM ISA Bridge (LPC) (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801CAM IDE U100 Controller (rev 02)

I should be able to get onto the P4 later on and see if the problem
persists there too.
--
Regards,
Mick


rdalek1967 at gmail

Nov 29, 2010, 5:41 AM

Post #13 of 19 (4554 views)
Permalink
Re: gentoo-sources-2.6.35-r12 causes kernel panic [In reply to]

Mick wrote:
>
> Ughh! Spoke too soon. :-(
>
> The older PIII machine still crashes in the same manner. This is what
> I have configured:
>
> $ cat /usr/src/linux/.config | grep -i CONFIG_ATA
> # CONFIG_ATALK is not set
> # CONFIG_ATA_OVER_ETH is not set
> CONFIG_ATA=y
> # CONFIG_ATA_NONSTANDARD is not set
> # CONFIG_ATA_VERBOSE_ERROR is not set
> CONFIG_ATA_ACPI=y
> CONFIG_ATA_SFF=y
> CONFIG_ATA_BMDMA=y
> CONFIG_ATA_PIIX=y
> CONFIG_ATA_GENERIC=y
>
> Also,
>
> CONFIG_SATA_PMP=y
>
> CONFIG_PATA_ISAPNP=y
>
> CONFIG_PATA_ACPI=y
> CONFIG_PATA_LEGACY=y
>
> This is what this old machine contains:
>
> # lspci
> 00:00.0 Host bridge: Intel Corporation 82830 830 Chipset Host Bridge (rev 04)
> 00:01.0 PCI bridge: Intel Corporation 82830 830 Chipset AGP Bridge (rev 04)
> ...
> 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 42)
> 00:1f.0 ISA bridge: Intel Corporation 82801CAM ISA Bridge (LPC) (rev 02)
> 00:1f.1 IDE interface: Intel Corporation 82801CAM IDE U100 Controller (rev 02)
>
> I should be able to get onto the P4 later on and see if the problem
> persists there too.
>

I'm not sure if this would help but it couldn't hurt to try.

http://kmuto.jp/debian/hcl/

Hope that helps.

Dale

:-) :-)


michaelkintzios at gmail

Nov 29, 2010, 6:51 AM

Post #14 of 19 (4552 views)
Permalink
Re: gentoo-sources-2.6.35-r12 causes kernel panic [In reply to]

On 29 November 2010 13:41, Dale <rdalek1967 [at] gmail> wrote:
> Mick wrote:
>>
>> Ughh! Spoke too soon. :-(
>>
>> The older PIII machine still crashes in the same manner. This is what
>> I have configured:
>>
>> $ cat /usr/src/linux/.config | grep -i CONFIG_ATA
>> # CONFIG_ATALK is not set
>> # CONFIG_ATA_OVER_ETH is not set
>> CONFIG_ATA=y
>> # CONFIG_ATA_NONSTANDARD is not set
>> # CONFIG_ATA_VERBOSE_ERROR is not set
>> CONFIG_ATA_ACPI=y
>> CONFIG_ATA_SFF=y
>> CONFIG_ATA_BMDMA=y
>> CONFIG_ATA_PIIX=y
>> CONFIG_ATA_GENERIC=y
>>
>> Also,
>>
>> CONFIG_SATA_PMP=y
>>
>> CONFIG_PATA_ISAPNP=y
>>
>> CONFIG_PATA_ACPI=y
>> CONFIG_PATA_LEGACY=y
>>
>> This is what this old machine contains:
>>
>> # lspci
>> 00:00.0 Host bridge: Intel Corporation 82830 830 Chipset Host Bridge (rev
>> 04)
>> 00:01.0 PCI bridge: Intel Corporation 82830 830 Chipset AGP Bridge (rev
>> 04)
>> ...
>> 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 42)
>> 00:1f.0 ISA bridge: Intel Corporation 82801CAM ISA Bridge (LPC) (rev 02)
>> 00:1f.1 IDE interface: Intel Corporation 82801CAM IDE U100 Controller (rev
>> 02)
>>
>> I should be able to get onto the P4 later on and see if the problem
>> persists there too.
>>
>
> I'm not sure if this would help but it couldn't hurt to try.
>
> http://kmuto.jp/debian/hcl/
>
> Hope that helps.

Thanks Dale, I think it is based on older kernels. It mentions:

ata_piix

which is the ONFIG_ATA_PIIX=y I have configured in the kernel. For a
minute I thought it's something simple I missed out on with the change
of the kernel version, but it seems it is more involved than that. I
just hope that the P4 machine works out right, because it is on daily
use.
--
Regards,
Mick


rdalek1967 at gmail

Nov 29, 2010, 7:17 AM

Post #15 of 19 (4556 views)
Permalink
Re: gentoo-sources-2.6.35-r12 causes kernel panic [In reply to]

Mick wrote:
> On 29 November 2010 13:41, Dale<rdalek1967 [at] gmail> wrote:
>
>> Mick wrote:
>>
>>> Ughh! Spoke too soon. :-(
>>>
>>> The older PIII machine still crashes in the same manner. This is what
>>> I have configured:
>>>
>>> $ cat /usr/src/linux/.config | grep -i CONFIG_ATA
>>> # CONFIG_ATALK is not set
>>> # CONFIG_ATA_OVER_ETH is not set
>>> CONFIG_ATA=y
>>> # CONFIG_ATA_NONSTANDARD is not set
>>> # CONFIG_ATA_VERBOSE_ERROR is not set
>>> CONFIG_ATA_ACPI=y
>>> CONFIG_ATA_SFF=y
>>> CONFIG_ATA_BMDMA=y
>>> CONFIG_ATA_PIIX=y
>>> CONFIG_ATA_GENERIC=y
>>>
>>> Also,
>>>
>>> CONFIG_SATA_PMP=y
>>>
>>> CONFIG_PATA_ISAPNP=y
>>>
>>> CONFIG_PATA_ACPI=y
>>> CONFIG_PATA_LEGACY=y
>>>
>>> This is what this old machine contains:
>>>
>>> # lspci
>>> 00:00.0 Host bridge: Intel Corporation 82830 830 Chipset Host Bridge (rev
>>> 04)
>>> 00:01.0 PCI bridge: Intel Corporation 82830 830 Chipset AGP Bridge (rev
>>> 04)
>>> ...
>>> 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 42)
>>> 00:1f.0 ISA bridge: Intel Corporation 82801CAM ISA Bridge (LPC) (rev 02)
>>> 00:1f.1 IDE interface: Intel Corporation 82801CAM IDE U100 Controller (rev
>>> 02)
>>>
>>> I should be able to get onto the P4 later on and see if the problem
>>> persists there too.
>>>
>>>
>> I'm not sure if this would help but it couldn't hurt to try.
>>
>> http://kmuto.jp/debian/hcl/
>>
>> Hope that helps.
>>
> Thanks Dale, I think it is based on older kernels. It mentions:
>
> ata_piix
>
> which is the ONFIG_ATA_PIIX=y I have configured in the kernel. For a
> minute I thought it's something simple I missed out on with the change
> of the kernel version, but it seems it is more involved than that. I
> just hope that the P4 machine works out right, because it is on daily
> use.
>

It tells in the top right corner what kernels it is based on. It
mentions 2.6.36.1, 2.6.37-rc3-git5 in the little box. Also, I just
noticed that it lists the mobo and branded PCs on the left. Maybe that
will help some. I just found mine that I been asking about on this
list. I never noticed that before today. o_O I guess I was looking in
the wrong place the past few days. Now to remember that it is there. ;-)

Dale

:-) :-)


michaelkintzios at gmail

Nov 29, 2010, 10:20 AM

Post #16 of 19 (4543 views)
Permalink
Re: gentoo-sources-2.6.35-r12 causes kernel panic [In reply to]

On Monday 29 November 2010 15:17:42 Dale wrote:
> Mick wrote:
> > On 29 November 2010 13:41, Dale<rdalek1967 [at] gmail> wrote:
> >> Mick wrote:
> >>> Ughh! Spoke too soon. :-(
> >>>
> >>> The older PIII machine still crashes in the same manner. This is what
> >>>
> >>> I have configured:
> >>> $ cat /usr/src/linux/.config | grep -i CONFIG_ATA
> >>>
> >>> # CONFIG_ATALK is not set
> >>> # CONFIG_ATA_OVER_ETH is not set
> >>> CONFIG_ATA=y
> >>> # CONFIG_ATA_NONSTANDARD is not set
> >>> # CONFIG_ATA_VERBOSE_ERROR is not set
> >>> CONFIG_ATA_ACPI=y
> >>> CONFIG_ATA_SFF=y
> >>> CONFIG_ATA_BMDMA=y
> >>> CONFIG_ATA_PIIX=y
> >>> CONFIG_ATA_GENERIC=y
> >>>
> >>> Also,
> >>>
> >>> CONFIG_SATA_PMP=y
> >>>
> >>> CONFIG_PATA_ISAPNP=y
> >>>
> >>> CONFIG_PATA_ACPI=y
> >>> CONFIG_PATA_LEGACY=y
> >>>
> >>> This is what this old machine contains:
> >>>
> >>> # lspci
> >>> 00:00.0 Host bridge: Intel Corporation 82830 830 Chipset Host Bridge
> >>> (rev 04)
> >>> 00:01.0 PCI bridge: Intel Corporation 82830 830 Chipset AGP Bridge (rev
> >>> 04)
> >>> ...
> >>> 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 42)
> >>> 00:1f.0 ISA bridge: Intel Corporation 82801CAM ISA Bridge (LPC) (rev
> >>> 02) 00:1f.1 IDE interface: Intel Corporation 82801CAM IDE U100
> >>> Controller (rev 02)
> >>>
> >>> I should be able to get onto the P4 later on and see if the problem
> >>> persists there too.
> >>
> >> I'm not sure if this would help but it couldn't hurt to try.
> >>
> >> http://kmuto.jp/debian/hcl/
> >>
> >> Hope that helps.
> >
> > Thanks Dale, I think it is based on older kernels. It mentions:
> >
> > ata_piix
> >
> > which is the ONFIG_ATA_PIIX=y I have configured in the kernel. For a
> > minute I thought it's something simple I missed out on with the change
> > of the kernel version, but it seems it is more involved than that. I
> > just hope that the P4 machine works out right, because it is on daily
> > use.
>
> It tells in the top right corner what kernels it is based on. It
> mentions 2.6.36.1, 2.6.37-rc3-git5 in the little box. Also, I just
> noticed that it lists the mobo and branded PCs on the left. Maybe that
> will help some. I just found mine that I been asking about on this
> list. I never noticed that before today. o_O I guess I was looking in
> the wrong place the past few days. Now to remember that it is there. ;-)

Yes, I had seen those but the drivers mentioned there for my PIII are
definitely from older kernels ...

The good news is that the P4 box fired up nicely (phew!).

Will wait for 2.6.36 series to see if this old PIII will work.
--
Regards,
Mick
Attachments: signature.asc (0.19 KB)


peter at humphrey

Nov 30, 2010, 3:11 AM

Post #17 of 19 (4526 views)
Permalink
Re: gentoo-sources-2.6.35-r12 causes kernel panic [In reply to]

On Monday 29 November 2010 18:20:56 Mick wrote:

> Will wait for 2.6.36 series to see if this old PIII will work.

I'm running 2.6.36-r3 at the moment. You only have to add a keyword to
gentoo-sources.

BtW, is it really necessary to quote the entire thread in every post?

--
Rgds
Peter. Linux Counter 5290, 1994-04-23.


michaelkintzios at gmail

Dec 18, 2010, 6:40 AM

Post #18 of 19 (4455 views)
Permalink
Re: gentoo-sources-2.6.35-r12 causes kernel panic [In reply to]

On 30 November 2010 11:11, Peter Humphrey <peter [at] humphrey> wrote:
> On Monday 29 November 2010 18:20:56 Mick wrote:
>
>> Will wait for 2.6.36 series to see if this old PIII will work.
>
> I'm running 2.6.36-r3 at the moment. You only have to add a keyword to
> gentoo-sources.

Just compiled gentoo-2.6.36-r5.

Unfortunately, I'm no closer to getting running kernel! :-(
=====================================
ERROR: Unable to locate IOAPIC for GSI4
ERROR: Unable to locate IOAPIC for GSI6

ERROR: Unable to locate IOAPIC for GSI4
ERROR: Unable to locate IOAPIC for GSI6
ERROR: Unable to locate IOAPIC for GSI3
ERROR: Unable to locate IOAPIC for GSI7
ERROR: Unable to locate IOAPIC for GSI13
ERROR: Unable to locate IOAPIC for GSI8
ERROR: Unable to locate IOAPIC for GSI1
ERROR: Unable to locate IOAPIC for GSI12

kernel oanic -not syncing: VFS: Unable to mount root fs on unknown block(0,0)
Pid: 1, comm: swapper Not taineted 2.6.36-gentoo-r5
Call trace:

<snip...> (some trace messages which contain):

panic
mount_block_root
kernel_init
prepare_namespace
sys_access
kernel_init
kernel_thread_helper
=====================================

Any ideas?
--
Regards,
Mick


michaelkintzios at gmail

Dec 28, 2010, 6:36 AM

Post #19 of 19 (4485 views)
Permalink
Re: gentoo-sources-2.6.35-r12 causes kernel panic [In reply to]

On Saturday 18 December 2010 14:40:07 Mick wrote:
> On 30 November 2010 11:11, Peter Humphrey <peter [at] humphrey> wrote:
> > On Monday 29 November 2010 18:20:56 Mick wrote:
> >> Will wait for 2.6.36 series to see if this old PIII will work.
> >
> > I'm running 2.6.36-r3 at the moment. You only have to add a keyword to
> > gentoo-sources.
>
> Just compiled gentoo-2.6.36-r5.
>
> Unfortunately, I'm no closer to getting running kernel! :-(
> =====================================
> ERROR: Unable to locate IOAPIC for GSI 4
> ERROR: Unable to locate IOAPIC for GSI 6
>
> ERROR: Unable to locate IOAPIC for GSI 4
> ERROR: Unable to locate IOAPIC for GSI 6
> ERROR: Unable to locate IOAPIC for GSI 3
> ERROR: Unable to locate IOAPIC for GSI 7
> ERROR: Unable to locate IOAPIC for GSI 13
> ERROR: Unable to locate IOAPIC for GSI 8
> ERROR: Unable to locate IOAPIC for GSI 1
> ERROR: Unable to locate IOAPIC for GSI 12
>
> kernel oanic -not syncing: VFS: Unable to mount root fs on unknown
> block(0,0) Pid: 1, comm: swapper Not taineted 2.6.36-gentoo-r5
> Call trace:
>
> <snip...> (some trace messages which contain):
>
> panic
> mount_block_root
> kernel_init
> prepare_namespace
> sys_access
> kernel_init
> kernel_thread_helper
> =====================================
>
> Any ideas?

What a muppet! I had the old root path in GRUB /dev/hda3, instead of the new
/dev/sda3 that the new kernel drivers now read.

Still getting the errors about "Unable to locate IOAPIC for GSI 4", but they
seem to be harmless.

Sorry for the noise!
--
Regards,
Mick
Attachments: signature.asc (0.19 KB)

Gentoo user RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.