Greetings. I haven't been able to find a single version yet in
the 2.5.x series that allows me to use SCSI emulation without a
kernel panic...until I tried a strange trick today. Even under
2.5.63, I still received the panic documented below, until I
turned on all the options under "Kernel Hacking". Then SCSI
emulation seems to work fine!
Some details: I have a dual Athlon MP2000 on an ASUS A7M266-D,
with a new IDE-ATAPI Plexwriter. I have attached the dmesg/klogd
output, the kernel panic that I painstakingly transcribed by
hand, and the kernel configuration I used. If there is anything
else needed...let me know!
---scott
On Sun, 2003-03-02 at 22:01, scott thomason wrote:
> 2.5.63, I still received the panic documented below, until I
> turned on all the options under "Kernel Hacking". Then SCSI
> emulation seems to work fine!
That might actually be useful info. What affect does the slab
poisoning option have in paticular.
On Sunday 02 March 2003 04:01 pm, scott thomason wrote:
> Greetings. I haven't been able to find a single version yet in
> the 2.5.x series that allows me to use SCSI emulation without
> a kernel panic...until I tried a strange trick today. Even
> under 2.5.63, I still received the panic documented below,
> until I turned on all the options under "Kernel Hacking". Then
> SCSI emulation seems to work fine!
Note to self: even though the panic disappears, and the device
appears in /dev, when the device is actually _written_ to using
cdrecord, various scsi errors happen. Blurf.
---scott
On Sun, 2 Mar 2003 16:01:24 -0600
scott thomason <[email protected]> wrote:
| Greetings. I haven't been able to find a single version yet in
| the 2.5.x series that allows me to use SCSI emulation without a
| kernel panic...until I tried a strange trick today. Even under
| 2.5.63, I still received the panic documented below, until I
| turned on all the options under "Kernel Hacking". Then SCSI
| emulation seems to work fine!
|
| Some details: I have a dual Athlon MP2000 on an ASUS A7M266-D,
| with a new IDE-ATAPI Plexwriter. I have attached the dmesg/klogd
| output, the kernel panic that I painstakingly transcribed by
| hand, and the kernel configuration I used. If there is anything
| else needed...let me know!
| ---scott
Need to run that oops report thru ksymoops (see the file
linux/Documentation/oops-tracing.txt) or turn on
CONFIG_KALLSYMS=y in the Kernel Hacking menu to decode all of those
hex addresses.
--
~Randy