Re: apt-cache causes freeze and aptitude a kernel panic on hp9000 d360/2 with fresh installed debian etch
Am Donnerstag, 23. August 2007 schrieb Grant Grundler: On Wed, Aug 22, 2007 at 11:16:08PM +0200, J??rgen Leibner wrote: Hello to all, any hints to the following? Linux version 2.6.18-5-parisc-smp (Debian 2.6.18.dfsg.1-13etch1) ... Backtrace:0% [101135c4] L34+0x1c/0x84 [101093c4] handle_interruption+0x404/0x59c [1010d090] intr_check_sig+0x0/0xc Unexpected interruption: Code=20 regs=2ebd4d00 (Addr=) Run a UP kernel unless you have a 2.6.22 kernel or later. You can pull a 2.6.22 kernel from unstable: http://packages.debian.org/unstable/admin/linux-image-2.6-parisc There are known SMP bugs in the interrupt handling that didn't get fixed until shortly before 2.6.22. Thanks for your hints. Now the machine is up and running fine with a 2.6.22-2 debian kernel. Thibaut VARENE said in the other mail, that a new kernel 2.6.18 will include now the needed patch. So I tried his hint first and upgraded Yesterday to the newest etch smp kernel. It freezes with a kernel panic. So I decided to migrate to lenny/sid. Now all is running fine with smp kernel Greetings, Jürgen Leibner
Re: Hardware-List (fwd)
On Wednesday 29 August 2007, Rob Sciuk wrote: I'm having some difficulties with Debian 4.0R1 on an HP9000 Series K200, also experienced similar behaviours with Sarge 3.1R6 and Debian 4.0R0, where the install freezes/panics at the point at which it states: Freeing unused kernel memory: 328K freed. The Gentoo 2007.0 release on the otherhand goes on to boot the full live cd. I'd very much like to run Debian, though I am just now putting Gentoo on a 712/60, and I might resort to that for the K200. Can you help me out here or provide pointers which can get me through the boot process ?? Sincerely, Rob Sciuk Hi Rob, could you please post the full boot log (e.g. captured with minicom on serial port) ? Helge -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apt-cache causes freeze and aptitude a kernel panic on hp9000 d360/2 with fresh installed debian etch
On 9/4/07, Jürgen Leibner [EMAIL PROTECTED] wrote: Thibaut VARENE said in the other mail, that a new kernel 2.6.18 will include now the needed patch. So I tried his hint first and upgraded Yesterday to the newest etch smp kernel. It freezes with a kernel panic. Just for the records, quoting Dann: committed in etch branch, should release in 4.0r2 (probably 2.6.18.dfsg.1-14). This is #435878. Current kernel in etch is 2.6.18.dfsg.1-14 so afaict the bugfix hasn't been uploaded yet. HTH T-Bone -- Thibaut VARENE http://www.parisc-linux.org/~varenet/
linux32 personality config.guess
With recent 64bit kernels linux32 seems to work, $ linux32 uname -m parisc but $ linux32 /usr/share/misc/config.guess hppa2.0-unknown-linux-gnu which seems to break some configury only knowing about hppa and hppa64. Is config.guess correct, and should configure scripts be changed? Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Hardware-List (fwd)
On Tue, 4 Sep 2007, Helge Deller wrote: Date: Tue, 4 Sep 2007 22:13:24 +0200 From: Helge Deller [EMAIL PROTECTED] To: debian-hppa@lists.debian.org, [EMAIL PROTECTED] Subject: Re: Hardware-List (fwd) On Wednesday 29 August 2007, Rob Sciuk wrote: I'm having some difficulties with Debian 4.0R1 on an HP9000 Series K200, also experienced similar behaviours with Sarge 3.1R6 and Debian 4.0R0, where the install freezes/panics at the point at which it states: Freeing unused kernel memory: 328K freed. The Gentoo 2007.0 release on the otherhand goes on to boot the full live cd. I'd very much like to run Debian, though I am just now putting Gentoo on a 712/60, and I might resort to that for the K200. Can you help me out here or provide pointers which can get me through the boot process ?? Sincerely, Rob Sciuk Hi Rob, could you please post the full boot log (e.g. captured with minicom on serial port) ? Helge Full log is attached, captured with cu/tip on FreeBSD Cheers, Rob. session_log Description: Binary data
crash in mux_poll on K200/Kittyhawk (was: Hardware-List (fwd))
Forwarding to parisc-linux mailing list.
Can someone with MUX knowledge take a look into this problem ?
Additionally, does someone knows what this device is ?
12. unknown device at 0xf190c000 [10/4/12] { 2, 0x0, 0x004, 0x0005f }
Thanks,
Helge
On Tuesday 04 September 2007, Rob Sciuk wrote:
On Tue, 4 Sep 2007, Helge Deller wrote:
On Wednesday 29 August 2007, Rob Sciuk wrote:
I'm having some difficulties with Debian 4.0R1 on an HP9000 Series
K200, also experienced similar behaviours with Sarge 3.1R6 and Debian
4.0R0, where the install freezes/panics at the point at which it
states:
Freeing unused kernel memory: 328K freed.
The Gentoo 2007.0 release on the otherhand goes on to boot the full
live cd. I'd very much like to run Debian, though I am just now
putting Gentoo on a 712/60, and I might resort to that for the K200.
Can you help me out here or provide pointers which can get me through
the boot process ??
Hi Rob,
could you please post the full boot log (e.g. captured with minicom on
serial port) ?
Helge
Full log is attached, captured with cu/tip on FreeBSD
Firmware Version 2.9
Duplex Console IO Dependent Code (IODC) revision 4
--
(c) Copyright 1990-1998, Hewlett-Packard Company, All rights reserved
--
Processor SpeedState CoProcessor State Cache Size
- - - --
0 100 MHz Active Functional 256 KB
1 100 MHz Idle Functional 256 KB
Central Bus Speed (in MHz) :100
Available Memory (bytes): 536870912
Good Memory Required (bytes): 19648512
Primary boot path:10/0.6 (dec)
Alternate boot path: 10/12/5.2 (dec)
Console path: 10/4/0.0 (dec)
Keyboard path:10/12/7.0 (dec)
---
Main Menu: Enter command or menu boot alt
Booting...
Boot IO Dependent Code (IODC) revision 0
HARD Booted.
palo ipl 1.14 [EMAIL PROTECTED] Sat Apr 8 16:08:16 EDT 2006
Boot image contains:
0/vmlinux32 4191629 bytes @ 0x3885800
0/vmlinux64 5798357 bytes @ 0x32fd800
0/ramdisk 4466902 bytes @ 0x2eb1800
Information: No console specified on kernel command line. This is normal.
PALO will choose the console currently used by firmware (serial).
Command line for kernel: 'root=/dev/ram ramdisk_size=12579' console=ttyB0
TERM=vt102 palo_kernel=0'0/vmlinux'
Selected kernel: '0/vmlinux from partition 0
Selected ramdisk: /ramdisk from partition 0
Warning: kernel name doesn't end with 32 or 64 -- Guessing... Choosing 32-bit
kernelELF32 executable
Entry 0010 first 0010 n 3
Segment 0 load 0010 size 2392744 mediaptr 0x1000
Segment 1 load 00349000 size 499712 mediaptr 0x24a000
Segment 2 load 0040 size 381062 mediaptr 0x2c4000
Loading ramdisk 4466902 bytes @ 1fbac000...
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.18-5-parisc (Debian 2.6.18.dfsg.1-13) ([EMAIL PROTECTED])
(gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 Fri Jun 1
00:54:09 UTC 2007
FP[0] enabled: Rev 1 Model 11
The 32-bit Kernel has started...
Initialized PDC Console for debugging.
Determining PDC firmware type: System Map.
model 58b0 0491 0002 40696e39 10f1 0004 008a
008a
vers 000d
CPUID vers 11 rev 13 (0x016d)
model 9000/819/K200
Total Memory: 512 MB
initrd: 2fbac000-2ffee8d6
initrd: reserving 1fbac000-1ffee8d6 (mem_max 2000)
drivers/parisc/led.c: KittyHawk-Machine (hversion 0x58b) found, LED detection
skipped.
LCD display at f019,f0190001 registered
Built 1 zonelists. Total pages: 131072
Kernel command line: root=/dev/ram ramdisk_size=12579' console=ttyB0 TERM=vt102
palo_kernel=0'0/vmlinux
PID hash table entries: 4096 (order: 12, 16384 bytes)
start_kernel(): bug: interrupts were enabled early
Console: colour dummy device 160x64
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 524288k available
Security Framework v1.0.0 initialized
SELinux: Disabled at boot.
Capability LSM initialized
Mount-cache hash table entries: 512
checking if image is initramfs... it is
Freeing initrd memory: 4362k freed
NET: Registered protocol family 16
EISA bus registered
Searching for devices...
Found devices:
1. U2-IOA BC Runway Port at 0xfff8a000 [10] { 12, 0x7, 0x580, 0xb }
2. KittyHawk GSY Core BA at 0xffd0 [10/12] { 11, 0x0, 0x015, 0x00081 },
additional addresses: 0xffd0c000 0xffc0
3. KittyHawk GSY Core SCSI at 0xffd06000 [10/12/5] { 10, 0x0, 0x015, 0x00082 }
4. KittyHawk GSY Core
Re: [parisc-linux] linux32 personality config.guess
With recent 64bit kernels linux32 seems to work, $ linux32 uname -m parisc but $ linux32 /usr/share/misc/config.guess hppa2.0-unknown-linux-gnu which seems to break some configury only knowing about hppa and hppa64. Is config.guess correct, and should configure scripts be changed? GCC accepts either parisc or hppa, at least in config.gcc. I tend to think the parisc form should be deprecated since no other PA-RISC targets use it. The others all use hppa. With respect to hppa variants, this is a hopeless mess and I don't believe this can be fixed. For example, libgmp treats hppa2.0w as indicating a 64-bit runtime. I'm sure you have hit this. Nominally, the first part of the target string represents the architecture of the kernel, and not the userspace architecture. This is not sufficient to configure runtime applications when multiple architectures are supported by one kernel. Dave -- J. David Anglin [EMAIL PROTECTED] National Research Council of Canada (613) 990-0752 (FAX: 952-6602) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Unknown device 0x0005f
On Tue, Sep 04, 2007 at 11:44:29PM +0200, Helge Deller wrote:
Additionally, does someone knows what this device is ?
12. unknown device at 0xf190c000 [10/4/12] { 2, 0x0, 0x004, 0x0005f }
I don't. We don't have anything with the 0x0005f programming model in
the database. We have:
{HPHW_A_DMA, 0x004, 0x00050, 0x80, Lanbrusca 802.3 (36967A)},
{HPHW_B_DMA, 0x008, 0x00051, 0x80, HP-PB Transit 802.3},
{HPHW_B_DMA, 0x004, 0x00052, 0x80, Miura LAN/Console (J2146A)},
{HPHW_A_DMA, 0x004, 0x00056, 0x80, HP-PB LoQuix FDDI},
{HPHW_A_DMA, 0x004, 0x00057, 0x80, HP-PB LoQuix FDDI (28670A)},
{HPHW_B_DMA, 0x008, 0x00058, 0x80, HP-PB Transit 802.4},
{HPHW_A_DMA, 0x004, 0x0005E, 0x00, Gecko Add-on Token Ring},
The owner could probably help us out by taking a look at the card in
slot 10/4/12 and seeing what chips are on it, and what connectors it has.
--
Intel are signing my paycheques ... these opinions are still mine
Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Unknown device 0x0005f
On Tue, 4 Sep 2007, Matthew Wilcox wrote:
Date: Tue, 4 Sep 2007 16:15:37 -0600
From: Matthew Wilcox [EMAIL PROTECTED]
To: Helge Deller [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED],
debian-hppa@lists.debian.org
Subject: Unknown device 0x0005f
On Tue, Sep 04, 2007 at 11:44:29PM +0200, Helge Deller wrote:
Additionally, does someone knows what this device is ?
12. unknown device at 0xf190c000 [10/4/12] { 2, 0x0, 0x004, 0x0005f }
I don't. We don't have anything with the 0x0005f programming model in
the database. We have:
{HPHW_A_DMA, 0x004, 0x00050, 0x80, Lanbrusca 802.3 (36967A)},
{HPHW_B_DMA, 0x008, 0x00051, 0x80, HP-PB Transit 802.3},
{HPHW_B_DMA, 0x004, 0x00052, 0x80, Miura LAN/Console (J2146A)},
{HPHW_A_DMA, 0x004, 0x00056, 0x80, HP-PB LoQuix FDDI},
{HPHW_A_DMA, 0x004, 0x00057, 0x80, HP-PB LoQuix FDDI (28670A)},
{HPHW_B_DMA, 0x008, 0x00058, 0x80, HP-PB Transit 802.4},
{HPHW_A_DMA, 0x004, 0x0005E, 0x00, Gecko Add-on Token Ring},
The owner could probably help us out by taking a look at the card in
slot 10/4/12 and seeing what chips are on it, and what connectors it has.
I can photograph it, if you like, how does one determine where slot
10/4/12 is?? I know that there are a couple of mux boards on the back,
but frankly I haven't opened up the box as of yet. Pointers?
Cheers,
Rob.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
