Re: Cannot boot 2.6.26 kernel on HPPA N4000
On Mon, Mar 16, 2009 at 11:25:51AM -0700, Marc Rodriguez wrote: > Package: linux-image > Version: 2.6.26-parisc64 > Severity: Critical > > > Attempting to boot a 2.6.26 kernel on an HP N4000 machine (64 bit PA-RISC) > yields the following results (beginning at system startup): > <> > > > > GSP Host Name: uninitialized > > GSP> co > > > CO > > You are now leaving the Guardian Service Processor Command Interface > and returning to the console mode. Type Ctrl B to reactivate it. > > > > Configuration Menu: Enter command > ma > Main > Menu --- > > Command Description > --- --- > BOot [PRI|ALT|] Boot from specified path > PAth [PRI|ALT] [] Display or modify a path > SEArch [DIsplay|IPL] [] Search for boot devices > > COnfiguration menuDisplays or sets boot values > INformation menu Displays hardware information > SERvice menu Displays service commands > > DIsplay Redisplay the current menu > HElp [|] Display help for menu or command > RESET Restart the system > > Main Menu: Enter command or menu > bo > > Interact with IPL (Y, N, or Cancel)?> y > Booting... > Boot IO Dependent Code (IODC) revision 1 > > > HARD Booted. > palo ipl 1.14 r...@duet Sat Apr 8 16:08:16 EDT 2006 > > Skipping extended partition 6 - beyond reach of IPL > > Partition Start(MB) End(MB) Id Type > > > 1 1 31 f0 Palo > > > 2 32 156 83 ext2 > > > 5 157 67413 83 ext2 > > PALO(F0) partition contains: > > 0/vmlinux64 6300839 bytes @ 0x48000 > > > Information: No console specified on kernel command line. This is normal. > > PALO will choose the console currently used by firmware (serial).Current > command line: > > 2/vmlinux root=/dev/sda5 initrd=2/initrd.img HOME=/ console=ttyS0 TERM=vt102 > > 0: 2/vmlinux > > 1: root=/dev/sda5 > > 2: initrd=2/initrd.img > > 3: HOME=/ > > 4: console=ttyS0 > > 5: TERM=vt102 > > > <#>edit the numbered field > > 'b'boot with this command line > > 'r'restore command line > > 'l'list dir > > ? 0 b > > > Command line for kernel: 'root=/dev/sda5 HOME=/ console=ttyS0 TERM=vt102 > palo_kernel=2/vmlinux' > > Selected kernel: /vmlinux from partition 2 > > Selected ramdisk: /initrd.img from partition 2 > > ELF64 executable > > Entry 0010 first 0010 n 3 > > Segment 0 load 0010 size 4648960 mediaptr 0x1000 > > Segment 1 load 005c4000 size 395160 mediaptr 0x47 > > Segment 2 load 00628000 size 304384 mediaptr 0x4d1000 > > Loading ramdisk 6339147 bytes @ 3f9e3000... > > Branching to kernel entry point 0x0010. If this is the last > > message you see, you may need to switch your console. This is > > a common symptom -- search the FAQ and mailing list at parisc-linux.org > > > Linux version 2.6.26 (2.6.26) (r...@sys0t-debian) (gcc version 4.3.2 (GCC) ) > #1 SMP Mon Mar 16 07:17:55 MDT 2009 > FP[0] enabled: Rev 1 Model 16 > The 64-bit Kernel has started... > console [ttyB0] enabled > Initialized PDC Console for debugging. > Determining PDC firmware type: 64 bit PAT. > model 5cc0 0491 0002 28f7f76d 10f0 0008 > 00b2 00b2 > vers 0203 > CPUID vers 17 rev 8 (0x0228) > capabilities 0x1 > model 9000/800/N4000-44 > Memory Ranges: > 0) Start 0x End 0x7fff Size 2048 MB > 1) Start 0x00018000 End 0x0001 Size 2048 MB > Total Memory: 4096 MB > initrd: 7f9e3000-7ffeea4b > initrd: reserving 3f9e3000-3ffeea4b (mem_max 1) > SMP: bootstrap CPU ID is 0 > Built 2 zonelists in Zone order, mobility grouping on. Total pages: 1034240 > Kernel command line: root=/dev/sda5 HOME=/ console=ttyS0 TERM=vt102 > palo_kernel=2/vmlinux > PID hash table entries: 4096 (order: 12, 32768 bytes) > Console: colour dummy device 160x64 > Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes) > Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) > Memory: 4109824k/4194304k available (3121k kernel code, 83764k reserved, > 1370k data, 300k init) > virtual kernel memory layout: > vmalloc : 0x8000 - 0x3f00 (1007 MB) > memory : 0x4000 - 0x00024000 (8192 MB) > .init : 0x40628000 - 0x40673000 ( 300 kB) > .data : 0x4040c518 - 0x40563000 (1370 kB) > .text : 0x4010 - 0x4040c518 (3121 kB) > Security Framework initialized > SELinux: Disabled at boot. > Capability LSM initialized > Mount-cache hash table entries: 256 > Brought up 1 CPUs > net_namespace: 1168 bytes > NET: Registered protocol family 16 > EISA bus registered > Searching for
Re: Cannot boot 2.6.26 kernel on HPPA N4000
On Sat, Jul 25, 2009 at 4:10 PM, Moritz Muehlenhoff wrote: > [Adding debian-hppa to CC and quoting in full] > > Is this a known issue, has it been fixed in current kernels from unstable? I believe this relates to that previous post: http://www.mail-archive.com/debian-hppa@lists.debian.org/msg06301.html Debian kernel seems to triggers HPMCs with PCI addon cards. It's been discussed previously here, dunno what the status of that bug is, but iirc it doesn't affect upstream. HTH -- Thibaut VARENE http://www.parisc-linux.org/~varenet/ -- To UNSUBSCRIBE, email to debian-hppa-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Cannot boot 2.6.26 kernel on HPPA N4000
Moritz, thanks for forwarding... On Sat, Jul 25, 2009 at 04:10:04PM +0200, Moritz Muehlenhoff wrote: > > Attempting to boot a 2.6.26 kernel on an HP N4000 machine (64 bit PA-RISC) > > yields the following results (beginning at system startup): > > <> ... > > Elroy version TR3.0 (0x4) found at 0xfecf4000 > > PCI: Address space collision on region 0 of device :d0:00.0 > > [70e0800:70e08ff] ... > > sym53c8xx :d0:00.0: enabling device ( -> 0003) > > sym53c8xx :d0:00.0: enabling SERR and PARITY (0003 -> 0143) > > > > * SYSTEM ALERT ** ... > > 0x187000FF6292 - type 0 = Data Field Unused > > 0x5800187000FF6292 6D02 100F120F - type 11 = Timestamp 03/16/2009 The address space collision is likely the cause of this HPMC. (0xff6292 == HPMC) With HPMC's, "PIM" info is worth collecting. See http://www.parisc-linux.org/faq/kernelbug-howto.html for details on how to collect PIM info. It would also be helpful to collect "in io" output from the same PDC prompt that allows one to run "ser pim" and "clearpim". Lastly, if an older kernel does boot, "lspci -v" would be helpful. > Is this a known issue, has it been fixed in current kernels from unstable? The "parenting" of resources in the generic PCI support has been changed. I can't say if it fixes this problem. Is it possible to test a 2.6.30 or 2.6.31-rc kernel? thanks, grant -- To UNSUBSCRIBE, email to debian-hppa-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Cannot boot 2.6.26 kernel on HPPA N4000
On Sat, Jul 25, 2009 at 05:08:24PM +0200, Thibaut VARENE wrote: > On Sat, Jul 25, 2009 at 4:10 PM, Moritz Muehlenhoff wrote: > > > [Adding debian-hppa to CC and quoting in full] > > > > Is this a known issue, has it been fixed in current kernels from unstable? > > I believe this relates to that previous post: > http://www.mail-archive.com/debian-hppa@lists.debian.org/msg06301.html > > Debian kernel seems to triggers HPMCs with PCI addon cards. It's been > discussed previously here, dunno what the status of that bug is, but > iirc it doesn't affect upstream. While many PCI cards won't work in PARISC systems, some do including many of those sold by HP. For generic PCI support, AFAIK, only PCI-PCI bridge support is broken and I've not tested those in a while. I have two systems setup in Cupertino Test Ring which each have one add-on card with PCI-PCI bridge (rio and ios). cheers, grant -- To UNSUBSCRIBE, email to debian-hppa-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Cannot boot 2.6.26 kernel on HPPA N4000
On Sun, Jul 26, 2009 at 4:45 PM, Grant Grundler wrote: > On Sat, Jul 25, 2009 at 05:08:24PM +0200, Thibaut VARENE wrote: >> Debian kernel seems to triggers HPMCs with PCI addon cards. It's been >> discussed previously here, dunno what the status of that bug is, but >> iirc it doesn't affect upstream. > > > While many PCI cards won't work in PARISC systems, some do including many > of those sold by HP. For generic PCI support, AFAIK, only PCI-PCI bridge > support is broken and I've not tested those in a while. I have two systems > setup in Cupertino Test Ring which each have one add-on card with PCI-PCI > bridge (rio and ios). I guess this wasn't obvious enough from the thread I was pointing to, but this bug affects otherwise perfectly working PCI cards (such as tulip, SYM2, or tg3). As I said, only 2.6.26 from Debian seems to be affected (among the few kernels I've tested). HTH -- Thibaut VARENE http://www.parisc-linux.org/~varenet/ -- To UNSUBSCRIBE, email to debian-hppa-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Cannot boot 2.6.26 kernel on HPPA N4000
On Sun, Jul 26, 2009 at 08:39:22AM -0600, Grant Grundler wrote: > Moritz, > thanks for forwarding... > > On Sat, Jul 25, 2009 at 04:10:04PM +0200, Moritz Muehlenhoff wrote: > > > Attempting to boot a 2.6.26 kernel on an HP N4000 machine (64 bit PA-RISC) > > > yields the following results (beginning at system startup): > > > <> > > ... > > > Elroy version TR3.0 (0x4) found at 0xfecf4000 > > > PCI: Address space collision on region 0 of device :d0:00.0 > > > [70e0800:70e08ff] > ... > > > sym53c8xx :d0:00.0: enabling device ( -> 0003) > > > sym53c8xx :d0:00.0: enabling SERR and PARITY (0003 -> 0143) > > > > > > * SYSTEM ALERT ** > ... > > > 0x187000FF6292 - type 0 = Data Field Unused > > > 0x5800187000FF6292 6D02 100F120F - type 11 = Timestamp 03/16/2009 > > The address space collision is likely the cause of this HPMC. > (0xff6292 == HPMC) > > With HPMC's, "PIM" info is worth collecting. See > http://www.parisc-linux.org/faq/kernelbug-howto.html > > for details on how to collect PIM info. > > It would also be helpful to collect "in io" output from the same PDC > prompt that allows one to run "ser pim" and "clearpim". > > Lastly, if an older kernel does boot, "lspci -v" would be helpful. > > > > Is this a known issue, has it been fixed in current kernels from unstable? > > The "parenting" of resources in the generic PCI support has been changed. > I can't say if it fixes this problem. Is it possible to test a 2.6.30 > or 2.6.31-rc kernel? That will be difficult for the bug submitter, since the current versions of the debian installer are not yet based on 2.6.30 AFAICT. However, maybe the PCI card, which causes the collision can be temporarily removed, so that the installation proceeds. After that, the 2.6.30 kernel from unstable could be installed and the PCI card re-plugged in. Marc, would you be able to test this? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-hppa-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Cannot boot 2.6.26 kernel on HPPA N4000
On Mon, Jul 27, 2009 at 11:16:21PM +0200, Moritz Muehlenhoff wrote: ... > However, maybe the PCI card, which causes the collision can be temporarily > removed, so that the installation proceeds. After that, the 2.6.30 kernel > from unstable could be installed and the PCI card re-plugged in. That sounds like a good idea. I don't have a better one other than providing the kernel binaries from a custom build. thanks, grant > Marc, would you be able to test this? > > Cheers, > Moritz > > > > > > > > -- To UNSUBSCRIBE, email to debian-hppa-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Cannot boot 2.6.26 kernel on HPPA N4000
On Mon, Jul 27, 2009 at 11:16:21PM +0200, Moritz Muehlenhoff wrote: > On Sun, Jul 26, 2009 at 08:39:22AM -0600, Grant Grundler wrote: > > Moritz, > > thanks for forwarding... > > > > On Sat, Jul 25, 2009 at 04:10:04PM +0200, Moritz Muehlenhoff wrote: > > > > Attempting to boot a 2.6.26 kernel on an HP N4000 machine (64 bit > > > > PA-RISC) > > > > yields the following results (beginning at system startup): > > > > <> > > > > ... > > > > Elroy version TR3.0 (0x4) found at 0xfecf4000 > > > > PCI: Address space collision on region 0 of device :d0:00.0 > > > > [70e0800:70e08ff] > > ... > > > > sym53c8xx :d0:00.0: enabling device ( -> 0003) > > > > sym53c8xx :d0:00.0: enabling SERR and PARITY (0003 -> 0143) > > > > > > > > * SYSTEM ALERT ** > > ... > > > > 0x187000FF6292 - type 0 = Data Field Unused > > > > 0x5800187000FF6292 6D02 100F120F - type 11 = Timestamp 03/16/2009 > > > > The address space collision is likely the cause of this HPMC. > > (0xff6292 == HPMC) > > > > With HPMC's, "PIM" info is worth collecting. See > > http://www.parisc-linux.org/faq/kernelbug-howto.html > > > > for details on how to collect PIM info. > > > > It would also be helpful to collect "in io" output from the same PDC > > prompt that allows one to run "ser pim" and "clearpim". > > > > Lastly, if an older kernel does boot, "lspci -v" would be helpful. > > > > > > > Is this a known issue, has it been fixed in current kernels from unstable? > > > > The "parenting" of resources in the generic PCI support has been changed. > > I can't say if it fixes this problem. Is it possible to test a 2.6.30 > > or 2.6.31-rc kernel? > > That will be difficult for the bug submitter, since the current versions > of the debian installer are not yet based on 2.6.30 AFAICT. > > However, maybe the PCI card, which causes the collision can be temporarily > removed, so that the installation proceeds. After that, the 2.6.30 kernel > from unstable could be installed and the PCI card re-plugged in. > > Marc, would you be able to test this? Marc, The next release of Debian (6.0, code name Squeeze) will be based on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell us whether the problem persists. If so, Grant should be able to debug this further. The 2.6.32 kernel is available from packages.debian.org and can be installed in both Debian stable, testing and unstable installations. Thanks, Moritz -- To UNSUBSCRIBE, email to debian-hppa-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Cannot boot 2.6.26 kernel on HPPA N4000
Moritz Muehlenhoff wrote: > On Sun, Jul 26, 2009 at 08:39:22AM -0600, Grant Grundler wrote: > > Moritz, > > thanks for forwarding... > > > > On Sat, Jul 25, 2009 at 04:10:04PM +0200, Moritz Muehlenhoff wrote: > > > > Attempting to boot a 2.6.26 kernel on an HP N4000 machine (64 bit > > > > PA-RISC) > > > > yields the following results (beginning at system startup): > > > > <> > > > > ... > > > > Elroy version TR3.0 (0x4) found at 0xfecf4000 > > > > PCI: Address space collision on region 0 of device :d0:00.0 > > > > [70e0800:70e08ff] > > ... > > > > sym53c8xx :d0:00.0: enabling device ( -> 0003) > > > > sym53c8xx :d0:00.0: enabling SERR and PARITY (0003 -> 0143) > > > > > > > > * SYSTEM ALERT ** > > ... > > > > 0x187000FF6292 - type 0 = Data Field Unused > > > > 0x5800187000FF6292 6D02 100F120F - type 11 = Timestamp 03/16/2009 > > > > The address space collision is likely the cause of this HPMC. > > (0xff6292 == HPMC) > > > > With HPMC's, "PIM" info is worth collecting. See > > http://www.parisc-linux.org/faq/kernelbug-howto.html > > > > for details on how to collect PIM info. > > > > It would also be helpful to collect "in io" output from the same PDC > > prompt that allows one to run "ser pim" and "clearpim". > > > > Lastly, if an older kernel does boot, "lspci -v" would be helpful. > > > > > > > Is this a known issue, has it been fixed in current kernels from unstable? > > > > The "parenting" of resources in the generic PCI support has been changed. > > I can't say if it fixes this problem. Is it possible to test a 2.6.30 > > or 2.6.31-rc kernel? > > That will be difficult for the bug submitter, since the current versions > of the debian installer are not yet based on 2.6.30 AFAICT. > > However, maybe the PCI card, which causes the collision can be temporarily > removed, so that the installation proceeds. After that, the 2.6.30 kernel > from unstable could be installed and the PCI card re-plugged in. > > Marc, would you be able to test this? Marc, would you be able to test this? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-hppa-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100222180807.gb17...@inutil.org
