scsi hanging at boot, update on problem for those interested
Hi, I know that there are a few people who have reported having problems with their scsi card( esp. siig), hanging at boot; especially with the internal cdrom and external scanner combo. I was one of them. A list member previously said that it was caused by having "verbose scsi error reporting " enabled in the kernel. Well I finally got around to doing a 2.4.17 upgrade and my scsi problem at boot disappeared with the following changes. Just disable all "probing of luns", verbose error reporting, "queing checks", and logging. These are all grouped in one section under scsi. I'm not sure which one (or combo) caused the problem, but my scsi no longer hangs on boot with those changes. I'm leaning toward "probing of luns" as the culprit, but who knows. :-) Merry Christmas.
----- Original Message -----
From: "zentara"
Hi, I know that there are a few people who have reported having problems with their scsi card( esp. siig), hanging at boot; especially with the internal cdrom and external scanner combo. I was one of them.
A list member previously said that it was caused by having "verbose scsi error reporting " enabled in the kernel.
Well I finally got around to doing a 2.4.17 upgrade and my scsi problem at boot disappeared with the following changes.
Just disable all "probing of luns", verbose error reporting, "queing checks", and logging. These are all grouped in one section under scsi.
I'm not sure which one (or combo) caused the problem, but my scsi no longer hangs on boot with those changes.
I'm leaning toward "probing of luns" as the culprit, but who knows. :-)
Merry Christmas. Hi Zen
I actually went for a re-compile of the SuSE 7.3 kernel yesterday after our previous chat and verbose error checking was already disabled. I then turned off Probe all LUNs 'cos I think it helped with previous SuSEs; unfortunately I kept getting errors (mostly with Video for Linux drivers cpia, bttv etc.etc. which halted the re-compile. In the end I just gave up and pulled the power cable (no switch available) out of the scanner. Maybe I'll have another go in the, not too distant, future. Anyway, thanks for the info. and Merry Crimbo. to you too. ATB Brian PS I just logged on for 5 mins. to check my email, Honest, I'm not really a sad git 8o)
On Tuesday 25 December 2001 11:28, you wrote:
----- Original Message ----- From: "zentara"
To: Sent: Tuesday, December 25, 2001 2:26 AM Subject: [SLE] scsi hanging at boot, update on problem for those interested Hi, I know that there are a few people who have reported having problems with their scsi card( esp. siig), hanging at boot; especially with the internal cdrom and external scanner combo. I was one of them.
A list member previously said that it was caused by having "verbose scsi error reporting " enabled in the kernel.
Well I finally got around to doing a 2.4.17 upgrade and my scsi problem at boot disappeared with the following changes.
Just disable all "probing of luns", verbose error reporting, "queing checks", and logging. These are all grouped in one section under scsi.
I'm not sure which one (or combo) caused the problem, but my scsi no longer hangs on boot with those changes.
I'm leaning toward "probing of luns" as the culprit, but who knows. :-)
Merry Christmas.
Hi Zen
I actually went for a re-compile of the SuSE 7.3 kernel yesterday after our previous chat and verbose error checking was already disabled. I then turned off Probe all LUNs 'cos I think it helped with previous SuSEs; unfortunately I kept getting errors (mostly with Video for Linux drivers cpia, bttv etc.etc. which halted the re-compile. In the end I just gave up and pulled the power cable (no switch available) out of the scanner. Maybe I'll have another go in the, not too distant, future. Anyway, thanks for the info. and Merry Crimbo. to you too.
ATB Brian
PS I just logged on for 5 mins. to check my email, Honest, I'm not really a sad git 8o)
I used to have the same problem with all the SuSE kernels. The Probe all luns was turned on by default and probably still is. It is easy to fix though without a re-compile of the kernel. Add the line append = max_scsi_luns=1 in your lilo.conf, and all will be well. It is referenced somewhere in the kernel docs, but don't ask me where. Mike -- Powered by SuSE 7.3, Kernel 2.4.10 KDE2.2.1 Kmail 1.3.1 For a great linux portal try http://www.freezer-burn.org
participants (3)
-
Brian Stevenson
-
Mike
-
zentara