Scanning disks -> crash!
I have a problem with my SCSI system. Not really related to
the d-i, but I thought maybe one here could help.
I've tried the new sarge installer with the following command
line (below) from my UltraSPARC-III (Blade 1000) machine.
This machine have one internal FC disk (which have woody
installed - is to be used in a CHROOT for development). Attached
to the external SCSI connectors are two MultiPack12 (each
containing 12 SCSI3 SCA disks). They are connected to the
host with 1.5 meter cables, and here lies the problem.
They must be TO long, because I keep getting SCSI resets etc.
The 'trick' seems to be the sym53c8xx option. It helps SOMEWHAT
(but not fully).
Now, the reason I take it up at all here is that MAYBE someone
know which params will help, and the other is that MAYBE the d-i
can help here. If it doesn't probe to hard, the kernel will survive.
So maybe a 'debian-installer/scsi-{probe,reset}-delay' option
perhaps!?
Picture:
http://www.bayour.com/Blade1000/THE%20Package.JPG
Boot command line (all in one line):
boot net expert BOOT_DEBUG=1 debian-installer/framebuffer=false \
debconf/priority=low sym53c8xx=tags:1,sync:10,burst:0,wide:0 \
panic=30 max_scsi_luns=1
The output (eventually) when running the d-i:
+ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ+ Starting up the partitioner +ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ+
| |
| 38% |
| |
| Scanning disks...Unable to handle kernel NULL pointer dereference |
tsk->{mm,active_mm}->context = 000000000000042c |
tsk->{mm,active_mm}->pgd = fffff800005dd000ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ+
Kernel panic: Aiee, killing interrupt handler!
In interrupt handler - not syncing
--
Nazi jihad colonel toluene Marxist bomb nitrate Ortega Ft. Meade
[Hello to all my fans in domestic surveillance] Delta Force radar
Honduras North Korea Legion of Doom
[See http://www.aclu.org/echelonwatch/index.html for more about this]
Reply to: